cax error after V7.5 update (build 232)

[O1Z06]

Would have posted in cax forum but didn't see any recent activity. Please move as required.

Just updated to V7.5.7.233 and the .cax calibration address are now overlapping. I tried a fresh .cax and cal_link file. Any help would be appreciated.

Excluded
B9000
B9003
B9006
B9007
B9011
B9012
B9021

15145
15146
15147

[GMPX]

Yes there was changes to .cax file handling.

The first change was to check that *.cax definitions did not overlap with any existing EFILive calibrations. If a *.cax file has been set up so that it does overlap, then the final data that is written to the file is not necessarily what you would expect. That is because both calibrations will write to the file. The order in which they write to the file is non-deterministic, so it could be that you end up changing your user defined calibration's value which gets written to the file, then the built in EFILive calibration's value (which occupies the same memory location) gets written to the same memory location, overwriting the changes you thought you had made. If/when that happens it gets very frustrating very quickly if you don't realize what's happening.

The second change we made was to prevent calibrations being defined in the OS memory area. A mistyped address in a *.cax file can wreak havoc to an engine controller if the OS software is changed accidentally. The ECM's built in CRC corruption detection would not catch the problem because when saving the file (after the accidental OS change) EFILive updates the OS checksum so the ECM would never know it had a corrupt OS resulting in a bricked ECM. Note, the OS restriction does not apply the LS1B PCM.

Cheers,
Ross

[O1Z06]

Thanks Ross. That is interesting about how it works but a bit over my head. I would sometimes see B9021 get reset back to its default value after a write so I would just check it every time. So now I think I understand why it did that.

With the new changes in the .cax file handling, will I still be able to modify the hidden parameters? I really need the transient fueling tables, not so much the lean cruise but it came with the file joecar wrote.

Thanks,
Jesse

[joecar]

B9021 should be ok with 12212156/02020003/02020005.

[joecar]

Thinking about it, it would be better if B9021 was predefined rather than 3rd-party cax-defined

[O1Z06]

Hey Joe, so I was just looking over my 02020005.cax file and noticed that the addresses for B9014 and B9021 are the same, (B632). Also my cal_link link file does not have B9013 and B9021. What does the cal link file do?

Here is what I have:
{B9001} Stomp Make Up Fuel
{B9002} Impact Factor Modifier
{B9004} Boiling Time Modifier
{B9005} Wall Mass Factor
{B9008} DFCO Stomp Compensation TPS Min
{B9009} Stomp Compensation Delta Low Limit
{B9010} Stomp Compensation Delta Limit
{B9013} Stomp Compensation Delay
{B9014} Minimum Stomp Fuel
{B9100} Lean Cruise Enable

Here is the cax I was using and B9021 worked ok.
http://forum.efilive.com/showthread.php?9143-cax-file-updates/page2

When I had B9021, it would be located just below B4006 under fuel/injectors/parameters. I have attached my .cax and cal_link files in the first post. Please let me know if you see something obvious. I will try just the .cax b (just B9021) that Mick posted and report back.

UPDATE:

Loaded cax b and B9021 is working now but don't have the others.

[Highlander]

This new handling brought some issues with a couple of CAX files that I have....... Is there a way we can disable this check?

[kangsta]

This new handling brought some issues with a couple of CAX files that I have....... Is there a way we can disable this check?

what controller?

[Highlander]

E38

[O1Z06]

B9021 should be ok with 12212156/02020003/02020005.

Loaded Micks "cax b" and now have B9021 but would like to have all the transient modifiers. Im still trying to fix a lean spike on tip out.

[Highlander]

01z06

because all the data is now under fuel - dynamics section.

[O1Z06]

01z06

because all the data is now under fuel - dynamics section.

The modifiers for transient fuel based on airflow and the duplicate boiling/impact/stomp tables were under a new folder called transient fuel. The fuel/dynamics section was not changed.

[O1Z06]

Well, I think I got it sorted. I modified the .cax and removed all the overlapping addresses from post 1.

B9014 and B9021 are the ones that confused me the most because they had the same address but different type, units and factor.

[joecar]

+1 delete B9014 and keep B9021.

[O1Z06]

Made a few minor changes to the folders.

Joecar, please move this thread to the .cax forum if you want.

Cheers,
Jesse

[joecar]

Ok, moved.

[tinindian]

I got the ".cax errors" after upgrading to build 235, OS is 12212156. Error loading B9000, B9003, B9006, B9007, B9011, B9012, and B9100. Only B9100 is actually in the tune, Lean Cruise enable. How do I get rid of the error messages? And will I trash my PCM if I load a tune with EFILive giving me these error messages? I have the latest 12212156.cax file.

[O1Z06]

Use cax b above, it's for 12212156 os with the overlapping addresses removed.

[tinindian]

Ok, that worked (no more error messages), but B9100 is gone - Lean Cruise Enable. So is LC enabled all the time or never? Thanks.

[joecar]

LC is enabled only if you enable it and do a full flash, and set its operating parameters correctly.

[tinindian]

Ok, but I can't enable it because I loaded cax b above and B9100 (LC Enable) is gone. LC worked great, before I "upgraded" to build 235.

[joecar]

Take the [B9100] section from your old cax file and add it to the end of your new cax file...

[tinindian]

Ok. B9100 is back but predictably so is the error message on startup.

[joecar]

Post a screenshot, and post your cax file.

[kangsta]

upgrade to the latest version, then in settings there is an option to allow cax additions in other memory areas for older controllers. I dont have EFILive on this computer but if you have the latest version off the website have a look through the settings section and you will find it.

[joecar]

+1 what kangsta said (I forgot that this option got added)...

Edit->Properties->Options and see "Allow cax files to modify...".

[tinindian]

Works perfect now, thanks guys!!!

[O1Z06]

Can you try your original cax file with the "allow cax option" checked and see if you get any error messages?

[tinindian]

I loaded my original cax file and do not get the error message.

[tinindian]

Ok, the error message is back. I loaded COS5 and it works fine, 02020005. Then I copied the latest 12212156.cax, renamed it to 02020005.cax and put it here C:\Program Files\EFILive\V7.5\Calibrations. The option to "Allow *.cax Files..." is checked. Here is the error message:

[joecar]

The Allow Cax option only allows particular overlaps... and what B9000 is overlapping is not allowed.

[tinindian]

Ok, I think I got it. I copied 'cax b.cax' and renamed it to 02020005.cax, then pasted the B9100 section at the end. For some reason my PC didn't want to upload the .cax file so I added the .txt extension. Thanks Joe.

[joecar]

Ok, I think I got it. I copied 'cax b.cax' and renamed it to 02020005.cax, then pasted the B9100 section at the end. For some reason my PC didn't want to upload the .cax file so I added the .txt extension. Thanks Joe.Your cax file looks correct... did the tunetool load it without error (with the Allow cax option)...?

[tinindian]

It loaded w/o error (Allow cax option checked), thanks again.

[Chevy366]

How does one go about checking the .cax overlap? I did the Properties>Option>Allow .cax etc... and the tune loads without error now but it seems to still screw with the tune.

[Taz]

E38

My E38 *.cax files did not trigger the warning message, and all loaded properly.

What particular E38 parameter is triggering the warning message for you ?

[joecar]

How does one go about checking the .cax overlap? I did the Properties>Option>Allow .cax etc... and the tune loads without error now but it seems to still screw with the tune.Disable the Allow CAX option, if the tunetool complains when loading a file, then the cax file overlaps.

[Chevy366]

Disable the Allow CAX option, if the tunetool complains when loading a file, then the cax file overlaps.
Did that, and it does, once that occurs is that it? You can no longer use the .cax because of the overlap?
Why now? Use to the .cax had no problems?

[joecar]

If you enable the Allow Cax option then the tunetool should continue to allow the cax overlap as previous...

[RevGTO]

I have the same problem after updating this week. I selected the option to allow cax and downloaded tinindian's cax file above and I still get the warning B9000 not allowed, overlap, etc. every time I open a 12212156 tune file.

I haven't run a lean cruise tune in a few years, but with this problem, would it load into the PCM if I tried it?

[Highlander]

post the cax file.. i'll fix the error.

[RevGTO]

Found my error. Per post #10 in the cax update thread, I placed it in the configuration file. Moved it to the calibration file and deleted my old cax thread and now it loads without the warning. Thanks.

[Snipesy]

Apparently when you call something B8101 weird things happen. I took pixs.
19240

[GMPX]

Yeah don't use....

B8101 to B8106
OR
B8151 to B8156

These are used by the Virtual VE tables in various ECM's.

[Snipesy]

Yeah don't use....

B8101 to B8106
OR
B8151 to B8156

These are used by the Virtual VE tables in various ECM's.

Good to know. Of course most people probably wouldn't run into this issue. :rolleyes:

[joecar]

In a cax you would use table id's in the range B9000 to B9999 to avoid colliding with any predefined tables id's.

[Snipesy]

In a cax you would use table id's in the range B9000 to B9999 to avoid colliding with any predefined tables id's.

752 of those are currently occupied by the mess that is the DTC table. I suppose I could make everything higher than B10000 (assuming there isn't anything in those ranges). I know the program will accept the values, but I'm not sure if they will cause other hidden issues by adding another digit.

[GMPX]

752 of those are currently occupied by the mess that is the DTC table.
LOL yes, Bosch DTC tables are a joke.