CHIRP

James Coon wrote:

(Describe what you were doing) I click on download radio data.

(Describe what you expected to happen) Connect to radio and download data.

(Describe what actually happened instead) I get an error message: "Error reading data from radio". The radio turns off and back on again.

(Has this ever worked before? New radio? Does it work with OEM software?) New radio. It does not work with OEM software, GMRS_50V2_CPS.

I have been online with BTech Support. I checked the COM Ports in Device Manager. Tried to reinstall FTDI CDM Drivers but what I had was good and the Installation Wizard did not update the software.

I have restarted the computer several times.

I have the latest version of CHIRP Next 20250117.

BTech Support asked me to submit this Bug Report.

Hi James, your debug log shows that CHIRP is not getting anything at all from the radio. Assuming you're choosing the right radio and port in the download box, the only other things that could cause this are:

1. Cable plugged into the wrong port on the radio
2. Cable not fully seated in the radio
3. Defective cable
4. Defective radio

The fact that it doesn't work with the OEM software is a great hint that it's something cable or radio related.

I seem to recall it is possible to use the wrong cable to plug into a different port on this radio, which confuses people. You might check related issue #10638 where it looks like that is what has happened.

Hello Dan,

That is exactly what I was telling BTech Support. The fact that it does not work with CHIRP on Windows or Mac Or OEM GMRS_50V2_CSP on Windows that it must be either the cable or the radio. Katy got a little snippety with me and told me to focus on CHIRP so I submitted this report as requested by her. I ordered another cable today.

The cable is connected to the correct port on the front of the radio.

Thank you for your time.

Sent with Proton Mail secure email.

On Monday, January 20th, 2025 at 11:01, Dan Smith redmine@chirpmyradio.com wrote:

Cool, probably the best use of your time to prove the cable as the fault, assuming it is. We might also tag @Jim Unroe as I think he knows about these radios and can comment on the cable confusion issue.

I'll leave this open, please comment about the outcome and then we can address or close as appropriate.

Thanks!

Hi James, would you try selecting the port using the "Help Me..." choice at the bottom of the list of Port: choices. I am just wondering if you might have more than one FTDI chip based programming cable plugged into your computer and the one at COM3 is not the one that is plugged into the GMRS-50V2. This could happen, for example, if you have a PC3 2-pin style programming cable for a handheld radio and a the PC04 style programming cable that is required for the GMRS-50V2 plugged in at the same time. Each one would get its own COM port assigned by the operating system.

The radio is powered on, right? I have to ask because I helped someone else that couldn't program their mobile radio because it was not powered on.

If neither of these scenarios are not the case, then I would agree it is either a problem with the programming cable and/or the radio.

Definitely worth a shot, but his debug log shows only a single port:

[2025-01-19 19:00:09,346] chirp.wxui.clone - DEBUG: All system ports: [{'device': 'COM3', 'name': 'COM3', 'description': 'USB Serial Port (COM3)', 'hwid': 'USB VID:PID=0403:6015 SER=DU0D6FCWA', 'vid': 1027, 'pid': 24597, 'serial_number': 'DU0D6FCWA', 'location': None, 'manufacturer': 'FTDI', 'product': None, 'interface': None}]

But, if that doesn't disappear when unplugging ("help me" will tell us) then maybe that's something else.

Nice. I didn't realize the debug.log does that now so I didn't look for it. Thanks.

Dan,

I know you had to ask. Yes the radio is turned on. When I get the error message, the radio turns off and back on again. There are 2 LED lights at the USB end. The green light comes on when plugged in. When I click the OK button, the other LED has a mili-second red flash then the error and the radio turns off and back on. So there is some sort of communication.

I only have the one cable plugged into the computer. When I unplug it, the COM 3 port in Device Manager goes away. So the computer is seeing it and it is the correct cable.

James

Sent with Proton Mail secure email.

On Monday, January 20th, 2025 at 17:01, Jim Unroe redmine@chirpmyradio.com wrote:

Hmm, the green light stays on solid? I'm not sure about this particular cable, but most of the FTDI cables I have with green and red lights use them for RX and TX respectively. The lights flash when data is sent, but aren't solid. Does the green light go out if you unplug the radio side of the cable?

If the radio resets that means it's getting the start command from chirp (which would correlate with the red light blinking). If the receive side (green light) is stuck such that chirp doesn't receive anything from the radio, that would explain chirp thinking the radio has not responded. Still, ether cable or the radio itself would be my suspicion. If the green light is solid even with the radio disconnected, then that would, to me, suggest something is up with the cable.

Yes, I just plugged the cable into the computer only and the green light is on all the time.

Sent with Proton Mail secure email.

On Monday, January 20th, 2025 at 20:12, Dan Smith redmine@chirpmyradio.com wrote:

Okay, perhaps it's wired as a power light on that cable, but if not it certainly lines up with chirp getting nothing back from the radio. It'll definitely be interesting to compare it to the behavior of the new cable.

I should have it by the end of the week, hopefully sooner. I will ask BTech support if the green light is wired for power on.

Sent with Proton Mail secure email.

On Monday, January 20th, 2025 at 20:19, Dan Smith redmine@chirpmyradio.com wrote:

Reply from BTech:

No the green light should not always be on

Katy

Sent with Proton Mail secure email.

On Monday, January 20th, 2025 at 20:19, Dan Smith redmine@chirpmyradio.com wrote:

It does the same on the Mac with the laptop closed and asleep. As soon as it is plugged in, the green light comes on.

Sent with Proton Mail secure email.

On Monday, January 20th, 2025 at 20:19, Dan Smith redmine@chirpmyradio.com wrote:

Reply from BTech:

No the green light should not always be on

Yeah, I thought not :)