The exported VOB seems broken while loading from Circuit tools.
link to the exported VOB
https://drive.google.com/open?id=1PzsyS ... jCXFU3r-d-
The lap of 8/11
Same lap of 7/28 works fine.
One more query is there any documentation for how to embed Laptimer recording into Racelogic's circuit tools? I read it somewhere but can't find it again.
Hugo
Exported VOB is not working properly
Re: Exported VOB is not working properly
Does the data look fine within LapTimer? In case it doesn't, the export will neither.
I can't check the file manually, it is too big. CT is quite fragile with the VBO format, there is no official documentation either.
- Harry
I can't check the file manually, it is too big. CT is quite fragile with the VBO format, there is no official documentation either.
- Harry
Re: Exported VOB is not working properly
It looks fine from laptimer on my iphone.
Re: Exported VOB is not working properly
Please export exactly this lap (not multiple laps) to HLPTR and send it to Harry@gps-laptimer.de
Harry
Harry
Re: Exported VOB is not working properly
Hi Harry,
It's sent out. I have both hlptrz and vbo for you.
Email title: LapTimer Export (LapTimer-0054-20190813-092756)
The laptime: 15:33.20
Distance: 17.013km
It's a mountain way.
Thanks.
It's sent out. I have both hlptrz and vbo for you.
Email title: LapTimer Export (LapTimer-0054-20190813-092756)
The laptime: 15:33.20
Distance: 17.013km
It's a mountain way.
Thanks.
Re: Exported VOB is not working properly
This looks like some interpolation problem. When zooming into the top point of the corrupted CT diagram, you will see something like this:
You will get this output:
Remove these lines from the VBO using a text editor to get a proper display in CT. I have not tested it, but should work.
I will check what is going on for the next version.
- Harry
This means there are some rows included in the VBO which have wrong polar positions and add this long extends to the South. Using a shell command to look for coordinates out of range can look like this:
Code: Select all
cat LapTimer-0054-20190811-214807.vbo|gawk '{ if (substr($3,1,5)<"+1491"||substr($3,1,5)>"+1495") print }'
Code: Select all
016 214254.70 -1672.99763305 -07936.62990791 004.100 169.30 +00352.40 -0.14 +0.17 001 00696 0040 000335400
016 214254.90 -1724.68779642 -07303.20845000 002.600 183.60 +00352.50 -0.12 +0.16 001 00686 0040 000335600
016 214255.00 -1644.99456939 -06518.43241515 002.400 192.70 +00352.50 -0.12 +0.15 001 00682 0040 000335700
016 214255.10 -1586.94482757 -06276.19032811 001.500 192.70 +00352.50 -0.11 +0.15 001 00692 0040 000335800
016 214255.20 -1586.94481668 -08330.22653556 001.700 171.20 +00352.50 -0.11 +0.15 001 00699 0040 000335900
016 214255.30 -1724.68796534 -07303.20844000 000.000 171.20 +00352.50 -0.09 +0.14 003 00706 0040 000336000
016 214326.70 -0890.05143065 -09687.36900065 001.700 149.20 +00362.00 +0.11 +0.00 006 01096 0040 000367400
016 214326.90 -1724.68829391 -07303.20848000 002.800 155.40 +00362.00 +0.14 -0.03 009 01104 0040 000367600
016 214327.00 -1437.31270762 -08768.91936381 003.000 148.70 +00362.00 +0.15 -0.03 009 01096 0040 000367700
I will check what is going on for the next version.
- Harry
Re: Exported VOB is not working properly
Update. The root cause is in the original recording. It looks like your 10 Hz GPS delivered corrupt data for the spot all the spikes originate from. I assume the interpolation applied during VBO export is running in precision issues triggered by the specific pattern shown in the "bad spot". You can try deleting the fixes in the area (Lap List ‣ the lap ‣ Fixes). The problem is around the 2800th fix of the lap. It is hard to handle because the recording is quite long combined with an update rate of 10 Hz.
- Harry
Re: Exported VOB is not working properly
Nice investigation and update. Really appraciate. I'm gonna to check what's wrong with my dual electronics xgps160. My hunch is the overheating during recording.
Thanks // Hugo
Thanks // Hugo
Re: Exported VOB is not working properly
Hi Harry,
I found the corrupted fixes. I remember what happened during the timeframe. I stopped there for 2mins for friends.
Hope this help to improve the laptimer.
I found the corrupted fixes. I remember what happened during the timeframe. I stopped there for 2mins for friends.
Hope this help to improve the laptimer.