ok so we have all seen the thread that was talking about the 2 byte load, to know exactly what load cell the ECU is in.

Now can somebody post up a step by step on exactly what you have to do to get it to work with evoscan?

also what are the possibilities that it will be a logable variable in future versions of evoscan or mitsulogger.

 

Both Evoscan and Mitsulogger can log the values from 2 byte load easily with its current method. I know Mitsulogger can log the proposed 2 and 3 byte responses if the guys making mods decide to do it.

This actually has been documented before in another thread, I just can't find it at the moment.

 

FWIW, same with the CableTools control I wrote (and use in the LogWorks MUT plug-in). Info on methods courtesy of MJ...

-jjf

 

https://www.evolutionm.net/forums/sh...ight=byte+load

searching is your friend.

WARNING... this is an advanced topic, don't try it unless you understand what you are doing.