[chirp_users] No response from radio, TM-V71 and DR-235, Debian

[guncrafter]

Sent from my Samsung Galaxy smartphone.


-------- Original message --------
From: Keith Murlless <kmurlless at gmail.com> 
Date:07-25-2016  6:08 AM  (GMT-05:00) 
To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com> 
Cc:  
Subject: Re: [chirp_users] No response from radio, TM-V71 and DR-235, Debian 

At the risk of offending our highly technical brethren,  I'd like to compliment CHIRP for producing an excellent "plug - n-play" version for Mac. 

Honestly, aside from having to maintain separate files for each Baofeng firmware set, my experience in up/down-loading from Baofeng to Mac,  via CHIRP, has truly been just that easy.

Good thing too... The frustrations and technical details that you discuss in this thread are beyond me.  Good luck with that...

I will offer that cable quality has popped up in various threads as a likely culprit in the case of up/down-load fails

Keith

On Jul 24, 2016 23:56, "CN85rq" <chirp-info at aberle.net> wrote:
Ken:
Thanks for your suggestions.  Since both radios are mobiles with serial
ports, the PTT isn't an issue.  I was testing with both USB-to-serial
cables (with chips) and serial-to-serial cables (no chips).  The
CheckChipVersion appears to be Windoze-only (an OS I haven't had in over
a decade), and I don't see an equivalent linux tool.

Tom:
I appreciate you pointing me in the right direction on breaking the
problem in half, and the "ID" command for the TM-V71.  I moved over to
testing with a 3rd computer, one known to connect with my Kantronics
9612.  Using the serial port monitor in Outpost PM and the linux minicom
utility I was able to isolate issues, solve part of the problem, and
better characterize the remaining difficulties.

All:
The dual-port MCS9865-based serial card on the Gigabyte GA-MA790X-UD4P
motherboard uses /dev/ttyS1 and /dev/ttyS2.  The USB-to-serial cable
uses /dev/USB0 on both the Gigabyte motherboard and the Raspberry Pi.
Both USB-to-serial cables (FTDI and unknown) and the Kenwood PG-5G PC
Serial Programming Cable all work.  Note to self: In order to make
problem isolation easier, clearly mark the three special APC 940-0024C
cables so they don't get mixed in with the other serial cables.

So, chirp works with the Kenwood TM-V71 using both a straight serial
cable and the both USB-to-serial cables.  Neither chirp, minicom, nor
the serial port monitor in Outpost PM will communicate with the Alinco
DR-235 MkIII.  In fact, when I put the mini-tester in line on the serial
cable, there is no signal (neither a green nor a red LED lit) on the
Receive Data line.  This is true for all three computers using both
cable types.

Is a special cable needed for the Alinco DR-235 to work with chirp?


Tom Hayward wrote on 07/24/2016 11:19 AM:
>
> You might try removing Chirp from the equation and test just the
> serial port on the TM-V71. First, note the rate set in menu 519,
> PC.SPD. Then launch a terminal emulator at this rate. Type ID and hit
> enter. You should get the model number of the radio printed to your
> console. If not, you've got a problem with your computer/USB serial
> port, cable, or the radio's serial port.
>
> If you do get a response, move on to Chirp. Use only the latest daily
> build, available on the PPA or here:
> http://trac.chirp.danplanet.com/chirp_daily/LATEST/
>
> Tom KD7LXL


Ken Cone wrote on 07/24/2016 10:58 AM:
> Hello,
> In my recent experience programming an Yaesu FT60R, two issues popped up:
> 1) finding the correct driver for the cable chipset, and 2) holding the PTT
> button long enough.
> The chipset driver information was here:
> http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41
>
> About half way down the page, in red is a link to an app that identified
> the Prolific the chipset.  Other chipset manufacturers may have similar
> tools.
> "Run PL2303 CheckChipVersion tool..."  This helped tremendously in
> identifying the correct driver.
> Holding the PTT button long enough came from page 65 of the FT-60R manual,
> in the section on Cloning.  After resolving these two issues, I was able to
> download memory contents to CHiRP, edit, and upload back to the HT.
>
> Hope this helps.
> 73,
> Ken
> KI7EIH
>
>
> Ken Cone
> kencone at gmail.com
> KI7EIH
_______________________________________________
chirp_users mailing list
chirp_users at intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Keith Murlless at kmurlless at gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20160725/3b9a85e8/attachment.html