Custom OS#5

[TFZ_Z06]

What I did all using ROADRUNNER:
Wrote 02020005 as cal and operating system. There are 3 choices, read, write cal, write cal and os.
Write CAL only of file from 12212156 that I converted from original tune file.
Read CAL and OS back and saved for tuning.
Made a few changes (disabled TPS VE so I could log first) and wrote it.
Turned key on, did not start engine. All seemed normal. Fuel pump came on, needles swing, looked like a normal startup.

Ok, time to set up scanner and log COL=TP, ROW=RPM and Data: g*K/kPa to create a starter TPS VE table.
SURPRISE, when I connect w/the scanner, it ask for a vin#. I input it and then it basically eliminates most of
my logging variables, including and especially VETABLE_DMA. So, I abort and keep trying to get it to recognize the logging
params.

Now the car is stuck in reduced power mode.

Ideas?

[joecar]

TFZ_Z06,

Car will not crank: is this the Z06...? Did you use a 12212156 file containing ETC...?

[TFZ_Z06]

I got the car running, but for others, here are the main problems I ran in to:

Problems on Install:
Problem 1: I initially had problems w/the logging because I didn't write the VIN# using the scan tool. The scanner kept seeing
zero's as the vin# and thus no PIDS were available.
Soln: Use Scan tools BiDirectional -> Change Vin#.

Problem 2: Oil Life = 0%.
Soln: Use Scan tools BiDirectional -> Change Oil Life. I changed mine to 100%.

Problem 3: The car wouldn't initially start becaause A0008 "Open Loop ECT Commanded Fuel Multiplier" was set to 2.0. This means the commanded fuel = 2 X MAIN VE or TPS VE whichever was active, in my case main ve. The adjustment range is 0.8 to 2.0. This is VERY effective for lean/rich cold starts.

Problem 4: P1336.
Soln: joecar instructions in next post. start engine, start scanner, select DVT tab, activate target controller, select Learning, then follow instructs in next post. In my case, as soon as the engine reached 4000rpm, the pcm cut engine power (as if one had instantaneously turned the key off), then I released the throttle to idle for a few seconds, deactivated DVT option, turned off engine and waited 15 seconds. P1336 solved.

First Test:
My setup is Open Loop, Speed Density (OLSD). I logged VETABLE_DMA w/engine running on the Main VE table first (A0003 Disabled), then I when I got comfortable w/the data, I transferred the Main VE table to the TPS VE with slight starting point adjustments. To tune the TPS VE table, I set the params in COS5 to use the TPS VE table until 90 KPA, 8000 RPM,90 TP%, then went out VE tuning using the RoadRunner.

Results:
Spectacular. I just got back after driving around about 45 minutes. My impressions of the difference between this and the Main VE table are the following:

1. Light throttle is much smoother and not nearly as jerky in areas that it was before. I can drive the car around in traffic and you would never know whats under the hood. The RoadRunner makes VE tuning so fast, by the time I was on the way home, I actually starting driving in 6th gear, at 800rpm standing on the brakes trying to tune it for high gear, low rpm! I'm going to visit FFP's dyno soon and finish off the TPS VE table.

2. The engine runs crisper at light throttle positions.

3. Not sure yet about the transition from part throttle to WOT. I'll report back after thats done. Can't really do it on the street without slicks on the car.

[joecar]

P1336 means the crank relearn has not been done...

In scantool goto the DVT tab, enter your PCM type (Gen III LS1 99-08), goto the Learning tab...

conditions must match those shown there (ECT, TP, VSS)...

then (read thru this before doing, this all happens in about 3 seconds or less):
- click Activate,
- click the CASE button,
- smoothly push throttle down to raise RPM to above 4500 (you have a 10 second window in which to accomplish this),
- engine will stumble for a moment, immediately release throttle when you detect this stumble,
- let engine spin down by itself to idle,
- after engine is at idle, turn off ignition and wait 15 seconds,
- while you're waiting 15 seconds, you can click Deactivate.

If the engine did not stumble then the relearn was not initiated and you have to redo it (turn engine off, turn on, and start again).

When you next turn on ignition and read DTC's, P1336 should be gone.

[TurboCamaro]

I have read this thread thoroughly a few times now.
It doesn't say definitively if you can utilize COS5 to control Nitrous Timing and Fuel on an '03 Corvette Z06 as this is a drive by wire car.

[TFZ_Z06]

I have read this thread thoroughly a few times now.
It doesn't say definitively if you can utilize COS5 to control Nitrous Timing and Fuel on an '03 Corvette Z06 as this is a drive by wire car.

Your OS 12593358 would require the 02040005, but only 0001, 0002, and 0003 are avail. Since your OS is actually a 2002, just use the same one I did on my 2002
Z06. 12212156 and 02020005.

For more info, see Help->Tutorials->Custom Update OS tutorial. It list the OS and the proper COS to use.

BTW, make sure your file is the OS above. If not, post up, I'm interested which you have.

[TurboCamaro]

You are correct my the cars operating system is 12593358 as you suggested.
Were you able to directly flash your original cal after the full flash of COS5.
This car is a Lingenfelter deal so I don't want to lose all of their work. I would like to go in and just confirm the VE, etc is good than add the Nitrous.

[joecar]

With 02020005/COS5, you can cal flash only from a 12212156 file...


i.e. you would have to copy all your tables to a 12212156 file with the same trans and throttle...

then you would full flash the copied-to 12212156 file and make sure your car runs correctly on this...

then you full flash 02020005 and then cal flash from the copied-to 12212156 file.

[joecar]

12212156 is the base OS for 02020005.

If it's just COS3 that you want, the look in the COS tutorial as TFZ said above.

[TFZ_Z06]

You are correct my the cars operating system is 12593358 as you suggested.
Were you able to directly flash your original cal after the full flash of COS5.
This car is a Lingenfelter deal so I don't want to lose all of their work. I would like to go in and just confirm the VE, etc is good than add the Nitrous.

No, it was not possible to directly flash my original cal. The original OS/cal for my 02Z was based on 12221588, thus would only work with 020300XX, where XX= 01, 02, 03. Of course, COS5 has the nitrous controls that are not avail in 1, 2, or 3.
You are in a similar situation w/your OS as you can only directly cal flash 12593358 using OS 020400XX. According to EFI's help tutorial, your processor pcm code/cal is really a 2002.

HOW TO MAKE YOUR 03Z WORK WITH 02020005:

1. Read and save your original Lingenfelter file.

2. Flash 02020005 to your processor using "CAL and OPERATING SYSTEM"

3. Transfer via COPY and PASTE all of your data from 12593358 to 12212156. Recommend you open two copies of EFI Tune
and just transfer as you go, using copy with labels when possible for speed and accuracy.

4. Flash CAL ONLY the 12212156 file you created via copy and paste.

6. Read back the file and save it. This is your base tuning file that will contain COS5 and your base CAL. From this point forward, you won't need to flash the OS, just a CAL ONLY.

7. Write VIN# via SCAN TOOL; see my post above.

8. Write Oil Life; see post above

9. Crank engine, Activate and relearn Crank misfire strategy. See joecar's post and part of mine above.

I'm getting ready to hook up my nitrous system again. So I can't wait to see how well it works. I'm currently tuning the TPS VE table and have had some very good feedback. At this point, I would like to see more options in COS5, provide there is enough room for coding in there.

REQUEST FOR EFI STAFF:
You already have a MAP kPa to use the MAIN VE map. What about the reverse? If I go below x kPa, use the original MAIN VE. The issue at hand is that I like the resolution I get out of using the TPS VS RPM, but I would like to tune the decel stuff too or cruise when the MAP is actually less than idle vacuum. This would give me the most resolution. If I have missed something, let me know. I've only had the OS a few days, but having fun so far...

EDIT: joecar you beat me. I was typing. As joecar said, flash 12212156 and make sure it runs first!!!!!!