Bug #805
closed
Wouxun UV6D - UART cable error
Added by Thomas Greer about 11 years ago.
Updated about 4 years ago.
Model affected:
Wouxun UV-6D
I read the instructions above:
Description
Hi
OSX 10.8.3 (And Windows 8)
CP2102 USB to UART
CHIRP 0.3.1
Failed to communicate with radio: I can't talk to this model (000: 00 00 00 00 00 00 00 00 ........
008: 00 00 00 00 00 00 00 00 ........
)
Using the official cable that came with the radio. Any help would be appreciated.
Regards
Thomas
Files
I don't know what to think. I dug out my homebrew CP2102 programming cable to see what would happen. I tried to read from my UV6D and go the same error. I rechecked to make sure the plugs were in solid. I made sure that device manager had assigned the same COM port as detected by CHIRP. Error, error, error. My debug.log is attached.
I then switched back to my Prolific (clone) chip based programming cable and the download worked as expected. I then went back to my CP2102 based cable and it work fine every time. No matter what I do, I cannot make it mess up again. The only thing I know that I did different the second time was to turn the radio on after the cables were plugged in.
Jim
It's the official Wouxun cable, so I'd hope its not that at fault!
With the Kenwood TH-D72 (CP210x) on OS X, hardware flow must be enabled to communicate with the radio. This seems to be an issue with the way Silicon Labs wrote their OS X driver. I haven't heard of any issues on Windows.
Just to see if this is the same issue, try loading the attached module (developer functions must be enabled). In this module, I pasted in the trick we use with the D72 to enable hardware flow only on OS X.
Unfortunately we don't have a good way to detect this condition and resolve it, so this fix probably won't work for everyone with other types of cables.
What is the name of the port? Something like /dev/cu.xxx.
/dev/cu.SLAB_USBtoUART
If I need to load the module when I want to program my radio, then it's a small price to pay really... The Wouxun stuff doesn't work. I had no labels and couldn't see anything!
Good, that is identical to how my TH-D72 (built in USB port) shows up, and it presents the same problem. One solution would be to enable hardware flow control every time we encounter "/dev/cu.SLAB_USBtoUART" on OS X. Is this only an OS X issue, or does it affect Windows as well? I've only seen it on OS X.
diff -r f83383051e60 chirpui/mainapp.py
--- a/chirpui/mainapp.py Mon Apr 22 09:52:39 2013 -0700
+++ b/chirpui/mainapp.py Wed Apr 24 21:02:36 2013 -0700
@@ -595,7 +595,7 @@
try:
ser = serial.Serial(port=settings.port,
baudrate=rclass.BAUD_RATE,
- rtscts=rclass.HARDWARE_FLOW,
+ rtscts=rclass.HARDWARE_FLOW or settings.port == "/dev/cu.SLAB_USBtoUART",
timeout=0.25)
ser.flushInput()
except serial.SerialException, e:
I was using it in windows via VMWare Fusion... so not 100% on if it's really a windows problem or if its still needing the HW flow enabled..
- Status changed from New to Closed
- Chirp Version changed from 0.3.0 to daily
- Model affected changed from Wouxun UV6D to Wouxun UV-6D
Also available in: Atom
PDF