...
If the PU message could not be uploaded to the cloud the Send OK\r\n is not sent. In future versions of this protocol we plan on adding a known timeout value and an error response once this timeout has occurred. For now we need to manage timeouts in the PU protocol. See below.
PU_MSG message protocol, version 1.
...
1
The PU_MSG is an 8-bit ASCII encoded string made up of a version field and one or more data label+value pairs. The version and data pairs are delimeted by the | character. The data label and data value are delimited by the @ character.
VERSION|DATA_LABEL@DATA_VALUE or VERSION|DATA_LABEL@DATA_VALUE|DATA_LABEL@DATA_VALUE etc.
For Where the VERSION field value please is the PU_MSG’s major version. Please always use the ASCII 1.
See the table below for possible DATA_LABEL values. The data value must be an alphanumeric ASCII string.
There can be more than one DATA_LABEL@DATA_VALUE pairs, however, the maximum PU_MSG length must not exceed 16 bytes/characters.
Data label | Description | Unit | Example |
|---|---|---|---|
0 | Internal retry counters: msg_count,retry_count | - | 42,7 for msg number 42 since powerup, and transmission this is the 7th try to upload it |
1 | Battery remaining in % | % | 42 for 42% battery remaining |
2 | Battery voltage in 1/10 V | 1/10 V | 362 for 36,2 Volt |
3 | Battery total capacity in 1/10 Ah | 1/10 Ah | 135 for 13,5 Ah max. battery capacity |
After the PU_MSG has been sent the telemetry device should await the PU_ACK message (see the AT protocol section above) and determine if the message should be resent after a timeout.
...