Bug #4569

Baofeng GT-5TP

Added by Pete Ed over 3 years ago. Updated 10 months ago.

Status:Closed Start date:02/28/2017
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:GT-5TP

Description

G'day Team ... Thank you for your excellent software.

Just some "Feedback" ...

I purchased two "Baofeng GT-5TP" radios last week, and they have different firmware to each other.

1st one has FW: N82301 ... this one will not respond to the latest build of CHIRP (20170217) ... I keep getting either: "incorrect radio" or "radio does not respond" (messages are from memory so they may be a little different to actual) ... this one (FW: N82301) will respond to software from "baofengtech.com" (BaoFeng UV-82HP VIP Programming Software) ... programmed successfully :-)

2nd one has FW: N82303 ... this one works fine with the latest build of CHIRP (20170217) and programed successfully , so, thank you again "CHIRP Team"!!!

It seems that the N82301 FW has an issue with CHIRP (20170217), as the radio is programmable via the "other" software.

Cheers ... Pete

CHIRP_debug_01-03-2017.log - Renamed for convienience. (23.1 kB) Pete Ed, 02/28/2017 11:46 pm

debug.log (22.8 kB) Julian Crisp, 03/27/2017 04:00 am

debug.log (32.2 kB) Julian Crisp, 03/27/2017 06:04 pm

Device Manager.JPG (85.3 kB) Julian Crisp, 03/29/2017 04:18 pm


Related issues

duplicated by New Model #4435: Baofeng GT-5TP Closed 01/21/2017
duplicated by New Model #4723: Baofeng GT-5TP Closed 04/12/2017

History

Updated by Jim Unroe over 3 years ago

  • Status changed from New to Feedback

CHIRP should detect the N82301 firmware version. It just looks for the "N82" part to recognize the radio. Please include the debug.log file.

Jim KC9HI

Updated by Pete Ed over 3 years ago

G'day Jim.

Thanks for your reply mate.

I have replicated the situation. First using the "UV-82HP" radio selection, as indicated that should be used at the Chirp website. Error was something like "Wrong Radio".

Next, I tried the "UV-5R" radio selection, and that failed also (I read somewhere that the UV-5R worked for some one). Error was something like "Radio did not respond".

Log file attached.

Cheers ... Pete

Updated by Jim Unroe over 3 years ago

Thanks for the debug.log file. CHIRP doesn't recognize your radio because it is not reporting a valid firmware version.

2017-03-01 18:26:57,140] chirp.drivers.uv5r - INFO: Radio Version is '\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff'

Is it an "official" UV-82HP purchased from Baofeng Tech or is it a variant purchased from someone else?

Jim KC9HI

Updated by Jim Unroe over 3 years ago

Never mind. Your radios are GT-5TP models that Baofeng Tech does not offer.

Jim

Updated by Pete Ed over 3 years ago

Thanks for your response Jim.

Is there any way of working around the "not reporting a valid firmware version" issue for this radio that I could do, maybe a config file that I can edit?

If not, not a problem, as I can use the "other" software - sadly, it is not as flexible as your "CHIRP" ;-)

Cheers ... Pete

Updated by Julian Crisp over 3 years ago

Afternoon lads. I have a Baofeng GT-5TP (firmware N82301) with an identical issue. Keeps telling me that the radio didn't respond.

Updated by Jim Unroe over 3 years ago

The solution for this issue is being addressed here

Jim KC9HI

Updated by Julian Crisp over 3 years ago

Didn't work for me.. "Radio did not respond" again

Updated by Jim Unroe over 3 years ago

Julian,

Do you have a working programming cable? Where is your debug.log file?

Jim KC9HI

Updated by Julian Crisp over 3 years ago

The drivers installed for the cable so I assume it works. It shows up as COM3 in device manager. Debug.log attached.

Updated by Jim Unroe over 3 years ago

You can't assume that if you are running Windows and a programming cable with a Prolific chip. Look in Device Manager. If it shows a Prolific chip on the Driver page, then the device driver version must be v3.3.2.105 or lower (v3.2.0.0 recommended) or it won't work.

Jim

Updated by Julian Crisp over 3 years ago

Its version 3.8.12.0. How do I down grade?

Updated by Julian Crisp over 3 years ago

Julian Crisp wrote:

Its version 3.8.12.0. Just down grading now

Updated by Julian Crisp over 3 years ago

Down graded to driver to 3.2.0.0, loaded the module that you linked above, selected the radio that you had listed in that post also. Still getting "Radio did not respond"

Updated by Jim Unroe over 3 years ago

I need the debug.log from the 3.2.0.0 driver. This sounds like a cable not fully connected to the radio issue.

Jim

Updated by Jim Unroe over 3 years ago

Julian,

Does the factory software work? If yes, let me know where it is available from.

Jim

Updated by Julian Crisp over 3 years ago

There was no factory software. Debug attached. Going to try a different cable in a hour or so. Will let you know if it works.

Updated by Julian Crisp over 3 years ago

Last one didn't work. Attached below

Updated by Jim Unroe over 3 years ago

Your radio does not respond. There is either a cable issue or your radio responds to a different "magic" code to initiate cloning. My guess is that it is a cabling issue. CHIRP can't solve that.

If it is because the radio responds to a different "magic" code, that magic code can only be determined from the factory software.

Do you have a GT-5TP like that of Ed (the person that opened this issue)? I just did some quick research, the GT-5TP is just a UV-82HP in different case. So it definitely responds to a different "magic". You both should be choosing UV-82HP (not BF-F8HP).

From the Supported Models list on the CHIRP home/wiki page:

  • UV-82HP/82DX/82HX (3 power levels)
    Also includes the GT-5TP

Jim

Updated by Pete Ed over 3 years ago

G'day Jim.

I was choosing the UV-82HP (not BF-F8HP) setting with my GT-5TP (FW: N82301). I did have success with the second GT-5TP that I purchased, as I previously reported, and it has firmware N82303, so it must be an issue with the N82301 firmware.

Sadly, my GT-5TP with FW: N82301 has stopped working so I will no longer be able to give feedback with that firmware.

Cheers ... Pete

Updated by Jim Unroe over 3 years ago

Pete,

Yes. I knew you were selecting the correct model. Based on the debug.log that he supplied, it was Julian that was selecting the wrong model. Sorry for the confusion.

Thanks for the feedback. After I receive a few more reports of success, I will try to get a patch submitted.

Jim

Updated by Julian Crisp over 3 years ago

Tried a different cable yesterday, same thing, "radio did not respond". Are you able to send me a simple (i'm new to this) step by step guide of how to do this. From Installing to it hopefully working. I will uninstall and delete all CHIRP files now and reinstall so I have a fresh place to start. I'm pretty new to this so the simpler the better. My radio is the Baofeng GT-5TP with firmware N82301 just to confirm. Cheers.

Updated by Jim Unroe over 3 years ago

Julian,

What kind of programming cable did you get. A generic cable or the better one based on an FTDI chip.

If it a generic cable with Prolific chip, you must downgrade the driver as described in this guide

Jim

Updated by Julian Crisp over 3 years ago

I have a generic cable. I'm on version 3.2.0.0. See screen shot attached.

Updated by Jim Unroe over 3 years ago

Julian,

The only other thing I can suggest right now would be to make sure the plug is fully inserted. On the GT-3 there is a ridge that runs around the socket well that can interfere and the plug sometimes needs trimmed to allow it to go in all the way. I don't know about the GT-5 radios. See Radio did not respond on the miklor website.

Updated by Pete Ed over 3 years ago

Hi Julian.

Have you tried to use the factory software that I mentioned in my first post? It worked OK for my GT-5TP that had the N82301 firmware.

Get the software from "baofengtech.com" in the download section. The software name is "BaoFeng UV-82HP VIP Programming Software". It is not as good as CHIRP, but it will at least let you know whether your radio's programming cable is working or not.

Cheers ... Pete

Updated by Jim Unroe 10 months ago

  • Status changed from Feedback to Resolved
  • Target version set to chirp-daily
  • Chirp Version changed from 0.4.0 to daily
  • Platform changed from Windows to All

related to #4445

Updated by Jim Unroe 10 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF

prevent spam