LIGO AIR Protocol: Difference between revisions
| [checked revision] | [checked revision] |
| Line 11: | Line 11: | ||
'''Example Manufacturer Data:''' <code>0x0CFFFC0D024D0100241F000600</code> | '''Example Manufacturer Data:''' <code>0x0CFFFC0D024D0100241F000600</code> | ||
{| class="wikitable" style="width:100%; | {| class="wikitable" style="width:100%; text-align:center;" | ||
|- | |- | ||
! Sequence number of bytes !! Description !! Example | ! Sequence number of bytes !! Description !! Example | ||
Revision as of 01:55, 29 June 2026
General Introduction
LIGO AIR Protocol utilizes Bluetooth Low Energy (BLE) to transmit structured fuel sensor data in advertising packets at regular intervals. Data includes fuel level, battery voltage of sensor, temperature, etc. For long-range applications, LIGO AIR Adapter is recommended to boost reception.
In addition to its native protocol, LIGO AIR supports both the Escort and Mielta protocols, enabling seamless protocol switching without requiring additional integration effort. Users can configure the desired protocol via the mobile application.
Advertising Message Format
Structure of Manufacturer Data field in advertising message (same for any type of peripheral unit).
Example Manufacturer Data: 0x0CFFFC0D024D0100241F000600
| Sequence number of bytes | Description | Example |
|---|---|---|
| 0 | Length of field | 0x0C
|
| +1 | Type of field (Manufacturer data) | Always 0xFF
|
| +2 | Company ID | 0x0DFC
|
| +4 | Hardware ID (type of device) | |
| +5 and further | Payload (sensor parameters) | 0x4D0100241F000600
|
In order to distinguish between types of hardware, the Hardware ID byte is used (see list of hardware below). The Hardware ID byte defines a set of useful parameters from the peripheral unit, their size, and order.
| Byte of Hardware ID | Type of Hardware |
|---|---|
0x02 |
LIGO Air |
0x03 |
LIGO Air Pro |
The list of hardware may be expanded.
Payload data format of LIGO AIR (Hardware ID 0x02) and LIGO AIR Pro (Hardware ID 0x03).
LIGO Air and LIGO Air Pro have the same payload data format. The structure of the payload is listed in the table below:
| Sequence number of bytes | Parameter type | Parameter length (bytes) | Range | Unit of measurement |
|---|---|---|---|---|
| 0 | Fuel level | 2 | 0 to 1023 (option), 0 to 4095 (default), or 0 to 65535 (option, liters) |
Arbitrary units |
| +2 | Reserved | 1 | N/A | N/A |
| +3 | Built-in battery voltage | 1 | 0 to 255 | Volt × 10 |
| +4 | Temperature | 1 | −128 to 127 | Celsius degrees |
| +5 | Reserved | 1 | N/A | N/A |
| +6 | Firmware version | 1 | 0 to 255 | Version number |
| +7 | Operation Mode | 1 | 0 and 1 | 0: Working Mode 1: Storage Mode |
Example Payload data: 0x4D0100241F000600
| 0x4D0100241F000600 | |||||||
| 4D01 | NA | 24 | 1F | NA | 06 | 00 | |
|---|---|---|---|---|---|---|---|
| Fuel level | Reserved | Battery voltage | Temperature | Reserved | Firmware version | Operation Mode | |
| Convert to little-endian (hex) | 014D | NA | 24 | 1F | NA | 06 | 00 |
| Convert to decimal | 333 | NA | 36 | 31 | NA | 006 | 0 |
| Convert to value | 333 (unit or liter) | NA | 3.6 Volt | 31 ºC | NA | 0.0.6 | Working mode |
Revision History
Loading revision history...