Bug #6953
closedPython traceback due to firmware issues
0%
Description
Hi everyone,
I help maintain chirp in Debian, and we have the following issue open in our bugtracker (text copied below) about error handling in chirp.
[[[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922439]]]
Today, when uploading a custom config to a Baofeng UV-5R I found this python
traceback:
ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 254, in run
self.__radio.sync_out()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 816, in sync_out
_do_upload(self)
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 674, in _do_upload
raise errors.RadioError(msg % (image_version, radio_version))
RadioError: Upload finished, but the 'Other Settings' could not be sent because the firmware version of the image (N5R2407BFB297 ) does not match that of the radio (HN5RV011FB297 ).
ERROR: ----------------
ERROR: Clone failed: Upload finished, but the 'Other Settings' could not be sent because the firmware version of the image (N5R2407BFB297 ) does not match that of the radio (HN5RV011FB297 ).
ERROR: --- Exception Dialog: Upload finished, but the 'Other Settings' could not be sent because the firmware version of the image (N5R2407BFB297 ) does not match that of the radio (HN5RV011FB297 ). ---
ERROR: None
ERROR: ----------------------------
The graphical interface showed a dialog window with a similar message.
Not sure if this traceback should be handled more gracefully, or this is
totally expected.
Updated by Bernhard Hailer almost 4 years ago
- Status changed from New to Closed
- Model affected changed from (All models) to Baofeng UV-5R
Totally expected :-) It just warns you that certain values could not be written to the radio, because the firmware versions aren't identical.