SDS100, BCD536HP/ProScan just stops

[USASA]

Bob:

I think I did answer your questions. I have stated many times the message that I get on ProScan and in windows. I have stated that no other com port is in use. I have stated that the cable is the one supplied by Uniden and that I did try other cables same result. I have stated the programs that both computers have in common just incase it is a conflict there. Others have had similar problems, as stated here. I do not know what else to say. Both the SDS100 and the BCD536HP have the same problem, just not as common on the BCD536HP as it is on the SDS100. The BCD536HP just stops, no message. To restart, pull the USB from the computer, re-plug it in and it may restart it may not. If not turn off the radio and start over. Some times that is what I have to do with the SDS100. That is it in a nut shell. There has to be some kind of a fix, if is is Unidens or ProScan's. I do not know one or the other or both. But it is more prevalent in the SDS100. That will only run for a hour or less, the BCD536HP may run all night without a hiccup or it may drop out a few times. Out here!

AL
USASA

 

[ProScan]

Bob:

I think I did answer your questions. I have stated many times the message that I get on ProScan and in windows. I have stated that no other com port is in use. I have stated that the cable is the one supplied by Uniden and that I did try other cables same result. I have stated the programs that both computers have in common just incase it is a conflict there. Others have had similar problems, as stated here. I do not know what else to say. Both the SDS100 and the BCD536HP have the same problem, just not as common on the BCD536HP as it is on the SDS100. The BCD536HP just stops, no message. To restart, pull the USB from the computer, re-plug it in and it may restart it may not. If not turn off the radio and start over. Some times that is what I have to do with the SDS100. That is it in a nut shell. There has to be some kind of a fix, if is is Unidens or ProScan's. I do not know one or the other or both. But it is more prevalent in the SDS100. That will only run for a hour or less, the BCD536HP may run all night without a hiccup or it may drop out a few times. Out here!

AL
USASA

Perhaps I'm not clear on the message. The message "in use by another instance" is not a valid ProScan message. ProScan will either show "in use by this instance" or "in use by another program". It may seem petty but it's important so I can try to get a better grasp on the problem. Can you post screenshots of the ProScan message along with the Windows message?

I and others went through a similar problem a few years ago where a user insisted many times that another problem wasn't using the comm. port. He finally used a utility program that found another program was using the comm. port.

I haven't seen this problem before as you're describing it. Regarding the other person stating that he has the same problem in this thread. I'm not sure what's going on there but he copied your words exactly. The message you and he are seeing isn't a valid ProScan message. Also you and he are stated that a scanner power cycling would resolve the problem "sometimes". Power cycling the scanner should resolve the problem every time. So basically, I don't think it's the same problem.

 

[ProScan]

Thanks for emailing me. As you know, I sent you two test files and they didn't fix the problem. The 1st one swapped out the Serial Port control with a Microsoft Serial Port control. No change on your side. The 2nd one turned off the RTS & DTR signals. They are not used by the scanner but I found out a long time ago, that a certain driver didn't work with DTR and RTS off so I turned the signals on. Anyways, I don't think anything can be done in ProScan. The serial port has been time tested for many years with zero issues. I would say the problem is more at the USB level. ProScan serial port operates at the application level.
My suggestions are 1) Swap the cables connected to the 536 and SDS100. Since the 536 doesn't do it as often, see if the problem follows. 2) Perhaps it could be the SD memory cards as they are known to cause all kinds of strange problems. 3) Perhaps don't use a modified USB cable with a switch as that could introduce other problems. 4) For a test, use a computer without any other software installed. 5) Try running the computer and scanner on the same power strip if not already. 6) If using a USB hub, then eliminate that.

 

[USASA]

Bob:

I have used a number of cables, changed ports (4-10), used different SD cards (3). The switch in the USB line, only came way after the problem was occurring. I have plugged the radio directly into the computer, no change there. I have tried almost every thing short of standing on one foot and whistling Dixie. That will be my last resort. It may be something I will just have to live with. Thanks for the help, keep up the good work. If anything changes I will let you know.

Al
USASA

 

[ProScan]

Perhaps google "utility to detect usb problems"
I see a "Microsoft Windows USB Troubleshooter" tool in many of the hits. Also this is another hit

How to Diagnose USB Problems - MajorGeeks

A frequent issue with USB ports is random disconnects and reconnect for no apparent reason. In this guide, we look at possible ways to fix this problem.

www.majorgeeks.com

or google "utility to detect serial port driver problems" (I haven't tried this one)