I have expanded the range of operating systems supported in the cax files for the Transient Fuel Parameters.
Let me know if you see any issues and I will have a look.
Have fun Guys.
Mick
I have expanded the range of operating systems supported in the cax files for the Transient Fuel Parameters.
Let me know if you see any issues and I will have a look.
Have fun Guys.
Mick
Rev it up, Drop the clutch, See what happens?
Just thought I would include the original cax files.
Rev it up, Drop the clutch, See what happens?
holy g-force batman! good job. I'd be interested in a combined transient/lean cruise .cax for 12208322. I'll have to look into it tommorow when I have access to download some of this to my laptop.
1996 c1500 gen1e 5.7L - the "LS31", 24x CNP, LS2 coils, modified T56, 12200411PCM running COS3, zz4 cam, custom MPFI, etc. coming soon: Twin Turbos
Can I copy 12212156.cax to 02020005.cax...?
And does the lean cruise stuff apply to 02020005...?
Last edited by joecar; September 27th, 2008 at 07:26 AM.
Mick,
The 12212156.cax file contains this line:
; Calibration definition extension for OS 02020003
Is that ok...?
I thought 02020005 was derived from 12212156.
Joe
12212156.cax and 0202003.cax are identical files...
01290003.cax is different from these only in that B9003 max limit is 5.
Yes Joe,
Rename the file and have a look at the parameters. You will find more supported operating systems including the cos5's.
I picked out that B9007 was looking a little out, if you see a TP setting of 29.7 or something like that this is wrong. I will look more at it. In that cax I also disabled 2 other parameters because they were not right.
I believe that in the cos operating systems true closed loop is disabled to make use of the commanded open loop tables for fueling. Therefor lean cruise is non functional without O2 feedback.
To find the parameter tables in 12212156 it was a simple task. The parameter locations were increased 2 hex bits from 12202088. There was no Black Magic to find these parameters, I just used a term called pattern recognition.
I have done this for quite some time on the OBD1 code on the Holden's as there is lacking support for there definitions, so I might make it look easy. To explain a little. If you know how many rows and columns there are in a parameter table you can build a table then shift through the code to find all the possible outcomes.
This is one software that I use to shift through the code to find table locations, only catch is you need to be able to work in .bin format. This software will search the code for all tables as such.
http://www.evc.de/en/download/down_winols.asp
I will look at the other stuff.
Cheers
Mick
Rev it up, Drop the clutch, See what happens?