Bug #10739
openUV5R Power On Message
0%
Description
Updated to the newest Chirp. Wanted to Change my message to my Call Sign and it refused to change. It fully uploaded to the radio, but didn't change.
Downgraded to:
CHIRP next-20230629 on Python 3.10.8 wxPython 4.2.0 msw (phoenix) wxWidgets 3.2.0
Changed message to my Call Sign and worked perfectly.
Files
Updated by Wito Krasnal 10 months ago
please refer to #10505.
do You have any warning messages from CHIRP when uploading?
20230629 was the last version before recent fixes concerning some abnormal Baofengs UV-5R.
but the nature of the fixes is such that if 20230629 worked for You, from 20230714 onwards should also work.
Updated by James McDowell 10 months ago
No Warning messages. Everything programmed like it usually does. Just didn't change any of the settings. It did change the channels as changed.
Version I tried on that seemed to have the issue was 20237019.
I reverted back to 20230629 and everything seemed to work normally.
Updated by Wito Krasnal 10 months ago
please report the issue to the developers under #10505. It might be important to them.
Updated by James McDowell 10 months ago
Will do... Just Installed 20230722 and still doing the same thing.
I dont need to change settings right now, but its good to have.
Updated by Wito Krasnal 10 months ago
ok to unload some work from the developers' backs I have reverted to 20230719 and changed the boot message like You did. For me it not only worked properly but there is a surplus surprise: since CHIRP (at least 20230719) does not automatically change welcome message to UPPERCASE, it happened that Baofeng UV-5R does accept lowercase letters at least in the welcome message. Please follow the discussion under #10505.