Official 2 byte thread!
 

Ok guys, since we are all sick and tired of going through a ton of threads to find the 2 byte HEX code and/or their appropriate MUT table locations for a particular 2-byte mod like 2-byte load, 2-byte RPM and 2-byte airflow (or you smart guys are sick of telling everyone over and over again,lol) I decided to make an official thread where i will just update this first post with any 2 byte locations you guys list for a particular ROM ID#.

I'm also adding the MUT 3D TABLE ADDRESS to the list.

NOTE:

If you currently don't have the 3D MUT TABLE installed in your ROM ID's XML file in ECUFLash (you may be using 1D tables for EACH 2byte mod location), download the attached file and save it onto your computer. Open it with NOTEPAD. Instructions on how to install it are inside the file.

DOWNLOAD 3D MUT TABLE HERE!


So if you've done some of these 2 byte mods already and don't mind looking in your tables to find the locations, it would help everyone out. I think this will save us ALL a great deal of time and be a viable resource. Thanks guys.



ATTENTION EVOSCAN USERS!
Be sure to edit the "RPM MUT 2 byte Mod" formula from 31.25*x to: 1000*x/256

OFFICIAL LIST:

88570008
2byte load
MUT 00 = 6B12
MUT 01 = 6B13

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow<-----------------------------------Need Confirmation
MUT 04 = 6B6A
MUT 05 = 6B6B

MUT 3D TABLE ADDRESS = 35920

88580013
2byte load
MUT 00 = 6B22
MUT 01 = 6B23

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow
MUT 04 = 6B7E
MUT 05 = 6B7F

MUT 3D TABLE ADDRESS = 373c4

88580014
2byte load
MUT 00 = 6B22
MUT 01 = 6B23

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow
MUT 04 = 6B7E
MUT 05 = 6B7F

MUT 3D TABLE ADDRESS = 373c4

88590013
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 = 6B1E
MUT 03 = 6B1F

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

88590014
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 = 6B1E
MUT 03 = 6B1F

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

88590015
2byte load
MUT 00 = 6B42
MUT 01 =6B43

2byte RPM
MUT 02 = 6B1E
MUT 03 = 6B1F

2byte AirFlow
MUT 04 = 6B9E
MUT 05 = 6B9F

MUT 3D TABLE ADDRESS = 3EE84

88840013
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 =
MUT 03 =

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

88840016
2byte load
MUT 00 = 6B22
MUT 01 = 6B23

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow
MUT 04 = 6B7E
MUT 05 =6B7F

MUT 3D TABLE ADDRESS = 377F8

88840017
2byte load
MUT 00 = 6B22
MUT 01 = 6B23

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow
MUT 04 = 6B7E
MUT 05 =6B7F

MUT 3D TABLE ADDRESS = 37944

90550001
2byte load
MUT 00 = 885C
MUT 01 = 885D

2byte RPM
MUT 02 = 883A
MUT 03 = 883B

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS = 2e9e0

92460000
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 =
MUT 03 =

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

93660005
2byte load
MUT 00 = 8960
MUT 01 = 8961

2byte RPM
MUT 02 = 893E
MUT 03 = 893F

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS = 33400


94170008
2byte load
MUT 00 = 895C
MUT 01 = 895D

2byte RPM
MUT 02 = 893A
MUT 03 = 893B

2byte AirFlow
MUT 04 = 89BA
MUT 05 = 89BB

MUT 3D TABLE ADDRESS = 38060
94170014
2byte load
MUT 00 = 895C
MUT 01 = 895D

2byte RPM
MUT 02 = 893A
MUT 03 = 893B

2byte AirFlow
MUT 04 = 89BA
MUT 05 = 89BB

MUT 3D TABLE ADDRESS = 38158

94170015
2byte load
MUT 00 = 895C
MUT 01 = 895D

2byte RPM
MUT 02 = 893A
MUT 03 = 893B

2byte AirFlow
MUT 04 = 89BA
MUT 05 = 89BB

MUT 3D TABLE ADDRESS = 38158

96420007
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 = 8962
MUT 03 = 8963

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

96420008
2byte load
MUT 00 = 8984
MUT 01 = 8985

2byte RPM
MUT 02 = 8962
MUT 03 = 8963

2byte AirFlow
MUT 04 = 89E2
MUT 05 = 89E3

MUT 3D TABLE ADDRESS = 39FA0

96420011
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 =
MUT 03 =

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

96530006
2byte load
MUT 00 = 898A
MUT 01 = 898B

2byte RPM
MUT 02 = 8962
MUT 03 = 8963

2byte AirFlow
MUT 04 = 89E2
MUT 05 = 89E3

MUT 3D TABLE ADDRESS = 36200


96940011
2byte load
MUT 00 = 899A
MUT 01 = 899B

2byte RPM
MUT 02 = 8976
MUT 03 = 8977

2byte AirFlow
MUT 04 = 89F6
MUT 05 = 89F7

MUT 3D TABLE ADDRESS = 3F314

98640014
2byte load
MUT 00 = 885C
MUT 01 = 885D

2byte RPM <-----------------------------------Need Confirmation
MUT 02 = 883A
MUT 03 = 883B

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS = 2E9E0

98640016
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 =
MUT 03 =

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS = 2EA9C

98650014
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 =
MUT 03 =

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

99270000
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 =
MUT 03 =

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

99860002
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 =
MUT 03 =

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS = 302D8

These are RPM's:
88580013 = 6AFE/6AFF
88580014 = 6AFE/6AFF
94170008 = 893A/893B
94170014 = 893A/893B
96940011 = 8976/8977
88590013 = 6B1E/6B1F
88590015 = 6B1E/6B1F
96420007 = 8962/8963

Thank you sir! Updated.

96940011- 2Byte Airflow = MUT 04- 89F6
MUT 05- 89F7

Updated. Thanks Tom.

88580013 and 14 2byte load = 0xFFFF6b22
88590013, 14 and 15 2byte load = 0xFFFF6b42

of the top of my head, but im pretty sure thats right.

you might want to include a section on howto configure up the MUT_TABLE :P

these are 2byte load for:

94170008=same as 94170014
94170015=same as 94170014
88590015= 6b42/6b43

88840016 (and 99.9% 88840017):

2byte load
MUT 00 = 6B28
MUT 01 = 6B29

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow (did not tried yet)
MUT 04 = 6074
MUT 05 = 6075

that looks like temp+baro corrected Al\lupo, maybe try 6b22/3 instead :)

Yep, that's true. Usually I log them both to look at boost (6B22 with mrfred boost management) and at timing (6B28). So we should specify if the listed addesses are for base load or corrected load... So:

2byte BASE load
MUT 00 = 6B22
MUT 01 = 6B23

2byte CORRECTED (temp+baro) load
MUT 00 = 6B28
MUT 01 = 6B29

BTW, could you please confirm 2 byte airflow addresses?

So the MUT table XML code is the same for all roms right? I'd just need to list the different MUT Table address' for each rom in the list? If so, I can just add the MUT Table code for the XML file and some simple instructions.

I know there are differences between the ROMs and I'm only used to my personal rom(94170014) so with these ROM ID's there is just one address for the loads, which i assume is MUT00?? Sorry for any ignorance.

Updated, hopefully i don't enter anything wrong ;) Thanks for the fast responses guys, we'll have this filled up in no time and you can all link the noob's here haha.


Since 94170008,94170014 and 94170015 seem to be the same, would I be correct in assuming that 94170015 uses the same 2byte RPM (893A/893B)as well?

ahh no, MUT_TABLES are in different locations on each different ROM, but the XML is the same for all ROM's just the address is different!

Yeah, thats what I said lol. like mine is address="38158" so I just need to have them understand that THIS is the # that needs editing before copying and pasting the code into their XML.

96530006
2byte load
MUT 00 = 898a
MUT 01 = 898b

Note: as we know - there are several loads used within the ecu code - baro./temp compenstated, not compenstaed etc. ect. - the one above seems to match the load used for timing. Another address is 8984, 8985 which seems to be used as reference load for boost control.

Also note you're not required to log load on MUT00 and 01. You can log it from any MUT that isn't used. Same goes for any other parameter you want to log (RPM, airflow).

But setting a commonly used standard helps to avoid confusion.

I haven't confirmed this so maybe others can.

ROM ID # 88570008
2Byte Load
MUT 00= 6B12
MUT 01= 6B13

2Byte Airflow (Not Tried yet)
MUT 04=6B6A
MUT 05= 6B6B

Don't mind 2byte Airflow, it is wrong for both version. I tried and it keeps at 255. Looking at the code it *seems* to be octane number rather than airflow...

could you post your 2byte load 96530006 xml file?what must I do for to set ecuflash?

Attached is the zipped xml for 96530006 - remove all the other files beginning with 96530006 from the evo folder in Ecuflash.

I am attaching also a screenshot of what you need to have in the MUT table after opening and editing your ROM.

I use these because thats what Evoscan is already setup for, and always has been. One less step, ya know? It doesn't NEED to be those ID's but why have to edit 2 things?

2Byte RPM users, what improvements have you noticed with it, Particularily with logworks?

98640014

MUT00 885C
MUT01 885D

MUT00 location to change is at 2E9E2
MUT01 location to change is at 2E9E6

MB

So if you added the entire 3D MUT table, you would only need to edit the MUT00 and MUT01 locations correct? And if you added only a 1D MUT Table you'd need to edit the addresses you listed above? I've always used the 3D table so I'm just making sure I understand the process.

I think adding the whole table is better, its one copy/paste and one address change.. and it gets people in the "right frame of mind" when talking about MUTs

I agree, and I've also used multiple MUT locations for testing things out, such as the ALT MAP ADC signal which came in handy.

96940011 MUT table:

3f314

96420008

Load
MUT00- 8984
MUT01- 8985

Airflow
MUT04- 89E2
MUT05- 89E3

MUT Table- 39FA0

Bump for this question:
2Byte RPM users, what improvements have you noticed with it, Particularily with logworks?

I haven't used logworks but its just more accurate readings. To the naked eye it may not look like much but once you start calculating different values along with it, the improvements/accuracies are probably more noticeable.

Added 3D MUT TABLE code and instructions to the first post.

94170008

Here is what I have been using. Seems mine are in different addresses than are in the first post.

<table name="00 2 Byte Load High" category="MUT" address="38062" type="1D" level="1" scaling="uint16"/>

<table name="01 2 Byte Load Low" category="MUT" address="38066" type="1D" level="1" scaling="uint16"/>

<table name="02 2 Byte RPM High" category="MUT" address="3806a" type="1D" level="1" scaling="Hex16"/>

<table name="03 2 Byte RPM Low" category="MUT" address="3806e" type="1D" level="1" scaling="Hex16"/>

<table name="04 2 Byte AirFlow High" category="MUT" address="38072" type="1D" level="1" scaling="uint16"/>

<table name="05 2 Byte AirFlow Low" category="MUT" address="38076" type="1D" level="1" scaling="uint16"/>

I have 3 Evo 7 MUT table addresses for adding 3D MUT Table.

98640014 MUT 3d Table start 2E9E0

98640016 MUT 3d Table start 2EA9C

99860002 MUT 3d Table start 302D8

I'll post the 2 Byte load addresses when I get them for 98640016 and 99860002

MB

[quote=FuelsResearch;5321077]96420008

Load
MUT00- 8984
MUT01- 8985

Airflow
MUT04- 8BB9
MUT05- 8BDB

MUT Table- 39FA0

quote]

Huge mistake on post #29!!! Fix 1st post.

Airlfow
04-0x89E2
05-0x89E3


My airflow is on 02,03 which caused the error. My apologies, I will go back to lurking now.

Yours are for the individual addresses for each to be used in a 1D table. Mine is the address for the entire 3D table. Once you install the 3D map, you can see EVERY MUT address in the chart and adjust them that way.

I assume when you open that table in ecuflash you'd have to enter the DECIMAL value I have on the first post? If not, tell me what values you have in the ECUFLash Tables. The 3D MUT table uses HEX values so I can convert your numbers you have listed.

96530006 - MUT table address = 36200

Updated, thanks guys.

Can you tell me the values you have listed in your tables for each of these in ECUFlash? Then I can find out what to put on the list. I'm almost certain they will be the same as 94170014 anyways. I'm most concerned with the airflow values. Im pretty sure you'll have 893A and 893B listed for your 2 byte RPM's since you are scaled for HEX16 already.

Fixed thanks Jack{thumbup}

Change Evoscan formula to 1000*x/256

I added a note in the first post for future users.

2-byte rpm for 96420007 works for 96420008. Since these two roms are apparantly pretty much identical, I would guess that airflow, load and MUT are all the same.

This should be stickied in nj's ecu topics thread

[QUOTE=FuelsResearch;...I would guess that airflow, load and MUT are all the same.

This should be stickied in nj's ecu topics thread[/QUOTE]


I would rather not guess if I can get away with it. That would be cool to have it stickied in there.

By no means, don't guess. I was just suggesting the possibility that a 0007 owner could try if they wanted, if it doesn't work it just won't log correctly.
But the 2-byte rpm does work, I just tried it.

2byte RPM eval for evoscan for the blind guy? TIA

LOL 4 post above yours homey{thumbup}
1000*x/256

Thanks Charlie...I told you I was blind. I knew i was in here but I couldnt find it for the life of me.

<table name="00 2 Byte Load High" category="MUT" address="38062" type="1D" level="1" scaling="uint16"/> 35164 or 895C
<table name="01 2 Byte Load Low" category="MUT" address="38066" type="1D" level="1" scaling="uint16"/> 35165 or 895D
<table name="02 2 Byte RPM High" category="MUT" address="3806a" type="1D" level="1" scaling="Hex16"/> 893A
<table name="03 2 Byte RPM Low" category="MUT" address="3806e" type="1D" level="1" scaling="Hex16"/> 893B
<table name="04 2 Byte AirFlow High" category="MUT" address="38072" type="1D" level="1" scaling="uint16"/> 35258 or 89BA
<table name="05 2 Byte AirFlow Low" category="MUT" address="38076" type="1D" level="1" scaling="uint16"/> 35259 or 89BB

Beautiful, thanks man.

Question,

Has anyone ever seen a ROm that shared only ONE 2 byte address (i.e; Load,RPM or Airflow) but didn't share all 3????? If not, we can fill up a good amount of these with "possible" codes that just need to get confirmed.

Ok, found in asm the reference for unclipped airflow. Sorry for the first post but I found the address somewhere and didn't try it :crap:
Airflow is checked now; I have bolded the changes.

88840016 (and 99.9% 88840017):

2byte load
MUT 00 = 6B28
MUT 01 = 6B29

2byte RPM (scaling 1000x/256)
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow (scaling 6.29x/64)
MUT 04 = 6B7E
MUT 05 = 6B7F

Great info. Thanks for putting this together.

My pleasure, just trying to give back ;-) It'll take a while to get it filled but hopefully it will become a "one stop shop" for everyone.

I think we should also add in the logging program definitions for logging this stuff.

Here is the mitsulogger definitions for RPM and Load. I need the airflow equation. RPM is not tested as i have not flashed my car with the MUT reference yet.

2-byte RPM Mitsulogger:
<Request LogReference="RequestID02" RequestID="02" Eval="x" Unit="INT" Logged="y" Response="2" />
<Request LogReference="RequestID03" RequestID="03" Eval="x" Unit="INT" Logged="y" Response="2" />
<Request LogReference="RPM-2byte" RequestID="FF" Eval="((256*RequestID02)+RequestID03)*1000/256" Unit="2byteRPM" Logged="y" Response="2" />

2-byte Load Mitsulogger:
<Request LogReference="RequestID00" RequestID="00" Eval="x" Unit="INT" Logged="y" Response="2" />
<Request LogReference="RequestID01" RequestID="01" Eval="x" Unit="INT" Logged="y" Response="2" />
<Request LogReference="Load-2byte" RequestID="FF" Eval="((256*RequestID00)+RequestID01)*10/32" Unit="2byteLoad" Logged="y" Response="2" Notes="Log using this Load Value" />

and what should we add in the xml def for the 2byte AirFlow to show in the ecu flash?

No need to add to the xml when you have the MUT table. Add the MUT address to xml, then make changes there. Al\lupo what is the MUT address for 88840016? Mscorei, see first post, download MUT xml and add correct MUT address. Open ecuflash and you can add what you need.

Here are the addresses for 88840016 & 17:

88840016
2byte load
MUT 00 = 6B22
MUT 01 = 6B23

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow
MUT 04 = 6B7E
MUT 05 =6B7F

MUT 3D TABLE ADDRESS = 377F8


88840017
2byte load
MUT 00 = 6B22
MUT 01 = 6B23

2byte RPM
MUT 02 = 6AFE
MUT 03 = 6AFF

2byte AirFlow
MUT 04 = 6B7E
MUT 05 = 6B7F

MUT 3D TABLE ADDRESS = 37944


I checked the values in asm for both, also airflow for 17 is the same of 16. MUT table are located in different places.

ok now I understand. 10x a lot. great help al\lupo!

Anyone feel like confirming that the MUT Table address for 94170008 is 38158 or 38150 for me? Someone listed it as 38158 but when I disassembled the ROM it seemed like 38150 was the MUT00 address to me. I'm still VERY new to disasm coding.

There is a typo in first post, RPM addresses for 88840016 are doubled.

Good lookin' out. All fixed,thanks.

Jack, thoughts on adding the logging definitions? I think it would be beneficial so we can log what 2-byte changes we make.

Yeah, it will be up soon. :)

:) i thought you forgot about me.

0x38060 is the start of the MUT table!

Already updated, heard through the grapevine that you confirmed that for us, thanks man. This list is pretty big and might take a while to fill up, but we'll do it damnit!

Gimme a week and I'll set up a section in the first post for Mitsulogger and Evoscan changes.

maybe we should get a mod to delete the posts in this thread that have already been pushed into the first post? just too keep it clean?

That'd be VERY helpful. Know any mods here?

I can tell you 100% that what you have for the MUT for 2 byte load on the first page is correct. Did a car with that today

Sweet, had someone IM me these past few days with issues and is road testing tonight. I'm confident that his results will be good. Thanks so much guys. I wish we could clone more Tephra's to go through the roms and find the missing locations to fill this list lol. Imagine 50 little Tephra Aussie's hopping around,lol.

96420011
2byte load
MUT 00 =
MUT 01 =

2byte RPM
MUT 02 =
MUT 03 =

2byte AirFlow
MUT 04 =
MUT 05 =

MUT 3D TABLE ADDRESS =

^^^^^^^anyone know the info for 96420011???? {pcfreak}

Jack, you are the man. I have had issues with the MUT addy on 70008 for quite a while. Finally got it all ironed out. This thread rocks! :)

BUMP for a great resource. Keep 'em coming guys! I wanna fill this list up completely!

96530006

Any help with 2Byte RPM and 2Byte Airflow?? Please

Anyone know what they are for 90550001 by any chance ?

Can someone please post up ALL of the ROM ID's for the 2003 USDM EVO 8's

Why do you need to see a list of ALL of them?

90550001:

MUT_TABLE: 0x2e9e0
Load: 0xFFFF885C
RPM: 0xFFFF883A

88580013/4:

MUT_TABLE: 0x373c4
Load: 0xFFFF6B22
RPM: 0xFFFF6AFE

96530006:
RPM: 0xFFFF8962

Does any one know were i can get a 96420008 stock rom??

^aktivematrix

We kinda think 96420008 was some tuners upgrade of 96420007!

As no one seems to have a stock 96420008 :)

Cheers Dave {thumbup}

Do you mean no one has a stock 20007 rom? I cant get the 96420008 ecuflash to show the MUT table.. Can any one conferm that MUT 3D TABLE ADDRESS = 39FAO Is right? I keep getting a parse error tag mismatch when i open ecuflash after altering the xml..

Make sure you didn't miss a tag in the coding. I sometimes delete a > or a < in the code by mistake at times. Also make sure that for every < table > code that you have an ending < /table > code at the end.

Does it tell you a line number where the error occurs? Thats the line number in Notepad where the XML error is, usually on the bottom taskbar (in Notepad, go to the top taskbar and click "VIEW" and checkmark 'Status Bar') you can see the line number as you move the cursor down the page.

I think 2byte rpm for 98640014 is:

MUT 02 = 883A
MUT 03 = 883B

unconfirmed though, just via IDA pro

Thanks that helped me out!!

Updated, thanks.

never mind

96530006 2Byte Airflow? Anyone? Anyone? :)

ok so I tested out the 2byte rpm fo 98640014. I don't think it was right but I got a graph that mirrors rpm but the scaling is off:

Engine rpm

https://img407.imageshack.us/img407/...4694970kv8.jpg

2byte rpm

https://img442.imageshack.us/img442/...3006209ef8.jpg

Any recommendations? This is what I had:

bump for my last post

R Mutt, play around with the graph scalings in evoscan!

I changed the scaling from .1 to .00125 and the graphs match but the actual rpm values for 2byte rpm are way off (I forgot to mention this before - refer to pics). I'm using the default eval formula in evoscan 2.0 maptracer edition which is 1000*x/256. Thought I was close, but now I'm second guessing myself :helpme:

Scaling of 0.1
https://img245.imageshack.us/img245/...0604437yx6.jpg

Scaling of 0.00125
https://img172.imageshack.us/img172/451/77510128cx8.jpg

oh - whats the formula in evoscan?

^^^

UPDATE:

96530006 2Byte Load could ALSO be, according to Tephra, 8984 and 8985.

I am surprised that I seem to be the only one interested in 2Byte Airflow for 96530006. I'd figure it out myself, I suppose, but I have no clue as to how I would go about that.

Could be...or "IS"? I can't add it to the list til its confirmed by a user unfortunately but a knowledgeable member will hopefully find your post with the "possible" addresses.

Guys - as you know there are several Loads used throughout the routines - some are baro, temp compensated etc. For 9653006 898A/898B is a load used in some Ignition and fueling routines, whereas the 8984/8985 is appearing in some boost routines. You can do you own testing use MUT00, MUT01 for 898a/898a and MUT02,MUT03 for 8984/8985 and you will see that they are mostly the same in the low load section and in the higher loads the difference is around 20 depending on the circumstances. So if tephra is using 8984 as a reference - no issues with that - is it just a little bit lower than the 898a.

Yeah, ideally we want to read the FINAL load value that the ECU is using at any given point, under the actual circumstances. Its silly to read the BASE load values when a handful of corrections are changing the load value the ECU is using for its final values.

Ok, i give... What value should I be using then?