It's interesting to see the proper timing change in respect to changing position of peak pressure (closer to TDC) when the bore - stroke ratio changes as in jid2's log with the 2.3l. However, I was thinking it would move the spark more BTDC with this car, unless this is retarded for octane.

 

It would be neat to get Hammish of EvoScan to do his chart files in Logworks file format.
A we know it can be done
B it would make his evoscan a much better product in that regard.

 

Jid2

what is your compression?

 

Ignore the timing on that log. As you can see there is some knock which is most likely false and I've been extra conservative with it. I get the same amount of knock with low or normal timing...

Compression is 9:1

 

That makes more sense

 

All you need to do is add a header to the .csv log then export to .dif and it will open right up in logworks.

To get a good header, you'll want to export a few logworks logs into .dif format and open in excel. You should be able to figure it out from there by taking the header from a .dif log and adapting your .csv log to have the same type of header entries. From there, export the .csv file to .dif.

I've used this to adjust for the time delay between the wideband channel and the actual data in logworks logs. Just an FYI, the LC-1 wideband data will lag behind your engine data by a few samples (likely a combination of exhaust gas velocity and then the data just being out of sync from processing). I've also used it because evoscan provides a faster logging rate then logworks and have gone directly from .csv to .dif files.

Also, when you add a new channel in the protocol.xml file, it's a good idea to open up logworks and go into the channel configuration through the dashboard to verify everything is scaled correctly. For some reason, it seems like it doesn’t always configure the graphing correctly. It is important to do it through the dashboard too, because any changes in the log window will only affect that log and will not have a permanent affect on future logs.

 

For protocol logging, yes, but for direct logging of devices in the LW chain (LC1 > SSI4 > TC4, etc) the logged data is real-time and capable of logging sample change equivalent to 3 pages of evoscan data for one second. And the only AFR lag is the time it takes the exhaust gas to travel from the exhaust valve to the sensor.

Bottom line: for logging MUT stuff, use evoscan, possibly more useful than OT-1. For logging directly, LW by far superior.

 

Yep, protocol logging I think is what most are interested in.

I don't use EVOscan for logging the AFR at all. Just for certain tuning where I'm less intersted in AFR. I've heard people have issues with the LC-1 and EVOscan and it causes the LC-1 to need to be calibrated constantly.

It could be just exhaust gas velocity delay, but it seems a little too long for that.

 

just as another pointer for ppl wanting to do this.
i opened lw2 and then opened example log file "turbo"
then saved it as a DIF file.
then opened that with excel to view the header as lw wants to see it.
so below here it is opened in excel you quickly see how you can add your evoscan csv log data to it. then give it a name for saving and in .dif format.
lw2 then will be able to open it.
i changed the name and scale for boost to represent my logged boost i.e psi.

for more channels just add extra columns with the LM-1 (LM1:#) the first column is LM-1 (LM1:0)

 

Just as an FYI, if you convert the log and open it in Logworks, logworks will change the time sample and rescale it to the 12 HZ intervals you would get logging with logworks.

If you convert a .csv log and open it in Logworks, then later try to use that log in VDR or other dyno programs, your HP will be wrong.

 

good point. noted

 

Can someone post me his Logworks protocol.xml file to able to log MAP sensor 1byte load wgdc wgdcc, target boost and boost error ? I would so please. With Evoscan it is impossible to see normaly on graph. Please upload somewhere or I coud send an email address . Thank you

 

this is the type of format i think. for load

<datachannel id="#41" name="1Byte Load" selected="0" units="load" min="0" max="270" expr="x*1.2" type="0" />

 

I've tried this and it doesn't seem to work. I've changed both multipliers to 1.6, one in ROM and the one saved in the protocols file for logworks and my maps still max out at 306 load(basically flat lines for a couple k revs). Not sure what the deal is, anyone have an idea. This is a V7 rom with the 1byte.