Since we have had so many new developments in the realms of what to log I thought we should standardize where these locations will be place in the MUT for EvoScan logging purposes.

For example....

I know it used to be that

00, 01 = 2 byte load
02, 03 = 2 byte rpm
04, 05 = 2 byte airflow

But, this is where is 9653 is putting...

2-byte LOAD_Raw (no temp compensation)
hex value at 1C in MUT table + 0x09
hex value at 1C in MUT table + 0x0A

2-byte LOAD_Temp_Compensated
hex value at 1C in MUT table + 0x0B
hex value at 1C in MUT table + 0x0C

2-byte LOAD_Baro_Compensated
hex value at 1C in MUT table + 0x0D
hex value at 1C in MUT table + 0x0E

2-byte LOAD_Temp_and_Baro_Compensated
hex value at 1C in MUT table + 0x0F
hex value at 1C in MUT table + 0x10

The problem here is That EvoScan has different look-ups for items above. For example my EvoScan v2.6 beta 19 has LTFTs being logged at 0C, 0D, and 0E.


Confused ? ? ?

 

I think you're confused and copied that above text from one of my posts.

That was from a thread where I was helping someone find the variable addresses to log the different load variables for his ROM (0013).

I was telling him to look at what variable was at 1C in his mut table and then add the respecitve hex numbers to it to get the variables to log. You can then put those variables in whatever MUT location that you want, as long as you setup your logging program for it.

 

Yeah....I did use your post as basis for this.

I realize that we can just select and input what we want into the MUT and log it. I was looking at making the locations for logged items a standard.

By standardizing where we put the address for say for example load+baro would then allow us to make our logging tools standard to log that item. I hope that makes sense.

 

I understand what you're trying to do, but I don't think you realize what I wrote.

You mentioned your fuel trims are requests 0C, 0D, 0E. Nothng I wrote had anything to do with that. The 0C, 0D, 0E I was referring to was simple addition of hex values.

 

hmmm...Oh ok. I am really confused now.

 

Maybe this will clear it up...here is 9653 2-byte load variables:

2-byte LOAD_Raw (no temp compensation)
8984
8985
2-byte LOAD_Temp_Compensated
8986
8987
2-byte LOAD_Baro_Compensated
8988
8989
2-byte LOAD_Temp_and_Baro_Compensated
898A
898B

What you quoted me on above was trying to tell someone how to find his load variables for a different ROM.

The hex value for mut 1C for 9653 is 897B.

0x897B + 0x09 = 0x8984
0x897B + 0x0A = 0x8985


I was simply showing him the offset of the load variables (at least for 9653) referenced from the MUT 1C load variable, so that he could know what they were (or test them) for 96940013.

 

Ok then for the sake of EvoScan....what needs to be done for logging Load+Baro+IAT ? ?

I assume we need to select a MUT location and build an XML so that EvoScan can create a loggable data item.

But....what MUT location should we choose ? ? Is any "un-used" location ok???

Sorry for my ignorance....The MUT is all new to me.

 

To log baro+temp compensated load, you would put 898A and 898B in consecutive MUT addresses (like MUT00 and MUT01) and then setup Evoscan to log MUT00 and MUT01 as 2-byte load.

 

which load is 895C/895D in 94170015? RAW? In the official 2byte thread, 9653 2byte load is 89BA/898B and I understood this was RAW, but in post #6 above is referenced as Load_IAT_BARO? which is which