Bug #10693
openBaofeng UV-S9X3 downgraded from tri-band to dual-band
Added by Mike A 11 months ago. Updated 8 months ago.
0%
Description
Immediately after "upload to radio", the Baofeng UV-S9X3 radio can no longer access 222 - 225 MHz via VFO and any saved memories on the 222 MHz band no longer transmit. This issue has been reported over on Amazon by multiple buyers of the this radio.
144 and 440 MHz bands continue to function as expected (VFO, memory).
Configured using the Radioddity > UV-5RX3 per "Supported Radio Models" CHIRP list.
Link to radio on amazon.com for hardware reference: https://tinyurl.com/4jrrufz6
Files
| Radioddity_UV-5RX3_20230701.img (6.53 KB) Radioddity_UV-5RX3_20230701.img | Mike A, 07/01/2023 05:27 PM | ||
| Radioddity_UV-5RX3_20191004-STOCK.img (6.51 KB) Radioddity_UV-5RX3_20191004-STOCK.img | Mike A, 07/01/2023 08:33 PM | ||
| baofeng_wp970i.py (32.3 KB) baofeng_wp970i.py | Adds UV-S9X3 support to wp970i driver | Jim Unroe, 07/22/2023 08:02 PM | |
| Baofeng_UV-S9X3_20230722(factory #1).img (8.19 KB) Baofeng_UV-S9X3_20230722(factory #1).img | Image from red UV-S9X3 bought from Amazon as S9X3 | Jim Unroe, 07/22/2023 08:02 PM | |
| Radioddity_UV-5RX3_20230722(factory #1).img (6.53 KB) Radioddity_UV-5RX3_20230722(factory #1).img | Image from red UV-S9X3 bought from Amazon as 5RX3 | Jim Unroe, 07/22/2023 08:05 PM | |
| debug.log (34.2 KB) debug.log | Chuck Murcko, 09/21/2023 11:11 PM | ||
| Baofeng_UV-S9X3_20230921(factory).img (8.19 KB) Baofeng_UV-S9X3_20230921(factory).img | Chuck Murcko, 09/21/2023 11:34 PM | ||
| debug.log (15.5 KB) debug.log | Chuck Murcko, 09/21/2023 11:35 PM | ||
| debug.log (4.46 KB) debug.log | Chuck Murcko, 09/22/2023 03:09 AM |
Updated by Jim Unroe 11 months ago
This is because Baofeng has made a change to their UV-5R and UV-82 like radios that has made then incompatible with CHIRP when uploading. This makes this issue a duplicate of issue #10505.
Hopefully you saved a copy of your first successful download, unedited, as a backup.
Jim KC9HI
Updated by Jim Unroe 11 months ago
Mike A wrote in #note-2:
Thanks for the prompt response Jim. I have an unmodified copy of the original stock image, but restoring through "upload to radio" does not restore the 222 MHz band function. Is there some other image write method that should be used in this situation?
This is because the radio corrupts the Aux block of memory every time CHIRP uploads to your radio. For the time being you will have to follow the instructions provided in #10505#note-40 to restore. You can then continue to use this method to program your radio until a permanent fix is developed or use the factory software.
Jim KC9HI
Updated by Mike A 11 months ago
Jim Unroe wrote in #note-3:
This is because the radio corrupts the Aux block of memory every time CHIRP uploads to your radio. For the time being you will have to follow the instructions provided in #10505#note-40 to restore. You can then continue to use this method to program your radio until a permanent fix is developed or use the factory software.
Jim KC9HI
Jim - thank you so much. 100% confirmation that this process works and has restored the 222 MHz functionality on the radio and also allows me to use CHIRP to program the radio. I am attaching a "stock image" that I have used to successfully restore the 222 MHz functionality to this message in case anyone else ends up in the same situation.
Updated by Doug Nelson 11 months ago
I know it is a different radio, but I can't seem to transmit on the Yaesu FT2800M, but receive is fine. The changes were in maybe the same time frame.
Updated by Chuck Murcko 10 months ago
Jim Unroe wrote in #note-1:
This is because Baofeng has made a change to their UV-5R and UV-82 like radios that has made then incompatible with CHIRP when uploading. This makes this issue a duplicate of issue #10505.
Hopefully you saved a copy of your first successful download, unedited, as a backup.
Jim KC9HI
Here's another data point. I just received a pair of UV-5RX3s, and the first CHIRP read shows one major difference between your factory image and mine: the upper VHF limit I read is 174 MHz(vs. 260 MHz for yours), yet the radio transmits on 220 out of the box.The radio still transmits on 220 MHz after uploading either factory image using UseAtOwnRisk. Firmware version is the same for both.
Updated by Chuck Murcko 10 months ago
In addition, the fatory .img files from the two radios differ by one byte.
chuck@argo-iv:~/Documents/Radio_VHF-UHF$ cmp -l Radioddity_UV-5RX3_20230720.img Factory\ Images/HN5VR01\ Radioddity_UV-5RX3(151123H)(factory).img
4105 377 132
Updated by Jim Unroe 10 months ago
- File baofeng_wp970i.py baofeng_wp970i.py added
- File Baofeng_UV-S9X3_20230722(factory #1).img Baofeng_UV-S9X3_20230722(factory #1).img added
- File Radioddity_UV-5RX3_20230722(factory #1).img Radioddity_UV-5RX3_20230722(factory #1).img added
Chuck Murcko wrote in #note-7:
In addition, the fatory .img files from the two radios differ by one byte.
chuck@argo-iv:~/Documents/Radio_VHF-UHF$ cmp -l Radioddity_UV-5RX3_20230720.img Factory\ Images/HN5VR01\ Radioddity_UV-5RX3(151123H)(factory).img
4105 377 132
I don't normally do this, but I went ahead an bought a UV-S9X3 on my own. Now I have a "stock" image that isn't messed up. Looking at it I can clearly see that this radio looks like it stores the band limits more like the BF-A58S and should be read from and written to using that driver. It is a shame that Baofeng uses the same "magic" to initiate cloning on the UV-S9X3 as it does the UV-5RX3.
Attached is the test driver module that adds the Baofeng UV-S9X3 model selection using the better driver. Load it using the follow guide: LoadingTestModules
I have also attached my "factory" image for those that want to try it (be sure to capture a new image from your radio before trying it).
Jim KC9HI
Updated by Chuck Murcko 8 months ago
I'm kinda surprised no one's replied. I got a UV-S9X3 today, and tried the new driver. Transmit works on 220. I've attached the debug log. The errors in it may be a separate issue from this one; as I am unable to change settings and getting an out of range frequency error "Error applying settings - Can't be between 179.9975-400.0000" when I try to do so.
Updated by Chuck Murcko 8 months ago
- File Baofeng_UV-S9X3_20230921(factory).img Baofeng_UV-S9X3_20230921(factory).img added
- File debug.log debug.log added
I also tried changing settings with Chirp on my factory image and got the above error. Image and debug log attached. The errors occur when I try to change Disply Mode A/B from Frequency to Channel.
Updated by Chuck Murcko 8 months ago
All's almost well. I used your factory image instead of mine. The only error I get in Settings is when I try to set Work Mode Settings-->VFO A or B frequency to 220 band. I get" Property error - Can't be between 179.9975-400.0000". All other settings and 220 band work.