Project

General

Profile

Actions

Bug #6725

closed

UV-5XP

Added by Wayne Greenleaf over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
04/18/2019
Due date:
% Done:

100%

Estimated time:
Chirp Version:
daily
Model affected:
uv-5xp
Platform:
All
Debug Log:
I read the instructions above:

Description

HI
for the uv-5xp 8 watt radio, chirp does not seem to support the 3 power level settings only low and high. when I set to low in chirp on the radio will be medium. is there something I can do to fix this?
thanks


Files

Baofeng_UV-5R_20190418.img (6.5 KB) Baofeng_UV-5R_20190418.img Wayne Greenleaf, 04/18/2019 05:26 PM
radio1.jpg (3.08 MB) radio1.jpg Wayne Greenleaf, 04/19/2019 01:58 PM
radio2.jpg (3.03 MB) radio2.jpg Wayne Greenleaf, 04/19/2019 01:58 PM
radio3.jpg (3.02 MB) radio3.jpg Wayne Greenleaf, 04/19/2019 01:58 PM
2020-06-30 UV-5XP test image, only 3 channels - low, med, high.img (6.5 KB) 2020-06-30 UV-5XP test image, only 3 channels - low, med, high.img Baofeng UV-5XP test image with low, mid and high power settings Ford Prefect, 06/30/2020 06:12 PM
CHIRP bug 6725 2020-07-01 debug.log (35.2 KB) CHIRP bug 6725 2020-07-01 debug.log Ford Prefect, 07/01/2020 07:23 PM
2020-07-01 UV-5XP test image, chans 1-3 (H,M,L).img (6.5 KB) 2020-07-01 UV-5XP test image, chans 1-3 (H,M,L).img fresh UV-5XP image file w/ only chans 1-3 programmed (High, Mid & Low Power, respectively) Ford Prefect, 07/01/2020 07:28 PM
uv5r_test.py (64.8 KB) uv5r_test.py Driver module to test support for UV-5XP Jim Unroe, 07/02/2020 06:04 AM
CHIRP bug 6725 2020-07-02 debug 1.log (35.9 KB) CHIRP bug 6725 2020-07-02 debug 1.log Ford Prefect, 07/02/2020 10:23 AM
CHIRP bug 6725 2020-07-02 debug 2.log (41.9 KB) CHIRP bug 6725 2020-07-02 debug 2.log Ford Prefect, 07/02/2020 10:23 AM
CHIRP bug 6725 2020-07-02 screenshot of error message.png (93.6 KB) CHIRP bug 6725 2020-07-02 screenshot of error message.png Ford Prefect, 07/02/2020 10:23 AM
uv5r_test2.py (62.8 KB) uv5r_test2.py select Vendor: Baofeng / Model: BF-F8HP Jim Unroe, 07/02/2020 11:39 AM
2020-07-02-01 UV-5XP test image, chans 1-3 and 11-13 (H,M,L).img (6.5 KB) 2020-07-02-01 UV-5XP test image, chans 1-3 and 11-13 (H,M,L).img using test driver module and UV-5XP selection in CHIRP Ford Prefect, 07/02/2020 02:58 PM
CHIRP bug 6725 2020-07-02 debug 3.log (39.7 KB) CHIRP bug 6725 2020-07-02 debug 3.log logs using uv5r_test2.py driver module and BT-F8HP model selection Ford Prefect, 07/02/2020 03:30 PM
uv5r_test3.py (63.3 KB) uv5r_test3.py Jim Unroe, 07/02/2020 05:08 PM
uv5r_test4.py (63.2 KB) uv5r_test4.py Jim Unroe, 07/02/2020 07:26 PM
CHIRP bug 6725 2020-07-03-01 debug.log (51.8 KB) CHIRP bug 6725 2020-07-03-01 debug.log Ford Prefect, 07/03/2020 09:00 AM
CHIRP bug 6725 2020-07-03-01 UV-5XP test image - imported from radio with all populated chans set at low power.img (6.5 KB) CHIRP bug 6725 2020-07-03-01 UV-5XP test image - imported from radio with all populated chans set at low power.img Ford Prefect, 07/03/2020 09:00 AM
uv5r_test5.py (62.9 KB) uv5r_test5.py Jim Unroe, 07/08/2020 11:19 AM
2020-07-09-01 MR A Channel screen shot.png (11 KB) 2020-07-09-01 MR A Channel screen shot.png Ford Prefect, 07/09/2020 09:54 AM
2020-07-09-01 list of radio models - would alphabetical sorting be possible.png (7.35 KB) 2020-07-09-01 list of radio models - would alphabetical sorting be possible.png Ford Prefect, 07/09/2020 09:54 AM
Actions #1

Updated by Jim Unroe over 5 years ago

  • Status changed from New to Feedback

Attach a downloaded image file.

Jim KC9HI

Actions #2

Updated by Wayne Greenleaf over 5 years ago

hi attached image file

Actions #3

Updated by Jim Unroe over 5 years ago

Wayne,

Unfortunately the firmware version that your radio reports to CHIRP indicated it is a radio with 2 power levels. Would you verify that the TXP menu gives you 3 choices?

Thanks,
Jim KC9HI

Updated by Wayne Greenleaf over 5 years ago

Hi
yes 3 power level settings see attached thanks

Actions #5

Updated by Ford Prefect over 4 years ago

I'm having the same problem. I have a radio labelled UV-5XP. When I turn it on holding the 3 key, it says version BFB298. Menu item #2 for TXP includes a MID setting (5W) in addition to the LOW (1W) and HIGH (8W) settings. However, CHIRP only displays the LOW and HIGH options. If I set my channels to LOW, the radio actually stores the setting as MID. This causes a significant hardship because the only way to then change the power level in the saved memory channel would be to delete the channel, and then manually (using the radio interface itself) configure the correct power level of LOW (along with the frequency, tone settings, etc.) in the VFO and resave the channel. This means that the channel names (which are only configurable via software) are lost. So right now a user has to make a choice to either have channel names but always be forced to transmit at least 5W and waste their battery, or be able to transmit at the lowest power (highly desirable for obvious reasons) but not be able to have named memory channels. I hope that this issue can be treated as a high priority and would be willing to assist as far as possible to see that it happens.

Actions #6

Updated by Ford Prefect over 4 years ago

Just to clarify, I'm aware it is possible to manually hit the # button to change the power setting on this radio, but this is still an issue as users (whether sophisticated or otherwise, e.g. family members using the radios in an emergency) might not be able to remember to change power levels every time.

Actions #7

Updated by Ford Prefect over 4 years ago

One further update that might aid troubleshooting: if I go into CHIRP Settings tab > Other Settings, the "Firmware Message 1" says "HN5RV01" and "Firmware Message 2" says "1". Sorry for the multiple back-to-back posts.

Actions #8

Updated by Ford Prefect over 4 years ago

Oh and one more thing - this issue also affects the official Baofeng software. Based on Jim's above comment, it sounds like this might be due to the radio firmware misreporting its own capabilities. I'm wondering if there is a possibility to work around this problem in the programming software.

Actions #9

Updated by Jim Unroe over 4 years ago

  • Status changed from Feedback to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-legacy
  • Platform changed from Windows to All

Would either of you attach a CHIRP Radio Images (*.img) file with 3 channels programmed, the only difference between them being the TX power level (in other words one set to LOW, one set to MID and the last one set to HIGH). Thanks.

Jim KC9HI

Actions #10

Updated by Ford Prefect over 4 years ago

I manually programmed three channels into the radio, each channel on 146.520. Channel 0 is low, 1 is mid, and 2 is high.

However, CHIRP shows channel 0 empty, with 146.520 showing for channels 1, 2 and 3, at respective power settings of low, low and high. So there's something off with the channel numbering as well. I've uploaded the image file as you requested.

Actions #11

Updated by Jim Unroe over 4 years ago

Ford Prefect wrote:

I manually programmed three channels into the radio, each channel on 146.520. Channel 0 is low, 1 is mid, and 2 is high.

However, CHIRP shows channel 0 empty, with 146.520 showing for channels 1, 2 and 3, at respective power settings of low, low and high. So there's something off with the channel numbering as well. I've uploaded the image file as you requested.

Thanks. I will take a look at it and see what I can figure out.

Jim KC9HI

Actions #12

Updated by Jim Unroe over 4 years ago

Ford,

Unfortunately there is no difference between channels 0 and 1.

Jim KC9HI

Actions #13

Updated by Wayne Greenleaf over 4 years ago

nice to see it's being looked at again. I was just set to have to change to low power every time i turn on the radio...

Actions #14

Updated by Jim Unroe over 4 years ago

Which model are you choosing to download from the radio? Also, would it be possible for you to attach a clean debug.log file (close CHIRP, open CHIRP, download from radio, close CHIRP)?

Instruction for how to locate the debug.log file can be found "here.":https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues

Jim KC9HI

Actions #15

Updated by Ford Prefect over 4 years ago

Jim, log file attached as requested.

Actions #16

Updated by Ford Prefect over 4 years ago

By the way, in this case the radio programming was slightly different than mentioned in my earlier example. The log file attached to my previous comment (and the fresh image file of the radio attached to this comment) have channels 1-3 programmed. In the radio itself, 1 is high, 2 is mid and 3 is low.

Actions #17

Updated by Jim Unroe over 4 years ago

Ford Prefect wrote:

By the way, in this case the radio programming was slightly different than mentioned in my earlier example. The log file attached to my previous comment (and the fresh image file of the radio attached to this comment) have channels 1-3 programmed. In the radio itself, 1 is high, 2 is mid and 3 is low.

This most recent "image" does indeed show all 3 power levels. Thanks.

Jim KC9HI

Actions #18

Updated by Jim Unroe over 4 years ago

I threw this together real quick. I need you to test it to see if it works the way I think it should. To try it out, do the following.

1.0 download test driver module
1.1 click the link for "uv5r_test.py" and wait for the next page to load
1.2 click the "download" link
1.3 save the file to a convenient location
2 load CHIRP
3 click "Help" in the menu bar
4 enable "Enable Developer Functions" 
5 click "File in the menu bar
6 click "Load Module" 
7 locate and load the custom driver module saved in step 1

The CHIRP window background will now be red to indicate that it has been temporarily modified. Download from your radio using the Model: UV-5XP selection. See if the 3 channels show HIGH, MID and LOW settings. Create additional channels with HIGH, MID and LOW settings. Save to an "image" file and load back into CHIRP to see that the settings remain the same.

Thanks,
Jim KC9HI

Updated by Ford Prefect over 4 years ago

Jim,

Attached please find two additional log files, each containing comments at the beginning of each file detailing the steps taken while that log file was being created

The first log file provides additional context that I thought you might find helpful in troubleshooting.

The second log file is the one in which the steps you requested in your previous comment were actually performed.

A screenshot of an error message received during the above testing is also attached.

Actions #20

Updated by Jim Unroe over 4 years ago

Ford,

Thanks for the testing. Please attach the downloaded "image" file so I have something here I can test with.

Jim KC9HI

Actions #21

Updated by Jim Unroe over 4 years ago

Ford,

Thanks for the testing. Please attach the downloaded "image" file so I have something here I can test with.

Also give this "uv5r_test2.py" driver module a test and report back. It allows the BF-F8HP model selection to recognize the firmware version in your radio.

Jim KC9HI

Actions #22

Updated by Ford Prefect over 4 years ago

See attached for the .img created in the earlier step. I'll try the uv5r_test2.py driver module here in a moment and then report back.

Actions #23

Updated by Ford Prefect over 4 years ago

Jim, I just selected the BT-F8HP model selection after loading the "uv5r_test2.py" driver module. CHIRP's upload and download functions now both appear to preserve the "mid" power-level settings when interfacing with my UV-5XP. Log attached.

Within CHIRP, I then copied & pasted a list of channels (all low power) taking up nearly the entire memory bank from a previously-saved configuration into a new tab that had been set up by downloading from the UV-5XP using the BF-F8HP model selection. I proceeded to then upload the entire set to the radio. The radio now shows all of those channels at low power, as desired, and appears on first glance to be functioning normally.

Actions #24

Updated by Jim Unroe over 4 years ago

Ford Prefect wrote:

Jim, I just selected the BT-F8HP model selection after loading the "uv5r_test2.py" driver module. CHIRP's upload and download functions now both appear to preserve the "mid" power-level settings when interfacing with my UV-5XP. Log attached.

Within CHIRP, I then copied & pasted a list of channels (all low power) taking up nearly the entire memory bank from a previously-saved configuration into a new tab that had been set up by downloading from the UV-5XP using the BF-F8HP model selection. I proceeded to then upload the entire set to the radio. The radio now shows all of those channels at low power, as desired, and appears on first glance to be functioning normally.

OK. I must have missed something first attempt when I made the UV-5XP an alias of the BF-F8HP. It should have behaved just like the second one did. I'll see what I can figure out.

Thanks for your testing.

Jim KC9HI

Actions #25

Updated by Jim Unroe over 4 years ago

Ford,

Give "uv5r_test3.py" a try. Use UV-5XP for the Model.

Jim KC9HI

Actions #26

Updated by Ford Prefect over 4 years ago

I get this error over the red background: "Unable to load module: invalid syntax (uv5r_test3.py, line 1900)".

Actions #27

Updated by Jim Unroe over 4 years ago

Ford Prefect wrote:

I get this error over the red background: "Unable to load module: invalid syntax (uv5r_test3.py, line 1900)".

Yeah. My bad. It didn't like the "-" and I sent it without testing it. :-(

See what this does and include the downloaded image.

Jim KC9HI

Actions #29

Updated by Jim Unroe over 4 years ago

Ford Prefect wrote:

Jim, please see attached log and image.

Ford, Did I understand you to say that the earlier test using the BF-F8HP selection worked?

Jim

Actions #30

Updated by Ford Prefect over 4 years ago

Using the BT-F8HP model selection with the "uv5r_test2.py" driver module, transferring data in both directions preserved all three possible power selections).

Using the UV-5XP mode l selection with the "uv5r_test4.py" driver module, downloading low-power channels from the radio resulted in the CHIRP application displaying those channels as high-power. But when those same channels were uploaded back to the radio, they were still correctly set at low power.

Actions #31

Updated by Jim Unroe over 4 years ago

Ford Prefect wrote:

Using the BT-F8HP model selection with the "uv5r_test2.py" driver module, transferring data in both directions preserved all three possible power selections).

Using the UV-5XP mode l selection with the "uv5r_test4.py" driver module, downloading low-power channels from the radio resulted in the CHIRP application displaying those channels as high-power. But when those same channels were uploaded back to the radio, they were still correctly set at low power.

So that is NO. Thanks. I'll have to stare at it some more. ;-)

Actions #32

Updated by Jim Unroe over 4 years ago

Ford,

I think I have finally figured out what was going on. Please give this test driver module a try.

Thanks,
Jim KC9HI

Updated by Ford Prefect over 4 years ago

Looks like it's fixed. I very much appreciate your efforts here. Curious when this might appear in an official update.

A couple of additional quick questions. If you prefer, I can open a separate thread for these.

  1. When I either download an image directly back from a radio, or when I load a saved image file, in which MR A and B Channel under Work Mode Settings had been configured to channel zero, CHIRP shows the setting as blank/unconfigured (see attached screenshot). See attached screenshot. However, if any non-zero channel number is configured, the channel number is correctly displayed. This does not appear to affect the actual preservation of channel zero as the setting, so I'd say it's probably a low-priority issue but one at least worth noting as it might confuse other users as it has me.

  2. When selecting a radio model, CHIRP displays the list of available models in an apparently-random order (see attached screenshot). There are several non-UV-model entries separating other UV-model entries, which might result in some users, who are expecting an alphanumerical sorting, to erroneously select the wrong model. Wondering if this is something that could be addressed at some point.

Thanks again and let me know if I can assist further.

Actions #34

Updated by Jim Unroe over 4 years ago

  • % Done changed from 0 to 90

Ford Prefect wrote:

Looks like it's fixed. I very much appreciate your efforts here. Curious when this might appear in an official update.

Thanks for testing. I will try to get a patch submitted today. Once that happens, we just have to patiently wait for it to be accepted. Once that happens the support will be in the following CHIRP daily build.

A couple of additional quick questions. If you prefer, I can open a separate thread for these.

  1. When I either download an image directly back from a radio, or when I load a saved image file, in which MR A and B Channel under Work Mode Settings had been configured to channel zero, CHIRP shows the setting as blank/unconfigured (see attached screenshot). See attached screenshot. However, if any non-zero channel number is configured, the channel number is correctly displayed. This does not appear to affect the actual preservation of channel zero as the setting, so I'd say it's probably a low-priority issue but one at least worth noting as it might confuse other users as it has me.

I've only noticed this when using Linux. I always assumed that it was an issue with one of CHIRP's dependencies and beyond CHIRP's control. I just learned to get used to it. If it bothers you, then open a separate issue.

  1. When selecting a radio model, CHIRP displays the list of available models in an apparently-random order (see attached screenshot). There are several non-UV-model entries separating other UV-model entries, which might result in some users, who are expecting an alphanumerical sorting, to erroneously select the wrong model. Wondering if this is something that could be addressed at some point.

This is one of the reasons that I try not to add any additional models. Normally I would have told you to just use the BF-F8P selection. The only reason I wend ahead and added a selection for UV-5XP was because I could see a lot of issues opened from UV-5XP owners trying to use UV-5X. I just learned to get used it. If bothers you, open a separate issue.

Thanks again and let me know if I can assist further.

Thank you. I couldn't have figured it out without your help.

Jim KC9HI

Actions #35

Updated by Jim Unroe over 4 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

Patch submitted. Support will be in the next CHIRP daily build following acceptance.

Jim KC9HI

Actions #36

Updated by Anonymous over 4 years ago

  • Status changed from Resolved to Closed

Applied in changeset commit:bb504662f35a.

Actions

Also available in: Atom PDF