Check my data logging

[dm79]

ok i think i have a000 fixed. i see how blk did it on mine. now working on others.

only thing im not sure on is the b3647 you said to copy the 100kpa column. and paste it into the other and rework table. still not sure how exactly. i dont have a 100 column. sorry guys im still new to this .

new tune file

[joecar]

Here is some info, some of it is COS5 specific, but the rest applies to all COS's: COS5.txt

[joecar]

The COS's retain adaptive spark when the MAF is disabled (sliding between HO and LO tables based on detected knock)...

so you don't really need to copy the HO table to the LO table (since this takes away any knock protection from the engine).

Also: 27° at high airmass might be too much advance, it's not safe unless dynamic compression drops a lot.

You also have A0000 enabled (this keeps the octane scaler to the A0001 value always regardless of knock)... you want to set A0000 to Disable.

[dm79]

i have it disabled. now it tells me only out of rage items are still a0001 and 2

[dm79]

and she started up and is running... although my oil pressure is not building up yet.

[joecar]

Fix all OOR items, including A0012 and A0013 (set those to say 500).

[ so you have figured out the OOR "trick"...? ]

Good job on getting it to start/run let us know what is going on with oil pressure.

[dm79]

im confused on th 10012 and 13. the valet ones. i have them set to 512. not sure what they should be at... i changed my a0001/2 to 50 and it didnt report it as out of range now

[joecar]

Set A0012, A0013 to 511.

Set A0001, A0002 to 99, save file, exit tunetool, re-start tunetool, set A0001, A0002 to 100, save file;


( the trick is shown here as explained in one of the links )

[joecar]

Look carefully at the sequence:

In the tables listed as OOR, see the cells marked with blue dog-ear corners, take note of the values, enter some value that is in range (like min+1 or max-1), do this on all tables, then save file, exit tunetool...

then open tunetool, go to those same tables and insert the old values back in those cells, save file, exit tunetool, reopen and verify no out-of-range messages.

Explanation: when the tunetool sees an OOR value, it displays the closest of min or max... when you then enter min or max, the tunetool thinks you did not edit the cells (since it compares what you entered to what it was displaying)... so you have to enter something different and save/exit, reopen and enter your proper min or max... little bit tricky.

the tunetool displays the closer of min or max value when a cell is OOR;
the tunetool saves a file only if there are changes, and it bases this on the displayed values;
so if the cell is OOR and you enter min or max, then the tunetool sees no change, so it does not save the change;
so you have to follow that specific sequence to correct OOR cells
( i.e. set value other than min or max, save, exit, restart, set value to min or max, save ).

[dm79]

here it is running. only thing is it sounds like its sucking in a lot of air. but its getting quitr now as it runs. anothr weird thing is neithr my external engine temp or oil pressur gauges are working.. same sender...