Jump to content

LIGO Air Configuration: Difference between revisions

From SOJI ELECTRONICS
[unchecked revision][unchecked revision]
No edit summary
Line 1: Line 1:
= LIGO Air Configuration =
= Package contents =


This page describes how to configure the LIGO AIR fuel level sensor, including BLE mobile application setup, calibration procedure (Set Empty / Set Full), calibration table options, and advertising protocol integration.
This page describes how to configure the LIGO AIR fuel level sensor, including BLE mobile application setup, calibration procedure (Set Empty / Set Full), calibration table options, and advertising protocol integration.

Revision as of 01:45, 13 May 2026

Package contents

This page describes how to configure the LIGO AIR fuel level sensor, including BLE mobile application setup, calibration procedure (Set Empty / Set Full), calibration table options, and advertising protocol integration.

Mobile Application

To configure the LIGO AIR fuel sensor, download the LIGO BLE Configurator app:

  • iOS: Available on App Store
  • Android: Available on Google Play (CH Play)

Hereinafter LIGO BLE Configurator is referred to as the "application" or "app".

Note: For full operation, you must grant all the permissions requested by the app (Camera, Location, Nearby devices, Bluetooth).

File:LIGO-AIR-app-permissions.png
Granting permissions for LIGO BLE Configurator

Connecting Sensor

  1. Run the application
  2. Open the device list and select the sensor you want to connect to
  3. Wait for the sensor to appear in the discovered devices list
  4. Press Connect next to the desired sensor

Each sensor in the list shows:

  • Device name (e.g., LIGO AIR_7EEF7E7F)
  • RSSI (signal strength)
  • Temperature
  • Current fuel level
  • Battery voltage (Vbat)
  • Firmware version (FW)
File:LIGO-AIR-device-list.png
Selecting LIGO AIR from device list

Recommendation: Signal strength (RSSI) at the receiving device must be ≥ -80 dBm. For weak signal cases, use LIGO PRO or LIGO AIR Adapter.

Calibration: Set Empty / Set Full

After installation, the sensor must be calibrated to ensure accurate measurement.

Step 1: Set Full

  1. Immerse the sensor in fuel until the fuel reaches the sensor flange
  2. Wait for the C_working value to stabilize
  3. Press Set Full button in the app
File:LIGO-AIR-set-full.png
Set Full procedure

Step 2: Set Empty

  1. Remove the sensor from the fuel
  2. Wait for 1–2 minutes to allow the fuel to drain from the measuring probe
  3. Press Set Empty button in the app
File:LIGO-AIR-set-empty.png
Set Empty procedure

Reference Values

Field Description Example
C_working_compensated Current capacitance value (temperature compensated) 19747
C_Min Captured "empty" reference value 4000
C_Max Captured "full" reference value 200000

Calibration Table

Volume measurement can be obtained in two ways:

Method Description
Calibration table on the Platform (Server) The sensor sends raw level values (0 to 4095) to the server via the telematic device. The platform uses a calibration table to convert these values into volume (liters).
Calibration table on the Sensor The sensor directly sends volume values (liters) based on the internal calibration table.

Note: For LIGO AIR sensors, the manufacturer recommends performing the calibration table on the platform.

Configurable Parameters

Parameter Description Default / Range
Device name Sensor BLE name shown in scan list LIGO AIR_<MAC>
Advertising protocol Protocol used in advertising packet SOJI (default) / Mielta / Escort
Measurement interval Sampling rate 5 to 10 seconds
Advertising message interval How often the sensor broadcasts LIGO AIR: 5–10s, LIGO AIR PRO: 10–15s
Output mode Raw value or liters 0–1023 / 0–4095 (default) / Liter 0–65535
Password Access password Must change default password to prevent unauthorized access

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
File:LIGO-AIR-payload-example.png
Payload data decoding example

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
18/06/2025 Protocol Integration 1.0 Initial Release
27/08/2025 Protocol Integration 1.1 Minor changes
SOJI Electronics