Uninstalling is a manual process you need to execute in the Terminalprogram of Apple. This guide describes these steps to remove the driver.The first command helps you finding the technical name of the driver,second you must unload the driver from the kernel, and the last stepfinally removes the driver from your system.
Deinstalling the PL2303 Driver¶
PL-2303 (H, HX, X chip version) Mac OS X Universal Binary Driver v1.4.0 (DMG file format), Prolific Edition For Mac OS X 10.6.x Snow Leopard (32-bit and 64-bit kernel) Added Driver Installation Manual. Arkmicro Usb To Serial Drivers For Mac Pro Arkmicro Usb To Serial Drivers For Mac PL2303 Mac OS X Driver Download Download File: Mac OS X Universal Binary Driver v1.6.1 (PKG file format). For Mac OS High Sierra (version 10.13) - see NOTE below.
step 1 - locating the driver¶
- for OS X 10.9 (or newer):
cd/Library/Extensions - for OS X 10.8 (or older):
cd/System/Library/Extensions
- Windows: PL2303 Windows Driver Download; Windows: PL2303 EEPROM Writer Program (HXD/EA/TA) Windows: PL23C3 Windows SDK (include sample code & doc) Mac OS: PL2303 Mac OS X Driver Download; Android: PL2303 Android Driver SDK Solution. PL2303TA.HXD.RA.EA.SA EOL Notice.
- PL-2303 (H, HX, X chip version) Mac OS X Universal Binary Driver v1.2.1r2 (DMG file format), Prolific Edition For MacOS 10.1 and above for PowerPC based Mac For MacOS 10.4 and above for PowePC and Intel based Mac Supports Mac OS X 10.5.
Grep the name from the command line:
ls|grep2303
step 2 - Unloading the driver¶
sudokextunload./<name>.kext
Deinstalling the CH341 Driver¶
step 1 - locating the driver¶
- for OS X 10.9 (or newer):
cd/Library/Extensions - for OS X 10.8 (or older):
cd/System/Library/Extensions
Grep the name from the command line:
Pl2303 Os X Drivers Downloads
ls|grepch341
Pl2303 Os X Driver
step 2 - Unloading the driver¶
sudokextunload./<name>.kext
In the past, manufacturers provided a serial (RS-232) interface to download data from their dive computers. Nowadays, recent systems do not have serial ports anymore, and almost all manufacturers have switched to USB interfaces. In contrast to the legacy serial interfaces, these cables require a driver to operate.
On Windows systems, you can simply install the drivers that are provided with the Windows application.
On Linux and Mac OS X, the situation is more complicated because most manufacturers do not provide a driver for non-Windows systems. However, most USB interfaces contain a serial-to-usb chip from one of the companies listed below, and you can obtain a driver from their website. Note that some Linux distributions or Mac OS X systems, already have these drivers included by default.
- FTDI (driver)
- Silicon Labs CP210x (driver)
- Prolific PL-2303 (driver)
In some cases, the generic driver from the chip manufacturer does not recognize the USB interface automatically and you need to perform some additional steps.
| Manufacturer | VID | PID |
|---|---|---|
| FTDI | 0x0403 | 0x6001 |
| Heinrichs-Weikamp | 0x0403 | 0x6001 |
| Ratio | 0x0403 | 0x6015 |
| Oceanic | 0x0403 | 0xF460 |
| Suunto | 0x0403 | 0xF680 |
| Suunto (Smartinterface) | 0x0403 | 0x6001 ? 0x6010 ? 0x6011 ? |
| Cressi (leonardo) | 0x0403 | 0x87D0 |
| Silicon Labs | 0x10C4 | 0xEA60 |
| Suunto (CustomIdea) | 0x10C4 | 0xEA60 |
| Mares | 0x10C4 | 0xEA60 |
| Prolific | 0x067B | 0x2303 |
| Reefnet | 0x067B | 0x2303 |
| Mares (Nemo Sport) | 0x04B8 | 0x0521 |
| Cressi | 0x04B8 | 0x0521 |
| Zeagle | 0x04B8 | 0x0522 |
| Freescale Semiconductor | ? | ? |
| Mares (Icon HD) | 0xFFFF | 0x0005 |
Suunto
The FTDI driver is included in the Linux kernel. The device node (usually /dev/ttyUSBx) will appear automatically once you plug in the USB cable.
Pelagic (Oceanic, ...)
The standard FDTI driver works just fine, but the custom Oceanic VID/PID (Vendor ID/Product ID) is not recognized automatically.
Linux
You need to load the driver manually, by executing the following command (as root):
Pl2303 Os X Drivers Windows 10
To make the change permanent, you can add the parameters to the file /etc/modprobe.d/options (or modify the source code and recompile the driver, but that is beyond the scope of this document):
An alternative approach for binding the Oceanic VID/PID to the FTDI driver is executing the following command (as root):
Mac OS X
Note: The latest FTDI driver (version 2.2.14 or higher) recognizes the Oceanic cable automatically and the procedure below is not necessary anymore.
Follow these steps to make the FTDI driver recognize the Oceanic cable:
- Locate the file /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist
- Alter the permissions to make it writeable, but BE SURE TO SET THEM BACK EXACTLY THE SAME AFTER YOU'RE DONE
- Open it, and search for 'Oceanic'. You'll find a Pelagic Oceanic entry (which is apparently something else). Change the idProduct from 62566 to 62560.
- Save, quit and restore the permissions.
- Reload the driver by running the following commands (as root):
Seiko (Cressi, Zeagle, ...)
The standard Prolific driver works just fine, but the custom Cressi VID/PID (Vendor ID/Product ID) is not recognized automatically.
Windows
Update: More detailed instructions are available here.
The Cressi software installs a USB only driver that does not provide a serial interface. Follow this procedure to modify the generic prolific driver to work with the Cressi interface.
- Download and install the generic pl2303 driver from the Prolific website.
- After installing the driver, a new oemXX.inf file (with XX being the last number available) will appear under c:windowsinf.
- Open this file and substitute the original vid/pid (067b 2303) with the 'new' ones (04b8 0521).
- After saving the file, the interface gets recognized as a standard pl2303 usb-to-serial interface.
Pl2303 Mac Os X Driver Download
Note that it's not possible to have two drivers installed for the same device. You'll have to uninstall the usb only driver first. You can always re-install it again.
Linux
Use the Oceanic procedure, with this command (as root):
Replace PID with 0521 (cressi) or 0522 (zeagle).
Mac OS X
Update: I made a bash script to automate the driverpatching. Download the script, start a terminal and runthe command: sudo bash seiko.sh The sudo command is to runthe script with root priviliges. You'll have to enter your password whenasked.
Use the Pelagic procedure.
The Prolific driver you need to modify is named 'ProlificUsbSerial.kext'. Search for the keys idVendor and idProduct, and change the idVendor value from 1659 to 1208, and the idProduct value from 8963 to 1313 (cressi and mares) or 1314 (zeagle).