Hello Simon 

The only thing I forgot was not to have the cable in when the Mac starts up 
I don’t know why my Mac would not see the cable 
Its  Good that you have got the Mac to  work 

Regards G1DCG


On 18 Nov 2017, at 08:03, Simon Diderrich <simon.diderrich@gmail.com> wrote:

Thanks for the reply David.

 I had to do a couple extra things like install the python runtime to get chirp actually running and then update the driver's for the prolific programming cable as it would only see the Bluetooth interface not the USB one. After that and with the full volume trick everything was good. 

Thanks
Simon

On 18 Nov 2017 6:36 PM, "David Dixon" <yattonbristol@btinternet.com> wrote:
I have a Mac mini running the same OS software as your's

I have just downloaded the update Chirp software and run it with  my BAOFENG uv-5r and works ok

As of to date I have never needed to install the drivers I just plug the Cable in and the Mac find the driver it needs
Then load the Chirp software put the radio in VFO mode turn sound almost full and click ok on the down load menu after setting it up for the type of radio I have and away it goes

Most of the posting I have seen over the years are about the cable not the right this to do with the so called nock of chips in side ( copied  )type and the radio not in the right mode to down load its easy to over looked
I have don’t it before now hope this helps

Regards David G1DCG




> On 17 Nov 2017, at 21:19, Charley Bratton <charley@bratton.net> wrote:
>
> After loading High Sierra (10.13.1) last night, my macbook running the current version of Chirp will no longer communicate with any of my radios.    Moving the same radio and cable to another Mac, also running the 20171104 version of Chirp, everything is normal.
>
> It appears that although the FTDI cable is recognized in the System Report on the USB bus, Chirp can no longer reach the serial interface on the radio.   I reloaded Python runtime module, but no improvement.   Also went to FTDI and loaded their v2.4.2 drivers for MacOS.   Also no help.
>
> Chirp’s debug log keeps saying “Radio did not respond”      My FTDI cable has LEDs.   When attached to the 10.13.1 machine, no lights are flashing when attempting to download from the radio or upload to the radio.
>
> Any suggestions for next steps?   Debug log attached.
>
> - Charley
>
> <debug.log>_______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to David  at yattonbristol@btinternet.com
> To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to diders at simon.diderrich@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to David  at yattonbristol@btinternet.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com