Has anyone made a dataloglab definition for Evoscan .99?

 

I used MJ's DLL definition for 0.97 and it has worked since.

You can find it here:

https://www.evolutionm.net/forums/sh...d.php?t=237768

Second post down....

 

That's the definition I have now, but the WideBandAF value wasn't being read correctly, plus it doesn't have the 2 byte ecu load. I fixed the wideband value, but I don't know how to go about adding new items.

 

Try this:

I added 2-byte load and RPM, just make sure the scaling is correct in the options. The scaling for 2byte RPM should be 0.01 and the scaling for 2byte load should be 1.

Click here (right click save as)

Import that into DLL, let me know if that works for you...

~Zach

 

Bump! The mitsulogger.txt file doesnt work with DLL at all. I've seen some dataloglab logs with 2byte load. I could change the definition file but everytime I try it messes everything up. My WBAF is also not working anymore since .99. can someone please post a working dataloglab definition file for EvoScan .99 preferably with 2byteload also or maybe explain how to fix the WBAF problem and add 2byteload? The file looks very simple but I dont get the. Here is the portion of the file that does WBAF.

[Column]
Name=WBAF
Description=WidebandAF
ColumnTitle=WidebandAF
DataItemID=83
Type=1
ColumnDecimalPlaces=4
DisplayDecimalPlaces=2


Why isnt this working, it looks correct, and why does it reference "83", is this a reference to dataloglab?

 

The 83 (i think) is a variable reference in DLL you have to make sure that other references (Load, MAF, RPM, etc....) are not using that same reference number or DLL will get pissed. The DLL definition works perfect for EVOScan v0.99 for me and many others that I have tuned. Post the errors you are getting with loading the file.

You might want to check under Customize, Options, then click on Data Item Definitions. Check here for each item listed and make sure the scaling is correct. The scaling for 2Byte load should be 1, the scaling for 2Byte RPM should be 0.01, and the scaling for WB02 should be 1. This is important because it will throw off you graphs if it is not scaled correctly to the rest of the map.

Let me know how it works for you,
~Zach