[chirp_users] Cable for use w/CHIRP and iCOM ID-51A
kc6iih at aol.com
Sun Dec 13 17:20:04 PST 2015
Generally the RTF SYSTEMS cables work only with their software.
Jock A. Soutar
Sent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone
<div>-------- Original message --------</div><div>From: Daniel Sohn <sohn at sti.net> </div><div>Date:12/13/2015 4:50 PM (GMT-08:00) </div><div>To: chirp_users at intrepid.danplanet.com </div><div>Subject: [chirp_users] Cable for use w/CHIRP and iCOM ID-51A </div><div>
Can anyone point me at the correct cable to buy, build or modify so that I can ** using OS X 10.11** (happens to be .2 now) program iCom ID-51A HTs with CHIRP?
I’ve searched some and tried the RT Systems generic Apple FDLI update to no effect wrt to using the RT System cable w/OS X.
I have several other options for programming ID-51s however it would be convenient if I could set up their non-DStar Freqs in somewhat similar arrangements to the many Baoefengs that are popping up like … well you know what, to facilitate CommT support for local ARES/RACES units. Goal is to create libraries of .csv files for various types of local & regional support/event/agency combinations and efficiently have identical Channel names or #s to expedite implementation of IACs in the field.
If anyone knows what would also work as an actual radio to radio ‘cloning’ cable for the ID-51s I’m interested in that too.
Ditto this for Baofengs in the UV-82/UV-82HP series.
73 & pax
chirp_users mailing list
chirp_users at intrepid.danplanet.com
To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chirp_users