https://www.youtube.com/watch?v=gF32-dCwr_o
Lap 54 of the weekend (in CSV file), 27th of the Day (in video)
- Overlay and CSV show no OBD data for the start of this lap
- However, I think Harry's was receiving OBD data - between the 4s and 9s marks, it is flashing the upshift indicator; I assume this means that it was receiving RPM data. This is not showing in the Overlay or CSV.
Also, the app is inconsistent - if you do 10 laps, in some screens it thinks there's Lap 0 => Lap 9, in others there's Lap 1 => Lap 10
BT1: data being picked up by Harry's, but not in CSV
-
- Fewer than 10 Posts
- Posts: 9
- Joined: Sat Jan 10, 2015 12:17 am
BT1: data being picked up by Harry's, but not in CSV
- Attachments
-
- LapTimerGPSRecDB.csv
- (90.32 KiB) Downloaded 117 times
BT1: data being picked up by Harry's, but not in CSV
Difficult to reproduce, but usually a connection issue with the OBD. Btw. If you get a single rpm fix, LapTimer will flash for some seconds - it may seem more than it is. Both overlays and CSV exports use the database content and should be consistent.
On index: yes, this may look inconsistent. Every lap has a unique index in the database (starting with 0) - which is shown in Lap Details and for lap references (e.g. laps covered by a session video), while all enumerations "number of lap of a day / session" start with index 1...
Harry
On index: yes, this may look inconsistent. Every lap has a unique index in the database (starting with 0) - which is shown in Lap Details and for lap references (e.g. laps covered by a session video), while all enumerations "number of lap of a day / session" start with index 1...
Harry