Harry's GPS Suite Forum

Harry wrote:Please test your update rates again once v17 is available. I just tested the Dual and receive solid 5 Hz (even when increasing precision to one decimal digit.

The attachment IMG_2298.PNG is no longer available

- Harry

Harry wrote:In version 16.6.2 and before, all update rates were displayed using one decimal digit (e. g. 4.9 Hz). As LapTimer measures update rates instead of using any by-design values, the display typically has been a bit bumpy (not sure this is the right term - I meant it changed a lot) without having a deeper meaning. The changes are simply from noise added whenever you handle real world input. E.g. the measured update rate may vary from 4.9 to 4.8 up to 5.1 without signaling any importing information. There is some smoothing applied but usually you will see changes nevertheless. LapTimer v17 changes this topic in two ways: a) it applies a different and much improved update rate calculation making the value itself more accurate, and less volatile b) it sets default update rate display precision to full Hz. This means - despite the changed algorithm to calculate - you will usually see 5 Hz instead of all the above values.

As LapTimer is a tool designed to show full details if required, you can touch any update rate gadget (like the GPS rate in the screenshots above) to change between 0.0 and 0 precision - once you have v17 This is a general mechanism many users are not aware of: LapTimer displays little field indicators (like "0.0" or the magnifier in the snapshots above) for the individual gadgets. This always means something happens when you touch this gadget. "0.0" means precision is changed, a small wrench means a setting is changed, a magnifier means you will be transferred to another view showing more or related information, the small graph means you get a data history for the value shown, etc.

- Harry

11,09-FEB-13,19:49:09.25,58.200000,32.521717,-97.623545,102.100000,63.441998,299.800000,983.595802,35.9,2,2,12,0.710000,1.2,1.550300,0.963312,1,0.31,0.44,32.521799,-97.623679,0,0.000000,0.000000,0.000000,0.000000,0
11,09-FEB-13,19:49:09.50,58.450000,32.521769,-97.623499,101.800000,63.255587,299.900000,983.923886,38.1,2,2,12,0.710000,1.2,1.557400,0.967723,1,0.36,0.43,32.521868,-97.623650,0,0.000000,0.000000,0.000000,0.000000,0
11,09-FEB-13,19:49:09.75,58.700000,32.521820,-97.623450,104.900000,65.181838,300.000000,984.251970,40.2,2,2,12,0.710000,1.2,1.564700,0.972260,1,0.37,0.43,32.521927,-97.623601,0,0.000000,0.000000,0.000000,0.000000,0
11,09-FEB-13,19:49:10.00,58.950000,32.521870,-97.623397,107.900000,67.045951,300.200000,984.908138,43.2,2,2,12,0.670000,1.1,1.572200,0.976920,1,0.39,0.23,32.521990,-97.623548,0,0.000000,0.000000,0.000000,0.000000,0
11,09-FEB-13,19:49:10.25,59.200000,32.521920,-97.623339,111.000000,68.972202,300.400000,985.564306,45.4,2,2,12,0.670000,1.1,1.579900,0.981704,1,0.45,0.08,32.522064,-97.623508,0,0.000000,0.000000,0.000000,0.000000,0

Harry wrote:Well I tried so hard Precision display does not change anything, correct. But that is item b) from my note. Item a) is a different topic and I'd suggest you re-test once v17 is available. The raw data attached above are recorded at 4 Hz, you can see that easily by watching the time stamps (.25, .50, .75, .00, ...). At 5 Hz, you will see .00, .20, .40, .60, .80, ... Not sure the Dual switches from 4 to 5 Hz depending on the receiving condition.

- Harry

Harry wrote:No, misunderstood, LapTimer just measures, I'm aware it is not the source for any issue (at least here ). Did you get a differential lock (shown as "3D+" or "DGPS" in LapTimer)? When I testing mine yesterday with latest firmware and iOS version, and got 5 Hz, it had clearly no DGPS position (had the receiver in my office).

- Harry