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

Scaling of 0.1


Scaling of 0.00125

 

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?

 

89E2 and 89E3 for 2Byte Airflow

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

 

98640014 2byte RPM confirmed!

The formula in evoscan 2.1 was incorrect (c/o Jack_of_Trades on 2.1 fixes)
RPM MUT 2 byte Mod

* Incorrect = 31.25*x
* Correct = 1000*x/256

 

Ok Im new to this... So I have the 3d mut table saved in my rom w/ the correct address for a "88590015" (3EE84). I look into the "3D MUT table" and 2byte load are in the right location MUT 00 - 6B42/
MUT 01 - 6B43 (I have this defined in my "15".xml).

But my 2Byte rpm/2Byte AirFlow are off! From what I have just read, I do NOT need to define these in the "15" .xml just edit the address in the right location??? I have been unable to find the definitions for 2byte rpm/airflow, so I hope this is correct!

For 2Byte rpm MUT 02 - 6B1E On my table it reads 02 - 6B9E (which is airflow)
03 - 6B1F 03 - 6B9F

For 2Byte airflow MUT 04 - 6B9E On my table it reads 04 - 6D85
05 - 6B9f 05 - 6DA7
Now is this as simple as editing the correct address in the right location???

 

MUT table addresses:

94170015: 38158

96420007: 39FA0


Found one error. 96420008 has the MUT table addy as 39FAO. Its 39FA0.

Can the title of the thread be changed to mention that MUT table addys are here too?

 

Yup, no need for any XML modding with the 3D MUT Table in ECUFlash Just edit the address in the correct locatrion on the table and you're ready to datalog in 2byte!

Thanks, I fixed that error. I think a MOD needs to edit my title, but its a good idea to add that now.