here is what I have used with success in logworks 2 in one location.
you need supporting ecu and hardware mods for boost and load as specified in other threads.

for logworks 3 I have not tried these yet, I am waiting for a non beta release with plugins

in protocols.xml

<datachannel id="#38" name="JDM Map Sensor" selected="0" units="PSI" min="0" max="30" expr="(x*0.19347)-14.23" type="0"/>

<datachannel id="#38" name="Jdm boost" selected="0" units="PSI" min="0" max="30" expr="(((1.334*x)*14.5)/100)-14.5" type="0"/>

<datachannel id="#86" name="Wastegate Duty Cycle" selected="0" units="%" min="0" max="100" expr="(100*x)/255" type="0"/>

<datachannel id="#00" name="loadmsb" selected="0" units="load" min="0" max="255" expr="x" type="0"/>

<datachannel id="#01" name="loadlsb" selected="0" units="load" min="0" max="255" expr="x" type="0"/>

math channel formula used after log when reviewing chart.

MC(ECU_Load;%;0;350) = ((loadmsb * 256) + loadlsb)*10/32

there were questions on the specifics of 2 byte in logworks so here goes

1. perform the 2 byte load mods to ecm explained here for the evo 9
https://www.evolutionm.net/forums/sh...d.php?t=261465
for 8s search its in here.

2. Add the following to the protocols.xml file in the logworks program folder like so
<datachannel id="#00" name="loadmsb" selected="0" units="load" min="0" max="255" expr="x" type="0"/>
<datachannel id="#01" name="loadlsb" selected="0" units="load" min="0" max="255" expr="x" type="0"/>



save as protocols.xml

3. with openport cable conected to computer and car run the openport 1.3 plugin and select loadmsb and loadlsb along with any other chanels you want logged.

4. run logworks and log your pulls

5. open your saved log in logworks for review

6. select formula calculator like so


7. add MC(ECU_Load;%;0;350) = ((loadmsb * 256) + loadlsb)*10/32 like so



and click add to math library

8. select math library

find your load formula and select use formula


your load will apear on the log and can be used to chart very effectively

 

Great info thx..

 

I have tried the logworks 2 plugin in the new LW3 beta, and it works fine.

I just added the boost and WDC logging last night, but my formulas were off.

 

This is great news. So would the the boost and 2 byte load be in the open port plug in?

 

Cant wait to log 2 byte load and hz with the best logger for evo's, I think I'm half there - got 96420007

 

Have you even found your mut table yet? If not then you need to find that first. You can do it with a hex editor and look for a pattern of ffffxxxxffffxxxx

 

Freon said if one of these - FFFF886C and FFFF8962 - work, he might be able to show me how to hex edit with a working xml def.

I just dont exactly know what he wants me to do with those to see if they work .

Any ideas ?

 

after you ad the above lines to the protocols.xml file when you run the openport plugin they will be there to select. keep in mind for the 2byte load you must select both the loadmsb and loadlsb items the use the formula after the log is done and you are reveiwing it. you must also install a jdm map sensor from mrfred and perform the 2 byte load mod to the ecu.

logworks 3 is supposed to have the ability to log both high and low byte load values and combine them real time but I have not tried this

 

So what if you care less about pressure, and you just want to log 2 byte load and hz with logworks, and you have one of these FFFF886C and FFFF8962 to choose from, how is that done?

 

I already run the jdm map and use 2 byte load but thanks

 

as far as 2 byte maf hz goes I havent logged that so I don't know. I havent read up on that and disassembly is something I know nothing about. you can use the above examples and formulas from evoscan or mitsulogger to write your own xml lines to log If you know the requests and have altered the code in the ecu. it shouldn't be too difficult. I just posted what I have used with success to help out others that like to use logworks.

 

I just want to alret you guys that the "14.5" number that you are using in the formula varies with atmospheric pressure. If you are at sea level, then you should use 14.7 for better accuracy.

 

You only want to change the second "14.5". If you want to simplify the equation a bit, use:

0.19347*x-14.5

14.7 is for sealevel. As you go up in altitude, the 14.5 number goes down. It will be quite a bit smaller at 3000 ft.

 

So the formula using 0.19347*x-14.5 will be like this:

<datachannel id="#38" name="Jdm boost" selected="0" units="PSI" min="0" max="30" expr="0.19347*x-14.5" type="0"/>

Is that correct?

 

added some detailed instructions in 1st post