question on custom os 0202005

[AllOutPerformance]

A0016 is set at 6 degrees
and monitor is on.
Yes i have back probed the pin and completley checked the circuit.
Went away from the switc even and went straight to battery ground after verifing the circuit was correct.

[AllOutPerformance]

2002custom.O.Snitrouscontrol4.8.tun

[AllOutPerformance]

Here is the tune.
Ive chhecked it 2 dozen times but maybe im missing something.

[AllOutPerformance]

Theres a few things i still need to change in just the base part of the tune.As i avent even made any pulls yet cause i havent gotten the nitrous control to work.
Gotta make some changes in the pe settings still and a few other tables.

[joecar]

It may not be working because the tunetool claims these are out of range:

Out of Range calibration summary: 10:28:27 pm, Tuesday May 10, 2011

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.
{A0017} N20 Monitor VE Multiplier Table RPM Enable, was out of range when loaded.
{A0018} N20 Monitor VE Multiplier Table MAP Enable, 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.
{A0015} N20 Monitor VE Multiplier, contained one or more out of range values when loaded.
{A0010} Boost Timing Table, contained one or more out of range values when loaded.

( and A0012/A0013 are OOR )

Give me a minute, I'll set those to in range values...

[Tordne]

I saw the same and was just setting up a test VM to load the latest GA software (I'm running pre-release and saw the same thing). Are you running the 7.5.6 Build 157 version Joe?

[AllOutPerformance]

Ok that doesn't show up when I bring up the tune.im version 157

[AllOutPerformance]

And how is it all out of range I didn't change any of that from the custom settings it comes with.

[Tordne]

You absolutely MUST manually change those setting as required. The COS doesn't come with any default settings. In fact the areas in memory that those custom tables occupy will contain whatever data was in the memory area of the cal-flash calibration that you flashed.

This is very significant and I think we may have found the issue . As the COS have been out for about 5 years now and no other reported issues I'm pretty confidant that this might just be the root cause right here.

[joecar]

I fixed the OOR values (there's a trick to doing this, see the History tab)...

try the attached file (when you open it, there should be no OOR values).