So I am thinking of buying the LM2.. Has anyone tried logging into evoscan with it with the programmable outputs? Will it work in evoscan with either of the other innovative products selected?
Also,
Is LW3 the same deal as far as LW2 in patching in the code for 2 byte mods, ect.? Does anyone think it may be a good idea to edit the LW3 logger to log from the X more accurately with the supplied obd cable or will all of that need to be done through the 2.0 cable?

TIA for any input

Pete

 

Hi Pete....

Check my post over here.
https://www.evolutionm.net/forums/ge...tion-help.html

Basically I am asking the same question....

I have been able to get the LM2 to talk to the OBD port on the Evo8, but have had a few problems, one being with the load.

What patches are you referring to with LW2 to get the 2 byte logged correctly?
I am hoping the same would apply to LW3 which wil solve some of my problems with the LM2.

Thx.

 

It involves editing the xml. file for the logworks program to read correctly from ecu that were patched for the mods.. I just want to know if the same can be done with the LW3..I am going to look into the LW# files tommorow to compare.. I am really interested in seeing if there is any kind of headway that can be made with the ot1 can interface and the innovative obd or openport 2.0 cable..

I am guessing the LW3 software can be patched to work with the the patched evo 8 roms no problem..

 

Did anybody menage to log knock or load 2byte via LM-2 since there is no protocol.xml in LogWorks3 ?

Thanks