SDS100/SDS200: Not finding CC

[pro106import]

Monitoring a site I don't normally monitor today. It's a very heavy data user site and I didn't realize I had all 10 frequencies programmed in. After about 5 minutes of no voice I noticed it was stuck on a data channel, removed all but the 4 CC's and it's taking away now.

I wonder how many people are having this issue and don't actually realize it???

Yes I have had to do this from the get go. But for a different reason, possibly related.
The squelch setting of 2 is too tight for the radio to receive the control channel consistently on a few of the distant systems I monitor. So I have to leave the squelch to open ( 0 or 1 ). For some reason, when the squelch is open, the radio seems not to consistently remember the active CC when scanning through each of the 4 of them every time it comes back around to that system. Maybe it is getting stuck on some noise or data since the squelch is open, IDK. So what I do to get around this is I have each possible control channel programmed as their own separate site on each system. So when the control channel changes, I just have to enable the site that has the active control channel. Yes, I put this on "THE LIST" way back a couple- three years ago to make the squelch presets more detailed on the lower (2-5) settings since anything after 5 is useless. Simple fix that I can do on a professional radio in 2 min. in the tuning mode.

 

[Ubbe]

Yes, I put this on "THE LIST" way back a couple- three years ago to make the squelch presets more detailed on the lower (2-5) settings since anything after 5 is useless. Simple fix that I can do on a professional radio in 2 min. in the tuning mode.

Moving the current 0-5 to instead by covered by 0-20 would let us use SQ settings equal to 1,25 and 1,5 and 1,75.

I would also like to see an option where you set a flag to a site or system that tells to temporarily set SQ to 0 and then restore it to previous value when leaving the site or system. It's not always preferred to have a low SQ setting to analog systems. Some Motorola radios have dual squelch, that when the signal gets weak it opens the squelch more, so it automatically adjusts the squelch to the signal strength so that you don't get a squelch tail when the signal are strong.

/Ubbe

 

[pro106import]

Moving the current 0-5 to instead by covered by 0-20 would let us use SQ settings equal to 1,25 and 1,5 and 1,75.

I would also like to see an option where you set a flag to a site or system that tells to temporarily set SQ to 0 and then restore it to previous value when leaving the site or system. It's not always preferred to have a low SQ setting to analog systems. Some Motorola radios have dual squelch, that when the signal gets weak it opens the squelch more, so it automatically adjusts the squelch to the signal strength so that you don't get a squelch tail when the signal are strong.

/Ubbe

Great suggestions Ubbe. Just that simple fix would make the radio much more usable. Doesn't look like it's ever going to happen.
I am glad there are other choices out there now with the emergence of @btt 's Blue Tail's stand alone unit where you can set each system or frequency to its own unique squelch threshold! And he updates his firmware with practically DAILY improvements from peoples requests.

 

[KevinC]

Great suggestions Ubbe. Just that simple fix would make the radio much more usable. Doesn't look like it's ever going to happen.
I am glad there are other choices out there now with the emergence of @btt 's Blue Tail's stand alone unit where you can set each system or frequency to its own unique squelch threshold!

But unfortunately does nothing for the issue I found.

 

[pro106import]

But unfortunately does nothing for the issue I found.

Yes, sorry it got a little off your issue. My fault. I guess the bottom line here is that nothing is getting fixed.

 

[donc13]

Yes, sorry it got a little off your issue. My fault. I guess the bottom line here is that nothing is getting fixed.

Who said that? Certainly no one associated with Uniden.

 

[pro106import]

Who said that? Certainly no one associated with Uniden.

Actions ( or lack there of ) speak louder than words.

 

[KevinC]

Who said that? Certainly no one associated with Uniden.

And Don Starr has spoken! Sorry, I couldn't resist.

 

[donc13]

And Don Starr has spoken! Sorry, I couldn't resist.

You're forgiven. 😊👹

 

[KevinC]

After having removed all but the possible control channels and putting ones that are obviously set to a preference of 1 first in the CC list I’ve had zero instances of failing to find the control channel upon power up in the last year. Now if we can only get anything on “the list” to actually be addressed.

 

[pro106import]

After having removed all but the possible control channels and putting ones that are obviously set to a preference of 1 first in the CC list I’ve had zero instances of failing to find the control channel upon power up in the last year. Now if we can only get anything on “the list” to actually be addressed.

Have patience. It's only been another year since we last talked about it. Give it another year or so.
Keep that squelch set to zero in the meantime.

 

[GTR8000]

After having removed all but the possible control channels and putting ones that are obviously set to a preference of 1 first in the CC list I’ve had zero instances of failing to find the control channel upon power up in the last year. Now if we can only get anything on “the list” to actually be addressed.

C'mon now, Rome wasn't built in a day. Although I also don't know that it took 2 years and 3 months.

 

[W5ATX]

Did you try rotating your coax?

 

[KevinC]

I sent a message to Uniden Japan, will advise when I hear back.

Maybe you can send them a message and see if they can address the issue I reported in the thread below over 3 1/2 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

 

[jasonhouk]

Maybe you can send them a message and see if they can address the issue I reported in the thread below over 3 1/2 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

Kevin,

Added to the issue log for UJE to review. Included link to original issue reported here in RR

 

[KevinC]

Kevin,

Added to the issue log for UJE to review. Included link to original issue reported here in RR

Thanks. I’m available for testing if needed as it’s extremely easy for me to replicate.

 

[jasonhouk]

Thanks. I’m available for testing if needed as it’s extremely easy for me to replicate.

UJE will analyze and asked for a debug log for the channel that is being falsely detected as a control channel.

Boot up while holding down the AVOID key, Set Debug Log Mode will be added to the Settings Menu.
After selecting SD Card and receiving that channel, stop logging and send me the log file and I’ll upload for analyzation.

 

[KevinC]

UJE will analyze and asked for a debug log for the channel that is being falsely detected as a control channel.

Boot up while holding down the AVOID key, Set Debug Log Mode will be added to the Settings Menu.
After selecting SD Card and receiving that channel, stop logging and send me the log file and I’ll upload for analyzation.

Here you go.

 

[KevinC]

And 852.4375 is the IV&D frequency it interpreted as a control channel. Once data stopped on that frequency it moved on and found a CC. If I pick the extremely busy simulcast the IV&D data sometimes never stops and it will get stuck forever.

 

[KevinC]

For anyone's curiosity, you can see the SDS100 identified 852.4375 as a control channel, when it was actually a IV&D (data) channel...

0038908 output_control_ch()
0038908 OK : output_trunk_freq(channel_lch = 65535) = 08524375
0038908 PLL,08524375
0038908 TERMINATOR
0038917 SP0 DA1: 0253 FIR2: C08B
0038918 SC0 DA1: 0253 FIR2: C08B
0038951 TERMINATOR
0038956 SP1 DA1: 0253 FIR2: 3333
0039090 LC
0039106 TERMINATOR
0039122 TERMINATOR
0039138 TERMINATOR
0039181 LC
0039214 SC1 DA1: 01CC FIR2: 3333
0039214 evnt_idscan_sigrec(C)