1.1.2 and OBD2

[desperado]

Was about to post about OBD2 for DM10 not working, but checked the website and saw 1.1.2 just posted today. It would have been nice to know 1.1.1 wouldn't work with OBD2 before I spent so much time troubleshooting my installation. :)

I've had a couple of issues so far.

The Seek with Data option works in Analysis by Distance, but not in Analysis by Time. And, it crashes Dashware more often than not.

It gets confused because the default OBD2 data profile maps both "mph" and "speed" to Velocity/Speed. I set up three additional Velocity data types: Velocity/OBD Speed ("speed"), Velocity/GPS Speed ("mph"), and Velocity/GPS Calculated Speed (from lat/lon). Then, so I don't have to change the default gauges, I can associate any one of these to Velocity/Speed.

[RandallNoll]

We'll look into the seeking. Thanks for posting on that. I've also just updated the DM10 manual to let people know they need 1.1.2 for OBD2.

It should map the mph from OBD2 to Velocity/Speed, then if that isn't present, go to (I believe) Calculated Speed. Our goal was to get the most accurate speed (from speed sensor via OBD2) and give that priority, but you can alter that in the profile if that isn't the case on your vehicle.

Thanks!

[Rolf]

Sorry for the confusion. You shouldn't have to create more "speed" data types. The way we set the Data Profile up, like Randall said, it should give priority to your OBD-II speed if it exists. If it doesn't exist, it should fall back to the GPS calculated speed.

By the way, it's OK to have more than one data column mapped to a given data type. DashWare will pick the first column it finds in your data.

If you want to explicitly choose your speed column, you can create your own data profile (clone the existing one). Then delete the mappings you don't want to use, and add the single mapping you want.

Make sense?

[desperado]

Thanks to both of you for the input. It does make sense. I realized the priority it was giving to one speed data item over the other. What I wanted to do was compare the OBD2 speed with the GPS speed, to determine the accuracy of the speedo! This required separate Velocity/Speed data items. I was able to do all this just by looking at the examples in the default data profile (without RTFM) so that is a great compliment to your software design.

Also, another comment about Seek with Data. I'd like the cursor on the data charts to move in sync with the video when Seek with Data is turned off and one is using the VCR controls. Then I wouldn't have to use sync with data, which so far is buggy (especially with large files).

[Rolf]

Aha! OK, that makes sense then. :)

We are looking into the Seek with Data issue.

We were thinking of either having playback/VCR controls on the graph side, or a "Seek Data with Video" check box to do what you asked for.