Versions Compared

Version Old Version 7 New Version Current
Changes made by

Uwe Sommerlatt

Uwe Sommerlatt

Saved on

Key

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

...

Parameters

Info

Please note , that the following description considers an assumes ideal behaviour in terms of times timing and durations. In reality, there will be smaller delays and inaccuracies may occur due to the varying cellular network as well as due to run time on the device's µ-controller in the order of a minuteconditions and the time required to obtain a position using the global navigation satellite system, resulting in potential transmission delays of several minutes. This becomes particularly noticeable when small intervals are configured for pxtime and pytime.

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.

...

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

Specifies the interval duration after which the device

sends new

transmits any unsent positioning information and sensor readings.

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
inComment0
custContentId3859873802
pageId3530981377
lbox1
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.

pcollect

Specifies the duration of the interval at which the device collects new sensor readings. These readings are stored locally and transmitted after the specified pxtime has elapsed. This functionality supports use cases where sensor data needs to be collected without being immediately sent.

Value range

  • The value is specified in minutes

  • Must be a float or an integer

  • Minimum value: 0.15

  • Maximum value: 1440

Note

  • The pcollectfunctionality is deactivated by default. In this case, the device will report value 0 for this parameter and new sensor readings are gathered in pxtime intervals.

  • Once activated, pcollect can’t be reset to 0 again. To achieve the same behavior as when pcollect is not activated, set its value equal to pxtime.

gnss-force-next-time

Force the device to update its GNSS position information the next time readings are collected.

Value range

  • Must be an integer

  • Valid values

    • 0 — Don’t force an update of the GNSS position information

    • 1 — Force an update of the GNSS position information

Note

  • When the device receives no GNSS signal, the position information won’t be updated, regardless of this setting.

  • The device will automatically reset this parameter to 0 after it executed the forced update.

gnss-trigger

Configure the device to update GNSS position information only after every the specified number of periodic data sets are collected.

Value range

  • Must be an integer

  • Minimum value: 0

  • Maximum value: 99999

Note

  • Setting the value to 0 disables the collection of GNSS position information for periodic transmissions.