Pro-106: Can't update Firmware

[menket01]

I have a Radio Shack Pro-106 scanner that I want to update from UpApp version 1.8 to 2.1. It also has DSP AppVer 1.4 and VocVer 1.0. I've tried upgrading to both 1.9 and 2.1 - both fail via the updater application - I can get to the step where it tests the connectivity to the scanner but it fails saying "No data from the scanner. Please retry from step 1."

I know I have the correct COM port and that my cable is good as I've used ARC500 scanner software to program it successfully and move data in both directions.

Any suggestions would be greatly appreciated. I'm following the steps exactly and entering the "CPU SW Upgrade" mode by pressing PRGM while powering up the scanner. I'm running on a Windows 10 laptop.

Thanks!

 

[gmclam]

To get the radio into firmware update mode, you must hold down the PGM key while powering on the radio. Do that before running the update application.

 

[menket01]

Thank you - just double checked that - put the scanner into firmware update mode prior to starting the update app. Same problem exists - no data from scanner, restart from Step 1.

 

[tvengr]

Is this the updater you are using? Save the attached zipped file to your computer and extract.

 

[menket01]

Yup, that's the one I'm using. Can't get either the CPU or DSP patches to load. I downloaded the version in your post and get the exact same response. I'm using the Silicon Labs driver and CP210x UART interface. That works fine with the ARC500 software to move data in either direction.

 

[tvengr]

If you have a mono adapter on the cable, remove it. Dumb question: Are you plugged into the PC/IF jack, not the headphone jack?

 

[menket01]

No mono adapter, plugged into the correct PC/IF jack. I tried the setup on another Windows 10 computer - same exact problem. Wondering if its a Windows 10 driver issue. The PC sees this as a CP2102 adapter. Odd that works fine with ARC500 for programming but not with DSP and CPU firmware updates. Thanks for your suggestion.

 

[tvengr]

Remove the batteries for several minutes with no external power, and then try it again. If that doesn't do it and the scanner boots up normally, do the following: Turn the scanner off. Turn the scanner on. At the welcome screen, press 0 and then press 2. That will reset the scanner without erasing the memory. Try updating the firmware again.

 

[pro92b]

The latest driver is 10.1.10. It was released in part to support Windows 10 20H2. If you are using an older driver, try updating. Aside from possible driver issues, a failure to communicate with the radio is often caused by a wrong comport number being specified. Triple check that you have the right comport number as listed in Device Manager.

Silicon Labs Virtual COM Port (VCP) Universal Driver for Windows 10
Package version: 10.1.10
Release date: 2021-01-13

CP210x USB to UART Bridge VCP Drivers - Silicon Labs

The CP210x USB to UART Bridge Virtual COM Port (VCP) drivers are required for device operation as a Virtual COM Port to facilitate host communication with CP210x products. These devices can also interface to a host using the direct access driver.

www.silabs.com

 

[menket01]

tvengr-did both, no change
pro92b-removed device and driver, reinstalled and checked to make sure I have the 10.1.10 driver - redownloaded, reinstalled, same outcome. I make certain I am choosing the correct Com Port (3 in my case). Only thing I noted was that my driver shows 10.1.10 103 but displayed driver date is 1/8/21 not 1/3/21 as shown above and in the download description on silabs site.

Thank you both for the recommendations. I'm going to take a closer look at the UART I purchased. It's working fine with ARC500 but not this cpu and dsp firware upgrade routine.

 

[gmclam]

Using the correct cable is essential. I know the real cable costs $35 and it's tempting to use something else; but the real cable handles all the GRE models. The RS 20-047 works with older models (like PRO-92) as well as the newer models (PRO-106) even though the earlier models shared a single connection for RX/TX and the newer models have them on separate wires. Additionally, newer models work at a higher baud rate. These details are all handled by the app software and cable driver.

I've never seen a GRE model that needed the pigtail. Also, GRE has a newer model cable that works just fine; P/N 100-016.

 

[menket01]

That may very well be my issue. I've wired up my own cable using an old stereo jack and a CP2102 USB-to-UART. Works fine with ARC500 but maybe it doesn't work for the firmware updates. I'm really enjoying the PRO-106 now that I'm figuring out how to program it using software. I'll probably just invest in the correct cable and give it a go. Thanks to all for the advice - and I'm learning a ton on this site - I'm now a huge fan!

 

[tvengr]

What is your city and county in Michigan? I use ARC500 also.

 

[menket01]

Rochester Hills, Oakland County

 

[menket01]

Received my new cable today. It works. Lesson learned - the CP2102 homemade cable worked fine for ARC500 programming and backups, but not with the firmware updates. I bought this one off ebay. Came labeled as Whistler but works great:


Thanks again for the help.

 

[gmclam]

Had you built your own cable using the FTDI chip, it would have probably worked. Years ago I tried to design a cheaper version of that cable and got one working, but it wasn't cheap enough to produce.

 

[Nasby]

Had you built your own cable using the FTDI chip, it would have probably worked. Years ago I tried to design a cheaper version of that cable and got one working, but it wasn't cheap enough to produce.

I tried it also but the time I spent wasn't worth it. These days I put a high premium on my time.
I ended up buying one on Ebay for 20 bucks.