cos 5 on ls1b 411 n20 monitor not working

[Age08]

any have this problem im running cos5 on ls1b 411 pcm, i hooked up the red connector pin 56 to ground when my nitrious solenoid is on, attached is a copy of my program i have verified my wiring and changing the A0012/A0013 to zero any ideas on why its not working? LS1Bblazer_0000_n20.ctz

[joecar]

Fix these:

Out of Range calibration summary: 04:24:40 pm, Saturday May 16, 2015

EFILive Custom Calibrations
{A0001} Forced Octane Scaler Percentage, was out of range when loaded.
{A0002} Octane Scaler Limiter, was out of range when loaded.
{A0004} MAP Disable TPS VE Table, was out of range when loaded.
{A0005} RPM Disable TPS VE Table, was out of range when loaded.
{A0006} TPS Disable TPS VE Table, was out of range when loaded.
{A0011} PCM Input #1 Function, was out of range when loaded.
{A0007} TPS VE Table, contained one or more out of range values when loaded.
{A0009} Boost VE Table, contained one or more out of range values when loaded.
{A0010} Boost Timing Table, contained one or more out of range values when loaded.

( also I, would set A0012,13 to 512 mph, even if they're not used )

[joecar]

Did you verify by measuring the voltage at PCM red pid 56...?

[Age08]

I did, I even wired it ground bypass my switch, Whats weird is how it says they are out of range when example {A0011} even tho it is set to N20 monitor.

[darcy]

It's not set to N2O monitor - it's currently an incorrect value and the tune tool is trying to display something logical.
Set it to an alternative value, save, close and reopen the file and then set to your desired value.

[joecar]

You have to set those (listed in post #2) to in-range values...

it's a little tricky, read this:

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

then re-open tunetool, go to those same tables and insert the old in-range 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.

[Age08]

I have done it now to the tune, but haven't tested it yet. when i get a chance I'll let you know if it worked.

Thanks