...
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 microcontroller 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 |
---|
Specifies the interval duration after which the device |
---|
transmits any unsent sensor readings. | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Value range |
| ||||||||||||||||||||||||||||||||||
Example |
|
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 |
|
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 | ||
---|---|---|---|
Value range |
|
gnss-force-next-time | Force the device to update its GNSS position information the next time readings are collected. | ||
---|---|---|---|
Value range |
|
gnss-trigger | Configure the device to update GNSS position information only after every the specified number of periodic data sets are collected. | ||
---|---|---|---|
Value range |
|