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

[Danspeed1]

Ken, I do not want to give you misinformation as I rarely have the opportunity to use tunerpro rt anymore, but I had a 1990 Corvette I was working on and ran into the same exact issue. I could never get it to emulate properly. In the event you do not receive any additional helpful information that may resolve your problem, I would recommend investing in a chip adapter to plug into your ecu. I did this and then tuned two chips. On in the car, made chances burned the new chip, replaced it, did another test run, and repeat until I got it dialed in. It took me about 15 swaps before I had the car dialed in but it worked like a charm.

Dan

[skandolis]

your 94 should have a flash computer if im not mistaken, a lot of people have trouble connecting to the lt1 computer because of all the extra modules on the car,for logging and diagnostics maybe try a program called $EEhack, written by one of the members here. i use it on my lt1 caprice no problems...(then again, tunerpro never gives me problems on it either)

[steveo]

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

[Danspeed1]

I wish I had know this when tuning my last one, although to be honest I was able to get the chips in and out as quickly as it takes to load a tune on hptuners. I generally never RTT anyway, I find it more complicated so to make an adjustment, upload (or in this case burn), reinstall and start again never real bothered me. It would be cool to have a true understanding though of how to get the RTT feature of Tunerpro RT to work. I just bought a 1989 Pontiac McLaren Grand Prix with the turbo 3.1 and you know I am going to want to mess around with that!

Dan

[steveo]

I wish I had know this when tuning my last one, although to be honest I was able to get the chips in and out as quickly as it takes to load a tune on hptuners. I generally never RTT anyway, I find it more complicated so to make an adjustment, upload (or in this case burn), reinstall and start again never real bothered me. It would be cool to have a true understanding though of how to get the RTT feature of Tunerpro RT to work. I just bought a 1989 Pontiac McLaren Grand Prix with the turbo 3.1 and you know I am going to want to mess around with that!

your 1990 is a completely different beast than this guy is dealing with

[Danspeed1]

your 1990 is a completely different beast than this guy is dealing with

Interesting... not that it matters at this point... you know the history of that car, but I wonder what the issues were. I hope he is able to find a solution to his problem as I am sure I will be tuning an lt1 corvette sometime in the future.

Good luck Ken...

Dan

[KenMathisHD]

Didn't mean to ghost my own thread lol, was expecting a popup to appear in email when I got a response. Though I may have to check the email I've got on my accout...
I didn't know that the LT1 in timing for talking to the ECM, that's odd that they'd be set up like that. I'm using $EE-16188051-Y-body-V3.8.adx as my TunerPro adx file - how much different is $EE hack from TunerPro? I'm assuming it will work the the same OBD cable I've been using, but does it require something specific be installed to have $EE hack talk to the cable?

[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.