[chirp_users] Mac to Vaesu communication problem
I am using a Mac with OS 10.6.8. I want to use Chirp to communicate with a Yaesu VX-6R.
I have a USB cable from RT Systems specifically designated for the Yaesu. I installed the driver and my computer says it recognizes the USB cable.
I installed a version of Chirp and it does not crash. When I try to download from my radio using Command-D, I get a window for selecting the Port, Vendor, and model. Under the choice for Port, I get two options: "/dev/cu.Bluetooth-PDA-Sync" and "/dev/cu.Bluetooth-Modem". When I try with "/dev/cu.Bluetooth-Modem", it immediately tells me it cannot open the port. When I try with " /dev/cu.Bluetooth-PDA-Sync", it tries to do something and then errors out, saying: "Failed to communicate with the radio."
Any ideas on what is wrong or what I can do to fix it?
I also use a Mac and have a Yeasu 7900R & FT60R both communicate well, but I did have to install the RT driver which then shows an additional com port. I did find in my case, I think because of the lighting ports and using a lightening to USB connector cable I have to use 2 different physical ports for the 2 different radios. On the RTsystems inc website click on support then on the right select Yeasu Prolific driver
Good luck, Mary KM6RMA
Sent from my iPad
On Jul 9, 2018, at 1:51 PM, Bruce Warren bruce@sendlgm.com wrote:
I am using a Mac with OS 10.6.8. I want to use Chirp to communicate with a Yaesu VX-6R.
I have a USB cable from RT Systems specifically designated for the Yaesu. I installed the driver and my computer says it recognizes the USB cable.
I installed a version of Chirp and it does not crash. When I try to download from my radio using Command-D, I get a window for selecting the Port, Vendor, and model. Under the choice for Port, I get two options: "/dev/cu.Bluetooth-PDA-Sync" and "/dev/cu.Bluetooth-Modem". When I try with "/dev/cu.Bluetooth-Modem", it immediately tells me it cannot open the port. When I try with " /dev/cu.Bluetooth-PDA-Sync", it tries to do something and then errors out, saying: "Failed to communicate with the radio."
Any ideas on what is wrong or what I can do to fix it? _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Mary at megraff@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Hi Bruce The two choices your seeing in chirp is NOT the driver for your cable. The driver is, either not installed or not recognized by your version of Mac OS. 10.6 I believe is snow Leopard. You may need to go to the Prolific web site and download an earlier version of your OS.
Randy VE3JPU@me.com
On Jul 9, 2018, at 6:04 PM, Mary Graff megraff@gmail.com wrote:
I also use a Mac and have a Yeasu 7900R & FT60R both communicate well, but I did have to install the RT driver which then shows an additional com port. I did find in my case, I think because of the lighting ports and using a lightening to USB connector cable I have to use 2 different physical ports for the 2 different radios. On the RTsystems inc website click on support then on the right select Yeasu Prolific driver
Good luck, Mary KM6RMA
Sent from my iPad
On Jul 9, 2018, at 1:51 PM, Bruce Warren bruce@sendlgm.com wrote:
I am using a Mac with OS 10.6.8. I want to use Chirp to communicate with a Yaesu VX-6R.
I have a USB cable from RT Systems specifically designated for the Yaesu. I installed the driver and my computer says it recognizes the USB cable.
I installed a version of Chirp and it does not crash. When I try to download from my radio using Command-D, I get a window for selecting the Port, Vendor, and model. Under the choice for Port, I get two options: "/dev/cu.Bluetooth-PDA-Sync" and "/dev/cu.Bluetooth-Modem". When I try with "/dev/cu.Bluetooth-Modem", it immediately tells me it cannot open the port. When I try with " /dev/cu.Bluetooth-PDA-Sync", it tries to do something and then errors out, saying: "Failed to communicate with the radio."
Any ideas on what is wrong or what I can do to fix it? _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Mary at megraff@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 Skid at ve3jpu@me.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
This covers most, if not all OSX USB-Serial Drivers.
The most important thing to realise that from 10.9 on Apple required signed drivers. All chips needed new drivers from then on. It does not always mean that the modern driver wouldn’t work on an older OS, it depends on how it was written.
More notes at the bottom. If I forgot something just ask!
Ken –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– FTDI Drivers FT232R USB UART (Best in class) All drivers available here: http://www.ftdichip.com/Drivers/VCP.htm For Mac OSX you must choose the right one, older 10.6 - 10.8 or 10.9 and newer
If you have one, this is what you'll see. (numeric suffix varies): Oasis:Test kfs$ ls -l /dev/tty.* crw-rw-rw- 1 root wheel 21, 0 4 Jul 10:33 /dev/tty.Bluetooth-Incoming-Port crw-rw-rw- 1 root wheel 21, 22 10 Jul 17:06 /dev/tty.usbserial-A50285BI
VendorID/ProductID: 0x0403/0x6001 (Future Technology Devices International Limited)
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Silicon Labs CP210x USB to UART Bridge Drivers for all OS are available here: https://www.silabs.com/products/development-tools/software/usb-to-uart-bridg...
If you have one, this is what you'll see: $ ls -l /dev/tty.* crw-rw-rw- 1 root wheel 21, 0 4 Jul 10:33 /dev/tty.Bluetooth-Incoming-Port crw-rw-rw- 1 root wheel 21, 10 10 Jul 16:18 /dev/tty.SLAB_USBtoUART
VendorID/ProductID: 0x10C4/0xEA60 (Silicon Laboratories, Inc.)
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Prolific Drivers All OS drivers listed here: http://www.prolific.com.tw/US/supportDownload.aspx?FileType=56&FileID=13...
10.9 - 10.13 http://www.prolific.com.tw/admin/Technology/GetFile.ashx?fileID=352 10.6 - 10.8 http://www.prolific.com.tw/admin/Technology/GetFile.ashx?fileID=238
Waring: There are fake Prolific chips around and their drivers now detect them and refuse to work!
If you have a prolific adaptor plugged in you will see this when you type: Oasis:Test kfs$ ls -l /dev/tty.* crw-rw-rw- 1 root wheel 21, 0 4 Jul 10:33 /dev/tty.Bluetooth-Incoming-Port crw-rw-rw- 1 root wheel 21, 12 10 Jul 16:58 /dev/tty.usbserial
VendorID/ProductID: 0x067B/0x2303 (Prolific Technology, Inc.)
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– WinChipHead (Cheap Chinese but works ok) CH340 and CH341
Difficult to find drivers originally but I found signed drivers here: https://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-...
Older unsigned drivers available from their website: http://www.wch.cn/downloads/file/178.html Goodluck understanding Chinese though!
If you have one of these plugged in with the correct driver, you'll see this (numeric suffix varies: ls -l /dev/tty.* crw-rw-rw- 1 root wheel 21, 0 4 Jul 10:33 /dev/tty.Bluetooth-Incoming-Port crw-rw-rw- 1 root wheel 21, 6 10 Jul 16:11 /dev/tty.wchusbserial1420 crw-rw-rw- 1 root wheel 21, 20 10 Jul 17:05 /dev/tty.wchusbserial210
VendorID/ProductID: 0x1A86/0x7523 (Prolific if known)
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Notes 1. These device listings were produced in a terminal which everyone one has in /Applications/Utilities. 2. Ignore anything related to Bluetooth! These are default entries setup to make it easy to communicate with old Feature Phones that have their own USB Serial interfaces 3. There is nothing at all stopping you from installing all these drivers at the same time. Only required ones will load. If you are missing the driver, it will not show! 4. From 10.9 Apple required drivers that were signed and things have gotten tighter since. Nowdays, thirdparty drivers can only be installed in "/Library/Extensions" 5. If you have installed a driver and its not loading, check the system log. It could be that you got an older unsigned driver and it is rejected. Ask for assistance.
On 9 Jul 2018, at 23:04, Mary Graff megraff@gmail.com wrote:
I also use a Mac and have a Yeasu 7900R & FT60R both communicate well, but I did have to install the RT driver which then shows an additional com port. I did find in my case, I think because of the lighting ports and using a lightening to USB connector cable I have to use 2 different physical ports for the 2 different radios. On the RTsystems inc website click on support then on the right select Yeasu Prolific driver
Good luck, Mary KM6RMA
Sent from my iPad
On Jul 9, 2018, at 1:51 PM, Bruce Warren <bruce@sendlgm.com mailto:bruce@sendlgm.com> wrote:
I am using a Mac with OS 10.6.8. I want to use Chirp to communicate with a Yaesu VX-6R.
I have a USB cable from RT Systems specifically designated for the Yaesu. I installed the driver and my computer says it recognizes the USB cable.
I installed a version of Chirp and it does not crash. When I try to download from my radio using Command-D, I get a window for selecting the Port, Vendor, and model. Under the choice for Port, I get two options: "/dev/cu.Bluetooth-PDA-Sync" and "/dev/cu.Bluetooth-Modem". When I try with "/dev/cu.Bluetooth-Modem", it immediately tells me it cannot open the port. When I try with " /dev/cu.Bluetooth-PDA-Sync", it tries to do something and then errors out, saying: "Failed to communicate with the radio."
Any ideas on what is wrong or what I can do to fix it? _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Mary at megraff@gmail.com mailto:megraff@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Bitfarmer at ei7dkb@logicatrium.com mailto:ei7dkb@logicatrium.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
participants (4)
-
Bruce Warren -
Ken FitzGerald-Smith -
Mary Graff -
Randy Elliott