Export/Dashware questions

[geogan]

Hi,

I noticed an old mail export contained a special CSV for Dashboard but when I export now there is only the standard CSV (same in export to Dropbox). Are you no longer doing a reformatted CSV version for Dashware?

Also in the CSV there is nothing for Braking - is this car related? ie. does my car ECU not return Braking information (i only see throttle information in CSV) I'm using the BT1 OBD device.

Can you explain the gears export - i may be imagining things but it appears it always shows gears as being one gear lower than what the actual gear is currently in car.

p.s. i also had to do the fix others here did where i had to clone the Laptimer config in Dashware and edit it to not delimit on semicolons because some of the headers have semicolons in them and Dashware was taking them as seperate columns so all columns after them were getting incorrect values. eg. throttle/gears

[Harry]

The two CSV exports were joined in v16. The new format has everything the old versions had.

Harry

[Harry]

Next point: braking information is not standardized by OBD. I'd suggest to use negative lineal acceleration instead.

Harry

[Harry]

Finally, gears are calculated as they are not standardized in OBD too. So LT requires you to specify a number of transmission values for your car: gear and drive ratios, and tyre dimension. Having this done, LT calculates gears from speed, rpm, and these values. I assume there is a problem in your configuration that results in wrong gear display.

Harry

[Harry]

PS, I will move that thread to using LapTimer

[geogan]

OK great thanks for your replies Harry.

By the way I have been experimenting in Dashware to get RPM needle and video to match perfectly after exporting Laptimer video and CSV data of same video and it appears that in order to get sync between them I have to set an offset of 4.2 seconds.

I don't really understand why this is

Does this mean there is a 4.2 second delay from the real engine data -> ECU -> BT1 -> iPhone -> OBD data recording?

And will this mean it should always be this exact delay for all recordings of this setup?

If not is there some other reason for the mismatch in timing between video and OBD

[Harry]

A misalignment between OBD, acceleration, and GPS should be impossible, the ranges are much smaller and can be compensated using LT's delay settings in Expert Settings. Same is true for video / data recording alignment although videos can be a lot more out of order due to processing issues. Keep in mind that the point alignment is done is the end of the video an recording, not the start. Staring video recording takes up to 2 seconds, and the GPS fix comes in up to two seconds late. Although that is compensated for the timing and recording, it cannot be done for the video. It simply starts late.

Harry

[geogan]

A misalignment between OBD, acceleration, and GPS should be impossible, the ranges are much smaller and can be compensated using LT's delay settings in Expert Settings. Same is true for video / data recording alignment although videos can be a lot more out of order due to processing issues. Keep in mind that the point alignment is done is the end of the video an recording, not the start. Staring video recording takes up to 2 seconds, and the GPS fix comes in up to two seconds late. Although that is compensated for the timing and recording, it cannot be done for the video. It simply starts late.

Harry

OK so it's normal for exported video to need compensation sync offset time added then - that's fine... just wondering.

p.s i don't think i had any misalignment problems between OBD, acceleration, and GPS... and when I finally get my DualXGPS delivered and set it to 5Hz the GPS/acceleration data should be much more accurate than it is now too hopefully

http://www.youtube.com/watch?v=ijyVSRsC ... e=youtu.be

[Harry]

Yes, for sure.

Harry