12592618 cax for 4l80e TCC unlock tables

[ddnspider]

I've got the above OS and updated the cax file to add the B9021 min injector pulse table. Now I'm trying to add the 4l80e TCC unlock tables to prevent the unlock at light load, but am getting some weird errors. I copied the below info from another member into my OS cax file but I get the error attached. I can't seem to upload a .cax file in my post to share. Can anyone tell me what I'm doing wrong?

24340



[D3001]
; Description
; --------------------------------------------------------------------------------------------------------
DESC.001 = The Low Speed TPS threshold will be used if the VSS is below this value.
DESC.002 =
DESC.003 =
;
;
; Seg Caption Major Minor Vis Dis 2D Grp
; --- ------------------------------- -------------------------- -------------------------- --- --- -- ---
VIEW = 4 "Min throttle mode - Low speed" "TCC" "Min Throttle TCC Release" 1 1 0 0
;
; Address(es) BitOff Bits Typ Inv
; -------------------------------- ------ ---- --- ---
ADDR = 1A006 0 16 SNM 0
;
; Units Factor Offset Prec MinLimit MaxLimit MinUser MaxUser
; --------- ------------- ------ ---- -------- -------- ------- -------
SI_SLOT = MPH 3.90625E-03 0 0 0 256 0 256
;
; Body Col Row
; -------------- -------------- --------------
ULABELS = . . .
;
; Enumerations
; -----------------------------------------------------------------------
SI_ENUM = .
IM_ENUM = .
;
; Units Labels
; ---------------- ------------------------------------------------------
SI_COL = .
IM_COL = .
;
SI_ROW = .
IM_ROW = .
; ================================================== =============================
[D3002]
; Description
; ----------------------------------------------------------------------------------------------------------
DESC.001 = The High Speed TPS threshold will be used if the VSS is above this value.
DESC.002 =
DESC.003 =
;
;
; Seg Caption Major Minor Vis Dis 2D Grp
; --- -------------------------------- -------------------------- -------------------------- --- --- -- ---
VIEW = 4 "Min throttle mode - High speed" "TCC" "Min Throttle TCC Release" 1 1 0 0
;
; Address(es) BitOff Bits Typ Inv
; -------------------------------- ------ ---- --- ---
ADDR = 1A008 0 16 SNM 0
;
; Units Factor Offset Prec MinLimit MaxLimit MinUser MaxUser
; ------------ ------------- ------ ---- -------- -------- ------- -------
SI_SLOT = MPH 3.90625E-03 0 0 0 256 0 256
;
; Body Col Row
; -------------- -------------- --------------
ULABELS = . . .
;
; Enumerations
; ---------------------------------------------------------------------------
SI_ENUM = .
IM_ENUM = .
;
; Units Labels
; ---------------- ----------------------------------------------------------
SI_COL = .
IM_COL = .
;
SI_ROW = .
IM_ROW = .
; ================================================== =================================
[D3003]
; Description
; --------------------------------------------------------------------------------------------------------
DESC.001 = Minimum Throttle Mode will enable if the TPS is below this value.
DESC.002 =
DESC.003 =
;
;
; Seg Caption Major Minor Vis Dis 2D Grp
; --- -------------------------------- --------------------------- -------------------------- --- --- -- ---
VIEW = 4 "Low Speed Min Throttle TPS Low" "TCC" "Min Throttle TCC Release" 1 1 0 0
;
; Address(es) BitOff Bits Typ Inv
; -------------------------------- ------ ---- --- ---
ADDR = 1A00A 0 16 UNM 0
;
; Units Factor Offset Prec MinLimit MaxLimit MinUser MaxUser
; --------- -------------- ------ ---- -------- -------- ------- -------
SI_SLOT = % 3.051758E-03 0 0 0 100 0 100
;
; Body Col Row
; -------------- -------------- --------------
ULABELS = . . .
;
; Enumerations
; -----------------------------------------------------------------------
SI_ENUM = .
IM_ENUM = .
;
; Units Labels
; ---------------- ------------------------------------------------------
SI_COL = .
IM_COL = .
;
SI_ROW = .
IM_ROW = .
; ================================================== =============================
[D3004]
; Description
; ----------------------------------------------------------------------------------------------------------
DESC.001 = Minimum Throttle Mode will disable if the TPS is above this value.
DESC.002 =
DESC.003 =
;
;
; Seg Caption Major Minor Vis Dis 2D Grp
; --- --------------------------------- --------------------------- -------------------------- --- --- -- ---
VIEW = 4 "Low Speed Min Throttle TPS High" "TCC" "Min Throttle TCC Release" 1 1 0 0
;
; Address(es) BitOff Bits Typ Inv
; -------------------------------- ------ ---- --- ---
ADDR = 1A00c 0 16 UNM 0
;
; Units Factor Offset Prec MinLimit MaxLimit MinUser MaxUser
; ------------ -------------- ------ ---- -------- -------- ------- -------
SI_SLOT = % 3.051758E-03 0 0 0 100 0 100
;
; Body Col Row
; -------------- -------------- --------------
ULABELS = . . .
;
; Enumerations
; ---------------------------------------------------------------------------
SI_ENUM = .
IM_ENUM = .
;
; Units Labels
; ---------------- ----------------------------------------------------------
SI_COL = .
IM_COL = .
;
SI_ROW = .
IM_ROW = .
; ================================================== =================================
[D3005]
; Description
; ---------------------------------------------------------------------------------------------------------
DESC.001 = Minimum Throttle Mode will enable if the TPS is below this value.
DESC.002 =
DESC.003 =
;
;
; Seg Caption Major Minor Vis Dis 2D Grp
; --- --------------------------------- --------------------------- -------------------------- --- --- -- ---
VIEW = 4 "High Speed Min Throttle TPS Low" "TCC" "Min Throttle TCC Release" 1 1 0 0
;
; Address(es) BitOff Bits Typ Inv
; -------------------------------- ------ ---- --- ---
ADDR = 1A00E 0 16 UNM 0
;
; Units Factor Offset Prec MinLimit MaxLimit MinUser MaxUser
; ------------ -------------- ------ ---- -------- -------- ------- -------
SI_SLOT = % 3.051758E-03 0 0 0 100 0 100
;
; Body Col Row
; -------------- -------------- --------------
ULABELS = . . .
;
; Enumerations
; ---------------------------------------------------------------------------
SI_ENUM = .
IM_ENUM = .
;
; Units Labels
; ---------------- ----------------------------------------------------------
SI_COL = .
IM_COL = .
;
SI_ROW = .
IM_ROW = .
; ================================================== =================================
[D3006]
; Description
; -----------------------------------------------------------------------------------------------------------
DESC.001 = Minimum Throttle Mode will disable if the TPS is above this value.
DESC.002 =
DESC.003 =
;
;
; Seg Caption Major Minor Vis Dis 2D Grp
; --- ---------------------------------- --------------------------- -------------------------- --- --- -- ---
VIEW = 4 "High Speed Min Throttle TPS High" "TCC" "Min Throttle TCC Release" 1 1 0 0
;
; Address(es) BitOff Bits Typ Inv
; -------------------------------- ------ ---- --- ---
ADDR = 1A010 0 16 UNM 0
;
; Units Factor Offset Prec MinLimit MaxLimit MinUser MaxUser
; ------------ -------------- ------ ---- -------- -------- ------- -------
SI_SLOT = % 3.051758E-03 0 0 0 100 0 100
;
; Body Col Row
; -------------- -------------- --------------
ULABELS = . . .
;
; Enumerations
; ---------------------------------------------------------------------------
SI_ENUM = .
IM_ENUM = .
;
; Units Labels
; ---------------- ----------------------------------------------------------
SI_COL = .
IM_COL = .
;
SI_ROW = .
IM_ROW = .
; ================================================== =================================

[ddnspider]

Bump for any help. I'm assuming I'm missing something obvious that I need to do.

[ddnspider]

Anyone?

[turbo_bu]

I believe the issue is that EFI Live is flagging these memory addresses as overlapping areas where it also has parameters. Thus, the software is trying to prevent you from accidentally making changes to the same section of memory. I have heard that this became an issue a while back, but I am not sure of the exact work around.

This might not help, but when I noticed this starting to pop up, I just made sure and stayed on an older version of software where this was not an issue.

[ddnspider]

I am on an older version of SW too. Dumb question, but I assume you can't just rename the names to something different that isn't used right?

[turbo_bu]

Yes, you can name the parameters any name as long as it is not used. Typically, most CAX files that I have seen have parameter names like D9xxx. Something that is way away from anything else in the calibration file.

It might be worth a try?

[ddnspider]

ill give it a shot and report back. If anyone else can confirm or has other info it would be much appreciated.

[ddnspider]

EDIT-- That didn't work. I tried all sorts of addresses and get the same overlap error.

[turbo_bu]

stupid question - which version are you using? I know you said older, but how old? FWIW - I am still running version 7.5.7 build 230. I can't remember which version they started to add the additional checks to CAX files.

[ddnspider]

I'm running 7.5.28. I don't see a build number anywhere on the "about tab of EFI Live".

[turbo_bu]

They might of changed how they label / track their versions. This version is from back ~2012. If you look at the setup.exe install file name, the information should be there too. For this version, the install file is: EFILiveV7.5.7.7.230_Setup.exe

[ddnspider]

I guess I don't understand where you're going. Are you saying an older version of the program would avoid this issue? Where would I get an old install file?

[turbo_bu]

Yes, that is my theory. I am pretty sure they older versions did not do these checks and thus wouldn't flag this CAX as an issue. I can try your CAX file to see if it loads on my older version. If it works we can try to figure out how to get you a copy of the older install files.

[ddnspider]

Yes, that is my theory. I am pretty sure they older versions did not do these checks and thus wouldn't flag this CAX as an issue. I can try your CAX file to see if it loads on my older version. If it works we can try to figure out how to get you a copy of the older install files.

That would be awesome, please let me know what you find out.

[turbo_bu]

Good news is that I was able to load your CAX file into this older version. It did come up with a warning about values out of range. But otherwise loaded and looks like you can make the changes to these addresses.2434424345

[ddnspider]

Awesome! Any concern with seeing valued out of range like that?

[joecar]

Somewhere in the V7 tunetool options/settings there is a check box to skip the overlap check... but take note thatbthe overlap check is saying the addresses for D3001-5 are incorrect, you have to find the right addresses.

[ddnspider]

I tried that and it still gives me the same error regardless of whether the box is checked or not. If you see above I've tried countless addresses and always get this error.

[turbo_bu]

ddnspider - sent you a copy of the old version. I hope it works for you. I did have one question about the CAX file you shared.

I have read about needing to do this for 4L80E segment swap files, but have never had to do this on a vehicle before. What I have seen, is that there are some variables that need changed as well as some guys talking about a couple of tables that also needs adjusted. Maybe changing the variables negates needing to make changes to the other tables??? The ones that I saw being changed had labels of TCC apply / release speed vs. TPS vs. gear (HPT labels). Let us know if you only needs these variables, or if there is more needed to take care of it.

[ddnspider]

I found my factory OS that can with a 4L80E. All I did was open both files and clicked on the segment swap and it copied over everything as a 4l80E tranmission instead of a 4l60E. I didn't have to change or set any variables when I did this swap. My understanding of the issue was from this thread:
https://forum.efilive.com/showthread.php?25078-4l80e-tcc-throttle-close-cax

[ddnspider]

The irony is thick....I can't open my own tune file with that older version of EFI Live. @turbo_bu did you actually open my own tune file or just didn't get an error with that cax file?

[ddnspider]

It says the .ctz file is not supported by that version of EFI Live.

[Supercharged111]

You can't have a version of EFILive that is older than the tune you're trying to open. Need to update your software.

[ddnspider]

Reread the thread. I'm using a newer version but turbo bu suggested I try an older version to see if it got past the cax table errors I'm seeing. I need help getting the trans tables in the cax file not to throw an error.

[Supercharged111]

If that's the case, I think you'll need to use the old software to pull the new tune off the PCM (so flash new tune with new software to PCM first). Don't just try to look at the new tune through the old software if that makes sense.

[ddnspider]

Haha I literally said the same thing in PM last night. I'm not convinced that's going to solve my problem but it's worth a shot. I wish some of the OG cax experts/vrrators were still around to help.

[turbo_bu]

ddnspider .... I opened up an existing file that I had with the same OS as yours. I knew that this older version would not touch your newer CTZ file. Unfortunately, I think that the newer version of EFILive will NOT save to an older version. One option is to use something like PCMHammer, or LSDroid to read your file as a binary. Both the newer and older versions of EFILive will read in *.bin files.

[ddnspider]

ddnspider .... I opened up an existing file that I had with the same OS as yours. I knew that this older version would not touch your newer CTZ file. Unfortunately, I think that the newer version of EFILive will NOT save to an older version. One option is to use something like PCMHammer, or LSDroid to read your file as a binary. Both the newer and older versions of EFILive will read in *.bin files.

Im going to do a read on what's in the truck with the older version of EFI Live and try to apply the same cax file and see what it does. Since you were able to open a file with my OS, can you try and apply the cax and see if it gives you an error?

[Supercharged111]

ddnspider .... I opened up an existing file that I had with the same OS as yours. I knew that this older version would not touch your newer CTZ file. Unfortunately, I think that the newer version of EFILive will NOT save to an older version. One option is to use something like PCMHammer, or LSDroid to read your file as a binary. Both the newer and older versions of EFILive will read in *.bin files.

That would solve another issue I thought of: firmware. New and old versions of software probably won't talk to the same version of firmware. . . right?

[turbo_bu]

That would solve another issue I thought of: firmware. New and old versions of software probably won't talk to the same version of firmware. . . right?

Yes, I think this becomes the issue. You can use the older 7.5 all you want, but it probably won't connect with your V2 that has been updated with the newer version of firmware which matches your newer version of EFILive. I am pretty sure that you can not downgrade your firmware either on the V2 to match this older version of EFILive. The proverbial catch 22.

I was able to open my tune file which matches your OS and make some changes using your CAX file. It saved ok, and I was able to re-open it and the changes were there. I did not flash it into a PCM.

[ddnspider]

It wouldn't sync up with my V2....I'm still stuck. Nobody around any more that creates or edits cax files?

[nonnieselman]

You could try to contact jesse at Wait4Me performance. I think he does classes on CAX files

[ddnspider]

Given the amount of experts on here at one time who were helping modify people's tune files to add some of these hidden tables, I was hoping someone was still around that could assist instead of paying for a class on such a specific use case.

[nonnieselman]

Given the amount of experts on here at one time who were helping modify people's tune files to add some of these hidden tables, I was hoping someone was still around that could assist instead of paying for a class on such a specific use case.

I understand.
But the cax file deal is not something easy to do and is quite complicated to go into rarely chartered territory's.
I was just reading a tune off a buddys truck with his HPT and found out they have quite a bit more Torque converter table options :(

[ddnspider]

I understand.
But the cax file deal is not something easy to do and is quite complicated to go into rarely chartered territory's.
I was just reading a tune off a buddys truck with his HPT and found out they have quite a bit more Torque converter table options :(

I agree, I found the same thing. I have HPT as well, just don't really want to license the vehicle twice just for those tables. I saw this thread where a couple of experts have the experience to edit the files correctly and was hoping to catch someone still on here. Doesn't sound promising at the moment.
https://forum.efilive.com/showthread.php?25078-4l80e-tcc-throttle-close-cax

[turbo_bu]

ddnspider - I don't think the issue is with your CAX file. It is an issue with the "newer" version of EFILive flagging it. This is why I can use it with my older version. The issue now is either getting EFILive to not flag it, or just getting a read of your base file from your PCM so that we can edit it in the older version of EFILive.

The only "other" option that I would recommend is to use one of the open source tools (LSdroid or PCMHammer) to read your PCM. That will create a binary file which you can use with your CAX file and the older version of EFILive. After you make the changes, you can save it to a file format which is compatible with your newer version of EFILive.

[ddnspider]

ddnspider - I don't think the issue is with your CAX file. It is an issue with the "newer" version of EFILive flagging it. This is why I can use it with my older version. The issue now is either getting EFILive to not flag it, or just getting a read of your base file from your PCM so that we can edit it in the older version of EFILive.

The only "other" option that I would recommend is to use one of the open source tools (LSdroid or PCMHammer) to read your PCM. That will create a binary file which you can use with your CAX file and the older version of EFILive. After you make the changes, you can save it to a file format which is compatible with your newer version of EFILive.

Dumb question....I am assuming I can register my V2 on multiple EFI Live PC's that run different versions of the tool without screwing anything up?

[turbo_bu]

Yes, you can install more than one version of EFILive on your PC. The hang up is that each version of software is designed to only work with it's version of V2 firmware.

[ddnspider]

Yes, you can install more than one version of EFILive on your PC. The hang up is that each version of software is designed to only work with it's version of V2 firmware.
Then it sounds like I'm stuck if I have newer firmware on my V2. I haven't updated it in probably a couple of years but indont know how old that version is that you sent me the exe of.

[1FastBrick]

Then it sounds like I'm stuck if I have newer firmware on my V2. I haven't updated it in probably a couple of years but indont know how old that version is that you sent me the exe of.
You should be able to down grade the Firmware through the EFI Live explorer.

I don't have my cable with me to go through the steps but as long as you have the install file on your computer, You should be able to do it.

[ddnspider]

You should be able to down grade the Firmware through the EFI Live explorer.

I don't have my cable with me to go through the steps but as long as you have the install file on your computer, You should be able to do it.

But don't I need the old firmware as part of that? My 1 PC has v8 with explorer etc. I loaded another PC with the old V7, but how do I downgrade firmware and to what on which PC? ����

[1FastBrick]

But don't I need the old firmware as part of that? My 1 PC has v8 with explorer etc. I loaded another PC with the old V7, but how do I downgrade firmware and to what on which PC? ����

As long as the old PC has the old V7 Install file it will contain the firmware. You can go into the Efi Live Explorer and change it. You will erase what's in there and then you can load the other file.

I don't have my cable with me so I cant walk you through it. Some how installing an update on mine failed and left in the boot loop mode one time. I had to install an older file first and then upgrade it to make it work again.

[1FastBrick]

On this page you can change the firmware to match the older software. You can bring up the explorer even on the older 7.5
But I don't have a unit with me right now.

24372

[1FastBrick]

This is the best I can do to show you right now. Click the box in the right where I put the red arrow and go into the folder. Open the boot block folder and load the correct one for the Flash Scan and not the Auto Cal. on left hand side you will see all your details including what is currently loaded. Make sure you have the older version on the V7 computer and install that.

TO go back to the newer version Firmware, connect to other comp with newer software and do the same thing to update the Firmware.

24373

[ddnspider]

What are the odds I brick my V2 doing something like this? I.E. is this something done regularly or am I doing something not recommended by Efi Live?

[1FastBrick]

What are the odds I brick my V2 doing something like this? I.E. is this something done regularly or am I doing something not recommended by Efi Live?

Unlike the other guys that don't offer good support, have poor customer service, and in general are just flat out greedy...

EFI wanted there user experience to be different. I know in the early days this was sometimes needed for tuning business where if they needed a new feature like on the newest vehicle but it may have caused issues elsewhere in the software to flash older cars, they could revert back until the issue was resolved.

As for ODDS, I couldn't tell you. I don't believe you actually brick the module on this equipment. I think if anything you go into a dead pool mode were it just flashes the lights back and forth to let you know the unit is not in a useable state.

IF you want send them an email and ask about it. They have nothing to hide and the are not going to steer you down the wrong path.

[ddnspider]

That's a good idea. I'll drop them an email.

[1FastBrick]

Good deal!

[ddnspider]

Good thing I emailed them. They responded with:
EFILive does not allow you to roll back or downgrade firmware.
Please supply the cax you are trying to add and I'll have one of the engineers take a look.
"

I sent over my files so hopefully they can help.

[ddnspider]

HOLY HELPFUL. Tech support was AMAZING. They responded to my message almost immediately and started digging in with me. They took the cax file I had and reverse engineered the correct addresses in memory for my OS. Then provided me a cax8 file and even caught a bug in it and told me how to fix it. Additionally, they found a separate duplicate table from the B9021 which has been replaced by default with the B3402 table and explained the units to me. AMAZING support.

Now for this TCC min unlock stuff. Does anyone have any suggestions on how to setup this up to start with? There's 2 sets of values, a min and a max TPS and a min and max speed. I assume I just set the min and max to the same value which is above the TCC min apply speed and set the TPS to something very low. Sound right?

[nonnieselman]

I use my lockup in 2nd-4th gear in tow haul and have it setup like this.

[ddnspider]

I use my lockup in 2nd-4th gear in tow haul and have it setup like this.

Excellent, Ill give that a try but I only lockup in 4th so Ill set my mph higher. Are you using a stock stall?

[ddnspider]

Anyone ever see this? The MAF appears to be maxxed, but not at the max airflow of 512g/sec. It's like it reaches a certain amount and flatlines. 24375

[nonnieselman]

Excellent, Ill give that a try but I only lockup in 4th so Ill set my mph higher. Are you using a stock stall?

yea Stock stall speed converter from Transstar. Its a BU52 part number in a 2500HD. Locking it up in 2nd gear at the right time makes it pull heavy trailers very good. But i dont try and lock it up unless TCC Slip is less than 500 rpms.

[1FastBrick]

Good thing I emailed them. They responded with:
EFILive does not allow you to roll back or downgrade firmware.
Please supply the cax you are trying to add and I'll have one of the engineers take a look.
"

I sent over my files so hopefully they can help.

Good to know on the firmware for future reference. I am also glad you emailed first.

I see they also were very helpful in getting your file fixed up!!! That's also great to here.

[ddnspider]

Yup they were SUPER helpful!!!