Log with negative resolution

[mituc]

I have a log with a decent amount of data (2.6MB in total) that I would like to look at but for some reason nothing is displayed. When I open the log in Versatuner I can see the minimum/maximum values for the PID's I was logging but the resolution is negative.
If I open the log in a plain text editor I can see that after the record time=566.752 the next value is -3727.995. This is pretty odd, it's like the versatuner is using the system clock to get the timer and the hour change occurred during that log. Which is unlikely, the laptop has been on for quite a while and there was no internet connection for the system to update the time via NTP or something. Also, the difference is not 3600 seconds but some odd value (4294.990? for this PID):

Code: Select all

      <Record Time="566.292" Value="0.41176470588235292" />
      <Record Time="566.512" Value="0.41176470588235292" />
      <Record Time="566.752" Value="0.41176470588235292" />
      <Record Time="-3727.995" Value="0.45490196078431372" />
      <Record Time="-3727.7549999999997" Value="0.47843137254901963" />
      <Record Time="-3727.515" Value="0.47843137254901963" />
      <Record Time="-3727.2749999999996" Value="0.4823529411764706" />
      <Record Time="-3727.035" Value="0.68235294117647061" />
      <Record Time="-3726.7949999999996" Value="0.72549019607843135" />
      <Record Time="-3726.555" Value="0.7803921568627451" />

It's more like the timer variable is kept on a data type not wide enough for time values greater than 566'ish seconds. Should I report this as a bug?

[YuraL]

The timer is reset when the screen goes blank or when the system goes into standby mode.

[Ugnius @ VersaTune]

This will be fixed in the next release. Thank you for reporting the bug.

[mituc]

Thanks guys!
The system did not went into stand-by but the screen may have went blank though. Now that I know I'll put my finger on the touchpad from time to time.

[mituc]

This still happens on long logs (over 10 minutes). The laptop never goes to stand-by (not even the display), and it's charging from the lighter all the time.

Code: Select all

      <Record Time="462.817" Value="29.28515625" />
      <Record Time="462.95799999999997" Value="29.28515625" />
      <Record Time="463.097" Value="29.28515625" />
      <Record Time="463.23699999999997" Value="29.28515625" />
      <Record Time="463.37699999999995" Value="29.28515625" />
      <Record Time="463.517" Value="29.28515625" />
      <Record Time="-3831.31" Value="29.28515625" />
      <Record Time="-3831.1699999999996" Value="29.28515625" />
      <Record Time="-3831.0299999999997" Value="29.28515625" />
      <Record Time="-3830.89" Value="29.28515625" />
      <Record Time="-3830.75" Value="29.28515625" />
      <Record Time="-3830.6099999999997" Value="29.28515625" />

I'm using the latest versatuner version available for MS3. (1.7.0).

[mituc]

This bug keeps popping up. Today it started to log with negative numbers after only 1 minute of logging.
I have even larger logs than this one, one of them almost 17 minutes long with 0 problems. The laptop never changed its state as I don't touch it while driving if I don't want to start a new fresh log. This time the laptop was running on battery instead of lighter socket.

[Steve @ VersaTune]

What vehicle interface are you using? I have seen this with the Tactrix interfaces, but not the VersaLink interfaces which have a fixed USB cable. Check the USB connection and OBD-II connection.

[mituc]

I'm using indeed the Tactrix, the VersaLink was not available when I purchased the Versatuner.
The cable is fine, basically the logging continues and there are no blank values at the transition point. Moreover, the timestamp of the logged values is managed by the versatuner, the tactrix is only an interface. So I can't see how it could be the tactrix this time...

[Steve @ VersaTune]

The timestamps come from the CAN messages. They are reset when a new connection is made.

[mituc]

It makes sense then. I'll change the USB cable, thank you!