BC125AT: Driver COM port problems

[Fallguy67]

When I initially installed the USB driver and ran the Uniden Programming Software everything worked just fine. However the next time the computer did not recognize the scanner (BC125AT) even after trying to auto detect the COM port and choosing "update driver" in the device manager it still would not recognize it until I restarted the computer.

However, no, even after restarting the computer, uninstalling the driver and basically starting from scratch, nothing I can do will let the computer recognize the scanner.

Any help or suggestions is greatly appreciated.

 

[Scan125]

Which version of Windows are you using. W7, W8.1 or W10?

If W10 then older versions of MS .NET incorrectly enumerated USB ports (often adding strange characters to the real port - e.g. COMn becoming COMn~ etc.

If you don't want to mess with .NET then you can try my free Scan125 Control Program which works with the Uniden 125 and 126 series of scanners (see my signature below for link)

Scan125 "cleanses" badly enumerated COM port numbers and works on W7 through to W10. Not tested on Vista, XP or 2000 but should be OK.

Another point to bear in mind is that from W8.1 and above Windows requires security signed drivers. The driver will comprise TWO files, a .INF and a .CAT file and BOTH have to be present when installing.

Earlier Uniden drivers were not signed but still exist and are used by many programs. The required signed driver is the "Uniden Universal Serial Driver".

 

[UPMan]

Does the system recognize that anything at all is plugged in? (i.e. Does it "kerchunk" when you plug in the scanner?)

 

[Fallguy67]

Scan125: I am using Windows 10, I do also have your program as well and enjoy it. However I would have the same problem with it. I do have the .INF and .CAT files

UPMan: Yes it does do the "kerchunk" when plugged in.

***UPDATE**

It seems the problem occurred when I was using a different USB cable than the one that came with the scanner. When I used the cable that came with the scanner I didn't have any problem at all. Go figure.

Thank you for you help!!

 

[Scan125]

Interesting. So I gather you are saying that the Uniden provided USB cable works perfectly OK but others don't.

This has to be a question for UPMan to define/explain any cable differences between Uniden originally supplied cables and standard USB cables.

If/when I get a chance I'll play with alternative but industry standard USB cables and see if I have the same issues.

 

[UPMan]

I don't know of any reason. The main difference between the supplied cable and most other cables is the RF choke in ours, that helps reduce conducted RF. I've used many other cables to connect, though.

 

[Unforgiven_AF]

Interesting. So I gather you are saying that the Uniden provided USB cable works perfectly OK but others don't.

This has to be a question for UPMan to define/explain any cable differences between Uniden originally supplied cables and standard USB cables.

If/when I get a chance I'll play with alternative but industry standard USB cables and see if I have the same issues.

I come from the Android world, and there is often a problem where aftermarket USB cables don't work while OEM cables do. Normally, it isn't so much what the OEMs do to make their cables work, but that many aftermarket cables are garbage. If you identify a good brand (I swear by Anker for phone cables but they don't have the ends for these scanners) you should be good to go with aftermarket. If you are buying the $3.99 10 pack at a convenience store, probably not so much.

 

[Fallguy67]

Interesting. So I gather you are saying that the Uniden provided USB cable works perfectly OK but others don't.

This has to be a question for UPMan to define/explain any cable differences between Uniden originally supplied cables and standard USB cables.

If/when I get a chance I'll play with alternative but industry standard USB cables and see if I have the same issues.

That is correct.

It is probably as Unforgiven_AF says and just the quality of the other cable I was using.