[SOLVED] V16 compatability with Dashware 1.3
[SOLVED] V16 compatability with Dashware 1.3
What's the compatability with the output csv file and Dashare with V16? I noticed my Accelleration (G's both directions) was not displaying after updating HLT to V16. Had no issues with previous HLT exporting the LapTimerGPSRecDB4Dashboard.csv file for use with Dashware. After some tinkering I revived that feature. I unselected semi-colon separation as an option in DW. Unfortunately I cannot seem to get the fastest lap to display nor the lap # that fast lap was on. Can you think of anything that would have changed in the export .csv file (formatting, header change, etc) from V15.0.5 to V16 that may cause fast lap time or fl# to not function in DW?
V16 compatability with Dashware 1.3
Hi,
Both fields should be derived by DW, they are not included in the export. Please check with DW first, maybe you need a new mapping file.
Harry
Both fields should be derived by DW, they are not included in the export. Please check with DW first, maybe you need a new mapping file.
Harry
Re: V16 compatability with Dashware 1.3
Update:
First I found out how to export sessions individually. Select the lap from the list within the session you are looking to export (look at the clock times). Scroll down to bottom and select export, within that menu select session then export and it will send that session; not the last session run like it does with the main export button (from laps menu). When I export by session the files sent to my email are .cvs, except the last session (it was longer than others). So far (1-2 sessions in of video editing) the files sent as .csv are ok, when I delete the semi colons. The problem is my last session is sent as a .gz. It's possible that windows compression does not handle the transfer to .csv. Maybe winzip or another compression software might handle it better. Unfortunately my best lap in is the last session; so I really want that one to work.
First I found out how to export sessions individually. Select the lap from the list within the session you are looking to export (look at the clock times). Scroll down to bottom and select export, within that menu select session then export and it will send that session; not the last session run like it does with the main export button (from laps menu). When I export by session the files sent to my email are .cvs, except the last session (it was longer than others). So far (1-2 sessions in of video editing) the files sent as .csv are ok, when I delete the semi colons. The problem is my last session is sent as a .gz. It's possible that windows compression does not handle the transfer to .csv. Maybe winzip or another compression software might handle it better. Unfortunately my best lap in is the last session; so I really want that one to work.
Last edited by toolo4sno on Fri Aug 24, 2012 3:59 am, edited 1 time in total.
V16 compatability with Dashware 1.3
Please check if you find a free downloadable version of "gunzip". I sure someone provides this for Win too.
Harry
Harry
Re: V16 compatability with Dashware 1.3
Update:
I got the csv to come out ok. I'm actually not sure what I did differently from before, but it worked. I'll have to review what made it work. I'm pretty sure the formatting looked the same as before when it was failing, but I just deleted the semi colons from the csv that was uncompressed from the gz. Actually, I delete those entire sections in the brackets (just in case).
I think the windows Gunzip application is 7-Zip file manager or something else. It was a little confusing and my winzip trial ran out. Either way, I got it to work and my videos are awesome again. The acceleration data also helped me between my 2nd track day to 3rd. I knew which corners I could push more. Then blended that knowledge with the gaining experience for the feel of reaching the limit.
Thanks Harry.
I got the csv to come out ok. I'm actually not sure what I did differently from before, but it worked. I'll have to review what made it work. I'm pretty sure the formatting looked the same as before when it was failing, but I just deleted the semi colons from the csv that was uncompressed from the gz. Actually, I delete those entire sections in the brackets (just in case).
I think the windows Gunzip application is 7-Zip file manager or something else. It was a little confusing and my winzip trial ran out. Either way, I got it to work and my videos are awesome again. The acceleration data also helped me between my 2nd track day to 3rd. I knew which corners I could push more. Then blended that knowledge with the gaining experience for the feel of reaching the limit.
Thanks Harry.
Re: V16 compatability with Dashware 1.3
Thanks for the update. Feel free to post your videos in the Community section or on the LapTimer Facebook page 
- Harry

- Harry
Re: [SOLVED] V16 compatability with Dashware 1.3
I'll add more details. To make it work, you have to make a copy of the "Harry's Lap Timer" data profile in DW by going to "File"->"Edit Data Profiles", selecting "Harry's Lap Timer (read only)" and clicking on the "Clone Data Profile" button. Then, on the clone, uncheck "Semicolon" on the "Separator Settings" section.
This is required because the header of the HLP's csv file includes semicolons.
I hope it helps.
This is required because the header of the HLP's csv file includes semicolons.
I hope it helps.
Re: [SOLVED] V16 compatability with Dashware 1.3
That was part of my experiment, but doing that (turning off semicolon in DW) made my fastest lap time, and lap # that happened on, readout not work. I don't believe there are any other semicolons in the file, but for some reason it did want to work with those semicolons there in the header. So once I figured out what did what in Dashware; I then edited the .csv (I just deleted the part in quotes "[UNKNOWN;2D3D;DGPS;INVALID]" in the exported csv file and the other ones like it. I didn't want any other strange characters doing other stuff I didn't want), left the settings as is in DW and imported. I have to revisit what I did exactly on the last session (exported as a .gz). The other files that I could export as cvs were no problem as long as I deleted the ";". All of this csv editing for me is in Win7 Notepad.etzilon wrote:I'll add more details. To make it work, you have to make a copy of the "Harry's Lap Timer" data profile in DW by going to "File"->"Edit Data Profiles", selecting "Harry's Lap Timer (read only)" and clicking on the "Clone Data Profile" button. Then, on the clone, uncheck "Semicolon" on the "Separator Settings" section.
This is required because the header of the HLP's csv file includes semicolons.
I hope it helps.
-
- Fewer than 10 Posts
- Posts: 1
- Joined: Tue Sep 18, 2012 10:24 am
Re: [SOLVED] V16 compatability with Dashware 1.3
Hi guys,
I was having similar issues when importing the session file into DW. I was able to modify the import spec to get the data to load but I lost the track position mapping and the OBD speed data.
Are you guys getting multiple laps to map and track your progress around the track lap per lap? I have never been able to get DW to do that. I used to load 1 lap at a time and synchronize (that worked perfect) but took a long time to enter 10-12 laps per session then combine the output files with the DW data.
I will try your suggestion of eliminating any unwanted data fields in the csv and loading.
Can you post some links to your videos where more than 1 lap is shown?
Thanks!
Rad
I was having similar issues when importing the session file into DW. I was able to modify the import spec to get the data to load but I lost the track position mapping and the OBD speed data.
Are you guys getting multiple laps to map and track your progress around the track lap per lap? I have never been able to get DW to do that. I used to load 1 lap at a time and synchronize (that worked perfect) but took a long time to enter 10-12 laps per session then combine the output files with the DW data.
I will try your suggestion of eliminating any unwanted data fields in the csv and loading.
Can you post some links to your videos where more than 1 lap is shown?
Thanks!
Rad
Re: [SOLVED] V16 compatability with Dashware 1.3
Here is my Youtube page link. There are plenty of examples where I used HLT and DW for a full session.
http://www.youtube.com/user/2lo4sno
http://www.youtube.com/user/2lo4sno