...
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 microcontroller in the order of a minute. |
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 |
|
Value range
pcollect |
---|
Instruct the device to gather multiple measurements locally and send them collectively afterwards via the mobile network.
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 |
|
9
|
86400
|
|
pcollect
mechanism once it has been activated
|
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 |
|