Android Rookie version: Bugs?
Posted: Sun Aug 18, 2013 1:47 pm
Not sure if its a software bug, or an incompatibility with my OBD hardware/
Info:
Latest Android version of LapTimer (rookie)
Verizon HTC DNA running latest approved OS
QStarz Bluetooth GPS
PLX Kiwi Bluetooth OBDII sensor
GoPro Hero HD
Observation:
After recording a test lap around the town, I exported to CSV and tried to render video overlays in 3 different apps (RaceRender2, Dashware, RaceChrono2Avi). In both RaceRender and Dashware, there were no readings apparent for throttle or brake. Also the gear indicator seemed a bit touchy and wonky reporting the wrong gears most of the time. Oddly enough I just opened the CSV file and saw the column for throttle and gears (including others like MAF) so it seems that the app is *recording* the values, but the programs aren't interpreting them for the overlay?
So at this point I'm not sure if the issue is Lap Timer, an incompatibility with my OBD sensor (doesn't seem so), or an incompatibility in file format with the rendering programs. Any ideas?
For what its worth, RaceChrono2Avi can't even open the CSV file...which doesn't surprise me because its an old, dead project. However it makes me sad because I liked that I could output a video overlay ONLY from that program, then import the video footage and overlay in Adobe Premiere and use that to sync/edit video. I hate using the video synchronization or editor in Dashware or RaceRender...its garbage.
Info:
Latest Android version of LapTimer (rookie)
Verizon HTC DNA running latest approved OS
QStarz Bluetooth GPS
PLX Kiwi Bluetooth OBDII sensor
GoPro Hero HD
Observation:
After recording a test lap around the town, I exported to CSV and tried to render video overlays in 3 different apps (RaceRender2, Dashware, RaceChrono2Avi). In both RaceRender and Dashware, there were no readings apparent for throttle or brake. Also the gear indicator seemed a bit touchy and wonky reporting the wrong gears most of the time. Oddly enough I just opened the CSV file and saw the column for throttle and gears (including others like MAF) so it seems that the app is *recording* the values, but the programs aren't interpreting them for the overlay?
So at this point I'm not sure if the issue is Lap Timer, an incompatibility with my OBD sensor (doesn't seem so), or an incompatibility in file format with the rendering programs. Any ideas?
For what its worth, RaceChrono2Avi can't even open the CSV file...which doesn't surprise me because its an old, dead project. However it makes me sad because I liked that I could output a video overlay ONLY from that program, then import the video footage and overlay in Adobe Premiere and use that to sync/edit video. I hate using the video synchronization or editor in Dashware or RaceRender...its garbage.