In case your USB to Serial is not working, you can try the followingsteps find and solve the problem.
USB to RS232 Cable(5 Feet),Anbear USB 2.0 to Serial Cable DB9 Converter Adapter with PL2303 Chipset for Windows 10, 8.1, 8, 7, Vista, XP, 2000, Linux and Mac OS X 10.6 and Above 4.2 out of 5 stars 113. Sabrent USB 2.0 to Serial (9-Pin) DB-9 RS-232 Converter Cable, Prolific Chipset, - HEXNUTS -, Windows 10/8.1/8/7/VISTA/XP, Mac OS X 10.6 and Above 2.5 Feet (CB-DB9P) TRENDnet USB to Serial 9-Pin Converter Cable, TU-S9, Connect a RS-232 Serial Device to a USB 2.0 Port, Supports Windows & Mac, Supports USB 1.1, USB 2.0, USB 3.0, 25 Inch Cable. May 03, 2016 USB to Serial for Mac OS X. The driver for the cable can be downloaded from the Prolific website, however we have found an open source driver, which does the job and more over gives some better performance. We recommend you download the open source driver. After you have installed the driver, connect your cable to any of your free USB ports. When you connect a device to you Mac, OS X searches for the appropriate driver via a matching algorithm. In case of a USB device, OS X uses the vendor id and product id of the device to load the right driver. However, if multiple drivers are registered for a certain device, the. The Keyspan USB Adapter 1.2 driver can be downloaded from the Keyspan Web site - it requires Mac OS X 10.1 or higher. Keyspan's USB Serial Adapter offers a way to connect serial devices to USB ports.
0. Is the device connected and recognized¶
The first step is to actually check if the USB serial device isconnected to your mac and recognized by OS X as USB Device.
Make sure you have all cables plugged in and open System Info toverify your device is connected:
![Mac Mac](/uploads/1/1/9/8/119867797/570004470.jpg)
Alternatively, you can use the command line to list all USB devicesconnected to your mac:
This check is not dependent on any driver, and only verifies if OS X recognizes the device at USB level.If the device doesn’t show up, it is either a broken cable or broken chip.
Make sure you use a fully wired micro-USB cable!
Since the introduction of micro-USB, some USB cables are not fullywired. You might have a charge-only cable. In that case the device willnever work. You can check it, when you connect the device via this cableit will never pop-up in the lists above.
1. Remove Conflicting Driver¶
When you connect a device to you Mac, OS X searches for theappropriate driver via a matching algorithm. In case of a USB device,OS X uses the vendor id and product id of the device to load the rightdriver. However, if multiple drivers are registered for a certaindevice, the matching algorithm becomes arbitrary. You will confrontedwith not working devices or strange behavior.
In the newest 3.0+ drivers we avoid this by setting a higher priorityin the matching results, however, it might be better to have noconflicts at all.
To check which drivers are installed, run the following command in theterminal application:
This commands detects installed drivers. It is necessary to have adminrights, so the sudo command is necessary. Alternatively you can list thedirectories
/Library/Extensions
and /System/Library/Extensions
,and search for the installed kexts.If you install our drivers then they should be installed in one of thefollowing directories:
- /Library/Extensions/osx-ch341.kext
- /Library/Extensions/osx-pl2303.kext
- /Library/Extensions/osx-cp2102.kext
For OS X 10.8 and earlier
- /System/Library/Extensions/osx-ch341.kext
- /System/Library/Extensions/osx-pl2303.kext
When no conflicting drivers are installed, the output on OS X 10.9+should look like:
In case you have found conflicting drivers, like theProlificUsbSerial.kext (Prolific) or usb.kext (Winchiphead), you shouldremove them. Execute the following steps in the terminal:
Usb To Serial Driver
cd/<_path_where_conflicting_driver_is_located_>/
sudokextunload./<name>.kext
sudorm-rf<name>.kext
![Mac Mac](/uploads/1/1/9/8/119867797/341594873.jpg)
The kextunload command may fail if the driver is not loaded. It may benecessary to reboot the mac to be sure the kexts are not loaded into thekernel.
2. Test If the Driver is Loaded¶
Next step is to check if the driver is loaded. Connect your USB toserial cable to your mac and execute the following command in Terminal:
sudokextstat|greprepleo
If you don’t see a driver, please make sure it is loaded by using thecommands:
cd/library/extensions/
sudokextload ./<name>.kext
Alternatively, rebooting your mac will also load the drivers. If youdon’t see the driver, it is possible you don’t own a supported device,or the driver is not loaded properly. Try to load the driver with theverbose command:
sudokextutil-v6 ./<nameofkext>.kext
in the directory/library/extensions
, inspect the output of sudodmesg
andcontact us via support@mac-usb-serial.com for further assistance.Since OS X High Sierra, you need to explicitly allow the drivers in the Security & Privacy pane of System Preferences.You will get a dialog System Extension Blocked during installation, which alerts you to approve the driver.
In case the
sudokextutil-v6 ./<nameofkext>.kext
command shows the line:You still need to approve the driver. This approval UI is only present in the Security & Privacy preferences panefor 30 minutes after the alert.The gatekeeper pane in System Preferences looks like:
Our Team Identifier for the gatekeeper is: C3V2MXS8TG (BJA Electronics). When you have approved the driver, you mightneed to reboot your machine. Click with a normal mouse, without emulating software. Apple is strict on this.
Until you approved the KEXT, future load attempts will cause the approval button in the Security & Privacy pane to reappear but will not triggeranother user alert. You can trigger it by these commands:
sudospctl--add--label'Repleo'
sudospctl--enable--label'Repleo'
You can verify the driver is allowed by:
In case this doesnot work, you can try to trigger the gatekeeper by loading the driver via kextutil, or rebooting your mac.
3. Test If the Device is Recognized¶
When the kext is loaded properly, it should instantiate the .cu and .ttyhandles. You can verify this using the terminal with the following tocommands:
sudodmesg|greprepleo
ls/dev|grepRepleo
The log files (via dmesg) shows is the driver is correctly allocated.The ls command shows if the .cu and .tty are loaded. If an erroroccurs it is also visible via the dmesg. Please contact us in case you see an error,and send us the dmesg output with this error for further assistance.
4. Test the Serial Interface with a Loopback¶
The last test is to verify the driver is really able to send and/orreceive data. Connect the RxD and TxD pin of the RS-233 connector, thiswill create a loopback. Any character transmitted from your Mac shouldalso be echoed into the terminal. Use a simple tool like CoolTerm to verify if data is transmitted.
In case no data is received, it is important that is not a hardwarefailure. Please test the setup using Windows or Linux to ensure thehardware is operating correctly. If the hardware is not the problem, youcan contact us for assistance.
Please include all the steps you did to determine the cause of theproblem.
USB to Serial for Mac OS X
The driver for the cable can be downloaded from the Prolific website, however we have found an open source driver, which does the job and more over gives some better performance. We recommend you download the open source driver.
After you have installed the driver, connect your cable to any of your free USB ports. Mac OS X will automatically create a serial device, which can be found in /dev. Start a terminal session and list all available serial (or tty) devices available. Type the following:
ls -l /dev/tty*
Find the entry that is referring to your cable. Typically this should look similar to:
Usb To Serial Drivers For Mac Os X 10.10
/dev/tty.PL2303-0002600D
Now that we have identified our new serial device, we can start connecting to a radio. Most people will use a Terminal Emulator, but as most of these programs were built pre-Leopard, you may find some difficulties running them on new(er) Mac hardware. We simply use the built-in screen program on Mac OS. So in the same terminal window, simply type:
Usb Driver Download For Mac
screen /dev/tty.PL2303-0002600D 57600
Update Mac Usb Drivers
You can obviously change the baud rate or any other options to what you need to connect to your specific device. Ten-Tec Omni-VII uses a baud rate of 57600. We did notice that every time you connect and re-connect the cable’s tty device id changes.