[chirp_users] Yaesu FT-2DR and Mac OS 10.13.3 (High Sierra) Programming Cable Recommendation

Sat Feb 17 16:22:24 PST 2018

The cable does not know and does not care which program runs on a computer
it is plugged into.

The cable you have should work fine IF the cable hardware is supported  by
MAC OS.

In linux there are commands like lsusb and lshw which would tell what USB
devicee are plugged in.

That is how I found out the type USB cable I had.

73
DR
N1EA
On Feb 10, 2018 6:08 PM, "Kell Bodholt" <KBodholt at hotmail.com> wrote:

> 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.
>
> 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.
>
> 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.
>
> 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.
>
> Thank you in advance.
> Svenster
>
> -----Original Message-----
> From: <chirp_users-bounces at intrepid.danplanet.com> on behalf of <
> chirp_users-request at intrepid.danplanet.com>
> Reply-To: <chirp_users at intrepid.danplanet.com>
> Date: Saturday, February 10, 2018 at 12:01 PM
> To: <chirp_users at intrepid.danplanet.com>
> Subject: chirp_users Digest, Vol 110, Issue 4
>
>     Send chirp_users mailing list submissions to
>         chirp_users at intrepid.danplanet.com
>
>     To subscribe or unsubscribe via the World Wide Web, visit
>         http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>     or, via email, send a message with subject or body 'help' to
>         chirp_users-request at intrepid.danplanet.com
>
>     You can reach the person managing the list at
>         chirp_users-owner at intrepid.danplanet.com
>
>     When replying, please edit your Subject line so it is more specific
>     than "Re: Contents of chirp_users digest..."
>
>
>     Today's Topics:
>
>        1. New Daily Build (Build System)
>
>
>     ----------------------------------------------------------------------
>
>     Message: 1
>     Date: Sat, 10 Feb 2018 00:13:48 -0800 (PST)
>     From: Build System <donotreply at danplanet.com>
>     Subject: [chirp_users] New Daily Build
>     To: chirp_users at intrepid.danplanet.com
>     Message-ID:
>         <874799113.100.1518250428614.JavaMail.jenkins at eagle.danplanet.com>
>     Content-Type: text/plain; charset="utf-8"
>
>     Greetings,
>
>     A new daily build of CHIRP is available.  This includes changes made
>     directly to the tree yesterday, and may include additional features,
>     bug fixes, and/or bugs.  If you are interested in trying it, grab it
>     from the following location:
>
>       http://trac.chirp.danplanet.com/chirp_daily/daily-20180210
>
>
>     A list of the changes included in this build (since the last daily)
>     follows:
>
>     Changes for Build #515
>     [Dan Smith <dsmith at danplanet.com>] Fix MURS1 radio to use
> validate_memory() and make edges test case tolerant
>
>     This fixes one test case that should ignore memories that don't
> validate
>     from the radio, and makes the MURS1 radio support said validation.
>
>     This is related to #5255
>
>     [Jim Unroe <rock.unroe at gmail.com>] [MURS-V1] Add Support for BTech
> MURS-V1
>
>     This patch adds support for the BTech MURS-V1 handheld radio.
>
>     #5255
>
>     [Jim Unroe <rock.unroe at gmail.com>] [MURS-V1] Prepare CHIRP for BTech
> MURS-V1 (update baofeng_common.py)
>
>     The BTech GMRS-V1 and BTech MURS-V1 are very different radios but both
>     respond to the same "magic". This patch provides checks to make sure...
>
>     1. the model selected by the user matches the physical radio model.
>     2. the image being uploaded matches the physical radio model.
>
>     related to #5255
>
>
>
>     ------------------------------
>
>     _______________________________________________
>     chirp_users mailing list
>     chirp_users at intrepid.danplanet.com
>     http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>     To unsubscribe, send an email to chirp_users-unsubscribe@
> intrepid.danplanet.com
>
>     End of chirp_users Digest, Vol 110, Issue 4
>     *******************************************
>
>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to D.J.J. Ring, Jr. at n1ea at arrl.net
> To unsubscribe, send an email to chirp_users-unsubscribe@
> intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180217/d12fe8e8/attachment.html 