More COS5 questions

[FreshDA9]

I have never attempted a COS before I have read the tutorial millions of time now and feel comfortable to do it to my truck. Although I was looking more into the COS5 for the Nitrous controls. Here is what I found:

My OS 12202088
My choices are 012500xx (either 01,02,03)

I was reading another thread here in which I think he flashed in another OS (12225074) then ran 01290005. I am looking for more information on this please. :banana:

I also noticed a lot of talk about tps ve table I wish not to use this I take it this is something that can be enabled and dissabled. Is this a varient of Alpha N tuning?

[ferocity02]

TPS VE can be disabled.

I switched to 12212156 and then did COS5. I don't think it really matters though.

[joecar]

For COS5 you need to first swap to OS 12212156 as ferocity said.

TPS VE is alpha-N (alpha being throttle angle, N being engine speed).

TPS VE can be enabled any time provided you populate the TPS VE table with values obtain from your corrected Main VE table (using the pid GM.VETABLE_DMA).

[FreshDA9]

Ok so just go under EFILive>V7.5>Calibrations>LS1B> and select 12212156 OS and full flash it like a COS. then retrieve it and open my original cal and flash it?

Will there be map addressing issues. (I wish I could find the other thread to look over the issues he ran into it.)

Then repeat for going to COS5.

[joecar]

Take the 2002 Camaro 12212156 tune file with the same transmission as yours, found on www.tunefiledepot.com (http://www.tunefiledepot.com)

then manually copy any non-stock tables from your 12202088 file over to the 12212156 file (open two instances of the tunetool);

then full flash the 12212156 file into your PCM, make sure your engine runs same as previous;

then follow COS5 procedure (full flash 02020005, cal only flash from 12212156, fix OOR cells, populate B3647 and other tables).

[FreshDA9]

Thank you Joecar, I will do this tomorrow and post results.

This may be a dumb question I have herd reference in other threads to "OOR" but don't know the meaning sorry.

[ferocity02]

Out of range?

When you switch to the COS you will need to go through the tables and fix values that are out of range. Some you will have to make lower/higher and the max/min, save, reopen and set to the max/min in order for the tune tool to not say they are out of range.

[joecar]

Yes, out-of-range... (those cells will have blue dogear corners)... to fix those set them to max-1, save file, exit tunetool (important step), re-start tunetool, set those same cells to max (what ferocity said).

[FreshDA9]

I take it some of these will not be used in my ecu thus is why they are getting set to max?

Also the file i found was for a 5.7l i take it doesnt matter as long as i copy my origanl maps and data into the spots that are changed such as Maf curve, temp settings, VE, PE and so on.

[ferocity02]

When you flash in COS5 and then read the tune off the PCM, there will be many values that are out of range that will need to be fixed. Also if you want to disable certain features then the corresponding calibrations will need to be set to the max or min values.

[FreshDA9]

Ok so this only happens when flashing the COS5 i was reading it as it would happen with the 2002 OS flash as well.

[joecar]

The 2002 F-car OS should flash straight in with no problems... (you will still have to copy over your 12202088 tables... and make sure it runs on 12212156 at least as good as it did on 12202088... if it doesn't then you have to find out what went wrong).


With COS5/02020005, some of the tables will contain the wrong values after doing the cal-only flash from 12212156...

for example B3605 is replaced by B3647 which has the values that B3605 previously contained (which are wrong for B3647 since it has RPM on the vertical axis instead of ECT);

also, some of the new tables (A00xx), will be out of range (OOR), the Out-Of-Range tab will identify these to you (as will their blue dog-ear corners)... but also note that A0012 and A0013 will also be OOR (these two are not identified to you, but will have blue dog-ear corners)... you have to set all of these to in-range values...

note that the tunetool displays the closest max or min value for an OOR cell (and colors the corners blue)... when you set the OOR cell's value to max or min, the tunetool sees no change, so it does not save your edit... you have to set an in-range value other than max or min, save file, exit tunetool, re-start tunetool and if desired set max or min value on those cells.

Among other things, you have to do this:
- set A0002 to 100%.
- set B3647 such that in the last 2 or 3 columns (high MAP) the commanded fuel is sufficiently rich/safe.

[joecar]

More info: COS5.txt (http://forum.efilive.com/attachment.php?attachmentid=10875&d=1305643237)

[joecar]

Contents of COS5.txt:



===================================== COS5 notes =====================================

These notes are extracted from the COS5 thread on the forum.

Start from either of these OS's (with the same transmission as yours):
- 12225074 Australian Holden -> upgrades to COS5 01290005
- 12212156 Camaro/Firebird 2002 -> upgrades to COS5 02020005

NOTE: The latest COS5 calibrations are included when you install EFILive V7 software.


The COS allows adaptable spark (i.e. sliding between HO and LO tables depending on
detection of knock) even when the MAF is failed; to do this these parameters must
be set as follows:
- A0000 set to Disabled,
- A0002 set to 100%.


===================================== SETUP NOTES =====================================

All Custom Tables/Parameters:
OOR (out-of-range) cells have blue dogears in the 4 corners.
Fix all OOR cells (including in A0012, A0013), this is tricky, read the OOR forum threads.
A0012 and A0013 max display value is flaged as OOR, so fix these also.
The Custom tables/parameters use memory areas that were previously undefined and may contain
garbage values, so edit them to sane values in case you ever accidentally enable features.

A0003 TP VE Enable:
Set to disable (can be enabled later if you intend to run the TP VE Table).

A0008 OL ECT Commanded Fuel Multiplier:
Use warmup ECT vs BEN logs to adjust this table (adjust in OL).

A0014 IAT VE Multiplier:
Use seaonsonal IAT vs BEN logs to adjust this table (adjust in OLSD).

N20 monitor is done via the same input as the Valet mode;
once it is grounded then the two compensation tables become active, although,
there are two parameters to stop those two tables even if the N20 is on (A0017, A0018);
timing retard from A0016 will only function when table B5956 has a multiplier value of 1.00.

COS4 was going to be the N20 options only, but in the end it was possible to squeeze
everything in to one OS, though, on the later 2004+ OS's this might not be possible;
there is a few cars in Aus running COS4, it's been out for a long time, but these were
only used by workshops for N2O cars only.

B3647 OL Commanded Fuel:
This was previously B3605 which was ECT vs MAP, and is now RPM vs MAP, so it requires editing.
In OL, any B3647 cells that are stoich will enable STFT trimming (semi-open loop mode),
this is undesirable during any BEN correction of VE or MAF.


===================================== TP VE Table (A0007) =================================

Nearly all 2003+ OS's use DBW, it is not known if TP VE table would work too well on them.

The VE lookup pid only works when using it in [g*K/kPa] (if you do it in % it may report 0).

Given plenty of logging the BEN will be so spot on you'd think the WBO2 was stuck!

The one problem this does have is in an A4 transitioning in and out of Drive,
there is no detected load change for the VE, however that also has an advantage
too because the fueling remains constant and the spark/IAC handles the RPM drop.

Use the TP VE only in the area's you cannot get consistent MAP values in,
and then switch back to the MAP VE once things become steady.

Make sure DFCO is disabled.

TP VE Table setup:
0. Set A0003 TP VE Enable to disable.
1. You need to have a good VE table with BENS very close to 1.00.
2. You need to change your preferences to view VE Table in [g*K/kPa] units.
3. Log a pid called GM.VETABLE_DMA to build your initial TP VE table.
4. Create a map that has the same dimensions as the TP VE Table and use the PID above as the Data.
5. Go for a drive and log, try and hit as many as possible points in the TP VE Table map.
6. Now copy/paste the values in the TP VE Table map to the TP VE Table in your COS5 tune file
(experiment with the copy and fill function and the the Linear Fill functions).

After the initial build of the TP VE Table, enable the TP VE Table,
change the TP VE Table map created above so that the data is now using the BEN factor;
this allows you to fine tune that table going forward.

Add a little to your TP table that you have plotted to ensure it isn't lean.

You will need to play with cut in/out points for switching between TP and MAP VE Tables;
for initial tuning, run exclusively off the TP VE Table, this allows you to apply BEN corrections;
to use the COS5 on an ongoing basis, apply BEN corrections both tables in their active regions.

If you get bucking at low RPM low throttle, check your base spark and high octane spark tables;
if they are way different where the bucking occurs try closing the gap between them.

================================================== ==============================================