PDA

View Full Version : 02 Vette Won't Start After Flashing



2xls1
June 16th, 2012, 02:57 PM
Let me start by saying I know very little about using EFI Live. I've been using HPT and Tunercat OBD1 and 2 for years though. I am trying to help a local shop that has EFI Live but also knows nothing about using it. The vehicle is an 02 twin turbo Vette that was tuned somewhere else (unknown where) with EFI Live and has a COS (2030003) installed. The shop removed some supposedly 80 lb injectors and installed some ID2000s and is going to tune it on E85 now. The car was running on gas. After installing v7.5 and v8.2 on my laptop I was able to read the file out of the Vette. All I changed was the IFR table, voltage offset, and short pulse adder using the data from Injector Dynamics web site. I then did a write calibration. Everything seemed to go fine. No errors reading or writing the file. Now the car won't start. Checking with a noid light we are not getting any injector pulses while cranking. We get one flash on the noid light with key on. The car would start and run fine before changing the injectors and reading and flashing the tune. What did I do wrong? When I opened the original file I read out I did get these errors. I didn't change anything in these tables. I just ignored them since the car was running fine with this file in it.

EFILive Custom Calibrations
{A0000} Forced Octane Scaler, was out of range when loaded.
{A0001} Forced Octane Scaler Percentage, was out of range when loaded.
{A0002} Octane Scaler Limiter, was out of range when loaded.

GMPX
June 16th, 2012, 03:34 PM
Would you be willing to post up the tune? It sounds like the COS was not set correctly to begin with if you are seeing those errors.

2xls1
June 16th, 2012, 04:11 PM
Here they are.

GMPX
June 16th, 2012, 07:33 PM
First thing I did was to fix those out of range warnings, that would have been causing some weird spark timing for sure. That won't fix your problem, but you shouldn't run the old tune with those warnings.
Is the flow rate of those injectors really 180+ lb/hr? Because that is what the flow table is set to.

2xls1
June 17th, 2012, 03:24 AM
The injectors are 2000 cc/min at 3 bar. Using the data supplied by Injector Dynamics, I reduced the IFR by 30% and left the stoich at 14.68 as a starting piont for the E85 tune. I'm not sure I'm going to leave it that way but the car should start and run with those settings.

2xls1
June 18th, 2012, 04:49 AM
I flashed the original file I read out of the car and the car starts. Of course the injectors are the wrong size in the file but the car will start. I even left the out of range errors in the file because they were there originally.

2xls1
June 18th, 2012, 04:53 AM
And on the A0001 and A0002 out of range errors. when I view the values in those 2 tables, EFILive shows the values to be 100 with an allowable range of 0-100. When I re-enter them as 100 and save the file the out of range errors go away.

joecar
June 18th, 2012, 07:20 AM
The tunetool displays any out-of-range values by displaying the nearest min or max value... so if the corners are blue the cell is still OOR (even if an in-range value is displayed).


Have you gotten them in-range...?

2xls1
June 18th, 2012, 08:32 AM
I set a0000 to disable and had to set a0001 and a0002 to 99 to get the errors to go away. Resetting them to 100 would still give me an error when opening the file again. Anyway, the car went to not starting again even with the original tune loaded. As just something to try I disabled the steering collumn lock fuel disable and the vats. I had already tried just the vats by itself and it still woulsn't start. With the collumn lock disabled the car starts up everytime. Even with the new injector values ao I guess that is what it was. We are finishing the tune now.

GMPX
June 18th, 2012, 09:22 AM
You know, when I think about it, I remember GM did an OS update for column lock problems on the LS1 PCM.

2xls1
June 18th, 2012, 10:01 AM
There is a TSB on the Vettes where you take the car to the dealer and they remove the lock from the column and they flash the PCM with the fuel cut disabled. The weird thing is this was a very reliably starting car before I started trying to change the tune.

joecar
June 18th, 2012, 10:25 AM
I set a0000 to disable and had to set a0001 and a0002 to 99 to get the errors to go away. Resetting them to 100 would still give me an error when opening the file again.
...To set the OOR cells back into range do this exactly:
- set all the OOR cells to max-1 or min+1 (e.g. 99 for A0001,2);
- save file,
- exit tunetool,
- restart tunetool,
- set those values to intended original value (e.g. 100 for A0001,2),
- save file;

now they're all in range.


( BTW: don't forget to also do A0012,13 if your COS has those )

2xls1
June 18th, 2012, 11:38 AM
A0011 was set to Not Used and 12 and 13 were set to 824. They were not giving me Out of Range errors. Joe, I was about to PM you for a phone # if I hadn't figured this out. Why was the car running just fine with these out of range? And if the A0000 being set to Enable makes it out of range why have that option? I did learn that using EFILive is a whole lot different than the other tuners I use. I never could get v7.5 to see the cable so I was using V8.2 to read and write and v7.5 to edit. Took a little while to figure out the scanner too. BTW the car made 720 rwhp on 10 psi on E85. The shop is going to try and figure out the boost controller and turn it up to 15 and we'll be tuning on it some more on Thursday. Thanks for all the replys.