Bug #10270
openUV-9R Pro: not the amount of data we want
0%
Description
Have some UV-9R Pros from a year or two ago that work fine but got a fresh batch and no dice. Can't upload or download. Have tried two cables. Older UV-9R Pros work with both cables.
Relevant stack trace:
[2023-01-13 22:24:53,212] chirp.wxui.clone - DEBUG: Selected
[2023-01-13 22:24:53,221] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-01-13 22:25:10,197] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
Error reading data from radio: not the amount of data we want.
[2023-01-13 22:25:13,868] chirp.wxui.clone - ERROR: Failed to clone: Error reading data from radio: not the amount of data we want.
Traceback (most recent call last):
File "chirp\wxui\clone.py", line 60, in run
File "chirp\drivers\baofeng_common.py", line 330, in sync_in
File "chirp\drivers\baofeng_common.py", line 179, in _download
File "chirp\drivers\baofeng_common.py", line 172, in _ident_radio
File "chirp\drivers\baofeng_common.py", line 165, in _ident_radio
File "chirp\drivers\baofeng_common.py", line 128, in _do_ident
File "chirp\drivers\baofeng_common.py", line 51, in _rawrecv
chirp.errors.RadioError: Error reading data from radio: not the amount of data we want.
[2023-01-13 22:25:19,304] chirp.wxui.clone - WARNING: Stopping clone thread
Files
| chirp_debug-6zihq5cv.txt (52.6 KB) chirp_debug-6zihq5cv.txt | |||
| MayNeedModifiedToFitProperly.jpg (61.1 KB) MayNeedModifiedToFitProperly.jpg | |||
| ShouldWorkAs-Is.jpg (33.8 KB) ShouldWorkAs-Is.jpg | |||
| UV9R_Adp_Close.png (637 KB) UV9R_Adp_Close.png | Pin Comparison for UV-9R Plus | ||
| BaofengUSB_AdptComp.jpg (328 KB) BaofengUSB_AdptComp.jpg | MayNeedModifiedToWorkProperly VS ShouldWorkAsIs |
Updated by Jim Unroe over 1 year ago
- File MayNeedModifiedToFitProperly.jpg MayNeedModifiedToFitProperly.jpg added
- File ShouldWorkAs-Is.jpg added
- Status changed from New to Feedback
You most likely do not have a working connection between the programming cable and the radio. For example, leave the programming cable disconnected from the radio and attempt a download. The same error will be experienced.
If you have a programming cable of type as shown in MayNeedModifiedToFitProperly.jpg , then it is likely due to a change in the manufacturing on the case. The shape of the boss of the radio that the plug lines up on has shifted relative to the pads of the socket causing the pins of the plug to not line up with the contact pads. You would need to modify the shell of the plug on the programming cable to allow the pins to line up properly. I have one here that I modified with a file to get the pins to line up so it would work.
Another solution is to acquire and use a programming cable of the type show in ShouldWorsAs-Is.jpg. I have 2 programming cables like this and the pins always line up so they always work.
Jim KC9HI
Updated by David Price 5 months ago
Hello, I have the same problem having recently got a new UV 9R Pro, just got the cable and same errors in Chirp, and the Boafang software. Exactly as OP has described. Thing is, I also have the 'ShouldWorkAs-Is.jpg' cable, I've double checked as I'm attaching/unattaching cable and the pins are definitely lining up. I'm new to all this and I really don't know what else to try!
Debug report:
[2023-11-30 16:57:54,878] chirp.logger - DEBUG: CHIRP next-20231129 on Win32 (Unknown 10.0:22631) (Python 3.10.8)
[2023-11-30 16:57:54,928] chirp.wxui - DEBUG: Using locale: en_GB (274)
[2023-11-30 16:57:54,938] chirp.wxui - DEBUG: Translation loaded=False for CHIRP: en_GB (de,el,en_US,es,fr,hu,it,nl,pl,pt_BR,ru,tr_TR,uk_UA,zh_CN) from C:\Program Files (x86)\CHIRP\chirp\locale
[2023-11-30 16:57:54,946] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en_GB (af,an,ar,ca,ca@valencia,co,cs,da,de,el,es,eu,fa_IR,fi,fr,gl_ES,hi,hr,hu,id,it,ja,ka,ko_KR,lt,lv,ms,nb,ne,nl,pl,pt,pt_BR,ro,ru,sk,sl,sq,sv,ta,tr,uk,vi,zh_CN,zh_TW)
[2023-11-30 16:57:55,162] main - INFO: Python/3.10.8 // Windows/Windows-10-10.0.22631-SP0 // CHIRP/next-20231129 // wx/4.2.0 msw (phoenix) wxWidgets 3.2.0
[2023-11-30 16:57:55,192] chirp.wxui.main - INFO: Removing stale legacy stock config DE Freenet Frequencies.csv
[2023-11-30 16:57:55,193] chirp.wxui.main - INFO: Removing stale legacy stock config EU LPD and PMR Channels.csv
[2023-11-30 16:57:55,193] chirp.wxui.main - INFO: Removing stale legacy stock config FR Marine VHF Channels.csv
[2023-11-30 16:57:55,193] chirp.wxui.main - INFO: Removing stale legacy stock config SE Jaktradio 155MHz.csv
[2023-11-30 16:57:55,194] chirp.wxui.main - INFO: Removing stale legacy stock config UK Business Radio Simple Light Frequencies.csv
[2023-11-30 16:57:55,194] chirp.wxui.main - INFO: Removing stale legacy stock config US 60 meter channels (Center).csv
[2023-11-30 16:57:55,194] chirp.wxui.main - INFO: Removing stale legacy stock config US 60 meter channels (Dial).csv
[2023-11-30 16:57:55,194] chirp.wxui.main - INFO: Removing stale legacy stock config US CA Railroad Channels.csv
[2023-11-30 16:57:55,195] chirp.wxui.main - INFO: Removing stale legacy stock config US Calling Frequencies.csv
[2023-11-30 16:57:55,195] chirp.wxui.main - INFO: Removing stale legacy stock config US FRS and GMRS Channels.csv
[2023-11-30 16:57:55,195] chirp.wxui.main - INFO: Removing stale legacy stock config US MURS Channels.csv
[2023-11-30 16:57:55,195] chirp.wxui.main - INFO: Removing stale legacy stock config US Marine VHF Channels.csv
[2023-11-30 16:57:55,763] chirp.wxui.main - INFO: Server reports next-20231129 is latest
[2023-11-30 16:58:54,752] chirp.wxui.clone - DEBUG: Using port 'COM3'
[2023-11-30 16:58:54,753] chirp.wxui.clone - DEBUG: Selected
[2023-11-30 16:58:54,773] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-11-30 16:58:55,675] chirp.wxui.clone - DEBUG: Setting flag for prompt pre_download
[2023-11-30 16:58:55,677] chirp.wxui.clone - DEBUG: Serial opened: Serial
Error reading data from radio: not the amount of data we want.
[2023-11-30 16:58:59,212] chirp.wxui.clone - ERROR: Failed to clone: Error reading data from radio: not the amount of data we want.
Traceback (most recent call last):
File "chirp\wxui\clone.py", line 69, in run
File "chirp\drivers\baofeng_common.py", line 460, in sync_in
File "chirp\drivers\baofeng_common.py", line 259, in _download
File "chirp\drivers\baofeng_common.py", line 252, in _ident_radio
File "chirp\drivers\baofeng_common.py", line 245, in _ident_radio
File "chirp\drivers\baofeng_common.py", line 208, in _do_ident
File "chirp\drivers\baofeng_common.py", line 54, in _rawrecv
chirp.errors.RadioError: Error reading data from radio: not the amount of data we want.
[2023-11-30 16:59:04,022] chirp.wxui.clone - DEBUG: Using port 'COM3'
[2023-11-30 16:59:04,022] chirp.wxui.clone - DEBUG: Selected
[2023-11-30 16:59:04,037] chirp.wxui.clone - DEBUG: Showing pre_download prompt
[2023-11-30 16:59:06,271] chirp.wxui.clone - DEBUG: No flag change for pre_download
[2023-11-30 16:59:06,710] chirp.wxui.clone - WARNING: Stopping clone thread
Updated by David Price 5 months ago
Update - Still not working - I have gone through the guidelines on
https://www.miklor.com/COM/UV_Drivers.php#install
It comes automatically with a CH340 driver so I assume it's a SiLabs chipset- however uninstalling and reinstalling the driver linked still garners the same error. I've also tried the backdated 3.2.0.0 Prolific driver - same response.
Updated by David Price 5 months ago
*WCH chipset, not SiLabs - to confirm, I re-downloaded the CH340 driver (CH341SER) - and as stated above - same error.
Updated by Jim Unroe 5 months ago
- I read the instructions above set to Yes
David Price wrote in #note-5:
Update - Still not working - I have gone through the guidelines on
https://www.miklor.com/COM/UV_Drivers.php#install
It comes automatically with a CH340 driver so I assume it's a SiLabs chipset- however uninstalling and reinstalling the driver linked still garners the same error. I've also tried the backdated 3.2.0.0 Prolific driver - same response.
The v3.2.0.0 driver is only necessary when dealing with a Prolific type chip.
I dug out my UV-9R, UV-9G and UV-9R Pro and 3 programming cables (FTDI, Prolific and WCH). I was able to download/upload from/to all 3 radios using the FTDI chip based programming cable. With the UV-9R Pro I also used the Prolific and WCH chip based programming cables to download/upload. They all worked. I had to fiddle with the Prolific cable because it has the shell style that should be avoided.
Have you tried the factory software? I expect that it won't work, either. No programming software can work until the user provides a working connection between the radio and computer.
Your debug log doesn't show that there is any data being returned from the radio. If it is not a connection problem at the radio, it is possible that your programming cable is defective. A incomplete connection of one or more wires 3 wires at the circuit board end of the USB cable or in plug's shell itself is all it would take to not function properly.
Updated by Sean Technisean 4 months ago
- File UV9R_Adp_Close.png UV9R_Adp_Close.png added
David Price wrote in #note-4:
Hello, I have the same problem having recently got a new UV 9R Pro, just got the cable and same errors in Chirp, and the Boafang software. Exactly as OP has described. Thing is, I also have the 'ShouldWorkAs-Is.jpg' cable, I've double checked as I'm attaching/unattaching cable and the pins are definitely lining up. I'm new to all this and I really don't know what else to try!
I am also having this exact problem with my two UV-9R Plus radios and CHIRP with the same results. On both a MacBook and a Windows10 PC. The Software gives the "Error reading from radio: not the amount of data we want." The UV-9R Plus screen lights up and changes to "Welcome" and then goes back to set frequencies. I'm using a MIRKIT USB cable with the FTDI chip. One UV-9R Plus is a year old, the other is brand new. My UV-5R works just fine on this same setup.
The pictures for MayNeedModifiedToFitProperly.jpg loads, but the pins on my 2.5/3.5mm adapter do not look like they use the same pins.
The pictures ShouldWorsAs-Is.jpg, does not load at all for me. Can you upload a different version of that file? Also could you compare the one you have that works to the picture I'm posting?
Updated by Jim Unroe 4 months ago
Sean Technisean wrote in #note-8:
The pictures for MayNeedModifiedToFitProperly.jpg loads, but the pins on my 2.5/3.5mm adapter do not look like they use the same pins.
The problem that you are having is due to the use of a 2.5/3.5mm adapter. These adapters only have the wires that are used to provide PTT and speaker/mic audio. They do not include the wires that are necessary to provide the data communications for a programming cable. This is why the 'data' pins are missing on the 'plug'.
You need to use a dedicated programming cable for these 'waterproof' radios that has a USB connector containing a USB-to-Serial chip on the computer end and the correct 'M' style connector on the radio end. The links below are to a few of the programming cables that I own.
MIRKIT 7-in-1: https://www.amazon.com/gp/product/B09LD2HCZV
Retevis: https://www.retevis.com/rt6-new-black-radio-programming-cable-us
Baofeng: https://www.amazon.com/Original-Baofeng-Waterproof-Programming-Software/dp/B06XHSPJZ4
I don't know why the website doesn't want to display the thumbnail of the ShouldWorkAs-Is.jpg picture, however if I right-click the link and choose 'Open link in new tab' or just click the link, it displays fine in Firefox.
Updated by Sean Technisean 4 months ago
- File BaofengUSB_AdptComp.jpg BaofengUSB_AdptComp.jpg added
Jim Unroe wrote in #note-9:
The problem that you are having is due to the use of a 2.5/3.5mm adapter. These adapters only have the wires that are used to provide PTT and speaker/mic audio. They do not include the wires that are necessary to provide the data communications for a programming cable. This is why the 'data' pins are missing on the 'plug'.
You need to use a dedicated programming cable for these 'waterproof' radios that has a USB connector containing a USB-to-Serial chip on the computer end and the correct 'M' style connector on the radio end. The links below are to a few of the programming cables that I own.
MIRKIT 7-in-1: https://www.amazon.com/gp/product/B09LD2HCZV
Retevis: https://www.retevis.com/rt6-new-black-radio-programming-cable-us
Baofeng: https://www.amazon.com/Original-Baofeng-Waterproof-Programming-Software/dp/B06XHSPJZ4
I don't know why the website doesn't want to display the thumbnail of the ShouldWorkAs-Is.jpg picture, however if I right-click the link and choose 'Open link in new tab' or just click the link, it displays fine in Firefox.
Thank you Jim!!! That must be my problems. I'll look into getting an actual Baofeng USB cable. Also, that image did indeed work in Firefox. I hope you don't mind, I combined your two images into one comparison picture to point out the difference. Maybe it will work for all browsers.