EFIDynoTuning Forum

I thought you were having trouble reducing the pressure not raising it. Cant you adjust the shift pressure for each gear ?

Sounds like your static offset pressure needs to be reduced for that gear. Would be much safer than clipping it.

How low did you set the clip ?

yeah trouble reducing pressure for 3rd but 2nd is a bit soft for my liking.

Shifting into 3rd is nice now clipped at 25 down from 94 (in raw decimal). The whole drivetrain used to wind up and bounce a few times it was so firm. I reduced dynamic TV and TOT modifiers all the way down to zero with no improvement in certain situations. It has to be the static capacity as you mentioned. I'll be working on finding these and then setting the line pressure back where it was.

- SCINT1 = Static capacity TV intercept, first gear.
- SCINT2 = Static capacity TV intercept, second gear.
- SCINT3 = Static capacity TV intercept, third gear.
- SCINT4 = Static capacity TV intercept, fourth gear.
- SCSLP1 = Static capacity TV slope, first gear.
- SCSLP1SD = Static capacity TV slope, downshift to first gear.
- SCSLP2 = Static capacity TV slope, second gear.
- SCSLP2SD = Static capacity TV slope, downshift to second gear.
- SCSLP2SU = Static capacity TV slope, upshift to second gear.
- SCSLP3 = Static capacity TV slope, third gear.
- SCSLP3SD = Static capacity TV slope, downshift to third gear.
- SCSLP3SU = Static capacity TV slope, upshift to third gear.
- SCSLP4 = Static capacity TV slope, fourth gear.
- SCSLP4SU = Static capacity TV slope, upshift to fourth gear

What shift kit did you put in?
Did you modify the Calibration Plate?

superior shift kit and boost valve. f8 pump with transgo on/off TCC valve. No mods to the calibration plate

74psi to 18psi is a major cut.

you sure you don't have the converter locked during the shift and its causing it to bang? what is the actual logged tv pressure during the shift ?

the tc can absorb most of it but depending on speed it doesn't always unlock to make the shift. I had success forcing the unlock but that got really annoying. Ill take a look at the tv log and post later on

@wwhite any help locating the above static capacity constants would be appreciated. I see you did not find them in KID2 so I am trying to sort it out by comparing the code with the manual.

Any idea what address [Re2+ff5d] is referencing? I calculated it using wrap around but landed in code or outside the used program memory.

NVM Grok figured it out for me:

Any idea what address [Re2+ff5d] is referencing?
CODE:

6940: 45,d2,00,fc,e2 ad3w Re2,Rfc,d2 Re2 = b480;
......
7551: b3,e3,5d,ff,3a ldb R3a,[Re2+ff5d] R3a = [Re2+ff5d];
Answer
To determine what address [Re2+ff5d] is referencing, let's break down the information given:

Re2 is assigned the value b480 at address 6940.
At address 7551, the instruction ldb R3a, [Re2+ff5d] is loading a byte into R3a from the address calculated by Re2 + ff5d.

Here's how we calculate the referenced address:

Value of Re2: Re2 = 0xb480
Offset: ff5d in hexadecimal:
ff5d is 65373 in decimal. However, in most addressing modes, especially when dealing with offsets relative to a register, ff5d is treated as a two's complement signed number because it starts with ff.
ff5d as a signed 16-bit value is actually -163 (-0x00A3 in decimal).

So, we'll interpret this as:
0xb480 + (-163).
Address Calculation:
Convert b480 to decimal: 46208
46208 - 163 = 46045
Convert back to hexadecimal: 0xb3b5

Thus, the address [Re2+ff5d] would be referencing:

Address 0xB3B5.

its not rolling over to b3dd ?

open calculator in windows

click view >> programmer
click hex
click word

then just type it in

b480+ff5d == b3dd