RomRaider

Hey Easty - can you post up the XML templates for the other tables - I've found them for AZ1G101N, and MFB wants to test them out - would rather be consistent, and use one set of definitions.

Cheers

I'd love to except I want to fully verify my work before I release it.

I've already found one error in my work and I can't fully get my mind around it!

Maybe you can help me out a little?

Threshold A and B don't function the way I described earlier, if you could help verify the following I'd really appreciate it.

1. Additive A is applied to requested torque until Threshold A is exceeded (the reverse of what I thought before).

2. Once Threshold A is exceeded neither Additives are applied.

3. (assuming Threshold A hasn't been exceeded) If Requested Torque + Additive A exceeds Threshold B then Requested Torque + Additive A is capped to a max value equal to Threshold A.

4. If Requested Torque + Additive A is less than Threshold B then Additive B is applied to Requested Torque instead of Additive A and Requested Torque + Additive B is capped to a Max value equal to Threshold B.

To add to my confusion there's Two groups of per gear values at the top of the routine that calculates the thresholds and additives. The second group can only be active when the switch value equals 1 but for the switch value to equal 1 requested torque must exceed threshold A. But once this happens non of the additives are applied anyway..... Confused either I've missed something or Subaru have goofed up the logic but I'd have to say I've probably missed something. On the one other Rom that I have looked at the second group of values were set to 1's effectively disabling them any way so maybe it was a goof up by Subaru.

The thing is I can step through this and write it down but I can't grasp exactly what they're trying to achieve with this.

It Is Easy enough to force this routine to act in a Predictable way and to achieve the goals I wish and that is to set both thresholds to so they equal Max requested torque that way Additive B is Always used! Additive B can then be adjusted to give per gear requested torque compensation as you see fit (see pic below).

I fear that even after I figure all this out it's going to be to complicated for average Joe to tune anyway though I'm sure we could come up with a "how to".

This is how I think I'll set mine up...

Threshold A/B = 400(same as my max requested torque)

Additive A/B when not in S# mode =
1st gear requested torque +4
2nd gear requested torque +3
3rd gear requested torque +2
4/5th gear requested torque +1

Additive A/B in S# mode =
1st gear requested torque +40
2nd gear requested torque +30
3rd gear requested torque +20
4/5th gear requested torque +10

I hope test this latter today I'll let you know how it goes if successful I'll post def's.

I'll see if I can thoroughly trawl through the logic tonight, been stretched for time - I did see the two areas of logic dealing with the gear selection, pretty extensive routine...

Could this be some limp mode or valet key logic, is it called by any of the DTC routines?

I don't think so as it is added to requested torque from your accelerator tables, well that's what the code is telling me. I haven't been able verify this through logging yet I suspect it may be disabled in code somewhere. So I may well have wasted my time on this one!

No worries mate, you still did find Requested Torque limit based on Iam condition.

I'm not quite done yet I'll continue to look into it.

In fact ignore my last post I think you could be right there is a routine call in the logic and if it returns with a 1 in r0 it load zero into fr8 instead of requested torque these additives are then added to fr8, which in effect will disable it.

What's easiest way to tell if it's a dtc routine?

That's not always easy, but maybe you could look for a sub that calls into the subs that turn on and off the MIL...?

So this may be a silly question: this per gear requested torque stuff sounds exactly like the 2007 year drive by wire throttle delay - I'm wondering if there's some form of these tables in the 07 sti and wrx ecu.

My 2004 sti had no such delay and it behaves like a cable throttle. I'll post some accelerator pedal angle vs. Throttle plate angle logs soon

td-d, is this map also works in Legacy GT model?

such as AE5F301C~ 09-10 EDM Legacy GT

thanks for reply~

It is, I defined it a while ago but has more resolution. Let me find it when I am near the tuning PC

<table name="Requested Torque Limit Max IAM" category="Drive-by-Wire Throttle (DBW)" address="dd05c" type="3D" level="1" scaling="RequestedTorque(rawecuvalue)">
<table name="IAM" address="dd014" type="X Axis" elements="6" scaling="IgnitionAdvanceMultiplier(IAM)"/>
<table name="Engine Speed" address="dd02c" type="Y Axis" elements="12" scaling="RPM"/>
</table>

<table name="Requested Torque Limit Max IAT" category="Drive-by-Wire Throttle (DBW)" address="d3850" type="3D" level="1" scaling="RequestedTorque(rawecuvalue)">
<table name="Intake Temp(F)" address="d3814" type="X Axis" elements="6" scaling="Temperature(DegreesF)"/>
<table name="Engine Speed" address="d382c" type="Y Axis" elements="9" scaling="RPM"/>
</table>

Requesting for the ff as cars use 1 to 1.2 bar actuators

AZ1G202G
AZ1J500G
AZ1E400U

AZ1G202G

Requested_Torque_Limit_Max_IAM DD6F8
Requested_Torque_Limit_Max_IAM_X_Axis DD6E0
Requested_Torque_Limit_Max_IAM_Y_Axis DD6EC

AZ1J500G

Requested_Torque_Limit_Max_IAM DD6F4
Requested_Torque_Limit_Max_IAM_X_Axis DD6DC
Requested_Torque_Limit_Max_IAM_Y_Axis DD6E8

Not finding it on AZ1E400U