<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Generally the RTF SYSTEMS cables work only with their software.</div><div><br></div><div><br></div><div style="font-size:10px">Jock A. Soutar </div><div style="font-size:10px">KC6IIH</div><div style="font-size:10px">Sent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone</div><br><br><div>-------- Original message --------</div><div>From: Daniel Sohn <sohn@sti.net> </div><div>Date:12/13/2015 4:50 PM (GMT-08:00) </div><div>To: chirp_users@intrepid.danplanet.com </div><div>Subject: [chirp_users] Cable for use w/CHIRP and iCOM ID-51A </div><div><br></div>Greetings:<br><br>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?<br><br>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.<br><br>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.<br><br>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.<br>Ditto this for Baofengs in the UV-82/UV-82HP series.<br><br>Many Thanks<br>73 & pax<br>…dan WL7COO<br><br><br>_______________________________________________<br>chirp_users mailing list<br>chirp_users@intrepid.danplanet.com<br>http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com</body>