Imported autocross laps in Circtuit Tools dont show

[Raktenpolo]

Hi,

I'm new to HLT so please excuse me if this issue is well known but I couldn't find anything while searching. I've got a problem when exporting my data to CT:

I have an Android Petrolhead Edition HLT with a XGPS 160. I recorded some laps from our recent autocross session with a single start and finish trigger. I can view the data in HLT fine. I can export a single or multiple laps to .vbo format. After removing spare lines, checking EOL and checking the number of satellites (18-19) I open the file in CT2 by doubleclicking. The files loads fine. I can see a list of channels but I don't get any laps in the session view. I've attached a screenshot of both the vbo file and the CT2 screen. I'm not sure where to look for. Is this an user error since I have never used CT2 (but I tried playing around with nerly every option and different exported files) or is this an issue with the data format that it does not recognize the laps?

Thanks in advance

[gplracerx]

Removing 'spare' lines was a bad idea. I'm guessing that the program needs to see a blank line at the end of a section to know to look for the next section.

[Harry]

CT is pretty fragile when it comes to VBO format imports. As gplracerx has written already, the empty lines are at least partially necessary. The only thing you should and probably need to change in VBO files is the line ending convention. This is described in detail here: viewtopic.php?f=8&t=1282

- Harry

[Raktenpolo]

Hi,

it's not the line endings. I tried different approaches but they aren't changed (in the first place) after transmitting them via gmail when I first open them.

I played around with the spare lines some more. There are certain lines which are not allowed to be spare lines - for example before the [comments] - as CT2 just crashes when it loads the files. Other (extra) spare lines seem to have no impact. Unfortunately I can't upload a vbo file here otherwise you could quickly check that yourself. Right now I'm kind of clueless. Is there a working vbo file somewhere on the net that I could download to see if that works and check where the differences to my file are?

[Harry]

Problem is if you export the VBO again and send it to Harry@gps-laptimer.de it will work... But you may try nevertheless...
Please add some comments so I recognize it as related to this thread.

- Harry

[Raktenpolo]

Ok Harry, I'm just sending you a mail with the files.

One is working. One isn't. Due to your last post I tried exporting one of the later laps via google drive. We did 22 laps recorded laps during that afternoon that worked. So I exported an earlier lap and I have the same problem. CT2 crashes: "System.ArgumentOutOfRange".

And it might be me using HLT wrongly so please stay with me.

The track is an autocross track in Braunschweig. It begins with a standing start a small connecting part inwards than you go twice around in a circle and have small outward part. When we began we had a lot of problems while doing the second circle that we came to close to the end trigger with the recording ending. So I moved the end trigger further back from the finish line. And have deleted all the laps we recorded with those triggers. I checked the start and finish section of the .vbo files an that does not seem to be an issue.

Then I stumbled across the fact that the laps that don't work are prior to lunch. So I tried to compare them in HLT. And we had a lot of problems during the recording due to sensor calibration, as we often switch driver and in the starting area you always have the big "progress to starting area", "press ready to signal that you are ready for recording" and "start accelerating to begin recording" overlays and can't get to the calibration screen. because our track is so small the starting area covers almost every place you can go with the car. So the only way to look at laps, or try to change settings or get external gps working is when you remove the smartphone from the car go somewhere totaly different and when you return the calibration ist broken...

So back to topic. In the screenshots I have attached you can see that the first (prior to lunch) lap (the one that isn't working) has no acceleration data and the second one does. So I thought that that was a problem. But I have attached a third lap (again later) with no accelaration and that loads fine in CT2.

So I'm quite clueless. The reason I'm interested in the first file is that that is the quickest round. So I want to see where we found that one second.

Sorry for the long post.
Philip

[Harry]

Hi,

I checked your files and cannot see something obvious that should crash CT. However, maybe some data configurations are not handled correctly and make CT fail (e.g. division by zero etc). One thing probably generating problems it the trigger generated for the standing start. When LapTimer exports data, it extrapolates some fixes before and after the actual lap data. This is to mimic a logger input (CT takes logger input, not preprocessed laps) and usually allows CT to apply it's own trigger detection and lap break down. As standing go situation start with speed 0, extrapolation just adds some more fixes to the beginning of the recording - in exactly the same position. Due to the missing extra fixes, the standing go trigger added by LapTimer is not "passed". I removed the trigger definitions from the first .vbo file and CT didn't crash any more. This in turn certainly means you need to define start and stop manually in CT.

- Harry