Versions Compared

Version Old Version 1 New Version Current
Changes made by

Uwe Sommerlatt

Uwe Sommerlatt

Saved on

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 that the following description

...

assumes ideal

...

behaviour in terms of

...

timing and durations. In reality

...

, delays and inaccuracies may occur due to

...

varying cellular network

...

conditions 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.

pxtime

...

Specifies the interval duration after which the device

...

transmits any unsent sensor readings.

Value range

  • Must be an integer

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

...

Note

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

Example

...

Drawio
zoom1
simple0
inComment0

...

custContentId

...

3512926225

...

pageId

...

3511812097
lbox1
diagramDisplayNamepxtime.drawio
contentVer

...

4
revision

...

4
baseUrlhttps://exelonix.atlassian.net/wiki
diagramNamepxtime.drawio
pCenter0
width

...

1000
links
tbstyle
height

...

271

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.