Wouxun HT programming cable issue

[cabletech]

And the more of these cheap Chinese radio are bought, the more this type of problem will happen and be talked about.

Also, this same kind of problem happens with the HYT, Blackbox and Hytra radios.

I can also tell you from experence, that none of these guys will give/sell the software to allow you to do more then enter frequency's.

What this means is that if the radio goes more then about 250hz off freq, then you have to send it to the factary for service.

[Outcast2]

This how to circumvent the problems. Chirp is the software that I use. The problem that most have is the driver (noted above). You need to use a previous version of the driver. I messed with the cables and a number of programs- no luck; just the yellow triangle.

I have the UV-5. The driver that I user2pl64.sys; After installing that I have NEVER had a problem with Chirp. Cheap programming keeps wanting to go to com11. If you keep the cable in, it will stay on the same com port.

[Outcast2]

Spelling error- the drive is the ser2pl64.sys, version 3.3

[jhooten]

Without knowing which version of windoze you are using this may be a little dirrerent from the XP I have on the programming computer.

open device manager
select the cable from the list to open properties
Click on the hardware tab
Click on port settings
click on advanced
On that window will be a place to select the comport number for the cable.

[LtDoc]

The 'problem' seems to be the connections made to the computer. There are quite a few different operating systems, and 'builds' of computers, so you have to know what you 'got' to start with. Then you have to know how to tell that computer to find what it's supposed to find, then what to do with it. That 'what to do with it' part is a part of the programming used to program the radio, let the program do what it's supposed to do, right? The 'trick' is supplying the right driver so that the @#$ computer knows where to 'look' to find the @#$ data. And then there's the part where your computer may not have the right connection to start with (RS-232 port/USB port/whatever). Just one more 'step' in the connecting process. What you use to make that conversion between ports can make a humongus difference, and is probably the biggest stumbling block in the whole mess. All of those converters are not the same or appropriate.
Knowing all that is YOUR responsibility. If you don't have that knowledge then you have a choice, learn what you ought'a known to start with (!yeah right!) or depend on the manufacturer of that device to make it easier for you ($$ yeah $$). [Guess which method I ended up with? $$ ]
Nothing 'new' in any of this, just a different way of looking at it...
- 'Doc

(That connections thingy isn't unique to Wouxun, almost all the other manufacturers/brands have the same 'problem'.)

[Outcast2]

There are several errors that are in the software made buy the manufacture made in the software. One has to deal with a jne at the location of the port. When the code checks to see the port number (that is stored in one of the stacks, it jumps to the wrong location that appears to default to COM: port 11. There is also a read error and write error when it loads data onto the stack.

The cable is a problem in that it does not fit all of the way so you must push hard on it.

Having said all of that, I still recommend Chirp software and an older driver. The Windows driver is also a bit irritating, in that the chip on the cable conflicts with the current driver. An older driver (XP seems the best) does not have the same problem as Win 7 (I don't about Win 8 yet) in recognizing the chip so you don't get that annoying yellow triangle. I could go into it but that would bore everyone.

Solution that always works is an older driver, Chirp software, and pushing hard on the cable when transferring data

[Outcast2]

The method of finding the COM: is exactly as describer above. I should have mentioned that. Knowing the version of the driver is also correct.

I am only familiar with XP, Vista and Win 7. Depending on the version and updates to the Prolific driver (there was one very recently) is very important. I must admit that I have not tried all of the newer versions with the newer updates. For me, it works with driver 3.3.... from XP on both 32 and 64 bit machines.

As someone noted above, the cable is very important. It would appear that the chips (now just the one that they give) are not all the same. So, the cable chip might be incompatible to various drivers. If you try everything noted above, and it stills does not work-->the cable is messed up. I would buy it from a different company (one in the US). There are still some scanners that have the old serial port. There are some serial to USB cables in the market from US. Google Serial to USB cable and they should come up. I would not spend the money unless you have to, depending on who made it can be very $$

[jshults]

I've learned a LOT about these over the last few days.....

There are USB cables with at least 3 different types of USB chips used.
Prolific, "fake" Prolific and Silicon Labs. There is a Prolific tool to Identify the chip you have. It might work.
I ended up opening my unit up to figure it out.

There are multiple drivers available for each brand of chip. Make sure you read the instructions on How to
disable auto-update the drivers from Internet. The older Prolific drives work on fake and real chips.
The new ones only work on certain chips. Also use the Device manager to manually install the driver to the "unknown" device.

Do NOT plug the cable in until you have installed the driver files from the ZIP or RAR file.

Once you determine if a driver does not work, rerun the install file and UN-install the driver before installing the next one. Use the FindPort tool to check your driver install. It'll tell you IF it see the USB cable.
I finally have 2 different cables working at the same time now. One Prolific and one Silicon Labs.

Good luck....