SDS100/SDS200: Clicking Noise SDS 200

[buddrousa]

Has to be a hardware change when supplies were short supply. We know this with the 996p2's as I would suspect in the other models.

 

[ofd8001]

Could be the repeaters for their systems have a shorter hang time. Thus clicking isn’t as noticeable.

 

[werinshades]

Could be the repeaters for their systems have a shorter hang time. Thus clicking isn’t as noticeable.

Have you tried programming as an OFT system and see if the problem persists?

 

[ofd8001]

As this doesn’t seem to happen on TRS I suspect OFT would work. But every time I go that route, I seem to miss short transmissions.

 

[buddrousa]

The hang time is different between Conventional and Trunking.
Conventional the repeater hangs transmitting the nac just like the old days of CTCSS Tones.
Trunking Systems the Repeater drops and the scanner sits on the Control Channel Decoding non-repeated DATA Stream waiting for the time out nothing going to the Audio Amp.

 

[ofd8001]

I e-mailed Uniden Support and this is what they had to say:

"We have passed the information along to the development team so that the issue may be addressed in a future firmware update."

 

[EAFrizzle]

I e-mailed Uniden Support and this is what they had to say:

"We have passed the information along to the development team so that the issue may be addressed in a future firmware update."

Translation: We don't really care.

I updated both my SDS 100 & 200 the same day the updates came out. Both have the clicking on conventional systems now. If Uniden decides to fix it, great. If not, no biggie for me. Even if they fix it, that won't make the SDS scanners worth a flip on VHF or Analog.

 

[werinshades]

I have a 2024 manufactured date SDS200 in my collection along with previous year manufacture dates. I can't report the "clicking noise" when I run my P25 or DMR systems in conventional mode with the latest firmware. I normally run them in OFT, but since I read this, reprogrammed a few of them conventionally as an experiment. It's possible it has less to do with firmware and more to do with a hardware conflict? Might have been a hardware change during 2024?