This weekend at the track I attempted to use Racechrono with my OBD-II BT dongle. I have previously used Racechrono with no issues, but this was my first attempt with the OBD. Prior to getting to the track, I tried out the OBD with the Torque app, and it worked just fine, though it does prompt you to allow the connection, which means hitting the home key to answer the prompt, but I was able to see all the readings and even clear some fault codes.
So I get to the track, set up RaceChrono like I always do (using a Qstarz BT GPS.) Prior to recording all my sessions, RaceChrono would show a message that OBD is a trial and was set to expire. I got home, exported them to CSV, then imported to Dashware for video sync'ing. But there was no RPM or Throttle position or any other OBD data. I opened the CSV in Excel and saw there was nothing in either of those columns. I rechecked my settings, everything appeared to be correct. Then I noticed an update (to 3.4) was available, so I installed it. Nothing changed but the coloring (from black to white.) Then I noticed I didn't have the gauge page like shown in the examples. So I completely uninstalled the app and reinstalled it. Now I get the gauge and map page, but another warning prevents me from using OBD at all, saying the trial has expired....
I have to deselect the OBD as a recorded sensor in order to use the app. It says it's an in-app purchase, but no link or other information is provided.
[img]
http://www.eatsleeptinker.com/wp-content/uploads/2013/10/Screenshot_2013-10-13-16-36-03.png[/img]
Comments
About importing to DashWare, only the new "RaceRender2" export format supports OBD-II channels. The old "Dashware/RaceChrono2AVI" format doesn't. Unfortunately Dashware does not yet support the new format (at least last time I checked), even though I've sent them samples. You could ask Dashware developer to add support for this, please include a sample as well.
http://www.eatsleeptinker.com/wp-content/uploads/2013/10/Screenshot_2013-10-13-16-35-31.png
Seems like this is different OBD-II problem you experienced earlier, right? I guess you updated to v2.42 already?
Are you running Torque in background at all? You need to exit Torque to be able to RaceChrono.
Here's what I had to do to get it to connect. Start Torque, then I'm prompted to allow pairing of the OBD-II Bluetooth by Android, which I click allow (there's no option to always allow.) Torque connects, starts pulling information. I then exit Torque and start RaceChrono and it connects to OBD and BT GPS. Otherwise I get the "connecting to OBD-II" message at the bottom in the red bar. This is version 3.42. Car is a 2002 BMW M Coupe.
That said, I just reviewed my session exports, and it is still dropping the OBD data, only capturing part of it. I can send you the .csv files if you give me your email.
That was the only bit of OBD data that was recorded for the full 20+ minute session. The rest of the log file is empty in the RPM and throttle position.