New Model #4445

When using the BF-F8HP driver for Baofeng GT-3TP Mk III, I get 'Incorrect 'Model' selected'

Added by Mikael Eriksson 8 months ago. Updated 6 months ago.

Status:In Progress Start date:01/23/2017
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

0%

Category:-
Target version:0.5.0
Chirp Version:daily Equipment Loan Offered:No

Description

I'm running version daily-20170115.

When using the BF-F8HP driver for Baofeng GT-3TP Mk III, I get 'Incorrect 'Model' selected'
The radio has three power levels.
I managed to read the image from the radio by selecting UV-5R, but then I will only get two power levels.

I looked into the image and it looks like Baofeng re-uses the same firmware revision ('HN5RV011\xff\xff\xff\xff\xff\xff') that they alredy have used for the UV-5R before.

I'm attaching the Image from the radio and the debug.log

debug.log (20.6 kB) Mikael Eriksson, 01/23/2017 12:26 pm

Baofeng_GT-3TP_MkIII.img (6.3 kB) Mikael Eriksson, 01/23/2017 12:26 pm

uv5r(2).py (57.9 kB) Steff *, 01/31/2017 03:43 am

uv5r_test_fix_for_HN5RV_firmware.py (61.7 kB) Jim Unroe, 03/26/2017 06:43 pm

uv5r_test_fix_2_for_HN5RV_firmware.py (61.7 kB) Jim Unroe, 03/28/2017 02:06 pm

Associated revisions

Revision 2877:0714032989d2
Added by Jim Unroe 6 months ago

[UV-5R] "Incorrect 'Model' selected." error

When Baofeng started shipping tri-power radios back in 2014, the firmware
version format could be used to identify if the detected radio had 2 power
levels (HIGH/LOW) or 3 power levels (HIGH/MID/LOW). CHIRP would then use this
firmware version to not only determine if the user had selected the correct
radio model, but also to present the only settings that were available on the
selected model.

Recently Baofeng radio models with 3 power levels have been shipping with with
the HN5RV001 firmware version. This same firmware version, as it has for the
last 2 years, continues to ship in radio models that have only 2 power levels.
This firmware version defeats CHIRP's ability to differentiate on its own
between these two model types.

This patch addresses the problem in 2 ways.

1. for radios with the HN5RV001 firmware version, CHIRP will assume that the
user has selected the correct radio model. The selected model is then appended
to the end of the image so CHIRP can identify the radio model when image is
loaded back into CHIRP at a later time.

2. the driver will now selectively uploads the image in ranges, thus bypassing
specific areas of memory that must not be overwritten by images from radios
with a different firmware version.

This patch also addresses, in a similar way, a related problem where the radio
does not report a firmware version at all to CHIRP.

releated to issue #4445 and many others

Revision 2879:2c4bb936f964
Added by Jim Unroe 5 months ago

[UV-5R] Fix pep8 Issue

This patch fixes a pep8 issue that I thought I has already fixed.

releated to issue #4445

History

Updated by Jim Unroe 8 months ago

Correct. This issue is known and has already been reported more than once.

Jim

Updated by Mikael Eriksson 8 months ago

Not sure if this is of any help, but I did an ugly quickfix to the yv5r.py and loaded is as a module.
I can confirm that the radio works in same way as the BF-F8HP. I can download an image from the radio, edit it and upload the image back to the radio.
Everything seems to work properly.

Updated by Jim Unroe 8 months ago

  • Status changed from New to Feedback

Mikael,

What was your "ugly quickfix? I did one the other day for someone by adding "N5RV" to the F8HP basetype. That will work when downloading from the radio and uploading a direct download back to the radio. But I am pretty sure that a saved image will be detected as a UV-5R image which is still a problem. If it is detected as a BF-F8HP image then it will cause issues for those UV-5R radios having the "HN5RV01" firmware for the last 2 years or so.

Jim

Updated by Mikael Eriksson 8 months ago

Jim,

I just removed "N5RV" from the BASETYPE_UV5R:

BASETYPE_UV5R = ["BFS", "BFB", "N5R-2", "N5R2", "BTS", "D5R2"] # removed "N5RV" 
and added it to the BASETYPE_F8HP:
BASETYPE_F8HP = ["BFP3V3 F", "N5R-3", "N5R3", "F5R3", "BFT", "N5RV"] # Added "N5RV" 

This way you can read a saved file, but it will, as you mentioned, break the backward compatibility with the UV-5R. (hence the ugliness)
(I also have an UV-5R with firmware "HN5RV011B297", so I'm very interested in having both of them working out of the box with Chirp)

I've looked at the source code and I haven't found a way to uniquely identify an saved image from an UV-5R and an GT-3TP from each other.

Updated by Jim Unroe 8 months ago

Mikael,

Yes. That should work perfectly for you. I'll keep thinking about a solution.

Jim

Updated by Steff * 8 months ago

Jim or Mikael, could you please upload the file?
i have the same problem GT-3TP BFP3-23
i am a newbie ...

Updated by Steff * 8 months ago

Thank you Jim.

it worked perfect and i got 3 power levels.....

i uploaded the file for other newbies like me....

Updated by Octavio Santos 7 months ago

Hi, im having the same problem with a GT-3TP with BFP3-23 firmware. Where do i put that file? thx.

Updated by Octavio Santos 7 months ago

What tool do you use to look into the .img file, so i can do the change, thx.
I'm a real newbie, forgive me. :)

Updated by Octavio Santos 7 months ago

According to chirp i have HN5RV01 firmware version.

Updated by Octavio Santos 7 months ago

Hi guys, as a suggestion, I was wondering if it's not easier to program the uv5r driver to 3 power levels and solve the issue for the GT-3TP (or 3 power level radios) with this firmware? Obviously this would solve the problem to the 3 power level radios, but it would add a problem to the uv5r. The thing is that the new created problem would be easier to fix as long as everyone knows that the low power level for the uv5r wouldn't work, so it wouldn't be considered by the user and thus not selected. The goal here is to make it possible to manage the radios entirely through chirp. What do you think?

Updated by Jim Unroe 6 months ago

The attached driver file is an attempt to solve the same HN5RV01 firmware version being used for both radios with 2 power levels (HIGH/LOW) and 3 power levels (HIGH/MID/LOW). Please test and provide feedback. Here is how to try it out.

1 download driver the file (click the link and click on "download" after the next page appears
2 load CHIRP
3 click Help
4 enable "Enable Developer Functions"
5 click File
6 click Load Module
7 locate and lose the driver file saved in step 1

Now try to download from your radio. Choose BF-F8HP for the model if your radio has 3 power levels, UV-5R if your radio has 2 power levels. If successful, try to upload back to your radio. Also save and load images to see if they are detected correctly.

Jim KC9HI

Updated by Jim Unroe 6 months ago

Update to support additional model with "blank" firmware version area.

Jim

Updated by Geoffroy Geoffroy 6 months ago

This is working for GT-3TP with firmware version BFP3-23

Updated by Geoffroy Geoffroy 6 months ago

This is working for GT-3TP with firmware version BFP3-23

Updated by David Marshall 6 months ago

Trying to follow this - Have a GT-3TP with firmware version showing as BFP3-25 when holding 3 at startup. I have not seen anything about this radio and this firmware version. I've tried the solution using Baofeng BF-F8HP but get "An error has occurred Radio did not respond". Running CHIRP daily-20170401 on MacOS 10.12.3.

Updated by Randall Elliott PE 6 months ago

Downloaded and fired up CHIRP daily-20170401.
Downloaded and loaded module "uv5r_test_fix_2_for_HN5RV_firmware.py"
Set radio type to BF-F8HP rather than trying a UV-5 variant.
"Download From Radio" worked just fine.
Opened my stock image stored back in 12Feb2017 with 121 channels used.
Attempted upload to radio came back with this:
"The upload was stopped because the firmware version of the image (N5R3409BFP3-25) does not match that of the radio (HN5RV011FB297 )."
What a whiner :-D
Cut and paste all 121 channels into downloaded image overwriting downloaded channels.
Attempted upload to radio worked that time.
NO whining this time :-D
Image from 12Feb2017 had Firmware Message 1: N5R3409, Firmware Message 2: BFP3-25, 6+Power-On Message 150319N.
Image downloaded tonight had Firmware Message 1: HN5RV01, Firmware Message 2: 1FB297, 6+Power-On Message 160328N.

Updated by Randall Elliott PE 6 months ago

By the way, The old image I was trying to upload is also a BF-F8HP image.

Updated by Randall Elliott PE 6 months ago

Downloading from my newly programmed UV-5RTP works sorta with UV-5R and UV-5X settings, but does not show tri-power options.
Downloading from my newly programmed UV-5RTP works right (so far) with BF-F8HP setting complete with tri-power options. I haven't been through all the settings to see if any didn't migrate, but I will be looking eventually.

Updated by Jim Unroe 6 months ago

Randall,

Your new radio does not report to CHIRP a firmware version that it can use to determine if it has 2 or 3 power levels. You have to do that by choosing UV-5R (2 power levels) or BF-F8HP (3 power levels).

Powering the radio on with the 3 key pressed is not the "real" firmware version and has not been for over 2 years. The real firmware version can only be determined by using CHIRP. The "real" firmware versions do not math so the upload is stopped as designed.

A patch has been submitted to add support for the radios with HN5RV01 firmware and the radios that don't report a firmware version at all.

Jim KC9HI

Also available in: Atom PDF