| Info |
|---|
The application behaviour can be customised via two methods for configuration:
|
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 |
|
...
|
...
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 |
|
...
|
...
|
...
|
pstart | Inventory track: |
|---|
...
|
|---|
...
Value range |
|
...
|
pdur | Denotes the length of the interval that begins after |
|---|
...
| |
|---|---|
Value range |
|
Example |
...
|
pxtime |
|---|
...
Denotes the length of the intervals after which the device sends new positioning information |
|---|
...
Value range |
|
...
| ||
Example |
...
|
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 |
|
...
| ||
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 |
|