Why is my EDACS in Limbo?
What's up with EDACS? What's the "Limbo" thing? Read on ...
See the pattern?
Here's the explanation:
The monitored system is in "Limbo" because the EDACS control channel does not provide system identity - only site identity. You can't tell if a site belongs to a previously logged system. On the calls tab, the program will indicate "Frequency needed!". Fill in the frequency for the control channel and your "Limbo" site should go away. This is a manual process each time you start a new decoding session.
What's up with EDACS? What's the "Limbo" thing? Read on ...
rdale said:EDACS error... Import the data from RR and I've got groups and my frequencies filled in. Exit the software, start back up - and it ignores the existing system and starts tracking a new system (labeled "Limbo") and I have to repeat the process.
Homeboyscanna said:The "Limbo" EDACS problem occurs for me as well, exactly the way rdale described it.
Cappyton said:When ever the signal is lost or i close UT and reopen it it saves all my setting and such, but when i go to enble RUN it willnot load my edacs system. It will always find the same system and make a new system entry called Limbo. Even when i delete it a new one pops up. It wont reopen the one i have all the TG's saved in.
See the pattern?
Here's the explanation:
The monitored system is in "Limbo" because the EDACS control channel does not provide system identity - only site identity. You can't tell if a site belongs to a previously logged system. On the calls tab, the program will indicate "Frequency needed!". Fill in the frequency for the control channel and your "Limbo" site should go away. This is a manual process each time you start a new decoding session.