[chirp_users] Chirp not identifying Kenwood TM-V71

David Hagood david.hagood at gmail.com
Fri Feb 10 04:08:12 PST 2012

On Thu, 2012-02-09 at 20:36 -0800, Dale Mosby wrote:
> I have been using Chirp with a Wouun KG-UV3D and USB cable for a couple
> months with no problems. Thanks for the useful utility.
> Today I finished up a mobile install of a Kenwood TV-V71A radio. I tried
> the stable version of Chirp (0.1.12) and also the daily build from Feb 9.
> When the program attempts to identify the radio it tells me that it is
> unable to probe the radio model.
> The odd thing is that it is printing the "V71" string which seems to
> indicate that there was some successful communication taking place.
Not really:
PC->V71: ID
The V71 in this case is printed by the Python object - it hasn't yet
talked to the radio, it's just saying "I am a Python V71 radio interface
object". You'd see the same thing if the radio were an Icom and you told
Chirp to look for a Kenwood - Chirp would create a Kenwood object, talk
to the Icom, and the object would then report back to the program "Dunno
what this is, it isn't a Kenwood."

> PC->V71: ID
> V71->PC:
> PC->V71: ID
> V71->PC:
> PC->V71: ID
> V71->PC:
> PC->V71: ID
> V71->PC:

"What we have here is a FAILURE to COMMUNICATE."

It looks like the radio isn't responding. Silly things to check:
1) are you sure you are selecting the correct serial device - it should
be /dev/ttyUSB[0-3] - you can run dmesg after you plug the cable into
the computer to see what name got assigned to it.
2) Is the cable fully plugged in? I know getting the cable all the way
into my TM-V7 is a pain.

More information about the chirp_users mailing list