New cable , no workie ......

[antus]

Digging up a bit of an old thread, but ive been researching info about the counterfit FTDI chips that have been in circulation in the last 6 months and stumbled on this thread.

I believe the issues is just that, counterfit chips. FTDI appear to have modified their drivers to detect the bad silicon and cause them not to work. This is why the old driver that pre-dates the forgeries hitting the market still works.

According to this site http://zeptobars.ru/en/read/FTDI-FT2...-fake-supereal the forgeries have been made to be API compatible but not a copy of FTDIs silicon at all.

It seems the market has been flooded and many genuine companies have been stung. Ive also been stung, and it seems one must now be careful to buy only though official distribution channels. There are other reports around the net of the same.

[89S10_Project]

Digging up a bit of an old thread, but ive been researching info about the counterfit FTDI chips that have been in circulation in the last 6 months and stumbled on this thread.

I believe the issues is just that, counterfit chips. FTDI appear to have modified their drivers to detect the bad silicon and cause them not to work. This is why the old driver that pre-dates the forgeries hitting the market still works.

According to this site http://zeptobars.ru/en/read/FTDI-FT2...-fake-supereal the forgeries have been made to be API compatible but not a copy of FTDIs silicon at all.

It seems the market has been flooded and many genuine companies have been stung. Ive also been stung, and it seems one must now be careful to buy only though official distribution channels. There are other reports around the net of the same.

It sounds like this may very well be my problem. The chips I'm using were purchased circa 2013, and are exhibiting the same flight performance- including not working at all since the latest drivers were installed.

I will be buying a prefab cable with OBD1 connector Friday and will leave the DIY route for future exploration. This way I'll have all needs addressed.

[phonedawgz]

You can try pulling up a terminal emulation program and trying out the port. Due to the nature of the wiring needed, you should get an echo of the characters sent. If instead you get null characters for every one sent you have the counterfeit problem.

[antus]

Its also not true that the chips work with the old drivers, at least the ones I had did not. I was on XP and installed the recommended older drivers and could connect to my ecm. But i couldnt log for more than a minute or two before the com port would crash (not sure if driver or hardware) and TP would lock right up until I disconnected the USB cable at which point TP came back to life but of course only counting data errors. Maybe with a smaller amount of data or at normal speeds they were more stable, or maybe whoever tested did not really give them a hammering, but I would not recommend using them for ALDL even if you do run the old driver.

[phonedawgz]

The data speeds that the GM OBD1 ECMs output is either extremely extremely slow (8192 baud) or extremely extremely extremely slow (130 baud), compared to the limits of the chips used (3,000,000 baud- 3 meg). I have quite a bit of experience with the genuine chips and with the fake chips. I have not seen the lock up problem before but I doubt it is coming from a data overrun of the fake or genuine chips.

[89S10_Project]

I am by no means an expert on GM EFI, but I know a thing or two about computers. Concur with phonedawgz, there's no way in this world that the GM EFI unit is buffer-overflowing the USB chips, real or phony.

Still wasn't able to get mine working. I get paid tomorrow, I need one of these cables ASAP. I'm in Charleston, SC- how quick can you get one to me, phonedawgz?

FTR, I will need a cable for a OBD1 setup in an 89 S10 Blazer. Originally had the "Vin Z" 4.3, now has a similar 5.7 running TBI with the 1227747 (or is it an 8062? Believe they are both compatible) ECM.

[phonedawgz]

PM replied to