CHIRP

The issue is most likely that you don't have a working connection between the radio and the computer. No software can program a radio when this is the case.

With this model there is typically 2 causes. Many times, both issues occur at the same time.

1. The programming cable most likely has a Prolific type USB-to-TTL chip. Both the PL2303HXA and more recently the PL2303TA chip have become EOT (End-Of-Life) by the chip vendor. For this reason they have removed support for these chips from the driver that they supply to Microsoft and the end user. The work around is to download, install and select a Prolific driver equal to or older than Prolific v3.3.2.105 (v3.2.0.0 recommended). A link for the driver and instructions for installing and selecting the driver are available "here":https://www.miklor.com/COM/UV_Drivers.php.

2. The programming cable is not properly connected with the radio. The radio end of the programming cable has 2 different styles of connectors. One has a plastic shell that is flush with the surface that the connection pins stick out of (photo attached). This is the better of the 2 types. It will generally allow the pins to line up correctly every time. The other has a plastic shell that sticks out past the surface that the pins stick out, roughly the same distance that the pins stick out (photo attached). The way this shroud fits over the boss of the radio that contains the speaker/mic socket restricts movement of the plug and if either is not made with very high precision can prevent the pins of the plug from lining up with the pads of the socket. My cable of the first type works every time (after installing the correct driver). My cable of the second type would only work after modifying the shroud of the connector with a file.

To show that either of these is contributing with this problem, perform this experiment. Leave the connector of the programming cable disconnected from the radio and then attempt a download using CHIRP. The error message will be exactly the same.

Jim KC9HI