PDA

View Full Version : need B9021 for 01250003



BLK02WS6
November 14th, 2011, 02:25 PM
Is there a .cax available to give me table B9021 for 01250003? Thanks!

Lextech
November 15th, 2011, 03:00 AM
I have looked through all of my stuff. I don't have one---That doesn't mean one doesn't exist. What year OS is that one based off of?

Jeff

BLK02WS6
November 15th, 2011, 01:07 PM
Thanks for looking! It is based on a 2001 OS...

Ninety8C5
November 15th, 2011, 04:04 PM
I had this cax file, but I don't know what is in it.

joecar
November 16th, 2011, 08:05 AM
The only cax files I have for B9021 are for 12212156 and 12202088...

B9021 has not been yet reverse-engineered inother files yet.

BLK02WS6
November 16th, 2011, 01:15 PM
The only cax files I have for B9021 are for 12212156 and 12202088...

B9021 has not been yet reverse-engineered inother files yet.

Just out of curiosity, I took one of those and renamed it 01250003 - you can then see B9021 - is that not a good thing to do? I just did it on my home laptop to see what would happen, not on my tuning laptop...

BLK02WS6
November 16th, 2011, 01:20 PM
I had this cax file, but I don't know what is in it.

Not B9021...

5.7ute
November 16th, 2011, 05:14 PM
Here you go.

joecar
November 17th, 2011, 05:40 AM
Just out of curiosity, I took one of those and renamed it 01250003 - you can then see B9021 - is that not a good thing to do? I just did it on my home laptop to see what would happen, not on my tuning laptop...No, some of those tables are at different addresses causing all tables after those to be shifted also.

BLK02WS6
November 17th, 2011, 12:15 PM
Here you go.

Thanks!

BLK02WS6
November 17th, 2011, 12:16 PM
No, some of those tables are at different addresses causing all tables after those to be shifted also.

Okay, thanks!

5.7ute
November 17th, 2011, 07:45 PM
Thanks!
No worries.
There are three different addresses for B9021 that I have found so far. This makes it easy as it means I only had to write 3 cax files, & you just rename the correct one for your OS & away you go. The list is as follows.
Cax a
Stock OS
12202088
92111922
12208322
Custom OS
0125000x
0127000x
Cax b
Stock OS
12209203
12212156
12225074
Custom OS
0201000x
0202000x
0129000x
Cax c
Stock OS
12221588
12593358
Custom OS
0203000x
0204000x

joecar
November 18th, 2011, 11:00 AM
Cool :cheers: thanks Mick, narrowing B9021 like that makes it easier.

BLK02WS6
November 18th, 2011, 12:34 PM
Thanks - that is awesome! :cucumber:

MICK
November 21st, 2011, 02:48 AM
Nice work!!!! Great to see the good guys helping out pushing the edge.

Mick

joecar
November 21st, 2011, 04:21 AM
Hey MICK, how's it going mate :cheers:

5.7ute
October 3rd, 2013, 05:43 PM
Cax file updated with 12592618 & 12587603 files.

BLK02WS6
October 4th, 2013, 10:55 AM
Thanks for working on these 1MB cax files Mick! It is a huge help to some of us! Great job!

Lextech
October 4th, 2013, 11:38 AM
I'm confused. The first 3 cax files show they are for the same family of OS yet have different Hex addresses for the B9021 parameter???
1. The 12587603 cax shows it is for a 12202088 OS and a Hex address of C00E.
2. The 12592618 cax shows it is for a 12202088 OS and a Hex address of BD20.
3. The cax A shows it is for the 12202088 OS and a Hex address of B630.
4. The cax B shows it is for the 12209203 OS and a Hex address of B632.
5. The cax C shows it is for the 12221588 OS and a Hex address of B634.

Jeff

5.7ute
October 4th, 2013, 12:44 PM
I'm confused. The first 3 cax files show they are for the same family of OS yet have different Hex addresses for the B9021 parameter???
1. The 12587603 cax shows it is for a 12202088 OS and a Hex address of C00E.
2. The 12592618 cax shows it is for a 12202088 OS and a Hex address of BD20.
3. The cax A shows it is for the 12202088 OS and a Hex address of B630.
4. The cax B shows it is for the 12209203 OS and a Hex address of B632.
5. The cax C shows it is for the 12221588 OS and a Hex address of B634.

Jeff

Hi Jeff. I just did not edit the internal descriptions. These have no function at all.

Lextech
October 5th, 2013, 12:18 AM
Hi Jeff. I just did not edit the internal descriptions. These have no function at all.
Thanks Mick,
I thought that might be the case.

Jeff

warlock007
October 13th, 2013, 03:19 PM
Hello,

I have the OS (156) from CAX b but dont know how to use it, can i get the instructions for dummies:))

Thanks in advance

joecar
October 13th, 2013, 07:02 PM
Hello,

I have the OS (156) from CAX b but dont know how to use it, can i get the instructions for dummies:))

Thanks in advanceRename "cax b.cax" to "12212156.cax" and copy it to C:\Program Files\EFILive\V7.5\Calibrations.

joecar
September 12th, 2014, 12:38 AM
Adding 09373372.cax from 60lb-injector-woes-chicken-or-the-egg&p=210270 (https://forum.efilive.com/showthread.php?24606-60lb-injector-woes-chicken-or-the-egg&p=210270#post210270) post #26:

Thanks Mick.

Jim_PA
June 22nd, 2016, 04:11 AM
Cax file updated with 12592618 & 12587603 files.


If my original OS was 12587603, and I have since updated it to COS3 (4073003) will the 12587603 cax file work if I rename it to 4073003?

Taz
June 22nd, 2016, 04:49 AM
Hi Jim,

I has been awhile since I mapped out that OS - I think the COS has a leading zero (i.e. 04073003) - so if you rename it to 04073003 it should work - just use caution until you are certain.

Jim_PA
June 22nd, 2016, 05:31 AM
Hi Jim,

I has been awhile since I mapped out that OS - I think the COS has a leading zero (i.e. 04073003) - so if you rename it to 04073003 it should work - just use caution until you are certain.


Yes it does work! -- Joecar posted this last year about the same issue and I eventually found it -- Thanks! --

"take note: each COS has a base OEM OS, meaning that you can rename the OEM OS to the COS's id."

joecar
June 22nd, 2016, 05:54 AM
If my original OS was 12587603, and I have since updated it to COS3 (4073003) will the 12587603 cax file work if I rename it to 4073003?


Hi Jim,

I has been awhile since I mapped out that OS - I think the COS has a leading zero (i.e. 04073003) - so if you rename it to 04073003 it should work - just use caution until you are certain.


Yes it does work! -- Joecar posted this last year about the same issue and I eventually found it -- Thanks! --

"take note: each COS has a base OEM OS, meaning that you can rename the OEM OS to the COS's id."Yes, it should work, be sure to have the leading zero in the filename (04073003.cax) as Taz said.

LS1FREEK
December 10th, 2019, 12:04 PM
Help! Can anyone make this CAX for a 12579405 os? Or is there a good os that is compatible for my truck? 2003 LM7 Silverado.