<div dir="ltr">I'm thinking it's simpler than Apple messing with the driver. Have you tried using the commandline to check what is printed when you plug in the cable?<div><br></div><div>unplug the cable, open terminal and type </div><div><br></div><div>sudo dmesg</div><div><br></div><div>plug the cable back in, and type the same again.</div><div><br></div><div>It should tell you the cable was detected, the driver was loaded, and what /dev node it's associated with.</div><div><br></div><div>IF you don't get a node name, then you can start barking up the driver tree.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 5, 2019 at 10:23 PM Jim Unroe <<a href="mailto:rock.unroe@gmail.com">rock.unroe@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Sep 5, 2019 at 9:58 PM Ted Smith <<a href="mailto:info@pikespeakparagliding.com" target="_blank">info@pikespeakparagliding.com</a>> wrote:<br>
><br>
><br>
><br>
> Hi,<br>
> You guys probably get this all the time, but now it’s my turn.<br>
> I have been using CHIRP with my Baofeng radios for the past couple of years with no problem.<br>
> I recently had to upgrade my Mac OS to 10.11. Now I can’t get CHIRP to talk to my radios.<br>
> I assume it is because the drivers are wrong or something. I have tried downloading the Prolific drivers. No luck so far.<br>
> There used to be a pl2303 option on the drop down menu when I was uploading/ downloading. It isn’t there anymore.<br>
> I’m not sure what to do at this point.<br>
> Please help, I’m begging.<br>
> Thanks,<br>
> -Ted<br>
<br>
Hi Ted,<br>
<br>
My son-in-law gave me a MacBook Air a couple of months ago. I'm not a<br>
Mac user so I decided that my first project would be to see if I could<br>
get CHIRP running on it.<br>
<br>
Most of my programming cables were furnished with the radios so<br>
virtually every one of the freebies has a counterfeit USB-to-TTL chip<br>
in it. So I knew up front that using device driver from the Prolific<br>
website was out of the question. I also have a homebrew programming<br>
cable that has a Silicon Labs chip and a few programming cables with<br>
FTDI chips.<br>
<br>
So what I did was to purchase and install a 3rd party device driver<br>
from Repleo. It works for programming cables with Prolific PL2303<br>
chips, WCH CH341 chips and Silicon Labs CP2102 chips. They want 7.90<br>
euros for it which at the time I bought it came to $9.11 USD.<br>
<br>
<a href="https://www.mac-usb-serial.com/" rel="noreferrer" target="_blank">https://www.mac-usb-serial.com/</a><br>
<br>
I used the native Apple driver for my programming cables with FTDI chips.<br>
<br>
Jim KC9HI<br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">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 Chance at <a href="mailto:chance.fulton@gmail.com" target="_blank">chance.fulton@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Chance Fulton<br><a href="mailto:chance.fulton@gmail.com" target="_blank">chance.fulton@gmail.com</a><br>810.441.5795</div>