[chirp_users] Chirp not identifying Kenwood TM-V71
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.
I am running this with a laptop running Ubuntu 11.04 and using he Kenwood USB to serial cable KPG-46U. I also have available a laptop running RHEL 6.2 but have not tried that yet.
Any hints appreciated. Terminal trace info follows. Thanks & 73, Dale, K7FW -------------------
dale@dale-T42:~/AmateurRadio/chirp-0.1.12$ python chirpw CHIRP 0.1.12 on Linux - Ubuntu 11.04 PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: --- Exception Dialog: Unable to probe radio model --- Traceback (most recent call last): File "/home/dale/AmateurRadio/chirp-0.1.12/chirpui/clone.py", line 167, in run cs.radio_class = detect.DETECT_FUNCTIONS[vendor](cs.port) File "/home/dale/AmateurRadio/chirp-0.1.12/chirp/detect.py", line 103, in detect_kenwoodlive_radio raise errors.RadioError("Unable to probe radio model") RadioError: Unable to probe radio model ---------------------------- ^CTraceback (most recent call last): File "chirpw", line 69, in <module> gtk.main() KeyboardInterrupt dale@dale-T42:~/AmateurRadio/chirp-0.1.12$
dale@dale-T42:~/AmateurRadio/chirp-daily-02092012$ python chirpw CHIRP daily-02092012 on Linux - Ubuntu 11.04 (Python 2.7.1+) PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: --- Exception Dialog: Unable to probe radio model --- Traceback (most recent call last): File "/home/dale/AmateurRadio/chirp-daily-02092012/chirpui/clone.py", line 164, in run cs.radio_class = detect.DETECT_FUNCTIONS[vendor](cs.port) File "/home/dale/AmateurRadio/chirp-daily-02092012/chirp/detect.py", line 103, in detect_kenwoodlive_radio raise errors.RadioError("Unable to probe radio model") RadioError: Unable to probe radio model
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.
First off, many thanks to David for taking an initial pass at helping with this. One of the reasons for this list is so that users can help users and let me concentrate on writing code. I wish I could get more people to follow David's example :)
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.
I think this is a known issue. Can you try setting your radio to 9600 baud and using 0.1.12 to download it? According to this bug, that should work:
http://chirp.danplanet.com/issues/27
I need to get over to the fire station with my laptop and wrestle with the V71 a bit to figure out what is going on.
Thanks!
Thanks for the suggestions. Evidently with the V71 as first choice I was fooled into thinking that Chirp was conversing with the radio.
I think the problem may be something called "modem-manager".
I checked Menu #519 "PC terminal baud rate speed" and found that it was 9600 baud. The manual indicates that this is default and I found this to be the case. I also checked that the interface cable is securely mated with the microphone jack.
I checked the /var/log/syslog file on Ubuntu and found that after connecting the USB device the "modem-manager" was opening and closing the USB0 port. This is something I had not heard of before. It was not immediately clear how to terminate this, if the process was killed it was respawned.
I hoped that this was a feature (mis-feature?) on Ubuntu so switched to a laptop with RHEL 6.2. One again, after plugging in the USB connector I found that modem-manager was fussing with the port. Could this be getting in the way somehow? I see the same behavior in which radio is not detected.
Here is the /var/log/messages from the RHEL 6.2 system: Feb 10 10:58:11 dalew500 kernel: usb 6-2: new full speed USB device using uhci_hcd and address 4 Feb 10 10:58:11 dalew500 kernel: usb 6-2: New USB device found, idVendor=10c4, idProduct=ea60 Feb 10 10:58:11 dalew500 kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 10 10:58:11 dalew500 kernel: usb 6-2: Product: CP2102 USB to UART Bridge Controller Feb 10 10:58:11 dalew500 kernel: usb 6-2: Manufacturer: Silicon Labs Feb 10 10:58:11 dalew500 kernel: usb 6-2: SerialNumber: 0567000FAC37 Feb 10 10:58:11 dalew500 kernel: usb 6-2: configuration #1 chosen from 1 choice Feb 10 10:58:11 dalew500 kernel: usbcore: registered new interface driver usbserial Feb 10 10:58:11 dalew500 kernel: USB Serial support registered for generic Feb 10 10:58:11 dalew500 kernel: usbcore: registered new interface driver usbserial_generic Feb 10 10:58:11 dalew500 kernel: usbserial: USB Serial Driver core Feb 10 10:58:11 dalew500 kernel: USB Serial support registered for cp210x Feb 10 10:58:11 dalew500 kernel: cp210x 6-2:1.0: cp210x converter detected Feb 10 10:58:12 dalew500 kernel: usb 6-2: reset full speed USB device using uhci_hcd and address 4 Feb 10 10:58:12 dalew500 kernel: usb 6-2: cp210x converter now attached to ttyUSB0 Feb 10 10:58:12 dalew500 kernel: usbcore: registered new interface driver cp210x Feb 10 10:58:12 dalew500 kernel: cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver Feb 10 10:58:12 dalew500 modem-manager: (ttyUSB0) opening serial device... Feb 10 10:58:24 dalew500 modem-manager: (ttyUSB0) closing serial device... Feb 10 10:58:24 dalew500 modem-manager: (ttyUSB0) opening serial device... Feb 10 10:58:30 dalew500 modem-manager: (ttyUSB0) closing serial device...
I tried the USB cable for the Wouxon hand held radio and was able to download from that radio. Here is the /var/log/messages file. Note that no mention of "modem-manager".
Feb 10 11:20:54 dalew500 kernel: usb 3-1: new full speed USB device using uhci_hcd and address 2 Feb 10 11:20:54 dalew500 kernel: usb 3-1: New USB device found, idVendor=067b, idProduct=2303 Feb 10 11:20:54 dalew500 kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 10 11:20:54 dalew500 kernel: usb 3-1: Product: USB-Serial Controller Feb 10 11:20:54 dalew500 kernel: usb 3-1: Manufacturer: Prolific Technology Inc. Feb 10 11:20:54 dalew500 kernel: usb 3-1: configuration #1 chosen from 1 choice Feb 10 11:20:54 dalew500 kernel: USB Serial support registered for pl2303 Feb 10 11:20:54 dalew500 kernel: pl2303 3-1:1.0: pl2303 converter detected Feb 10 11:20:54 dalew500 kernel: usb 3-1: pl2303 converter now attached to ttyUSB0 Feb 10 11:20:54 dalew500 kernel: usbcore: registered new interface driver pl2303 Feb 10 11:20:54 dalew500 kernel: pl2303: Prolific PL2303 USB to serial adaptor driver
What do you think? Is modem-manager involved in the problem or is it something else? Has the Kenwood USB cable been used with Linux and a V71? Other suggestions welcomed. 73, Dale, K7FW
I think the problem may be something called "modem-manager".
Well, maybe, although if it closes the modem after inspecting it, I expect it's probably fine. You could try something like "service modem-manager stop".
The manual indicates that this is default and I found this to be the case. I also checked that the interface cable is securely mated with the microphone jack.
Hmm? The cable should go into the mini-DIN connector on the back of the radio... Which cable are you using exactly?
I saw modem-manager do a few open/close cycles on USB0. Did seem to end up in the "closed"state. Also did not find anything with Google telling me that it was causing serious problems trying to use a USB device. I did try the "service stop" method of disabling while I had the laptop out in the truck. A bit of investigation when I returned to the house indicated that modem-manager wasn't really a typical service but somehow related to dbus which is why the "service stop" did not terminate it. I haven't had time to look into this further.
The cable I have is from Kenwood, "KPG-46U". This has a standard USB connector on one end and an 8 pin modular connector on the other (RJ45 is the designation I think). The box says "interface cable (USB)".
The radio has two potential places that would accept the RJ45. One is the microphone connector the other is the connection for the front panel. The instruction sheet that came with the came is quite "unhelpful" by stating: "Connect one of the KPG-22U/36U/43U/46U USB connectors to the USB port of the computer, and the other connector to the transceiver."
They do not say *where* to connect it. I tried a bit of Google searching with no luck and didn't want to see any smoke escape from this new radio so I gave the Ham Radio Outlet store where I purchased all this a call. They said to connect the cable to the microphone port. So that is what I have been doing.
Is this cable actually what is used to program the radio? If so, where does it connect? If not, WTF is the cable for and why did HRO sell me the cable?
Thanks for your assistance. And thanks for the software - useful so far with the Wouxun and I'm sure before long for the Kenwood as well. 73, Dale
Is this cable actually what is used to program the radio?
No. That's the cable for the TM-271 or TM-281, not the V71.
If not, WTF is the cable for
You want a PG-5G for that radio.
and why did HRO sell me the cable?
Hmm, not familiar with HRO, huh? :-D
Well thank you for the assistance in debugging. The V71A, remote install kit, and programming cable were all purchased at the same time from Ham Radio Outlet (HRO) in the Portland, Oregon area.
I made the incorrect assumption that this bundle of parts were all going to work together. It now seems that HRO sold me the incorrect cable. They confirmed this in my phone call with them just now.
Sorry about starting out by blaming the software rather than the hardware. :-)
I will give another try with the correct cable and I suspect see better results.
Thanks & 73, Dale, K7FW
Dale,
FWIW, and hopefully you didn't buy the expensive Kenwood cable yet, I use this cheap cable with Chirp and my TM-V71A: http://www.pccables.com/cgi-bin/orders6.cgi?action=Showitem&id=ID940742&...
Also, as for that modem-manager process, it could be something udev spawns. I recently switched from Ubuntu to Debian on all of my machines, otherwise I'd try to do a little more digging for you.
Mat WD4DDY
On 02/10/2012 01:53 PM, Dale Mosby wrote:
Well thank you for the assistance in debugging. The V71A, remote install kit, and programming cable were all purchased at the same time from Ham Radio Outlet (HRO) in the Portland, Oregon area.
I made the incorrect assumption that this bundle of parts were all going to work together. It now seems that HRO sold me the incorrect cable. They confirmed this in my phone call with them just now.
Sorry about starting out by blaming the software rather than the hardware. :-)
I will give another try with the correct cable and I suspect see better results.
Thanks & 73, Dale, K7FW
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Modem-manager comes from NetworkManager (which I hate btw). It's evil and from what I can tell, can't be disabled today. From all the searching I did, the easiest way to stop it from messing with serial ports is to find it with "which" and rename it to something that NetworkManager can't find. Effective but such an ugly hack.
--David
Mathew Mrosko wrote:
Dale,
FWIW, and hopefully you didn't buy the expensive Kenwood cable yet, I use this cheap cable with Chirp and my TM-V71A: http://www.pccables.com/cgi-bin/orders6.cgi?action=Showitem&id=ID940742&...
Also, as for that modem-manager process, it could be something udev spawns. I recently switched from Ubuntu to Debian on all of my machines, otherwise I'd try to do a little more digging for you.
Mat WD4DDY
On 02/10/2012 01:53 PM, Dale Mosby wrote:
Well thank you for the assistance in debugging. The V71A, remote install kit, and programming cable were all purchased at the same time from Ham Radio Outlet (HRO) in the Portland, Oregon area.
I made the incorrect assumption that this bundle of parts were all going to work together. It now seems that HRO sold me the incorrect cable. They confirmed this in my phone call with them just now.
Sorry about starting out by blaming the software rather than the hardware. :-)
I will give another try with the correct cable and I suspect see better results.
Thanks & 73, Dale, K7FW
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Sorry about starting out by blaming the software rather than the hardware. :-)
No worries, I write software and I tend to blame it first too :)
I will give another try with the correct cable and I suspect see better results.
Excellent. I took a trip to the fire station tonight where we have a V71. I fixed a couple of issues with the driver that have been outstanding for a while. So, when you get the correct cable, grab the latest daily build and enjoy the latest features *and* working V71 support :)
Dan,
I am trying to use Chirp on a Vista Laptop and I am getting an error. Vista Business with all updates..
C:\Program Files\CHIRP\chirpw.exe The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.
The log says the error is ID 33 with the following text in the info field:
Activation context generation failed for "C:\Program Files\CHIRP\chirpw.exe". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18 e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.
-- John
participants (6)
-
Dale Mosby -
Dan Smith -
David Hagood -
David Ranch -
John Gorena -
Mathew Mrosko