Never mind. I got it to work. Thanks

 

In case others are wondering about the solution to the above, the error message looked like this:

Could not find file 'C:\Windows\system32\malf.csv'

It occurred because the files had not been extracted from the zip file and placed in the same folder together. Pressing "Continue" might have worked but there would have been no DTC's reported.

 

Hi there!
Recently, one guy from the local american car club asked me to build a copy of a cable that I built with this threads help. But he uses not LT1 but 4.3L L99 engine in his 1979 Monte Carlo. So I decided to post him my cable for tests before building a copy. This cable passed tests great with GaryDoug's Scan9495 app on that engine and I was very glad to know about this.
For now another one guy asked me to build a copy of cable to use it with his '95 454 engine (Suburban 2500). But he noticed to me that it has 12-pin OBD-I connector. Also he said that his PCM uses 8192 baud rate.
So I would like to ask, is there any chance that this cable will work? I know that this great app Scan9495 works with LT1 and L32 engines, but it has a tab where we can find a raw data going from the cable. If Scan9495 will show some raw data going from the cable connected to that PCM, can I say that this cable works properly? This guy will try to use another apps working with COM-ports to recieve data from this cable.
Thank you very much!

 

The reason it works on the L99 is that the pcm data is almost exactly like the LT1 data. It uses the same commands to ask for the data and the same format in the reply with data. Only a few minor items are not the same.

The 454 (7.4L) is not the same, but Scan9495 does have a custom mode which can retrieve the raw data, but not display it in a good format like for the LT1. You would have to manually extract the data using the definition file for that engine (A219) and it would be a very tedious operation. The cable should work fine on the 7.4L engine. The LT1 is 8192 Baud and the 94 LT1 is a 12-pin connector. Instead of Scan9495, I suggest he use the free app TunerPro RT with the $0E definition file. It's harder to set up but would be easier to use once that is done.

TunerPro and TunerPro RT - Professional Automobile Tuning Software

 

Thank you!
Now it is all clear for me about the L99 engine. I knew that it is similar to LT1 engine.
Also I asked that guy about the app he wanted to use with cable, he said that it will be a TunerPro. Also he said, that he already tried to use this app with some selfmade cables, but all of them failed to transfer any data from PCM. So I think, that he has some chance to retrieve data with cable you provided on the first pages of this thread. I'll try to build this cable like one for '94 LT1 engine, hope this will work for '95 454 engine.

 

Hi there!
I have a problem. I've built another one cable using the same components from the same seller. So I conndected a new cable to the same laptop and it found those drivers that were in the system from my first cable (that worked properly) and installed them right (COM6 port appeared). Ran the app, and when the cable was connected to the car I tapped Connect/Reset button. But the app shoewd an error message window with 'Connected device doesn't work' phrase.
So, what it could be? Where is the problem?


Thank you very much!

 

I am not familiar with that message so I doubt the app is reporting it. Can you make sure that is the exact message?
Some of sellers of the adapter cables we buy change the wire colors so we wire it up wrong. Did you check the continuity of the wires to the pins on the end connector or the pcb first?

 

O.k. I will take a screenshot of that message window, but there is some issue - that phrase was in Russian because of operation systems localization. So I simply translated it in English. But the other information was in English right there, so I think that a screenshot will be helpful. Maybe it will be the best if I take some short video.
I also thought about wire shuffling. That cables are completely identical, and I've bought it from the same seller.
I only checked the quality of soldering. The only difference is that my first cable black wire I soldered to the hole in the center of the connectors PCB, but in the second one I used fourth and fifth pins together - that's all. Please, tell me what I must to check according to your phrase 'continuity of the wires to the pins on the end connector or the pcb first'?
Thank you!

 

Here is how to check with a multimeter or continuity checker.
Remove the two halves of the plastic case on the USB end by prying them apart. Most are very easy to remove. See what wires are attached to the TXD and RXD terminals. Check for continuity from both of those to pin 9 on the 16-pin connector. See what wire is connected to the Common or ground terminal on the USB end and check for continuity from that to pin 4 and/or 5 on the 16 pin end.

 

Thank you! I'll try to check that stuff today. I'll open the case and try to recognize TXD/RXD terminal and the ground, then check continuity.
Also I made some ridiculous video to show what the error occurred. So, sorry for my English and pronunciation. Thank you.

 

Does the other cable work ok? Does it use COM6 also? The message seems to be indicating an error with the device, not a wiring mistake. Perhaps it is defective. Can you temporarily change the region setting to US so we can see the error message in English and try again?

 

Yes, you're right! My first cable worked fine, but used a COM3 port.
Here's the old screenshot...





Ok. If it will be helpful I'll change region setting to US, I don't know, but maybe it will be necessary to install even an English languauge pack for this OS, cause it was Russian from the box.

 

Good afternoon Gary, will your program work on a 94 Impala SS LT1? Just want to do some basic scans and change electric fans temps.

Thank you and god bless.

 

Probably, but this app is not for making any changes to the pcm.

 

What cable must one buy for a 1993 LT1?


The original post doesn't explicitly say.