94 lt1 corvette pcm 16181333 first time

[gokussx4]

I have searched around and couldn't find an answer to this problem. What I have done:

• Purchased the ALDL cable from aldlcable.com
• Installed ftdi drivers and configured usb serial adapter to com 5
• Installed tunerpro rt
• Downloaded the $EE xdf and adx files for my pcm
• Set in preferences to use plugin and the tuner pro acquistion
• opened the list view of the engine data
• clicked connect and started getting data from the car

The problem is that the data is not correct at all. cylinder id, desired idle, engine speed, etc all have a rotation of numbers that make no sense and the vehicle isn't started. Also, in the status bar below I see the error count constantly increasing and flashing DA data error.
I am pretty sure I am missing something here, please help!

[EagleMark]

The ADX from TunerPro website has never worked but I did make one work for Camaro, Firbird, Impala SS, Caprice and Roadmaster LT1 94-95. Those files and more you'll need are in this thread:
http://www.gearhead-efi.com/Fuel-Inj...to-TunerPro-RT

Lat week I was trying to get the ADX working on a Corvette with a guy via email and after about 5 trys we realizes he had a Com port issue...

If you'd like to try these it would be nice to have one working for the Corvette! Or if someone had a 94-95 Corvette in CDA ID come over to the house so I can figure it out.

Try these files one at a time. First make sure you have done this:
http://www.gearhead-efi.com/Fuel-Inj...to-TunerPro-RT
If you installed cable in one USB port in your laptop then you have to use that one, if you move to another USB port it gets another COM number and have to change TP.

Start car and load ADX then connect. If it does not work turn off car 30 seconds load next ADX start car rinse and repeat!

[gokussx4]

I am going to do this today. I tried it with 2 laptops and go the same result, pretty sure the aldl cable is good being brand new but you never know. Guess its also possible that there could be a problem with the obd and or wiring from the pcm. If there is a way to use a multimeter on the obd port to test I am definitely not against that either :)

Thanks so much Eagle, I will get back to you on these soon!

[jacmaa]

The 94 and 95 Corvette has a 16181333 pcm. Looks like Eaglemark has been working with a 16188051 pcm?

[gokussx4]

EagleMark, jacmaa and I are both working on this car, just so there isn't any confusion :)

We had some success but with an oddity. The $EE-16188051-Y-body-V3.9.adx has worked but not right away. Sat here hitting connect/disconnect at random times and it did finally connect without errors. One pattern I noticed is that the hertz was really low when having errors. When it had no more errors and the data was somewhat stable (engine off/ignition on it was reading engine speed at a solid 50 rpm) the hertz was much higher (7-9 vs 1-3). thoughts?

If you are really interested to solve this we aren't against a little telecommunication such as a google hangout or cell call either ;)

[gokussx4]

Tried out datamaster. It had similar issues though. When at 10 records a second it would error on every 17th record. At first i kept moving the sample rate down and saw about a 2/3 slope of sample rate to number of records to an error. I got 4 rec/sec sample rate to almost work 100%, at one point though it had about 3 instances in a row of 7 records then error. After that it got about 3000 records without an error.

It must be a setting because when it does error it does so in a consistent fashion. Maybe its the usb emulation settings, has anyone had any luck with 94 vette and changing those?

[gokussx4]

Think I might have something here! So I started reviewing the def files you gave me here and found that test 3 and 4 were giving 0 or .10 hertz but no data errors (no data either though). Test 2 was giving the same problem as the others. I compared briefly 2 to 3 and saw that adx header connection on test 2 wasn't set to corvette connection like test 3 was. Changed that and bam works everytime so far! What else should I explore with this file to test functionality of scanning?

[gokussx4]

Update. Received about 5 errors into a idle scan. This was over a 20 min period and didn't happen until it got over 185f which happens to coincide with the fans turning on. Doesn't happen everytime the fan kicks on and off but when it does thats when the errors will occur. Much better than before though thanks :)

[EagleMark]

The 94 and 95 Corvette has a 16181333 pcm. Looks like Eaglemark has been working with a 16188051 pcm?

They are both the same PCM and both use the same ALDL file.

The problem with Corvette is silencing the CCM... that's why there are differant ADX files above, make a change and new ADX. If I had a car here I could wiz through all the possible changes in max couple hours...

That is why I suggested trying each one. One or two of them have known CCM silence commands for 93 Corvette, differant PCM but same CCM silence commands.

So test2 is working with test 3 connection command?

[EagleMark]

If so I see where 3 had a pause in wrong spot, I adjusted 2 to your findings. So give this a shot. If it works then everyone finally has one!

[EagleMark]

Well we finally have a Corvette ADX file and has been tested on 94 and 95 Corvette with success!

Other $EE files are located here:
http://www.gearhead-efi.com/Fuel-Inj...rmation-EE-EEB

[AustinJohn]

Well we finally have a Corvette ADX file and has been tested on 94 and 95 Corvette with success!

To make this work with my 94 lt1 Corvette pcm 16181333 should I use EE.xdf with this?

Thanks, John

[Drew95]

Well we finally have a Corvette ADX file and has been tested on 94 and 95 Corvette with success!

Other $EE files are located here:
http://www.gearhead-efi.com/Fuel-Inj...rmation-EE-EEB

Hey all -

N00b here and I realize this is a REALLY old thread, but I'm hoping someone is still around who can help me out.

I have a 95 Vette that is using the stock PCM, but it's had a custom tune put it in to fit all my mods (LT4 396 stroker, 42lb injectors, 4.10 rear, ZF-6, C5 wheels, etc. etc.). My issue is I'm trying to use the ALDL Bluetooth kit from Red Devil River with ALDLDroid. Has anyone tried this? I get SOME readouts that are right on the $ (mainly temp gauges like Coolant and oil - they match my cluster readout perfectly), but other things like RPM, MPH, Engine/Trans Data etc. either completely wig out or don't even budge. I have a constant red bar along the bottom that mentions checksum errors. Disabling checksum verification has no effect. Same with disable hardware acceleration.

I've attached the debug log just in case.

Thanks in advance for any help!

Drew

[steveo]

what ADX file are you using?

[steveo]

i read your debug log and you're using the incorrect ADX, it's trying to silence the ECM:

[DEBUG] (ECU) 04/15/18 13:33:16.110 Sending command "Silence Chatter Send" (F4 56 08 AE) and now listening for packet (7 bytes)

you need a corvette one that silences the CCM, command would start with F1 not F4

there are some adx files in this thread, make sure you use one that says y-body

http://www.gearhead-efi.com/Fuel-Inj...rmation-EE-EEB