Yes it would.

I have working logging that supports 2 bytes done properly from any address (ie the bytes aren't split). Neither logger on present release supports it yet, but they're working on it. Real time maps with 7 copies in ROM and 1 copy in RAM are also running, the RAM copy can be edited, but it is horrible to use until the loggers are updated.

 

What requestID were you planning on putting the "proper" 2 byte load on. The release I'm packing now handles 2 byte responses properly.

I would strongly suggest not using requestid's 00-05 for any of the mods, they appear to be bitmapped data that might be useful in the future.

 

E4 and E5, address defined by E0. E5 also post increments the address at E0.

00-05 are unchanged from stock now. Not needed any more

 

I figured as much, but it probably would have been good to clarify it since there are a few people doing the mod to those first few MUT requests.

 

New 2byte MUT mod DataItem has been tested successfully in v0.99 of EvoScan

A New LoadMax200 DataItem has also been added to v0.99 of EvoScan.

A New 2byte RAM mod DataItem has also been added to v0.99 of EvoScan.

 

Great news, keep up the good work and dont get discouraged by bickering girls.

 

This has actually always been possible in Mitsulogger, but I just verified that this is working in 1.6b3 with a mix of responses. I'm waiting for John to verify the information replied is correct.

Once you have more than a handful of 2 byte items, you'll definitely need to do the baud rate mod to speed up the transfer.

 

Here are the new formats for the 2Byte Support in EvoScan v0.99

<DataListItem DataLog="N" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="00" RequestID2="01" Eval="0.3125x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes=""/>
<DataListItem DataLog="N" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="31.25x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>
<DataListItem DataLog="N" Display="E1 RAM 1Byte Mod" LogReference="TestE1" RequestID="E1" Eval="x" RAMAddress="FFFF6073" Unit="1byte" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes=""/>
<DataListItem DataLog="N" Display="E4 RAM 2Byte Mod" LogReference="TestE4" RequestID="E4" Eval="x" RAMAddress="00002ABA" Unit="2bytes" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="65536" ChartMin="0" ChartMax="65536" ScalingFactor="1" Notes=""/>

 

I think I'm probably going to end up handling the address reference similarly just to maintain some level of sanity between the two loggers. That wasn't how I was originally going to do it though but I like the simplicty of it.

 

Since my rom ID is 94170014 which is different from jcsbanks I cant just copy and paste what he posted in my 94170014xml to get this to work?

 

no,

each version of ROM has specific memory locations for the REAL load (2byte load) you need to find this memory location then overwrite the MUT req with it.. - check the other posts in this thread to find a matching ROM ID, hopefully someone has already done the hard work

 

I already looked I dont think anyone has posted mine, dam that sucks lol

 

Is there by chance a tutorial on how to find the correct memory locations for 2byte load and airflow in a specific rom(id 94170014), or would someone be willing to help me find it. Any help would be greatly appreciated. Also if someone has these memory locations for this rom already please let me know. Thx

 

well get the closest ROM ID to yours and try the MOD and just hope you get the right memory locations haha

check aktivematrix forums for your ROM ID maybe..

 

lol yea ill check it out and pray lol