Latest with version 17, LapTimer generates a fully compatible VBO file suitable for Racelogic's free Circuit Tools. Both the old and the current version 2 of Circuit Tools were tested successfully.
Two issues you may run into:
- Racelogic's Tools expect raw data, while LapTimer changes raw data recordings to lap boundaries (using triggers) during recording. To allow recognition of lap boundaries in CT, LapTimer is able to export multi lap sessions and adds some extrapolated data to the beginning and the end of the recording. In addition, LapTimer triggers are exported too. Now, when opening a VBO file, CT will break down laps using its own algorithm (which can produce slightly different lap times). Keep that in mind, as LapTimer and CT use different concepts, things may vary a bit.
- [THIS ITEM OUTDATED STARTING WITH LAPTIMER 18.3. WE FOUND A WAY TO KEEP LINE ENDING CONVENTIONS!] The iPhone is a Unix platform, while CT works on Windows only. Both platforms feature different formats for line ends. As VBO files are practically always used on Windows, LapTimer uses the Windows conventions for VBO export. But: it seems that certain configurations of mail tools and OSes think they are smart and start changing the format during transfer again, leading to unreadable VBO files (CT is particularly picky with its format). Here is a workaround you may use in case you get an error message during VBO opening: download the free Windows text editor Notepad++; open the VBO file in Notepad++; select Edit ‣ Line Operations ‣ Remove Empty Lines; select Edit ‣ EOL Conversions ‣ Windows; save the VBO and open in CT. As an alternative, use the replace function: select Search ‣ Replace; select "Extended…" from "Search Mode", enter "\r\r\n" in "Find what" and "\r\n" in "Replace with"; run "Replace All"
Hope that helps,
P.S. There is a know bug in CT2 that crashes the tool when using the open dialog with (LapTimer) VBO files. Please double click the VBO instead - to work around the dialog. RL will have that fixed with the next release.