SDS100/SDS200: Odd Behavior on Simulcast

[KevinC]

To add to my post, it took me a while to figure out what was happening. I'd turn on the scanner and notice minutes later I hadn't heard any traffic, I'd power cycle and it usually fixed it (sometimes it took a couple of power cycles). I noticed as @RMason mentioned that it would lock onto a frequency that wasn't a CC and just stay there. Once I removed all the non-CC frequencies and put the most used CC first in the list I never had the issue again.

 

[KevinC]

I appreciate everyone's help in this matter.

I would power cycle a bunch of times and see if it keeps on working.

 

[afchev]

To add to my post, it took me a while to figure out what was happening. I'd turn on the scanner and notice minutes later I hadn't heard any traffic, I'd power cycle and it usually fixed it (sometimes it took a couple of power cycles). I noticed as @RMason mentioned that it would lock onto a frequency that wasn't a CC and just stay there. Once I removed all the non-CC frequencies and put the most used CC first in the list I never had the issue again.

After messing with the SDS100 before I downloaded the updated Frequency list, it definitely appeared to be locked on a non-CC frequency. I even manually selected a TG that I was hearing on the SDS200 and still the radio wasn't picking it up, and wasn't changing frequencies. So I do believe this may be the problem. SDS100 has now been updated and is working just fine now and is echoing what the SDS200 is hearing. I'll keep these settings for now and see if the problem replicates itself.

 

[KevinC]

After messing with the SDS100 before I downloaded the updated Frequency list, it definitely appeared to be locked on a non-CC frequency. I even manually selected a TG that I was hearing on the SDS200 and still the radio wasn't picking it up, and wasn't changing frequencies. So I do believe this may be the problem. SDS100 has now been updated and is working just fine now and is echoing what the SDS200 is hearing. I'll keep these settings for now and see if the problem replicates itself.

I reported this issue in the forums before but it doesn't appear Uniden has acted on it.

 

[RMason]

@JoeBearcat - it seems that the sds will sometimes lock onto an IV&D channel instead of the control channel. It will lock onto a frequency that isn't a CC and just stay there. The firmware should be able to distinguish between an IV&D channel and a control channel.

 

[KevinC]

@JoeBearcat - it seems that the sds will sometimes lock onto an IV&D channel instead of the control channel. It will lock onto a frequency that isn't a CC and just stay there. The firmware should be able to distinguish between an IV&D channel and a control channel.

He was active in my thread about it almost 3 years ago...

SDS100/SDS200: - Not finding CC

This may happen to the SDS200 also as well as others models, but I've confirmed it on my SDS100. Randomly I turn my SDS100 on and it will show it's sitting on a frequency and will show "DATA", but the system ID, site number and RFSS are blank and it won't receive any calls. Today I confirmed it...

forums.radioreference.com

 

[mule1075]

No, I'm using a global filter.

Ok cool it was just a thought.