New Model #3733
closed
Added by Bob Evans over 8 years ago.
Updated over 4 years ago.
Equipment Loan/Gift Offered:
No
I read the instructions above:
Description
I recently got a new (very new - early adopter) radio - the Wouxun KG-UV8E. I was told it is based on the KG-UV8D and would work with Chirp using the 8D driver. Every attempt either can't read (failure to connect) or gives the error
Failed to communicate with radio: string index out of range
I am running OS X 10.11.5. I am using the serial adaptor/cable Chirp labels dev/cu.usbserial-A403RNWA that came with my Baofeng UV-82 (works great on that one, and my older KG-UV3d & UV6X Wouxuns). This is the only cable I can currently get to work with the signed usb serial (pl2303?) driver I finally found for El Capitan. I have been told that the UV8E is essentially a tri-band 8D (adds 220 band). I haven't been able to get to a working Windows machine to try with the factory software - which appears to be the 8D software on Wouxun's site - just to see if the cable works. Part of that problem has also been having the correct driver for Windows 7 or 10. Did try with the supplied Wouxun cabled software on Windows 10 running under Fusion (have been able to do that for the older radios in the past) - but currently I can't talk to any of my radios that way so I suspect it is a driver issue. Haven't tried with the Baofeng cable.
Wasn't sure wether to call this a Bug or New Model as I'd been informed that Chirp's 8D driver worked with the gas
Files
- Status changed from New to Feedback
Hi Bob,
Unfortunately, the stories that start out with "It's just like X, it'll work with CHIRP" rarely end in happiness. My guess is that the error you're hitting is in the very first bit of the download process where we query the radio and examine the response. I expect the radio isn't responding at all and we're improperly handling that situation. I've added some extra debugging to that driver which will be in tomorrow's daily build which will help us track it down better. But, if the radio isn't responding to the UV8D query string, it won't be a great answer.
Jim might have some more insight into what this model is based on or the differences.
Anyway, please try with tomorrow's build when it's available and report back.
Thanks!
Hi Dan,
Thanks for looking at this. Here's the latest. Found actual Wouxon software for this radio (typical Wouxon clumsy interface - can't load from spreadsheet or .csv , can't export radio read to .csv or anything else etc.). Found and installed correct USB Serial driver (per instructions at Mikor) in Windows 10 (both in a desktop and in a VMWare Fusion emulated installation on a MAcBook Pro). Cable and drivers worked fine was able to download and upload channels on all three bands just fine on both installations. I think that covers potential cable/driver issues. May try to download the Wouxon KG-8D software and see what happens. Only "glitch" in using Wouxon software was trying to program and upload some commercial channels I have programmed on my KG-UV6DX which has low power/narrow band restricted Tx on commercial channels. - outside the 8e's valid Tx range. One potential problem i see with using the UV8D module (not knowing how the programming) is if it error checks for frequencies outside the known range for a particular model. I do have a 220 channel programmed in the UV8E.
If, as you suspect, the radio just isn't responding to the "parent" model query, what are the chances of getting a KG-UV8E build in the works? This is a great little new tri-band (2M, 1.25M, 70mm) HT. Would be happy to help where I can - possibly even radio loan but that might be tough as I'm in a local ACS group and we are re-configuring so our primary repeater is in 440 band, secondary in 220 band and simplex in 2M - loan depends on how long I might have to carry two radios to get try-band function.
Bob Evans
PS - forgot to include - attempt on 20160611 daily build generated error" Radio din not respond" see prior attached debug log - B
- Status changed from Feedback to Rejected
Hi Bob,
Indeed the radio isn't responding to the initial query. You might find someone that is willing to talk you through taking a serial log of the OEM software in order to see what string it's using (on the off chance that that is all that is different -- not likely). My policy is that I don't do remote debug because it's just very time consuming and rarely fruitful.
If there is not a "model support" issue already open requesting this model, you should open one and mark it as "equipment loan offered" if you wish. There are a huge number of other more popular models being worked as higher priority at the moment, but getting the issue opened is the first start. At the end of the day, it'll take a developer that is interested in doing the work to pick it up, but an offer of a loan is much more likely to get attention than one that doesn't!
I'm going to close this as "rejected" just because it's not a bug with the current wouxun driver so you can open that new issue cleanly for the new model.
Thanks!
- Tracker changed from Bug to New Model
- Status changed from Rejected to Closed
- Chirp Version changed from 0.4.0 to daily
- Equipment Loan/Gift Offered set to No
Supported now for a while already.
Also available in: Atom
PDF