LIGO AIR Datasheet: Difference between revisions
| [unchecked revision] | [checked revision] |
m Admin moved page LIGO Air Datasheet to LIGO AIR Datasheet |
|
(No difference)
| |
Revision as of 02:34, 14 May 2026
Protocol Integration
LIGO AIR utilizes Bluetooth Low Energy (BLE) to transmit structured fuel sensor data in advertising packets at regular intervals. Data includes fuel level, battery voltage, temperature, and operation mode. For long-range applications, the LIGO AIR Adapter is recommended to boost reception.
In addition to its native protocol, LIGO AIR supports both 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 the Manufacturer data field in the 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) | 0x02 – LIGO Air |
| +5 and further | Payload (sensor parameters) | 0x4D0100241F000600 |
Hardware ID Mapping
In order to distinguish between types of hardware, the hardwareid byte defines a set of useful parameters from the peripheral unit, their size and order.
| Byte of hardwareid | Type of hardware |
|---|---|
| 0x02 | LIGO Air |
| 0x03 | LIGO Air Pro |
The list of hardware may be expanded.
Payload Data Format
LIGO Air and LIGO Air Pro use the same payload data format.
| 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) / Liter: 0 to 65535 (option) | Arbitrary units |
| +2 | Reserved | 1 | NA | NA |
| +3 | Built-in battery voltage | 1 | 0 to 255 | Volt × 10 |
| +4 | Temperature | 1 | -128 to 127 | Celsius degrees |
| +5 | Reserved | 1 | NA | NA |
| +6 | Firmware version | 1 | 0 to 255 | Version number |
| +7 | Operation Mode | 1 | 0 and 1 | 0: Working Mode, 1: Storage Mode |
Example Payload Decoding
Example Payload data: 0x4D0100241F000600
| Bytes | 4D01 | NA | 24 | 1F | NA | 06 | 00 |
|---|---|---|---|---|---|---|---|
| Field | Fuel level | Reserved | Battery voltage | Temperature | Reserved | Firmware version | Operation Mode |
| Little-endian (hex) | 014D | NA | 24 | 1F | NA | 06 | 00 |
| Decimal | 333 | NA | 36 | 31 | NA | 006 | 0 |
| Value | 333 (unit or liter) | NA | 3.6 Volt | 31 °C | NA | 0.0.6 | Working mode |
Security Recommendations
- Change the default password provided by the manufacturer immediately after first connection to prevent unauthorized access
- Verify the sensor's MAC address against the manufacturer's QR code label to confirm device authenticity
- Restrict app installation to authorized technicians only
Revision History
| Date | Document | Version | Description | Action |
|---|---|---|---|---|
| 18/06/2025 | Protocol Integration | 1.0 | Initial Release | None |
| 27/08/2025 | Protocol Integration | 1.1 | Minor changes | 📄 View ⬇ Download |