If it says something like "No suitable drivers found" then I'll have to have a poke around for - but if you're lucky, it should find the BMW Scanner cable drivers and add them.
You need to look on there for the drivers folder (I'm pretty sure it is a folder called Drivers !) and see if you can update the drivers for the BMW Scanner cable. When you want to install its driver, please connect with your car. Now find the BMW Scanner CD and pop that in. You can see a box that says "Update Driver." - select that.
Get yourself to the place you show in your second picture. I'm working from memory here (on train to London!), so bear with me. If so, we need to try to update the drivers for the BMW Scanner cable. So, first thing to confirm 100% - you have definitely got a BMW Scanner cable (with the big black "box" thing at the end), and not using Jimmy's cable? Buy For BMW Scanner 1.4.0 FTDI Chip OBD2 Code Reader Unlock Version OBD2 Diagnostic Interface For BMW Series 1.4 Multi-Functions for 16.8 usd in the online. Basically, it looks as if it is trying to use the drivers for Jimmy's cable and not the BMW Scanner drivers. "Device drivers (or another FTDI drivers) are installed" If you look at the third picture, and read the text next to the green box, it says:
Requires Mac OS X 10.Ran out of time last night to get screen shots done, but I checked my laptop and I would say that my initial diagnosis of wrong driver is correct. Please see the ReadMe, Release Notes and Video Install Guide Please see the ReadMe and Video Install Guide If unsure which ARM version to use, compare the output of readelf and file commands on a system binary with the content of release/build/libftd2xx.txt in each package. Release/build/libftd2xx.txt in each package. This is FTDI’s final release before Microsoft stopped certifying drivers for these versions of Windows.ġ.3.6 ARMv6 hard-float (suits Raspberry Pi) Windows XP, Vista, Server 2003, Server 2008 As such current builds will still work on XP and VISTA but are not Microsoft certified. NOTE: Microsoft have ended support for certifying XP and VISTA through their WHCK test program. Universal Windows Drivers enable developers to create a single driver package that runs across multiple different device types, from embedded systems to tablets and desktop PCs. *** Suitable for Raspberry Pi, please check which instruction set your model implements. **includes the following versions of Windows CE 4.2-5.2 based operating systems: Windows Mobile 2003, Windows Mobile 2003 SE, Windows Mobile 5, Windows Mobile 6, Windows Mobile 6.1 ,Windows Mobile 6.5 You must use the Windows RT build for this platform. Also, as Windows 8 RT is a closed system not allowing for 3rd party driver installation our Windows 8 driver will not support this variant of the OS. *Includes the following version of the Windows operating system: Windows 7, Windows 8/8.1, Windows 10, Windows 11, Windows Server 2008 R2 and Windows server 2012 R2.
Rooting of Android device is not required. Please see the ReadMe, Release Notes and Video Install Guideįor use of the CAT files supplied for ARM and x86 builds refer to With the VCP driver as a standard COM port.
If using a device with standard FTDI vendorĬlaiming the device as a serial port (locking out D2XX programs). If unsure which ARM version to use, compare the output of readelfĪnd file commands on a system binary with the content of 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-certification as a result of making these changes.įor more detail on FTDI Chip Driver licence terms, please click here.Ī guide to support the driver (AN_271) is available In no event shall future technology devices international limited be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services loss of use, data, or profits or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.įTDI drivers may be used only in conjunction with products based on FTDI parts.įTDI drivers may be distributed in any form as long as license information is not modified. This software is provided by Future Technology Devices International Limited “as is” and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed.