Obd2 Serial Cable Driver
For most of these operating systems two types of driver are available: Virtual COM Port (VCP) drivers and direct (D2XX) drivers. The VCP driver emulates a standard PC serial port such that the USB device may be communicated with as a standard RS232 device. The D2XX driver allows direct access to a USB device via a DLL interface.
Obd2 Serial Cable Driver
This driver is for the CB-FTDI USB to Serial cable (CSI Part# 17394 - Black Cable). Support is for Windows XP/Vista/7/8/10 32 & 64 bit. This driver is not compatible with the SC-USB Interface.
Older Ross-Tech RS-232 Serial interfaces can be set to power up as "dumb K-Line pass through" interfaces. This allowed those old Serial interfaces to be compatible with a wide variety of third-party applications which expect a "K-line pass-through" serial interface. However, our USB interfaces present additional challenges. Early in their development, we found a number of technical advantages to using a "direct" USB driver which bypasses the Windows Serial drivers entirely. Hence the USB drivers that ship with VCDS do not emulate a serial COM port and cannot be used with applications that expect to communicate via a serial port. NOTE: The following applies to our legacy USB interfaces (HEX-USB, KII-USB and HEX-USB+CAN). It does NOT apply to our current HEX-V2 or HEX-NET interfaces. These new interfaces do not use a USB UART chip and cannot be be used for "dumb K-line pass-through"!
In order to facilitate the use of third-party applications which expect to communicate with a serial interface, drivers that emulate a COM port are available. However, anyone thinking about using them needs to be aware of the following points:
The cable is two feet long. If you are looking for a longer USB to Serial adapter add a USB extension cable or a standard serial cable to your order. If you don't want any attached cable, check out the Plug-in version.
If you have found the file in the path, you will need to run each of the following commands in the CLI/Terminal to remove old CH340 drivers. In this case, there was only the usbserial.kext file but it does not hurt to run both commands. Make sure to have administrative privileges to ensure that the drivers are removed.
Check if the old drivers were removed in the paths by using the ls command with your respective OS version. You will notice that the *.kext file is removed from the respective paths. In this case, the usbserial.kext was removed from Mac OSX High Sierra.
There are some reported cases of serial communication failure when using the factory drivers in Linux. If you encounter this problem, you can try installing patched drivers as explained in this forum post. Here are the steps (to run in the command line):
If you installed the drivers for the CH340 on your computer but have issues connecting via serial terminal or uploading code using the Arduino IDE, there may be an issue with your user settings preventing you from using the CH340. You may receive an avrdude: ser_open(): can't open device error similar to the output shown below.
If you are uploading to certain boards like the Apollo3 on the Artemis development boards with fast baud rates, there are some platforms (Linux flavors) where the standard CH340 USB to serial drivers don't operate well at speeds higher than 115200. So if you run into upload problems, consider reducing the upload speed. For more information about upload issues, see this forum post and consider upgrading with these drivers for Mac OSX or these for Linux.
Most of the time, when you install Arduino on Mac OS X, the drivers are installed automatically. However, if there was a problem with the installation and you don't see any options that include 'usbserial' under the 'Tools -> Serial Port' menu, then you will need to install the drivers. You may also need to install the full FTDI drivers if you are running OSX 10.10 or later. The factory drivers are not complete.
Recent versions of the linux kernel include support for the CP2102 USB-to-UART Bridge Controller as part of the usb-serial driver, so your Pololu CP2102 should work right out of the box. We have verified that the CP2102 works with Ubuntu versions 7.04 and 8.04. If you experience any problems, we recommend you upgrade to the most recent version of your distribution.
The ICUSB232DB25 USB to RS232 DB9/DB25 Serial Adapter Cable (M/M) lets you connect 9-pin (DB9) or 25-pin (DB25) RS232 serial devices to your laptop or desktop computer through a USB port, as though the computer offered an onboard serial port. The integrated 3-foot (0.9 meter) cable allows it to be connected directly from the serial device to the computer without requiring additional cables.
A cost-effective solution that bridges the compatibility gap between modern computers and legacy serial peripherals, this high quality USB/RS232 Serial Adapter cable ships with a DB-9 to DB-25 adapter for connection to varied serial equipment.
These are the same descriptions where some call it a controller while others call it a UART. There is one final note and that is that there are many white box devices that use this same driver. The Moyina USB console cable driver also uses this driver. Even though the Moyina uses a FT232RL chipset. These drivers will work on it as well. The FT232rl driver will work with this driver which many have used in USB port cables and convertors.
Our USB to Serial Adapter fully supports Windows 11, Windows 10, Windows 8, Windows 7. Utilizing the Newest FTDI Chip Technology allowing to be upwards compatible with Newer Operating Systems. Replacing your old USB to Serial Adapter with our new USB to serial adapter should be completely seamless. You can plug our adapter in and click update drivers from Windows and it will automatically download the drivers directly from Microsoft. The Drivers are fully certified.
The Mini-Scanner DLC adapter board is attached to the back of the Data Link Connector plug and therefore lives under the dash near the driver's shins. It connects to the main unit via a 10-way ribbon cable that has a socket at each end and is therefore removable. The purpose of the adapter board is to render the signals safe to pass over a cable. It would be cheaper just to run wires directly from the DLC pins to the main unit. However, I've chosen to buffer the car's signals as close as possible to the connector. My intent is that the ribbon cable can be damaged in any way without harm to the car. No power is taken from the car unless the main unit is attached and turned on. Note that I have not isolated the scanner from the car's electrical system. Opto-isolators and an isolating DC-to-DC converter would add quite a bit to the cost and many applications of the scanner will not benefit from isolation. So, we'll have to be careful when connecting the scanner to an external computer powered from 110 VAC or the car's power outlet.
The power supply is at the bottom left. I need 5V for the LCD and serial port driver and 3.3V for the Z8Encore! microcontroller. Q1 turns the unit on and off. This transistor is turned on by either or both of the On/Reset switch and Q2. Q2 is biased on as soon as power is applied unless port PA2 of the microcontroller interferes. So, when you press and hold the On/Reset switch, the circuit powers up. To turn the scanner off, the microcontroller software configures PA2 as an open-drain output and sets it low, removing the bias from Q2.
Below the backlight circuit on the right is the serial port for connecting a computer or other device. The alternate function of ports PD4, 5 and 6 is used, which is to say, UART1. I have some concerns in this area. I don't think there's space for a DB9, so I've thrown in a 4-pin header. So, a custom cable is required, which increases cost, but at least you don't have to buy your own if you don't already have one. Then, there's the issue of ground being connected to the car's electrical ground, so you need to watch what you connect here. Infra-red (IRDA) might be better all round, but how would you keep a notebook in line-of-sight for logging?
Once you've hacked everything, why not go out in the garage and hack your car? This cable allows you to access the pins on your car's OBDII connector. It has an OBDII connector on one end and a DB9 female serial connector on the other. The overall length of the cable is 5'.
I recommend gridconnect.com for any CAN to USB or serial port needs. I've worked with their USB-CAN adapters and software and it is the best-performing for the price. The API is relatively simple and for $259 you can get drivers and source code (in C) for windows. The link listed above is a simple serial-can bridge to work with teraterm or hyperterminal
I've run the cable under the driver-side floor mat and over to the center console (keeping it out of the way of the driver's feet) and the cable was no worse for wear after a multi-state trip, so it seems to be well made.
The screws on the DB9 end of the cable are occasionally difficult to screw by hand, but I cannot tell if that is due to the cable or the port into which I am screwing it. In either case, using a flat head screw driver to finish the final few revolutions has always worked.
10. Back in your Device Manager double click on your OBDII cable again.Locate USB Serial Convertor Properties->Driver->Update Driver-> Browse my computer.Locate your driver and install. You will need to install it for both USB Serial Converter and Ports & COM.