Misfire DTC and MAP thresholds

td-d · **Posted:** Tue Jul 03, 2012 8:10 am

I thought I would move this across to its own thread, I've found the Misfire DTC threshold table (which based on the number of misfire events, triggers a CEL) and the manifold pressure 2d table that also defines the point below which the CEL is not triggered.

The Ecuflash addresses for AZ1G101N are:

Code:

   <scaling name="Misfire DTC" units="units" toexpr="x" frexpr="x" format="%.0f" min="0" max="255" inc="1" storagetype="uint8" endian="big"/>

   <table name="Misfire Count MAP Threshold" category="Misfire" address="c5670" type="2D" level="1" scaling="Pressure (bar)">
      <table name="X" category="Misfire" address="c5638" type="X Axis" elements="14" scaling="RPM"/>
   </table>

   <table name="Misfire DTC Threshold" category="Misfire" address="c57bc" type="3D" level="1" scaling="Misfire DTC">
      <table name="Engine Load" address="c575c" type="X Axis" elements="10" scaling="EngineLoad(g/rev)1"/>
      <table name="Engine Speed" address="c5784" type="Y Axis" elements="14" scaling="RPM"/>
   </table>

To find it in the Forester roms is relatively straightforward - follow X-ref for the roughness_monitor parameter from the SSMGet routine for roughness_monitor 1 to its memory location:

Code:

ROM:00053510 SsmGet_Roughness_Monitor_Cylinder_1_P63:
ROM:00053510                                         ; DATA XREF: ROM:PtrSsmGet_Roughness_Monitor_Cylinder_1_P63o
ROM:00053510                 mov.l   #Ram_Roughness_Monitor_Cylinder_1, r2
ROM:00053512                 rts
ROM:00053514                 mov.b   @r2, r0

Following Ram_Roughness_Monitor_Cylinder_1 leads to the following memory location:

Code:

RAM:FFFF93E2 unk_FFFF93E2:   .res.b 1                ; DATA XREF: sub_67D88+28o
RAM:FFFF93E2                                         ; sub_67E0C:off_67F50o
RAM:FFFF93E3 unk_FFFF93E3:   .res.b 1                ; DATA XREF: sub_68116+42o
RAM:FFFF93E3                                         ; sub_68116+4Ao ...
RAM:FFFF93E4                 .res.b 1
RAM:FFFF93E5                 .res.b 1
RAM:FFFF93E6                 .res.b 1
RAM:FFFF93E7                 .res.b 1
RAM:FFFF93E8 Ram_Roughness_Monitor_Cylinder_1:.res.b 1
RAM:FFFF93E8                                         ; DATA XREF: ROM:SsmGet_Roughness_Monitor_Cylinder_1_P63o
RAM:FFFF93E8                                         ; ROM:off_536C8o ...
RAM:FFFF93E9 Roughness_Monitor_Cylinder_2:.res.b 1   ; DATA XREF: ROM:SsmGet_Roughness_Monitor_Cylinder_2_P64o
RAM:FFFF93E9                                         ; ROM:off_536CCo ...
RAM:FFFF93EA Ram_Roughness_Monitor_Cylinder_3:.res.b 1
RAM:FFFF93EA                                         ; DATA XREF: ROM:SsmGet_Roughness_Monitor_Cylinder_3_P69o
RAM:FFFF93EA                                         ; ROM:off_53704o ...
RAM:FFFF93EB Ram_Roughness_Monitor_Cylinder_4:.res.b 1
RAM:FFFF93EB                                         ; DATA XREF: ROM:SsmGet_Roughness_Monitor_Cylinder_4_P70o
RAM:FFFF93EB                                         ; ROM:off_53708o ...

Following the X-ref from the Ram variable two up from the Roughness_Monitor_1 location (i.e. unk_FFFF93E2 in this case) will take you to a routine that looks like so:

Code:

ROM:00067D88 sub_67D88:                              ; CODE XREF: sub_6563C+292p
ROM:00067D88                                         ; sub_659B4+30Ep
ROM:00067D88                                         ; DATA XREF: ...
ROM:00067D88                 sts.l   pr, @-r15
ROM:00067D8A                 fmov.s  fr15, @-r15
ROM:00067D8C                 stc.l   gbr, @-r15
ROM:00067D8E                 mov.l   #unk_FFFF94DF, r0
ROM:00067D90                 ldc     r0, gbr
ROM:00067D92                 add     #unk_FFFFFFFC, r15
ROM:00067D94                 mov.l   #E_Engine_Load_4ByteExt_E32, r2
ROM:00067D96                 fmov.s  @r2, fr15
ROM:00067D98                 mov.l   #unk_FFFF94FC, r2
ROM:00067D9A                 fmov.s  @r2, fr8
ROM:00067D9C                 mov.b   @(0,gbr), r0
ROM:00067D9E                 tst     #1, r0
ROM:00067DA0                 bt      loc_67DBE
ROM:00067DA2                 mov.l   #Table_Misfire_DTC_threshold, r4
ROM:00067DA4                 mov.l   #sub_BE93C, r2
ROM:00067DA6                 fmov    fr15, fr4
ROM:00067DA8                 jsr     @r2 ; sub_BE93C
ROM:00067DAA                 fmov    fr8, fr5
ROM:00067DAC                 mov.b   r0, @(h'86,gbr)
ROM:00067DAE                 mov.b   @(h'86,gbr), r0 ; FFFF9565
ROM:00067DB0                 mov.l   #unk_FFFF93E2, r4
ROM:00067DB2                 mov.b   @r4, r2
ROM:00067DB4                 cmp/hs  r2, r0
ROM:00067DB6                 bt      loc_67DBE
ROM:00067DB8                 mov.b   @(h'86,gbr), r0
ROM:00067DBA                 mov.l   r0, @r15
ROM:00067DBC                 mov.b   r0, @r4

The first 3D table is the DTC threshold table.

td-d · **Posted:** Tue Jul 03, 2012 8:10 am

If you follow the Xref back from the 3D table to the data location, you will see a 2D table being referenced further down (with a number of float values above it):

Code:

ROM:00067F1C off_67F1C:      .data.l unk_FFFF90FC    ; DATA XREF: sub_67BDE+F4r
ROM:00067F1C                                         ; sub_67BDE+10Er
ROM:00067F20 off_67F20:      .data.l sub_BE550       ; DATA XREF: sub_67BDE+102r
ROM:00067F20                                         ; sub_67BDE:loc_67D2Ar ...
ROM:00067F24 off_67F24:      .data.l loc_C3DB6       ; DATA XREF: sub_67BDE+134r
ROM:00067F28 off_67F28:      .data.l unk_FFFF93E0    ; DATA XREF: sub_67BDE+150r
ROM:00067F28                                         ; sub_67BDE+158r ...
ROM:00067F2C off_67F2C:      .data.l E_Manifold_Relative_Sea_Level_Pressure_4byteExt_E52
ROM:00067F2C                                         ; DATA XREF: sub_67D5Cr
ROM:00067F2C                                         ; sub_67E0C+26r
ROM:00067F30 off_67F30:      .data.l unk_FFFF94D8    ; DATA XREF: sub_67D5C+4r
ROM:00067F30                                         ; sub_67D5C:loc_67D76r
ROM:00067F34 off_67F34:      .data.l flt_C4544       ; DATA XREF: sub_67D5C+Ar
ROM:00067F38 off_67F38:      .data.l flt_C4548       ; DATA XREF: sub_67D5C+12r
ROM:00067F3C off_67F3C:      .data.l unk_FFFF94DF    ; DATA XREF: sub_67D88+6r
ROM:00067F40 off_67F40:      .data.l E_Engine_Load_4ByteExt_E32 ; DATA XREF: sub_67D88+Cr
ROM:00067F44 off_67F44:      .data.l unk_FFFF94FC    ; DATA XREF: sub_67D88+10r
ROM:00067F48 off_67F48:      .data.l Table_Misfire_DTC_threshold ; DATA XREF: sub_67D88+1Ar
ROM:00067F4C off_67F4C:      .data.l sub_BE93C       ; DATA XREF: sub_67D88+1Cr
ROM:00067F50 off_67F50:      .data.l unk_FFFF93E2    ; DATA XREF: sub_67D88+28r
ROM:00067F54 off_67F54:      .data.l unk_FFFF69F8    ; DATA XREF: sub_67DCA+6r
ROM:00067F58 off_67F58:      .data.l sub_23D00       ; DATA XREF: sub_67DCA+8r
ROM:00067F5C off_67F5C:      .data.l sub_22BA4       ; DATA XREF: sub_67DCA+Er
ROM:00067F5C                                         ; sub_67E0C+2Cr
ROM:00067F60 off_67F60:      .data.l word_C3F42      ; DATA XREF: sub_67DCA+1Ar
ROM:00067F64 off_67F64:      .data.l byte_C3F44      ; DATA XREF: sub_67DCA:loc_67DEAr
ROM:00067F68 off_67F68:      .data.l unk_FFFF94D9    ; DATA XREF: sub_67DCA:loc_67DFCr
ROM:00067F6C off_67F6C:      .data.l unk_FFFF93DC    ; DATA XREF: sub_67E0C+14r
ROM:00067F70 off_67F70:      .data.l Ram_Vehicle_Speed_0 ; DATA XREF: sub_67E0C+1Ar
ROM:00067F74 off_67F74:      .data.l unk_FFFF94DC    ; DATA XREF: sub_67E0C+1Er
ROM:00067F74                                         ; sub_67E0C+34r ...
ROM:00067F78 off_67F78:      .data.l flt_C4550       ; DATA XREF: sub_67E0C+46r
ROM:00067F7C off_67F7C:      .data.l unk_FFFF9584    ; DATA XREF: sub_67E0C+4Ar
ROM:00067F7C                                         ; sub_67E0C+60r ...
ROM:00067F80 off_67F80:      .data.l flt_C4558       ; DATA XREF: sub_67E0C+50r
ROM:00067F84 off_67F84:      .data.l word_858CC      ; DATA XREF: sub_67E0C+56r
ROM:00067F88 off_67F88:      .data.l flt_C454C       ; DATA XREF: sub_67E0C:loc_67E68r
ROM:00067F8C off_67F8C:      .data.l flt_C4554       ; DATA XREF: sub_67E0C+66r
ROM:00067F90 off_67F90:      .data.l Table_Misfire_Count_MAP_Threshold
ROM:00067F90                                         ; DATA XREF: sub_67E0C+6Er
ROM:00067F94 off_67F94:      .data.l Fun_GetMapValue2D_8B_16B_Float
ROM:00067F94                                         ; DATA XREF: sub_67E0C:loc_67E7Cr
ROM:00067F98 off_67F98:      .data.l sub_BE61C       ; DATA XREF: sub_67E0C+7Ar
ROM:00067F9C off_67F9C:      .data.l unk_FFFF8FF0    ; DATA XREF: sub_67E0C+8Ar
ROM:00067FA0 off_67FA0:      .data.l unk_FFFF90C0    ; DATA XREF: sub_67E0C+96r
ROM:00067FA0                                         ; sub_67E0C+A8r

This is the Misfire_Count_MAP_Threshold

Code:

ROM:000858C0 Table_Misfire_Count_MAP_Threshold:.data.w h'E ; DATA XREF: sub_67E0C+6Eo
ROM:000858C0                                         ; sub_67E0C:off_67F90o
ROM:000858C2                 .data.w 0
ROM:000858C4                 .data.l Misfire_Count_MAP_Threshold_Y_Axis
ROM:000858C8                 .data.l Misfire_Count_MAP_Threshold

td-d · **Posted:** Tue Jul 03, 2012 8:11 am

To find it in the STI's is slightly trickier. To find the DTC threshold table, use exactly the same process with the roughness monitor variables.

Here are the raw tables for AE5I910V:

The A/B tables are dependent on a logger variable - have not yet had the time to identify what the logic is. The 3D table is the threshold for the number of misfires required to trigger a DTC, whilst the the MAP threshold looks like it is a minimum value required for the counter to be activated (don't forget that the raw values are in mmHg). There are a bunch of other RPM values around the routine, which I've not had time to scrutinise, but I think would be RPM thresholds of some type.

Code:

ROM:000A2D70 Table_Misfire_DTC_Threshold:.data.w h'A ; DATA XREF: sub_7813C+1Ao
ROM:000A2D70                                         ; sub_7817E:off_7821Co
ROM:000A2D72                 .data.w h'E
ROM:000A2D74                 .data.l flt_C69D0
ROM:000A2D78                 .data.l flt_C69F8
ROM:000A2D7C                 .data.l byte_C6A30      ; = 1.48e2
ROM:000A2D80                 .data.l 0

ROM:000A28FC Misfire_Count_MAP_Threshold_B:.data.w h'E ; DATA XREF: sub_776B4+5Ao
ROM:000A28FC                                         ; sub_776B4:off_7778Co
ROM:000A28FE                 .data.w 0
ROM:000A2900                 .data.l flt_C5600
ROM:000A2904                 .data.l flt_C5638

ROM:000A2908 Misfire_Count_MAP_Threshold_A:.data.w h'E ; DATA XREF: sub_776B4+56o
ROM:000A2908                                         ; sub_776B4:off_77788o
ROM:000A290A                 .data.w 0
ROM:000A290C                 .data.l flt_C5670
ROM:000A2910                 .data.l flt_C56A8

To find the MAP A/B tables, take the X-ref back to the first JSR from the actual misfire DTC function itself, which will lead you a long string of subroutines being called:

Code:

ROM:00075E66 loc_75E66:                              ; CODE XREF: sub_75C4A+212j
ROM:00075E66                 mov.l   #sub_7741E, r3
ROM:00075E68                 jsr     @r3 ; sub_7741E
ROM:00075E6A                 nop
ROM:00075E6C                 mov.l   #sub_77668, r3
ROM:00075E6E                 jsr     @r3 ; sub_77668
ROM:00075E70                 nop
ROM:00075E72                 mov.l   #Misfire_Count_MAP_Threshold_A, r3
ROM:00075E74                 jsr     @r3 ; Misfire_Count_MAP_Threshold_A
ROM:00075E76                 nop
ROM:00075E78                 mov.l   #sub_777B0, r3
ROM:00075E7A                 jsr     @r3 ; sub_777B0
ROM:00075E7C                 nop
ROM:00075E7E                 mov.l   #sub_77888, r3
ROM:00075E80                 jsr     @r3 ; sub_77888
ROM:00075E82                 nop
ROM:00075E84                 mov.l   #sub_77904, r3
ROM:00075E86                 jsr     @r3 ; sub_77904
ROM:00075E88                 nop
ROM:00075E8A                 mov.l   #sub_77934, r3
ROM:00075E8C                 jsr     @r3 ; sub_77934
ROM:00075E8E                 nop
ROM:00075E90                 mov.l   #sub_77964, r3
ROM:00075E92                 jsr     @r3 ; sub_77964
ROM:00075E94                 nop
ROM:00075E96                 mov.l   #sub_77DF2, r3
ROM:00075E98                 jsr     @r3 ; sub_77DF2
ROM:00075E9A                 nop
ROM:00075E9C                 mov.l   #sub_77F7C, r3
ROM:00075E9E                 jsr     @r3 ; sub_77F7C
ROM:00075EA0                 nop
ROM:00075EA2                 mov.l   #sub_7802E, r3
ROM:00075EA4                 jsr     @r3 ; sub_7802E
ROM:00075EA6                 nop
ROM:00075EA8                 mov.l   #sub_79BFC, r3
ROM:00075EAA                 jsr     @r3 ; sub_79BFC
ROM:00075EAC                 nop
ROM:00075EAE                 mov.l   #sub_79CF0, r3
ROM:00075EB0                 jsr     @r3 ; sub_79CF0
ROM:00075EB2                 nop
ROM:00075EB4                 mov.l   #sub_7A062, r3
ROM:00075EB6                 jsr     @r3 ; sub_7A062
ROM:00075EB8                 nop
ROM:00075EBA                 mov.l   #sub_799F8, r3
ROM:00075EBC                 jsr     @r3 ; sub_799F8
ROM:00075EBE                 nop
ROM:00075EC0                 mov.l   #sub_7A45A, r3
ROM:00075EC2                 jsr     @r3 ; sub_7A45A
ROM:00075EC4                 nop
ROM:00075EC6                 mov.l   #sub_78110, r3
ROM:00075EC8                 jsr     @r3 ; sub_78110
ROM:00075ECA                 nop
ROM:00075ECC                 mov.l   #Func_Misfire_DTC_Threshold, r3
ROM:00075ECE                 jsr     @r3 ; Func_Misfire_DTC_Threshold
ROM:00075ED0                 nop

If you follow the earlier subroutines (in this case 15 subroutines above the DTC subroutine, and 3rd from the start) you will find a routine that looks like this:

Code:

ROM:000776B4 Misfire_Count_MAP_Threshold_A:          ; CODE XREF: sub_75C4A+22Ap
ROM:000776B4                                         ; sub_75FB4+2A0p
ROM:000776B4                                         ; DATA XREF: ...
ROM:000776B4                 sts.l   pr, @-r15
ROM:000776B6                 fmov.s  fr14, @-r15
ROM:000776B8                 fmov.s  fr15, @-r15
ROM:000776BA                 stc.l   gbr, @-r15
ROM:000776BC                 mov.l   #unk_FFFF9B94, r0
ROM:000776BE                 ldc     r0, gbr
ROM:000776C0                 add     #unk_FFFFFFFC, r15
ROM:000776C2                 mov.l   #unk_FFFF660C, r2
ROM:000776C4                 fmov.s  @r2, fr14
ROM:000776C6                 mov.l   #sub_22A10, r2
ROM:000776C8                 jsr     @r2 ; sub_22A10
ROM:000776CA                 nop
ROM:000776CC                 mov.b   r0, @r15
ROM:000776CE                 mov.l   #unk_FFFF9B94, r2
ROM:000776D0                 fmov.s  @r2, fr15
ROM:000776D2                 mov.l   #unk_FFFF8BAE, r2
ROM:000776D4                 mov.b   @r2, r6
ROM:000776D6                 mov.l   #flt_C436C, r2
ROM:000776D8                 fmov.s  @r2, fr8
ROM:000776DA                 fcmp/gt fr14, fr8
ROM:000776DC                 bt      loc_776E4
ROM:000776DE                 mov     #h'7F, r0 ; ''
ROM:000776E0                 bra     loc_776F0
ROM:000776E2                 or.b    #1, @(r0,gbr)
ROM:000776E4 ; ---------------------------------------------------------------------------
ROM:000776E4
ROM:000776E4 loc_776E4:                              ; CODE XREF: Misfire_Count_MAP_Threshold_A+28j
ROM:000776E4                 mov.l   #flt_C4368, r2
ROM:000776E6                 fmov.s  @r2, fr8
ROM:000776E8                 fcmp/gt fr14, fr8
ROM:000776EA                 bf      loc_776F0
ROM:000776EC                 mov     #h'7F, r0 ; ''
ROM:000776EE                 and.b   #h'FE, @(r0,gbr)
ROM:000776F0
ROM:000776F0 loc_776F0:                              ; CODE XREF: Misfire_Count_MAP_Threshold_A+2Cj
ROM:000776F0                                         ; Misfire_Count_MAP_Threshold_A+36j
ROM:000776F0                 mov.b   @r15, r0
ROM:000776F2                 cmp/eq  #1, r0
ROM:000776F4                 bf      loc_77790
ROM:000776F6                 mov.b   @(h'7F,gbr), r0
ROM:000776F8                 tst     #1, r0
ROM:000776FA                 bt      loc_77708
ROM:000776FC                 tst     r6, r6
ROM:000776FE                 mov.l   #word_A28F0, r4
ROM:00077700                 bf      loc_77798
ROM:00077702                 mov.l   #word_A28E4, r4
ROM:00077704                 bra     loc_77798
ROM:00077706                 nop
ROM:00077708 ; ---------------------------------------------------------------------------
ROM:00077708
ROM:00077708 loc_77708:                              ; CODE XREF: Misfire_Count_MAP_Threshold_A+46j
ROM:00077708                 tst     r6, r6
ROM:0007770A                 mov.l   #Table_Misfire_Count_MAP_Threshold_A, r4
ROM:0007770C                 bf      loc_77798
ROM:0007770E                 mov.l   #Table_Misfire_Count_MAP_Threshold_B, r4
ROM:00077710                 bra     loc_77798
ROM:00077712                 nop

There are 4 sets of 2D tables - the last ones (middle if you view the subroutine graphically) are the misfire tables. I'm not yet sure what the variables being tested as to which 'set' of tables are used yet.

Bamofo · **Joined:** Mon Jul 02, 2007 7:46 am **Posts:** 430

@TD-D - How would one take this to disable it for idle. set it to a super high value? This is per trip I assume too?

I have an 06 WRX that i mapped this out for but i want to make sure i understand the context.

Also can you confirm both of these for for me if you have a second

ROM: A8DH202X
1) Misfire DTC Threshold
Z = c5680
X = c5620
Y = c5648

2) Misfire Cout MAP Threshold
C52b8
14 elements - c5280

The Misfire Count... IS that setup to only look at misfire below that Pressure? You have it in BAR.. I put it in PSI and its showing under 3.60 PSI. Just makign sure i understand that too. I can map it out for other cars too its a very unique looking map.

td-d · **Posted:** Fri Jul 13, 2018 5:01 am

Yup - you want to increase the threshold for setups like lightened flywheels.

The MAP value is the minimum MAP for misfire to be picked up - i.e. above it.

Addresses are correct.

Bamofo · **Joined:** Mon Jul 02, 2007 7:46 am **Posts:** 430

td-d wrote:

Yup - you want to increase the threshold for setups like lightened flywheels.

The MAP value is the minimum MAP for misfire to be picked up - i.e. above it.

Addresses are correct.

To make this more clear, Are you saying that the MAP value needs to be above this threshold to start counting towards the 3D misfire table? I would have thought the opposite. So please let me know which is correct. These are great finds btw.. I need to just find all the cool posts from you and map it out across all cars i can.. Thanks TD

Merp · **Joined:** Thu Jul 23, 2009 1:46 pm **Posts:** 863

Excellent work! :mrgreen:

Bamofo · **Joined:** Mon Jul 02, 2007 7:46 am **Posts:** 430

@td-d

Do you see any IAT / ECT / On/off switch around this functionality. Instead of setting the misfire thresholds higher im interested in just turning it off all together for some built motors.... or on cars that are low compression anyways...

Im not able to turn off the misfire CEL it seems to be part of a routine that makes the ECU really angry.

Let me know... 06WRX is my test rom if you have it open... but anything you have show me and ill find it in my rom.

td-d · **Posted:** Thu Feb 14, 2019 9:00 am

Bamofo wrote:

@td-d

Do you see any IAT / ECT / On/off switch around this functionality. Instead of setting the misfire thresholds higher im interested in just turning it off all together for some built motors.... or on cars that are low compression anyways...

Not really - but I guess you could just hack the code to branch straight over the table - it checks a certain parameter and then skips the table if it's not equal to 1. Change the bf/s to a bra command, and it will skip over the table.

Bamofo · **Joined:** Mon Jul 02, 2007 7:46 am **Posts:** 430

is The parameter a flag that’s preset. Or is it an active variable.

td-d · **Posted:** Thu Feb 14, 2019 9:53 am

Not a preset - it check a specific bit of a variable to see if it's set to 0 or 1.

Bamofo · **Joined:** Mon Jul 02, 2007 7:46 am **Posts:** 430

td-d wrote:

Yup - you want to increase the threshold for setups like lightened flywheels.

The MAP value is the minimum MAP for misfire to be picked up - i.e. above it.

Addresses are correct.

Is it absolute pressure? or PSI... 3psi isnt when its misfiring i dont think... its either idle or cruise...

legaulois · **Posted:** Thu Jun 30, 2022 9:33 am

ROM: AZ1J500G
1) Misfire DTC Threshold
<map name="Misfire DTC Threshold1" type="3" class="Misfire">
<rows scaling="EF32BITBASE_EngineSpeed(RPM)1" count="14" offset="#C5A44"/>
<cols scaling="EF32BITBASE_EngineLoad(g/rev)1" count="10" offset="#C5A1C"/>
<data offset="#C5A7C" format="%.0f"/>
</map>

2) Misfire Cout MAP Threshold
<map name="Misfire Cout MAP Threshold A" type="2" class="Misfire">
<rows scaling="EF32BITBASE_EngineSpeed(RPM)1" count="14" offset="#C49BC"/>
<data offset="#C49F4" storagetype="float" format="%.0f"/>
</map>
and
<map name="Misfire Cout MAP Threshold B" type="2" class="Misfire">
<rows scaling="EF32BITBASE_EngineSpeed(RPM)1" count="14" offset="#C494C"/>
<data offset="#C4984" storagetype="float" format="%.0f"/>
</map>

mech · **Joined:** Mon Jun 27, 2022 1:03 am **Posts:** 12

A8DK100I

Code:

<table name="Misfire Count MAP Threshold" category="Misfire" address="C52FC" type="2D" level="1" scaling="Pressure (bar)">
      <table name="X" category="Misfire" address="C52C4" type="X Axis" elements="14" scaling="RPM"/>
      </table>

      <table name="Misfire DTC Threshold" category="Misfire" address="C582C" type="3D" level="1" scaling="Misfire DTC">
      <table name="Engine Load" address="C57CC" type="X Axis" elements="10" scaling="EngineLoad(g/rev)1"/>
      <table name="Engine Speed" address="C57F4" type="Y Axis" elements="14" scaling="RPM"/>
      </table>

Knifey · **Joined:** Thu Nov 25, 2010 5:50 am **Posts:** 16

Does anyone have these tables for A8DK101X?

RomRaider

Misfire DTC and MAP thresholds

Who is online