Harry's GPS Suite Forum

The latest 17.4.3 does an awesome job. Thanks!
I probably will need to fix the timing a bit, but running two tests with manual recording today showed good results on OBD data.
http://www.youtube.com/watch?v=hYakDspe-lc
http://www.youtube.com/watch?v=5Ee5_p45h_M
However, what is still visible in the movie is that the G-Force is not rendered.
G-Force is also missing in the (now working) graphs for recorded data.
When recording the videos, the G-Force indicator moved correctly, however.
Assuming though this is no longer an issue with the BT1 connection.
GPS/Accelerator readings are coming from an from iPhone 4 purely.

Happy to hear. On acceleration: except there is something very strange going on, I'd assume the missing acceleration is related to the usual issue with missing calibration while standing still. This however would mean you do not get it displayed in real time either...

Harry

You are right. Calibrated and it worked fine. Thanks!

This is a video that is depicting quite well current experience with latest Petrolhead:
- RPMs are available nearly all the time when driving, some occasional drops but very ok overall. That is very much better than before and gave me an excellent impression at first.
- for OBD-Speed and gear I notice longer periods of outages while driving
- When the video is rendered, the outages of the Speed and Gear are impacting the rendering of the RPMs as well for some strange reason. I'm given dropped RPMs where I am sure they were intact while driving, including some rev limiter warnings that happened when in the video the RPMs are nulled.

[youtube]http://www.youtube.com/watch?v=G2LSU0LC3A8[/youtube]

sidenote: video is from engine start until shutdown. there is some initial delay in OBD data as the BT1 dongle takes some time to start up. SIgnificant outages can be seen from 0:52 onwards. Around 10min there is a sequence of even speed, the OBD performance appears to be better then, but that might be a coincidence.

Actually this is an indicator the car / LapTimer OBD communication has still some problems. LapTimer requests a number of PIDs in a cycle. In case one PID is not answered correctly, the whole process gets stuck. In cases like this, the BT1 will start sending a standard set of PIDs - which is RPM only by default. So my theory is there is still a compatibility issues happening from time to time. During this outages, RPM is displayed from the auto-updates and displayed in real time view. However, as the overall cycle is not successful, data is not stored. Sorry to say, but to debug that, I need one more log including a section where one of these outages occur.

- Harry

I was considering that, I should be able to create a longer log tonight.
However, when I run the original GoPoint app in the very same setup, this is listing me all the data (RPM, speed, and others like temp, ignition timings etc) and this is available from the very beginning and I do not observe any drop there at any time...

The GoPoint App uses a completely different dialog for requesting data. I just displays what it gets and does not need to manage timing consistency, make sure the best update rates are achieved etc.

- Harry

Submitted a log from an longer run this morning.
I noticed no drops in RPM when using the Buddy App, however.

I recall myself that the Buddy app has not been updated for quite a while, if I remember correctly. It might be using OBD readout code that is different from current Laptimer?

Also I'd like to add that Laptimer used to work nearly perfect for me in the past. It used to be way better than VideoPro, which is no longer the case unfortunately. The problems I observe now were popping up roughly around the timeframe when the rebranding into the different editions of LapTimer was made.

The only difference between the OBD implementation of the current GPS / OBD Buddy and LapTimer is it is an iOS6 built being treated different by iOS7 like native iOS7 builds. So no difference here except potential iOS7 issues. I think we had the discussion on old vs. new OBD implementation already. The old one has been less sophisticated, the new one is faster and has more features. It is more picky against sloppy OBD implementations - that is the downside.

I cannot see too much problems in the log you sent, the dropout we discussed did not happen. What I can see is your car does not respond with a valid vehicle identification number when asked. So you may exclude this PID from the request adding "0902" to the Exclude PIDs Expert Setting. This at least will speed up things and probable improve a timing issue that generates the drop outs. Just a try...

- Harry

Wanted to come back with some feedback.
Still facing the issues, unfortunately.
Putting the "0902" to the Exclude PIDs Expert Setting brought very little to zero benefit.
With 17.4.x issues with extensive dropouts
With 17.5.0 complete lockup of screen, unusable
With 17.5.1 same as before with 17.4.x

From latest testing I can clearly see the data arrives correctly when not recording nearly all of the time.
When starting recording, after around 1.30 min the speed and gear data is lost and comes back only after several minutes, for some seconds only.
After stop of the recording it takes a while but then live data comes back without drops.
Also I did some tests with another car (Ford Focus 1) with about the same results.

Things run better on a freshly booted phone, but for the first recording only. After subsequent recordings and/or some rendering or other activity, the problems develop towards as described.
I've checked the new System Status overview screen. There I've seen the OBD rate in green when recording showed dropping.