I am using Dataviewer version 3.1.7.5 with the U7135 Predator firmware 9r05 on a 2007 Dodge Charger SRT.
I am finding that the data which is displayed where you put the cursor on the chart is not correctly lined up with the time stamp.
You can see this in the two enclosed screen snapshots for the example described below.
One is dataviewer and the other is from excel.
Example:
I put the cursor on a point on the curve in dataviewer and it shows 5735 RPM, Vehicle Speed of 43.0 at Time of 6.626
I then export that data as a CSV file and bring it into Excel.
In Excel, tiime stamp of 6.626 shows 5735 RPM,Vehicle Speed of 38.5 NOT 43 MPH
It is time stamp 6.713 where these data values really are. You can see that in my excel snapshot.
I have double checked other values at different times and from different logs and they all exhibit this behaviour.
Any idea what I may be doing wrong or is this a bug in the program?
I am not trying to be picky. I am trying to understand a stuttering problem under WOT and I can do different plots in Excel with the CSV file for the same time area while I am looking at Dataviewer.
I am looking at more data than just RPM/Speed - this was just to keep the description simpler.
Bug ReDataviewer Data Values not lined up with time properly
Moderator: mikel
Bug ReDataviewer Data Values not lined up with time properly
- Attachments
-
- Cursor point is at 6:626
- Dataviewer Plot.jpg (177.64 KiB) Viewed 2217 times
-
- Same data in Exel. Time point is highligted.
- Same data in Excel.jpg (315.07 KiB) Viewed 2217 times
RE: Bug ReDataviewer Data Values not lined up with time prop
The data samples come in at different time stamps for different parameters. When the data is exported to CSV, however, every time stamp gets a row and every parameter gets a column. The DataViewer carries a data value forward in time so that every cell is filled.
In your example, a new RPM was received at 626 but the next MPH was not received until 713.
If you record fewer parameters, then the data points will be more granular, i.e. more samples per second per parameter.
In your example, a new RPM was received at 626 but the next MPH was not received until 713.
If you record fewer parameters, then the data points will be more granular, i.e. more samples per second per parameter.
johnc <at> diablosport.com