Issues with using TunerPro on a 94 Vette with 155k miles

[Injected CJ7]

the problem is the timing it takes to silence the CCM module, which is the bus master on that particular car. as soon as you have power to it, the CCM and ECM both start blabbing away with useless information on the bus. the program needs to find a section of silence on that serial line (which has transmit and recieve on the same wire) long enough to throw out the necessary command, and complete sending it before more bus chatter happens.

what ADX are you using?

with tunerpro, the ADX isn't exactly smart enough to get the timing right, as far as I know, 'disconnecting and reconnecting' a few times usually does the trick, sometimes it might take a few tries.

of course i have to recommend eehack too, it's logging/analysis/graphing are purpose built for lt1 tuning and diagnosis.

it has a corvette-specific connection mode that apparently works well.. i didn't write the routine myself, someone with a corvette wrote it for me... it's been fairly well tested now. definitely give it a shot

Hi Steveo,
I've been reading tons of threads on eehack, and I'm getting ready to try it out in my '95 Vette. I've used TunerProRT in the past to get my 78 Jeep CJ7 ('88 5.7L Tune Port) datalogged so I could get a tune put on it (long story). So I have a very limited knowledge with using this type of equipment. I have a cheap laptop with XP and just enough processing power for the minimum requirements. I have a Moates (ALDU1 and CABL2) cable as well. My quick question is whether I have the right files to load. I have:

eehack 4.7
EE_16212471.bin
EEX.XDF
$EE-16188051-V3.8.adx

My car is a 95 LTI, automatic, 3.07 rear, shorty headers, Magnaflow Cat Back 3" exhaust. The rest is stock. I'm waiting for a new battery for the laptop, so I won't need a 5 mile long extension cord to datalog LOL. Can you tell me if I have the right files to get started, and is there a preferred order to load in files and hook up the cable? Sorry for being such a Newb, but I'd really like to hear your thoughts.

Thanks!
John

[steveo]

Hi Steveo,
I've been reading tons of threads on eehack, and I'm getting ready to try it out in my '95 Vette. I've used TunerProRT in the past to get my 78 Jeep CJ7 ('88 5.7L Tune Port) datalogged so I could get a tune put on it (long story). So I have a very limited knowledge with using this type of equipment. I have a cheap laptop with XP and just enough processing power for the minimum requirements. I have a Moates (ALDU1 and CABL2) cable as well. My quick question is whether I have the right files to load. I have:

eehack 4.7
EE_16212471.bin
EEX.XDF
$EE-16188051-V3.8.adx

My car is a 95 LTI, automatic, 3.07 rear, shorty headers, Magnaflow Cat Back 3" exhaust. The rest is stock. I'm waiting for a new battery for the laptop, so I won't need a 5 mile long extension cord to datalog LOL. Can you tell me if I have the right files to get started, and is there a preferred order to load in files and hook up the cable? Sorry for being such a Newb, but I'd really like to hear your thoughts.

Thanks!
John

that's alright except for the ADX file, wont work with your 'vette. you don't need the ADX anyway, eehack will do all of your datalogging

your modifications are minimal, wouldn't expect much tuning required

read this thread

http://www.gearhead-efi.com/Fuel-Inj...-lt1-M6-tuning

[Injected CJ7]

that's alright except for the ADX file, wont work with your 'vette. you don't need the ADX anyway, eehack will do all of your datalogging

your modifications are minimal, wouldn't expect much tuning required

read this thread

http://www.gearhead-efi.com/Fuel-Inj...-lt1-M6-tuning

Hi Steveo,

I did read the thread shown above. I was able to try datalogging my 95 C4 yesterday, and I have a couple of questions. When I hooked it up to the running car, several SES lights immediately came on. I think it was ASR off, Service ASR, Service Engine Soon, and maybe another (can't recall). Also, as I drove off on my lap around the block, the gas gauge read 'reserve' (pretty sure I wasn't that low), and the coolant temperature was at 76F and never changed. I never figured out how to load the BIN or XDF files into eehack. Do these files have to be in the same folder as the program? The files were on the desktop, not in the folder, and I'm thinking that might be an issue. I've attached the data file, in case you have time to take a quick look at it. Of much greater concern is that my transmission began acting funny after I stopped for gas. It was slipping from a start as if it was low on fluid, and didn't want to upshift. I limped it home and checked fluid level (seemed OK) and then shut it off. So, could running the car with eehack, using probably the wrong (or no) support files affect the operation of the electronic 4L60E trans? Also, if I put the BIN and XDF files in the program folder with eehack, will it recognize them and work correctly? The engine seems to run well, except that the idle speed is about 1200 to 1300 when the car is in park or neutral. I've checked for vacuum leaks in all the 'small' hoses, but still need to double check the PCV, brake booster, and maybe the canister purge lines. From my readings, it seems that a vacuum leak is the most likely scenario, but I haven't found it (yet). If you can give me any feedback, it would be greatly appreciated!

Thanks,
John

[lionelhutz]

EEhack doesn't use the bin or xdf file. That is a Tunerpro thing. Does it run right once you disconnect the laptop and cycle the key off and then re-start it? It should.

[steveo]

When I hooked it up to the running car, several SES lights immediately came on. I think it was ASR off, Service ASR, Service Engine Soon, and maybe another (can't recall).

because we have to silence the CCM (command and control module) to do any datalogging, it may disable or affect some instrumentation or functions that the CCM is responsible for, but i didn't think the fuel gauge and temperature were one of them. the CCM definitely doesn't contain any functions that affect how the engine or transmission run, even if it's unplugged the car should drive as normal.

Of much greater concern is that my transmission began acting funny after I stopped for gas. It was slipping from a start as if it was low on fluid, and didn't want to upshift. I limped it home and checked fluid level (seemed OK) and then shut it off. So, could running the car with eehack, using probably the wrong (or no) support files affect the operation of the electronic 4L60E trans?

there's nothing 'by default' that eehack does that could affect your transmission

it does have a line pressure control but you have to enable 'expert mode'. it does have an override gear selector too. these are in the control section. i'm sure you'd remember doing that.

[steveo]

i looked at your log, looks about normal for a stock 'vette, its trims are a bit lean but all corvette calibrations are for some reason. of course your car isn't really modified so i'm not sure what you'd expect to see there, shorty headers and a catback don't exactly throw off a calibration

[Injected CJ7]

i looked at your log, looks about normal for a stock 'vette, its trims are a bit lean but all corvette calibrations are for some reason. of course your car isn't really modified so i'm not sure what you'd expect to see there, shorty headers and a catback don't exactly throw off a calibration

Thanks Steveo,
It's comforting to know that the log looks normal, as the car runs pretty well, except for the dang high idle! With respect to the SES lights, if they aren't causing an actual problem (which you indicate they aren't) then I'm not concerned. I stepped though the codes on the car and got the following:
1.
H41
4.
H77
H22
9.
H64
H72

I cleared them all, but haven't started the car yet. I'm going to do another datalog with eehack this weekend. Just so I'm sure of the steps I should follow:

1. Start eehack (no support files necessary) with usb cable plugged in to computer, but ODBII plug not connected to car,
2. Select Port and Vehicle Type in Settings Window,
3. Start engine,
4. Plug ODBII in to car,
5. Begin driving and logging.

Does this sound correct?

In the log file I sent you (trial 1), I looked at the graph in the area of 290 to 350 seconds, when I came to a complete stop and put the car in park. At this point, my Idle Target RPM was about 550, my Idle Air Controller Position was around 20, but my Idle speed was around 1300. Does this data support the possibility of a vacuum leak? I'm not sure what other parameters I should look at to help track down what the problem is. If you have any suggestions or ideas, I would greatly appreciate hearing them.

One more quick question. In the ECM/Calibration Info window, the VIN and Cal ID# do not match my car. I assume this means the ECM has been replaced at some point, correct? I see there are Set VIN and Set CALID buttons. Should I put my data in here, or doesn't it matter?

Thank you for all the help so far. It is greatly appreciated! I'm sending you a few bucks for an adult beverage or two. Your program is Awesome!

Regards,
John

[steveo]

I cleared them all, but haven't started the car yet. I'm going to do another datalog with eehack this weekend. Just so I'm sure of the steps I should follow:

1. Start eehack (no support files necessary) with usb cable plugged in to computer, but ODBII plug not connected to car,
2. Select Port and Vehicle Type in Settings Window,
3. Start engine,
4. Plug ODBII in to car,
5. Begin driving and logging.

you're overthinking it. plug the cable into your car and laptop before starting eehack, turn the key on, and connect. you can log whether the engine is running or not. your old port and vehicle type settings will be remembered from last time. also eehack is always logging (just remember to save after..)

One more quick question. In the ECM/Calibration Info window, the VIN and Cal ID# do not match my car. I assume this means the ECM has been replaced at some point, correct? I see there are Set VIN and Set CALID buttons. Should I put my data in here, or doesn't it matter?

you can definitely set your vin if you want, but it doesn't matter. the calibration id is 16200891 in your last log, this does match a 1994 auto 'vette so no problem there

In the log file I sent you (trial 1), I looked at the graph in the area of 290 to 350 seconds, when I came to a complete stop and put the car in park. At this point, my Idle Target RPM was about 550, my Idle Air Controller Position was around 20, but my Idle speed was around 1300. Does this data support the possibility of a vacuum leak?

did not meet the conditions for idle. look at your TPS (throttle position) during that time, it's at 9%, and other parameters indicate an open throttle condition. either you didn't have your foot off the gas, or your throttle was partially stuck open for some reason (cable, sticky plates, floor mat?). the log doesn't indicate a TPS fault of any kind.