SR30C ANY SR30C User Out There

[DudleyG]

I don't have a SR30C scanner. One thing to try - sometimes the software on the computer is very picky about the baud rate. I just tried several of my Uniden scanners (BCD325P2 and BCD160DN) attached to a Windows 10 computer and the scanners by default, all attached at baud rate of 9600. You can see the rate by right clicking on the COM PORT in Device Manager. Try changing the baud rate and see if that helps - Just a long shot!

 

[eddferrell]

I don't have a SR30C scanner. One thing to try - sometimes the software on the computer is very picky about the baud rate. I just tried several of my Uniden scanners (BCD325P2 and BCD160DN) attached to a Windows 10 computer and the scanners by default, all attached at baud rate of 9600. You can see the rate by right clicking on the COM PORT in Device Manager. Try changing the baud rate and see if that helps - Just a long shot!

Thanks DudleyG, I initially started with the default baud rate of 9600 several weeks ago and then other rates up to 57600. It seems from my limited knowledge that the scanner will work with anything from 9600 to 57600 because the software will look for the baud rate of the COM port and use that. Just for fun, I did just change the baud rate of the COM3 port in device manager to 9600 and try the Uniden software and the Scan75 software with the same (bad) result.
The odd part is that the program PuTTY (at 57600 baud) can talk to the scanner (MDL, VOL, SQL, BAV, etc.), send commands to the scanner (i.e. VOL,5), and change the scanner settings (i.e actually changes the scanner volume); but other programs cannot. None of them (except PuTTY) see a scanner present, or can find a scanner on any COM port.
Thanks for the suggestion. Every bit helps.
Edd

 

[eddferrell]

So this is just to wrap up this post for others with similar issues. It turns out that sometimes it's the scanner. After several different computers, several different cables, several different scanner programs, and trying every COM port and driver setting combination possible, the only thing left was a problem with the scanner.
I've had amazing support from Nick, the creator of Scan125 and Scan75. He provided custom versions of his software that logged extra information to troubleshoot the problem. The results were erratic answers from the scanner and no conclusive results. We both agree that it must be the scanner. Maybe a bad memory chip, bad firmware (non-upgradable), bad "something-or-other"... but with everything else ruled out, it is the scanner.
It took about 20 minutes to manually program the scanner with 60 frequencies. Sometimes you just need cut your losses and admit defeat.
Thank you Nick for all of your hours of help and correspondence! Hopefully this thread will help others in the same situation.
Edd