<p>The cable does not know and does not care which program runs on a computer it is plugged into.</p>
<p>The cable you have should work fine IF the cable hardware is supported by MAC OS.</p>
<p>In linux there are commands like lsusb and lshw which would tell what USB devicee are plugged in.</p>
<p>That is how I found out the type USB cable I had.</p>
<p>73<br>
DR<br>
N1EA</p>
<div class="gmail_quote">On Feb 10, 2018 6:08 PM, "Kell Bodholt" <<a href="mailto:KBodholt@hotmail.com">KBodholt@hotmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Looking for some specific advice for a FTDI cable for use with the Yaesu FT-2DR and Mac OS 10.13.3 on McBook Air (not running Windows on a separate partition). I have reviewed the Chirp FAQ, cable sections, Activity, etc. and have searched various websites for a specific FTDI USB cable without success as most that I have located do not have the correct connection to plug into the FT-2DR. The FT-2DR came with a USB cable, but I believe this is a cable specifically for updating the firmware and not for programing via Chirp. I'm unable to find any info on the Yaesu USB cable whether it’s a FTDI and/or Prolific type cable, but I suspect that its neither as my MacBook Air does nothing when plugged in nor does Chirp recognize any available port for uploading/receiving HT data.<br>
<br>
The FT-2DR does have a SD card, and I have event tried making a backup file of the memory channels (file name created on SD card is MEMORY.dat), taking that file and loading it into Chirp, manipulating with my local repeater info, re-save as a MEMORY.dat file, and on the FT-2DR read the file with no success.<br>
<br>
I've spent way too much time trying to figure this out, and I am giving up. So can anyone recommend a FTDI cable specific for the FT-2DR that will work with Chirp on my MacBook Air or alternatively a FTDI cable specific to the FT-2DR that will work with Chirp on a Windows 10 machine. I don't want to fuss with counterfeit cables and the headache of loading appropriate drivers.<br>
<br>
The data cable that came with the FT-2DR is a std USB on one end and the end that goes into the data port on the FT-2DR I believe is a mini usb.<br>
<br>
Thank you in advance.<br>
Svenster<br>
<br>
-----Original Message-----<br>
From: <<a href="mailto:chirp_users-bounces@intrepid.danplanet.com">chirp_users-bounces@intrepid.<wbr>danplanet.com</a>> on behalf of <<a href="mailto:chirp_users-request@intrepid.danplanet.com">chirp_users-request@intrepid.<wbr>danplanet.com</a>><br>
Reply-To: <<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a>><br>
Date: Saturday, February 10, 2018 at 12:01 PM<br>
To: <<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a>><br>
Subject: chirp_users Digest, Vol 110, Issue 4<br>
<br>
Send chirp_users mailing list submissions to<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:chirp_users-request@intrepid.danplanet.com">chirp_users-request@intrepid.<wbr>danplanet.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:chirp_users-owner@intrepid.danplanet.com">chirp_users-owner@intrepid.<wbr>danplanet.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of chirp_users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. New Daily Build (Build System)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Sat, 10 Feb 2018 00:13:48 -0800 (PST)<br>
From: Build System <<a href="mailto:donotreply@danplanet.com">donotreply@danplanet.com</a>><br>
Subject: [chirp_users] New Daily Build<br>
To: <a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
Message-ID:<br>
<<a href="mailto:874799113.100.1518250428614.JavaMail.jenkins@eagle.danplanet.com">874799113.100.1518250428614.<wbr>JavaMail.jenkins@eagle.<wbr>danplanet.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Greetings,<br>
<br>
A new daily build of CHIRP is available. This includes changes made<br>
directly to the tree yesterday, and may include additional features,<br>
bug fixes, and/or bugs. If you are interested in trying it, grab it<br>
from the following location:<br>
<br>
<a href="http://trac.chirp.danplanet.com/chirp_daily/daily-20180210" rel="noreferrer" target="_blank">http://trac.chirp.danplanet.<wbr>com/chirp_daily/daily-20180210</a><br>
<br>
<br>
A list of the changes included in this build (since the last daily)<br>
follows:<br>
<br>
Changes for Build #515<br>
[Dan Smith <<a href="mailto:dsmith@danplanet.com">dsmith@danplanet.com</a>>] Fix MURS1 radio to use validate_memory() and make edges test case tolerant<br>
<br>
This fixes one test case that should ignore memories that don't validate<br>
from the radio, and makes the MURS1 radio support said validation.<br>
<br>
This is related to #5255<br>
<br>
[Jim Unroe <<a href="mailto:rock.unroe@gmail.com">rock.unroe@gmail.com</a>>] [MURS-V1] Add Support for BTech MURS-V1<br>
<br>
This patch adds support for the BTech MURS-V1 handheld radio.<br>
<br>
#5255<br>
<br>
[Jim Unroe <<a href="mailto:rock.unroe@gmail.com">rock.unroe@gmail.com</a>>] [MURS-V1] Prepare CHIRP for BTech MURS-V1 (update baofeng_common.py)<br>
<br>
The BTech GMRS-V1 and BTech MURS-V1 are very different radios but both<br>
respond to the same "magic". This patch provides checks to make sure...<br>
<br>
1. the model selected by the user matches the physical radio model.<br>
2. the image being uploaded matches the physical radio model.<br>
<br>
related to #5255<br>
<br>
<br>
<br>
------------------------------<br>
<br>
______________________________<wbr>_________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a><br>
<br>
End of chirp_users Digest, Vol 110, Issue 4<br>
******************************<wbr>*************<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com">chirp_users@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_users</a><br>
This message was sent to D.J.J. Ring, Jr. at <a href="mailto:n1ea@arrl.net">n1ea@arrl.net</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com">chirp_users-unsubscribe@<wbr>intrepid.danplanet.com</a></blockquote></div>