I won't write into fine detail because I'm assuming if you're doing this then you've already done 2-byte load (and possibly other mods).

So here is the info I found thanks to Tom-05-MR and Tephra.

2003-2004 94170008, 94170014
(0x)893A - hi-byte
(0x)893B - low-byte

2004 96420007
(0x)8962 - hi-byte
(0x)8963 - low-byte

2005 96940011
(0x)8976 - Hi-byte
(0x)8977 - Low-byte

2006 88590013, 88590014, 88590015
(0x)6B1E - hi-byte
(0x)6B1F - low-byte

2006 88840016
(0x)6AFE - hi-byte
(0x)6AFF - low-byte

Here are some requestIDs to use assuming you've already used 00 and 01 for load.


Example, if you wanted to setup 2-byte RPM to log on requestID 02 and 03 in ECUFlash for 2005 evolution 8.

In your 96940011.xml

<table name="MUT RequestID 02" address="3F31E" category="MUT" type="1D" level="1" scaling="Hex16" />

<table name="MUT RequestID 03" address="3F322" category="MUT" type="1D" level="1" scaling="Hex16" />

Note: You can put whatever you want for table name="---" like table name="2-byte RPM hi-byte"

Then open ECUFlash and bring up the MUT RequestID 02 and 03 tables.
For MUT RequestID 02 put in = 0x8976
For MUT RequestID 03 put in = 0x8977

Logger sample xml

Evoscan:

<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="1000*x/256" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>

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" />

Please reply with addresses for the unknown ROMs.

 

You've got 0x6B43/0x6B42 for the Evo IX. Those are the low/high byte addresses for one of the load variables.

 

88580013 = 6AFE/6AFF
88580014 = 6AFE/6AFF
94170008 = 893A/893B
94170014 = 893A/893B
96940011 = 8976/8977
88590013 = 6B1E/6B1F
88590015 = 6B1E/6B1F
96420007 = 8962/8963

Hope this helps!

 

remind me again, whats the advantage of 2-byte rpm?

 

more accurate logging also you get more up-to-date info (ive found anyways)

 

I thought the weak point (weak as in slow) was the ecu output to the logger making 2 byte RPM less useful.

I guess it wont hurt to try it out and compare on my logger to see

So, 8962/8963 (35170/35171) it is, thanks again now I have to remember how to find the address

 

Thank you Tephra.

First post edited. The roms you mentioned and I didn't list I will, just need to do some searching and figure out what car they are.

 

I have a question for logging 2byte RPM on LW:

If I paste the RPM high/low lines from 3. to 2. to setup the ROM's XML for RPM and flash it with the respective bit converts (35171/35170) to the ECU, then what lines do I need to write in the LogWorks Protocol for 1., and what math do I need to use as the formula for 4.?




Thanks

 

C6C6CH3vo, I have done the 2 byte load in logworks. From my understanding it has to be in the protocal xml file. Do you know if you can put the 2 byte load, jdm map etc.. into the mut III. Or change the knock sum from protocal to the mut III? It kind of sucks not being able to log knock with the rest of the protocal stuff

 

Kreionic, I got lost half way in your question once mutIII was mentioned because knock sum is already in there.

But for evoscan, logging 2bRPM is as simple as flashing the new xml modified ROM then selecting it to log.

With LW (not EvoSpecific) I need to find someone who knows there stuff (Eric) and has some spare time to figure what to use as the MC to plug in the lsb/msbRPM.

 

LOL ok after looking at your your post above. You added the the 2 byte load under mutIII right? I added it under generic OBD II. I guess I should switch where I have the 2 byte load from obdII to mutIII. Do you have the jdm map? Did you add that under mutIII aswell?

 

what does (0x), or 'x' stands for?
sorry for the newb question...

 

i don't know why, but you have to type the 0x in front of the address or it won't accept it.

 

0x denotes you are looking at a hex value

ie 0xA = decimal 10

0x10 is not the same as 10

 

roger, thanks for putting all of that info into one post. I'll have to give it a shot this week.

Also, thanks tephra for helping...just one more item to put on your "Making the Evo Community awesome" list