What other sorts of weird stuff do OOR cells do? Any reason why, when setting to max/min, it shows as OOR thus requiring the fix above?
What other sorts of weird stuff do OOR cells do? Any reason why, when setting to max/min, it shows as OOR thus requiring the fix above?
1998 GMC Sierra K1500 5.7/4L80E, longtubes, 411 w/COS 5, marine cam/intake, Whipple. 91 octane at 6000'.
1997 GMC Sierra K3500 7.4/4L80E, 411 w/COS 3, Whipple, small cam.
2004 Corvette Z06 with longtubes.
When the PCM encounters an OOR value, it has to do some extra processing to "fix" it...
this extra processing may be simple or it may be complex (you don't know what it is doing, it may be good or bad);
generally (in software), if you can minimize the execution path, you get better performance and you avoid any problems that the extra processing may introduce
( the most traveled path is the most debugged path )
For OOR cells, the tunetool displays max or min (whichever is closest)... and marks the cell as OOR;
so even tho you see max or min value, if the cell is marked then its real value is beyond the min-max range;
let's say if you see max and it is marked OOR, and you set it to max (i.e. you type in the max value), the tunetool does not save any change to the tunefile, that is why you have to do the special trick.