SDS200 Proscan Audio

[ripper1234]

I keep losing the comm port and audio with my SDS200 when connected with URL, it says in the log of Proscan that it is still connected to source client. I just have to turn the SDS200 off and back on each time to connect the Comm port and audio again. Any suggestions would help? I am using windows 10 Pro .

 

[jonwienke]

Set the scanner to a static IP. Otherwise your router may periodically assign it a different IP address and break the connection with ProScan (or any other software).

 

[ripper1234]

Set the scanner to a static IP. Otherwise your router may periodically assign it a different IP address and break the connection with ProScan (or any other software).

Just did that, will see if that works.

 

[K4AOL]

I have 2 SDS200s and was running proscan for months, yesterday I lost speaker audio of both scanners if scanners are connected by USB. Closed Proscan disconnected scanners and restarted radios and they work. plug in USB without starting proscan and they go quiet again. Only thing I can think of is reinstall drivers and proscan.

 

[ProScan]

I have 2 SDS200s and was running proscan for months, yesterday I lost speaker audio of both scanners if scanners are connected by USB. Closed Proscan disconnected scanners and restarted radios and they work. plug in USB without starting proscan and they go quiet again. Only thing I can think of is reinstall drivers and proscan.

Power cycle the scanner.

{Edit} Are you using the Ethernet connection for the audio?

 

[ripper1234]

Power cycle the scanner.

So i have to power cycle the scanner everyday?

 

[K4AOL]

Power cycle the scanner.

Closed Proscan disconnected scanners and "restarted radios and they work. plug in USB without starting proscan and they go quiet again." Only thing I can think of is reinstall drivers and proscan.

 

[ProScan]

So i have to power cycle the scanner everyday?

Shouldn't. The only time the scanner needs power cycling to restore the audio is if the Ethernet connection is flaky or the computer/ProScan shuts down unexpectedly. That is because the scanner audio protocol didn't receive the TEARDOWN command and the protocol locks up internally.

I would investigate what changed in your setup if it was running good for months.

 

[ripper1234]

Shouldn't. The only time the scanner needs power cycling to restore the audio is if the Ethernet connection is flaky or the computer/ProScan shuts down unexpectedly. That is because the scanner audio protocol didn't receive the TEARDOWN command and the protocol locks up internally.

I would investigate what changed in your setup if it was running good for months.

hmm not seeing anything with the connection of the computer, well in logs of the modem or router log. not sure if there is a lan connection log for proscan to hub.

 

[ProScan]

When you plug in the USB cable the audio goes quiet. It sounds to me like the Ethernet cable could be bumped. Reseat the Ethernet cable or swap the cable to see if it makes a difference.

 

[ProScan]

not seeing anything with the connection of the computer, well in logs of the modem or router log. not sure if there is a lan connection log for proscan to hub.

Not the computer connection but rather the scanner Ethernet connection.

 

[pzav]

Does anyone have any update on a solution for the dropping of connections? I'm new to Proscan and my SDS200, and things work well for a few hours, but then Proscan drops the network connection to the scanner. The SDS200 is still operating. Powercycling the scanner sometimes fixes it.

I'm running everything on stable network hardware locally.

 

[ProScan]

Does anyone have any update on a solution for the dropping of connections? I'm new to Proscan and my SDS200, and things work well for a few hours, but then Proscan drops the network connection to the scanner. The SDS200 is still operating. Powercycling the scanner sometimes fixes it.

I'm running everything on stable network hardware locally.

What have you done to troubleshoot this? Did you read the tips in the URL Setup window?

 

[ProScan]

Does anyone have any update on a solution for the dropping of connections? I'm new to Proscan and my SDS200, and things work well for a few hours, but then Proscan drops the network connection to the scanner. The SDS200 is still operating. Powercycling the scanner sometimes fixes it.

I'm running everything on stable network hardware locally.

Have you checked the following?
Insure you're not running AVG Antivirus software. Don't use that as that will interrupt TCP connections.
Make sure all the Ethernet cables are good and seated firmly in the connectors.
Insure the scanner is using the latest firmware.
Insure no other apps or other instances of ProScan are not using the same scanner LAN audio connection.

 

[buddrousa]

I have 16 scanners running on the same PC with no problems for over a year.
1. I hate DHCP and cheap routers I static address 99% of everything on my network.
2. I have windows automatic update turned off I do mine myself.
3. I have turned off hibernate harddrive sleeping and anything else that powers off or puts the PC to sleep.

 

[sparkydude]

I have the same problem almost everyday. My ProScan connection is fine with less than 1% packet loss, then, in the afternoon or evening packet loss jumps to 60-70 % and of course all is lost. Restart the BCD536 ( I have two running on different PC's ) usually solves the problem. So similar problem, but I don't think the problem is ProScan.

 

[belvdr]

I would not suggest static addressing anything these days. There are no issues with DHCP; simply use reservations for what you need, such as the scanner and the PC.

 

[ProScan]

I have the same problem almost everyday. My ProScan connection is fine with less than 1% packet loss, then, in the afternoon or evening packet loss jumps to 60-70 % and of course all is lost. Restart the BCD536 ( I have two running on different PC's ) usually solves the problem. So similar problem, but I don't think the problem is ProScan.

It sounds like you have Wi-Fi interference. Try relocating the scanner & dongle.