Accuracy - is important.

The accuracy settings available in your Object -> Edit settings page, are used to ensure the time matches, and the rest of the settings are used for history data filtering, and reports.

  • Time Zone offset - If you are unable or unwilling to set your hardware timezone to UTC-00, you can change it here, and we'll adjust the values into UTC from this value whenever we receive data. (This does change the data, so do not change unless you have to!
  • We use the "Detect Stops Using" formula to tell when you last stopped, so we can show you the stop on the history.
  • Min. moving speed in km/h (affects stops and track accuracy, default 6) - is used to filter small motion from triggering stop detection
  • Min. engine idle speed in km/h (affects engine idle status, default 3) - you can have a speed while at idle, for instance at the lights. This is the the lowest speed we would call "idle"
  • Min. difference between track points (eliminates drifting, default 0.0005) - this is the raw floating point difference between different gps coordinates, to prevent duplicates from muddying up reports.
  • Min. gpslev value (eliminates drifting, default 5) - if your device can (it should) report the number of satellites it can see at this time, we can use this to filter any datapoints recorded from low-accuracy "low-satellite".
  • Max. hdop value (eliminates drifting, default 3) - if your device can report this (GTKPRO+ do) we can use it to make the history reports even more accurate. It essentially calculates how inaccurate the gps reading is. When you have less than 9 satellites, you have to assume you are on the earth side of intersecting spheres, the less you have or the closer the satellites are together, the less accurate it is, or "the precision is diluted", hence: Horizontal Dilution of Precision". I wouldn't change this, but you can if you want to play with history pages and live in a place with spotty satellite coverage.
  • We don't currently support the fuel filling checks, so just leave those as they are.
  • Finally, if you want to reread the sensors, you can clear them, this is useful if your device sets parameters high, but you don't want to manually reset them all.. you can clear them all here, and the next datapoint will set all the parameters.