Overview¶

This error means chirp got no response from the radio at all. In almost all cases, this means a connectivity problem (although it can occur if you select the completely wrong driver for what is connected). The most common reason for this problem with inexpensive radios and connectors is a fitment issue*. Other reasons include bad cable connections, faulty drivers, etc.

Workaround¶

If you have an inexpensive radio that uses the Kenwood K1 connector (the ubiquitous dual-pronged 90-degree one), you can probably work around the issue by pushing very hard to fully seat the connector, or even by trimming some of the plastic around the radio and/or the connector itself.

Solution¶

The best and most obvious real solution is to obtain higher quality hardware made to more exacting standards. The CHIRP project recommends high-quality FTDI-based cables from BlueMax49ers, which generally also have high-quality connectors that minimize problems. Note that just because you're using the cable that came with your radio or the one your radio manufacturer sells/recommends, does not mean it is the best one available.

Other good solutions include this one from Jim, KC9HI:

What I came up with as a solution for this was to create extension
cables. The straight plugs eliminate the interference with the case
without needing to do any modifications to the programming cable or
the radio.

I started out with the 2.5mm -> 3.5mm adapter and 3.5mm -> 2.5mm
adapter cables so that by swapping the order I create a 2.5mm -> 2.5mm
and 3.5mm -> 3.5mm extension of equal length. This was especially
important because I could not find regular 2.5mm or 3.5mm extensions
or a reasonable length or of an equal length.

I eventually did find a good source of extension cables of reasonable
and matching length. That is what I now recommend and use for the
UV-17 case style socket well depth issue.

6inch 3.5mm SLIM Mini-Stereo TRS Male to Female Audio Extension Cable
6inch 2.5mm Mini-Stereo TRS Male to Female Speaker/Audio EXTENSION Cable