Logging went insane

[scoobyman]

I've been logging for a bit now to know how it works, however, after making a log yesterday and looking at it - values all across the board are just random.

I have recently started using 2 ecu modes and i have installed an external lambda sensor, could any of this affect it ?

The ECU itself works fine, and the ECU manager reads all the values correctly, but log is just a huge mess of weird numbers.

I also noticed that my date and time was set incorrectly on the laptop as i had taken out the battery and didn't synchronize it so the date was set to 2002, i know it can sometimes play weird games on computer programs, could this be the cause it ?

I'll attach the log if anyone wants to look at it.

[Sean]

What channels look strange to you? I had a quick browse and without knowing what specific to look for it looked ok to me.

[AdamW]

Looks ok to me too, air temp looks unusally low but most of the common channels seem to show realistic values. What channel/area are you concerned about?

[scoobyman]

Sorry guys, uploaded wrong file.
Here is the recent log

[scoobyman]

This small one is broke as well

[David Ferguson]

Are you using multiple configurations in the same ECU? (you mentioned using two modes) If so, do both configurations have exactly the same logging setup? If not, I could see that being a problem as when the download happens the active configuration is used to know how to interpret the logged data. If that data were created by a different logging configuration -- I would expect garbage.

[David Ferguson]

A few observations on your file 20020101-0464201.ld (sti06, fuel pump dying):

- The throttle position doesn't seem to be calibrated in your config.
- Logging is setup just for dyno pulls (start at 2000 RPM, and stop when < 1500 for 2 seconds) - this would not be a good choice for driving the car around, as the logging would start and stop many times and it will confuse you. I might suggest start logging at > 2000 RPM, but only stop logging when RPM < 100 (i.e. engine stopped).
- You're logging Lambda2, but it's not configured -- the data shows what looks like data for Lambda 2

[scoobyman]

Thanks everyone, It looks like the ecu was getting confused by mode switching with different ecu logging parameters.

Tried getting logs from separates modes today and it worked out fine, but once i switched modes midrun my log would come out with insane numbers.

Thanks for the tips regarding start stop parameters, i use 4000 rpm as a start trigger with no delay and 2,000 rpm as a stop trigger with 2 seconds delay.

Also, i dont use throttle position as it makes the car choppy for some reason.