Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • minimal trip duration - Trips of less than 130 seconds are ignored.

  • minimal trip distance - Trips of less than 215 meters are ignored.

  • minimal parking duration - Parking for less than five minutes does not detected as stop.

  • minimal no data duration - Gaps in reported positions longer than one hour are considered as stops.

  • ignition - Force switch to stop state if eBike is switched off.

  • speed threshold - If the speed is above 0.01 knots, the bike is considered to be in motion.

Following is an example to illustrate how it works:

...

Is there a particular cadence of events when a ride starts?

Typically:

  1. “Status Online" when bike is slightly moved

  2. "Alarm vibration” when bike is moved more

  3. "Ignition on” once bike gets switched on

  4. “Moving” once bike rides at least 215 meters or for 130 seconds

What does the Stops report tell us?

...

Both of the above should not happen in an ideal world. Usually this is related to a bad GPS reception:

  1. The tracker is in an area with no / bad GPS reception like: indoor parking, tunnel, narrow valley,…

  2. The tracker was not properly installed within the bike: PowUnity symbol not pointing outwards or put inside the frame (covered with metal)

In case the tracker was offline for a longer period it will take longer to get the first GPS fix, so the beginning of the ride might will have a straight line (from old location to first fix).

...

There are two ways how the push notification (which triggers the sound) is handled by the app depending on it’s state:

  1. The app is in the background (or not running):
    none of our app code is run -> the push is handled only by the OS / browser. In that case the alarm will only sound for a few seconds and then stop - unless the backend / server sends another push because the device is still moving and movement alarm was triggered again.

  2. The app is in the foreground:
    Notification is handled by our app code and we start playing the alarm sound in a loop until the user switches if off (by toggling the alarm button).

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@3c93c68
sortmodified
showSpacefalse
reversetrue
typepage
cqllabel = "kb-how-to-article" and type = "page" and space = "BTAPI"
labelskb-how-to-article

...