Hi Harry,
Having a problem with the data captured off a BT1A OBD dongle fitted to a Holden Monaro. While it looks to work and reports live data, when you overlay it is all missing but for a very occasional 'blip' of information. I will try and pull all the diagnostic info together using the post I saw about fault finding obd. In the meantime, have you had any other reports of problems with the BT1a or the OBD from a Monaro? HLT does indicate a low refresh rate.
I'm using;
iPod 5 32gb (latest IOS update)
Latest update of HLT GP
Dual GPS150
GoPro 3+ black
BT1a
Thanks in advance.
Dan
Problematic OBD Data
Re: Problematic OBD Data
Hi,
I have no particular experience with the BT1A / Holden Monaro combination. What is the OBD update rate exactly? Please check the Sensor List for the number. In case the OBD real time view is responsive, but does not show up in the recordings, you may check if your GPS reception / recording is good (4 or 5 Hz displayed). LapTimer actually stores GPS positions and augments OBD data. So in case there is a problem with GPS, you may miss OBD data too.
- Harry
I have no particular experience with the BT1A / Holden Monaro combination. What is the OBD update rate exactly? Please check the Sensor List for the number. In case the OBD real time view is responsive, but does not show up in the recordings, you may check if your GPS reception / recording is good (4 or 5 Hz displayed). LapTimer actually stores GPS positions and augments OBD data. So in case there is a problem with GPS, you may miss OBD data too.
- Harry
Re: Problematic OBD Data
Hi Harry,
Returning to this issue as I didn't get to resolve it. Still running the same hardware but now on iOS 8.1.2. HLT always updated before use.
Settings in Expert Settings - OBD Tweaks
Speed Multiplier = 1
Throttle PID = Position B
Default Protocol = Automatic
Ignore NO Data/NAK replies = ON
Request Sequence Pause 0.01
Sequential Requests (BT1) = OFF
CAN Multi Requests (ELM327) = OFF
Custom Host = 0.0.0.0
Custom Port = 0
Auto Exclude PID's = ON
Exclude PID's = 010001200140
While on track, OBD data is being received as RPM, temp, fuel, throttle, gear change warning, all display. However, when an overlay is produced, there is no OBD data other than about 4 or 5 frames. In the .hlptrz file, this is verified by only those frames having any OBD data attached.
I did switch from Throttle PID A to PID B and this did resolve the live data display but I later found it hadn't resolved the overlay data.
Strangest thing of all that I have discovered from comparing a few .hlptrz exports is that the one frame of data happens at effectively the same location on the track. I haven't worked out if this is a time or location related phenomena yet but will check a few more.
Any suggestion as to why data would be received and displayed live on the screen but not recorded in the .hlptrz file? Is this an overhead issue from using video as well?? I record at 720P on the ipod.
I should also add that I have the iPod more or less for the exclusive use of HLT, so it has very few apps installed.
Thanks,
Returning to this issue as I didn't get to resolve it. Still running the same hardware but now on iOS 8.1.2. HLT always updated before use.
Settings in Expert Settings - OBD Tweaks
Speed Multiplier = 1
Throttle PID = Position B
Default Protocol = Automatic
Ignore NO Data/NAK replies = ON
Request Sequence Pause 0.01
Sequential Requests (BT1) = OFF
CAN Multi Requests (ELM327) = OFF
Custom Host = 0.0.0.0
Custom Port = 0
Auto Exclude PID's = ON
Exclude PID's = 010001200140
While on track, OBD data is being received as RPM, temp, fuel, throttle, gear change warning, all display. However, when an overlay is produced, there is no OBD data other than about 4 or 5 frames. In the .hlptrz file, this is verified by only those frames having any OBD data attached.
I did switch from Throttle PID A to PID B and this did resolve the live data display but I later found it hadn't resolved the overlay data.
Strangest thing of all that I have discovered from comparing a few .hlptrz exports is that the one frame of data happens at effectively the same location on the track. I haven't worked out if this is a time or location related phenomena yet but will check a few more.
Any suggestion as to why data would be received and displayed live on the screen but not recorded in the .hlptrz file? Is this an overhead issue from using video as well?? I record at 720P on the ipod.
I should also add that I have the iPod more or less for the exclusive use of HLT, so it has very few apps installed.
Thanks,
Re: Problematic OBD Data
Hi,
For the current version of LapTimer, please start with turning ON "Sequential Requests (BT1)". The parallel requests generate a timing issue and will make incoming OBD data incomplete. I doubt it is related to the problem raised - but you never know.
To debug the thing I'd recommend to vary the recording scenario to find the root cause: please turn "Manual Timing" ON in LapTimer's Settings. This allows you to record arbitrary drives using standard timer views (not video). Now, switch to Timer View and drive around. Verify you get consistent OBD input (changing constantly). Once this is verified, press "Start" in Timer and record a minute. "Stop" the recording afterwards. Repeat the same steps including video. Instead of using the Start / Stop buttons in Timer view, you can use stay in Video View and use the rd / green manual buttons here.
Back home, check both "lap" recordings in (GPS / OBD speed chart for example) and let me know what you see.
- Harry
For the current version of LapTimer, please start with turning ON "Sequential Requests (BT1)". The parallel requests generate a timing issue and will make incoming OBD data incomplete. I doubt it is related to the problem raised - but you never know.
To debug the thing I'd recommend to vary the recording scenario to find the root cause: please turn "Manual Timing" ON in LapTimer's Settings. This allows you to record arbitrary drives using standard timer views (not video). Now, switch to Timer View and drive around. Verify you get consistent OBD input (changing constantly). Once this is verified, press "Start" in Timer and record a minute. "Stop" the recording afterwards. Repeat the same steps including video. Instead of using the Start / Stop buttons in Timer view, you can use stay in Video View and use the rd / green manual buttons here.
Back home, check both "lap" recordings in (GPS / OBD speed chart for example) and let me know what you see.
- Harry