Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

The application behaviour can be customised via two methods for configuration:

  • Parameters
    The application parameters control the primary aspects of the application

  • User configuration file
    The user configuration file enables fine-grained customisation of the application behaviour
    (e.g. enabling/disabling individual sensors). Please contact support to receive detailed documentation about the user configuration file, its format and options.

Parameters

Please note, the following description considers an ideal behaviour in terms of times and durations. In reality, there will be smaller delays and inaccuracies due to the cellular network as well as due to run time on the device's µ-controller in the order of a minute.

papp

Configures the application variant that is executed

Value range

  • Must be an integer

  • Valid values

    • 0 — Inventory track

    • 1 — Theft track

With the inventory track application, you configure a time of day in which you want to track the device's position. The device won't report a change of position outside the configured interval.

The general idea behind the theft track application is, that you configure a time of day in which motion of the device is allowed. The device will send its position when it detects motion outside the configured interval and ignores movement otherwise.

pmode

The mode parameter determines which events will cause the application to send telemetry data

Value range

  • Must be an integer

  • Valid values

    • 0 — Motion detection

    • 1 — Scheduled intervals

    • 2 — Motion detection and scheduled intervals

pstart

Inventory track:
Denotes the start of the interval in which the device sends positioning information
Theft track:
Denotes the start of the interval in which motion of the device is allowed

Value range

  • Must be an integer

  • The value is interpreted as minutes since 0 o'clock. Hence, it must not exceed 1440. The parameters pstart and pdur are used in conjunction, and therefore the sum of both values must not exceed 1440 as well.

pdur

Denotes the length of the interval that begins after pstart. The semantic of this interval is determined by the application (See papp).

Value range

  • Must be an integer

  • The pdur value is specified in minutes and must not exceed 1440. The parameters pdur and pstart are used in conjunction, and therefore the sum of both values must not exceed 1440 as well.

Example

pxtime

Denotes the length of the intervals after which the device sends new positioning information

Value range

  • Must be an integer

  • The pxtime value is specified in minutes and must be smaller or equal to the pdur value

  • If pmode is set to 0, this setting has no effect

Example

pytime

Denotes a dead time after a motion was detected. Motions of the device within the dead time don't trigger a new transfer of positioning information.

Value range

  • Must be an integer

  • The pytime value is specified in minutes

  • If pmode is set to 1, this setting has no effect

Example

  • No labels