Bug #10493
openUV5R Settings Blank
Added by Alan . over 1 year ago. Updated over 1 year ago.
0%
Description
Memories are loading ok but settings menu is blank.
I have 2 cables and USB connections seem fine on Com8 (driver provided by "wch.cn" so presume cloned cable).
Manufacturer's software works ok.
Please see debug.
Thanks
Alan
Files
| Baofeng_UV-5R_20230401.img (6.52 KB) Baofeng_UV-5R_20230401.img | Alan Gurbutt, 04/01/2023 01:22 PM | ||
| Baofeng_UV-5R_20230401(settings).img (6.52 KB) Baofeng_UV-5R_20230401(settings).img | Jim Unroe, 04/01/2023 04:19 PM | ||
| chirp_debug-vhf0e6ig.txt (52.8 KB) chirp_debug-vhf0e6ig.txt | Alan ., 04/01/2023 11:11 PM | ||
| uv5r.jpg (154 KB) uv5r.jpg | Alan ., 04/01/2023 11:11 PM | ||
| error.png (99.6 KB) error.png | James Flanighan, 06/23/2023 08:40 PM | ||
| Fix.PNG (380 KB) Fix.PNG | James Flanighan, 06/23/2023 08:40 PM | ||
| Baofeng_UV-5R_20230627_PTT_Issue.img (6.52 KB) Baofeng_UV-5R_20230627_PTT_Issue.img | James Flanighan, 06/27/2023 07:18 PM | ||
| Baofeng_UV-5R_20230627_PTT_2_Issue.img (6.52 KB) Baofeng_UV-5R_20230627_PTT_2_Issue.img | James Flanighan, 06/27/2023 08:07 PM | ||
| Baofeng_UV-5R_20230627_PTT_2_Issue.img (6.52 KB) Baofeng_UV-5R_20230627_PTT_2_Issue.img | James Flanighan, 06/28/2023 06:45 AM |
Updated by Alan . over 1 year ago
I've researched the chip in the USB cable branded Baofeng and it's CH340. I've updated to latest drivers from manufactures site to no avail, the fault persists.
I've tried the same cables in my Kenwood TH-7F and there's no menu showing in Chirp. Also communication errors.
Should I try another cable with a genuine FTDI?
Updated by Jim Unroe over 1 year ago
Someone or something has set the radio's band limits to invalid values. Make a fresh download from the radio and attach it to this issue, I will set them to the "factory" default values.
Jim KC9HI
Updated by Alan Gurbutt over 1 year ago
Jim Unroe wrote in #note-2:
Someone or something has set the radio's band limits to invalid values. Make a fresh download from the radio and attach it to this issue, I will set them to the "factory" default values.
Jim KC9HI
Many thanks Jim.
I purchased the radio from overseas so not sure about it's credentials.
I've attached the download.
Alan G0NQA
Updated by Jim Unroe over 1 year ago
Alan Gurbutt wrote in #note-3:
Jim Unroe wrote in #note-2:
Someone or something has set the radio's band limits to invalid values. Make a fresh download from the radio and attach it to this issue, I will set them to the "factory" default values.
Jim KC9HI
Many thanks Jim.
I purchased the radio from overseas so not sure about it's credentials.
I've attached the download.
Alan G0NQA
Alan,
This radio is in bad shape. Other than the Welcome message, this radio has no data in the Aux Memory area. I don't know if it just missed a step at the factory or it has bad memory, etc.
So I'm not even sure if it is possible to fix your radio. It will depend on if your radio will accept the changes that I made to this image and remember them.
What I have done is to perform the absolute minimum editing necessary to the "image" to get the Setting tabs to display in CHIRP (band limits and service settings). If you load it into CHIRP, you will now see that the Settings tabs are displayed. What you will have to do to test your radio's Aux Memory area would be to upload this image into it. Then download the updated radio back into CHIRP. If the Settings tabs are still showing up, the radio retained the data sent to it. If the Settings tabs don't display, then the Aux Memory area of your radio does not accept and/or retain changes.
Test you radio to see if it will scan the programmed channels and receive stations without having to press and hold the orange [MINI] button. When the Aux Memory area does not contain valid data the side affects are that channels can't be scanned and/or the squelch will never open when a signal is present. If these side affects are present, then we might try uploading a "factory" image from another similar radio to fix it, but I am thinking a better option at this point would be to see if it can be returned or replaced.
Jim KC9HI
Updated by Alan . over 1 year ago
- File chirp_debug-vhf0e6ig.txt chirp_debug-vhf0e6ig.txt added
- File uv5r.jpg uv5r.jpg added
Jim Unroe wrote in #note-4:
Alan Gurbutt wrote in #note-3:
Jim Unroe wrote in #note-2:
Someone or something has set the radio's band limits to invalid values. Make a fresh download from the radio and attach it to this issue, I will set them to the "factory" default values.
Jim KC9HI
Many thanks Jim.
I purchased the radio from overseas so not sure about it's credentials.
I've attached the download.
Alan G0NQAAlan,
This radio is in bad shape. Other than the Welcome message, this radio has no data in the Aux Memory area. I don't know if it just missed a step at the factory or it has bad memory, etc.
So I'm not even sure if it is possible to fix your radio. It will depend on if your radio will accept the changes that I made to this image and remember them.
What I have done is to perform the absolute minimum editing necessary to the "image" to get the Setting tabs to display in CHIRP (band limits and service settings). If you load it into CHIRP, you will now see that the Settings tabs are displayed. What you will have to do to test your radio's Aux Memory area would be to upload this image into it. Then download the updated radio back into CHIRP. If the Settings tabs are still showing up, the radio retained the data sent to it. If the Settings tabs don't display, then the Aux Memory area of your radio does not accept and/or retain changes.
Test you radio to see if it will scan the programmed channels and receive stations without having to press and hold the orange [MINI] button. When the Aux Memory area does not contain valid data the side affects are that channels can't be scanned and/or the squelch will never open when a signal is present. If these side affects are present, then we might try uploading a "factory" image from another similar radio to fix it, but I am thinking a better option at this point would be to see if it can be returned or replaced.
Jim KC9HI
Thanks for your work Jim.
No go i'm afraid- please see attached
I'll ask for a refund on the radio
Alan G0NQA
Updated by Bogdan N. over 1 year ago
@Alan, you may want to take a look at this too, might be the same issue: https://chirp.danplanet.com/issues/10505
Updated by James Flanighan over 1 year ago
Alan, I created this account to make this comment. I had the exact same error as you received. On my brand new UV-5R, I downloaded and saved the default configuration file. I then tried disabling PTT (working on my HAM license) and I think I may have changed another setting out of bounds while clicking around.
When I tried uploading the config file I got the error in image 1 and when I downloaded the configuration file again from the UV-5R the setting tab was blank.
What worked for me (and I don't know if it just papers over the issues Jim Unroe said about the Aux memory) was making a backup of my original config file and then editing the values after model number to zeros (see the attached image) using hex editor (I used HxD in windows).
The file uploaded successfully and I had my settings back.
Updated by James Flanighan over 1 year ago
EDIT
I just encountered the error again when trying to program some channels. I downloaded from radio with no issues, edited the channels and then received the same error as above when I uploaded to the radio. I resolved this by saving the edited img, opening it in a hex editor, editing the same location in the file as above then reuploading with no issues.
It seems that there is a bug in CHIRP where somewhere between downloading from radio and uploading the IMG, the firmware version in the image is corrupted to all FFs instead of OOs. Manually fixing it resolve the issue Alan and I are experiencing.
Updated by Jim Unroe over 1 year ago
James Flanighan wrote in #note-8:
EDIT
I just encountered the error again when trying to program some channels. I downloaded from radio with no issues, edited the channels and then received the same error as above when I uploaded to the radio. I resolved this by saving the edited img, opening it in a hex editor, editing the same location in the file as above then reuploading with no issues.
It seems that there is a bug in CHIRP where somewhere between downloading from radio and uploading the IMG, the firmware version in the image is corrupted to all FFs instead of OOs. Manually fixing it resolve the issue Alan and I are experiencing.
Again... It is when uploading the issue occurs. The radio changes the Aux memory to 0xFF. You just don't find out until after your next download. To prevent this from happening you currently must use the test driver module. It tests for and recognizes which radios misbehave and skips uploading the Aux memory area when it does.
Jim KC9HI
Updated by James Flanighan over 1 year ago
Thank you Jim. I have had to edit the hex file to successfully upload to the radio and over and above that disabling PTT doesn't work despite confirming the appropriate bits are 00 in the image downloaded from the radio. I fear that you are right the AUX memory on my radio is shot.
Updated by Jim Unroe over 1 year ago
James Flanighan wrote in #note-10:
Thank you Jim. I have had to edit the hex file to successfully upload to the radio and over and above that disabling PTT doesn't work despite confirming the appropriate bits are 00 in the image downloaded from the radio. I fear that you are right the AUX memory on my radio is shot.
No. It's not shot. The radio just doesn't want to cooperate. Luckily I was able to finally locate one with the same problem so I am able to better diagnose the issue. I think I am close to wrestling it to the ground.
Jim
Updated by Jim Unroe over 1 year ago
James Flanighan wrote in #note-10:
Thank you Jim. I have had to edit the hex file to successfully upload to the radio and over and above that disabling PTT doesn't work despite confirming the appropriate bits are 00 in the image downloaded from the radio. I fear that you are right the AUX memory on my radio is shot.
I came up with a whole new method for a workaround for this issue. It has been attached to #10505. It would be nice if you would test it.
Jim KC9HI
Updated by James Flanighan over 1 year ago
Jim Unroe wrote in #note-12:
James Flanighan wrote in #note-10:
Thank you Jim. I have had to edit the hex file to successfully upload to the radio and over and above that disabling PTT doesn't work despite confirming the appropriate bits are 00 in the image downloaded from the radio. I fear that you are right the AUX memory on my radio is shot.
I came up with a whole new method for a workaround for this issue. It has been attached to #10505. It would be nice if you would test it.
Jim KC9HI
Wow - that was fast. Im away from home right now on business and will be back on Friday. I will test and get back to you then. Thanks again Jim.
Updated by James Flanighan over 1 year ago
Unexpectedly back home early.
I'll also update the other issue:
- Able to download via CHIRP, change settings and memories, and then upload the firmware to radio without getting the mismatch error that I was getting earlier.
- I had [previously only had experienced the missing settings issue once (had to edit the img file to fix) but this has not occurred since
- Unfortunately, no matter what I do my PTT keeps working. I have unchecked the VHF Tx Enabled and UHF Tx Enabled flags in CHIRP. Uploaded the image to radio. Downloaded from radio and confirmed the flags are unchecked but PTT still works
The PTT is so far the only thing that seems to not work in this fix.
Thanks again Jim.
Updated by Jim Unroe over 1 year ago
James Flanighan wrote in #note-14:
The PTT is so far the only thing that seems to not work in this fix.
Ok. That's likely an issue in a different section area of memory. Would you attach an image from that final state?
Jim
Updated by James Flanighan over 1 year ago
I have attached an image downloaded fresh off the radio. PTT still works despite the appropriate boxes being unchecked.
I had previously programmed channels in memories with the Duplex setting turned to "off" which successfully disabled PTT.
Thanks Jim.
Updated by Jim Unroe over 1 year ago
James Flanighan wrote in #note-16:
I have attached an image downloaded fresh off the radio. PTT still works despite the appropriate boxes being unchecked.
I had previously programmed channels in memories with the Duplex setting turned to "off" which successfully disabled PTT.
Thanks Jim.
This isn't a good file to begin with. The Aux memory is bad. It was either bad to begin with or you didn't have my test driver module running when you uploaded it.
Jim
Updated by James Flanighan over 1 year ago
Jim Unroe wrote in #note-17:
James Flanighan wrote in #note-16:
I have attached an image downloaded fresh off the radio. PTT still works despite the appropriate boxes being unchecked.
I had previously programmed channels in memories with the Duplex setting turned to "off" which successfully disabled PTT.
Thanks Jim.
This isn't a good file to begin with. The Aux memory is bad. It was either bad to begin with or you didn't have my test driver module running when you uploaded it.
Jim
PTT seems to be disabled now!
I could have sworn I had the test driver module loaded (hence why I wasn't getting any firmware mismatch errors).
I just tried it again by:
- Reloading the test driver module
- Uploading the intial saved image from the radio (saved the first time I used CHIRP)
- Downloading the saved image - disabling PTT and then re-uploading back to radio.
For reference here is the downloaded image with PTT disabled.
Jim Unroe wrote in #note-17:
James Flanighan wrote in #note-16:
I have attached an image downloaded fresh off the radio. PTT still works despite the appropriate boxes being unchecked.
I had previously programmed channels in memories with the Duplex setting turned to "off" which successfully disabled PTT.
Thanks Jim.
This isn't a good file to begin with. The Aux memory is bad. It was either bad to begin with or you didn't have my test driver module running when you uploaded it.
Jim
Updated by James Flanighan over 1 year ago
PTT seems to be disabled now!
I could have sworn I had the test driver module loaded (hence why I wasn't getting any firmware mismatch errors).
I just tried it again by:
Reloading the test driver module
Uploading the intial saved image from the radio (saved the first time I used CHIRP)
Downloading the saved image - disabling PTT and then re-uploading back to radio.
For reference here is the downloaded image with PTT disabled.
Updated by Jim Unroe over 1 year ago
James Flanighan wrote in #note-19:
PTT seems to be disabled now!
I could have sworn I had the test driver module loaded (hence why I wasn't getting any firmware mismatch errors).
I just tried it again by:
Reloading the test driver module
Uploading the intial saved image from the radio (saved the first time I used CHIRP)
Downloading the saved image - disabling PTT and then re-uploading back to radio.
For reference here is the downloaded image with PTT disabled.
And this is a properly formatted image. It should continue to work for you as long as you use the test driver module for uploading. Make a copy and keep it as a backup.
Jim KC9HI
Updated by Jim Unroe over 1 year ago
The latest CHIRP release (20230703) has a fix that should prevent the issue where the radio blanks out its Aux block of memory. This makes it no longer necessary to upload using the method described in issue #10505.
Jim KC9HI