-
Notifications
You must be signed in to change notification settings - Fork 0
Octa Payload Format
mdemeyer edited this page Sep 21, 2020
·
1 revision
The idea of defining an octa payload format is to standardize the way sensor data is sent over different wireless technologies. In order to cope with technologies with severe constraints on payload size (e.g. Sigfox), the message overhead is kept to a minimum.
The payload format consists of a concatenation of pairs, where is uniquely defined below. is defined to be 1 byte long. Some values of have a special meaning and cannot be used as a regular "sensor type identifier". A list of defined types is included below. The length of is defined by the field.
| type (1b) | value |
|---|---|
| 3 | GPS (long): LAT, LON, HDOP, each as 4 byte single precision float, little endian. |
| 7 | CO2: 4 byte unsigned integer, little endian. |
A full list of these type bytes is kept in the core/common/inc/payloadformat.h file.