88590015 - MUT 8A = 0-100% Throttle position

Reply Subscribe

Thread Tools

Search this Thread

Jan 30, 2009 | 08:06 AM

acamus

Thread Starter

Evolved Member

Joined: Mar 2008

Posts: 730

Likes: 3

From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude

88590015 - MUT 8A = 0-100% Throttle position

I guess BEZ has made mistake on this one.

For those who can read math
Throttle Position = 100/222(MUT_8A - 33) {%}

OBDII PID11 is calculated in below code sequence, for those who can read code.
88590015:

Code:

ROM:0003AA8A                 mov.l   @(h'24C,pc), r4 ; [0003ACD8] = MUT_8A
ROM:0003AA8C                 mov.w   @r4, r4
ROM:0003AA8E                 extu.w  r4, r4
ROM:0003AA90                 mov     #h'21, r5
ROM:0003AA92                 mov.l   @(h'240,pc), r10 ; [0003ACD4] = sub_F0C
ROM:0003AA94                 jsr     @r10 ; sub_F0C  ; If r4 >= r5, then r4 - r5 -> r0, else r0 = 0
ROM:0003AA96                 nop
ROM:0003AA98                 extu.w  r0, r1
ROM:0003AA9A                 mov     r1, r10
ROM:0003AA9C                 shll8   r10
ROM:0003AA9E                 sub     r1, r10
ROM:0003AAA0                 mov     r10, r4
ROM:0003AAA2                 mov.w   @(h'EC,pc), r5 ; [0003AB92] = h'DE
ROM:0003AAA4                 mov.l   @(h'70,pc), r10 ; [0003AB18] = sub_8C4
ROM:0003AAA6                 jsr     @r10 ; sub_8C4  ; r4/r5 -> r0
ROM:0003AAA8                 nop
ROM:0003AAAA                 extu.w  r0, r4
ROM:0003AAAC
ROM:0003AAAC loc_3AAAC:                              ; CODE XREF: PROCESS_MODE_01_OBD_REQUEST+1E0j
ROM:0003AAAC                                         ; PROCESS_MODE_01_OBD_REQUEST+1F0j
ROM:0003AAAC                 mov.l   @(h'22C,pc), r10 ; [0003ACDC] = sub_590
ROM:0003AAAE                 jsr     @r10 ; sub_590  ; constrain r4 to within 0xFF (#255)
ROM:0003AAB0                 nop
ROM:0003AAB2                 mov.l   @(h'20,pc), r11 ; [0003AAD4] = OBD_Buffer_A
ROM:0003AAB4                 mov.w   r0, @r11
ROM:0003AAB6                 bra     loc_3AB64
ROM:0003AAB8                 nop
ROM:0003AAB8 ; ----------------------------------------------------

Last edited by acamus; Jan 30, 2009 at 08:18 AM.

Jan 30, 2009 | 08:46 AM

Deepnine

Evolving Member

iTrader: (4)

Joined: Apr 2008

Posts: 186

Likes: 0

From: Germany

MUT_8A is load_error in Evoscan 2.5, what does it have to do with throttle position? Have i missed something?

Jan 30, 2009 | 08:56 AM

acamus

Thread Starter

Evolved Member

Joined: Mar 2008

Posts: 730

Likes: 3

From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude

EvoScan uses what BEZ_BASHNI has deciphered, I think he made a mistake on this one.

Jan 30, 2009 | 09:03 AM

Deepnine

Evolving Member

iTrader: (4)

Joined: Apr 2008

Posts: 186

Likes: 0

From: Germany

I see the other calculation, but i don't understand what is has to do with throttle position.
Throttle position is MUT_1F and not MUT_8A

What is MUT_8A by the way?

Jan 30, 2009 | 09:06 AM

acamus

Thread Starter

Evolved Member

Joined: Mar 2008

Posts: 730

Likes: 3

From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude

Speaking of 88590015, when you look at FFFF6ACC occurences, you will find that it is TPS with the offset.
MUT_17 is TPS ADC Voltage reading 0-5V

MUT_1F is ECU Load

Last edited by acamus; Jan 30, 2009 at 09:31 AM.

Jan 31, 2009 | 03:10 AM

Mattjin

Evolved Member

Joined: Apr 2008

Posts: 604

Likes: 0

From: Sydney, Australia

Acamus, do you know if anyone has found the MUT table equivalent for OBD outputs? I mean, when you connect a normal OBD2 scan tool to the car and view live data, it does not seem to use the MUT table. Changing the MUT table doesn't seem to effect these OBD outputs.

The reason for asking is that almost every OBD type device I have seen will always show TPS as absolute and not as a calibrated form for the evos. If MUT 8A is TPS scaled, then maybe there is a way to change the OBD output to show the calibrated TPS.

Feb 1, 2009 | 09:43 PM

acamus

Thread Starter

Evolved Member

Joined: Mar 2008

Posts: 730

Likes: 3

From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude

No, there is no "OBD Table" complement/equivalent, it is implemented like

Code:

switch(obd_mode)
{
      case mode_01:
             switch (obd_pid)
             {
                     case pid_01:
                         do_pid_01_work();
                         break;
                     .......
             }
      ..........
}

if you want to get the same value via PID 11 as via MUT_17 you can change the code posted above to:

Code:

ROM:0003AA8A                 mov.l   @(h'24C,pc), r4 ; [0003ACD8] = MUT_17
ROM:0003AA8C                 mov.w   @r4, r4
ROM:0003AA8E                 extu.w  r4, r4
ROM:0003AA90                 nop
ROM:0003AA92                 nop
ROM:0003AA94                 nop
ROM:0003AA96                 nop
ROM:0003AA98                 nop
ROM:0003AA9A                 nop
ROM:0003AA9C                 nop
ROM:0003AA9E                 nop
ROM:0003AAA0                 nop
ROM:0003AAA2                 mov.w   @(h'EC,pc), r5 ; [0003AB92] = h'64
ROM:0003AAA4                 mov.l   @(h'70,pc), r10 ; [0003AB18] = sub_8C4
ROM:0003AAA6                 jsr     @r10 ; sub_8C4  ; r4/r5 -> r0
ROM:0003AAA8                 nop
ROM:0003AAAA                 extu.w  r0, r4
ROM:0003AAAC
ROM:0003AAAC loc_3AAAC:                              ; CODE XREF: PROCESS_MODE_01_OBD_REQUEST+1E0j
ROM:0003AAAC                                         ; PROCESS_MODE_01_OBD_REQUEST+1F0j
ROM:0003AAAC                 mov.l   @(h'22C,pc), r10 ; [0003ACDC] = sub_590
ROM:0003AAAE                 jsr     @r10 ; sub_590  ; constrain r4 to within 0xFF (#255)
ROM:0003AAB0                 nop
ROM:0003AAB2                 mov.l   @(h'20,pc), r11 ; [0003AAD4] = OBD_Buffer_A
ROM:0003AAB4                 mov.w   r0, @r11
ROM:0003AAB6                 bra     loc_3AB64
ROM:0003AAB8                 nop

Last edited by acamus; Feb 2, 2009 at 03:59 AM.

Trending Topics

What modern tire is the closest thing to the Advan A046

9

356
Evo 5 Cylinder Head Replacement...

3

165
Jaraxles' Build Thread (Evo X)

424

63.0k
Help with fog lamps on 2018 sport es

3

216
2002 Lancer OZ Cruise Control Help - Please

6

3.6k

Feb 2, 2009 | 08:34 AM

Deepnine

Evolving Member

iTrader: (4)

Joined: Apr 2008

Posts: 186

Likes: 0

From: Germany

Quote:

Originally Posted by acamus

Speaking of 88590015, when you look at FFFF6ACC occurences, you will find that it is TPS with the offset.
MUT_17 is TPS ADC Voltage reading 0-5V

MUT_1F is ECU Load

Yes ofcause, i was a bit confused. Wasn't my best day, today it looks so simple, i don't know why i didn't understand that.

Feb 3, 2009 | 06:14 AM

eTiLiKo

Evolving Member

iTrader: (1)

Joined: Sep 2007

Posts: 354

Likes: 1

From: Italy

I think that is the same on 99860002,read my old post

https://www.evolutionm.net/forums/ec...ml#post6437353

Feb 3, 2009 | 06:21 AM

#10

acamus

Thread Starter

Evolved Member

Joined: Mar 2008

Posts: 730

Likes: 3

From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude

Yes it is true, for any ROM, I forgot to mention, I am just picking the "well known ROM" that anybody can search the code sequence, I am glad that you already posted the picture. I was about to create one.

Mar 7, 2009 | 05:12 AM

#11

eTiLiKo

Evolving Member

iTrader: (1)

Joined: Sep 2007

Posts: 354

Likes: 1

From: Italy

Have you discovered what is the true MUT for Load error?
It is very annoying tune boost on evo VII (99860002 and 9055001 also) without the load error log

For EVO IX (8884001x) instead MUT 8A works well.

EDIT :
In the MUT table,for 9986002 and 9055001 in MUT 8A i have 8803 and in MUT 8B 8BE3.
For 8884001x MUT 8A = 6ECF and MUT 8B = 6EC5
Could this be the problem?

Last edited by eTiLiKo; Mar 7, 2009 at 05:34 AM.

Mar 8, 2009 | 07:22 AM

#12

acamus

Thread Starter

Evolved Member

Joined: Mar 2008

Posts: 730

Likes: 3

From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude

Quote:

Originally Posted by eTiLiKo

Have you discovered what is the true MUT for Load error?
It is very annoying tune boost on evo VII (99860002 and 9055001 also) without the load error log

MUT 8A is universal, and is used equally in all ROMs.
differences in hex addresses of variables are expectant as the ROM size differs and code differs for different markets/engine setup.