So you just answered your own question BAD 92.
Radioshack 20-047 programming cable issues
- Thread starter Cobra_Commander
- Start date
I just don't think it's likely;
1) I have owned the Pro-92 since brand new and it's been babied
2) The Pro-2067 experiences the exact same failure. I think the chances of two Pro92's (ok, one is a 2067 but they're basically the same) having the same, rare failure are very slim
3) The Win-92 software does initiate the download (the screen on the pro-92 switches to the sending data mode exactly the same way the Pro-95 does with Win95). It seems the Win-92 is waiting for a data packet that is not coming (or if it's coming, Win92 is not seeing) for some reason... As far as the Pro-92 is concerned, it is sending the data (it takes a few minutes and it 'colors in' a progress bar across the screen of the scanner).
Ok look at from this point.
1. You Cannot connect to it with a PC.
2. You cannot clone it with a 2067 using a different cable.
That does not leave many if any options.
1. You Cannot connect to it with a PC.
2. You cannot clone it with a 2067 using a different cable.
That does not leave many if any options.
I did not try #2 yet (Cloning between the 92 and 2067). I only tried downloading from the Pro-92 to the computer and from the 2067 to the computer with Win92 and neither was successful. I will try cloning directly from one scanner to the other without the computer and see what happens.
I assume I need a stereo (3 connector) cable between the two scanners?
Thanks for the continued help. I'm determined to get this to work.
What I do not find is what OS are you using 11 64 PRO?
I am using Windows 11 Enterprise (64 bit OS). I have also tried running Win92 in Vista and Windows 7 compatibility modes, even though Win95 runs fine natively in Windows 11, and honestly Win92 at least appears to run fine and is able to send data through the cable (you can tell because the Pro-92 or 2067 screen changes to show that it starts to send data when I click Download from Scanner in Win92).
I have also tried on a Windows 10 machine with identical results.
I have tried running Win92 elevated (run as Administrator) with identical results.
Last edited:
Have you tried changing the comport speed to 9600?
I verified that the port defaults to 9600 so every time I plug it in it's set this way (see below) but I also tried again with it at 9600 to be sure.
COM7 is a higher number than we used to have in older versions of windows, but both Win95 and Win92 allow setting the COM port to 7
COM7 is a higher number than we used to have in older versions of windows, but both Win95 and Win92 allow setting the COM port to 7
I tried cloning from the Pro-92 to the Pro-2067 with a mono cable and it worked!
I tried cloning from the Pro-95 to the Pro-92 and, while both scanners went into clone mode, and both screens changed when I initiated a Send from the Pro-95, BOTH scanners said they were in Send mode (!) and the transfer didn't work.
New theory: the digital logic voltage levels are not the same between the Pro92/2067 and the Pro-95. That could explain why everything "kind of" works with the Pro-92 but not really. It could also explain why a cable that works with the Pro-95 doesn't work with the Pro-92 and 2067.
The only evidence I have to support this theory is here: GRE Programming Cables -> "For the PRO-92 the allowable voltage is 0 - 5 volts while the newer radios, PRO-93, PRO-95, and PRO-96, require a 0 - 3.5 volt input."
I tried cloning from the Pro-95 to the Pro-92 and, while both scanners went into clone mode, and both screens changed when I initiated a Send from the Pro-95, BOTH scanners said they were in Send mode (!) and the transfer didn't work.
New theory: the digital logic voltage levels are not the same between the Pro92/2067 and the Pro-95. That could explain why everything "kind of" works with the Pro-92 but not really. It could also explain why a cable that works with the Pro-95 doesn't work with the Pro-92 and 2067.
The only evidence I have to support this theory is here: GRE Programming Cables -> "For the PRO-92 the allowable voltage is 0 - 5 volts while the newer radios, PRO-93, PRO-95, and PRO-96, require a 0 - 3.5 volt input."
I am at a loss as I said before I only use Factory Cables 3 EF Johnsons for my 5100/5300's 2 Kenwoods for my NX-5200/Nx-5300/Nx-5700/Nx-5800's TK790's TK7120's
The PRO-92 is a 5 volt design. Later models are 3.3v designs. The correct cable has an open collector output so that the RX can be pulled to the correct voltage.
I built my own cable a while back and found the 20-047 design to be quite interesting. The physical 3.5mm plug is stereo, but whether or not a signal is applied (or received) on the ring depended on the application. Earlier models performed TX & RX both on the tip (which would only require a mono connection). Later models separated RX & TX and required the stereo plug.
tvengr
Well Known Member
Download and install ARC500 for the free trial period. Go to the Scanner tab and click on Install USB Driver. It installs a generic driver which will work with most cables.
Thanks for that confirmation!
Any idea if this very simple download-only cable for the pro-92 would work with a USB-to-DB9 adapter? I assume they have 5V available from USB.
YES!
Finally some success. Years ago I bought some CP2102 modules to make programming cables for other radios. I found one (which I think was a computer PTT input for an Icom) which looked like it might work. It was wired to the 5V side (not the 3.3V). I plugged it in and successfully downloaded the memory contents of the Pro-92. I did not try uploading but I will when I build a proper cable.
@Cobra_Commander Perhaps this was your issue as well? Looks like you also posted the same question on Reddit 2 weeks ago?
All of these people might have the same issue:
The OP, @Cobra_Commander
@cws1970; PRO-92 Cloning Problem
@radar614 : Pro 2067 won't take upload
The signature is unique enough that I think these may all be the same issue (despite what @DonS says here about the DLL package; PRO-92 Software - Win92 - Data Management for the RadioShack PRO-92/2067 Trunking Scanner )
So for anyone Googling this problem in the future- make sure your cable uses 5V TTL serial outputs, not 3.3V
Finally some success. Years ago I bought some CP2102 modules to make programming cables for other radios. I found one (which I think was a computer PTT input for an Icom) which looked like it might work. It was wired to the 5V side (not the 3.3V). I plugged it in and successfully downloaded the memory contents of the Pro-92. I did not try uploading but I will when I build a proper cable.@Cobra_Commander Perhaps this was your issue as well? Looks like you also posted the same question on Reddit 2 weeks ago?
All of these people might have the same issue:
The OP, @Cobra_Commander
@cws1970; PRO-92 Cloning Problem
@radar614 : Pro 2067 won't take upload
The signature is unique enough that I think these may all be the same issue (despite what @DonS says here about the DLL package; PRO-92 Software - Win92 - Data Management for the RadioShack PRO-92/2067 Trunking Scanner )
So for anyone Googling this problem in the future- make sure your cable uses 5V TTL serial outputs, not 3.3V
You show a path for TX to the scanner, but don't show RX. As I recall, one issue from this post was something like "waiting for reply from scanner". That will certainly happen if you don't have a path to RX on the PC side.
Yes! That is intentional. This is a simple one-way (download from PC to scanner only) cable. In Win92, if you are not trying to upload from scanner to PC and don't have "verify data" turned off, you can just spit data out without a return path.
However, I believe the point is moot now that the culprit seems to be the logic levels (at least for me).
I wonder if all those lists of scanner programming cables out there should have an extra attribute added (5V or 3.3V). Do any scanners use 2.5V or 1.8V logic??
Similar threads
BCD325P2/BCD996P2:
BCD996P2-Bad data cable