Network connection causing SDS200 to go deaf.

[r6daddy]

I can reproduce the issue by not power cycling the the scanner daily as I have been doing. Eventually, there will be a loss of audio that is only remedied by power cycling. This has occurred at random intervals. It may occur after one day or as long as six or seven days. You can review earlier posts back and forth between me and ProScan for specifics. Programming the scanner has been static with no changes lately. I update from RR weekly and check for Scanner updates at that time. Yes, I am willing to test. I power cycled last evening, 5/24. Going forward, I will not. I'll let you know when the audio is lost again so tests can be run if you like.

 

[phd-2]

I wonder if someone can test changing the IP on the scanners involved (especially those who have two or more units and only one with the issue). We will be fine as long as the thread does not become a debate.

What would you like me to change the IP addresses to? I have 3 SDS200's. I have tried isolating them on a VLAN (thus running different IPS addresses and subnet) for a few weeks so the only traffic they saw was to proscan but that didn't prevent the problem. It *MAY* have increased the amount of time it took to repro it.

 

[kd8wlu]

Quick update on this issue: Updated to ProScan 21.2 on 5/31 and audio has been stable since (1 week). No other changes made to environment or settings.

 

[ProScan]

Quick update on this issue: Updated to ProScan 21.2 on 5/31 and audio has been stable since (1 week). No other changes made to environment or settings.

No changes in 21.2 in this area FYI. Maybe the intermittent may take time to show up. Don't know.
My theory is the scanner processor has to work harder when using the rtsp and maybe it's causing a heat related issue.

 

[r6daddy]

My last reboot of the scanner was 5/27. Shortly after that, I upgraded ProScan to 21.2 also. So far, so good. Keeping my fingers crossed. Previous to the upgrade, I ran my Web Server 24/7. After the upgrade, I did not start it to see if by chance, that was causing the issue. I will keep all updated.

 

[kd8wlu]

After almost two weeks, the SDS200 went silent again this morning. Rebooted and back with audio.

 

[KevinC]

After almost two weeks, the SDS200 went silent again this morning. Rebooted and back with audio.

I may have missed this in an earlier post, but what happens if you don't start ProScan and just let it run with the network plugged?

 

[KevinC]

I may have missed this in an earlier post, but what happens if you don't start ProScan and just let it run with the network plugged?

Replying to my own thread to avoid any edit conspiracies...

I would try this myself, but I've had mine running on ProScan for weeks now with no lost audio.

 

[r6daddy]

After almost two weeks, the SDS200 went silent again this morning. Rebooted and back with audio.

Day 16 here and there is still audio coming from the SDS200. Were you running the Web Server when the audio quit? I normally do, but have chosen not to do so after the last reboot as a test. The SDS is still connected to another PC via Ethernet but not running the Web Server. This allows me to listen remotely via ProScan.
@JoeBearcat Any progress questioning Uniden if there is a logfile for this scanner and how to retrieve it?

 

[RMason]

if there is a logfile for this scanner and how to retrieve it?

Do the instructions on the sds100/200 wiki page for creating a debug file work?

SDS100 and SDS200 FAQ Page - The RadioReference Wiki

wiki.radioreference.com

 

[KevinC]

Do the instructions on the sds100/200 wiki page for creating a debug file work?

SDS100 and SDS200 FAQ Page - The RadioReference Wiki

wiki.radioreference.com

I wonder how big those files can be? The instruction say to run the log for a few minutes and it appears to take weeks for this issue to happen sometime apparently.

 

[r6daddy]

Do the instructions on the sds100/200 wiki page for creating a debug file work?

SDS100 and SDS200 FAQ Page - The RadioReference Wiki

wiki.radioreference.com

Many thanks for sending this information. I will wait until my audio quits and will run this procedure after the next start of the scanner that fixes the audio. Not sure if the scanner retains the information needed or if it is erased with the restart. Also, I'll need someone to interpret the file. Perhaps@JoeBearcat can comment.

 

[KevinC]

Many thanks for sending this information. I will wait until my audio quits and will run this procedure after the next start of the scanner that fixes the audio. Not sure if the scanner retains the information needed or if it is erased with the restart. Also, I'll need someone to interpret the file. Perhaps@JoeBearcat can comment.

It gets erased upon a power cycle as far as I know.

 

[JoeBearcat]

What would you like me to change the IP addresses to? I have 3 SDS200's. I have tried isolating them on a VLAN (thus running different IPS addresses and subnet) for a few weeks so the only traffic they saw was to proscan but that didn't prevent the problem. It *MAY* have increased the amount of time it took to repro it.

I guess the ideal test would be to swap the IPs between a working unit and the unit with the issue, then see if the issue changes units.

 

[r6daddy]

Update:
Day 22 with no audio problems. As stated in my previous post, I am running ProScan v21.2 and I am not running the web server. Previous to this 22 day run, I ran the web sever so I could listen remotely on my phone via the URL and designated port. Could this be a lead to the cause? I will continue to run as is for a few more weeks. I will then start the web server and will see what happens. The SDS200 is currently connected via Ethernet to a PC running ProScan. This allows me to listen to my scanner on the PC via ProScan.

 

[phd-2]

I guess the ideal test would be to swap the IPs between a working unit and the unit with the issue, then see if the issue changes units.

I’m not sure I understand what you are asking. I have 3 SDS200’s and all of them exhibit this problem and have since they were new. They’ve been assigned many different IP’s over time and even different subnets and VLANs at times.

 

[kd8wlu]

I'm only running (1) SDS200, but tried changing my IP as suggested by @JoeBearcat (different static IP assignment, same VLAN, same network speed). ~48 hours later had the same problem of no audio from the stream and no audio from the SDS200 speaker.

Second experiment: disable ProScan Comm Port connection over URL and keep audio URL stream. I ran in this configuration for about 1 week without issues, but no audio happened again over the weekend while I was out.

 

[KevinC]

I'm only running (1) SDS200, but tried changing my IP as suggested by @JoeBearcat (different static IP assignment, same VLAN, same network speed). ~48 hours later had the same problem of no audio from the stream and no audio from the SDS200 speaker.

Second experiment: disable ProScan webserver and keep audio URL stream. I ran in this configuration for about 1 week without issues, but no audio happened again over the weekend while I was out.

This is so weird. For the life of me I can't duplicate it.

 

[r6daddy]

Bummer. Thanks for the report. I'm still OK after 30 days. I will start the web server tomorrow to see what happens. Will report back.

 

[r6daddy]

Update:
Started web server at the end of day 30. Ran full 8 days with web server on and audio is still good. Today, I started port forwarding so I can listen outside of the LAN. Will report back. This is the configuration I was running when audio was lost in the past. The only thing that has changed is the f/w revision.