Versions Compared

Key

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

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

Info

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

...

Drawio
zoom1
simple0
inComment0
custContentId3512598560
pageId3511812097
lbox1
diagramDisplayNamepstart_pdur.drawio
contentVer9
revision9
baseUrlhttps://exelonix.atlassian.net/wiki
diagramNamepstart_pdur.drawio
pCenter0
width1000
links
tbstyle
height206.5

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

...

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

Example

...

Drawio
zoom1
simple0
inComment0
custContentId3512926225
pageId3511812097
lbox1
diagramDisplayNamepxtime.drawio
contentVer4
revision4
baseUrlhttps://exelonix.atlassian.net/wiki
diagramNamepxtime.drawio
pCenter0
width1000
links
tbstyle
height271

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

...

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

Example

...

Drawio
mVer2
zoom1
simple0

...

inComment

...

0

...

custContentId

...

3859873802
pageId3530981377

...

lbox

...

1
diagramDisplayNameUntitled Diagram-1696860677087.drawio

...

contentVer1
revision1
baseUrlhttps://exelonix.atlassian.net/wiki
diagramNameUntitled Diagram-1696860677087.drawio
pCenter0
width1015
links
tbstyle
height261

cid

A custom identifier that will be attached to all telemetry records of the device. After a value was assigned to a device, it can be used instead of the device ID to analyse telemetry data via the Exelonix backend.

Value range

  • Must be a string with a maximum length of 32 characters

  • Only characters a-zA-Z0-9.- are permitted

Note
  • The same value can be assigned to multiple devices. You need to ensure uniqueness across multiple devices yourself if this is required.