Bug #8669
closedMac - BTECH UV-5X3 - Error reading data from radio: not the amount of data we want
0%
Description
- I’m on a Mac.
- BTECH UV-5X3
- Bao Feng Programming Cable PC03 FTDI Cable Dual Pin
- "Error reading data from radio: not the amount of data we want”
- PORT: usbserial-AB0KNAFC
Here’s the error log:
[2021-01-11 11:55:47,857] chirp.ui.inputdialog - ERROR: ----------------------------
[2021-01-11 11:56:27,592] chirp.ui.mainapp - DEBUG: User selected BTECH UV-5X3 on port /dev/cu.usbserial-AB0KNAFC
[2021-01-11 11:56:27,596] chirp.ui.clone - DEBUG: Clone thread started
Error reading data from radio: not the amount of data we want.
[2021-01-11 11:56:31,109] chirp.ui.reporting - DEBUG: Reporting exception
[2021-01-11 11:56:31,109] chirp.ui.common - ERROR: -- Exception: --
[2021-01-11 11:56:31,110] chirp.ui.common - ERROR: Traceback (most recent call last):
File "/private/var/folders/zx/09mj7lsn57z3yg9t9j4hj7c40000gp/T/AppTranslocation/99E2DB1D-EFAE-4B57-A6F5-5BD3C97F8158/d/CHIRP.app/Contents/Resources/chirp/chirp/ui/clone.py", line 256, in run
self.__radio.sync_in()
File "/private/var/folders/zx/09mj7lsn57z3yg9t9j4hj7c40000gp/T/AppTranslocation/99E2DB1D-EFAE-4B57-A6F5-5BD3C97F8158/d/CHIRP.app/Contents/Resources/chirp/chirp/drivers/baofeng_common.py", line 321, in sync_in
data = _download(self)
File "/private/var/folders/zx/09mj7lsn57z3yg9t9j4hj7c40000gp/T/AppTranslocation/99E2DB1D-EFAE-4B57-A6F5-5BD3C97F8158/d/CHIRP.app/Contents/Resources/chirp/chirp/drivers/baofeng_common.py", line 179, in _download
ident = _ident_radio(radio)
File "/private/var/folders/zx/09mj7lsn57z3yg9t9j4hj7c40000gp/T/AppTranslocation/99E2DB1D-EFAE-4B57-A6F5-5BD3C97F8158/d/CHIRP.app/Contents/Resources/chirp/chirp/drivers/baofeng_common.py", line 172, in _ident_radio
raise error
RadioError: Error reading data from radio: not the amount of data we want.
Updated by Bernhard Hailer over 3 years ago
- Status changed from New to Feedback
- Model affected changed from (All models) to BTECH UV-5X3
- Platform changed from Windows to MacOS
I assume this is MacOS. This looks like a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
If there's no solution to be found in any of them, please read: How To Report Issues and provide a debug log. Thank you!
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
On older MacOS versions, you must have the KK7DS Python runtime for Mac OSX installed. I don't have information yet what to do on new versions (like Big Sur).
Big Sur is a problem on its own, because basically all USB drivers need to be rewritten. FTDI is still working on it.
Also see MacOS Tips!
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.
Updated by Bernhard Hailer about 3 years ago
- Status changed from Feedback to Closed
No more input from submitter.