Project

General

Profile

Actions

Bug #11835

closed

Bad ack from radio using PC04 cable

Added by Hank Blackwood 5 months ago. Updated 4 months ago.

Status:
Not a bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/15/2025
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
BTECH UV-25X4 G2
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

(Describe what you were doing) - Trying to connect radio to CHIRP and dowload from radio to PC.

(Describe what you expected to happen) I expected the few channels programmed into the radio would be retrieved into CHIRP

(Describe what actually happened instead) - After entering the correct com port and radio model, and clicking the start to download, error msg - bad ack from radio

(Has this ever worked before? New radio? Does it work with OEM software?) It does not work with BTECH software. This is a new radio. bought it and the cable from BTECH (UV-25X4 and PC04).


Files

config.txt (1.53 KB) config.txt Hank Blackwood, 02/15/2025 06:39 PM
win_system_info.txt (85.3 KB) win_system_info.txt Hank Blackwood, 02/15/2025 06:39 PM
debug_log.txt (7.84 KB) debug_log.txt Hank Blackwood, 02/15/2025 06:39 PM

Related issues 1 (0 open1 closed)

Has duplicate Bug #11872: Bad ack from radioRejected03/02/2025

Actions

Updated by Hank Blackwood 5 months ago

[Uploaded from CHIRP next-20250214]

Actions #2

Updated by Dan Smith 4 months ago

If it doesn't work with the OEM software, then it's not a CHIRP bug. I believe it's common that people use the wrong cable with this radio, perhaps @Jim Unroe can confirm that here. Either way, the cable is wrong or faulty (also common) if neither software works with it.

Actions #3

Updated by Jim Unroe 4 months ago

Unfortunately what you are using is not a Baofeng Tech PC04 programming cable. According to the debug.log file that you submitted, the programming cable that you are using was manufactured with a Prolific type PL2303GC chip. Baofeng Tech (the radio dealer in the USA) only sells FTDI chip based programming cables.

I would suspect that either that programming cable is wired for a different mobile radio and/or the driver that was automatically installed by Windows is incompatible with the chip in your programming cable (a common problem with Prolific type chips used in the MS Windows environment).

For the latter problem you can download, install and manually select the older Prolific v3.2.0.0 device driver to get your programming cable working. A link to the driver and instructions for manually selecting it are available from the Miklor radio information website's Drivers and USB Cables page.

Another common problem on these mobile radios, which I don't think is the issue here, is that speaker/headphone jack and data jack are not very far apart on the back of the radio. This makes it very easy for someone to accidentally plug the programming cable into the wrong port.

Actions #4

Updated by Hank Blackwood 4 months ago

Thanks Jim. 

I’ll try and order a 3rd cable from the BTech store on Amazon. The 1st 2 came in BTech packaging from the BTech store on Amazon. 

Hank

On Mar 2, 2025, at 9:50 PM, Jim Unroe redmine@chirpmyradio.com wrote:



Actions #5

Updated by Hank Blackwood 4 months ago

I bought yet another Btech cable - it works with the radio using CHIRP.

The other 2 cables show Prolific chips - they were purchased thru the BTECH store on Amazon as PC04 cables in BTECH packaging indicating FTDI chipsets.  Go figure?!

Hank
K4HYJ
ARRL Section Manager Georgia

----- Original Message -----
From: Jim Unroe (redmine@chirpmyradio.com)
Date: 03/02/25 21:50
To: hbjr@optilink.us
Subject: [CHIRP - Bug #11835] Bad ack from radio using PC04 cable

Actions #6

Updated by Dan Smith 4 months ago

  • Status changed from New to Not a bug

You're not the first one Hank!

I'll close this as not a bug, thanks for following up.

Actions

Also available in: Atom PDF