[alex-qts]

Not sure if anyone has seen this yet...

Worrying for those of us that have replica chips in our USB to serial adapters. Apparently the new drivers from FTDI are now sending out random data on the RS232 interface when replica / fake chips are detected, that could be incredibly damaging to our cars during coding.


http://www.theregister.co.uk/2016/01...erfeits_again/

Might be better to stick to older drivers and make sure they don't update.

[PhaseP]

My inpa setup on my laptop didn't work yesterday, sys-0010 initialization error for anything I try to do with inpa. It was working a few weeks ago, and I didn't change anything since, other than windows updates.
Trying to troubleshoot today, I noticed the USB serial driver was updated recently, January 6, 2016 I believe. Then a quick google search I found the same news, that new windows driver was corrupting fake chips.

I just did "Update Driver" for the USB Serial port, and it found a new driver dated January 22, 2016, version 2.12.14.0. I haven't tried it yet, will soon do, and share what I find.

[PhaseP]

The most recent 2.12.14.0 version of FTDI driver is not working either. I am trying to downgrade to 2.08 but uninstall isn't really deleting the drivers, and it automatically reinstalls 2.12.14.0. Need to clean up the registry manually I guess, it is a pain. Will report if I find a solution.
It maybe something specific with my setup, but due to timing of the new drivers coming up and mine stopping working all of a sudden I do suspect it is the new drivers.

[fazman]

Originally Posted by PhaseP

The most recent 2.12.14.0 version of FTDI driver is not working either. I am trying to downgrade to 2.08 but uninstall isn't really deleting the drivers, and it automatically reinstalls 2.12.14.0. Need to clean up the registry manually I guess, it is a pain. Will report if I find a solution.
It maybe something specific with my setup, but due to timing of the new drivers coming up and mine stopping working all of a sudden I do suspect it is the new drivers.

Read the article: http://www.techrepublic.com/article/...terfeit-chips/

You will understand why uninstall/re-install or downgrade won't help you.

I'm glad my coding laptop is a WinXP laptop

[PhaseP]

This time it doesn't "brick" the chip, it only makes it inoperable with that driver in use. Reverting back to old version of drivers are reported to be fine. This is what people who found this second one have reported.

I am not sure what I am running into is this or not, but I highly suspect it due to timing.

[328nick]

Here is a remedy for Windows 10 to stop automatic updates on selected drivers. This only works if you have NOT already updated to the new version.

I checked mine just now and I still have the Jan 6 2016 version 2.12.12.0. So far this version has been working for me.

Follow the link below and find the download link. Open the program, press next, select 'hide updates', select your FTDI drivers from the list, and press next. Now the selected drivers will not automatically update. This is supposed to be a 'temporary fix' but you can leave them this way as long as you want.

https://support.microsoft.com/en-us/kb/3073930

EDIT: for reference my cable is from bimmer software com

[PhaseP]

2.12.12.0 has the added making fake chips inoperable code. After a lot of manual fiddling with registry, I installed 2.8 driver, which is reported to be fine in this regard, but I still get the initialization error. I am planning on wiping clean the laptop and restart. Again not sure this is the problem but nothing else changed.

The cable does have an FTDI chip on it, but I have no idea or way to find out if it is a fake or not. It was an ebay buy years ago was working since a few week ago.

[B3NPM]

Mine is also on 2.12.12.0 and is fine. The later 2.12.14.0 stopped working. Reverted laptop back to factory and blocked update of driver.

[PhaseP]

Just as information, there are two devices and related drivers: one is the USB COM port, the other USB COM converter. They both need correct drivers. You can find the other one from windows device manager, by clicking on the USB com port then choosing show devices by connection. Its parent node is the converter.

I decided to wipe clean my laptop and restart from scratch.

[PhaseP]

Just to give update, my obd/usb cable with current latest driver release version 2.12.16.00 is working again. Apparently FTDI removed disabling functionality from the driver against fake chips.