Whistler-upgraded 668 > 1080 no longer shows up as a USB device

[sempai]

hi,

I sent my Radio Shack 668 p25 scanner to Whistler for the update to listen to DMR. I got the scanner back and it has some differences and at least the object browser isn't totally ignorant of DMR anymore so presumably it worked.

But it no longer shows up as a USB device. I was prepared to do the unsigned driver song and dance and nothing was working so I hitched it up to a machine in my household IT rack and `lsusb` doesn't see it no matter what power state it's in and I've tried two USB cables (they are mini USB, the larger small end, not micro USB) and I can't get the scanner to be recognized in Windows 10 on two VMs on two different hypervisors, nor does it show up as a USB device when I plug it into any of the macOS workstations I've got on my desk at home.

Can't say I expected a problem like this. Is there something I have to do in order to enable the USB data interface or to mount the µSD (microSD) card or speak to the scanner to haul my config into the Whistler software? Do I have to call or email Whistler about this? The sheet of paper I had in the box when it came back didn't mention anything like this.

 

[RaleighGuy]

If you installed the software and drivers it should be working. If not you might need to contact @Whistler_Support , but it sounds like a computer hardware issue on your side, not the scanner.

 

[Wackyracer]

Double check the instructions that came with the scanner, do not miss a step. Sounds like the WS1080 comport driver is not installed or working. (The pro-668 driver will not work on a WS1080). Make sure your usb cable and port are working correctly.

Technically you do not need any of that to program it if you have a sdcard reader PLUS it is 10times faster.

 

[tvengr]

☞ Don't forget this... (whistlergroup.com)

 

[sempai]

Reply

If you installed the software and drivers it should be working. If not you might need to contact @Whistler_Support , but it sounds like a computer hardware issue on your side, not the scanner.

On four? Five computers? It doesn't show up on the USB bus even, driver or no driver it should show up on the USB bus. I'll engage support but I'm not sure a different computer will change things. I've just done a manual database update by mounting the µSD card and unzipping Whistler's latest into my scanner.

 

[JD21960]

Investigate "digital signatures, Whistler drivers" in the search box above. There are a few steps to follow to do that. My WS1080 needed to have the signature security on Windows turned off temporarily* that's a TEMP thing for those who went crazy over this same thing back then* .... to work right. Then you reboot. Worked fine ever since

 

[sempai]

There are a few steps to follow to do that. My WS1080 needed to have the signature security on Windows turned off temporarily* that's a TEMP thing for those who went crazy over this same thing back then* .... to work right. Then you reboot. Worked fine ever since

I've done that just like I've done it for it back when it was still a Pro-668. It's asinine they won't sign the g-ddamned driver but I even built a new Windows 10 VM again and it doesn't matter if I've got the driver installed or not. It charges over USB but it does not register on the bus. As devices are attached/removed they are detected and identified e.g. several of my computers are on UPS so I can keep working through a power outage for about 48 minutes or safely power down equipment that shouldn't just get switched off, so many of them have a USB interface to the UPS to communicate with it about how severe the situation is:

Feb 22 17:53:10 post kernel: [21394.984811] usb 2-4: new low-speed USB device number 57 using xhci_hcd
Feb 22 17:53:10 post kernel: [21395.139010] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 22 17:53:10 post kernel: [21395.139011] usb 2-4: Manufacturer: Tripp Lite
Feb 22 17:53:10 post kernel: [21395.160558] hid-generic 0003:09AE:2012.0563: hiddev0,hidraw0: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:00:14.0-4/input0
Feb 22 17:55:05 post kernel: [21510.506536] usb 2-10: new full-speed USB device number 60 using xhci_hcd
Feb 22 17:55:05 post kernel: [21510.506642] usb 2-10: Device not responding to setup address.

It's possible that usb 2-10 there might be the scanner, but lsusb doesn't see it and it doesn't respond the way xchi/ehci expects for some reason. There's a HID device and that UPS that show up correctly because they get picked up and identified.

 

[JD21960]

This is why I dual boot now (Use Linux 99% of the time) instead of looking at a box inside a box ...it all gets tedious

 

[sempai]

It isn't like virtualization is complicated, but that capture from lsusb was done on-console on a linux system, nothing detects the device from a system xhci/ehci level before the Whistler driver would pick it up is all. I'm going to ship it back i guess 😂