SDS200: Help...strange new issue - analog signals only

[Storm5m]

My SDS200 monitors an analog EDACS system as well as some digital systems. Lately after being on for some time, all analog transmissions will be distorted and sound "robotic" with scratchy distortion. My SDS100 has never had this issue and can receive the same signals in the same location without issue. Once this distortion starts only a power cycle will resolve. I have changed filter settings, moved the unit and swapped antenna. While this is happening all digital signals will sound fine. It is not the speaker either as audio sound distorted when passed through Proscan (ethernet) as well. This never happened until recently but now happens often with no changes to the EDACS programming or firmware. I do tend to leave the unit on quite a bit since it feeds Proscan. Should this unit go back to Uniden for repair?

 

[hiegtx]

My SDS200 monitors an analog EDACS system as well as some digital systems. Lately after being on for some time, all analog transmissions will be distorted and sound "robotic" with scratchy distortion. My SDS100 has never had this issue and can receive the same signals in the same location without issue. Once this distortion starts only a power cycle will resolve. I have changed filter settings, moved the unit and swapped antenna. While this is happening all digital signals will sound fine. It is not the speaker either as audio sound distorted when passed through Proscan (ethernet) as well. This never happened until recently but now happens often with no changes to the EDACS programming or firmware. I do tend to leave the unit on quite a bit since it feeds Proscan. Should this unit go back to Uniden for repair?

I had something roughly similar with my SDS100. One day, it starting ignoring certain systems that I knew were programmed correctly, and not set as Avoid. In theory, the SD card is used to load your selected lists and other details when the scanner is turned on, and then for recording (if Replay is activated), or recording all calls if you have made that choice. But we have seen a number of other issues, from time to time, which in theory should not have been related to the memory card, such as randomly rebooting the scanner.

In my case, I formatted the card, used Sentinel to 'clear user data' to prepare the card, then reloaded all the Favorites lists, the problem went away & has not recurred since. (I also had a spare card, if needed, but it was not necessary for this instance.) I would suggest formatting the card with the SD Memory Card Formatter. Then use 'Clear User Data', from the drop-down Scanner menu in Sentinel. And, finally, reload the card via Sentinel. Might make a difference, might not. But in any case, it will only take a few minutes to try, and no cost, other than your time, is involved.

 

[Storm5m]

Thank you! I followed your steps. Will see what happens.

 

[Storm5m]

I had something roughly similar with my SDS100. One day, it starting ignoring certain systems that I knew were programmed correctly, and not set as Avoid. In theory, the SD card is used to load your selected lists and other details when the scanner is turned on, and then for recording (if Replay is activated), or recording all calls if you have made that choice. But we have seen a number of other issues, from time to time, which in theory should not have been related to the memory card, such as randomly rebooting the scanner.

In my case, I formatted the card, used Sentinel to 'clear user data' to prepare the card, then reloaded all the Favorites lists, the problem went away & has not recurred since. (I also had a spare card, if needed, but it was not necessary for this instance.) I would suggest formatting the card with the SD Memory Card Formatter. Then use 'Clear User Data', from the drop-down Scanner menu in Sentinel. And, finally, reload the card via Sentinel. Might make a difference, might not. But in any case, it will only take a few minutes to try, and no cost, other than your time, is involved.

Thank you! I followed your steps. Will see what happens.

 

[JoeBearcat]

Check your power supply.

 

[Storm5m]

Check your power supply.

Thank you. I am using the Factory "wall wart" AD-1009 but I do have that plugged into a CyberPower UPS. Any concern with the UPS?

 

[Storm5m]

@JoeBearcat I have always felt like my SDS200 was defective, a dud or a lemon. It has never performed as well as my SDS100 (even outside of this newer interference issue) but that can be subjective (SDS100 vs SDS200) and hard to prove. I took a chance and ordered a new SDS200 to run side by side with my original SDS200. I have always wanted to do this although this is an expensive troubleshooting option. All of my intuitions were immediately confirmed. The new SDS200 performs like my SDS100. It picks up signals that the original SDS200 unit does not. I am noting improved RSSI values of 10-15dBm at the same location and with the same antenna. I called support and was told send it in for repair for $89.95 since it is 14 months old. I understand that you are not service, nor is it your role to intervene but I most say that I am disappointed in Uniden's response. I am so heavily invested with Uniden. I have other scanners outside of the SDS series as well. I did not expect to hear that I should send it in for repair at a steep cost since it is two months out of warranty. I am not sure how to write this up correctly in a repair order to avoid disappointment. I was hoping they could do some troubleshooting or diagnostic before shipping it out. My fear is this same defective unit will be sent back to me. Happy to have a new unit that is working great, but frustrated and unsure of next steps for my original SDS200. Thank you for listening to my rant.

 

[JoeBearcat]

As for the repair costs, those are generally flat rate, and are the costs even if it costs twice as much to repair (in which case it would be a bargain).

As for it being 14 months old, it is unfortunate this test was not performed sooner or even sent in for possible repair under warranty.

I'm not sure what response you are looking for. I can empathize that you did not suspect this during the warranty period.

Personally, I would look at the antenna port to make sure the center pin is not damaged. Next, I would look at the connection to the board.

 

[pchasse]

Did this repair get completed and did it resolve the original issue? I am having the exact same issue, precisely as the OP describes except I only monitor P25 digital not EDACS alongside mostly analog. A restart fixes it each time but that’s not ideal for recording and logging etc. My scanner is days old w/ latest firmware installed. Wondering if I too have a dud.

 

[Storm5m]

The repair was completed but I am not sure that it has resolved the issue. While the SDS200 was out for repair, I purchased a 2nd SDS200. I can tell you that the 2nd SDS200 has the same issue but possibly less often. If I leave the scanner on for an extended time for the purpose of monitoring with Proscan, it will have the same issue and need to be rebooted. I have only had the issue with analog thus far. It's hard to say if the issue was resolved on the original unit sent in for repair as I don't use that one as often now. Sorry I couldn't be more helpful but the fact that this happened with two different units make me think it's possibly inherent to the scanner.

 

[pchasse]

@JoeBearcat Care to make any comment? Is this a known issue and perhaps in the pipeline for a firmware fix. There seem to be numerous threads in this forum with awfully similar symptoms. Or is a return in order here? Hard to justify this $ on a scanner that can’t reliably scan. Might also add, that would be a shame as it’s a beast. Amazing. So I’d be happy to hang out for a patch.

 

[MStep]

Did this repair get completed and did it resolve the original issue? I am having the exact same issue, precisely as the OP describes except I only monitor P25 digital not EDACS alongside mostly analog. A restart fixes it each time but that’s not ideal for recording and logging etc. My scanner is days old w/ latest firmware installed. Wondering if I too have a dud.

It's possible in some of the aforementioned situations, overheating of some part could be the culprit. Semiconductor shortages have caused some manufactures to likely switch to parts which were not originally certified for their particular use. If you've only had the radio for a few days and are already experiencing issues, the easiest "fix" is to return the radio for a refund. You could try reordering from a different source, or perhaps wait some time and hope that your next order will be from a different "batch" of units.

The folks at Radio Reference might consider setting up a serial number database for folks to report and to help identify particular batches of radios with specific issues.

 

[Ubbe]

It's possible in some of the aforementioned situations, overheating of some part could be the culprit.

It's difficult seeing that as a reboot fixes the problem without being powered off long enough to allow cooling down.

The firmware code in Uniden scanners are not of the highest quality. When I generate a test signal with a modulated 1KHz tone and tune the SDS100's receiver over the frequency bands where it receives mixing products with that 1KHz tone distorted it suddenly reboots, probably due to some buffer overflowing that isn't error trapped and the program goes astray and a watch dog function resets the scanner.

/Ubbe

 

[pchasse]

... with that 1KHz tone distorted it suddenly reboots, probably due to some buffer overflowing that isn't error trapped and the program goes astray and a watch dog function resets the scanner.

I'd pay good money for a crash to reboot.

This bug/defect is insidious in that the digital reception is unaffected while analog goes silent. So, a good bit of time can go by before I realize something is wrong - usually when a busy dispatch channel is quiet for too long or one particular analog channel comes in (just that one) as a robotic distorted voice (like a voice box). And, alas, that makes the scanner useless for unattended logging/recording. And that's why I got it.

If anyone knows the command to force a reboot (over LAN ethernet) I'd love to know that - as to setup a chron job. There's a button in ProScan, so it is possible, but not sure if there's an API endpoint of some kind to hit, of if relies on some other protocol (like serial over ethernet). In the end though, if unresolved soon, it's looking like a return and a different model. I have no time or shipping $ for a rig lottery. That would be super disappointing considering my long wait for this model particularly.

 

[gdasilva]

@JoeBearcat My unit is about six months old and I having the same issue...replaced SD card and antenna...reboot fixes issue every time. I have to reboot roughly every 24 hours.
I dont have this issue with my sds100 or my 436hp....
I'm very disappointed

 

[gdasilva]

@JoeBearcat in case you were wondering I"m using a new 32gb Samsung Endurance Pro Sd Card and am using a MoonRaker Base antenna and Oem power brick directly connected to the wall.
Sounds like sending out to repair will be futile, am I wrong? Please kindly advise me on what to do now.

 

[donc13]

I certainly haven't read every thread in this forum, not even every thread since I got my SDS200 in March.

That being said, it would seem to ME that a few common things appear to be occurring from the recent threads.

1. The radio is left on 24/7
2. (and probably why #1) the audio is being fed to someone like Broadcastify.
3. Many, if not all are using ethernet to grab the audio.
4. Turning the radio off and on always clears the problem. That tells me it's not a hardware issue but rather software.
5. Unknown if all are using the same software to grab and push the ethernet audio to Broadcastify.

.My way too old brain (that used to code 6502's in assembly language) is telling me the firmware for the ethernet (as someone else suggested) is overflowing a stack or buffer somewhere and that part of the firmware should be gone over with a fine tooth comb.

Especially since Paul had more "plans" for both USB and ethernet, but sadly, some of those plans passed when Paul passed.

And finally the developer of ProScan said a few days ago that he can (has) the ability to detect some audio issues and force a reboot of the SDS200. Perhaps he might want to add (or not) the equivalent of a cron job to reboot every X days at a certain slow time as an option.

Anyway, that's just my thoughts for whatever they are worth.

 

[JoeBearcat]

I am following this issue although I have not seen any common themes yet.

Can someone with the issue try a higher quality 12V power supply as a test?

Ubbe can you cite details on your test?

 

[gdasilva]

I am following this issue although I have not seen any common themes yet.

Can someone with the issue try a higher quality 12V power supply as a test?

Ubbe can you cite details on your test?

Oem powerbrick not good enough?
i have run my rig on a 12volt automotive test bench with enough "clean power' and have had the same issue.

I certainly haven't read every thread in this forum, not even every thread since I got my SDS200 in March.

That being said, it would seem to ME that a few common things appear to be occurring from the recent threads.

1. The radio is left on 24/7
2. (and probably why #1) the audio is being fed to someone like Broadcastify.
3. Many, if not all are using ethernet to grab the audio.
4. Turning the radio off and on always clears the problem. That tells me it's not a hardware issue but rather software.
5. Unknown if all are using the same software to grab and push the ethernet audio to Broadcastify.

.My way too old brain (that used to code 6502's in assembly language) is telling me the firmware for the ethernet (as someone else suggested) is overflowing a stack or buffer somewhere and that part of the firmware should be gone over with a fine tooth comb.

Especially since Paul had more "plans" for both USB and ethernet, but sadly, some of those plans passed when Paul passed.

And finally the developer of ProScan said a few days ago that he can (has) the ability to detect some audio issues and force a reboot of the SDS200. Perhaps he might want to add (or not) the equivalent of a cron job to reboot every X days at a certain slow time as an option.

Anyway, that's just my thoughts for whatever they are worth.

I agree with @donc13 , I too run an ethernet to pc.
@JoeBearcat its not a power problem.

 

[Ubbe]

Ubbe can you cite details on your test?

SDS100 test
/Ubbe