If your cheap BMW INPA K+DCAN USB interface with FTDI chip failed to install drivers or the system prompt cannot locate the drivers. Here is a little write-up on how to fix it.
Disclaimer:
I am using Windows 8.1 system. No sure if it works on yours. You are on your own risk.
FTDI Driver Installation - Example 3: Windows 2000. Insert the CD into the drive and connect the USB Serial converter to an available USB port, the “Found New Hardware Wizard” window will pop up. Drivers are available which allow FTDI devices to work with the following operating systems:.FTDI Windows 8 USB Serial Driver: Windows 8 x64: Windows Server 2008 R2: Windows 7 FTDI USB Serial Adapter Driver: Windows 7 x64 Windows Server 2008 Windows Server 2008 x64 Windows Vista Windows Vista x64 Windows Server 2003 Windows Server 2003 x64 Windows XP Windows XP x64 64-bit USB to Serial. Please be warned that counterfeit (fake) PL-2303HX (Chip Rev A) USB to Serial Controller ICs using Prolific's trademark logo, brandname, and device drivers, were being sold in the China market. Counterfeit IC products show exactly the same outside chip markings but generally are of poor quality and causes Windows driver compatibility issues. FTDI drivers may be used only in conjunction with products based on FTDI parts. FTDI drivers may be distributed in any form as long as license information is not modified. If a custom vendor ID and/or product ID or description string are used, it is the responsibility of the product manufacturer to maintain any changes and subsequent WHCK re. Get the latest official FTDI USB Serial port (com/lpt/serial) drivers for Windows 10, 8.1, 8, 7, Vista and XP PCs. Update drivers with the largest database available.
Pre-installation caution:
Here are the INPA driver & software, free download links. If the driver/software is working, then ignore the next part. Otherwise take a look at the following part for reference.
INPA Driver: http://www.obd2vip.com/download/inpa-driver.zip（Close antivirus software or set your browser to download success）
INPA software: http://www.obd2vip.com/download/inpa-2.zip
Procedure:
1. Open your Device Manager. Control Panel–Hardware & Sound–Device Manager.
2. Connect the INPA K+DCAN cable with computer/PC-Double click
3. Locate USB Serial Converter->DetailsDropdown Menu->Hardware IDs. The PID number is the one you want. Will most likely be 0000.
4. Download CDM v2.08.30
http://www.ftdichip.com/Drivers/CDM/CDM%20v2.08.30%20for%20Windows%208.1.zip
5. Disable “Driver signature verification” Settings–Change PC Settings–Recovery–Advanced Startup–Restart.
This will restart your PC to Advanced settings. From there: Troubleshoot–Advanced Options–Startup Settings–Restart–F7
Follow these picture guides:
Your PC will then restart with signature verification disabled. You are now able to edit the INPA drivers.
6. Unzip the Drivers file that you just downloaded and open up
7. Open ftdibus.inf
8. Replace every PID_6001 with PID_0000 to match your hardware ID. Scan through the whole document. Then save it.
9. Then find ftdiport.inf. Do the same to ftdiport.inf
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.
11. Setup INPA cable as normal and run INPA software.
It seems that the white FTDI chip INPA cables have to be manually put into D-CAN mode. This file will take care of that. It is normal for the LED to go out.
http://www.mediafire.com/download/35fnrnd3q3dvf3w/D-CAN.exe
If you put the cable into DCAN mode, the LED goes off, and it says there is no adapter connected. Please connect it to the car and run the DCAN mode.
Related posts:
Ftdi Usb Serial Driver Osx
Versions supported
- Windows 10
- Windows 8.1
Applies to
- Device manufacturers of CDC Control devices
Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.
- Improved PnP and power management by the driver (such as, handling surprise removal).
- Added power management features such as USB Selective Suspend.
In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.
Usbser.sys installation
Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
Note
If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.
Windows 10
In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function device object (FDO) in the device stack. If your device belongs to the Communications and CDC Control device class, Usbser.sys is loaded automatically.You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.
USBClass_02
USBClass_02&SubClass_02
- If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
- If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
- If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.
Note
Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.
Windows 8.1 and earlier versions
In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies 'Usbser' as a lower filter driver in a device stack.
The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the [Version] section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.
For more information, see How to use or reference the Usbser.sys driver from universal serial bus (USB) modem .inf files.
Configure selective suspend for Usbser.sys
Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the Suspend state and resume Working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:
Ftdi Usb Serial Driver Windows 10
To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:
'0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.
'0x00000000': Enters selective suspend only when there are no open handles to the device.
That entry can be added in one of two ways:
Write an INF that references the install INF and add the registry entry in the HW.AddReg section.
Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.
For more information, see Microsoft OS Descriptors.
Develop Windows applications for a USB CDC device
If you install Usbser.sys for the USB CDC device, here are the application programming model options:
Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.
In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:
Win32 programming model:
.NET framework programming model: