Pass through logs corrupt..?

[samh_08]

I am trying to do my AutoVE and I am running into issues. I have the latest builds of everything and my scan logs are all corrupt. Values jump all over the place. When I am just scanning, all the data is normal and good, but as soon as I try to go over my saved log it is all over the place.

Please let me know ASAP.

Thanks,

Sam

[mr.prick]

LOL

Are all you logs coming out like this?

[samh_08]

Haha Im glad you find humor in this. :) Yes, my last two logs have been like this. I've only taken probably 5 total logs though and the last two scanned normal and turned to this.


Any idea

[Blacky]

Can you please log those PIDs again and once logging has started, stop it again. Then display the [Console F6] tab page and copy/paste the packet programming trace data into this thread. The data I need to see should look identical to this (except for the timestamps):

11:29:06.122: Programming PID GM.AFR, into dynamic packet 0[0..1] offset: 0...
11:29:06.154: Programming PID GM.DYNCYLAIR_DMA, into dynamic packet 0[2..3] offset: 2...
11:29:06.179: Programming PID GM.IAC, into dynamic packet 0[4..5] offset: 4...
11:29:06.204: Programming PID SAE.RPM, into dynamic packet 1[0..1] offset: 0...
11:29:06.228: Programming PID GM.FTC, into dynamic packet 1[2..2] offset: 2...
11:29:06.253: Programming PID GM.KR, into dynamic packet 1[3..3] offset: 3...
11:29:06.278: Programming PID GM.TFT, into dynamic packet 1[4..4] offset: 4...
11:29:06.303: Programming PID SAE.ECT, into dynamic packet 1[5..5] offset: 5...
11:29:06.328: Programming PID SAE.IAT, into dynamic packet 2[0..0] offset: 0...
11:29:06.352: Programming PID SAE.MAP, into dynamic packet 2[1..1] offset: 1...
11:29:06.377: Programming PID SAE.SPARKADV, into dynamic packet 2[2..2] offset: 2...
11:29:06.402: Programming PID SAE.TP, into dynamic packet 2[3..3] offset: 3...
11:29:06.427: Programming PID SAE.VSS, into dynamic packet 2[4..4] offset: 4...
11:29:06.452: Using scan mode: Stream-Fast
On the log you posted, there seems to be a problem programming the TFT PID, it was placed at packet 0 offset 0, instead of packet 1 offset 4.

Regards
Paul

[samh_08]

Thanks for the quick help Paul. I think the screw up was on my side. I clicked the TFT PID while I was monitoring real time data, NOT while I was recording. I dont know if you aren't supposed to do that or not, but I figured it was still ok if I was just monitoring and not recording. If it shouldn't be doing this either way then let me know and I'll look into it more for you.

Thanks again,
Sam

[Blacky]

It sounds like a bug that we'll need to investigate here. I guess we never thought to test that scenario :doh2:.

The correct way the software should handle that, is to not allow new PID selections once data logging has commenced.

Regards
Paul

[samh_08]

Understood. Haha I guess I have a way of testing these odd ball scenarios. :hihi:

Let me know if you need anything else.

Sam