[chirp_users] [CHIRP] #91: Kenwood tm-v71 identifies, then Chirp freezes...

CHIRP Tracker

25 Apr 2011 25 Apr '11

7:52 a.m.

#91: Kenwood tm-v71 identifies, then Chirp freezes... --------------------------------+------------------------------------------- Reporter: psharmor@… | Type: Bug Status: new | Priority: Functionality Milestone: | Component: Memory Editor Version: 0.1.9 | Keywords: kenwood tm-v71 tmv71 Platform: Linux | --------------------------------+------------------------------------------- In my several attempts to get my Kenwood TM-V71A to be workable with Chirp, anytime I start the detection routine for reading the radio, the windows both freeze / blank, and it produces the following, but nothing further, on terminal:

me@host:~$ chirpw PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: PC->V71: ID V71->PC: ID TM-V71 PC->D7: ID

This is my current scenario: Running v0.1.11 on Kubuntu Natty (beta, updated multiple times a day), on a Fit-PC2i, via direct serial to pg-5h cable kit. Serial port is confirmed as /dev/ttyS0, Kenwood's own software works correctly, via sharing of the serial port to VirtualBox WinXP image. Of course, XP is NOT running, during my attempts to utilize Chirp, so port should be free, and is also chmod 777 for testing purposes.

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

Show replies by date

CHIRP Tracker

25 Apr 25 Apr

7:58 a.m.

#91: Kenwood tm-v71 identifies, then Chirp freezes... ---------------------------------+------------------------------------------ Reporter: psharmor@… | Owner: kk7ds Type: Bug | Status: accepted Priority: Functionality | Milestone: Component: Memory Editor | Version: 0.1.9 Resolution: | Keywords: kenwood tm-v71 tmv71 Platform: Linux | ---------------------------------+------------------------------------------ Changes (by kk7ds):

* owner: => kk7ds * status: new => accepted

Comment:

Hmm, that's strange. It looks like maybe CHIRP isn't recognizing that it got a reply from the radio and moving on to the next baud rate. I tested this not to long ago, but I'll be in a spot to try it again tonight so maybe I'll see if I can do that.

I recently moved the V71 to using the live-mode driver along with the D710. Could you try the last beta before the current release (0.1.11b7) to see if it behaves properly in clone mode? You can get it here:

http://chirp.danplanet.com/download/beta/

That will be a useful data point.

Thanks!

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:1 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

8:19 a.m.

Comment (by anonymous):

Replying to [comment:1 kk7ds]:

...

Hmm, that's strange. It looks like maybe CHIRP isn't recognizing that

it got a reply from the radio and moving on to the next baud rate. I tested this not to long ago, but I'll be in a spot to try it again tonight so maybe I'll see if I can do that.

...

I recently moved the V71 to using the live-mode driver along with the

D710. Could you try the last beta before the current release (0.1.11b7) to see if it behaves properly in clone mode? You can get it here:

...

http://chirp.danplanet.com/download/beta/

That will be a useful data point.

Thanks!

Unfortunately, no change. This may have been the version I was already running, although the tar.gz did NOT have the b7 in title (I just discovered your software 2-3 days ago, and excited as all get out!!).

Thank you for the quick response, and hopefully, I'll be able to help ya' with troubleshooting!

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:2 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

8:26 a.m.

Comment (by kk7ds):

Hmm, not sure what to say about that. I believe you also have used CHIRP with a wouxun, right? Was that with the same machine and serial port, or was it using the USB cable?

Do you have any other radios to try? I'll admit that I don't get to test the kenwood live driver as often as I'd like, but I've never seen that sort of behavior before and I'd lean towards something strange with your atypical machine's serial port.

Do you have a USB-to-serial adapter you could try? Also, could you set the PC baudrate on the V71 down to something slower, like 9600 or something and see if that changes it?

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:3 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

8:34 a.m.

Comment (by kk7ds):

You might also verify that the serial port is free by doing:

lsof | grep ttyS0

fuser /dev/ttyS0

Also, could you try CHIRP in your XP VM? If it works there, then I expect that either your serial hardware is buggy and the extra buffering introduced by VirtualBox is "helping".

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:4 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

8:54 a.m.

Comment (by Paul H <psharmor@…>):

Wow... You must have ESPN or something...lol. I do have a pair of Wouxun's, one uvd1p, and one uv2d. In both cases, the interface is done with usb-serial cable that accompanied one of them in shipping, but formatting is slightly off...

On the other hand, my usb-serial cable for my Kenny has failed, so I've just replaced with a serial. My system's serial port is standard, but on such a small form-factor, it does require a dongle.

I do have a coupla' usb-to-serial port adapters, but it'll be a bit before I can make one available for testing (coupla' hours). I'll install Chirp on xp-vm, and see if it has a similar issue, as well as play with port speeds in the meantime, as time permits.

lsof and fuser commands both returned no info.

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:5 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

8:59 a.m.

Comment (by kk7ds):

I know it shows up as a normal serial port, but I'd guess that it's not. Many embedded machines like that hang a fifo off of a GPIO pin on the CPU or chipset, which often causes problems like this.

Thanks for testing that stuff, let me know how it goes. I'll try to test our V71A at the fire station when I'm there tonight and see if it works for me.

Thanks!

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:6 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

9:31 a.m.

Comment (by Paul H <psharmor@…>):

Replying to [comment:6 kk7ds]:

...

I know it shows up as a normal serial port, but I'd guess that it's not.

Many embedded machines like that hang a fifo off of a GPIO pin on the CPU or chipset, which often causes problems like this.

...

Thanks for testing that stuff, let me know how it goes. I'll try to

test our V71A at the fire station when I'm there tonight and see if it works for me.

...

Thanks!

No bueno... Usb-to-serial adapter, pl2303-based, shows up now as /dev/ttyUSB0, chmod 777, nothing has changed. Installing on xp-vm is next step.

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:7 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

10:38 a.m.

Comment (by Paul H <psharmor@…>):

And now, I'm able to say that installed on xp-vm, the usb-to-serial was no good, but the direct serial worked fine. Not sure why. Usb-to-serial was similar / same failure, altho under xp it did NOT just hang, but rather gave an error to the effect of ...cannot scan radio...

Anyhow, hope the info's helpful!

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:8 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

10:41 a.m.

Comment (by kk7ds):

Okay, that's a good data point. I will test with a couple different machines tonight as time permits and see if I can reproduce that in some way.

Could you also try both native and usb serial in linux, but with the radio set at a lower baudrate? I think it defaults to 57600, which is pretty fast.

Thanks!

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:9 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

5:42 p.m.

Comment (by kk7ds):

I'm able to communicate very well with our TM-V71A here at the fire station. All baud rates, USB and native serial, Natty and Maverick. I'd like to hear about your tests with other baud rates and then we can start adding some debug to figure out what's going on.

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:10 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

18 May 18 May

3:04 p.m.

Comment (by psharmor@…):

My apologies... Hadn't been able to get around to the testing of baud rates and such, until just now.

Unfortunately, the problem seems to remain with newest daily, on COMPLETELY DIFFERENT system (OS still Kubuntu Natty), usb-serial adapter, etc.

I might have an issue with the serial cable for radio, and/or the radio itself, as I did perform the MARS mod... I'll check with another serial cable as soon as I'm able to borrow one.

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:11 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

3:11 p.m.

Comment (by psharmor@…):

Run from terminal, after the freeze, and given the ctrl-c to stop, the following appears:

Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/chirpui/mainapp.py", line 533, in mh self.do_download(*args) File "/usr/local/lib/python2.7/dist-packages/chirpui/mainapp.py", line 300, in do_download radio = settings.radio_class(ser) File "/usr/local/lib/python2.7/dist-packages/chirp/kenwood_live.py", line 97, in __init__ self.__id = get_id(self.pipe) File "/usr/local/lib/python2.7/dist-packages/chirp/kenwood_live.py", line 63, in get_id r = command(s, "ID") File "/usr/local/lib/python2.7/dist-packages/chirp/kenwood_live.py", line 53, in command result += s.read(8) File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 442, in read ready,_,_ = select.select([self.fd],[],[], self._timeout) KeyboardInterrupt

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:12 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

21 May 21 May

1:11 a.m.

Comment (by dzubey@…):

Here's some help. Spend the evening here working with the software trying to get it working with my TM-V71A. Here's a few notes:

In a terminal emulator, when I type ID at 9600N81 I get back "TM- V71M90200539\r". I think the code is expecting "ID TM-V71A", and trying to take the rightmost part of the string. That won't work. (tmv71a_ll.py)

Secondly, I only get a reply to the ID string once. Any other attempts are met with silence. I'm tired, but I remember at some point the code waited for a \r, which this radio gave after the ID, and that got put into get_id but it shuts up afterwards, so the code locked up.

Oh, also, my radio doesn't reply to anything over the serial port unless it's turned on into program mode, by holding down MR and PM while turning it on.

Anyways, hope that helps debug a big more. I'll join the mailing lists tomorrow.I did try the beta code, but to no avail.

-Dan N7NMD

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:13 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

CHIRP Tracker

4:30 a.m.

Comment (by kk7ds):

Hmm, that's extremely bizarre. When I program it, I do so outside of programming mode, just powered on normally.

The ID'ing behavior is also strange and not what I see (although it's probably related to being in program mode).

Note that tmv71a_ll.py is no longer used by that driver and will be removed from the tree at some point. This model is now controlled in live mode like the TM-D710, so all the code for it lives in kenwood_live.py.

-- Ticket URL: http://trac.chirp.danplanet.com/trac/ticket/91#comment:14 CHIRP http://trac.chirp.danplanet.com/trac CHIRP Development

4988

Age (days ago)

5014

Last active (days ago)

List overview

Download

14 comments

1 participants

tags (0)

participants (1)

CHIRP Tracker