Bug #11024
closedBaofeng UV-5R 'nonetype' object has no attribute 'setvalue'
100%
Description
When trying to change my startup screen display settings in an existing radio programming file, I get an error message:
'nonetype' object has no attribute 'setvalue'
I am not trying to enter any characters other than regular capital letters.
Files
Updated by Jim Unroe over 1 year ago
You will have to attach your CHIRP Radio Images (*.img) file.
Updated by Geoff Beasley over 1 year ago
Thanks, the .img file is now attached.
Updated by Jim Unroe over 1 year ago
Geoff Beasley wrote in #note-2:
Thanks, the .img file is now attached.
This file loads and edit with no problem. The welcome message has already been changed.
I don't understand your issue.
Updated by Geoff Beasley over 1 year ago
I had a custom welcome message in the radio's .img file already. I downloaded the .img and tried to update it with a new welcome message along with some new channel/frequency memories, but it presents an error when I click to a new field. Attached is the error message I get when trying to change the welcome message.
Updated by Jim Unroe over 1 year ago
Geoff Beasley wrote in #note-4:
I had a custom welcome message in the radio's .img file already. I downloaded the .img and tried to update it with a new welcome message along with some new channel/frequency memories, but it presents an error when I click to a new field. Attached is the error message I get when trying to change the welcome message.
That has to be a different image because the image that you added to this issue works fine for me. Make a fresh download from your radio, save to to a CHIRP Radio Images (*.img) file and attach it here.
Updated by Geoff Beasley over 1 year ago
- File Baofeng_UV-5R_20231219.img Baofeng_UV-5R_20231219.img added
- File debug.log debug.log added
Thanks for your ongoing help. I have attached the new .img and debug.log files after having deleted the prior debug.log, starting CHIRP, downloading the image from the radio, attempting to change the power-on message, recreating the error message referenced earlier, and saving the new .img file locally.
Updated by Jim Unroe over 1 year ago
Geoff Beasley wrote in #note-6:
Thanks for your ongoing help. I have attached the new .img and debug.log files after having deleted the prior debug.log, starting CHIRP, downloading the image from the radio, attempting to change the power-on message, recreating the error message referenced earlier, and saving the new .img file locally.
Thanks for the additional image. I can now duplicate the error. I will take a look at this after lunch.
Updated by Jim Unroe over 1 year ago
This is apparently due to a change that was made to CHIRP itself that is causing side affects with this driver. I am investigating. In the mean time revert back the CHIRP-next build prior to this change.
Updated by K E over 1 year ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|bc552dc14c6bbec96768b9092858acd3e458e37f.