nj1266

iTrader: (6)

I am getting spikes when I log the 2 byte load with Logworks. It does not happen all the time, but it does happen.

I remember that someone in this forum was able to edit the *.log file to remove the spike.

Anyone knows how I can edit a *.log and smooth out the spike based on the before and after values?

Jorge T

iTrader: (18)

Export the *.log to *.dif. Use Excel to open the dif file and edit the spikes.

I create a column with the 2byte load calc formula and change the loadmsb value which is the one that gets screwy # causing the spike. Then I delete the loadcalc column, clean up the file and save it again in dif. I open the file using LW3 again and recalculate the load calc.

Another way is to edit the load calc math channel values directly. But the file may get unstable and get corrupt.

You may have to keep using the file in dif format, lately I've had the LC-1 AFR get corrupted using save as *.log using this procedure in LW3b2.


Make sure to make a copy of the log file before you do any editing.

Tuner@Swift

iTrader: (1)

The spikes are caused during the shift in reading the most significant byte and least significant byte. As long as you realize whats going on, theres no need to worry about them.

nj1266

iTrader: (6)

Thanks Jorge. It worked

Jorge T

iTrader: (18)

C6C6CH3vo

iTrader: (9)

I get spikes in 2byte load as well.

Is there any way logging 2 byte can change the way the ECU processes? Weirdness here but these spikes have corresponded to a change of other parameters, but I'm not certain if coincedence

Tuner@Swift

iTrader: (1)

Are these the type of spikes you guys are seeing? If so, they aren't a big deal and should have no effect on what the ECU is actually doing.

l2r99gst

iTrader: (2)

^^Right.

Those spikes are just because of the MSB or LSB changing in the time it took to log the MSB and LSB separately.

For example, when your load crosses from 255 to 256 (2byte load of 80), the MSB and LSB may look like this:

MSB LSB
.
.
.
0 254
0 255
1 0
1 1
1 2
.
.
.

The 1 in the MSB represents 256. So, if your logger logged a 1 for the MSB, and the LSB changed from 0 to 255 (for the next lower load), then your logger would put those two numbers together and get (256+255)*10/32, or a load of 160.

These point occur anytime the LSB changes number. These will be at two byte load increments of 80. So you may see these spike around loads of 80, 160, 240, 320, etc.


Eric