CHIRP

The most likely culprit is the programming cable and not CHIRP.

The # 1 most likely cause is Windows has installed a device driver that is incompatible with the USB-to-TTL chip in the programming cable. In nearly all programming cables with a Prolific type chip, the chip is an unauthorized (aka counterfeit) copy. The device driver that is automatically installed by Windows is intentionally incompatible with counterfeit chips. A workaround is to download, install and select the older V3.2.0.0 driver per the instructions "here":http://www.miklor.com/COM/UV_Drivers.php. Another is to replace the programming cable with one having a different brand of USB-to-TTL chip. Programming cables with an FTDI chip are popular.

The # 2 most likely cause is the programming cable's 2-pin plug is not making a good connection with the radio's socket. Some of the possible causes and their solutions are covered "here":http://www.miklor.com/COM/UV_ErrorMess.php#error1.

Jim KC9HI

No more feedback by submitter.