Joe,
That's right with the factor.
With the B9003 out of range.
In the cax file you can set the boundaries for the out of range check that EFILive uses. Look at the values in this table and consider what your max and min settings would be and input this data into the cax file. I have blue highlighted the settings that need adjusting to eliminate the out of range report of this parameter.
; Units Factor Offset Prec MinLimit MaxLimit MinUser MaxUser
; -------- -------------- ------ ---- -------- -------- -------- --------
SI_SLOT = m/sec 0.024993 0 3 0 2 0 2
Use something like this and as further testing continues you can tweak these min and max values if any other parameters fall out of range. When you open the tuning software and look at a parameter, in the top right hand corner of the screen you will see the new min and max limits that are set in the cax file.
Cheers
Mick
Last edited by MICK; September 26th, 2008 at 12:13 PM.
Rev it up, Drop the clutch, See what happens?
See post #21 and #22: showthread.php?p=79309#post79309
I'm trying to resolve which of 12208322.cax and 01270003.cax is correct info at lines 364/367 and 402/405.
Mick,
Question: should the COS files include lean cruise, or should I leave it out of the COS files...?
Joe there is a couple of ways to look at it.
It is easy to update the base family operating system .cax file, then copy and paste a file then rename it to a cos ID with the lean cruise.
Then the lean cruise will not work on the cos operating systems so there is no point adding it in but then you would have to edit the updates to the cos .cax files separately this will increase the work load and support.
Maybe we can just add the lean cruise in the cos for now to make it a little easier and folks can test weather it is a rumor or not.
Your call.
Rev it up, Drop the clutch, See what happens?