Trouble with GoPoint BT1 and Harrys pro

[CoreForce]

My feedback is less positive unfortunately.

I was running Petrolhead v17.1.5 last weekend.
The GoPoint BT1 is with Firmware 177.0.6
Sometimes the Sensor Information said "parallel requests disabled" only, sometimes it listed those PIDs as in the picture.
The Car was a Ford Focus 2 RS.
Running on iPhone 4, VGA video recording resolution.
I was driving around in the Vogese mountains (France) using the manual record function only (no triggered recording from a previously known track).

When recording, after some sessions I recognized that the gauges always jumped to the values that were valid in the moment when hitting the record button, but remained there static for the rest of the recording. This pattern remained consistent for multiple attempts, also after rebooting the iPhone and retrying.

I can not provide any overlayed video, as this option is not existent in the videos.
When I open one video, the section "LapTimer Integration" under Metadata it just states "Keiner".
Under "Typ" I sometimes can select it from Original (Cam symbol) to Overlay (Gauges symbol) but changing this has no effect at all to the video. I was unable to find any other option to create the overlay. For the videos that were overlayed by VideoPro it recognizes them as such, however.

After recognizing there is no point in continuing this way, I switched over to VideoPro.
This app provided me with OBD2 readings in the usual way (with some wiered drops occasionally but otherwise correct).
Strangely enough however, it does not render G-Force readings, this indicator remains centered, whatever.
I can provide overlay video for this if interested.

For me this was a bit of a bummer as LapTimer did not do any good for me.
It used to work to some extend in older versions though.
Also I'm quite clueless on what to try next in order to make it work.
What I had switched on this time is the turbo indicator. I saw the other thread about it where it was about the calculated boost values and wanted to check if that is already in. Seemed not to be the case. Anyhow, this setting should not have created the results received, is it?

[Harry]

Turbo boost should not be related to this. Can you please check the "OBD Tweaks" Expert Settings and send a snapshot? Once I had a look into this, you may want to follow the FAQ on debugging OBD connections: viewtopic.php?f=20&t=1500

- Harry

[CoreForce]

Expert Settings snapshot as requested.
BT1 not connected at the moment of the snapshot.
Let me know if that would be required.

[Harry]

Please remove the "Exclude PIDs" value (set it to an empty string) and try again. This should actually be cleared in LapTimer v17.1.5... In case it reappears without having "Auto Exclude PIDs" turn on, please let me know!

- Harry

[CoreForce]

This did the trick, thanks.
Looks much better now.

[CoreForce]

So I did some more test runs, still facing challenges.

Petrolhead on version 17.4.1, iOS 7.0, iPhone 4
Situation: switched BT1 and iPhone into other car.

Result 1:
From a fresh start of the app, the data recordings are missing in the video.
I mean, it's not much action there (a friend and me headed to the ZRH airport to see the An225, lot of other people had same idea), but it should render the idle revs at least. I remember that the rev data was there on the screen when the recording was running.
http://www.youtube.com/watch?v=wfmXd9xhNlA

Result 2:
The same like above, but in addition to that one can see that
- the data recording jumps to current values and sticks there at certain points, happens multiple times.
- data was rendered to screen correctly when recording
- it is clearly missing the rendering of the G-Force indicator as well. The indicator was working while recording.
- Video rendering stops way before the end of the recording. It's 1-2 minutes missing to the end.
http://www.youtube.com/watch?v=JbnV63LHydI

I checked the Exclude PIDs setting, it's still empty.

What is puzzling me is the setup of Petrolhead that have to fiddle around often, especially in this car (StreetKa).
Petrolhead has two of my cars set up currently, both recognized by the VIN.
But when I connect in this car, the setup is still always with the other one (Focus RS). In the settings screen, the Focus is listed and cannot be changed. Also a track is listed and cannot be changed there.
When I start Petrolhead, I try to got to the screen for car, driver and track setup. But this one loops forever and cannot be changed there either.
So I end up with always recording into this one track of mine and always the Focus RS, having to change track and car later in each of the recordings manually.

I'm not quite sure whether it is only one issue I observe here or if it is a full load of it. Maybe I do something wrong completely here?
But I want to make sure this thing work before I take it on the track. The least thing I want to do on a track is to have fiddling around and going crazy on it there. It's basically just the driving that I would like to have in focus and therefore this thing should work smoothly then.

Question: What's next?

And yes, I do real driving. Check out here with red-cyan-glasses for some other wired attempt of techy stuff in a race car.
http://www.youtube.com/watch?v=C2lZiEAdvvg

[Harry]

Yes, good idea to sort things out ahead of track days... In case I understand correctly, there are two issues: #1 OBD recording does not work #2 car / vehicle switching, or display in Settings.

To start with the easy #2: please ignore the rows in Settings, they are actually the track and vehicle that were set manually within LapTimer. The strings are not correctly updated when the track or the car are switched automatically. I will remove these items from Settings on the next bug fix release, I had this item in my list for some time.

To check which track and car are those "really" selected, please always use the Event hover view available in every timer view: for example, switch to the Timer tab and press the small wrench. You will get a display similar to this one (upcoming version 17.5) showing the current track, vehicle, driver, and reference lap. In case you want to change these values manually, you can do that from here. Please note track and vehicle are actually switched automatically: track when passing a trigger, and vehicle when connecting an OBD delivering a registered VIN.

Changing the track manually is necessary in case you start a recording manually (e.g. by pressing the red button in Video View or Stopwatch View). As written above, during automatic operation using track sets / triggers, LapTimer changes automatically.

#1 seems to be more difficult. I'm pretty sure that if you look into the data you overlaid to the video, you will see no OBD data has been stored. Please check that using Lap List -> the lap -> Preview -> Charts -> swipe to RPM page or simply export the lap to CSV or HLPTRL and send it to me (Harry@gps-laptimer.de). In case you can reproduce the situation LapTimer shows OBD values in real time but does not store them - this would be a bug and needs to be fixed. To verify this item, would you please repeat the test by recording a short section manually while making sure you see constant change(!) in OBD values and while having good GPS reception? Thanks. The reason I ask is this effects usually appears when either the OBD connection breaks at some time (connection or compatibility issue) - like in the second video, or in case you had no GPS position (which actually means no data is stored - neither for GPS nor for OBD.

Thanks for your feedback.

- Harry

[CoreForce]

#1 seems to be more difficult. I'm pretty sure that if you look into the data you overlaid to the video, you will see no OBD data has been stored. Please check that using Lap List -> the lap -> Preview -> Charts -> swipe to RPM page or simply export the lap to CSV or HLPTRL and send it to me (Harry@gps-laptimer.de). In case you can reproduce the situation LapTimer shows OBD values in real time but does not store them - this would be a bug and needs to be fixed. To verify this item, would you please repeat the test by recording a short section manually while making sure you see constant change(!) in OBD values and while having good GPS reception? Thanks. The reason I ask is this effects usually appears when either the OBD connection breaks at some time (connection or compatibility issue) - like in the second video, or in case you had no GPS position (which actually means no data is stored - neither for GPS nor for OBD.

Hi Harry,

thanks for the quick response.
I just sent you the data by eMail.
I do have data recorded.
In the Map tab I see a short track.
In the Rounds tab I see some data
When selecting the middle "Diagrams" tab, Petrolhead crashes into iPhone home screen.

Now checking on the #2 section...

Thanks for looking into it.
Falk

[Harry]

The crash is a known bug in the Charts area (see troubleshooting section here on the forum). That one will be fixed in 17.4.2.

- Harry

[CoreForce]

As promised I was checking on Nr. 2 this evening.

Thanks for pointing out about the setting of car.
This worked, manually. The car was not detected automatically, though it lists the VIN with it.
But I was able to set track to Undefined and car to correct one.

I started Petrolhead regularly, not on a freshly booted phone though.
I switched off WiFi this time.

I did 3 recordings, for which I already sent you the data.
Video 1 seemed to work fine. It showed all data correctly on the screen when driving. Start/Stop was manual. After stopping and seeing the confirmation message about a round was saved, I've terminated Petrolhead in favor for some driving advise from Waze. After 30 min or so I brought Petrolhead back up. When starting it crashed, and apparently the Video material got lost along with it. After new start it was checking the database but had no warning on integrity like it used to show when crashing while recording.

Video 2 seemed to be recording ok. I had the revs and speed showing up, verifying by bringing the car into rev limiter warning.
Also the G-Force was working fine on the display when cornering. In the Overlay Video, I don't see the data like I saw it while recording. The data is static again for the Overlay. The video lacks the last 14 seconds of audio.
http://www.youtube.com/watch?v=fLosIymQQwA

Video 3 seemed to be fine as well, but I was missing the speed and the gear selection for quite some time in the display when recording.
The moment the speed came up while recording is the same moment when in the overlay there is some short "movement" in the otherwise fixed values. It's around mark 1:22 of the video. Again, all values remain static whilst I've seen them showing correct values when recording.
When rendering the Video I was hitting an error message (see attachment). Second time rendering worked fine, without quitting Petrolhead in between.
http://www.youtube.com/watch?v=C6TGl53NpVw