Lean angle issue? Calibration / Landscape Orientation

[Harry]

Acceleration View is actually portrait only. It rotates to landscape sometimes nevertheless, no idea why... It should be blocked. So please use it in portrait only. As long as you have Motorbike Preset selected, there is no need to calibrate anything. What you need to do is mounting the phone exactly with a tilt of 70 degree and 0 rotation. This should give you (near) zero acceleration while standing still. Acceleration values are shown in several views, not only Acceleration View. Try Timer or GPS (in landscape or portrait) for example. Measured lean angles are very sensible with respect to wrong mounting positions. The effect is you will get too low values for lean.

For your Qstarz issue, there seems to be no other way than logging what is actually going on. Please follow the instructions in viewtopic.php?f=39&t=1933 and enable GPS Sensor and Database trace classes, disable any other please. Log a section where you see 5Hz reported and do some recording. Thanks.

- Harry

[Harry]

@architect, Thanks for sending the GPS log!

I have been able to find the update rate issue. Your XT818 is configured to not deliver RMC (NMEA) sentences. This means LapTimer needs to use combinations from GGA and ZDA sentences to reproduce the information usually available from RMC. Although this is a valid fall back implemented for some time already, it didn't work with second fractions (hundreds) correctly so far. This issue will be fixed in the next bug fix release (19.0.10 or later).

Or in case "NMEA sentence" doesn't tell you anything: the current XT818 device configuration hasn't been handled correctly, but will be in 19.0.10

Please do not change the XT818 configuration now as I'd like to see if the 19.0.10 fix works. Thanks for a short feedback once you can test it. And thanks again for helping.

- Harry

[architect]

Any idea when the new release will be?

I really wanna use the timer!

[Harry]

I have one more bug to fix (a more complicated one). Once this is done, I will release 19.0.10. Maybe today, maybe in two days...

[architect]

I planning on the track Thursday so....
If I don't see an update by then I will switch the settings then switch it back on next release to help you test?

[Harry]

Enough time...

[architect]

Yup no RMC... What do the numbers represent under each variable?

I had followed these settings from another website...

[Harry]

Hi,

The numbers are updates per second. Adding 5 everywhere will need too much bandwidth, so you need to keep some update rates low. I assume the Data Bandwidth is giving an indication on the share of bandwidth available is actually used. The lower, the better. The standard sets supported by LapTimer are:

#1 RMC (high) GGA (high) GSA (1) GSV (1)

and

#2 GGA (high) GSA (1) GSV (1) ZDA (1)

Where "high" is the highest number supported by the receiver (5 or 10 in your case). Set all sentences not listed to zero, they are not used at all.

Option #2 is the one generating the issues we discussed. #1 will work as expected.

- Harry

[architect]

Thanks for the informative reply.

Side question. So I tried to turn on the right data set. But now, the 5hz position only goes to 1hz and the 10hz only shows 2hz in the GPS view... The Environment Distiurbance is <5 so I'm not sure if that has anything to do with it...

[Harry]

Please post a snapshot of the configuration tool.