<p dir="ltr">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. </p>
<p dir="ltr">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. </p>
<p dir="ltr">Good thing too... The frustrations and technical details that you discuss in this thread are beyond me. Good luck with that... </p>
<p dir="ltr">I will offer that <i>cable quality</i> has popped up in various threads as a likely culprit in the case of up/down-load fails<br></p>
<p dir="ltr">Keith</p>
<div class="gmail_quote">On Jul 24, 2016 23:56, "CN85rq" <<a href="mailto:chirp-info@aberle.net">chirp-info@aberle.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ken:<br>
Thanks for your suggestions. Since both radios are mobiles with serial<br>
ports, the PTT isn't an issue. I was testing with both USB-to-serial<br>
cables (with chips) and serial-to-serial cables (no chips). The<br>
CheckChipVersion appears to be Windoze-only (an OS I haven't had in over<br>
a decade), and I don't see an equivalent linux tool.<br>
<br>
Tom:<br>
I appreciate you pointing me in the right direction on breaking the<br>
problem in half, and the "ID" command for the TM-V71. I moved over to<br>
testing with a 3rd computer, one known to connect with my Kantronics<br>
9612. Using the serial port monitor in Outpost PM and the linux minicom<br>
utility I was able to isolate issues, solve part of the problem, and<br>
better characterize the remaining difficulties.<br>
<br>
All:<br>
The dual-port MCS9865-based serial card on the Gigabyte GA-MA790X-UD4P<br>
motherboard uses /dev/ttyS1 and /dev/ttyS2. The USB-to-serial cable<br>
uses /dev/USB0 on both the Gigabyte motherboard and the Raspberry Pi.<br>
Both USB-to-serial cables (FTDI and unknown) and the Kenwood PG-5G PC<br>
Serial Programming Cable all work. Note to self: In order to make<br>
problem isolation easier, clearly mark the three special APC 940-0024C<br>
cables so they don't get mixed in with the other serial cables.<br>
<br>
So, chirp works with the Kenwood TM-V71 using both a straight serial<br>
cable and the both USB-to-serial cables. Neither chirp, minicom, nor<br>
the serial port monitor in Outpost PM will communicate with the Alinco<br>
DR-235 MkIII. In fact, when I put the mini-tester in line on the serial<br>
cable, there is no signal (neither a green nor a red LED lit) on the<br>
Receive Data line. This is true for all three computers using both<br>
cable types.<br>
<br>
Is a special cable needed for the Alinco DR-235 to work with chirp?<br>
<br>
<br>
Tom Hayward wrote on 07/24/2016 11:19 AM:<br>
><br>
> You might try removing Chirp from the equation and test just the<br>
> serial port on the TM-V71. First, note the rate set in menu 519,<br>
> PC.SPD. Then launch a terminal emulator at this rate. Type ID and hit<br>
> enter. You should get the model number of the radio printed to your<br>
> console. If not, you've got a problem with your computer/USB serial<br>
> port, cable, or the radio's serial port.<br>
><br>
> If you do get a response, move on to Chirp. Use only the latest daily<br>
> build, available on the PPA or here:<br>
> <a href="http://trac.chirp.danplanet.com/chirp_daily/LATEST/" rel="noreferrer" target="_blank">http://trac.chirp.danplanet.com/chirp_daily/LATEST/</a><br>
><br>
> Tom KD7LXL<br>
<br>
<br>
Ken Cone wrote on 07/24/2016 10:58 AM:<br>
> Hello,<br>
> In my recent experience programming an Yaesu FT60R, two issues popped up:<br>
> 1) finding the correct driver for the cable chipset, and 2) holding the PTT<br>
> button long enough.<br>
> The chipset driver information was here:<br>
> <a href="http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41" rel="noreferrer" target="_blank">http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41</a><br>
><br>
> About half way down the page, in red is a link to an app that identified<br>
> the Prolific the chipset. Other chipset manufacturers may have similar<br>
> tools.<br>
> "Run PL2303 CheckChipVersion tool..." This helped tremendously in<br>
> identifying the correct driver.<br>
> Holding the PTT button long enough came from page 65 of the FT-60R manual,<br>
> in the section on Cloning. After resolving these two issues, I was able to<br>
> download memory contents to CHiRP, edit, and upload back to the HT.<br>
><br>
> Hope this helps.<br>
> 73,<br>
> Ken<br>
> KI7EIH<br>
><br>
><br>
> Ken Cone<br>
> <a href="mailto:kencone@gmail.com">kencone@gmail.com</a><br>
> KI7EIH<br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Keith Murlless at <a href="mailto:kmurlless@gmail.com">kmurlless@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
</blockquote></div>