SOJI ELECTRONICS - User contributions [en]

File:CalibTable-Generator-Icon.png

2026-11-09T07:01:41Z

Admin:

CalibTable Generator

2026-11-09T06:56:44Z

Admin: /* Support / Contact */

== Overview ==
This feature generates a complete fuel tank calibration table from just '''three refuels'''. The user only needs to select the tank shape, enter the tank height and the sensor height after cutting, and the fuel level and litres of each refuel; the app calculates all points of the table automatically, with no need to fill in small increments and manually record each point. Available from app version 2.2.4.

The table generator has two modes:

{| class="wikitable"
|-
! Mode !! Description !! Sensor connection !! Output
|-
| Standalone || Refuel data is already available, or preparing a table for LIGO AIR, LIGO MAX, LIGO PRO BLE || Not required || CSV file
|-
| Sensor Live || Calibrate directly on the vehicle while connected to a LIGO AIR or LIGO PRO BLE / PRO 2(S) sensor || Required || Written directly to the sensor or to a CSV file
|}

Supported tank shapes:

<gallery mode="packed" widths="200" heights="150">
File:AutoCalib-tank-parallelepiped.png|''Parallelepiped''
File:AutoCalib-tank-cylinder.png|''Cylinder''
File:AutoCalib-tank-dshape.png|''D-shape''
</gallery>

== Preparation ==

* The fuel tank is empty or fully drained.
* The sensor has been cut to the correct length and installed on the tank.
* A tool to accurately measure the litres added is available (a metered pump or a calibrated measuring container).
* The two tank dimensions are known:
** '''H – Tank height (cm):''' the internal height of the tank at the sensor mounting position, measured from the bottom.
** '''L – Sensor height (cm):''' the length of the sensor after cutting, measured from the lower edge of the aluminium tube to the underside of the sensor base.

The difference '''d = H − L''' is the bottom gap; fuel below the probe tip is not measured by the sensor.

'''Three-refuel plan:'''

# '''Refuel 1 (offset):''' starting from an empty tank, fill to about 5–10 % of the tank volume.
# '''Refuel 2:''' fill to about 40–60 %.
# '''Refuel 3:''' fill the tank completely (100 %).

'''Note:''' For each refuel, record only the litres added in that refuel; '''do not accumulate''' the litres from previous refuels.

<div style="text-align:center;">[[File:AutoCalib-dim-cylinder.png|frameless|400px]]<div style="font-style:italic; color:#555;">Figure 1. Tank height H, sensor height L and bottom gap d</div></div>

== Opening the Calibration Table Generator ==

=== Standalone Mode ===

# Open the app; on the '''Bluetooth Products''' page, select '''CALIBTABLE GENERATOR'''.
# The '''CalibTable Generator''' page opens; no sensor connection is required.

=== Sensor Live Mode ===

# Connect the LIGO AIR or LIGO PRO BLE sensor as usual.
# Go to the '''Settings''' tab > '''Calibration Table''' > '''Auto Calibration'''.

The page looks the same as in Standalone mode, with an additional '''Fuel level from sensor''' line showing the live reading from the sensor.

'''Note:''' The '''Manual Calibration''' item in the same menu is used to build a multi-point calibration table manually; this document covers Auto Calibration only.

<gallery mode="packed" widths="250" heights="500">
File:AutoCalib-01-products-generator.png|''Figure 2. CALIBTABLE GENERATOR on the Bluetooth Products page''
File:AutoCalib-02-settings-calibration-table.png|''Figure 3. Settings > Calibration Table''
File:AutoCalib-03-calibration-menu.png|''Figure 4. Calibration Table menu''
</gallery>

== Step 1 – Tank Type and Dimensions ==

# Select the tank shape: '''Parallelepiped''', '''Cylinder''' or '''D-shape'''.
# Enter '''Tank height (H)''' and '''Sensor height (L)''' in cm (decimals are accepted, e.g. 60.5).
# The app automatically calculates '''Bottom gap: d = H − L'''.

* L must not be greater than H.
* Tap the ⓘ icon next to each field to view a short explanation.

<gallery mode="packed" widths="250" heights="190">
File:AutoCalib-dim-parallelepiped.png|''Measuring H, L – rectangular box''
File:AutoCalib-dim-cylinder.png|''Measuring H, L – horizontal cylinder''
File:AutoCalib-dim-dshape.png|''Measuring H, L – D-shape''
</gallery>

== Step 2 – Refuel Calibration ==

The refuel table has three rows, one per refuel (row 1 starts from an empty tank). Target fill levels for each tank shape:

{| class="wikitable" style="text-align:center;"
|-
! Refuel 1 (offset): 5–10 % !! Refuel 2: 40–60 % !! Refuel 3: full (100 %)
|-
| [[File:AutoCalib-refuel-parallelepiped-1.png|frameless|180px]] || [[File:AutoCalib-refuel-parallelepiped-2.png|frameless|180px]] || [[File:AutoCalib-refuel-parallelepiped-3.png|frameless|180px]]
|}

Refuel table columns:

{| class="wikitable"
|-
! Column !! Description
|-
| Fuel level start || Taken automatically from the Fuel level end of the previous row; the first row is always 0.
|-
| Fuel level end || Fuel level reported by the sensor after the refuel, in sensor units (0 – 4095).
|-
| ΔV (L) || Litres added in this refuel (not cumulative).
|}

For each refuel:

=== In Standalone Mode (the user already has the refuel data) ===

Enter the existing data of the 3 refuels into the 3 corresponding rows '''1st refuel''', '''2nd refuel''', '''3rd refuel''' (including the Fuel level end and the corresponding litres of that refuel).

=== Reading the Fuel Level in Sensor Live Mode ===

# Fill to the target level for that row and wait for the fuel surface to settle.
# Read the fuel level from the sensor and enter it in '''Fuel level end'''.
# Enter the litres added in '''ΔV (L)'''.

* Tap ⓘ next to the row name to view the target fill level illustration for the selected tank shape.
* When you enter '''Fuel level end''', the tank illustration in Step 1 shows an estimated % mark, helping you check whether the value is reasonable.

The '''Fuel level from sensor''' line above the refuel table shows the live reading with its status:

* '''Stable''' (green): enter this value in the '''Fuel level end''' of the current refuel.
* '''Unstable''' (red): the fuel surface is still moving – wait longer before recording.

=== Rows Highlighted in Red ===

A refuel row turns red when '''Fuel level end''' ≤ '''Fuel level start''', '''Fuel level end''' > 4095, or '''ΔV''' ≤ 0. Correct the values in that row before generating the table.

== Step 3 – Export the Table ==

# Select '''Sensor type'''; the number of calibration points is set automatically according to the sensor.
# To use a different number of points: select '''Custom''' and enter it in '''Calibration points (custom)'''; the points are distributed evenly over the 0 – 4095 range.
# Tap '''Generate calibration table'''. If the data is invalid, a red message box appears above the button (see the Error Messages section).

{| class="wikitable"
|-
! Mode !! Sensor type options
|-
| Standalone || LIGO AIR (50 points), LIGO PRO BLE (30 points), LIGO MAX (100 points), Custom (2 – 200 points)
|-
| Sensor Live – LIGO PRO BLE || LIGO PRO BLE (30 points), Custom (2 – 30 points)
|-
| Sensor Live – LIGO AIR || LIGO AIR (50 points), Custom (2 – 50 points)
|}

<gallery mode="packed" widths="250" heights="500">
File:AutoCalib-04-step1.png|''Figure 5. Step 1 – tank type and dimensions''
File:AutoCalib-05-step2.png|''Figure 6. Step 2 – refuel calibration''
File:AutoCalib-06-step2-live.png|''Figure 7. Fuel level from sensor (Sensor Live)''
File:AutoCalib-07-step3.png|''Figure 8. Step 3 – export settings''
</gallery>

== Results ==

The '''Results''' page shows:

{| class="wikitable"
|-
! Item !! Description !! Item !! Description
|-
| Tank shape || Selected tank shape || V(4095) || Volume at the maximum sensor level – the largest measurable volume (L)
|-
| Parameters || H, L and d || V(0) || Volume at level 0
|-
| Calibration mode || Number of refuels used || Points || Number of points in the table
|-
| Offset || Fuel level and litres of refuel 1 || ||
|}

The calibration table lists each point with the columns '''#, Fuel level, V (L)''' and '''Zone''' (zero, offset, refuel 2, refuel 3, full). Tap '''Chart''' (top-right corner) to view the volume-versus-fuel-level graph – the curve should rise smoothly, with no sudden jumps.

=== Download CSV File (Both Modes) ===

Tap '''Download CSV''' and choose a save location on the phone; the app shows '''Success''' with the file path. Use the file to load the table into LIGO MAX, keep installation records, or import it via Manual Calibration.

{| class="wikitable"
|-
! Item !! Value
|-
| File name || yyyyMMdd_HHmmss_<points>points_<tank>_H<H>_L<L>.csv, e.g. 20261103_101530_50points_cylinder_H60.5_L57.5.csv
|-
| Columns || No, Volume (liter), Level
|-
| Limits || Maximum 200 points; each volume value up to 65,535 L
|}

=== Save to Sensor (Sensor Live Mode Only) ===

Tap '''Save to sensor''', select '''Yes''' in the "Would you like to save calibration points?" dialog and wait until "Calibration points saved successfully!" appears. For LIGO AIR, the app automatically enables the calibration table on the sensor after writing; no further setup is needed.

<gallery mode="packed" widths="250" heights="500">
File:AutoCalib-09-results.png|''Figure 9. Results page''
File:AutoCalib-10-chart.png|''Figure 10. Calibration chart''
File:AutoCalib-11-csv-saved.png|''Figure 11. CSV file saved''
File:AutoCalib-12-save-sensor.png|''Figure 12. Table saved to the sensor''
</gallery>

== Error Messages ==

<div style="text-align:center;">[[File:AutoCalib-08-error.png|frameless|300px]]<div style="font-style:italic; color:#555;">Figure 13. Example of an input error message</div></div>

{| class="wikitable"
|-
! Message !! Cause !! Solution
|-
| Tank height H is empty. / Sensor height is empty. || H or L has not been entered || Enter both values in Step 1
|-
| Sensor height (…) cannot exceed tank height (…) || L is greater than H || Re-measure H and L
|-
| 1st refuel (offset): fuel level end is empty. (or litres added) || The refuel row is incomplete || Fill in all three rows in Step 2
|-
| Fuel level offset must be within 1…4093. || Fuel level end of refuel 1 is 0 or too high || Check the reading after refuel 1
|-
| Refuel N: fuel level end = X must be greater than fuel level start = Y. || The level after refuel N is not higher than before || Check the reading of refuel N
|-
| Refuel N: fuel level end cannot exceed 4095. || The value exceeds the sensor's measuring range || Enter a value from 0 to 4095
|-
| Voffset must be greater than 0 / Refuel N: ΔV must be greater than 0. || Litres added is 0 or negative || Enter the correct litres added
|-
| Number of points must be within 2…<max>. || Custom number of points is out of range || Enter a value within the range in Step 3
|-
| Total fuel volumn (…) cannot exeed 65535. || Total litres too large || Re-check the litres entered
|-
| Cannot export – LIGO MAX accepts at most 200 calibration points. || The table has more than 200 points || Regenerate the table with at most 200 points
|}

== Related Documents ==
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:Software & Applications]]

Category:CalibTable Generator

2026-11-09T06:55:41Z

Admin: Auto-created category for CalibTable Generator

{{DEFAULTSORT:05 CalibTable Generator}}

[[Category:Software & Applications]]

CalibTable Generator

2026-11-09T06:55:41Z

Admin: Initial Release [release]

== Overview ==
This feature generates a complete fuel tank calibration table from just '''three refuels'''. The user only needs to select the tank shape, enter the tank height and the sensor height after cutting, and the fuel level and litres of each refuel; the app calculates all points of the table automatically, with no need to fill in small increments and manually record each point. Available from app version 2.2.4.

The table generator has two modes:

{| class="wikitable"
|-
! Mode !! Description !! Sensor connection !! Output
|-
| Standalone || Refuel data is already available, or preparing a table for LIGO AIR, LIGO MAX, LIGO PRO BLE || Not required || CSV file
|-
| Sensor Live || Calibrate directly on the vehicle while connected to a LIGO AIR or LIGO PRO BLE / PRO 2(S) sensor || Required || Written directly to the sensor or to a CSV file
|}

Supported tank shapes:

<gallery mode="packed" widths="200" heights="150">
File:AutoCalib-tank-parallelepiped.png|''Parallelepiped''
File:AutoCalib-tank-cylinder.png|''Cylinder''
File:AutoCalib-tank-dshape.png|''D-shape''
</gallery>

== Preparation ==

* The fuel tank is empty or fully drained.
* The sensor has been cut to the correct length and installed on the tank.
* A tool to accurately measure the litres added is available (a metered pump or a calibrated measuring container).
* The two tank dimensions are known:
** '''H – Tank height (cm):''' the internal height of the tank at the sensor mounting position, measured from the bottom.
** '''L – Sensor height (cm):''' the length of the sensor after cutting, measured from the lower edge of the aluminium tube to the underside of the sensor base.

The difference '''d = H − L''' is the bottom gap; fuel below the probe tip is not measured by the sensor.

'''Three-refuel plan:'''

# '''Refuel 1 (offset):''' starting from an empty tank, fill to about 5–10 % of the tank volume.
# '''Refuel 2:''' fill to about 40–60 %.
# '''Refuel 3:''' fill the tank completely (100 %).

'''Note:''' For each refuel, record only the litres added in that refuel; '''do not accumulate''' the litres from previous refuels.

<div style="text-align:center;">[[File:AutoCalib-dim-cylinder.png|frameless|400px]]<div style="font-style:italic; color:#555;">Figure 1. Tank height H, sensor height L and bottom gap d</div></div>

== Opening the Calibration Table Generator ==

=== Standalone Mode ===

# Open the app; on the '''Bluetooth Products''' page, select '''CALIBTABLE GENERATOR'''.
# The '''CalibTable Generator''' page opens; no sensor connection is required.

=== Sensor Live Mode ===

# Connect the LIGO AIR or LIGO PRO BLE sensor as usual.
# Go to the '''Settings''' tab > '''Calibration Table''' > '''Auto Calibration'''.

The page looks the same as in Standalone mode, with an additional '''Fuel level from sensor''' line showing the live reading from the sensor.

'''Note:''' The '''Manual Calibration''' item in the same menu is used to build a multi-point calibration table manually; this document covers Auto Calibration only.

<gallery mode="packed" widths="250" heights="500">
File:AutoCalib-01-products-generator.png|''Figure 2. CALIBTABLE GENERATOR on the Bluetooth Products page''
File:AutoCalib-02-settings-calibration-table.png|''Figure 3. Settings > Calibration Table''
File:AutoCalib-03-calibration-menu.png|''Figure 4. Calibration Table menu''
</gallery>

== Step 1 – Tank Type and Dimensions ==

# Select the tank shape: '''Parallelepiped''', '''Cylinder''' or '''D-shape'''.
# Enter '''Tank height (H)''' and '''Sensor height (L)''' in cm (decimals are accepted, e.g. 60.5).
# The app automatically calculates '''Bottom gap: d = H − L'''.

* L must not be greater than H.
* Tap the ⓘ icon next to each field to view a short explanation.

<gallery mode="packed" widths="250" heights="190">
File:AutoCalib-dim-parallelepiped.png|''Measuring H, L – rectangular box''
File:AutoCalib-dim-cylinder.png|''Measuring H, L – horizontal cylinder''
File:AutoCalib-dim-dshape.png|''Measuring H, L – D-shape''
</gallery>

== Step 2 – Refuel Calibration ==

The refuel table has three rows, one per refuel (row 1 starts from an empty tank). Target fill levels for each tank shape:

{| class="wikitable" style="text-align:center;"
|-
! Refuel 1 (offset): 5–10 % !! Refuel 2: 40–60 % !! Refuel 3: full (100 %)
|-
| [[File:AutoCalib-refuel-parallelepiped-1.png|frameless|180px]] || [[File:AutoCalib-refuel-parallelepiped-2.png|frameless|180px]] || [[File:AutoCalib-refuel-parallelepiped-3.png|frameless|180px]]
|}

Refuel table columns:

{| class="wikitable"
|-
! Column !! Description
|-
| Fuel level start || Taken automatically from the Fuel level end of the previous row; the first row is always 0.
|-
| Fuel level end || Fuel level reported by the sensor after the refuel, in sensor units (0 – 4095).
|-
| ΔV (L) || Litres added in this refuel (not cumulative).
|}

For each refuel:

=== In Standalone Mode (the user already has the refuel data) ===

Enter the existing data of the 3 refuels into the 3 corresponding rows '''1st refuel''', '''2nd refuel''', '''3rd refuel''' (including the Fuel level end and the corresponding litres of that refuel).

=== Reading the Fuel Level in Sensor Live Mode ===

# Fill to the target level for that row and wait for the fuel surface to settle.
# Read the fuel level from the sensor and enter it in '''Fuel level end'''.
# Enter the litres added in '''ΔV (L)'''.

* Tap ⓘ next to the row name to view the target fill level illustration for the selected tank shape.
* When you enter '''Fuel level end''', the tank illustration in Step 1 shows an estimated % mark, helping you check whether the value is reasonable.

The '''Fuel level from sensor''' line above the refuel table shows the live reading with its status:

* '''Stable''' (green): enter this value in the '''Fuel level end''' of the current refuel.
* '''Unstable''' (red): the fuel surface is still moving – wait longer before recording.

=== Rows Highlighted in Red ===

A refuel row turns red when '''Fuel level end''' ≤ '''Fuel level start''', '''Fuel level end''' > 4095, or '''ΔV''' ≤ 0. Correct the values in that row before generating the table.

== Step 3 – Export the Table ==

# Select '''Sensor type'''; the number of calibration points is set automatically according to the sensor.
# To use a different number of points: select '''Custom''' and enter it in '''Calibration points (custom)'''; the points are distributed evenly over the 0 – 4095 range.
# Tap '''Generate calibration table'''. If the data is invalid, a red message box appears above the button (see the Error Messages section).

{| class="wikitable"
|-
! Mode !! Sensor type options
|-
| Standalone || LIGO AIR (50 points), LIGO PRO BLE (30 points), LIGO MAX (100 points), Custom (2 – 200 points)
|-
| Sensor Live – LIGO PRO BLE || LIGO PRO BLE (30 points), Custom (2 – 30 points)
|-
| Sensor Live – LIGO AIR || LIGO AIR (50 points), Custom (2 – 50 points)
|}

<gallery mode="packed" widths="250" heights="500">
File:AutoCalib-04-step1.png|''Figure 5. Step 1 – tank type and dimensions''
File:AutoCalib-05-step2.png|''Figure 6. Step 2 – refuel calibration''
File:AutoCalib-06-step2-live.png|''Figure 7. Fuel level from sensor (Sensor Live)''
File:AutoCalib-07-step3.png|''Figure 8. Step 3 – export settings''
</gallery>

== Results ==

The '''Results''' page shows:

{| class="wikitable"
|-
! Item !! Description !! Item !! Description
|-
| Tank shape || Selected tank shape || V(4095) || Volume at the maximum sensor level – the largest measurable volume (L)
|-
| Parameters || H, L and d || V(0) || Volume at level 0
|-
| Calibration mode || Number of refuels used || Points || Number of points in the table
|-
| Offset || Fuel level and litres of refuel 1 || ||
|}

The calibration table lists each point with the columns '''#, Fuel level, V (L)''' and '''Zone''' (zero, offset, refuel 2, refuel 3, full). Tap '''Chart''' (top-right corner) to view the volume-versus-fuel-level graph – the curve should rise smoothly, with no sudden jumps.

=== Download CSV File (Both Modes) ===

Tap '''Download CSV''' and choose a save location on the phone; the app shows '''Success''' with the file path. Use the file to load the table into LIGO MAX, keep installation records, or import it via Manual Calibration.

{| class="wikitable"
|-
! Item !! Value
|-
| File name || yyyyMMdd_HHmmss_<points>points_<tank>_H<H>_L<L>.csv, e.g. 20261103_101530_50points_cylinder_H60.5_L57.5.csv
|-
| Columns || No, Volume (liter), Level
|-
| Limits || Maximum 200 points; each volume value up to 65,535 L
|}

=== Save to Sensor (Sensor Live Mode Only) ===

Tap '''Save to sensor''', select '''Yes''' in the "Would you like to save calibration points?" dialog and wait until "Calibration points saved successfully!" appears. For LIGO AIR, the app automatically enables the calibration table on the sensor after writing; no further setup is needed.

<gallery mode="packed" widths="250" heights="500">
File:AutoCalib-09-results.png|''Figure 9. Results page''
File:AutoCalib-10-chart.png|''Figure 10. Calibration chart''
File:AutoCalib-11-csv-saved.png|''Figure 11. CSV file saved''
File:AutoCalib-12-save-sensor.png|''Figure 12. Table saved to the sensor''
</gallery>

== Error Messages ==

<div style="text-align:center;">[[File:AutoCalib-08-error.png|frameless|300px]]<div style="font-style:italic; color:#555;">Figure 13. Example of an input error message</div></div>

{| class="wikitable"
|-
! Message !! Cause !! Solution
|-
| Tank height H is empty. / Sensor height is empty. || H or L has not been entered || Enter both values in Step 1
|-
| Sensor height (…) cannot exceed tank height (…) || L is greater than H || Re-measure H and L
|-
| 1st refuel (offset): fuel level end is empty. (or litres added) || The refuel row is incomplete || Fill in all three rows in Step 2
|-
| Fuel level offset must be within 1…4093. || Fuel level end of refuel 1 is 0 or too high || Check the reading after refuel 1
|-
| Refuel N: fuel level end = X must be greater than fuel level start = Y. || The level after refuel N is not higher than before || Check the reading of refuel N
|-
| Refuel N: fuel level end cannot exceed 4095. || The value exceeds the sensor's measuring range || Enter a value from 0 to 4095
|-
| Voffset must be greater than 0 / Refuel N: ΔV must be greater than 0. || Litres added is 0 or negative || Enter the correct litres added
|-
| Number of points must be within 2…<max>. || Custom number of points is out of range || Enter a value within the range in Step 3
|-
| Total fuel volumn (…) cannot exeed 65535. || Total litres too large || Re-check the litres entered
|-
| Cannot export – LIGO MAX accepts at most 200 calibration points. || The table has more than 200 points || Regenerate the table with at most 200 points
|}

== Support / Contact ==
<div class="dim">

''Customer support channels for this app.''

'''What to fill in:''' contact table
* Website, Email, Phone, Service hours

</div>
<div class="noprint">
== Related Documents ==
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:Software & Applications]]

LIGO BLE CONFIGURATOR

2026-11-04T07:49:03Z

Admin: edit content of autocalib mode

== Overview ==
The LIGO BLE Configurator is a cross-platform mobile application for configuring, monitoring, and managing LIGO Bluetooth Low Energy (BLE) fuel level sensors. It runs on Android and iOS and communicates with sensors over Bluetooth Low Energy. The application is developed by SOJI Electronics JSC using Microsoft .NET MAUI.

=== Supported Product Lines ===

From the home screen (Bluetooth Products page) you choose one of three product lines. The available pages and settings adapt to the product you select.

{| class="wikitable"
|-
! Product !! Type !! Description
|-
| LIGO AIR || Wireless sensor || Battery-powered wireless fuel level sensor using Bluetooth 5.2
|-
| LIGO PRO BLE / PRO 2(S) || Wired sensor || Wired fuel level sensor with Bluetooth 5.2 for wireless configuration
|-
| LIGO AIR ADAPTER || Transceiver || Transceiver device that connects multiple LIGO AIR wireless sensors
|}

=== Key Capabilities ===

* Scan for and connect to nearby LIGO BLE sensors
* View real-time sensor data (fuel level, temperature, capacitance, battery, accelerometer)
* Calibrate the tank using Set Empty / Set Full points and a multi-point calibration table
* Configure sensor parameters (output format, transmission interval, address, baud rate, and more)
* Manage BLE / advanced settings (TX power, advertising interval, BLE mode, logging)
* Download stored data logs and export them as Excel (.xlsx) files
* View setting / event logs retrieved from the SOJI server
* Update sensor firmware
* Create installation and maintenance reports with photos
* Manage multiple wireless sensors through the LIGO AIR ADAPTER
* Protect sensor access with a password, including a password recovery mechanism

=== Navigation Structure ===

After a product is selected, the application uses a three-tab layout at the bottom of the screen:

{| class="wikitable"
|-
! Tab !! Purpose
|-
| Connection || Device scanning, connection, and the real-time device dashboard
|-
| Settings || Product-specific configuration pages (calibration, parameters, advanced settings, logs, reports)
|-
| Help || Online support contacts, application information, and user-guide resource links
|}

[[File:01-products-page.png|center|250px|thumb|Figure 1. Bluetooth Products (home) page]]

== System Requirements ==

=== Operating System ===

{| class="wikitable"
|-
! Platform !! Minimum version
|-
| Android || Android 8.0 Oreo (API level 26) or later
|-
| iOS || iOS 13.2 or later
|}

=== Hardware ===

* A mobile device with Bluetooth Low Energy (BLE) support. BLE hardware is required; the app shows a warning if the device does not support BLE.
* A camera is used for scanning QR codes and taking report photos (optional features).

=== Permissions ===

The application declares and requests the following permissions. On first use (when the Products page opens), the app requests Bluetooth, Location, and Camera permission.

{| class="wikitable"
|-
! Permission !! Why it is used
|-
| Bluetooth || Read data from and write configuration to LIGO BLE sensors
|-
| Location || Required by the operating system for BLE scanning; also used to record the sensor installation location
|-
| Camera || Scan a sensor serial-number QR code and take photos for reports
|-
| Photos / Storage || Attach photos to reports and save exported data files
|-
| Internet / Network || Upload logs and reports and retrieve server-side setting logs
|}

'''NOTICE: Android Location requirement'''

On Android, Location Services must be enabled for BLE scanning to work. This is an Android operating-system requirement, not a limitation of the application.

=== Network ===

An internet connection is required only for the server-connected features: uploading data logs and reports to the SOJI server, and viewing setting / event logs retrieved from the server. Scanning, connecting, calibration, parameter configuration, and firmware updates work over Bluetooth without an internet connection.

== Installation ==

=== Installing the Application ===

# Install LIGO BLE Configurator from the Apple App Store (iOS) or Google Play Store (Android), or from the distribution package provided by SOJI Electronics.
# Open the application after installation completes.

<gallery mode="packed" widths="250" heights="500">
File:Google-Play.png|LIGO BLE Configurator on Google Play
File:App-Store.png|LIGO BLE Configurator on App Store
</gallery>

=== Granting Permissions ===

When you open the application and reach the Products page, it checks for the permissions it needs and prompts you to grant any that are missing:

# Allow Bluetooth access. If Bluetooth permission is not granted, the app shows a message asking you to allow Bluetooth access and cannot scan for sensors.
# Allow Location access (used for BLE scanning and to record installation location).
# Allow Camera access (used for QR scanning and report photos).
# If Bluetooth is turned off on the device, enable it when prompted.

'''NOTICE: Bluetooth not available'''

If the device hardware does not support Bluetooth Low Energy, the app displays the warning "Your phone does not support Bluetooth Low Energy" and scanning is unavailable.

''[ Screenshot to be added: Operating-system permission dialog (Bluetooth / Location / Camera) ]''

''Please capture this screen and place the image here.''

''Operating-system permission dialog (Bluetooth / Location / Camera)''

== Quick Start ==

This section walks through connecting to a sensor and reaching its dashboard for the first time.

=== Select a Product ===

# Open the app to display the Bluetooth Products page.
# Tap the product line you are working with: LIGO AIR, LIGO PRO BLE / PRO 2(S), or LIGO AIR ADAPTER.
# The app opens the scan page for that product and begins searching for nearby BLE devices automatically.

=== Scan and Connect ===

The scan page lists discovered devices. Each row shows the device name, signal strength (RSSI), and a fuel-level reading taken from the advertisement data.

* Use the search bar to filter the list by name or serial number.
* Use the SOJI filter toggle to show only SOJI / LIGO devices.
* Use the QR scanner to find a specific sensor by scanning its QR code.

# Locate your target device in the list.
# Tap Connect on the device row to start the BLE connection.
# When the connection succeeds, the app opens the Device page (dashboard).

<gallery mode="packed" widths="250" heights="500">
File:02-scan-page-air.png|Figure 2. Scan page (LIGO AIR)
File:02-scan-page.png|Figure 3. Scan page (LIGO PRO)
</gallery>

=== Open Settings ===

Use the Settings tab to reach the configuration pages for the connected device. The menu contents depend on the product line.

<gallery mode="packed" widths="250" heights="500">
File:settings-menu.png|Figure 5. Settings menu (LIGO PRO)
File:settings-menu-air.png|Figure 6. Settings menu (LIGO AIR)
</gallery>

=== Password Prompt ===

LIGO sensors are password protected. The password is not requested at connection time; instead, it is requested the first time you open a password-protected settings page (for example Parameter Settings, Advanced Settings, or Set Empty / Set Full). Enter the password and tap OK to continue.

* The factory default password is 1234. Change it after the initial setup.
* If you forget the password, use Forgot Password on the prompt to obtain a recovery hash and contact SOJI support. See Section 9.

[[File:password-prompt.png|center|250px|thumb|Figure 4. Password prompt]]

== Features ==

This section summarises the main screens. Detailed configuration steps are in Section 6 (Configuration / Settings).

=== Device Dashboard ===

After connecting, the Device page shows a tank graphic with a fill-level indicator plus live readings. The fields shown depend on the product line.

==== LIGO PRO BLE ====

<gallery mode="packed" widths="250" heights="500">
File:03-device-page-pro.png|Figure 7. LIGO PRO dashboard (top)
File:03-device-page-pro-2.png|Figure 8. LIGO PRO dashboard (details)
File:03-device-page-pro-3.png|LIGO PRO dashboard (further details)
</gallery>

Fields displayed under the DEVICE section include:

{| class="wikitable"
|-
! Field !! Description
|-
| Data source || Source of the displayed data (advertisement or connected)
|-
| C_working_compensated || Temperature-compensated working capacitance value
|-
| C Min / C Max || Empty / full tank capacitance reference values
|-
| OSC frequency || Oscillator frequency reading
|-
| Fuel volume (Liter) || Calculated fuel volume based on calibration
|-
| Baudrate || Current serial communication baud rate
|-
| Filter time (s) || Signal filtering time in seconds
|-
| BLE mode || Current Bluetooth operating mode
|-
| Address || Sensor network address
|-
| Rssi || Received Signal Strength Indicator
|-
| Boot counts || Number of sensor power-on cycles
|-
| Operating time (hours) || Total sensor operating time
|-
| Sensor type || Hardware type identifier
|-
| Protocol || Communication protocol (when available)
|-
| Sensor message || Status message (color-coded: green = OK, red = error)
|-
| Device ID / Serial Number || Identifiers (tap to copy to clipboard)
|-
| Boot / Firmware / Hardware version, FW build date || Firmware and hardware identifiers
|}

==== LIGO AIR ====

<gallery mode="packed" widths="250" heights="500">
File:04-device-page-air.png|Figure 9. LIGO AIR dashboard (top)
File:04-device-page-air-2.png|Figure 10. LIGO AIR dashboard (details)
File:04-device-page-air-3.png|LIGO AIR dashboard (further details)
</gallery>

The LIGO AIR dashboard adds wireless-specific fields not present on the wired LIGO PRO:

{| class="wikitable"
|-
! Field !! Description
|-
| Raw data || Unprocessed sensor reading
|-
| C_working_compensated, C Min, C Max || Capacitance working and reference values
|-
| CNT || Counter / oscillator count value
|-
| Vbat || Battery voltage (e.g. X.XX V)
|-
| Axis X / Y / Z || Three-axis accelerometer readings
|-
| Time/Date || Sensor internal real-time clock value
|-
| Rssi, Boot counts, Operating time || Signal strength and usage statistics
|-
| Sensor message || Status message (color-coded)
|-
| Serial Number / MAC address || Identifiers (tap to copy)
|-
| Boot / Firmware / Hardware version, FW build date || Firmware and hardware identifiers
|}

=== Calibration ===

Two calibration methods map raw capacitance readings to fuel volume: Set Empty / Set Full (two reference points) and a multi-point calibration table for non-linear tanks. See [https://wiki.sojielectronics.com/index.php?title=LIGO_BLE_CONFIGURATOR&stable=0#Calibration_2 Calibration].

=== Logs ===

* '''Data Logs''' – download historical measurements stored in the sensor and export them as Excel files.
* '''Setting Logs / Event Logs''' – view configuration-change and event history retrieved from the SOJI server.

=== Firmware Update ===

Update the sensor firmware over the air. LIGO PRO uses the Nordic DFU process (.zip files); LIGO AIR and LIGO AIR ADAPTER use the Silicon Labs OTA process (.gbl files). See [https://wiki.sojielectronics.com/index.php?title=LIGO_BLE_CONFIGURATOR&stable=0#Firmware_Update_2 Firmware Update].

=== Reports ===

Create installation and maintenance reports with up to 3 photos each, and view previously created reports. See Section 6.5.

=== Multi-Sensor Management (LIGO AIR ADAPTER) ===

The LIGO AIR ADAPTER aggregates data from multiple LIGO AIR sensors. From the adapter connection page you can add sensors, remove sensors, and refresh their status. See Section 6.

[[File:11-adapter-scan.png|center|250px|thumb|Figure 11. LIGO AIR ADAPTER - connected sensor list]]

== Auto Calibration Table ==

The Auto Calibration feature (CalibTable Generator) builds a complete fuel tank calibration table from only '''three refuels'''. Instead of adding fuel in small steps and recording dozens of points by hand, you enter the tank shape, two dimensions, and the fuel level and litres of each refuel. The application then calculates every point of the table. Available from application version 2.2.4.

=== Overview ===

The generator can be used in two modes:

{| class="wikitable"
|-
! Mode !! When to use !! Sensor connection !! Output
|-
| Standalone || You already have refuel measurements, or you are preparing a table for LIGO AIR, LIGO MAX, LIGO PRO BLE || Not required || CSV file
|-
| Sensor Live || You are calibrating on the vehicle while connected to a LIGO AIR or LIGO PRO BLE / PRO 2(S) sensor || Required || Write directly to the sensor, or CSV file
|}

Supported tank shapes:

<gallery mode="packed" widths="200" heights="150">
File:AutoCalib-tank-parallelepiped.png|Parallelepiped (rectangular box)
File:AutoCalib-tank-cylinder.png|Cylinder (horizontal)
File:AutoCalib-tank-dshape.png|D-shape
</gallery>

=== Before You Start ===

* The fuel tank is '''empty''', or drained to the lowest possible level.
* The sensor probe has been cut to length and installed on the tank.
* You have a way to measure the '''litres added''' accurately (a metered pump or a calibrated container).
* You know the two tank dimensions:
** '''H – Tank height''' (cm): the total inside height of the tank, measured from the bottom.
** '''L – Sensor height''' (cm): the probe length after cutting, from the lower edge of the mounting base to the probe tip.
* The difference '''d = H − L''' is the bottom gap. Fuel below the probe tip cannot be measured by the sensor.

<div style="text-align:center;">
[[File:AutoCalib-dim-cylinder.png|frameless|400px]]
<div style="font-style:italic; color:#555;">Figure 23. Tank height H, sensor height L and bottom gap d</div>
</div>

Plan three refuels:

# '''1st refuel (offset):''' from an empty tank, fill to about '''5–10 %''' of the tank volume.
# '''2nd refuel:''' fill to about '''40–60 %'''.
# '''3rd refuel:''' fill to a '''full tank (100 %)'''.

'''NOTICE: Litres per refuel'''

For each refuel, record only the litres added '''in that refuel'''. Do not add up the litres from previous refuels.

=== Opening the Generator ===

==== Standalone Mode ====

# Open the application to display the Bluetooth Products page.
# Tap '''CALIBTABLE GENERATOR'''.
# The CalibTable Generator page opens. No sensor connection is needed.

<div style="text-align:center;">
[[File:AutoCalib-01-products-generator.png|frameless|300px]]
<div style="font-style:italic; color:#555;">Figure 24. CALIBTABLE GENERATOR on the Bluetooth Products page</div>
</div>

==== Sensor Live Mode ====

# Connect to a '''LIGO AIR''' or '''LIGO PRO BLE''' sensor as usual.
# Open the '''Settings''' tab and tap '''Calibration Table'''.
# Tap '''Auto Calibration'''.

<gallery mode="packed" widths="250" heights="500">
File:AutoCalib-02-settings-calibration-table.png|Figure 25. Settings > Calibration Table
File:AutoCalib-03-calibration-menu.png|Figure 26. Calibration Table menu
</gallery>

'''NOTICE: Manual Calibration'''

The '''Manual Calibration''' item in the same menu opens the multi-point calibration table described in [[#Multi-Point Calibration Table|Multi-Point Calibration Table]]. This section covers '''Auto Calibration''' only.

The page is the same as in Standalone mode, with one extra line, '''Fuel level from sensor''', which shows the live reading from the connected sensor (see [[#Reading the Fuel Level in Sensor Live Mode|Reading the Fuel Level in Sensor Live Mode]]).

=== Step 1 – Tank Type and Dimensions ===

# Tap the tank shape: '''Parallelepiped''', '''Cylinder''' or '''D-shape'''.
# Enter '''Tank height (H)''' in cm.
# Enter '''Sensor height (L)''' in cm.
# The application calculates '''Bottom gap: d = H − L''' automatically.

<div style="text-align:center;">
[[File:AutoCalib-04-step1.png|frameless|300px]]
<div style="font-style:italic; color:#555;">Figure 27. Step 1 – tank type and dimensions</div>
</div>

How to measure H and L for each tank shape:

<gallery mode="packed" widths="250" heights="190">
File:AutoCalib-dim-parallelepiped.png|Parallelepiped
File:AutoCalib-dim-cylinder.png|Cylinder
File:AutoCalib-dim-dshape.png|D-shape
</gallery>

* L must not be greater than H.
* Decimal values are accepted, for example 60.5.
* Tap the ⓘ icon next to a field to show a short explanation.

=== Step 2 – Refuel Calibration ===

The refuel table has three rows, one per refuel:

{| class="wikitable"
|-
! Row !! Fill target !! Note
|-
| 1st refuel (offset) || From empty to 5–10 % || Start with an empty tank
|-
| 2nd refuel || To 40–60 % ||
|-
| 3rd refuel || To full tank (100 %) ||
|}

Fill targets for each tank shape:

{| class="wikitable" style="text-align:center;"
|-
! Tank shape !! 1st refuel: 5–10 % !! 2nd refuel: 40–60 % !! 3rd refuel: full
|-
! Parallelepiped
| [[File:AutoCalib-refuel-parallelepiped-1.png|frameless|180px]] || [[File:AutoCalib-refuel-parallelepiped-2.png|frameless|180px]] || [[File:AutoCalib-refuel-parallelepiped-3.png|frameless|180px]]
|-
! Cylinder
| [[File:AutoCalib-refuel-cylinder-1.png|frameless|180px]] || [[File:AutoCalib-refuel-cylinder-2.png|frameless|180px]] || [[File:AutoCalib-refuel-cylinder-3.png|frameless|180px]]
|-
! D-shape
| [[File:AutoCalib-refuel-dshape-1.png|frameless|180px]] || [[File:AutoCalib-refuel-dshape-2.png|frameless|180px]] || [[File:AutoCalib-refuel-dshape-3.png|frameless|180px]]
|}

Table columns:

{| class="wikitable"
|-
! Column !! Description
|-
| Fuel level start || Filled in automatically from the previous row's Fuel level end. The first row always starts at 0.
|-
| Fuel level end || The fuel level reported by the sensor after this refuel, in sensor units (0 – 4095)
|-
| ΔV (L) || The litres added in this refuel only
|}

For each refuel:

# Fill the tank to the target level for that row.
# Wait for the fuel surface to settle.
# Read the fuel level from the sensor and enter it in '''Fuel level end'''.
# Enter the litres added in '''ΔV (L)'''.

<div style="text-align:center;">
[[File:AutoCalib-05-step2.png|frameless|300px]]
<div style="font-style:italic; color:#555;">Figure 28. Step 2 – refuel calibration</div>
</div>

* Tap the ⓘ icon next to a row name to show the fill-target picture for the selected tank shape.
* While you type a Fuel level end value, the tank picture in Step 1 shows a line with the estimated fill percentage. Use it to check that the value is plausible.

==== Reading the Fuel Level in Sensor Live Mode ====

In Sensor Live mode, the line '''Fuel level from sensor''' above the refuel table shows the live sensor reading and a status badge:

{| class="wikitable"
|-
! Badge !! Meaning
|-
| Stable (green) || The last three readings differ by no more than 1 unit. The value can be recorded.
|-
| Unstable (red) || The fuel surface is still moving. Wait before recording.
|}

When the badge shows '''Stable''', type the displayed value into '''Fuel level end''' of the current refuel.

<div style="text-align:center;">
[[File:AutoCalib-06-step2-live.png|frameless|300px]]
<div style="font-style:italic; color:#555;">Figure 29. Fuel level from sensor in Sensor Live mode</div>
</div>

==== Rows Highlighted in Red ====

A refuel row turns red when:

* Fuel level end is not greater than Fuel level start.
* Fuel level end is greater than 4095.
* ΔV is 0 or negative.

Correct the values in that row before generating the table.

=== Step 3 – Output ===

# Select the '''Sensor type'''. The number of calibration points is set automatically for that sensor.
# To use a different number of points, select '''Custom''' and enter the value in '''Calibration points (custom)'''. The points are spread evenly over fuel level 0 – 4095.
# Tap '''Generate calibration table'''.

{| class="wikitable"
|-
! Mode !! Sensor type options
|-
| Standalone || LIGO AIR (50 points), LIGO PRO BLE (30 points), LIGO MAX (100 points), Custom (2 – 200 points)
|-
| Sensor Live – LIGO PRO BLE || LIGO PRO BLE (30 points), Custom (2 – 30 points)
|-
| Sensor Live – LIGO AIR || LIGO AIR (50 points), Custom (2 – 50 points)
|}

<div style="text-align:center;">
[[File:AutoCalib-07-step3.png|frameless|300px]]
<div style="font-style:italic; color:#555;">Figure 30. Step 3 – output settings</div>
</div>

If any input is invalid, a red message box appears above the button. See [[#Auto Calibration Error Messages|Auto Calibration Error Messages]].

=== Results ===

The Results page shows:

{| class="wikitable"
|-
! Item !! Description
|-
| Tank shape || Selected tank shape
|-
| Parameters || H, L and d
|-
| Calibration mode || Number of refuels used
|-
| Offset || Fuel level and litres of the 1st refuel
|-
| V(4095) || Volume at the maximum sensor level, i.e. the largest volume the sensor can measure (L)
|-
| V(0) || Volume at level 0
|-
| Points || Number of points in the table
|}

The calibration table lists each point with the columns '''#''', '''Fuel level''', '''V (L)''' (rounded to whole litres) and '''Zone''' (zero, offset, refuel 2, refuel 3, full).

Tap '''Chart''' at the top right to plot volume against fuel level. The curve should rise smoothly without sudden steps.

<gallery mode="packed" widths="250" heights="500">
File:AutoCalib-09-results.png|Figure 31. Results page
File:AutoCalib-10-chart.png|Figure 32. Calibration chart
</gallery>

==== Download CSV ====

Available in both modes.

# Tap '''Download CSV'''.
# Choose where to save the file on the phone.
# The application shows '''Success''' with the saved file path.

<div style="text-align:center;">
[[File:AutoCalib-11-csv-saved.png|frameless|300px]]
<div style="font-style:italic; color:#555;">Figure 33. CSV file saved</div>
</div>

{| class="wikitable"
|-
! Item !! Value
|-
| File name || <code>yyyyMMdd_HHmmss_<points>points_<tank>_H<H>_L<L>.csv</code>, for example <code>20261103_101530_50points_cylinder_H60.5_L57.5.csv</code>
|-
| Columns || No, Volume (liter), Level
|-
| Limits || At most 200 points; each volume at most 65 535 L
|}

Use the CSV file to load the calibration table into LIGO MAX, to keep with the installation records, or to import through Manual Calibration.

==== Save to Sensor ====

Available in Sensor Live mode only.

# Tap '''Save to sensor'''.
# Tap '''Yes''' on "Would you like to save calibration points?".
# Wait while the application shows ''Saving''. The message "Calibration points saved successfully!" confirms the write.

For '''LIGO AIR''', the application also enables the calibration table on the sensor after writing it. No further setting is needed.

<div style="text-align:center;">
[[File:AutoCalib-12-save-sensor.png|frameless|300px]]
<div style="font-style:italic; color:#555;">Figure 34. Calibration table saved to the sensor</div>
</div>

=== Auto Calibration Error Messages ===

<div style="text-align:center;">
[[File:AutoCalib-08-error.png|frameless|300px]]
<div style="font-style:italic; color:#555;">Figure 35. Example of an input error message</div>
</div>

{| class="wikitable"
|-
! Message !! Cause !! Solution
|-
| Tank height H is empty. / Sensor height is empty. || H or L was not entered || Enter both values in Step 1
|-
| Sensor height (…) cannot exceed tank height (…) || L is greater than H || Measure H and L again
|-
| 1st refuel (offset): fuel level end is empty. (or litres added) || A refuel row is incomplete || Fill in all three rows in Step 2
|-
| Fuel level offset must be within 1…4093. || The 1st refuel Fuel level end is 0 or too high || Check the reading after the 1st refuel
|-
| Refuel N: fuel level end = X must be greater than fuel level start = Y. || The level after refuel N is not higher than before || Check the reading for refuel N
|-
| Refuel N: fuel level end cannot exceed 4095. || Value above the sensor range || Enter a value from 0 to 4095
|-
| Voffset must be greater than 0 / Refuel N: ΔV must be greater than 0. || Litres added is 0 or negative || Enter the litres actually added
|-
| Number of points must be within 2…<max>. || Custom point count out of range || Enter a value within the range in [[#Step 3 – Output|Step 3]]
|-
| Total fuel volumn (…) cannot exeed 65535. || Total litres too large || Check the litres entered
|-
| Cannot export – LIGO MAX accepts at most 200 calibration points. || Table has more than 200 points || Generate the table again with 200 points or fewer
|}

== Configuration / Settings ==

All configuration pages provide Load from Sensor (read current values from the device) and Save to Sensor (write changes to the device).

=== Calibration ===

==== Set Empty / Set Full ====

Establishes the empty-tank and full-tank reference points for linear fuel-level calculation. Applicable to LIGO PRO BLE and LIGO AIR.

[[File:06-set-empty-full.png|center|250px|thumb|Figure 12. Set Empty / Set Full page]]

Set the empty point:

# Lower the fuel level to minimum (drain the tank).
# Open Settings > Set Empty/Full.
# Watch the live C_working_compensated value and wait for it to stabilise.
# Tap Set Empty to record the C Min value.

Set the full point:

# Fill the tank to maximum.
# Wait for the C_working_compensated value to stabilise.
# Tap Set Full to record the C Max value.

'''CAUTION: Stable readings required'''

Make sure the fuel level is completely stable before tapping Set Empty or Set Full. Unstable readings produce inaccurate calibration.

==== Multi-Point Calibration Table ====

For non-linear tanks, a multi-point table improves accuracy. Applicable to LIGO PRO BLE and LIGO AIR (on LIGO AIR it is reached via the calibration page).

[[File:05-calibration-page.png|center|250px|thumb|Figure 13. Multi-point calibration table]]

# Tap Load from Sensor to read the current table from the device.
# Tap + to add a calibration point.
# Enter the known Volume (liter); the Level value comes from the current reading.
# Repeat for several fuel levels (for example empty, 1/4, 1/2, 3/4, full).
# Tap - next to a row to remove a point.
# Tap Save to Sensor to write the table to the device.

Use View Chart to plot the calibration curve and confirm it rises smoothly. On LIGO AIR, Advanced Settings > Recalculate in liters recalculates stored calibration data into liter units.

=== Parameter Settings ===

==== LIGO PRO BLE ====

[[File:07-parameter-settings-pro.png|center|250px|thumb|Figure 14. LIGO PRO parameter settings]]

{| class="wikitable"
|-
! Parameter !! Options / Range !! Description
|-
| Automatic transmission || OFF, HEX, ASCII, ASCII-EXT, ASCII-DV || Serial output format
|-
| Prefix / Postfix || Free text || Text added before / after messages
|-
| Parameter selection || Units (0-4095), Volume (liter), Level (mm), Volume (%) || Output parameter type
|-
| Address || 0 - 254 || Sensor network address
|-
| Message interval (s) || 0 - 255 || Time between automatic transmissions
|-
| Actual length (mm) || 0 or greater || Physical sensor tube length
|-
| Level min / Level max || 0.0-8.0 V / 2.0-9.0 V || Analog output voltage range (analog mode)
|-
| Baudrate || 2400, 4800, 9600, 14400, 19200, 38400, 115200 || Serial communication speed
|-
| Filter time (s) || 0 - 255 || Signal smoothing time
|-
| Volume unit (Liter) || 0.1 (liter), 1 (liter) || Fuel volume resolution
|-
| C_Min / C_Max (Manual) || 0 - 100000 || Capacitance reference values
|}

'''CAUTION: Manual C_Min / C_Max'''

Editing C_Min and C_Max manually is not recommended and can cause inaccurate readings. Use the Set Empty / Set Full procedure instead.

==== LIGO AIR ====

[[File:08-parameter-settings-air.png|center|250px|thumb|Figure 15. LIGO AIR parameter settings]]

{| class="wikitable"
|-
! Parameter !! Options / Range !! Description
|-
| Advertising protocol || SOJI, ESCORT, MIELTA, TECHNOTON, EUROSEN_V1, EUROSEN_V2 || BLE advertising data format
|-
| Maximum level || 1023, 4095 || Maximum digital output value
|-
| Filter time || 1 - 15 || Signal smoothing factor
|-
| C_Min / C_Max (Manual) || 0 - 300000 || Capacitance reference values
|}

==== LIGO AIR ADAPTER ====

{| class="wikitable"
|-
! Parameter !! Options / Range !! Description
|-
| Message interval (s) || 1 - 60 || Interval between data transmissions
|-
| Protocol || SOJI, LLS || Output communication protocol
|-
| Baudrate || 2400, 4800, 9600, 14400, 19200, 38400, 115200 || Serial communication speed
|}

=== Advanced Settings ===

==== LIGO PRO BLE (BLE Settings) ====

[[File:09-ble-settings.png|center|250px|thumb|Figure 16. LIGO PRO advanced / BLE settings]]

{| class="wikitable"
|-
! Parameter !! Options !! Description
|-
| BLE transmission level || 0 - 10 || Bluetooth transmission power level
|-
| BLE mode || Off, On, Auto Off, Auto Readonly || Bluetooth operating mode
|}

{| class="wikitable"
|-
! BLE mode !! Behavior
|-
| On || Bluetooth is always on and configurable
|-
| Off || Bluetooth is turned off; reconfiguration requires a wired computer connection (not recommended)
|-
| Auto Off || Bluetooth turns off after 24 h of continuous power; restarts after a power cycle
|-
| Auto Readonly || Bluetooth becomes read-only after 24 h; writable again after a power cycle
|}

'''WARNING: BLE mode Off'''

Setting BLE mode to Off disables Bluetooth on the sensor until it is reconfigured through a wired computer connection. Do not select it unless you have alternative configuration access.

The Change your password section lets you set a new password: enter the current password, the new password, confirm it, and tap Change password.

==== LIGO AIR ====

[[File:10-air-advance-settings.png|center|250px|thumb|Figure 17. LIGO AIR advanced settings]]

{| class="wikitable"
|-
! Parameter !! Options / Range !! Description
|-
| Advertising interval (s) || 5, 10 || BLE advertisement interval (restricted to 10 when TX power >= 10 dBm)
|-
| Measuring interval (s) || 5, 6, 7, 8, 9, 10 || Time between measurement cycles
|-
| TX power (dBm) || 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19.5 || BLE transmission power
|-
| Log data mode || Disable, Enable || Internal data-logging on/off
|-
| Log data interval || 30, 60, 120, 180, 240 (s) || Interval between logged data points
|}

Utility functions on this page:

{| class="wikitable"
|-
! Function !! Description
|-
| Sync time/date || Synchronise the sensor's internal clock (RTC) with the phone
|-
| Recalculate in liters || Convert stored calibration data into liter units
|-
| Factory reset || Reset the sensor to factory defaults
|-
| Change password || Set a new sensor password
|}

'''WARNING: Factory reset'''

Factory reset erases all calibration data, parameter settings, and custom configuration. This action cannot be undone. Document your settings first.

==== LIGO AIR ADAPTER ====

{| class="wikitable"
|-
! Parameter !! Options / Range !! Description
|-
| Log data mode || Disable, Enable || Internal data-logging on/off
|-
| Log data interval || 30, 60, 120, 180, 240 (s) || Interval between logged data points
|}

The adapter advanced page also provides Sync time/date, Factory reset, and Change password.

=== Firmware Update ===

[[File:14-dfu-page.png|center|300px|thumb|Figure 18. Firmware upgrade page (three-step process)]]

Firmware update uses a three-step workflow: select the firmware File, select the target Device, then start the Upload and monitor progress.

{| class="wikitable"
|-
! Product !! Method !! File type
|-
| LIGO PRO BLE || Nordic DFU || .zip
|-
| LIGO AIR / LIGO AIR ADAPTER || Silicon Labs OTA || .gbl
|}

During the LIGO PRO upload the app reports the stages Enable Bootloader, DFU Initialization, Firmware Upload (with upload speed in kB/s and percentage), and DFU Complete. After updating, reconnect and check the Firmware version and FW build date on the dashboard.

'''WARNING: Do not interrupt a firmware update'''

Do not interrupt the sensor power supply and keep the phone close to the sensor while the firmware is loading. Interrupting an update may make the sensor inoperable.

''[ Screenshot to be added: Silicon Labs OTA firmware page (LIGO AIR / ADAPTER) ]''

''Please capture this screen and place the image here.''

''Silicon Labs OTA firmware page (LIGO AIR / ADAPTER)''

=== Installation & Maintenance Reports ===

[[File:15-installation-report.png|center|250px|thumb|Figure 19. Installation report menu]]

From Settings > Installation Report you can create an installation report, create a maintenance report, or view existing reports.

# Choose Create installation report or Create maintenance report.
# Fill in the report fields (technician, date, vehicle/plate, device details). Device serial and firmware are filled in automatically when connected.
# Attach up to 3 photos by taking a new photo or selecting one from the gallery.
# Tap Create Report to generate the report.

Use View report to search and open a saved report; the report detail page shows the entered values and attached photos.

''[ Screenshot to be added: Create report form and report detail page ]''

''Please capture this screen and place the image here.''

''Create report form and report detail page''

=== Data Logs ===

<gallery mode="packed" widths="350" heights="500">
File:12-data-logs.png|Figure 20. Data logs with downloaded data
File:12-data-logs-view.png|Data logs — downloaded data view
</gallery>

Download historical data stored in the device and review it in a table. Applicable to LIGO PRO BLE, LIGO AIR, and LIGO AIR ADAPTER. Select a date range, then download:

{| class="wikitable"
|-
! Range !! Description
|-
| Today / Yesterday || Current or previous day
|-
| Week / Month || Past 7 days / past 30 days
|-
| Custom || User-defined start and end date/time
|}

# Open Settings > Data Logs (for LIGO AIR, via Setting & Data Logs).
# Make sure the sensor is connected (Download is disabled when disconnected).
# Select the date range and tap Download.
# Choose where to save: Device and server or Server only.
# Save the exported .xlsx (Excel) file to your device.

The downloaded data grid includes columns: Time, C (capacitance), Temp, Volt, Pulse, AccX/AccY/AccZ, Incli (inclination), and Level.

=== Setting / Event Logs ===

[[File:13-event-logs.png|center|250px|thumb|Figure 21. Setting / event logs]]

View configuration-change and event history. For LIGO PRO this is Setting Logs; for LIGO AIR it is reached via Setting & Data Logs > View Setting Logs.

# Open the setting-logs page; the search box is pre-filled with the connected device's ID. You can also enter an IMEI or serial number.
# Entries appear as expandable cards. Tap an entry to view details such as the changed property, the new value, and the GPS location at the time of the event.

'''NOTICE: Internet required'''

Server-side setting logs require an internet connection. If the network is unavailable the app shows "Network Error!".

== Compatibility ==

=== Devices and Operating Systems ===

{| class="wikitable"
|-
! Item !! Supported
|-
| Mobile OS || Android 8.0 (API 26) and later; iOS 13.2 and later
|-
| Connectivity || Bluetooth Low Energy
|}

=== Supported Sensors ===

* LIGO AIR (wireless)
* LIGO PRO BLE and LIGO PRO 2(S) (wired)
* LIGO AIR ADAPTER (transceiver for multiple LIGO AIR sensors)

=== Advertising Protocols (LIGO AIR) ===

The LIGO AIR advertising data can be formatted using one of the following protocols, selectable in Parameter Settings:

* SOJI
* ESCORT
* MIELTA
* TECHNOTON
* EUROSEN_V1
* EUROSEN_V2

The LIGO AIR ADAPTER output supports the SOJI and LLS protocols.

=== Firmware Update Compatibility ===

{| class="wikitable"
|-
! Product !! Update method !! File type
|-
| LIGO PRO BLE || Nordic DFU || .zip
|-
| LIGO AIR / LIGO AIR ADAPTER || Silicon Labs OTA || .gbl
|}

=== Language ===

The application interface is in English only. A language indicator labelled "EN" appears in the top bar of the Products page; in this version it is an indicator and the application does not provide additional interface languages.

== Troubleshooting ==

=== Connection ===

{| class="wikitable"
|-
! Problem !! Solution
|-
| Device not in the scan list || Enable Bluetooth; enable Location Services (Android); move closer to the sensor; check whether the SOJI filter is hiding it; the sensor BLE mode may be Off
|-
| Connection drops during use || Stay close to the sensor; reduce nearby BLE interference
|-
| "Please connect to Sensor!" || You opened a settings page without an active connection - connect first from the Connection tab
|-
| "Adapter is disconnected to your phone!" || The adapter connection was lost - return to the scan page and reconnect
|-
| "Your phone does not support Bluetooth Low Energy" || The device hardware lacks BLE; use a BLE-capable phone
|}

=== Password ===

{| class="wikitable"
|-
! Problem !! Solution
|-
| Forgot the password || Tap Forgot Password on the prompt, note the recovery hash, and contact SOJI support (the hash is time-limited)
|-
| Password is rejected || Re-enter carefully; the factory default is 1234
|-
| "Please enter the sensor's password!" || Enter the sensor password when prompted before a write operation
|}

=== Calibration ===

{| class="wikitable"
|-
! Problem !! Solution
|-
| Reading will not stabilise || Park on level ground with the engine off and let the fuel settle before Set Empty / Set Full
|-
| Value highlighted in red || The value is outside the accepted range shown for that field
|-
| Calibration looks wrong || Use Set Empty / Set Full instead of editing C_Min / C_Max manually
|}

=== Firmware Update ===

{| class="wikitable"
|-
! Problem !! Solution
|-
| Upload button disabled || Connect to the sensor first and ensure the BLE link is active
|-
| Connection lost during update || Keep the phone close, power-cycle the sensor, and retry from step 1
|-
| Update fails repeatedly || Re-download the firmware file and confirm it is the correct type for the product
|}

=== Logs / Network ===

{| class="wikitable"
|-
! Problem !! Solution
|-
| "Network Error!" || Check the internet connection and retry (server logs require internet)
|-
| No data for the selected range || Widen the date range or confirm data logging was enabled on the sensor
|}

== Security & Privacy ==

=== Sensor Access Protection ===

* Sensor configuration is protected by a password. The factory default is 1234; change it after the initial setup.
* The password is requested when you open a password-protected settings page, not at connection time.
* The app stores sensor passwords in encrypted form on the device.

=== Password Recovery ===

If the password is lost, the Forgot Password option produces a recovery hash. The hash is time-limited and is used together with SOJI support to recover access. Record the new password securely after changing it.

=== Recommendations ===

* Change the default sensor password (1234) after the first connection.
* Keep a secure record of any new password and of the recovery hash when you change a password.
* Use BLE mode Off only when you have a wired computer connection available, because it disables Bluetooth access to the sensor.

== Support / Contact ==

Support contacts and application information are available on the Help tab.

=== Online Support ===

{| class="wikitable"
|-
! Channel !! Contact
|-
| Zalo || (+84) 934 601 358
|-
| WhatsApp || (+84) 934 601 358
|-
| Email || support@sojielectronics.com
|}

=== About / Company ===

{| class="wikitable"
|-
! Field !! Value
|-
| Developer || SOJI ELECTRONICS., JSC
|-
| Office || C50-LK13, Lot No.09, Le Trong Tan, Duong Noi, Ha Dong, Hanoi, Vietnam
|-
| Factory || Van Khe, Nghia Huong, Quoc Oai, Hanoi, Vietnam
|-
| Website || sojielectronics.com
|-
| Tel || (+84) 24 62 932 369
|}

<gallery mode="packed" widths="250" heights="500">
File:16-about-page.png|Figure 22. Help / About page
File:16-about-page-2.png|Help / About page (details)
</gallery>

=== User-Guide Resources (in the Help tab) ===

* User Guide for LIGO fuel level sensor
* Quick Install Guide for LIGO fuel level sensor
* Extending sensor tube instructions
* Installation video

Tap a resource to open it in the device's web browser.

<div class="noprint">
== Related Documents ==
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:Software & Applications]]

LIGO PRO BLE User Guide

2026-08-11T03:16:38Z

Admin: Initial Release [release]

== Safety Information ==
{{Notice
| title = Installer Qualifications and Safety
| body = *LIGO PRO BLE measures the accurate fuel level in fuel tanks, therefore the device installation process also needs to be extremely accurate.
*Installation technicians should be well-trained by specialists or experts in this field before installing the device.
*Implement protection against electric shocks and electrical fires, labour safety and hygiene.
*List of installing tools is provided in section APPENDIX A below.
*List of accessories is provided in section APPENDIX B below.
}}

== Product Overview ==
LIGO PRO BLE sensor is produced and developed by SOJI Electronics Join Stock Company. The device is designed to measure the level of liquid fuels and other non-conductive liquids in vehicle's tanks and stationary fuel storages, applicable in different fields. The measured values will be t transformed into output signal in the form of: Analog, Frequency, RS232, RS485… and transmitted to a connected external device

Under particular conditions, the device can reach a high accuracy up to 99.5%. At present, on the market there are several lines of sensor using different technologies to measure fuel level such as: magnetically operated switches (reed switches), ultrasound wave (ultrasonic sensor), capacitive sensing (capacitive sensor). Among these ones, capacitive sensing technology is considered to have highest accuracy and greatest lifespan.

== Package Contents ==

10 main items with specific quantities are described below:

{| class="wikitable" style="text-align:center;"
|-
! No. !! Description !! Qty (pcs)
|-
| 1 || style="text-align:left;" | LIGO Fuel Level Sensor. Standard lengths: 700, 1000, and 1500mm (for other customized lengths, please contact the manufacturer) || 01
|-
| 2 || style="text-align:left;" | Oil filter || 01
|-
| 3 || style="text-align:left;" | Gasoline-resistant rubber gasket || 01
|-
| 4 || style="text-align:left;" | Anti-vibration spring when moving || 01
|-
| 5 || style="text-align:left;" | 1A Fuse protection || 01
|-
| 6 || style="text-align:left;" | Self-drilling screw M4.8x32mm || 04
|-
| 7 || style="text-align:left;" | Rivet and screw M5x20mm || 04
|-
| 8 || style="text-align:left;" | Sealing wire || 02
|-
| 9 || style="text-align:left;" | 7m signal wire || 01
|-
| 10 || style="text-align:left;" | Quick installation manual || 01
|}

== Specifications ==

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! AF !! RS232 !! RS485
|-
| style="text-align:left;" | Standard length (L), mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Output signal || Analog (0-9V) || RS232 || RS485
|-
| style="text-align:left;" | Baud rate, bit/sec || colspan="3" | 2400, 4800, 9600, 19200, 38400, 57600, 115200.
|-
| style="text-align:left;" | Power supply (DC input voltage, V) || colspan="3" | 6-40V
|-
| style="text-align:left;" | Supply protection (Over-voltage 100 VDC for 2 minutes. Reverse polarity) || colspan="3" | Yes
|-
| style="text-align:left;" | Maximum power consumption, mA || colspan="3" | 20
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP69K
|-
| style="text-align:left;" | Operating temperature, °C || colspan="3" | -40...+85
|-
| style="text-align:left;" | Maximum allowed humidity level,% || colspan="3" | 100
|-
| style="text-align:left;" | Resolution, bit || colspan="3" | 12
|-
| style="text-align:left;" | Digital reading range corresponding to the minimum level measurement value || Analog (0...8V) || 0 || 0
|-
| style="text-align:left;" | Digital reading range corresponding to the maximum level measurement value || Analog (1...9V) || 4095 || 4095
|-
| style="text-align:left;" | Average sampling period, s || colspan="3" | 0...255
|-
| style="text-align:left;" | Message interval, s || Continuous || 1...255 || 1...255
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±1
|-
| style="text-align:left;" | Bluetooth specs || colspan="3" | Bluetooth 5.1, IEEE 802.15.4-2006, 2.4 GHz, -95 dBm sensitivity, +8 dBm TX Power
|-
| style="text-align:left;" | Average service life, years (expected) || 10 || 10 || 10
|}

== Installation ==

=== Selecting the location to install sensor ===

* Installation location should be as close as possible to the geometric center and placed at the deepest level of the tank.

<div style="text-align:center;">
[[File:LIGO-SP-fig1-location.png|frameless|894px]]
<div style="font-style:italic; color:#555;">Figure 1. Selecting the location to install sensor</div>
</div>

* When being installed, the sensor should not be in contact with reinforcement ribs inside the tank

<div style="text-align:center;">
[[File:LIGO-SP-fig2-two-sensors.png|frameless|730px]]
<div style="font-style:italic; color:#555;">Figure 2. Installation of two sensors in one tank allows for significant reduction</div>
</div>

=== Drilling the hole on fuel tank ===

* Drill out the central bore by bimetal core drill ø38 mm

<div style="text-align:center;">
[[File:LIGO-SP-fig3-drilling.png|frameless|580px]]
<div style="font-style:italic; color:#555;">Figure 3. Drilling the selected hole</div>
</div>

* Drill out four mounting holes according to the diagram:

<div style="text-align:center;">
[[File:LIGO-SP-fig4-mounting-holes.png|frameless|541px]]
<div style="font-style:italic; color:#555;">Figure 4. Drill out four mounting holes</div>
</div>

The mounting hole diameter depends on the tank material:

* ø 4 mm – for metal tank with wall thickness over 3 mm (cut M5 self screw M4.8)

<div style="text-align:center;">
[[File:LIGO-SP-fig5-hole-thick.png|frameless|402px]]
<div style="font-style:italic; color:#555;">Figure 5. Hole thick</div>
</div>

* ø 7 mm – for plastic and metal tank with wall thickness up to 3 mm (for rivets)

<div style="text-align:center;">
[[File:LIGO-SP-fig6-rivet-nut.png|frameless|372px]]
<div style="font-style:italic; color:#555;">Figure 6. Rivet nut M5</div>
</div>

<div style="text-align:center;">
[[File:LIGO-SP-fig7-install-rivet.png|frameless|535px]]
<div style="font-style:italic; color:#555;">Figure 7. Installing revit nut if tank's wall is thinner than 3mm</div>
</div>

=== Measuaring the tank depth and cutting sensor'measuring probe ===

<div style="text-align:center;">
[[File:LIGO-SP-fig8-measure-depth.png|frameless|615px]]
<div style="font-style:italic; color:#555;">Figure 8. Measuring the tank depth</div>
</div>

* Cut the sensor's measuring probe so that its length is 25 mm less than the depth of the tank. Ensure that shearing line is perpendicular to the sensor longitudinal axis

<div style="text-align:center;">
[[File:LIGO-SP-fig9-length.png|frameless|723px]]
<div style="font-style:italic; color:#555;">Figure 9. Origin length (L) and length after cutting (Lm)</div>
</div>

Notes: Minimum allowable length of the measuring probe is 150 mm.

=== Installing screen filter ===
Screen filter is mounted on the measuring probe of sensor to protect measuring probe electrodes from mud and water. Using the filter extends significantly faultless lifetime of the sensor.

Screen filter mounting order: firstly put on fixator, then put on bottom stop and fix it with two side screws. Put the screen filter over bottom stop and fasten it with a fixator locks.

<div style="text-align:center;">
[[File:LIGO-SP-fig15-screen-filter.png|frameless|747px]]
<div style="font-style:italic; color:#555;">Figure 10. Installing screen filter procedue</div>
</div>

=== Installing and connecting ===

* Applying oil-and-petrol resistant non-conductive sealant to ruber gasket

<div style="text-align:center;">
[[File:LIGO-SP-fig16-sealant.png|frameless|595px]]
<div style="font-style:italic; color:#555;">Figure 11. Applying the sealant to gasket</div>
</div>

* Put the sensor into the tank and fix: when fixing with rivets, use a rivet driver when bolting, put on a seal (per bolt), a spacer and a spring washer when fixing to plastic tanks with wall thickness over 3 mm, use vendor furnished self-tapping screws and a seal (per self-tapping screw)

<div style="text-align:center;">
[[File:LIGO-SP-fig17-install.png|frameless|663px]]
<div style="font-style:italic; color:#555;">Figure 12. Put sensor into the tank</div>
</div>

* Connect the sensors to an external device using 7m cable

The wire cable color:

'''RS232/RS485:'''

<div style="text-align:center;">
[[File:RS232-RS485.jpg|frameless|756x756px]]
<div style="font-style:italic; color:#555;">Figure 13. Wiring diagram of RS232 and RS485 output signals</div>
</div>

{| class="wikitable" style="text-align:center;"
! Wire Color !! Description
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div> || style="text-align:left;" | GND (Ground) (V-)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div> || style="text-align:left;" | TXD/B-
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div> || style="text-align:left;" | RXD/A+
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div> || style="text-align:left;" | 6 - 40 VDC
|}

'''AF:'''

<div style="text-align:center;">
[[File:LIGO-SP-fig19-wiring-AF.png|frameless|873px]]
<div style="font-style:italic; color:#555;">Figure 14. Wiring diagram of Analog and Frequency output signals.</div>
</div>

{| class="wikitable" style="text-align:center;"
! Wire Color !! Description
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div> || style="text-align:left;" | GND (Ground) (V-)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div> || style="text-align:left;" | Out (Analog/Frequency)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div> || style="text-align:left;" | 15-37 VDC or 7.5-75V for SP PRO series
|}

* Connect the fuse holder to LIGO sensor power cable (brown wire) in close vicinity to the vehicle power supply circuit
* Installing the fuse in the fuse holder

=== Sealing ===

* Install the bolt through a hole in the seal.

<div style="text-align:center;">
[[File:LIGO-SP-fig22-sealing.png|frameless|891px]]
<div style="font-style:italic; color:#555;">Figure 15. Sealing</div>
</div>

== Configuration ==

=== Connecting sensor to smartphone and setting ===

To configure the LIGO AIR fuel sensor, download the '''LIGO BLE Configurator''' app on '''Appstore (for IOS) or CH Play (for Android devices).'''

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

<gallery mode="packed" widths="250" heights="500">
File:LIGO-AIR-fig9-app-permissions-1.jpg|Figure 16. Grant all the permissions request by program
File:LIGO-AIR-fig10-app-permissions-2.jpg|Figure 17. Grant all the permissions request by program
</gallery>

Grant all the permissions request by program as above

==== Connecting sensor ====

Run the application and select the sensor you want to connect to, as shown in the pictures below:

<gallery mode="packed" widths="250" heights="500">
File:LIGO-Connect-PRO-BLE-1.jpg|Figure 18. Selecting sensor type
File:LIGO-Connect-PRO-BLE-2.jpg|Figure 19. Connecting sensor
</gallery>

==== Set Empty and Set Full ====

Step 1: Set Full

* Immerse the sensor in fuel until the fuel reaches the sensor flange
* Wait for C_working value to stablize and then press Set Full button

<div style="text-align:center;">
[[File:LIGO-AIR-fig13-set-full.jpg|frameless|304px]]
<div style="font-style:italic; color:#555;">Figure 20. Set Full</div>
</div>

Step 2: Set Empty

* Remove the sensor from the fuel and wait for 1-2 minutes allow the fuel drain from the measuring probe and then press Set Empty button.

<div style="text-align:center;">
[[File:LIGO-AIR-fig14-set-empty.jpg|frameless|304px]]
<div style="font-style:italic; color:#555;">Figure 21. Set Empty</div>
</div>

=== Calibration table ===

After installation, the sensor must be calibrated to ensure accurate volume measurement. Calibration table can be performed either on the platform (server) or locally on the sensor.

* '''Calibration table on the Platform (Server):''' The sensor sends raw level values (ranging from 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 calibration table on the platform.

=== Attention! ===

* The manufacturer is not responsible for product availability in case of non-compliance of requirements of this service manual, unauthorized service and repair; if device has damage or traces of opening of head's body, mechanical damage of the probe or the interface cable, as well as traces of corrosive acids, open flame, high voltage, lightning strikes or other natural factors.

== Certification / Compliance ==

Refer to [[LIGO PRO BLE Certification & Approvals]] for current certificate status.''

== Support / Contact ==

{| class="wikitable"
|-
! Channel !! Detail
|-
| Company || SOJI ELECTRONICS.,JSC
|-
| Address || C50-LK13, Lot No. 09, New Urban Area, Le Trong Tan street, Duong Noi Ward, Ha Dong District, Hanoi City, Vietnam
|-
| Tel/Fax || +84 24 62 932 369
|-
| Email || contact@sojielectronics.com
|-
| Website || [http://sojielectronics.com sojielectronics.com]
|}

<div class="noprint">
== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>
[[Category:LIGO PRO BLE ]]

File:Icon-test.svg

2026-07-21T10:51:48Z

Admin:

LIGO PRO BLE User Guide

2026-07-07T07:45:01Z

Admin: change image

LIGO PRO BLE Datasheet

2026-07-07T07:41:23Z

Admin: change image

== Product Overview ==

LIGO-PRO-BLE Fuel Level Sensor is produced and developed by SOJI Electronics JSC. The device is designed to measure the level of liquid fuel and other non-conductive liquids in vehicle tanks and stationary fuel storage, applicable in different fields. The measured values will be transmitted to an external device as an output signal such as Analog, Frequency, RS232, or RS485… to connect to an external device.

The purpose of creating a new product was to satisfy the increasing demand of the transport telematics market for improved reliability of the design, data, and ease of installation. Unlike its predecessors, the new sensor is integrated with Bluetooth Low Energy (BLE) making installation more convenient, easier, and faster.

In addition, the new heavy-duty metal structure helps increase protection against electrostatic, electromagnetic and conducted interference. LIGO-PRO-BLE is also designed with IP69K waterproof standards and better shock and vibration resistance.

== Key Features ==

* High accuracy up to 99,5%.
* Wide range input voltage: 6-40V.
* Galvanic isolation up to 2500V.
* Can be optionally cut off or prolonged up to 6000mm.
* Wide operating temperature range from -40°C to +85°C.
* Built-in Anti-mud oil filter and anti-vibration springs.
* IP69K waterproof standard.
* Integrated BLE technology for configuration via smartphone (available on App Store and Google Play).

== Applications ==
* Trucks, excavators, heavy construction machines…
* Marine vessels and electric generators.
* Off-highway machinery including high-temperature & vibration environments.
* Industrial oil storage tanks or stationary storage tanks.

== Product Variants / Ordering Information ==

=== Products and accessories ===

10 main items with specific quantities are described below:

{| class="wikitable" style="text-align:center;"
|-
! No. !! Description !! Qty (pcs)
|-
| 1 || style="text-align:left;" | LIGO Fuel Level Sensor. Standard lengths: 700, 1000, and 1500mm (for other customized lengths, please contact the manufacturer) || 01
|-
| 2 || style="text-align:left;" | Oil filter || 01
|-
| 3 || style="text-align:left;" | Gasoline-resistant rubber gasket || 01
|-
| 4 || style="text-align:left;" | Anti-vibration spring when moving || 01
|-
| 5 || style="text-align:left;" | 1A Fuse protection || 01
|-
| 6 || style="text-align:left;" | Self-drilling screw M4.8x32mm || 04
|-
| 7 || style="text-align:left;" | Rivet and screw M5x20mm || 04
|-
| 8 || style="text-align:left;" | Sealing wire || 02
|-
| 9 || style="text-align:left;" | 7m signal wire || 01
|-
| 10 || style="text-align:left;" | Quick installation manual || 01
|}

== Technical Specifications ==

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! AF !! RS232 !! RS485
|-
| style="text-align:left;" | Standard length (L), mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Output signal || Analog (0-9V) || RS232 || RS485
|-
| style="text-align:left;" | Baud rate, bit/sec || colspan="3" | 2400, 4800, 9600, 19200, 38400, 57600, 115200.
|-
| style="text-align:left;" | Power supply (DC input voltage, V) || colspan="3" | 6-40V
|-
| style="text-align:left;" | Supply protection (Over-voltage 100 VDC for 2 minutes. Reverse polarity) || colspan="3" | Yes
|-
| style="text-align:left;" | Maximum power consumption, mA || colspan="3" | 20
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP69K
|-
| style="text-align:left;" | Operating temperature, °C || colspan="3" | -40...+85
|-
| style="text-align:left;" | Maximum allowed humidity level,% || colspan="3" | 100
|-
| style="text-align:left;" | Resolution, bit || colspan="3" | 12
|-
| style="text-align:left;" | Digital reading range corresponding to the minimum level measurement value || Analog (0...8V) || 0 || 0
|-
| style="text-align:left;" | Digital reading range corresponding to the maximum level measurement value || Analog (1...9V) || 4095 || 4095
|-
| style="text-align:left;" | Average sampling period, s || colspan="3" | 0...255
|-
| style="text-align:left;" | Message interval, s || Continuous || 1...255 || 1...255
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±1
|-
| style="text-align:left;" | Bluetooth specs || colspan="3" | Bluetooth 5.1, IEEE 802.15.4-2006, 2.4 GHz, -95 dBm sensitivity, +8 dBm TX Power
|-
| style="text-align:left;" | Average service life, years (expected) || 10 || 10 || 10
|}

=== Dimensions ===

<div style="text-align:center;">
[[File:LIGO-PRO-BLE-dimensions.png|frameless|703px]]
<div style="font-style:italic; color:#555;">Figure 1. LIGO-PRO-BLE's overall dimensions (cm)</div>
</div>

=== Wiring Connection ===

'''AF (Analog & Frequency)'''

<div style="text-align:center;">
[[File:LIGO-PRO-BLE-wiring-AF.png|frameless|636px]]
<div style="font-style:italic; color:#555;">Figure 2. Wiring diagram of Analog and Frequency output signals</div>
</div>

'''RS232'''

<div style="text-align:center;">
[[File:LIGO-PRO-BLE-wiring-RS232.png|frameless|642px]]
<div style="font-style:italic; color:#555;">Figure 3. Wiring diagram of RS232 output signals'''RS485'''</div>
</div>'''RS485'''<div style="text-align:center;">
[[File:BLE-RS485.jpg|frameless|656x656px]]
<div style="font-style:italic; color:#555;">Figure 4. Wiring diagram of RS485 output signals</div>
</div>

=== Connector ===

<div style="text-align:center;">
[[File:LIGO-PRO-BLE-connector.png|frameless|624px]]
<div style="font-style:italic; color:#555;">Figure 5. The details of connector pins</div>
</div>

<div style="display:flex;gap:20px;justify-content:center;flex-wrap:wrap;align-items:flex-start;">

<div>

{| class="wikitable" style="text-align:center;margin:0;"
|+ AF/ RS232
! No !! Description !! Color of the wire
|-
| 1 || GND || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div>
|-
| 2 || NC (Not connected) || '''NC'''
|-
| 3 || VCC (6-40V) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div>
|-
| 4 || TXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div>
|-
| 5 || Analog Output || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#fff;border:1px solid #999;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">White</span></div>
|-
| 6 || RXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#7b3f00;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Brown</span></div>
|}
</div>

<div>

{| class="wikitable" style="text-align:center;margin:0;"
|+ RS485
! No !! Description !! Color of the wire
|-
| 1 || GND || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div>
|-
| 2 || RS485 (B) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#2e8b2e;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Green</span></div>
|-
| 3 || VCC (6-40V) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div>
|-
| 4 || TXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div>
|-
| 5 || RS485 (A) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div>
|-
| 6 || RXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#7b3f00;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Brown</span></div>
|}
</div>

</div>

== Compliance and Certifications ==

Refer to [[LIGO PRO BLE Certification & Approvals]] for current certificate status.''

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO BLE ]]

File:BLE-RS485.jpg

2026-07-07T07:39:09Z

Admin:

upload

LIGO PRO User Guide

2026-07-07T07:34:50Z

Admin: change content

== Safety Information ==
{{Notice
| title = Installer Qualifications and Safety
| body = *LIGO SP Fuel Level Sensor measures the accurate fuel level in fuel tanks, therefore the device installation process also needs to be extremely accurate.
*Installation technicians should be well-trained by specialists or experts in this field before installing the device.
*Implement protection against electric shocks and electrical fires, labour safety and hygiene.
*List of installing tools is provided in section APPENDIX A below.
*List of accessories is provided in section APPENDIX B below.
}}

== Product Overview ==
LIGO Fuel level sensor is produced and developed by SOJI Electronics Join Stock Company. The device is designed to measure the level of liquid fuels and other non-conductive liquids in vehicle's tanks and stationary fuel storages, applicable in different fields. The measured values will be t transformed into output signal in the form of: Analog, Frequency, RS232, RS485… and transmitted to a connected external device

Under particular conditions, the device can reach a high accuracy up to 99.5%. At present, on the market there are several lines of sensor using different technologies to measure fuel level such as: magnetically operated switches (reed switches), ultrasound wave (ultrasonic sensor), capacitive sensing (capacitive sensor). Among these ones, capacitive sensing technology is considered to have highest accuracy and greatest lifespan.

== Package Contents ==

=== Apendix A ===

List of equipment for fuel level sensors installation

{| class="wikitable" style="text-align:center;"
|-
! STT !! Descriptions !! Qty
|-
| 1 || style="text-align:left;" | Bimetal core drill ø38 mm || 1
|-
| 2 || style="text-align:left;" | Core drill shank || 1
|-
| 3 || style="text-align:left;" | Metal drill ø7 mm & ø4 mm || 1
|-
| 4 || style="text-align:left;" | Hacksaw || 1
|-
| 5 || style="text-align:left;" | T Spanner 8mm Single Sided || 1
|-
| 6 || style="text-align:left;" | Tap M5 with holder || 1
|-
| 7 || style="text-align:left;" | Snap-seal for bolt/self-tapping screw || 1
|-
| 8 || style="text-align:left;" | Laptop || 1
|-
| 9 || style="text-align:left;" | DC power supply unit 12V-24V or battery 12V || 1
|-
| 10 || style="text-align:left;" | Measuring container || 1
|-
| 11 || style="text-align:left;" | Fuel || 1
|-
| 12 || style="text-align:left;" | Gauging container || 1
|-
| 19 || style="text-align:left;" | USB to RS232 cable || 1
|-
| 20 || style="text-align:left;" | Tape mesaure || 1
|}

=== Apendix B ===

Sensor LIGO SP and all the accessories

<div style="text-align:center;">
[[File:LIGO-SP-accessories.png|frameless|782px]]
<div style="font-style:italic; color:#555;">Sensor LIGO SP and all the accessories</div>
</div>

{| class="wikitable" style="text-align:center;"
|-
! STT !! Description !! Qty
|-
| 1 || style="text-align:left;" | LIGO Fuel Level Sensor. Standard lengths: 700, 1000, 1500mm (for other customized lengths, please contact the manufacturer) || 01
|-
| 2 || style="text-align:left;" | 7m cable || 01
|-
| 3 || style="text-align:left;" | Gasoline resistant rubber gasket || 01
|-
| 4 || style="text-align:left;" | Oil filter || 01
|-
| 5 || style="text-align:left;" | Anti-vibration spring || 01
|-
| 6 || style="text-align:left;" | Fuse 2A || 01
|-
| 7 || style="text-align:left;" | Sealing cord || 02
|-
| 8 || style="text-align:left;" | Rivet and screw M5x20mm || 04
|-
| 9 || style="text-align:left;" | Self-drilling screw M4.8x32mm || 04
|}

== Specifications ==

=== Technical specifications of the LIGO-SP product ===

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! AF !! RS232 !! RS485
|-
| style="text-align:left;" | Standard length (L),mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Output signal || Analog (0…9V), Frequency (500… 2000Hz). || RS232 || RS485
|-
| style="text-align:left;" | Baud rate, bit/sec || 9600 || colspan="2" | 2400, 4800, 9600, 19200, 38400, 57600, 115200.
|-
| style="text-align:left;" | Power supply (DC input voltage, V) || 15-37 || 12-37 || 12-37
|-
| style="text-align:left;" | Maximum power consumption, mA || colspan="3" | 20
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP67
|-
| style="text-align:left;" | Operating temperature, °C || colspan="3" | -40...+85
|-
| style="text-align:left;" | Maximum allowed humidity level,% || colspan="3" | 100
|-
| style="text-align:left;" | Resolution, bit || colspan="3" | 12
|-
| style="text-align:left;" | Digital reading range corresponding to the minimum level measurement value || Analog (0...8V); Frequency (500...1500 Hz) || 0 || 0
|-
| style="text-align:left;" | Digital reading range corresponding to the maximum level measurement value || Analog (1...9V); Frequency (1000...2000 Hz) || 4095 || 4095
|-
| style="text-align:left;" | Average sampling period, (s) || colspan="3" | 0...255
|-
| style="text-align:left;" | Message interval, (s) || Continuous || 1...60 || 1...60
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±2
|-
| style="text-align:left;" | Average service life, (years)) || colspan="3" | 8
|}

=== Technical specifications of the LIGO-SP PRO product ===

* LIGO-SP PRO product is designed for devices having wide input voltage (7-75V), the voltage of the internal sensing printed circuit board isolated from outside is 2500V. The internal temperature sensor has a very low error at <0.6°С. The product is designed to operate in extreme environment.

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! AF !! RS232 !! RS485
|-
| style="text-align:left;" | Standard length (L),mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Output signal || Analog (0…9), Frequency (500… 2000Hz). || RS232 || RS485
|-
| style="text-align:left;" | Baud rate, bit/sec || 9600 || colspan="2" | 2400, 4800, 9600, 19200, 38400, 57600, 115200.
|-
| style="text-align:left;" | Power supply (DC input voltage, V)<br>2500V internal isolated || colspan="3" | 7-75
|-
| style="text-align:left;" | Maximum power consumption, mA || colspan="3" | 20
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP67
|-
| style="text-align:left;" | Operating temperature, °C || colspan="3" | -40...+85
|-
| style="text-align:left;" | Maximum allowed humidity level,% || colspan="3" | 100
|-
| style="text-align:left;" | Resolution, bit || colspan="3" | 12
|-
| style="text-align:left;" | Digital reading range corresponding to the minimum level measurement value. || Analog (0...8V); Frequency (500...1500 Hz) || 0 || 0
|-
| style="text-align:left;" | Digital reading range corresponding to the maximum level measurement value || Analog (1...9V); Frequency (1000...2000 Hz) || 4095 || 4095
|-
| style="text-align:left;" | Average sampling time, (s) || colspan="3" | 0...255
|-
| style="text-align:left;" | Message interval, (s) || continuous || 1...60 || 1...60
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±0.6
|-
| style="text-align:left;" | Average service life, (years) || colspan="3" | 10
|}

== Installation ==

=== Selecting the location to install sensor ===

* Installation location should be as close as possible to the geometric center and placed at the deepest level of the tank.

<div style="text-align:center;">
[[File:LIGO-SP-fig1-location.png|frameless|894px]]
<div style="font-style:italic; color:#555;">Figure 1. Selecting the location to install sensor</div>
</div>

* When being installed, the sensor should not be in contact with reinforcement ribs inside the tank

<div style="text-align:center;">
[[File:LIGO-SP-fig2-two-sensors.png|frameless|730px]]
<div style="font-style:italic; color:#555;">Figure 2. Installation of two sensors in one tank allows for significant reduction</div>
</div>

=== Drilling the hole on fuel tank ===

* Drill out the central bore by bimetal core drill ø38 mm

<div style="text-align:center;">
[[File:LIGO-SP-fig3-drilling.png|frameless|580px]]
<div style="font-style:italic; color:#555;">Figure 3. Drilling the selected hole</div>
</div>

* Drill out four mounting holes according to the diagram:

<div style="text-align:center;">
[[File:LIGO-SP-fig4-mounting-holes.png|frameless|541px]]
<div style="font-style:italic; color:#555;">Figure 4. Drill out four mounting holes</div>
</div>

The mounting hole diameter depends on the tank material:

* ø 4 mm – for metal tank with wall thickness over 3 mm (cut M5 self screw M4.8)

<div style="text-align:center;">
[[File:LIGO-SP-fig5-hole-thick.png|frameless|402px]]
<div style="font-style:italic; color:#555;">Figure 5. Hole thick</div>
</div>

* ø 7 mm – for plastic and metal tank with wall thickness up to 3 mm (for rivets)

<div style="text-align:center;">
[[File:LIGO-SP-fig6-rivet-nut.png|frameless|372px]]
<div style="font-style:italic; color:#555;">Figure 6. Rivet nut M5</div>
</div>

<div style="text-align:center;">
[[File:LIGO-SP-fig7-install-rivet.png|frameless|535px]]
<div style="font-style:italic; color:#555;">Figure 7. Installing revit nut if tank's wall is thinner than 3mm</div>
</div>

=== Measuaring the tank depth and cutting sensor'measuring probe ===

<div style="text-align:center;">
[[File:LIGO-SP-fig8-measure-depth.png|frameless|615px]]
<div style="font-style:italic; color:#555;">Figure 8. Measuring the tank depth</div>
</div>

* Cut the sensor's measuring probe so that its length is 25 mm less than the depth of the tank. Ensure that shearing line is perpendicular to the sensor longitudinal axis

<div style="text-align:center;">
[[File:LIGO-SP-fig9-length.png|frameless|723px]]
<div style="font-style:italic; color:#555;">Figure 9. Origin length (L) and length after cutting (Lm)</div>
</div>

Notes: Minimum allowable length of the measuring probe is 150 mm.

== Configuration ==

=== On mobile platform ===

Connecting the sensor to LIGO mobile configurator

<div style="text-align:center;">
[[File:LIGO-PRO-mobile-connect.png|frameless|600px]]
<div style="font-style:italic; color:#555;">Figure 9. Connecting the sensor to the LIGO mobile configurator</div>
</div>

Configuring and managing the appropriate settings for the LiGO device sensor is essential to ensure its proper, stable, and accurate operation. It also allows for continuous monitoring of the device's operational status, potential failures (whether caused by the sensor itself or external factors), and overall lifespan.

<div style="text-align:center;">
[[File:LIGO-PRO-mobile-ui.png|frameless|444px]]
<div style="font-style:italic; color:#555;">Figure 10. Device's management, setting up and configuration software interface</div>
</div>

=== On PC Device ===
==== Installing software and connecting configuration tool ====

'''Preparation:'''
* Laptop or PC
* Power supply 12 -24VDC or battery 12V
* USB to RS232 cable.
* Configuration tool from SOJI ELECTRONICS (We recommend to upgrage to the latest possible version)

<div style="text-align:center;">
[[File:LIGO-SP-fig10-connect.png|frameless|969px]]
<div style="font-style:italic; color:#555;">Figure 10. Connecting USB to RS232 cable and configuration tool to laptop or PC</div>
</div>

12-24VDC

==== Download and install software. Downloading and installing softwares ====

===== Installing USB to RS232 driver =====

* Installing driver for USB to RS232 cable
* After finishing right click and check to ensure the driver is installed successful "Computer" >> "Manager" >> "Device Manager" >> "Port (COM & LPT)" as follow the picture bellow, otherwise, please check the cable and cable driver.

<div style="text-align:center;">
[[File:LIGO-SP-fig11-driver.png|frameless|678px]]
<div style="font-style:italic; color:#555;">Figure 11. Installing USB to RS232 driver successful</div>
</div>

===== Installing sensor software configuration =====

* Visit our website: [http://sojielectronics.com/support/download/ http://sojielectronics.com/support/download/] and download setup file "Setup Utility Program "

<div style="text-align:center;">
[[File:LIGO-SP-fig12-config-tool.png|frameless|710px]]
<div style="font-style:italic; color:#555;">Figure 12. Sensor configuration tool</div>
</div>

'''Parameters descriptions:'''

'''Load config:''' Load configurations from sensor to PC. Note: user must load configurations from sensor before changing configurations on PC.

'''Save config:''' Save configurations from PC to sensor

'''Update firmware:''' Upgrade new firmware for sensor (visit www.sojielectronics.com for the latest firmware version)

'''Set full:''' Set Full for maximum fuel level calibration

'''Set Empty:''' Set Empty for minimum fuel level calibration

'''Level Min:''' Configure LIGO SP-AF output voltage or frequency range according to the voltage or frequency range of the tracking device input.

'''Level Max:''' Configure LIGO SP-AF output voltage or frequency range according to the voltage or frequency range of the tracking device input

'''Output type:''' Selecting voltage or frequency output (used only for AF sensor)

'''Filter time:''' Setting output signal processing time (0-255). Default is 60 seconds.

'''Automatic transmission mode:''' Automatic transmission mode applied only for RS232/RS485 defines sensor output message type:
* Off – no automatic message transmission, sensor waits for tracking device request;
* HEX - automatic message transmission in binary format (used by default);
* ASCII - automatic message transmission in text format;
* ASCII EXT – automatic message transmission in extended text format. Additional Prefix and Postfix configurable parameters are available for this mode to insert required header or ending of the message.

'''Message interval:''' Time period the sensor automatically send output message to the tracking device. Parameter value range is 1…255 seconds with 1 second step. Default value is 1 second.

'''Actual length:''' The actual length of sensor probe

'''Address (0-254):''' Set the network address for the sensor. When several sensors are connected to one external device, they should have a unique network address.

'''Parameter selection:''' Selection of output value type for sensor data

One of the following output value types available for RS232 and RS485 sensor
* Fuel level in standard (normalized) units (0...1000).
* Fuel level in millimeters (mm), 0.1 mm step.
* Fuel volume in liters (L), 0.1 L step.
* Fuel volume in percentage (%), 0.4% step.

'''Output:'''

'''OSC frequency:''' Initial measuring generator frequency (Hz)

'''Data output:''' Data output (0-4095)

'''Sensor message:''' Sensor working message if sensor message is none sensor works fine, otherwise malfunction codes are displayed as table:

{| class="wikitable"
|-
! Sensor message !! Transcript of the malfunction Code !! Possible solution
|-
| style="text-align:center;" | 255 or 254 || Calibration error || Check if the measuring probe actual size value is inserted correctly and (or) re-calibrate the sensor
|-
| style="text-align:center;" | 253 || Short circuit in measuring probe tubes || Wash the measuring probe tubes with clean fuel, clean fuel tank of mud and water.
|-
| style="text-align:center;" | 252 || Calibration error || Check if the measuring probe actual size value is inserted correctly and (or) re-calibrate the sensor
|-
| style="text-align:center;" | 251 || Hardware failure || Contact supplier
|-
| style="text-align:center;" | 250 || Calibration error || Check if the measuring probe actual size value is inserted correctly and (or) re-calibrate the sensor.
|}

'''Calibration Table:''' This entry is used to record fuel tank calibration into the sensor internal memory. The table is filled out with the data achieved during fuel tank calibration procedure. The data is entered as a table of correspondence between measured fuel level value (Fuel level (uint) field) and fuel volume in the tank (Volume (L) field). Recommended number of table entries is 15. Max possible is 30 entries.

'''Enable AutoClib feature:''' Sensor automatically calibrates Min, Max levels after cutting. User does not need to reconfigure after cutting.

===== Min/Max Calibration =====

'''a) Set Empty level'''

* Keeping sensor apart from fuel and set Empty level

<div style="text-align:center;">
[[File:LIGO-SP-fig13-set-empty.png|frameless|689px]]
<div style="font-style:italic; color:#555;">Figure 13. Setting Empty level.</div>
</div>

'''b) Set Full level'''

* Fill the measuring container with fuel.
* Immerse the sensor in the fuel to the full length of the measuring probe and set Full level

<div style="text-align:center;">
[[File:LIGO-SP-fig14-set-full.png|frameless|655px]]
<div style="font-style:italic; color:#555;">Figure 14. Setting Full level</div>
</div>

'''c) Installing screen filter'''

Screen filter is mounted on the measuring probe of sensor to protect measuring probe electrodes from mud and water. Using the filter extends significantly faultless lifetime of the sensor.

Screen filter mounting order: firstly put on fixator, then put on bottom stop and fix it with two side screws. Put the screen filter over bottom stop and fasten it with a fixator locks.

<div style="text-align:center;">
[[File:LIGO-SP-fig15-screen-filter.png|frameless|747px]]
<div style="font-style:italic; color:#555;">Figure 15. Installing screen filter procedue</div>
</div>

'''d) Installing and connecting'''

* Applying oil-and-petrol resistant non-conductive sealant to ruber gasket

<div style="text-align:center;">
[[File:LIGO-SP-fig16-sealant.png|frameless|595px]]
<div style="font-style:italic; color:#555;">Figure 16. Applying the sealant to gasket</div>
</div>

* Put the sensor into the tank and fix: when fixing with rivets, use a rivet driver when bolting, put on a seal (per bolt), a spacer and a spring washer when fixing to plastic tanks with wall thickness over 3 mm, use vendor furnished self-tapping screws and a seal (per self-tapping screw)

<div style="text-align:center;">
[[File:LIGO-SP-fig17-install.png|frameless|663px]]
<div style="font-style:italic; color:#555;">Figure 17. Put sensor into the tank</div>
</div>

* Connect the sensors to an external device using 7m cable

The wire cable color:

'''RS232/RS485:'''

<div style="text-align:center;">
[[File:RS232-RS485.jpg|frameless|756x756px]]
<div style="font-style:italic; color:#555;">Figure 18. Wiring diagram of RS232 and RS485 output signals</div>
</div>

{| class="wikitable" style="text-align:center;"
! Wire Color !! Description
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div> || style="text-align:left;" | GND (Ground) (V-)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div> || style="text-align:left;" | RXD/B-
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div> || style="text-align:left;" | TXD/A+
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div> || style="text-align:left;" | 12-37 VDC or 7.5-75V for SP PRO series
|}

'''AF:'''

<div style="text-align:center;">
[[File:LIGO-SP-fig19-wiring-AF.png|frameless|873px]]
<div style="font-style:italic; color:#555;">Figure 19. Wiring diagram of Analog and Frequency output signals.</div>
</div>

{| class="wikitable" style="text-align:center;"
! Wire Color !! Description
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div> || style="text-align:left;" | GND (Ground) (V-)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div> || style="text-align:left;" | Out (Analog/Frequency)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div> || style="text-align:left;" | 15-37 VDC or 7.5-75V for SP PRO series
|}

* Connect the fuse holder to LIGO sensor power cable (brown wire) in close vicinity to the vehicle power supply circuit
* Installing the fuse in the fuse holder

'''e) Calibration'''

* Launch Sensor >> load Config >> From Sensor >> Calibration Table

<div style="text-align:center;">
[[File:LIGO-SP-fig20-calib-table.png|frameless|727px]]
<div style="font-style:italic; color:#555;">Figure 20. Calibration table</div>
</div>

* Pump fuel in the tank, the amount of pumped fuel depends on the tank's volume (at least 20 times of pumping)
* After pumping, wait for a while (about 2 minutes) for the output data to be stable, then select "add a row" and insert the actual pumped liters in "liter" box, input the data given by sensor into "Data" box. User can click on the button to sync up data, or read data in the "output" tab as the image below.
* Repeat the above steps until the oil tank is full (Attention: It is recommended to write down the information on the paper to compare with input data and avoid mistaking during the process)
* After completing the above process, select "Volume (liter)'' as the output data.

<div style="text-align:center;">
[[File:LIGO-SP-fig21-param.png|frameless|464px]]
<div style="font-style:italic; color:#555;">Figure 21. Parameter selection</div>
</div>

* Finally, click on the "Sensor" button at the top left corner -> Save config -> To sensor to save data for the sensor.

'''Attention:'''
* The time between each pumping must be at least 2 minutes apart or wait for measured values to be stable, then comes the next pumping.

'''f) Sealing'''

* Install the bolt through a hole in the seal.

<div style="text-align:center;">
[[File:LIGO-SP-fig22-sealing.png|frameless|891px]]
<div style="font-style:italic; color:#555;">Figure 22. Sealing</div>
</div>

==== Quick installation without PC ====

This method is only applicable to configure Min and Max level.

===== Preparation before setting up =====

* The sensor's auto-recognisation mode needs to be turned on by checking the "Enable AutoCalib Feature" box.

<div style="text-align:center;">
[[File:LIGO-SP-fig24-autocalib.png|frameless|865px]]
<div style="font-style:italic; color:#555;">Figure 24. Turning on the auto-recognisation mode before installing</div>
</div>

* External devices such as GPS tracking or Dataloger… must have the software integrated with the configurator. The configuration is performed directly on the device.

===== Automatically setting up and configuring the sensor after cutting =====

* After measuring and cutting sensor, remove iron filings and clean burrs between the tubes, then follow steps below:

'''Step 1:''' Do not allow the sensor to contact oil.

'''Step 2:''' Ensure 12-24VDC stable power supply for the sensor.

'''Step 3:''' Make sure the sensor is under stable condition within 30-60s. The sensor will automatically recognise Min and Max level.

'''Step 4:''' Cut the power and reboot. The sensor now recognizes new configurations.

<div style="text-align:center;">
[[File:LIGO-SP-fig25-auto-config.png|frameless|634px]]
<div style="font-style:italic; color:#555;">Figure 25. Leave the sensor in the air, provide with a stable power supply in 30-60s to configure "Min" level.</div>
</div>

'''Attention:'''

- In case of improper operation and the sensor cannot recognise properly the actual Min, Max level, user should reconfigure using a PC.

==== Connecting multiple sensors together ====

''(Only applicable to RS232 and RS485)''

In some situations, there are oil tanks with specific dimensions, interconnected oil tanks, or oil tanks that are either too long or too large. Using just one sensor to measure the accurate fuel level inside these oil tanks may not be feasible. Hence, there is a need to connect two or more sensors together through a data processor called SUM-DATA.

<div style="text-align:center;">
[[File:LIGO-PRO-multi-sensor-tank.png|frameless|728px]]
<div style="font-style:italic; color:#555;">Figure 26. Oil tank with particular dimensions connecting multiple sensors together</div>
</div>

Connection diagram of the processor SUM-DATA for multiple sensors:

<div style="text-align:center;">
[[File:LIGO-PRO-sumdata-2sensors.png|frameless|648px]]
<div style="font-style:italic; color:#555;">Figure 27: Connecting two sensors by 01 processor SUM-DATA</div>
</div>

<div style="text-align:center;">
[[File:LIGO-PRO-sumdata-multi.png|frameless|707px]]
<div style="font-style:italic; color:#555;">Figure 28: Connecting multiple sensors together by multiple processors SUM-DATA</div>
</div>

== Operation ==

== Troubleshooting ==

== Maintenance ==

== Certification / Compliance ==

Refer to [[LIGO PRO Certification & Approvals]] for current certificate status.''

== Support / Contact ==

{| class="wikitable"
|-
! Channel !! Detail
|-
| Company || SOJI ELECTRONICS.,JSC
|-
| Address || C50-LK13, Lot No. 09, New Urban Area, Le Trong Tan street, Duong Noi Ward, Ha Dong District, Hanoi City, Vietnam
|-
| Tel/Fax || +84 24 62 932 369
|-
| Email || contact@sojielectronics.com
|-
| Website || [http://sojielectronics.com sojielectronics.com]
|}

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO ]]

LIGO PRO User Guide

2026-07-07T07:33:56Z

Admin: change image

== Safety Information ==
{{Notice
| title = Installer Qualifications and Safety
| body = *LIGO SP Fuel Level Sensor measures the accurate fuel level in fuel tanks, therefore the device installation process also needs to be extremely accurate.
*Installation technicians should be well-trained by specialists or experts in this field before installing the device.
*Implement protection against electric shocks and electrical fires, labour safety and hygiene.
*List of installing tools is provided in section APPENDIX A below.
*List of accessories is provided in section APPENDIX B below.
}}

== Product Overview ==
LIGO Fuel level sensor is produced and developed by SOJI Electronics Join Stock Company. The device is designed to measure the level of liquid fuels and other non-conductive liquids in vehicle's tanks and stationary fuel storages, applicable in different fields. The measured values will be t transformed into output signal in the form of: Analog, Frequency, RS232, RS485… and transmitted to a connected external device

Under particular conditions, the device can reach a high accuracy up to 99.5%. At present, on the market there are several lines of sensor using different technologies to measure fuel level such as: magnetically operated switches (reed switches), ultrasound wave (ultrasonic sensor), capacitive sensing (capacitive sensor). Among these ones, capacitive sensing technology is considered to have highest accuracy and greatest lifespan.

== Package Contents ==

=== Apendix A ===

List of equipment for fuel level sensors installation

{| class="wikitable" style="text-align:center;"
|-
! STT !! Descriptions !! Qty
|-
| 1 || style="text-align:left;" | Bimetal core drill ø38 mm || 1
|-
| 2 || style="text-align:left;" | Core drill shank || 1
|-
| 3 || style="text-align:left;" | Metal drill ø7 mm & ø4 mm || 1
|-
| 4 || style="text-align:left;" | Hacksaw || 1
|-
| 5 || style="text-align:left;" | T Spanner 8mm Single Sided || 1
|-
| 6 || style="text-align:left;" | Tap M5 with holder || 1
|-
| 7 || style="text-align:left;" | Snap-seal for bolt/self-tapping screw || 1
|-
| 8 || style="text-align:left;" | Laptop || 1
|-
| 9 || style="text-align:left;" | DC power supply unit 12V-24V or battery 12V || 1
|-
| 10 || style="text-align:left;" | Measuring container || 1
|-
| 11 || style="text-align:left;" | Fuel || 1
|-
| 12 || style="text-align:left;" | Gauging container || 1
|-
| 19 || style="text-align:left;" | USB to RS232 cable || 1
|-
| 20 || style="text-align:left;" | Tape mesaure || 1
|}

=== Apendix B ===

Sensor LIGO SP and all the accessories

<div style="text-align:center;">
[[File:LIGO-SP-accessories.png|frameless|782px]]
<div style="font-style:italic; color:#555;">Sensor LIGO SP and all the accessories</div>
</div>

{| class="wikitable" style="text-align:center;"
|-
! STT !! Description !! Qty
|-
| 1 || style="text-align:left;" | LIGO Fuel Level Sensor. Standard lengths: 700, 1000, 1500mm (for other customized lengths, please contact the manufacturer) || 01
|-
| 2 || style="text-align:left;" | 7m cable || 01
|-
| 3 || style="text-align:left;" | Gasoline resistant rubber gasket || 01
|-
| 4 || style="text-align:left;" | Oil filter || 01
|-
| 5 || style="text-align:left;" | Anti-vibration spring || 01
|-
| 6 || style="text-align:left;" | Fuse 2A || 01
|-
| 7 || style="text-align:left;" | Sealing cord || 02
|-
| 8 || style="text-align:left;" | Rivet and screw M5x20mm || 04
|-
| 9 || style="text-align:left;" | Self-drilling screw M4.8x32mm || 04
|}

== Specifications ==

=== Technical specifications of the LIGO-SP product ===

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! AF !! RS232 !! RS485
|-
| style="text-align:left;" | Standard length (L),mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Output signal || Analog (0…9V), Frequency (500… 2000Hz). || RS232 || RS485
|-
| style="text-align:left;" | Baud rate, bit/sec || 9600 || colspan="2" | 2400, 4800, 9600, 19200, 38400, 57600, 115200.
|-
| style="text-align:left;" | Power supply (DC input voltage, V) || 15-37 || 12-37 || 12-37
|-
| style="text-align:left;" | Maximum power consumption, mA || colspan="3" | 20
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP67
|-
| style="text-align:left;" | Operating temperature, °C || colspan="3" | -40...+85
|-
| style="text-align:left;" | Maximum allowed humidity level,% || colspan="3" | 100
|-
| style="text-align:left;" | Resolution, bit || colspan="3" | 12
|-
| style="text-align:left;" | Digital reading range corresponding to the minimum level measurement value || Analog (0...8V); Frequency (500...1500 Hz) || 0 || 0
|-
| style="text-align:left;" | Digital reading range corresponding to the maximum level measurement value || Analog (1...9V); Frequency (1000...2000 Hz) || 4095 || 4095
|-
| style="text-align:left;" | Average sampling period, (s) || colspan="3" | 0...255
|-
| style="text-align:left;" | Message interval, (s) || Continuous || 1...60 || 1...60
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±2
|-
| style="text-align:left;" | Average service life, (years)) || colspan="3" | 8
|}

=== Technical specifications of the LIGO-SP PRO product ===

* LIGO-SP PRO product is designed for devices having wide input voltage (7-75V), the voltage of the internal sensing printed circuit board isolated from outside is 2500V. The internal temperature sensor has a very low error at <0.6°С. The product is designed to operate in extreme environment.

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! AF !! RS232 !! RS485
|-
| style="text-align:left;" | Standard length (L),mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Output signal || Analog (0…9), Frequency (500… 2000Hz). || RS232 || RS485
|-
| style="text-align:left;" | Baud rate, bit/sec || 9600 || colspan="2" | 2400, 4800, 9600, 19200, 38400, 57600, 115200.
|-
| style="text-align:left;" | Power supply (DC input voltage, V)<br>2500V internal isolated || colspan="3" | 7-75
|-
| style="text-align:left;" | Maximum power consumption, mA || colspan="3" | 20
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP67
|-
| style="text-align:left;" | Operating temperature, °C || colspan="3" | -40...+85
|-
| style="text-align:left;" | Maximum allowed humidity level,% || colspan="3" | 100
|-
| style="text-align:left;" | Resolution, bit || colspan="3" | 12
|-
| style="text-align:left;" | Digital reading range corresponding to the minimum level measurement value. || Analog (0...8V); Frequency (500...1500 Hz) || 0 || 0
|-
| style="text-align:left;" | Digital reading range corresponding to the maximum level measurement value || Analog (1...9V); Frequency (1000...2000 Hz) || 4095 || 4095
|-
| style="text-align:left;" | Average sampling time, (s) || colspan="3" | 0...255
|-
| style="text-align:left;" | Message interval, (s) || continuous || 1...60 || 1...60
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±0.6
|-
| style="text-align:left;" | Average service life, (years) || colspan="3" | 10
|}

== Installation ==

=== Selecting the location to install sensor ===

* Installation location should be as close as possible to the geometric center and placed at the deepest level of the tank.

<div style="text-align:center;">
[[File:LIGO-SP-fig1-location.png|frameless|894px]]
<div style="font-style:italic; color:#555;">Figure 1. Selecting the location to install sensor</div>
</div>

* When being installed, the sensor should not be in contact with reinforcement ribs inside the tank

<div style="text-align:center;">
[[File:LIGO-SP-fig2-two-sensors.png|frameless|730px]]
<div style="font-style:italic; color:#555;">Figure 2. Installation of two sensors in one tank allows for significant reduction</div>
</div>

=== Drilling the hole on fuel tank ===

* Drill out the central bore by bimetal core drill ø38 mm

<div style="text-align:center;">
[[File:LIGO-SP-fig3-drilling.png|frameless|580px]]
<div style="font-style:italic; color:#555;">Figure 3. Drilling the selected hole</div>
</div>

* Drill out four mounting holes according to the diagram:

<div style="text-align:center;">
[[File:LIGO-SP-fig4-mounting-holes.png|frameless|541px]]
<div style="font-style:italic; color:#555;">Figure 4. Drill out four mounting holes</div>
</div>

The mounting hole diameter depends on the tank material:

* ø 4 mm – for metal tank with wall thickness over 3 mm (cut M5 self screw M4.8)

<div style="text-align:center;">
[[File:LIGO-SP-fig5-hole-thick.png|frameless|402px]]
<div style="font-style:italic; color:#555;">Figure 5. Hole thick</div>
</div>

* ø 7 mm – for plastic and metal tank with wall thickness up to 3 mm (for rivets)

<div style="text-align:center;">
[[File:LIGO-SP-fig6-rivet-nut.png|frameless|372px]]
<div style="font-style:italic; color:#555;">Figure 6. Rivet nut M5</div>
</div>

<div style="text-align:center;">
[[File:LIGO-SP-fig7-install-rivet.png|frameless|535px]]
<div style="font-style:italic; color:#555;">Figure 7. Installing revit nut if tank's wall is thinner than 3mm</div>
</div>

=== Measuaring the tank depth and cutting sensor'measuring probe ===

<div style="text-align:center;">
[[File:LIGO-SP-fig8-measure-depth.png|frameless|615px]]
<div style="font-style:italic; color:#555;">Figure 8. Measuring the tank depth</div>
</div>

* Cut the sensor's measuring probe so that its length is 25 mm less than the depth of the tank. Ensure that shearing line is perpendicular to the sensor longitudinal axis

<div style="text-align:center;">
[[File:LIGO-SP-fig9-length.png|frameless|723px]]
<div style="font-style:italic; color:#555;">Figure 9. Origin length (L) and length after cutting (Lm)</div>
</div>

Notes: Minimum allowable length of the measuring probe is 150 mm.

== Configuration ==

=== On mobile platform ===

Connecting the sensor to LIGO mobile configurator

<div style="text-align:center;">
[[File:LIGO-PRO-mobile-connect.png|frameless|600px]]
<div style="font-style:italic; color:#555;">Figure 9. Connecting the sensor to the LIGO mobile configurator</div>
</div>

Configuring and managing the appropriate settings for the LiGO device sensor is essential to ensure its proper, stable, and accurate operation. It also allows for continuous monitoring of the device's operational status, potential failures (whether caused by the sensor itself or external factors), and overall lifespan.

<div style="text-align:center;">
[[File:LIGO-PRO-mobile-ui.png|frameless|444px]]
<div style="font-style:italic; color:#555;">Figure 10. Device's management, setting up and configuration software interface</div>
</div>

=== On PC Device ===
==== Installing software and connecting configuration tool ====

'''Preparation:'''
* Laptop or PC
* Power supply 12 -24VDC or battery 12V
* USB to RS232 cable.
* Configuration tool from SOJI ELECTRONICS (We recommend to upgrage to the latest possible version)

<div style="text-align:center;">
[[File:LIGO-SP-fig10-connect.png|frameless|969px]]
<div style="font-style:italic; color:#555;">Figure 10. Connecting USB to RS232 cable and configuration tool to laptop or PC</div>
</div>

12-24VDC

==== Download and install software. Downloading and installing softwares ====

===== Installing USB to RS232 driver =====

* Installing driver for USB to RS232 cable
* After finishing right click and check to ensure the driver is installed successful "Computer" >> "Manager" >> "Device Manager" >> "Port (COM & LPT)" as follow the picture bellow, otherwise, please check the cable and cable driver.

<div style="text-align:center;">
[[File:LIGO-SP-fig11-driver.png|frameless|678px]]
<div style="font-style:italic; color:#555;">Figure 11. Installing USB to RS232 driver successful</div>
</div>

===== Installing sensor software configuration =====

* Visit our website: [http://sojielectronics.com/support/download/ http://sojielectronics.com/support/download/] and download setup file "Setup Utility Program "

<div style="text-align:center;">
[[File:LIGO-SP-fig12-config-tool.png|frameless|710px]]
<div style="font-style:italic; color:#555;">Figure 12. Sensor configuration tool</div>
</div>

'''Parameters descriptions:'''

'''Load config:''' Load configurations from sensor to PC. Note: user must load configurations from sensor before changing configurations on PC.

'''Save config:''' Save configurations from PC to sensor

'''Update firmware:''' Upgrade new firmware for sensor (visit www.sojielectronics.com for the latest firmware version)

'''Set full:''' Set Full for maximum fuel level calibration

'''Set Empty:''' Set Empty for minimum fuel level calibration

'''Level Min:''' Configure LIGO SP-AF output voltage or frequency range according to the voltage or frequency range of the tracking device input.

'''Level Max:''' Configure LIGO SP-AF output voltage or frequency range according to the voltage or frequency range of the tracking device input

'''Output type:''' Selecting voltage or frequency output (used only for AF sensor)

'''Filter time:''' Setting output signal processing time (0-255). Default is 60 seconds.

'''Automatic transmission mode:''' Automatic transmission mode applied only for RS232/RS485 defines sensor output message type:
* Off – no automatic message transmission, sensor waits for tracking device request;
* HEX - automatic message transmission in binary format (used by default);
* ASCII - automatic message transmission in text format;
* ASCII EXT – automatic message transmission in extended text format. Additional Prefix and Postfix configurable parameters are available for this mode to insert required header or ending of the message.

'''Message interval:''' Time period the sensor automatically send output message to the tracking device. Parameter value range is 1…255 seconds with 1 second step. Default value is 1 second.

'''Actual length:''' The actual length of sensor probe

'''Address (0-254):''' Set the network address for the sensor. When several sensors are connected to one external device, they should have a unique network address.

'''Parameter selection:''' Selection of output value type for sensor data

One of the following output value types available for RS232 and RS485 sensor
* Fuel level in standard (normalized) units (0...1000).
* Fuel level in millimeters (mm), 0.1 mm step.
* Fuel volume in liters (L), 0.1 L step.
* Fuel volume in percentage (%), 0.4% step.

'''Output:'''

'''OSC frequency:''' Initial measuring generator frequency (Hz)

'''Data output:''' Data output (0-4095)

'''Sensor message:''' Sensor working message if sensor message is none sensor works fine, otherwise malfunction codes are displayed as table:

{| class="wikitable"
|-
! Sensor message !! Transcript of the malfunction Code !! Possible solution
|-
| style="text-align:center;" | 255 or 254 || Calibration error || Check if the measuring probe actual size value is inserted correctly and (or) re-calibrate the sensor
|-
| style="text-align:center;" | 253 || Short circuit in measuring probe tubes || Wash the measuring probe tubes with clean fuel, clean fuel tank of mud and water.
|-
| style="text-align:center;" | 252 || Calibration error || Check if the measuring probe actual size value is inserted correctly and (or) re-calibrate the sensor
|-
| style="text-align:center;" | 251 || Hardware failure || Contact supplier
|-
| style="text-align:center;" | 250 || Calibration error || Check if the measuring probe actual size value is inserted correctly and (or) re-calibrate the sensor.
|}

'''Calibration Table:''' This entry is used to record fuel tank calibration into the sensor internal memory. The table is filled out with the data achieved during fuel tank calibration procedure. The data is entered as a table of correspondence between measured fuel level value (Fuel level (uint) field) and fuel volume in the tank (Volume (L) field). Recommended number of table entries is 15. Max possible is 30 entries.

'''Enable AutoClib feature:''' Sensor automatically calibrates Min, Max levels after cutting. User does not need to reconfigure after cutting.

===== Min/Max Calibration =====

'''a) Set Empty level'''

* Keeping sensor apart from fuel and set Empty level

<div style="text-align:center;">
[[File:LIGO-SP-fig13-set-empty.png|frameless|689px]]
<div style="font-style:italic; color:#555;">Figure 13. Setting Empty level.</div>
</div>

'''b) Set Full level'''

* Fill the measuring container with fuel.
* Immerse the sensor in the fuel to the full length of the measuring probe and set Full level

<div style="text-align:center;">
[[File:LIGO-SP-fig14-set-full.png|frameless|655px]]
<div style="font-style:italic; color:#555;">Figure 14. Setting Full level</div>
</div>

'''c) Installing screen filter'''

Screen filter is mounted on the measuring probe of sensor to protect measuring probe electrodes from mud and water. Using the filter extends significantly faultless lifetime of the sensor.

Screen filter mounting order: firstly put on fixator, then put on bottom stop and fix it with two side screws. Put the screen filter over bottom stop and fasten it with a fixator locks.

<div style="text-align:center;">
[[File:LIGO-SP-fig15-screen-filter.png|frameless|747px]]
<div style="font-style:italic; color:#555;">Figure 15. Installing screen filter procedue</div>
</div>

'''d) Installing and connecting'''

* Applying oil-and-petrol resistant non-conductive sealant to ruber gasket

<div style="text-align:center;">
[[File:LIGO-SP-fig16-sealant.png|frameless|595px]]
<div style="font-style:italic; color:#555;">Figure 16. Applying the sealant to gasket</div>
</div>

* Put the sensor into the tank and fix: when fixing with rivets, use a rivet driver when bolting, put on a seal (per bolt), a spacer and a spring washer when fixing to plastic tanks with wall thickness over 3 mm, use vendor furnished self-tapping screws and a seal (per self-tapping screw)

<div style="text-align:center;">
[[File:LIGO-SP-fig17-install.png|frameless|663px]]
<div style="font-style:italic; color:#555;">Figure 17. Put sensor into the tank</div>
</div>

* Connect the sensors to an external device using 7m cable

The wire cable color:

'''RS232/RS485:'''

<div style="text-align:center;">
[[File:RS232-RS485.jpg|frameless|756x756px]]
<div style="font-style:italic; color:#555;">Figure 18. Wiring diagram of RS232 and RS485 output signals</div>
</div>

{| class="wikitable" style="text-align:center;"
! Wire Color !! Description
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div> || style="text-align:left;" | GND (Ground) (V-)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div> || style="text-align:left;" | TXD/B-
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div> || style="text-align:left;" | RXD/A+
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div> || style="text-align:left;" | 12-37 VDC or 7.5-75V for SP PRO series
|}

'''AF:'''

<div style="text-align:center;">
[[File:LIGO-SP-fig19-wiring-AF.png|frameless|873px]]
<div style="font-style:italic; color:#555;">Figure 19. Wiring diagram of Analog and Frequency output signals.</div>
</div>

{| class="wikitable" style="text-align:center;"
! Wire Color !! Description
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div> || style="text-align:left;" | GND (Ground) (V-)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div> || style="text-align:left;" | Out (Analog/Frequency)
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div> || style="text-align:left;" | 15-37 VDC or 7.5-75V for SP PRO series
|}

* Connect the fuse holder to LIGO sensor power cable (brown wire) in close vicinity to the vehicle power supply circuit
* Installing the fuse in the fuse holder

'''e) Calibration'''

* Launch Sensor >> load Config >> From Sensor >> Calibration Table

<div style="text-align:center;">
[[File:LIGO-SP-fig20-calib-table.png|frameless|727px]]
<div style="font-style:italic; color:#555;">Figure 20. Calibration table</div>
</div>

* Pump fuel in the tank, the amount of pumped fuel depends on the tank's volume (at least 20 times of pumping)
* After pumping, wait for a while (about 2 minutes) for the output data to be stable, then select "add a row" and insert the actual pumped liters in "liter" box, input the data given by sensor into "Data" box. User can click on the button to sync up data, or read data in the "output" tab as the image below.
* Repeat the above steps until the oil tank is full (Attention: It is recommended to write down the information on the paper to compare with input data and avoid mistaking during the process)
* After completing the above process, select "Volume (liter)'' as the output data.

<div style="text-align:center;">
[[File:LIGO-SP-fig21-param.png|frameless|464px]]
<div style="font-style:italic; color:#555;">Figure 21. Parameter selection</div>
</div>

* Finally, click on the "Sensor" button at the top left corner -> Save config -> To sensor to save data for the sensor.

'''Attention:'''
* The time between each pumping must be at least 2 minutes apart or wait for measured values to be stable, then comes the next pumping.

'''f) Sealing'''

* Install the bolt through a hole in the seal.

<div style="text-align:center;">
[[File:LIGO-SP-fig22-sealing.png|frameless|891px]]
<div style="font-style:italic; color:#555;">Figure 22. Sealing</div>
</div>

==== Quick installation without PC ====

This method is only applicable to configure Min and Max level.

===== Preparation before setting up =====

* The sensor's auto-recognisation mode needs to be turned on by checking the "Enable AutoCalib Feature" box.

<div style="text-align:center;">
[[File:LIGO-SP-fig24-autocalib.png|frameless|865px]]
<div style="font-style:italic; color:#555;">Figure 24. Turning on the auto-recognisation mode before installing</div>
</div>

* External devices such as GPS tracking or Dataloger… must have the software integrated with the configurator. The configuration is performed directly on the device.

===== Automatically setting up and configuring the sensor after cutting =====

* After measuring and cutting sensor, remove iron filings and clean burrs between the tubes, then follow steps below:

'''Step 1:''' Do not allow the sensor to contact oil.

'''Step 2:''' Ensure 12-24VDC stable power supply for the sensor.

'''Step 3:''' Make sure the sensor is under stable condition within 30-60s. The sensor will automatically recognise Min and Max level.

'''Step 4:''' Cut the power and reboot. The sensor now recognizes new configurations.

<div style="text-align:center;">
[[File:LIGO-SP-fig25-auto-config.png|frameless|634px]]
<div style="font-style:italic; color:#555;">Figure 25. Leave the sensor in the air, provide with a stable power supply in 30-60s to configure "Min" level.</div>
</div>

'''Attention:'''

- In case of improper operation and the sensor cannot recognise properly the actual Min, Max level, user should reconfigure using a PC.

==== Connecting multiple sensors together ====

''(Only applicable to RS232 and RS485)''

In some situations, there are oil tanks with specific dimensions, interconnected oil tanks, or oil tanks that are either too long or too large. Using just one sensor to measure the accurate fuel level inside these oil tanks may not be feasible. Hence, there is a need to connect two or more sensors together through a data processor called SUM-DATA.

<div style="text-align:center;">
[[File:LIGO-PRO-multi-sensor-tank.png|frameless|728px]]
<div style="font-style:italic; color:#555;">Figure 26. Oil tank with particular dimensions connecting multiple sensors together</div>
</div>

Connection diagram of the processor SUM-DATA for multiple sensors:

<div style="text-align:center;">
[[File:LIGO-PRO-sumdata-2sensors.png|frameless|648px]]
<div style="font-style:italic; color:#555;">Figure 27: Connecting two sensors by 01 processor SUM-DATA</div>
</div>

<div style="text-align:center;">
[[File:LIGO-PRO-sumdata-multi.png|frameless|707px]]
<div style="font-style:italic; color:#555;">Figure 28: Connecting multiple sensors together by multiple processors SUM-DATA</div>
</div>

== Operation ==

== Troubleshooting ==

== Maintenance ==

== Certification / Compliance ==

Refer to [[LIGO PRO Certification & Approvals]] for current certificate status.''

== Support / Contact ==

{| class="wikitable"
|-
! Channel !! Detail
|-
| Company || SOJI ELECTRONICS.,JSC
|-
| Address || C50-LK13, Lot No. 09, New Urban Area, Le Trong Tan street, Duong Noi Ward, Ha Dong District, Hanoi City, Vietnam
|-
| Tel/Fax || +84 24 62 932 369
|-
| Email || contact@sojielectronics.com
|-
| Website || [http://sojielectronics.com sojielectronics.com]
|}

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO ]]

File:RS232-RS485.jpg

2026-07-07T07:33:03Z

Admin:

up image

File:LIGO-BLE-ADAPTER-Product-overview.png

2026-07-07T07:22:17Z

Admin: Admin moved page File:LIGO-BLE-ADAPTER-Product-overview.png to File:LIGO-AIR-ADAPTER-Product-overview.png

#REDIRECT [[File:LIGO-AIR-ADAPTER-Product-overview.png]]

File:LIGO-AIR-ADAPTER-Product-overview.png

2026-07-07T07:22:17Z

Admin: Admin moved page File:LIGO-BLE-ADAPTER-Product-overview.png to File:LIGO-AIR-ADAPTER-Product-overview.png

MediaWiki:Common.js

2026-07-07T07:18:55Z

Admin: Update

LIGO PRO 2 User Guide

2026-07-07T06:51:51Z

Admin: change image

LIGO AIR ADAPTER User Guide

2026-07-06T00:47:43Z

Admin: change content

== Safety Information ==
{{Notice
| title = Important notes during sensor installation
| body = Read and understand all safety information in this document before installing, operating or servicing the LIGO AIR ADAPTER
*Keep the device out of the reach of children. It is not a toy and contains small parts.
*Do not modify, drill or otherwise alter the device.
*Always '''disconnect power''' before wiring, connecting/disconnecting cables or servicing.
*Connect the device only to a power source within the rated input voltage.
}}

== Product Overview ==

=== Scope ===

This document provides instructions for installation, configuration, operation, and basic troubleshooting of the LIGO AIR ADAPTER.

It is intended for system integrators, installers, and technical personnel involved in fuel monitoring and GPS telematics systems.

=== Product Overview ===

LIGO AIR ADAPTER is a communication and aggregation product designed to connect Ligo Air/Ligo Air Pro wireless fuel level sensors to GPS trackers that do not support BLE communication.

The device acts as:
* A BLE to wired protocol bridge.
* A Sensor Union Module (SUM) capable of aggregating data from multiple sensors.
* A BLE signal receiver with enhanced sensitivity for extended wireless range.

LIGO AIR ADAPTER supports multiple output interfaces including RS232, RS485, and AF, ensuring compatibility with a wide range of GPS tracking devices.

=== Wiring diagram ===
<div style="text-align:center;">
[[File:System architecture1.png|frameless|1150px]]
<div style="font-style:italic; color:#555;">Figure 1. LIGO AIR ADAPTER — Wiring diagram</div>
</div>
* Wireless fuel sensors (Ligo Air / Ligo Air Pro) transmit fuel level data via BLE.
* LIGO AIR ADAPTER receives BLE data and processes it.
* Processed data is transmitted to the GPS tracker via RS232, RS485 or AF interface.
* Log sensor data for history view and troubleshooting.

== Package Contents ==
{| class="wikitable"
|+ Table 1. LIGO AIR ADAPTER — Package content
!No.
!Description
!Qty (pcs)
|-
|1
|LIGO AIR ADAPTER
|01
|-
|2
|Quick user guide
|01
|}

== Specifications ==
{| class="wikitable" style="text-align:center;"
|+ Table 2. LIGO AIR ADAPTER — Detail specifications
| valign="top" |'''No.'''
| valign="top" |'''PARAMETERS'''
| valign="top" |'''RS232'''
| valign="top" |'''RS485'''
| valign="top" |'''PRO'''
| valign="top" |'''AF'''
|-
| valign="top" |1
| valign="top" style="text-align:left;" |Dimension (without wire), mm
| colspan="4" valign="top" |67x80
|-
| valign="top" |2
| valign="top" style="text-align:left;" |Output interface
| colspan="2" valign="top" |Digital
| valign="top" |Analog & Digital
| valign="top" |Analog
|-
| valign="top" |3
| valign="top" style="text-align:left;" |Baud rate, bit/sec
| colspan="3" valign="top" |2400, 4800, 9600, 14400, 19200, 38400, 115200.
| valign="top" |
|-
| valign="top" |4
| valign="top" style="text-align:left;" |Power supply, VDC
| colspan="4" valign="top" |7 – 36 VDC
|-
| valign="top" |5
| valign="top" style="text-align:left;" |Maximum power consumption
| colspan="4" valign="top" |~15 mA @13.5VDC
|-
| valign="top" |6
| valign="top" style="text-align:left;" |Power supply protection
| colspan="4" valign="top" |1000VDC reverse polarity protection
|-
| valign="top" |7
| valign="top" style="text-align:left;" |Operating temperature, °C
| colspan="4" valign="top" |-40 to 85 °C
|-
| valign="top" |8
| valign="top" style="text-align:left;" |Waterproof standard
| colspan="4" valign="top" |IP67
|-
| valign="top" |9
| valign="top" style="text-align:left;" |Output value range
| colspan="2" valign="top" |Digital
| valign="top" |Digital and analog

| valign="top" |Analog (0-10V)
|-
| valign="top" |10
| valign="top" style="text-align:left;" |Data output mode
| colspan="4" valign="top" |SUM, AVERAGE, INDIVIDUAL
|-
| valign="top" |11
| valign="top" style="text-align:left;" |Bluetooth specs
| colspan="4" valign="top" |BLE 5.2
|-
| valign="top" |12
| valign="top" style="text-align:left;" |Average service life, years (expected)
| colspan="4" valign="top" |8 years
|}

== Installation ==

=== Hardware description and installation ===

==== Cable and wire definition ====

{| class="wikitable" style="text-align:center;"
|+ Table 3. LIGO AIR ADAPTER — Cable description
! No. !! Wire Color !! Wire Name !! Description
|-
| 1 || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f00;border:1px solid #999;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">RED</span></div>|| '''VCC'''|| style="text-align:left;" | Power supply (7–36 V DC)
|-
| 2 || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#fff;border:1px solid #999;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">WHITE</span></div>|| '''AF'''|| style="text-align:left;" | Analog output (0–10 V)
|-
| 3 || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">BLACK</span></div>|| '''GND'''|| style="text-align:left;" | Ground
|-
| 4 || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#2e8b2e;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">GREEN</span></div>|| '''RS485-B'''|| style="text-align:left;" | Signal wire B for RS485
|-
| 5 || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">YELLOW</span></div>|| '''RS485-A'''|| style="text-align:left;" | Signal wire A for RS485
|-
| 6 || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">BLACK</span></div>|| '''GND'''|| style="text-align:left;" | Ground
|-
| 7 || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#7b3f00;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">BROWN</span></div>|| '''RS232-RX'''|| style="text-align:left;" | Input data for RS232
|-
| 8 || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#1e6cff;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">BLUE</span></div> || '''RS232-TX''' || style="text-align:left;" | Output data for RS232
|}

==== Mechanical installation ====

* Install Ligo Adapter inside the vehicle cabin or protected enclosure
* Avoid direct exposure to water, excessive heat, or strong electromagnetic sources
* Ensure sufficient distance from high-current cables when possible

==== Electrical connection ====
Connect the selected communication interface to the GPS tracker following the table below:

{| class="wikitable" style="text-align:center;"
|+ Table 4. LIGO AIR ADAPTER — Wiring connection
! No. !! Wire Name !! RS232 !! RS485 !! AF !! PRO
|-
| 1 || '''VCC''' || ✓ || ✓ || ✓ || ✓
|-
| 2 || '''AF''' || — || — || ✓ || ✓
|-
| 3 || '''GND''' || ✓ || ✓ || ✓ || ✓
|-
| 4 || '''RS485-B''' || — || ✓ || — || ✓
|-
| 5 || '''RS485-A''' || — || ✓ || — || ✓
|-
| 6 || '''GND''' || ✓ || ✓ || ✓ || ✓
|-
| 7 || '''RS232-RX''' || ✓ || — || — || ✓
|-
| 8 || '''RS232-TX''' || ✓ || — || — || ✓
|}

{{Notice
| title = Output Protocol Compatibility — RS232 / RS485 / AF
| body = The PRO model supports all available output communication protocols (RS232, RS485 and AF). Select the output interface compatible with the existing GPS tracker.
}}

=== LED Status Indication ===

The Ligo Adapter is equipped with a status LED to indicate its current operating state.

{| class="wikitable"
|+ Table 5. LIGO AIR ADAPTER — LED status
! LED Status !! Description
|-
| style="text-align:center;" | Red blinking || No sensor is paired with the adapter
|-
| style="text-align:center;" | Red solid || Sensor(s) paired, but no data is being received
|-
| style="text-align:center;" | Green solid || Valid data is being received from paired sensor(s)
|}

== Configuration ==

=== Software configuration ===

LIGO AIR ADAPTER is configured using Ligo BLE Configurator. Please download and install it from Play Store on android OS or App Store on IOS before starting configurations.

The software is structured into three main sections, each serving a specific purpose in the installation, operation and troubleshooting as these below figures.

<gallery mode="packed" widths="250" heights="500">
File:LIGO-BLE-Adapter-fig2-connection-section.png|Figure 2. Connection section
File:LIGO-BLE-Adapter-fig3-settings-section.png|Figure 3. Settings section
File:LIGO-BLE-Adapter-fig4-help-section.png|Figure 4. Help section
</gallery>

<div style="display:flex; gap:30px; flex-wrap:wrap; align-items:flex-start;">

<div style="flex:1; min-width:260px;">
<div style="font-size:1.2em; font-weight:bold; color:#0054A6; border-bottom:2px solid #eaecf0; padding-bottom:5px; margin-bottom:10px;">Connection section</div>
This section provides general information and real-time status of the device. It allows users to quickly verify that the adapter is powered, accessible, and ready for configuration.

'''Included information:'''
* Device name
* Device MAC address and serial number
* Firmware / Hardware version
* Fuel data of paired sensors
* Supply voltage and temperature
* RSSI signal

The Connection section allows users to quickly verify that the adapter is powered, accessible, and ready for configuration.
</div>

<div style="flex:1; min-width:260px;">
<div style="font-size:1.2em; font-weight:bold; color:#0054A6; border-bottom:2px solid #eaecf0; padding-bottom:5px; margin-bottom:10px;">Settings section</div>
The Settings section contains all configuration parameters related to sensor pairing, output interfaces, and data type. It is intended for device setup and integration with GPS tracking devices.

'''Key configuration functions:'''
* Sensor pairing management (add / remove sensors using MAC address)
* Output interface configuration (RS232, RS485, AF)
* Communication protocol
* Data mode selection (SUM, AVERAGE, INDIVIDUAL)
* Data log configuration and viewing
* Installation report generation
</div>

<div style="flex:1; min-width:260px;">
<div style="font-size:1.2em; font-weight:bold; color:#0054A6; border-bottom:2px solid #eaecf0; padding-bottom:5px; margin-bottom:10px;">Help section</div>
The Support section provides technical assistance and software information.

This section includes:
* Software version
* Technical support contact information
* Reference documentation and troubleshooting resources

This section ensures that users can easily access assistance if necessary.
</div>

</div>
=== Sensor pairing and configuration ===

==== Sensor pairing ====

Follow these steps to pair Ligo Air/Ligo Air Pro sensors with LIGO AIR ADAPTER

* Launch Ligo BLE Configurator application > Select LIGO AIR ADAPTER (the software auto scan nearby BLE Adapter) > press Connect button
* Switch to Settings section to start pairing sensor to the LIGO AIR ADAPTER as Figure 4.

<gallery mode="packed" widths="250" heights="500">
File:LIGO-Adapter-config-select-device.png|Step 1. Select device
File:LIGO-Adapter-config-scan-sensor.png|Step 2. Scan sensors
File:LIGO-Adapter-config-confirm-pairing.png|Step 3. Confirm pairing
</gallery>

==== Parameters configuration ====

<gallery mode="packed" widths="250" heights="500">
File:LIGO-Adapter-parameter-1.png|Parameters - page 1
File:LIGO-Adapter-parameter-2.png|Parameters - page 2
</gallery>

{| class="wikitable"
|-
! No. !! Parameter !! Description
|-
| style="text-align:center;" | 1 || Message interval (1..60s) || Defines the time interval between two consecutive data transmissions from the LIGO AIR ADAPTER
|-
| style="text-align:center;" | 2 || Protocol || Selects the output communication protocol used to transmit fuel data to the GPS tracker.
* SOJI protocol
* LLS protocol
|+ Table 6. LIGO AIR ADAPTER — Parameter descriptions
| style="text-align:center;" | 3 || Automatic transmission mode || Defines the data transmission format.
* HEX format
* ASCII format
|-
| style="text-align:center;" | 4 || Baud rate || Sets the serial communication speed for RS232 or RS485 output.
|-
| style="text-align:center;" | 5 || Data mode || Defines how fuel data from multiple paired sensors is processed before transmission.
* SUM: Total fuel value of all paired sensors
* AVERAGE: Average fuel value of all paired sensors
* INDIVIDUAL: Fuel data from each sensor is transmitted individually upon Modbus request.
|-
| style="text-align:center;" | 6 || Address (1-254) || Sets the Modbus address of the LIGO AIR ADAPTER.
|-
| style="text-align:center;" | 7 || Level min (0..8V) || Defines the minimum output voltage level for the AF output.
|-
| style="text-align:center;" | 8 || Level max (2..10V) || Defines the maximum output voltage level for the AF output.
|-
| style="text-align:center;" | 9 || Max volume || Defines the maximum digital fuel level resolution used for data transmission.
* 1023: 10-bit resolution.
* 4095: 12-bit resolution.
|}

== Operation ==

=== Data log and settings log ===

==== Data log ====

<gallery mode="packed" widths="250" heights="500">
File:LIGO-Adapter-open-log.png|Step 1. Open log
File:LIGO-Adapter-select-period.png|Step 2. Select period
File:LIGO-Adapter-view-data.png|Step 3. View data
</gallery>

The Data Log function allows users to view historical fuel level data received from paired sensors over time.

The log records:
* Timestamp of received data
* Fuel level values from paired sensors
* RSSI signal
* Temperature of sensor

This function is used for:
* System verification during installation
* Diagnostic and troubleshooting purposes
* Validation of sensor communication stability

The user can select a time period (Today, Yesterday, Week, Month, or a Custom Period) and then press the Download button to retrieve the data log, as shown in Figure 6.

The retrieved data log is displayed in the Log Display Area.

==== Settings log ====

<gallery mode="packed" widths="250" heights="500">
File:LIGO-Adapter-open-setting-log.png|Step 1. Open settings log
File:LIGO-Adapter-select-source.png|Step 2. Select source
File:LIGO-Adapter-view-setting-log.png|Step 3. View log
</gallery>

The Settings Log function allows users to review the historical configuration records of the LIGO AIR ADAPTER.

This log stores all parameter changes previously configured by the user, enabling traceability and verification of device setup.

The user can select the Log source (data from EEPROM or data on the server), and the settings log will be displayed in the Log Display Area, as shown in Figure 7.

==== Report ====

<div style="display:flex; gap:30px; align-items:flex-start; flex-wrap:wrap;">
<div style="flex:1; min-width:280px;">
<div style="font-size:1.1em; font-weight:bold; color:#0054A6;">Installation Report</div>
Each installation report includes:
*Installer Name
*Installation Date and Time
*Serial Number of Adapter (SN)
*Model: Vehicle Information
*Plate number: License of vehicle
*Other information
*Real installation photos captured via mobile device
</div>
<div>
<div style="text-align:center;">
[[File:install-report.png|frameless|284px]]
<div style="font-style:italic; color:#555;">Figure 9. Installation report</div>
</div>
</div>
</div>

<div style="display:flex; gap:30px; align-items:flex-start; flex-wrap:wrap;">
<div style="flex:1; min-width:280px;">
<div style="font-size:1.1em; font-weight:bold; color:#0054A6;">Maintenance Report</div>
Each maintenance report includes:
*Installer Name
*Maintenance Date and Time
*Serial Number of Adapter (SN)
*Model: Vehicle Information
*Plate number: License of vehicle
*Other information
*Real installation photos captured via mobile device
</div>
<div>
<div style="text-align:center;">
[[File:maintance-report.png|frameless|284px]]
<div style="font-style:italic; color:#555;">Figure 10. Maintenance report</div>
</div>
</div>
</div>

<div style="display:flex; gap:30px; align-items:flex-start; flex-wrap:wrap;">
<div style="flex:1; min-width:280px;">
<div style="font-size:1.1em; font-weight:bold; color:#0054A6;">View Report</div>
The View Report function allows users to review installation and maintenance history at any time.

Steps to open reports:

* '''Open View Report''' in the Ligo BLE Configurator App.
* '''Enter the Adapter Serial Number (SN)''' and press the Search button.

The system displays:
*Installation reports
*Maintenance reports
</div>
<div>
<div style="text-align:center;">
[[File:view-report.png|frameless|284px]]
<div style="font-style:italic; color:#555;">Figure 11. View report</div>
</div>
</div>
</div>

== Troubleshooting ==

{| class="wikitable"
|+ Table 7. LIGO AIR ADAPTER — Troubleshooting
! Issue !! Possible Cause !! Recommended Action
|-
| No data on GPS || Incorrect wiring || Verify interface wiring
|-
| Sensor not detected || MAC address not added, wrong MAC address || Reconfigure sensor list
|-
| Unstable data || BLE signal attenuation || Reposition adapter
|-
| Incorrect fuel value || Wrong data mode || Check SUM / AVERAGE setting
|}

== Certification / Compliance ==

Refer to [[LIGO AIR ADAPTER Certification & Approvals]] for current certificate status.''

== Support / Contact ==

{| class="wikitable"
|+ Table 9. LIGO AIR ADAPTER — Support/ Contact
! Channel !! Detail
|-
| Company || SOJI ELECTRONICS.,JSC
|-
| Address || C50-LK13, Lot No. 09, New Urban Area, Le Trong Tan street, Duong Noi Ward, Ha Dong District, Hanoi City, Vietnam
|-
| Tel/Fax || +84 24 62 932 369
|-
| Email || contact@sojielectronics.com
|-
| Website || [http://sojielectronics.com sojielectronics.com]
|}

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ADAPTER ]]

LIGO AIR ADAPTER Datasheet

2026-07-06T00:44:30Z

Admin: change Image

== Product Overview ==
'''Ligo BLE Adapter''' is an intelligent communication and integration module designed to enable seamless connectivity between '''wireless fuel level sensors (BLE)''' and '''GPS/telematics devices that do not natively support BLE communication'''.

Acting as a protocol bridge, Ligo Adapter allows existing GPS systems to integrate wireless fuel sensors without hardware modification or replacement, significantly reducing deployment and upgrading costs while enhancing system flexibility.

In addition to protocol conversion, Ligo Adapter functions as a '''SUM Data''', capable of simultaneously connecting to '''10 wireless fuel sensors''' and aggregating their data for transmission to the GPS device via standard wired interfaces such as '''RS232, RS485, and Analog/Frequency (AF).'''

To ensure reliable wireless performance in challenging environments, Ligo Adapter incorporates a '''BLE receive-path signal amplification mechanism''', improving receiver sensitivity and extending the effective communication range of wireless fuel sensors. This feature is particularly beneficial in environments with high attenuation or electromagnetic interference, such as vehicle cabins, metal fuel tanks, and industrial machinery.

== Key Features ==

* '''Protocol''' '''bridge for Non-BLE GPS/Telematics''': Enables seamless connectivity between '''wireless BLE fuel level sensors''' and '''GPS/telematics devices that do not natively support BLE'''.
* '''Multi-Sensor''' '''data hub (up to 10 Sensors)''': Connecting to up to '''10 wireless fuel sensors simultaneously.'''
* '''Standard wired output interfaces:''' Transmits aggregated sensor data to the GPS/telematics device via standard wired interfaces '''RS232, RS485, AF.'''
* '''BLE receive-path signal amplification:''' Incorporates a '''BLE receive-path signal amplification''' mechanism that improves '''receiver sensitivity''' and '''extends the effective communication range''' of wireless fuel sensors.

== Applications ==

Ligo Adapter is developed to achieve the following objectives:

* Allows GPS and telematics units without BLE capability to communicate with wireless fuel level sensors.
* Support multiple wired communication interfaces. Ensures broad compatibility with a wide range of GPS devices through RS232, RS485, and AF interfaces.
* Aggregate data from multiple sensors (SUM function). Supports simultaneous connection of up to 10 fuel level sensors, consolidating sensor data into a single communication channel to the GPS unit.
* Extend BLE communication range and reliability. Enhances BLE reception through signal amplification, improving data stability and transmission distance in high-loss or noisy environments.

== Product Variants / Ordering Information ==

== Technical Specifications ==

{| class="wikitable" style="text-align:center;"
|-
! No. !! Parameters !! RS232 !! RS485 !! PRO !! AF
|-
| 1 || style="text-align:left;" | Dimention (without wire), mm || 67x80
|67x80
|67x80
|67x80
|-
| 2 || style="text-align:left;" | Output interface || Digital
|Digital|| Analog & Digital || Analog
|-
| 3 || style="text-align:left;" | Baud rate, bit/sec || 2400–115200
|2400–115200
|2400–115200||2400–115200
|-
| 4 || style="text-align:left;" | Power supply, VDC || 7–36 VDC
|7–36 VDC
|7–36 VDC
|7–36 VDC
|-
| 5 || style="text-align:left;" | Maximum power consumption || ~15mA @13.5V
|~15mA @13.5V
|~15mA @13.5V
|~15mA @13.5V
|-
| 6 || style="text-align:left;" | Power supply protection || 1000VDC reverse polarity|| 1000VDC reverse polarity|| 1000VDC reverse polarity||1000VDC reverse polarity
|-
| 7 || style="text-align:left;" | Operating temperature, °C || -40 to 85°C|| -40 to 85°C|| -40 to 85°C||-40 to 85°C
|-
| 8 || style="text-align:left;" | Waterproof standard || IP67|| IP67|| IP67||IP67
|-
| 9 || style="text-align:left;" | Output signal type || Digital
|Digital|| Digital & Analog || Analog (0-10V)
|-
| 10 || style="text-align:left;" | Data output mode || SUM / AVG / Individual
|SUM / AVG / Individual
|SUM / AVG / Individual
|SUM / AVG
|-
| 11 || style="text-align:left;" | Bluetooth specs || BLE 5.2|| BLE 5.2|| BLE 5.2||BLE 5.2
|-
| 12 || style="text-align:left;" | Average service life, years (expected) || 8 years|| 8 years|| 8 years||8 years
|}

=== Wiring Description ===

<div style="text-align:center;">
[[File:Phương tiện truyền thông (15).jpg|frameless|466x466px]]
<div style="font-style:italic; color:#555;">Figure 1. Wiring diagram of Ligo BLE Adapter</div>
</div>

{| class="wikitable" style="text-align:center;"
|-
! Color !! Function !! Description
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f00;border:1px solid #999;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">RED</span></div> || VBAT || style="text-align:left;" | 7 - 36VDC
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#fff;border:1px solid #999;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">WHITE</span></div> || AF || style="text-align:left;" | Analog output
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">BLACK</span></div> || GND || style="text-align:left;" | GND
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#2e8b2e;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">GREEN</span></div> || RS485-B || style="text-align:left;" | RS485-B
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">YELLOW</span></div> || RS485-A || style="text-align:left;" | RS485-A
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">BLACK</span></div> || GND || style="text-align:left;" | GND
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#7b3f00;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">BROWN</span></div> || RS232-Rx || style="text-align:left;" | RS232-Rx
|-
| <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#1e6cff;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">BLUE</span></div>|| RS232-Tx || style="text-align:left;" | RS232-Tx
|}

== Compliance and Certifications ==

Refer to [[LIGO BLE ADAPTER Certification & Approvals]] for current certificate status.''

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ADAPTER ]]

File:Phương tiện truyền thông (15).jpg

2026-07-06T00:43:26Z

Admin:

upload

LIGO PRO 2 Protocol

2026-06-30T11:56:29Z

Admin: change content

== General Introduction ==

LLS Protocol is used in LIGO RS232 / RS485 fuel level sensor with the following parameters:

* Baud rate: 2400,4800,9600,19200,38400,115200 (can be configured by software on PC or via LIGO BLE Configurator application on mobile phone)
* Data bits: 8
* Parity: None
* Stop bits: 1
* Flow control: None

LIGO fuel level sensor has 2 working modes:

# '''Slave mode:''' In this mode, the sensor will respond to all requests from the external device (master device). Each sensor in the network will be distinguished by different addresses configured with the LIGO Configurator software
# '''Master mode:''' In this mode the sensor will automatically send data to the external device with a preset interval (message interval)

To enable this mode on the LIGO Configurator software, do the following:

* Automatic transmission: select HEX (binary) or ASCII or ASCII EXT

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Automatic-Transmission.png|frameless|219px]]
<div style="font-style:italic; color:#555;">Automatic transmission setting in LIGO Configurator</div>
</div>

* Set the time of each transfer (Message interval)

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Message-Interval.png|frameless|228px]]
<div style="font-style:italic; color:#555;">Message interval setting in LIGO Configurator</div>
</div>

== Exchange Protocol Description ==

The LLS protocol supports two types of exchange protocols: binary (HEX) and character view (transmission of ASCII sequences). It is recommended to use binary exchange protocol.

=== Format of Binary Protocol Messages ===

All the commands of the binary communication protocol have the same standardized format which is given in the table:

{| class="wikitable"
|-
! Sequential number of the field !! Field name !! Field size, byte !! Description
|-
| style="text-align:center;" | 1 || Prefix || style="text-align:center;" | 1 || The field is a marker of the message beginning shall have prefix 31h, and an outcoming messages shall be displayed with 3Eh prefix by the program.
|-
| style="text-align:center;" | 2 || Network address || style="text-align:center;" | 1 || For prefix 31h specify the network address of the recipient. <br>For prefix 3Eh specify the network address of the sender.
|-
| style="text-align:center;" | 3 || Operation code || style="text-align:center;" | 1 || For prefix 31h specify the code of operation which the program shall perform For Eh prefix specify the code of operation to which the response is given
|-
| style="text-align:center;" | 4 || Data || style="text-align:center;" | It depends on the operation code || Data composition and format of the field depends on the operation code
|-
| style="text-align:center;" | 5 || Checksum || style="text-align:center;" | 1 || The field is used to control over data integrity
|}

=== Single-Stage Data Reading (command 06h) ===

The command is designed for reading of the current data: relative level, temperature, frequency. The data are transmitted with a lower byte ahead.

==== Command format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | The checksum
|}

==== Response format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output (command 07h) ===

Command is designed to switch on periodic data output.

After the command is processed, the sensor starts sending data periodically — level, temperature, and frequency — with the time interval prescribed by the 13h command.

Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power power supply (if the data output mode is not istalled by default).

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Periodic data output format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output Interval Adjustment (13h command) ===

Command is designed to set up interval of periodic data output.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 0…255 || style="text-align:left;" | Interval of the data output in seconds
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Default Data Output Mode (command 17h) ===

This command determines the order of data output after the sensor is powered on or the processor is reset. After the power is on or the processor is reset, the program will send data periodically via the interface at the time interval prescribed by the 13h command.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="4" | +3 || rowspan="4" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The data are output in binary form
|-
| 02h || style="text-align:left;" | The data are output in character-coded form (ASCII mode)
|-
| 03h || style="text-align:left;" | The data are output in character-coded form (ASCII EXT mode)
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h…FFh || style="text-align:left;" | Checksum
|}

== Description of Commands for the Text-Based Protocol ==

Data exchange via the text-based protocol includes receipt and sending of ASCII symbols sequence interpreted and the request and response commands.

=== Reading the Data ===

The command is designed for reading of the current data: relative level, temperature, frequency. The command is a sequence of symbols ASCII "D" and "O". After receipt of the "DO" command the program will response in the form of ASCII symbols sequence.

For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. All values are in hexadecimal form.

In case the frequency value exceeds FFFh, the data are considered invalid.

=== Periodic Data Output ===

The command is designed to switch on periodic data output. After processing the command, the sensor performs periodic data output in the text-based form (ASCII codes) of the following data: relative level, temperature, frequency.

The data are being output periodically with an interval set up when cofiguring the sensor (LIGO Configurator software). In case the data output interval is set to zero, the data output won't be performed.

Switching on of the periodic data output is done by sending of the "DP" symbols in line. After processing of the command, the symbols line will be received. For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power supply.

== Checksum Calculation Algorithm ==

The checksum is calculated using Dallas APPLICATION NOTE 27 table method: ''Understanding and Using Cyclic Redundancy Checks with Dallas Semiconductor iButton Products''. One can use the following algorithms to calculate the checksum with a polynom <code>x^8 + x^5 + x^4 + 1</code> (C language):

<syntaxhighlight lang="c" line>
U8 CRC8(U8 data, U8 crc)
{
U8 i = data ^ crc;
crc = 0;
if (i & 0x01) crc ^= 0x5e;
if (i & 0x02) crc ^= 0xbc;
if (i & 0x04) crc ^= 0x61;
if (i & 0x08) crc ^= 0xc2;
if (i & 0x10) crc ^= 0x9d;
if (i & 0x20) crc ^= 0x23;
if (i & 0x40) crc ^= 0x46;
if (i & 0x80) crc ^= 0x8c;
return crc;
}
</syntaxhighlight>

== Modbus RTU Register Mapping ==

The SOJI sensor is capable of communication via the RS-485 serial bus in the Modbus/RTU protocol. The sensor supports the Modbus function 03 – Read Holding Registers
{| class="wikitable" style="text-align:center;"
|-
! No !! Address
|'''Type'''
|'''Description'''
|'''Unit'''
|-
| 1 || 0x00
|U16
|Sensor address (slave ID)
| style="text-align:left;" |–
|-
| 2 || 0x01
|U16
|Min calibration (Cmin) – '''Low word'''
| style="text-align:left;" |–
|-
| 3 ||0x02
|U16
|Min calibration (Cmin) – '''High word'''
| style="text-align:left;" |–
|-
| 4
|0x03
|U16
|Fuel level data (12-bit / mm / liter)
| style="text-align:left;" |raw / mm / L
|-
|5
|0x04
|U16
|Temperature
| style="text-align:left;" |°C
|-
|6
|0x05
|U16
|Reserved
| style="text-align:left;" |–
|-
|7
|0x06
|U16
|Reserved
| style="text-align:left;" |–
|-
| 8 ||0x07
|U16
|Max calibration (Cmax) – '''Low word'''
| style="text-align:left;" |–
|-
|9
|0x08
|U16
|Max calibration (Cmax) – '''High word'''
| style="text-align: left;" |–
|-
|10
|0x09
|U16
|Sensor height (actual height, set via app)
| style="text-align: left;" |mm
|-
|11
|0x0A
|U16
|OSC current
| style="text-align: left;" |–
|-
|12
|0x0B
|U16
|OSC current
| style="text-align: left;" |–
|}
'''Detailed register description'''

'''🔹''' '''0x00 — Sensor address'''

The slave address of the sensor. The master uses this value as the address byte in the request frame.

'''🔹''' '''0x01 + 0x02 — Min calibration (Cmin) (32-bit)'''

The '''minimum''' calibration value is a 32-bit value split across two 16-bit registers:

* 0x01 = '''Low word''' (lower 16 bits)
* 0x02 = '''High word''' (upper 16 bits)

'''Combination formula:'''

Cmin = (RegHigh << 16) | RegLow

'''🔹''' '''0x07 + 0x08 — Max calibration (Cmax) (32-bit)'''

Same scheme as min, this is the '''maximum''' calibration value:

* 0x07 = Low word
* 0x08 = High word

Together, the min/max pairs define the '''calibration range''' of the capacitive sensor:

* '''Empty''' tank ↔ Cmin
* '''Full''' tank ↔ Cmax

'''🔹''' '''0x03 — Fuel level data'''

This register has '''3 output modes''', selectable by the user through the '''mobile configuration app:'''
{| class="wikitable"
|'''Mode'''
|'''Value range'''
|'''Meaning'''
|'''Conversion'''
|-
|'''Raw (12-bit)'''
|0 – 4095
|Raw value
|0 = empty, 4095 = full (per min/max calibration)
|-
|'''mm (height)'''
|0 – (Sensor_height × 10)
|Fuel level height by actual height
|Actual level (mm) = Value / 10
|-
|'''3. Liter (volume)'''
|0 – Vmax
|Fuel volume
|Per the calibration table/factor configured in the app
|}
'''Raw mode example:'''

Reg = 2048 → 2048 / 4095 ≈ 50% of full scale

'''mm mode example''' (output = Fuel level height × 10):

Reg = 3500 → Fuel level height = 3500 / 10 = 350.0 mm

'''Liter mode example:''' depends on tank geometry + the calibration chart the user enters in the app, e.g. Reg = 80 → 80 liters.

'''🔹''' '''0x04 — Temperature'''

Temperature measured at the sensor (°C).

'''Example:''' Reg = 25 → 25 °C.

'''🔹 0x09 — Sensor height (actual probe height)'''

The physical height of the sensor probe, '''set by the user via the app'''.

'''Example:'''

Reg = 5000 → Sensor height = 5000/10 = 500 mm

'''🔹''' '''0x0A + 0x0B — OSC current'''

Oscillator current/parameter.

'''🔹''' '''0x05, 0x06 — Reserved'''

Reserved for future expansion, currently unused.<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO 2]]

LIGO PRO BLE Protocol

2026-06-30T11:54:30Z

Admin: change content

== General Introduction ==

LLS Protocol is used in LIGO RS232 / RS485 fuel level sensor with the following parameters:

* Baud rate: 2400,4800,9600,19200,38400,115200 (can be configured by software on PC)
* Data bits: 8
* Parity: None
* Stop bits: 1
* Flow control: None

LIGO fuel level sensor has 2 working modes:

# '''Slave mode:''' In this mode, the sensor will respond to all requests from the external device (master device). Each sensor in the network will be distinguished by different addresses configured with the LIGO Configurator software
# '''Master mode:''' In this mode the sensor will automatically send data to the external device with a preset interval (message interval)

To enable this mode on the LIGO Configurator software, do the following:

* Automatic transmission: select HEX (binary) or ASCII or ASCII EXT

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Automatic-Transmission.png|frameless|219px]]
<div style="font-style:italic; color:#555;">Automatic transmission setting in LIGO Configurator</div>
</div>

* Set the time of each transfer (Message interval)

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Message-Interval.png|frameless|228px]]
<div style="font-style:italic; color:#555;">Message interval setting in LIGO Configurator</div>
</div>

== Exchange Protocol Description ==

The LLS protocol supports two types of exchange protocols: binary (HEX) and character view (transmission of ASCII sequences). It is recommended to use binary exchange protocol.

=== Format of Binary Protocol Messages ===

All the commands of the binary communication protocol have the same standardized format which is given in the table:

{| class="wikitable"
|-
! Sequential number of the field !! Field name !! Field size, byte !! Description
|-
| style="text-align:center;" | 1 || Prefix || style="text-align:center;" | 1 || The field is a marker of the message beginning shall have prefix 31h, and an outcoming messages shall be displayed with 3Eh prefix by the program.
|-
| style="text-align:center;" | 2 || Network address || style="text-align:center;" | 1 || For prefix 31h specify the network address of the recipient. <br>For prefix 3Eh specify the network address of the sender.
|-
| style="text-align:center;" | 3 || Operation code || style="text-align:center;" | 1 || For prefix 31h specify the code of operation which the program shall perform For Eh prefix specify the code of operation to which the response is given
|-
| style="text-align:center;" | 4 || Data || style="text-align:center;" | It depends on the operation code || Data composition and format of the field depends on the operation code
|-
| style="text-align:center;" | 5 || Checksum || style="text-align:center;" | 1 || The field is used to control over data integrity
|}

=== Single-Stage Data Reading (command 06h) ===

The command is designed for reading of the current data: relative level, temperature, frequency. The data are transmitted with a lower byte ahead.

==== Command format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | The checksum
|}

==== Response format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output (command 07h) ===

Command is designed to switch on periodic data output.

After the command is processed, the sensor starts sending data periodically — level, temperature, and frequency — with the time interval prescribed by the 13h command.

Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power power supply (if the data output mode is not istalled by default).

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Periodic data output format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output Interval Adjustment (13h command) ===

Command is designed to set up interval of periodic data output.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 0…255 || style="text-align:left;" | Interval of the data output in seconds
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Default Data Output Mode (command 17h) ===

This command determines the order of data output after the sensor is powered on or the processor is reset. After the power is on or the processor is reset, the program will send data periodically via the interface at the time interval prescribed by the 13h command.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="4" | +3 || rowspan="4" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The data are output in binary form
|-
| 02h || style="text-align:left;" | The data are output in character-coded form (ASCII mode)
|-
| 03h || style="text-align:left;" | The data are output in character-coded form (ASCII EXT mode)
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h…FFh || style="text-align:left;" | Checksum
|}

== Description of Commands for the Text-Based Protocol ==

Data exchange via the text-based protocol includes receipt and sending of ASCII symbols sequence interpreted and the request and response commands.

=== Reading the Data ===

The command is designed for reading of the current data: relative level, temperature, frequency. The command is a sequence of symbols ASCII "D" and "O". After receipt of the "DO" command the program will response in the form of ASCII symbols sequence.

For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. All values are in hexadecimal form.

In case the frequency value exceeds FFFh, the data are considered invalid.

=== Periodic Data Output ===

The command is designed to switch on periodic data output. After processing the command, the sensor performs periodic data output in the text-based form (ASCII codes) of the following data: relative level, temperature, frequency.

The data are being output periodically with an interval set up when cofiguring the sensor (LIGO Configurator software). In case the data output interval is set to zero, the data output won't be performed.

Switching on of the periodic data output is done by sending of the "DP" symbols in line. After processing of the command, the symbols line will be received. For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power supply.

== Checksum Calculation Algorithm ==

The checksum is calculated using Dallas APPLICATION NOTE 27 table method: ''Understanding and Using Cyclic Redundancy Checks with Dallas Semiconductor iButton Products''. One can use the following algorithms to calculate the checksum with a polynom <code>x^8 + x^5 + x^4 + 1</code> (C language):

<syntaxhighlight lang="c" line>
U8 CRC8(U8 data, U8 crc)
{
U8 i = data ^ crc;
crc = 0;
if (i & 0x01) crc ^= 0x5e;
if (i & 0x02) crc ^= 0xbc;
if (i & 0x04) crc ^= 0x61;
if (i & 0x08) crc ^= 0xc2;
if (i & 0x10) crc ^= 0x9d;
if (i & 0x20) crc ^= 0x23;
if (i & 0x40) crc ^= 0x46;
if (i & 0x80) crc ^= 0x8c;
return crc;
}
</syntaxhighlight>

== Modbus RTU Register Mapping ==
The SOJI sensor is capable of communication via the RS-485 serial bus in the Modbus/RTU protocol. The sensor supports the Modbus function 03 – Read Holding Registers
{| class="wikitable"
!No
!Address
|'''Type'''
|'''Description'''
|'''Unit'''
|-
|1
|0x00
|U16
|Sensor address (slave ID)
|–
|-
|2
|0x01
|U16
|Min calibration (Cmin) – '''Low word'''
|–
|-
|3
|0x02
|U16
|Min calibration (Cmin) – '''High word'''
|–
|-
|4
|0x03
|U16
|Fuel level data (12-bit / mm / liter)
|raw / mm / L
|-
|5
|0x04
|U16
|Temperature
|°C
|-
|6
|0x05
|U16
|Reserved
|–
|-
|7
|0x06
|U16
|Reserved
|–
|-
|8
|0x07
|U16
|Max calibration (Cmax) – '''Low word'''
|–
|-
|9
|0x08
|U16
|Max calibration (Cmax) – '''High word'''
|–
|-
|10
|0x09
|U16
|Sensor height (actual height, set via app)
|mm
|-
|11
|0x0A
|U16
|OSC current
|–
|-
|12
|0x0B
|U16
|OSC current
|–
|}
'''Detailed register description'''

'''🔹''' '''0x00 — Sensor address'''

The slave address of the sensor. The master uses this value as the address byte in the request frame.

'''🔹''' '''0x01 + 0x02 — Min calibration (Cmin) (32-bit)'''

The '''minimum''' calibration value is a 32-bit value split across two 16-bit registers:

* 0x01 = '''Low word''' (lower 16 bits)
* 0x02 = '''High word''' (upper 16 bits)

'''Combination formula:'''

Cmin = (RegHigh << 16) | RegLow

'''🔹''' '''0x07 + 0x08 — Max calibration (Cmax) (32-bit)'''

Same scheme as min, this is the '''maximum''' calibration value:

* 0x07 = Low word
* 0x08 = High word

Together, the min/max pairs define the '''calibration range''' of the capacitive sensor:

* '''Empty''' tank ↔ Cmin
* '''Full''' tank ↔ Cmax

'''🔹''' '''0x03 — Fuel level data'''

This register has '''3 output modes''', selectable by the user through the '''mobile configuration app:'''
{| class="wikitable"
|'''Mode'''
|'''Value range'''
|'''Meaning'''
|'''Conversion'''
|-
|'''Raw (12-bit)'''
|0 – 4095
|Raw value
|0 = empty, 4095 = full (per min/max calibration)
|-
|'''mm (height)'''
|0 – (Sensor_height × 10)
|Fuel level height by actual height
|Actual level (mm) = Value / 10
|-
|'''Liter (volume)'''
|0 – Vmax
|Fuel volume
|Per the calibration table/factor configured in the app
|}
'''Raw mode example:'''

Reg = 2048 → 2048 / 4095 ≈ 50% of full scale

'''mm mode example''' (output = Fuel level height × 10):

Reg = 3500 → Fuel level height = 3500 / 10 = 350.0 mm

'''Liter mode example:''' depends on tank geometry + the calibration chart the user enters in the app, e.g. Reg = 80 → 80 liters.

'''🔹''' '''0x04 — Temperature'''

Temperature measured at the sensor (°C).

'''Example:''' Reg = 25 → 25 °C.

'''🔹 0x09 — Sensor height (actual probe height)'''

The physical height of the sensor probe, '''set by the user via the app'''.

'''Example:'''

Reg = 5000 → Sensor height = 5000/10 = 500 mm.

'''🔹''' '''0x0A + 0x0B — OSC current'''

Oscillator current/parameter.

'''🔹''' '''0x05, 0x06 — Reserved'''

Reserved for future expansion, currently unused.<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO BLE ]]

LIGO PRO BLE Protocol

2026-06-30T11:53:15Z

Admin: Update Modbus RTU

== General Introduction ==

LLS Protocol is used in LIGO RS232 / RS485 fuel level sensor with the following parameters:

* Baud rate: 2400,4800,9600,19200,38400,115200 (can be configured by software on PC)
* Data bits: 8
* Parity: None
* Stop bits: 1
* Flow control: None

LIGO fuel level sensor has 2 working modes:

# '''Slave mode:''' In this mode, the sensor will respond to all requests from the external device (master device). Each sensor in the network will be distinguished by different addresses configured with the LIGO Configurator software
# '''Master mode:''' In this mode the sensor will automatically send data to the external device with a preset interval (message interval)

To enable this mode on the LIGO Configurator software, do the following:

* Automatic transmission: select HEX (binary) or ASCII or ASCII EXT

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Automatic-Transmission.png|frameless|219px]]
<div style="font-style:italic; color:#555;">Automatic transmission setting in LIGO Configurator</div>
</div>

* Set the time of each transfer (Message interval)

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Message-Interval.png|frameless|228px]]
<div style="font-style:italic; color:#555;">Message interval setting in LIGO Configurator</div>
</div>

== Exchange Protocol Description ==

The LLS protocol supports two types of exchange protocols: binary (HEX) and character view (transmission of ASCII sequences). It is recommended to use binary exchange protocol.

=== Format of Binary Protocol Messages ===

All the commands of the binary communication protocol have the same standardized format which is given in the table:

{| class="wikitable"
|-
! Sequential number of the field !! Field name !! Field size, byte !! Description
|-
| style="text-align:center;" | 1 || Prefix || style="text-align:center;" | 1 || The field is a marker of the message beginning shall have prefix 31h, and an outcoming messages shall be displayed with 3Eh prefix by the program.
|-
| style="text-align:center;" | 2 || Network address || style="text-align:center;" | 1 || For prefix 31h specify the network address of the recipient. <br>For prefix 3Eh specify the network address of the sender.
|-
| style="text-align:center;" | 3 || Operation code || style="text-align:center;" | 1 || For prefix 31h specify the code of operation which the program shall perform For Eh prefix specify the code of operation to which the response is given
|-
| style="text-align:center;" | 4 || Data || style="text-align:center;" | It depends on the operation code || Data composition and format of the field depends on the operation code
|-
| style="text-align:center;" | 5 || Checksum || style="text-align:center;" | 1 || The field is used to control over data integrity
|}

=== Single-Stage Data Reading (command 06h) ===

The command is designed for reading of the current data: relative level, temperature, frequency. The data are transmitted with a lower byte ahead.

==== Command format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | The checksum
|}

==== Response format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output (command 07h) ===

Command is designed to switch on periodic data output.

After the command is processed, the sensor starts sending data periodically — level, temperature, and frequency — with the time interval prescribed by the 13h command.

Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power power supply (if the data output mode is not istalled by default).

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Periodic data output format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output Interval Adjustment (13h command) ===

Command is designed to set up interval of periodic data output.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 0…255 || style="text-align:left;" | Interval of the data output in seconds
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Default Data Output Mode (command 17h) ===

This command determines the order of data output after the sensor is powered on or the processor is reset. After the power is on or the processor is reset, the program will send data periodically via the interface at the time interval prescribed by the 13h command.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="4" | +3 || rowspan="4" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The data are output in binary form
|-
| 02h || style="text-align:left;" | The data are output in character-coded form (ASCII mode)
|-
| 03h || style="text-align:left;" | The data are output in character-coded form (ASCII EXT mode)
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h…FFh || style="text-align:left;" | Checksum
|}

== Description of Commands for the Text-Based Protocol ==

Data exchange via the text-based protocol includes receipt and sending of ASCII symbols sequence interpreted and the request and response commands.

=== Reading the Data ===

The command is designed for reading of the current data: relative level, temperature, frequency. The command is a sequence of symbols ASCII "D" and "O". After receipt of the "DO" command the program will response in the form of ASCII symbols sequence.

For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. All values are in hexadecimal form.

In case the frequency value exceeds FFFh, the data are considered invalid.

=== Periodic Data Output ===

The command is designed to switch on periodic data output. After processing the command, the sensor performs periodic data output in the text-based form (ASCII codes) of the following data: relative level, temperature, frequency.

The data are being output periodically with an interval set up when cofiguring the sensor (LIGO Configurator software). In case the data output interval is set to zero, the data output won't be performed.

Switching on of the periodic data output is done by sending of the "DP" symbols in line. After processing of the command, the symbols line will be received. For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power supply.

== Checksum Calculation Algorithm ==

The checksum is calculated using Dallas APPLICATION NOTE 27 table method: ''Understanding and Using Cyclic Redundancy Checks with Dallas Semiconductor iButton Products''. One can use the following algorithms to calculate the checksum with a polynom <code>x^8 + x^5 + x^4 + 1</code> (C language):

<syntaxhighlight lang="c" line>
U8 CRC8(U8 data, U8 crc)
{
U8 i = data ^ crc;
crc = 0;
if (i & 0x01) crc ^= 0x5e;
if (i & 0x02) crc ^= 0xbc;
if (i & 0x04) crc ^= 0x61;
if (i & 0x08) crc ^= 0xc2;
if (i & 0x10) crc ^= 0x9d;
if (i & 0x20) crc ^= 0x23;
if (i & 0x40) crc ^= 0x46;
if (i & 0x80) crc ^= 0x8c;
return crc;
}
</syntaxhighlight>

== Modbus RTU Register Mapping ==
The SOJI sensor is capable of communication via the RS-485 serial bus in the Modbus/RTU protocol. The sensor supports the Modbus function 03 – Read Holding Registers
{| class="wikitable"
!No
!Address
|'''Type'''
|'''Description'''
|'''Unit'''
|-
|1
|0x00
|U16
|Sensor address (slave ID)
|–
|-
|2
|0x01
|U16
|Min calibration (Cmin) – '''Low word'''
|–
|-
|3
|0x02
|U16
|Min calibration (Cmin) – '''High word'''
|–
|-
|4
|0x03
|U16
|Fuel level data (12-bit / mm / liter)
|raw / mm / L
|-
|5
|0x04
|U16
|Temperature
|°C
|-
|6
|0x05
|U16
|Reserved
|–
|-
|7
|0x06
|U16
|Reserved
|–
|-
|8
|0x07
|U16
|Max calibration (Cmax) – '''Low word'''
|–
|-
|9
|0x08
|U16
|Max calibration (Cmax) – '''High word'''
|–
|-
|10
|0x09
|U16
|Sensor height (actual height, set via app)
|mm
|-
|11
|0x0A
|U16
|OSC current
|–
|-
|12
|0x0B
|U16
|OSC current
|–
|}
'''Detailed register description'''

'''🔹''' '''0x00 — Sensor address'''

The slave address of the sensor. The master uses this value as the address byte in the request frame.

'''🔹''' '''0x01 + 0x02 — Min calibration (Cmin) (32-bit)'''

The '''minimum''' calibration value is a 32-bit value split across two 16-bit registers:

* 0x01 = '''Low word''' (lower 16 bits)
* 0x02 = '''High word''' (upper 16 bits)

'''Combination formula:'''

Cmin = (RegHigh << 16) | RegLow

= RegHigh × 65536 + RegLow

'''🔹''' '''0x07 + 0x08 — Max calibration (Cmax) (32-bit)'''

Same scheme as min, this is the '''maximum''' calibration value:

* 0x07 = Low word
* 0x08 = High word

Together, the min/max pairs define the '''calibration range''' of the capacitive sensor:

* '''Empty''' tank ↔ Cmin
* '''Full''' tank ↔ Cmax

'''🔹''' '''0x03 — Fuel level data'''

This register has '''3 output modes''', selectable by the user through the '''mobile configuration app:'''
{| class="wikitable"
|'''Mode'''
|'''Value range'''
|'''Meaning'''
|'''Conversion'''
|-
|'''Raw (12-bit)'''
|0 – 4095
|Raw value
|0 = empty, 4095 = full (per min/max calibration)
|-
|'''mm (height)'''
|0 – (Sensor_height × 10)
|Fuel level height by actual height
|Actual level (mm) = Value / 10
|-
|'''3. Liter (volume)'''
|0 – Vmax
|Fuel volume
|Per the calibration table/factor configured in the app
|}
'''Raw mode example:'''

Reg = 2048 → 2048 / 4095 ≈ 50% of full scale

'''mm mode example''' (output = Fuel level height × 10):

Reg = 3500 → Fuel level height = 3500 / 10 = 350.0 mm

'''Liter mode example:''' depends on tank geometry + the calibration chart the user enters in the app, e.g. Reg = 80 → 80 liters.

'''🔹''' '''0x04 — Temperature'''

Temperature measured at the sensor (°C).

'''Example:''' Reg = 25 → 25 °C.

'''🔹 0x09 — Sensor height (actual probe height)'''

The physical height of the sensor probe, '''set by the user via the app'''.

'''Example:'''

Reg = 5000 → Sensor height = 5000/10 = 500 mm.

'''🔹''' '''0x0A + 0x0B — OSC current'''

Oscillator current/parameter.

'''🔹''' '''0x05, 0x06 — Reserved'''

Reserved for future expansion, currently unused.<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO BLE ]]

LIGO PRO 2 Protocol

2026-06-30T11:51:23Z

Admin: Update Modbus RTU

== General Introduction ==

LLS Protocol is used in LIGO RS232 / RS485 fuel level sensor with the following parameters:

* Baud rate: 2400,4800,9600,19200,38400,115200 (can be configured by software on PC or via LIGO BLE Configurator application on mobile phone)
* Data bits: 8
* Parity: None
* Stop bits: 1
* Flow control: None

LIGO fuel level sensor has 2 working modes:

# '''Slave mode:''' In this mode, the sensor will respond to all requests from the external device (master device). Each sensor in the network will be distinguished by different addresses configured with the LIGO Configurator software
# '''Master mode:''' In this mode the sensor will automatically send data to the external device with a preset interval (message interval)

To enable this mode on the LIGO Configurator software, do the following:

* Automatic transmission: select HEX (binary) or ASCII or ASCII EXT

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Automatic-Transmission.png|frameless|219px]]
<div style="font-style:italic; color:#555;">Automatic transmission setting in LIGO Configurator</div>
</div>

* Set the time of each transfer (Message interval)

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Message-Interval.png|frameless|228px]]
<div style="font-style:italic; color:#555;">Message interval setting in LIGO Configurator</div>
</div>

== Exchange Protocol Description ==

The LLS protocol supports two types of exchange protocols: binary (HEX) and character view (transmission of ASCII sequences). It is recommended to use binary exchange protocol.

=== Format of Binary Protocol Messages ===

All the commands of the binary communication protocol have the same standardized format which is given in the table:

{| class="wikitable"
|-
! Sequential number of the field !! Field name !! Field size, byte !! Description
|-
| style="text-align:center;" | 1 || Prefix || style="text-align:center;" | 1 || The field is a marker of the message beginning shall have prefix 31h, and an outcoming messages shall be displayed with 3Eh prefix by the program.
|-
| style="text-align:center;" | 2 || Network address || style="text-align:center;" | 1 || For prefix 31h specify the network address of the recipient. <br>For prefix 3Eh specify the network address of the sender.
|-
| style="text-align:center;" | 3 || Operation code || style="text-align:center;" | 1 || For prefix 31h specify the code of operation which the program shall perform For Eh prefix specify the code of operation to which the response is given
|-
| style="text-align:center;" | 4 || Data || style="text-align:center;" | It depends on the operation code || Data composition and format of the field depends on the operation code
|-
| style="text-align:center;" | 5 || Checksum || style="text-align:center;" | 1 || The field is used to control over data integrity
|}

=== Single-Stage Data Reading (command 06h) ===

The command is designed for reading of the current data: relative level, temperature, frequency. The data are transmitted with a lower byte ahead.

==== Command format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | The checksum
|}

==== Response format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output (command 07h) ===

Command is designed to switch on periodic data output.

After the command is processed, the sensor starts sending data periodically — level, temperature, and frequency — with the time interval prescribed by the 13h command.

Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power power supply (if the data output mode is not istalled by default).

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Periodic data output format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output Interval Adjustment (13h command) ===

Command is designed to set up interval of periodic data output.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 0…255 || style="text-align:left;" | Interval of the data output in seconds
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Default Data Output Mode (command 17h) ===

This command determines the order of data output after the sensor is powered on or the processor is reset. After the power is on or the processor is reset, the program will send data periodically via the interface at the time interval prescribed by the 13h command.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="4" | +3 || rowspan="4" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The data are output in binary form
|-
| 02h || style="text-align:left;" | The data are output in character-coded form (ASCII mode)
|-
| 03h || style="text-align:left;" | The data are output in character-coded form (ASCII EXT mode)
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h…FFh || style="text-align:left;" | Checksum
|}

== Description of Commands for the Text-Based Protocol ==

Data exchange via the text-based protocol includes receipt and sending of ASCII symbols sequence interpreted and the request and response commands.

=== Reading the Data ===

The command is designed for reading of the current data: relative level, temperature, frequency. The command is a sequence of symbols ASCII "D" and "O". After receipt of the "DO" command the program will response in the form of ASCII symbols sequence.

For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. All values are in hexadecimal form.

In case the frequency value exceeds FFFh, the data are considered invalid.

=== Periodic Data Output ===

The command is designed to switch on periodic data output. After processing the command, the sensor performs periodic data output in the text-based form (ASCII codes) of the following data: relative level, temperature, frequency.

The data are being output periodically with an interval set up when cofiguring the sensor (LIGO Configurator software). In case the data output interval is set to zero, the data output won't be performed.

Switching on of the periodic data output is done by sending of the "DP" symbols in line. After processing of the command, the symbols line will be received. For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power supply.

== Checksum Calculation Algorithm ==

The checksum is calculated using Dallas APPLICATION NOTE 27 table method: ''Understanding and Using Cyclic Redundancy Checks with Dallas Semiconductor iButton Products''. One can use the following algorithms to calculate the checksum with a polynom <code>x^8 + x^5 + x^4 + 1</code> (C language):

<syntaxhighlight lang="c" line>
U8 CRC8(U8 data, U8 crc)
{
U8 i = data ^ crc;
crc = 0;
if (i & 0x01) crc ^= 0x5e;
if (i & 0x02) crc ^= 0xbc;
if (i & 0x04) crc ^= 0x61;
if (i & 0x08) crc ^= 0xc2;
if (i & 0x10) crc ^= 0x9d;
if (i & 0x20) crc ^= 0x23;
if (i & 0x40) crc ^= 0x46;
if (i & 0x80) crc ^= 0x8c;
return crc;
}
</syntaxhighlight>

== Modbus RTU Register Mapping ==

The SOJI sensor is capable of communication via the RS-485 serial bus in the Modbus/RTU protocol. The sensor supports the Modbus function 03 – Read Holding Registers
{| class="wikitable" style="text-align:center;"
|-
! No !! Address
|'''Type'''
|'''Description'''
|'''Unit'''
|-
| 1 || 0x00
|U16
|Sensor address (slave ID)
| style="text-align:left;" |–
|-
| 2 || 0x01
|U16
|Min calibration (Cmin) – '''Low word'''
| style="text-align:left;" |–
|-
| 3 ||0x02
|U16
|Min calibration (Cmin) – '''High word'''
| style="text-align:left;" |–
|-
| 4
|0x03
|U16
|Fuel level data (12-bit / mm / liter)
| style="text-align:left;" |raw / mm / L
|-
|5
|0x04
|U16
|Temperature
| style="text-align:left;" |°C
|-
|6
|0x05
|U16
|Reserved
| style="text-align:left;" |–
|-
|7
|0x06
|U16
|Reserved
| style="text-align:left;" |–
|-
| 8 ||0x07
|U16
|Max calibration (Cmax) – '''Low word'''
| style="text-align:left;" |–
|-
|9
|0x08
|U16
|Max calibration (Cmax) – '''High word'''
| style="text-align: left;" |–
|-
|10
|0x09
|U16
|Sensor height (actual height, set via app)
| style="text-align: left;" |mm
|-
|11
|0x0A
|U16
|OSC current
| style="text-align: left;" |–
|-
|12
|0x0B
|U16
|OSC current
| style="text-align: left;" |–
|}
'''Detailed register description'''

'''🔹''' '''0x00 — Sensor address'''

The slave address of the sensor. The master uses this value as the address byte in the request frame.

'''🔹''' '''0x01 + 0x02 — Min calibration (Cmin) (32-bit)'''

The '''minimum''' calibration value is a 32-bit value split across two 16-bit registers:

* 0x01 = '''Low word''' (lower 16 bits)
* 0x02 = '''High word''' (upper 16 bits)

'''Combination formula:'''

Cmin = (RegHigh << 16) | RegLow

= RegHigh × 65536 + RegLow

'''🔹''' '''0x07 + 0x08 — Max calibration (Cmax) (32-bit)'''

Same scheme as min, this is the '''maximum''' calibration value:

* 0x07 = Low word
* 0x08 = High word

Together, the min/max pairs define the '''calibration range''' of the capacitive sensor:

* '''Empty''' tank ↔ Cmin
* '''Full''' tank ↔ Cmax

'''🔹''' '''0x03 — Fuel level data'''

This register has '''3 output modes''', selectable by the user through the '''mobile configuration app:'''
{| class="wikitable"
|'''Mode'''
|'''Value range'''
|'''Meaning'''
|'''Conversion'''
|-
|'''Raw (12-bit)'''
|0 – 4095
|Raw value
|0 = empty, 4095 = full (per min/max calibration)
|-
|'''mm (height)'''
|0 – (Sensor_height × 10)
|Fuel level height by actual height
|Actual level (mm) = Value / 10
|-
|'''3. Liter (volume)'''
|0 – Vmax
|Fuel volume
|Per the calibration table/factor configured in the app
|}
'''Raw mode example:'''

Reg = 2048 → 2048 / 4095 ≈ 50% of full scale

'''mm mode example''' (output = Fuel level height × 10):

Reg = 3500 → Fuel level height = 3500 / 10 = 350.0 mm

'''Liter mode example:''' depends on tank geometry + the calibration chart the user enters in the app, e.g. Reg = 80 → 80 liters.

'''🔹''' '''0x04 — Temperature'''

Temperature measured at the sensor (°C).

'''Example:''' Reg = 25 → 25 °C.

'''🔹 0x09 — Sensor height (actual probe height)'''

The physical height of the sensor probe, '''set by the user via the app'''.

'''Example:'''

Reg = 5000 → Sensor height = 5000/10 = 500 mm

'''🔹''' '''0x0A + 0x0B — OSC current'''

Oscillator current/parameter.

'''🔹''' '''0x05, 0x06 — Reserved'''

Reserved for future expansion, currently unused.<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO 2]]

LIGO AIR Protocol

2026-06-29T01:56:14Z

Admin: /* Advertising Message Format */

== 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:''' <code>0x0CFFFC0D024D0100241F000600</code>

{| class="wikitable" style="width:100%; text-align:center;"
|-
! Sequence number of bytes !! Description !! Example
|-
| 0 || Length of field || <code>0x0C</code>
|-
| +1 || Type of field (Manufacturer data) || Always <code>0xFF</code>
|-
| +2 || Company ID || <code>0x0DFC</code>
|-
| +4 || Hardware ID (type of device) || <code>0x02</code> — LIGO Air |
|-
| +5 and further || Payload (sensor parameters) || <code>0x4D0100241F000600</code>
|}

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.

{| class="wikitable" style="text-align:center;"
|-
! Byte of Hardware ID !! Type of Hardware
|-
| <code>0x02</code> || style="text-align:left; | LIGO Air
|-
| <code>0x03</code> || style="text-align:left; | LIGO Air Pro
|}

''The list of hardware may be expanded.''

'''Payload data format of LIGO AIR (Hardware ID <code>0x02</code>) and LIGO AIR Pro (Hardware ID <code>0x03</code>).'''

LIGO Air and LIGO Air Pro have the same payload data format. The structure of the payload is listed in the table below:

{| class="wikitable" style="width:100%; text-align:center;"
|-
! Sequence number of bytes !! Parameter type !! Parameter length (bytes) !! Range !! Unit of measurement
|-
| 0 || Fuel level || 2 || 0 to 1023 (option), <br>0 to 4095 (default), <br>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 <br>1: Storage Mode
|}

'''Example Payload data:''' <code>0x4D0100241F000600</code>
{| style="border-collapse:collapse;margin:0 auto;text-align:center;font-family:Arial,sans-serif;font-size:11pt;"
|-
| style="border:none;background:transparent;" |
| colspan="7" style="border:none;background:transparent;padding:0 0 6px 0;font-size:50pt;font-family:Consolas,'Courier New',monospace;font-weight:bold;letter-spacing:1px;text-align:center;" | <span style="color:#222">0x</span><span style="color:#5E7440">4D01</span><span style="color:#C99D3F">00</span><span style="color:#3170A8">24</span><span style="color:#1F2D52">1F</span><span style="color:#6E408A">00</span><span style="color:#1A1A1A">06</span><span style="color:#7BC571">00</span>
|-
| style="border:none;background:transparent;" |
! style="background:#5E7440;color:#fff;padding:10px 18px;font-weight:bold;min-width:80px;" | 4D01
! style="background:#C99D3F;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | NA
! style="background:#3170A8;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 24
! style="background:#1F2D52;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 1F
! style="background:#6E408A;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | NA
! style="background:#1A1A1A;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 06
! style="background:#7BC571;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 00
|-
| style="border:none;background:transparent;" |
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Fuel level
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Reserved
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Battery voltage
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Temperature
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Reserved
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Firmware version
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Operation Mode
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to little-endian (hex)
| style="padding:6px 12px;" | 014D
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 24
| style="padding:6px 12px;" | 1F
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 06
| style="padding:6px 12px;" | 00
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to decimal
| style="padding:6px 12px;" | 333
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 36
| style="padding:6px 12px;" | 31
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 006
| style="padding:6px 12px;" | 0
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to value
| style="padding:6px 12px;" | 333 (unit or liter)
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 3.6 Volt
| style="padding:6px 12px;" | 31 ºC
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 0.0.6
| style="padding:6px 12px;" | Working mode
|}

<div class="noprint">

== Related Documents ==
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ]]

LIGO AIR Protocol

2026-06-29T01:55:42Z

Admin: /* Advertising Message Format */

== 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:''' <code>0x0CFFFC0D024D0100241F000600</code>

{| class="wikitable" style="width:100%; text-align:center;"
|-
! Sequence number of bytes !! Description !! Example
|-
| 0 || Length of field || <code>0x0C</code>
|-
| +1 || Type of field (Manufacturer data) || Always <code>0xFF</code>
|-
| +2 || Company ID || <code>0x0DFC</code>
|-
| +4 || Hardware ID (type of device) || <code>0x02</code> — LIGO Air |
|-
| +5 and further || Payload (sensor parameters) || <code>0x4D0100241F000600</code>
|}

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.

{| class="wikitable style="text-align:center;"
|-
! Byte of Hardware ID !! Type of Hardware
|-
| <code>0x02</code> || style="text-align:left; | LIGO Air
|-
| <code>0x03</code> || style="text-align:left; | LIGO Air Pro
|}

''The list of hardware may be expanded.''

'''Payload data format of LIGO AIR (Hardware ID <code>0x02</code>) and LIGO AIR Pro (Hardware ID <code>0x03</code>).'''

LIGO Air and LIGO Air Pro have the same payload data format. The structure of the payload is listed in the table below:

{| class="wikitable" style="width:100%; style="text-align:center;"
|-
! Sequence number of bytes !! Parameter type !! Parameter length (bytes) !! Range !! Unit of measurement
|-
| 0 || Fuel level || 2 || 0 to 1023 (option), <br>0 to 4095 (default), <br>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 <br>1: Storage Mode
|}

'''Example Payload data:''' <code>0x4D0100241F000600</code>
{| style="border-collapse:collapse;margin:0 auto;text-align:center;font-family:Arial,sans-serif;font-size:11pt;"
|-
| style="border:none;background:transparent;" |
| colspan="7" style="border:none;background:transparent;padding:0 0 6px 0;font-size:50pt;font-family:Consolas,'Courier New',monospace;font-weight:bold;letter-spacing:1px;text-align:center;" | <span style="color:#222">0x</span><span style="color:#5E7440">4D01</span><span style="color:#C99D3F">00</span><span style="color:#3170A8">24</span><span style="color:#1F2D52">1F</span><span style="color:#6E408A">00</span><span style="color:#1A1A1A">06</span><span style="color:#7BC571">00</span>
|-
| style="border:none;background:transparent;" |
! style="background:#5E7440;color:#fff;padding:10px 18px;font-weight:bold;min-width:80px;" | 4D01
! style="background:#C99D3F;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | NA
! style="background:#3170A8;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 24
! style="background:#1F2D52;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 1F
! style="background:#6E408A;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | NA
! style="background:#1A1A1A;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 06
! style="background:#7BC571;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 00
|-
| style="border:none;background:transparent;" |
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Fuel level
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Reserved
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Battery voltage
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Temperature
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Reserved
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Firmware version
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Operation Mode
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to little-endian (hex)
| style="padding:6px 12px;" | 014D
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 24
| style="padding:6px 12px;" | 1F
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 06
| style="padding:6px 12px;" | 00
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to decimal
| style="padding:6px 12px;" | 333
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 36
| style="padding:6px 12px;" | 31
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 006
| style="padding:6px 12px;" | 0
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to value
| style="padding:6px 12px;" | 333 (unit or liter)
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 3.6 Volt
| style="padding:6px 12px;" | 31 ºC
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 0.0.6
| style="padding:6px 12px;" | Working mode
|}

<div class="noprint">

== Related Documents ==
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ]]

LIGO AIR Protocol

2026-06-29T01:53:53Z

Admin: /* Advertising Message Format */

== 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:''' <code>0x0CFFFC0D024D0100241F000600</code>

{| class="wikitable" style="width:100%; style="text-align:center;"
|-
! Sequence number of bytes !! Description !! Example
|-
| 0 || Length of field || <code>0x0C</code>
|-
| +1 || Type of field (Manufacturer data) || Always <code>0xFF</code>
|-
| +2 || Company ID || <code>0x0DFC</code>
|-
| +4 || Hardware ID (type of device) || <code>0x02</code> — LIGO Air |
|-
| +5 and further || Payload (sensor parameters) || <code>0x4D0100241F000600</code>
|}

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.

{| class="wikitable style="text-align:center;"
|-
! Byte of Hardware ID !! Type of Hardware
|-
| <code>0x02</code> || style="text-align:left; | LIGO Air
|-
| <code>0x03</code> || style="text-align:left; | LIGO Air Pro
|}

''The list of hardware may be expanded.''

'''Payload data format of LIGO AIR (Hardware ID <code>0x02</code>) and LIGO AIR Pro (Hardware ID <code>0x03</code>).'''

LIGO Air and LIGO Air Pro have the same payload data format. The structure of the payload is listed in the table below:

{| class="wikitable" style="width:100%; style="text-align:center;"
|-
! Sequence number of bytes !! Parameter type !! Parameter length (bytes) !! Range !! Unit of measurement
|-
| 0 || Fuel level || 2 || 0 to 1023 (option), <br>0 to 4095 (default), <br>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 <br>1: Storage Mode
|}

'''Example Payload data:''' <code>0x4D0100241F000600</code>
{| style="border-collapse:collapse;margin:0 auto;text-align:center;font-family:Arial,sans-serif;font-size:11pt;"
|-
| style="border:none;background:transparent;" |
| colspan="7" style="border:none;background:transparent;padding:0 0 6px 0;font-size:50pt;font-family:Consolas,'Courier New',monospace;font-weight:bold;letter-spacing:1px;text-align:center;" | <span style="color:#222">0x</span><span style="color:#5E7440">4D01</span><span style="color:#C99D3F">00</span><span style="color:#3170A8">24</span><span style="color:#1F2D52">1F</span><span style="color:#6E408A">00</span><span style="color:#1A1A1A">06</span><span style="color:#7BC571">00</span>
|-
| style="border:none;background:transparent;" |
! style="background:#5E7440;color:#fff;padding:10px 18px;font-weight:bold;min-width:80px;" | 4D01
! style="background:#C99D3F;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | NA
! style="background:#3170A8;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 24
! style="background:#1F2D52;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 1F
! style="background:#6E408A;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | NA
! style="background:#1A1A1A;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 06
! style="background:#7BC571;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 00
|-
| style="border:none;background:transparent;" |
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Fuel level
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Reserved
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Battery voltage
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Temperature
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Reserved
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Firmware version
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Operation Mode
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to little-endian (hex)
| style="padding:6px 12px;" | 014D
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 24
| style="padding:6px 12px;" | 1F
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 06
| style="padding:6px 12px;" | 00
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to decimal
| style="padding:6px 12px;" | 333
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 36
| style="padding:6px 12px;" | 31
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 006
| style="padding:6px 12px;" | 0
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to value
| style="padding:6px 12px;" | 333 (unit or liter)
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 3.6 Volt
| style="padding:6px 12px;" | 31 ºC
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 0.0.6
| style="padding:6px 12px;" | Working mode
|}

<div class="noprint">

== Related Documents ==
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ]]

LIGO PRO 2 Datasheet

2026-06-29T01:31:15Z

Admin: change content

== Product Overview ==

The Ligo PRO 2 Fuel Level Sensor is produced and developed by SOJI Electronics JSC. The device is designed to measure the level of liquid fuel and other non-conductive liquids in vehicle tanks and stationary fuel storage, applicable across different fields. The measured values are transmitted to an external device as output signals such as Analog, Frequency, RS232, or RS485.

Ligo PRO 2 was created to satisfy the increasing demand of the transport telematics market for improved reliability of design, data accuracy, and ease of installation. The sensor is integrated with Bluetooth Low Energy (BLE) making installation more convenient, easier, and faster.

In addition, the heavy-duty metal structure helps increase protection against electrostatic, electromagnetic and conducted interference. The Ligo PRO 2 is also designed with IP69K waterproof standards and superior shock and vibration resistance.

== Key Features ==

*High accuracy up to 99.5%
*Wide range input voltage: 6-40V
*Galvanic isolation up to 2500V
*Configurable length up to 6000mm
*Operating temperature: -40°C to +85°C
*Built-in anti-mud oil filter and anti-vibration springs
*IP69K waterproof standard
*Integrated BLE technology for smartphone configuration

== Applications ==

*Trucks, excavators, heavy construction machines
*Marine vessels and electric generators
*Off-highway machinery including high-temperature and vibration environments
*Industrial oil storage tanks or stationary storage tanks

== Product Variants / Ordering Information ==

== Technical Specifications ==

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! AF !! RS232 !! RS485
|-
| style="text-align:left;" | Standard length (L), mm || colspan="3" | 700, 1000, 1500 ... up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Output signal || Analog (0-9V) || RS232 || RS485
|-
| style="text-align:left;" | Baud rate, bit/sec || colspan="3" | 2400, 4800, 9600, 19200, 38400, 115200
|-
| style="text-align:left;" | Power supply (DC input voltage, V) || colspan="3" | 6-40V
|-
| style="text-align:left;" | Supply protection (Over-voltage 100 VDC for 2 min. Reverse polarity) || colspan="3" | Yes
|-
| style="text-align:left;" | Maximum power consumption, mA || colspan="3" | 20
|-
| style="text-align:left;" | Waterproof standard (IP) || colspan="3" | IP69K
|-
| style="text-align:left;" | Operating temperature, °C || colspan="3" | -40 ... +85
|-
| style="text-align:left;" | Maximum allowed humidity level, % || colspan="3" | 100
|-
| style="text-align:left;" | Resolution, bit || colspan="3" | 12
|-
| style="text-align:left;" | Output range (min level) || Analog (0...8V) || 0 || 0
|-
| style="text-align:left;" | Output range (max level) || Analog (1...9V) || 4095 || 4095
|-
| style="text-align:left;" | Average sampling period, s || colspan="3" | 0 ... 255
|-
| style="text-align:left;" | Message interval, s || Continuous || 1 ... 255 || 1 ... 255
|-
| style="text-align:left;" | Absolute error in temperature measurement, °C || colspan="3" | ±1
|-
| style="text-align:left;" | Bluetooth specs || colspan="3" | Bluetooth 5.1, IEEE 802.15.4-2006, 2.4 GHz, -95 dBm sensitivity, +8 dBm TX Power
|-
| style="text-align:left;" | Average service life, years (expected) || colspan="3" | 10
|}

=== Dimensions ===

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig1-dimensions.jpg|frameless|915px]]
<div style="font-style:italic; color:#555;">Figure 1. Ligo PRO 2 overall dimensions (cm)</div>
</div>

=== Wiring Connection ===

==== AF (Analog & Frequency) ====

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig2-wiring-AF.png|frameless|892px]]
<div style="font-style:italic; color:#555;">Figure 2. Wiring diagram – Analog and Frequency output signals</div>
</div>

==== RS232 ====

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig3-wiring-RS232.png|frameless|903px]]
<div style="font-style:italic; color:#555;">Figure 3. Wiring diagram – RS232 output signals</div>
</div>

==== RS485 ====

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig4-wiring-RS485.png|frameless|867px]]
<div style="font-style:italic; color:#555;">Figure 4. Wiring diagram – RS485 output signals</div>
</div>

=== Connector ===

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig5-connector.png|frameless|703px]]
<div style="font-style:italic; color:#555;">Figure 5. Connector pin details</div>
</div>

==== AF / RS232 Pinout ====

{| class="wikitable" style="text-align:center;"
|-
! Pin !! Description !! Wire Color
|-
| 1 || GND || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div>
|-
| 2 || NC (Not connected) || NC
|-
| 3 || VCC (6-40V) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div>
|-
| 4 || TXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div>
|-
| 5 || Analog Output || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#fff;border:1px solid #999;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">White</span></div>
|-
| 6 || RXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#7b3f00;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Brown</span></div>
|}

==== RS485 Pinout ====

{| class="wikitable" style="text-align:center;"
|-
! Pin !! Description !! Wire Color
|-
| 1 || GND || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div>
|-
| 2 || RS485 (B) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#2e8b2e;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Green</span></div>
|-
| 3 || VCC (6-40V) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div>
|-
| 4 || TXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div>
|-
| 5 || RS485 (A) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div>
|-
| 6 || RXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#7b3f00;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Brown</span></div>
|}

== Compliance and Certifications ==
Refer to [[LIGO PRO 2 Certification & Approvals]] for current certificate status.

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO 2 ]]

LIGO AIR User Guide

2026-06-26T01:55:19Z

Admin: /* Technical specifications */

== Safety Information ==
{{Notice
| title = Important notes during sensor installation
| body = *Install the sensor in the direction of maximum signal transmission (the directional arrow on the sensor cover should point toward the receiving device).
*Minimum allowable length of the measuring probe is 150 mm.
*Make sure there is no metal plate covering the sensor head, as this may block Bluetooth signal.
*Ensure that the signal strength (RSSI) at the receiving device is not less than -80 dBm. In cases of weak signal, it is necessary to use a LIGO PRO or a LIGO AIR Adapter to ensure the transmission strength remains within the acceptable range.
*Change the default password provided by the manufacturer to prevent unauthorized access.
*Detailed instructions for using mobile application (LIGO BLE configurator) are described in detail in the ‘LIGO BLE Configurator App User Guide’ document.
}}

== Product Overview ==

This user guide provides detailed instructions for the proper installation of the LIGO AIR fuel level sensor. The guide is intended for technicians, engineers, system integrators and end-users who are responsible for installing and maintaining the sensor in a variety of fuel tanks and vehicles.

The LIGO AIR fuel level sensor is a precision device designed by SOJI Electronics to measure the level of fuel in tanks with high accuracy and reliability. Correct installation is critical to ensure optimal performance and long-term durability.

Please read this guide thoroughly before beginning the installation process. Following the steps and recommendations provided will help you avoid common issues and ensure safe, effective operation of the sensor.

== Package Contents ==

{| class="wikitable" style="text-align:center;"
|-
! No. !! Description !! Qty (pcs)
|-
| 1 || style="text-align:left;" | LIGO AIR Fuel Level Sensor. Standard lengths: 700, 1000, and 1500mm (for customized lengths, please contact the manufacturer) || 01
|-
| 2 || style="text-align:left;" | Oil filter || 01
|-
| 3 || style="text-align:left;" | Gasoline-resistant rubber gasket || 01
|-
| 4 || style="text-align:left;" | Bottom-stop and springs || 01
|-
| 5 || style="text-align:left;" | Self-drilling screw M4.8x32mm || 05
|-
| 6 || style="text-align:left;" | Rivet and screw M5x20mm || 05
|-
| 7 || style="text-align:left;" | Protective cap || 01
|-
| 8 || style="text-align:left;" | User manual || 01
|}

== Specifications ==

=== Technical specifications ===

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! LIGO AIR LxS || LIGO AIR LxT !! LIGO AIR-PRO
|-
| style="text-align:left;" | Standard length (L), mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Bluetooth specs || colspan="3" | Bluetooth 5.4, IEEE 802.15.4-2006, 2.4 GHz, -95 dBm sensitivity
|-
| style="text-align:left;" | TX power max || 6 dBm || 6 dBm || 19.5 dBm
|-
| style="text-align:left;" | Advertising Protocol || colspan="3" | - SOJI Protocol (default)<br>- Mielta Protocol (setting in mobile app)<br>- Escort Protocol (setting in mobile app)
- Technoton Protocol (setting in mobile app)
- EUROSEN Protocol (setting in mobile app)
|-
| style="text-align:left;" | Power supply: Built-in Battery Li-SOCL2 || 3.6V * 2600mAh || 3.6V * 2600mAh || 3.6V * 3600mAh
|-
| style="text-align:left;" | Current consumption in working mode (uA) || 9 || 9 || 27
|-
| style="text-align:left;" | Measurement interval (second) || colspan="3" | From 5 to 10
|-
| style="text-align:left;" | Advertising message interval (second) || From 5 to 10 || From 5 to 10 || 10
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP69K
|-
| style="text-align:left;" | Operating temperature (°C) || colspan="3" | -40...+85
|-
| style="text-align:left;" | Resolution (bit) || colspan="3" | 12
|-
| style="text-align:left;" | Accelerometer || N/A || Built-in
|Built-in
|-
| style="text-align:left;" | Memory || colspan="3" | Built-in 32Mb EEPROM
|-
| style="text-align:left;" | Average sampling period, s || colspan="3" | 5 to 60
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±2
|-
| style="text-align:left;" | Average service life, years (expected) || colspan="3" | 10 years
|-
| style="text-align:left;" | Storage condition || colspan="3" | 15°C to 30°C, RH < 60%
|}

=== Overview of sensor structure ===

<div style="text-align:center;">
[[File:LIGO-AIR-fig1-sensor-structure.png|frameless|674px]]
<div style="font-style:italic; color:#555;">Figure 1. LIGO AIR series' overall dimensions (mm).</div>
</div>

{| class="wikitable" style="text-align:center;"
|-
! Manufacturer part number !! L (mm)
|-
| style="text-align:left;" | LIGO AIR – L7S<br>LIGO AIR – L7T<br>LIGO AIR PRO – L7S || 700 ± 3
|-
| style="text-align:left;" | LIGO AIR – L10S<br>LIGO AIR – L10T<br>LIGO AIR PRO – L10S || 1000 ± 3
|-
| style="text-align:left;" | LIGO AIR – L15S<br>LIGO AIR – L15T<br>LIGO AIR PRO – L15S || 1500 ± 3
|}

== Installation ==

=== Fuel tank preparation ===

# Empty the tank, clean and dry it if necessary, for gasoline fuel tanks, all fuel vapors must be removed from the tank to prevent fire or explosion during installation.
# Selecting the installation location for the LIGO AIR fuel level sensor, take the following requirements into account:
#* The sensor's installation location must be as close as possible to the tank's geometric center and at its deepest point.
#* The sensor's installation location must be as close as possible to the tank's geometric center and at its deepest point.
#* Ensure that the sensor must avoid contact with reinforcement ribs and other equipment inside the tank.

<div style="text-align:center;">
[[File:LIGO-AIR-fig2-tank-preparation.png|frameless|600px]]
<div style="font-style:italic; color:#555;">Figure 2. Tank installation location requirements</div>
</div>
3. Drilling a central hole (Ø42 mm), then drill four additional holes for mounting screws as shown in the figure below:
<div style="text-align:center;">
[[File:LIGO-AIR-fig3-drilling.png|frameless|523px]]
<div style="font-style:italic; color:#555;">Figure 3. Drilling central hole Ø42 mm and four mounting screw holes</div>
</div>

'''Notes:''' The mounting hole diameter depends on the material and thickness of the tank
* For fuel tanks with a wall thickness ≤3 mm, M5 rivet nut should be used. In this case, Drill 4 × Ø7 mm mounting screw holes.
* For fuel tanks with a wall thickness >3 mm, M4.8 self-tapping screw can be used. In this case, Drill 4 × Ø7 mm mounting screw holes.
* Mounting holes positions must ensure that the sensor is installed in the direction of maximum signal transmission (the directional arrow on the sensor cover should point toward the receiving device).

=== Sensor preparation ===

1. Cutting sensor tube

The length of the sensor tube should be calculated according to the following formula:

'''L = H - 25 mm'''

Where:
* '''L''' – final tube length after cutting
* '''H''' - height of the tank at the installation point.

After cutting, remove any burrs and clean the tube using fuel.

'''Note:''' The minimum length of the tube after cutting must be at least 150 mm (15cm)

2. Installing bottom-stop springs and filter

Installing the bottom-stop and the oil filter in sequence, as shown in the figure below:

<div style="text-align:center;">
[[File:Screenshot 2026-06-19 161113.png|frameless|562px]]
<div style="font-style:italic; color:#555;">Figure 4. Installing bottom-stop springs and oil filter</div>
</div>

=== Installing sensor on the fuel tank ===

# Apply gasket sealant to fuel tank, gasket and sensor flange (using Fuel resistant RTV Silicone gasket maker).
# Insert the LIGO AIR fuel sensor into the tank and secure fasten it securely using the appropriate screws (using self-tapping screws or rivet nut depending on fuel tank thickness and material as mentioned above).

<div style="text-align:center;">
[[File:LIGO-AIR-fig5-installing-on-tank.png|frameless|624px]]
<div style="font-style:italic; color:#555;">Figure 5. Installing sensor on the fuel tank</div>
</div>

'''Note:''' Install the sensor in the direction of maximum signal transmission (the directional arrow on the sensor cover should point toward the receiving device).

<div style="text-align:center;">
[[File:LIGO-AIR-fig6-clearance.png|frameless|540px]]
<div style="font-style:italic; color:#555;">Figure 6. Minimum 150 mm clearance between sensor top and overhead metal surface</div>
</div>

'''Note:''' Ensure a minimum clearance of 150 mm between the top of the sensor and any overhead metal surface.

=== Installing protective cap ===

The protective cap should be installed after the sensor installation and calibration processes are completed. This cap helps prevent unauthorized access and protects the sensor from environmental factors such as sunlight, physical impact…

<div style="text-align:center;">
[[File:LIGO-AIR-fig7-protective-cap-install.png|frameless|537px]]
<div style="font-style:italic; color:#555;">Figure 7. Installing protective cap</div>
</div>

Push the protective cap until it clicks into place, indicating that it is fully seated.

In cases when sensor inspection is required, the protective cap must be removed. Follow the removal procedure as shown in picture below:

<div style="text-align:center;">
[[File:LIGO-AIR-fig8-protective-cap-remove.png|frameless|651px]]
<div style="font-style:italic; color:#555;">Figure 8. Protective cap removal procedure</div>
</div>

'''Note:''' Please ensure that no parts of the sensor are damaged while removing the protective cap.

== Configuration ==

=== Connecting sensor to smartphone and setting ===

To configure the LIGO AIR fuel sensor, download the '''LIGO BLE Configurator''' app on '''Appstore (for IOS) or CH Play (for Android devices).'''

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

<gallery mode="packed" widths="250" heights="500">
File:LIGO-AIR-fig9-app-permissions-1.jpg|Figure 9. Grant all the permissions request by program
File:LIGO-AIR-fig10-app-permissions-2.jpg|Figure 10. Grant all the permissions request by program
</gallery>

Grant all the permissions request by program as above

==== Connecting sensor ====

Run the application and select the sensor you want to connect to, as shown in the pictures below:

<gallery mode="packed" widths="250" heights="500">
File:LIGO-AIR-fig11-connect-1.jpg|Figure 11. Selecting sensor type
File:LIGO-AIR-fig12-connect-2.jpg|Figure 12. Connecting sensor
</gallery>

==== Set Empty and Set Full ====

Step 1: Set Full

* Immerse the sensor in fuel until the fuel reaches the sensor flange
* Wait for C_working value to stablize and then press Set Full button

<div style="text-align:center;">
[[File:LIGO-AIR-fig13-set-full.jpg|frameless|304px]]
<div style="font-style:italic; color:#555;">Figure 13. Set Full</div>
</div>

Step 2: Set Empty

* Remove the sensor from the fuel and wait for 1-2 minutes allow the fuel drain from the measuring probe and then press Set Empty button.

<div style="text-align:center;">
[[File:LIGO-AIR-fig14-set-empty.jpg|frameless|304px]]
<div style="font-style:italic; color:#555;">Figure 14. Set Empty</div>
</div>

=== Calibration table ===

After installation, the sensor must be calibrated to ensure accurate volume measurement. Calibration table can be performed either on the platform (server) or locally on the sensor.

* '''Calibration table on the Platform (Server):''' The sensor sends raw level values (ranging from 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 calibration table on the platform.

== Operation ==

=== Solutions for long-range or in metal-obstructed environments ===

In some cases, when the distance between the sensor and the receiver is long or there are many metal obstacles causing signal attenuation, customers can choose the LIGO AIR PRO model to increase transmission power or install the LIGO AIR Adapter at the receiver side to boost the signal received from the sensor.

Below is a comparison table of transmission distances between different types of sensors and receivers:

{| class="wikitable" style="text-align:center;"
|-
! Device !! Bluetooth signal range
|-
| style="text-align:left;" | LIGO AIR + Telematics (tracker) device || Standard distance
|-
| style="text-align:left;" | LIGO AIR + LIGO AIR Adapter || 2 x Standard distance
|-
| style="text-align:left;" | LIGO AIR Pro + LIGO AIR Adapter || 4 x Standard distance
|}

== Troubleshooting ==
<div class="dim">
{| class="wikitable"
|-
! Symptom !! Possible Cause !! Solution
|-
| Sensor not discovered by LIGO BLE Configurator app
|
* App permissions not granted
* Sensor outside Bluetooth range
* Metal obstruction blocking sensor head
* Sensor battery depleted (end of service life)
|
* Re-grant Bluetooth & location permissions
* Move within range; verify line-of-sight
* Remove any metal plate above sensor
* Verify sensor age vs ~10-year service life
|-
| RSSI at receiver below −80 dBm
|
* Distance too far
* Metal obstruction in signal path
* Sensor orientation wrong (arrow not toward receiver)
|
* Use LIGO AIR PRO or add LIGO AIR Adapter
* Re-route or remove obstruction
* Re-mount sensor so directional arrow points to receiver
|-
| Reading shows 0% after Set Empty when fuel is present
|
* Set Empty / Set Full procedure executed in wrong order
* Tube damaged or burrs not removed
|
* Repeat calibration: Set Full first (immersed), then Set Empty (drained)
* Inspect tube, deburr, re-cut if necessary
|-
| Cannot connect with default password (login refused)
|
* Default password already changed by previous user
|
* Contact the previous installer
|}

If the problem persists, contact [[#Support / Contact|Support]].
</div>

== Maintenance ==

== Certification / Compliance ==

Refer to [[LIGO AIR Certification & Approvals]] for current certificate status.''

== Support / Contact ==

{| class="wikitable"
|-
! Channel !! Detail
|-
| Company || SOJI ELECTRONICS.,JSC
|-
| Address || C50-LK13, Lot No. 09, New Urban Area, Le Trong Tan street, Duong Noi Ward, Ha Dong District, Hanoi City, Vietnam
|-
| Tel/Fax || +84 24 62 932 369
|-
| Email || contact@sojielectronics.com
|-
| Website || [http://sojielectronics.com sojielectronics.com]
|}

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ]]

LIGO AIR Datasheet

2026-06-26T01:52:05Z

Admin: /* Technical Specifications */

== Product Overview ==

LIGO-AIR Fuel Level Sensor is developed and manufactured by SOJI Electronics JSC. The device is designed to measure the level of liquid fuel and other non-conductive liquids in vehicle tanks and stationary fuel storage, applicable in different fields. Equipped with advanced Bluetooth Low Energy technology, LIGO AIR enables seamless, real-time data transmission without the need for complex wiring and easy for installation.

The purpose of creating a new product was to satisfy the increasing demand of the transport telematics market for improved reliability of the design, data, and ease of installation. Unlike its predecessors, the wireless fuel level sensor helps minimize the risk of signal wire tampering.

In addition, the heavy-duty metal structure helps increase protection against environmental factors such as dust, moisture, vibration and high temperature conditions. This ensures that the LIGO AIR sensor maintains stability, durability, and operational lifespan equal to or even greater than that of wired sensors.

== Key Features ==

* High accuracy up to 99,5%.
* By utilizing directional antenna technology, the sensor achieves a communication range up to 1.5 times greater than typical market-available sensors.
* With ultra-low power consumption (9uA in working mode and 4uA in storage mode), the sensor ensures longer battery life and reduced maintenance.
* Can be optionally cut off or prolonged up to 6000mm.
* Wide operating temperature ranges from -40°C to +85°C.
* TX power up to 19.5dBm (LIGO AIR PRO).
* Battery capacity up to 3600mAh (optional) helps to extend battery life of sensor.
* Replaceable battery.
* Built-in accelerometer.
* Built-in 32Mb EEPROM for data logs (Continuously stored for a minimum of 90 days) and setting logs (Maximum 500 logs).
* Built-in Anti-mud oil filter and anti-vibration springs.
* IP69K waterproof standard.
* 8-10 years of battery life.

== Applications ==

* Trucks, excavators, heavy construction machines…
* Marine vessels and electric generators.
* Off-highway machinery including high-temperature & vibration environments.
* Industrial oil storage tanks or stationary storage tanks.

== Product Variants / Ordering Information ==

During our discussions with customers and market research, we found that most wireless fuel level sensors on the market suffer from key issues such as poor durability, short battery life (2-4 years), and unstable connectivity (Bluetooth signal).

To address these challenges, the LIGO AIR series was developed — a new generation of wireless fuel level sensors engineered for superior reliability, long battery life, and stable long-range communication in all environments.

The LIGO AIR series offers three specialized versions, each optimized to meet specific operational demands — from cost efficiency to long-range communication and extended battery life as bellow:

* '''LIGO AIR LxS:''' The standard version of the LIGO AIR sensor is designed as a cost-effective solution that fulfills essential monitoring needs while maintaining reliable performance (Trucks, excavators, cement mixer truck, heavy construction machines…)
* '''LIGO AIR LxT:''' The extended-battery version of the LIGO AIR sensor is designed for applications that demand long operational life (8-12 years) and reliable performance in harsh environments, including high-temperature conditions.
* '''LIGO AIR PRO:''' The long-range version of the LIGO AIR sensor is designed for applications requiring extended transmission distances or operation in environments with significant obstacles (Marine vessels, electric generators, Industrial oil storage tanks, stationary storage tanks…)

The following table summarizes the performance differences between LIGO AIR models and competitive products in terms of battery life and transmission distance:

{| class="wikitable" style="text-align:center;"
|-
! rowspan="2" | Comparison product
! Competitive products on the market
! Standard version
! Extended battery life
! Extended transmission range
|-
! Product
! LIGO AIR LxS
! LIGO AIR LxT
! LIGO AIR Pro LxS
|-
| style="text-align:left;" | Battery life || 0.4 x Standard (2-4 years) || Standard (6-8 years) || 1.5x Standard (8-12 years) || Standard (6-8 years)
|-
| style="text-align:left;" | Transmission range || 0.6 x Standard || Standard || Standard || 2x standard
|}

== Technical Specifications ==

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! LIGO AIR LxS !! LIGO AIR LxT !! LIGO AIR-PRO
|-
| style="text-align:left;" | Standard length (L), mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Bluetooth specs || colspan="3" | Bluetooth 5.4, IEEE 802.15.4-2006, 2.4 GHz, -95 dBm sensitivity
|-
| style="text-align:left;" | TX power max || 6 dBm || 6 dBm || 19.5 dBm
|-
| style="text-align:left;" | Advertising Protocol || colspan="3" | - SOJI Protocol (default)<br>- Mielta Protocol (setting in mobile app)<br>- Escort Protocol (setting in mobile app)
- Technoton Protocol (setting in mobile app)

- Eurosen Protocol (setting in mobile app)
|-
| style="text-align:left;" | Power supply || 3.6V * 2600mAh || 3.6V * 2400mAh || 3.6V * 3600mAh
|-
| style="text-align:left;" | Current consumption in working mode (uA) || 9 || 9 || 27
|-
| style="text-align:left;" | Measurement interval (second) || colspan="3" | From 5 to 10
|-
| style="text-align:left;" | Advertising message interval (second) || From 5 to 10 || From 5 to 10 || From 10 to 15
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP69K
|-
| style="text-align:left;" | Operating temperature (°C) || colspan="3" | -40...+85
|-
| style="text-align:left;" | Resolution (bit) || colspan="3" | 12
|-
| style="text-align:left;" | Accelerometer || N/A || Built-in || Built-in
|-
| style="text-align:left;" | Memory || colspan="3" | Built-in 32Mb EEPROM
|-
| style="text-align:left;" | Average sampling period, s || colspan="3" | 5 to 60
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±2
|-
| style="text-align:left;" | Average service life, years (expected) || colspan="3" | 10 years
|}

=== Dimensions ===
<div style="text-align:center;">
[[File:LIGO-AIR-fig1-dimensions.png|frameless|674px]]
<div style="font-style:italic; color:#555;">Figure 1. LIGO AIR series' overall dimensions (mm).</div>
</div>

{| class="wikitable" style="text-align:center;"
|-
! Manufacturer part number !! L (mm)
|-
| style="text-align:left;" | LIGO AIR – L7S<br>LIGO AIR – L7T<br>LIGO AIR PRO – L7S || 700 ± 3
|-
| style="text-align:left;" | LIGO AIR – L10S<br>LIGO AIR – L10T<br>LIGO AIR PRO – L10S || 1000 ± 3
|-
| style="text-align:left;" | LIGO AIR – L15S<br>LIGO AIR – L15T<br>LIGO AIR PRO – L15S || 1500 ± 3
|}

== Compliance and Certifications ==
Refer to [[LIGO AIR Certification & Approvals]] for current certificate status.''

=== Warranty ===

* The warranty period is 3 years from the date of shipment by the manufacturer.
* The warranty period and service life do not apply to the battery.
* Compliance with the specified operating, transport, and storage conditions is a prerequisite for the manufacturer's guarantee.
* The manufacturer reserves the right to modify the design and composition of the product without prior notice to the customer.

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ]]

LIGO AIR Datasheet

2026-06-26T01:50:00Z

Admin: /* Technical Specifications */

== Product Overview ==

LIGO-AIR Fuel Level Sensor is developed and manufactured by SOJI Electronics JSC. The device is designed to measure the level of liquid fuel and other non-conductive liquids in vehicle tanks and stationary fuel storage, applicable in different fields. Equipped with advanced Bluetooth Low Energy technology, LIGO AIR enables seamless, real-time data transmission without the need for complex wiring and easy for installation.

The purpose of creating a new product was to satisfy the increasing demand of the transport telematics market for improved reliability of the design, data, and ease of installation. Unlike its predecessors, the wireless fuel level sensor helps minimize the risk of signal wire tampering.

In addition, the heavy-duty metal structure helps increase protection against environmental factors such as dust, moisture, vibration and high temperature conditions. This ensures that the LIGO AIR sensor maintains stability, durability, and operational lifespan equal to or even greater than that of wired sensors.

== Key Features ==

* High accuracy up to 99,5%.
* By utilizing directional antenna technology, the sensor achieves a communication range up to 1.5 times greater than typical market-available sensors.
* With ultra-low power consumption (9uA in working mode and 4uA in storage mode), the sensor ensures longer battery life and reduced maintenance.
* Can be optionally cut off or prolonged up to 6000mm.
* Wide operating temperature ranges from -40°C to +85°C.
* TX power up to 19.5dBm (LIGO AIR PRO).
* Battery capacity up to 3600mAh (optional) helps to extend battery life of sensor.
* Replaceable battery.
* Built-in accelerometer.
* Built-in 32Mb EEPROM for data logs (Continuously stored for a minimum of 90 days) and setting logs (Maximum 500 logs).
* Built-in Anti-mud oil filter and anti-vibration springs.
* IP69K waterproof standard.
* 8-10 years of battery life.

== Applications ==

* Trucks, excavators, heavy construction machines…
* Marine vessels and electric generators.
* Off-highway machinery including high-temperature & vibration environments.
* Industrial oil storage tanks or stationary storage tanks.

== Product Variants / Ordering Information ==

During our discussions with customers and market research, we found that most wireless fuel level sensors on the market suffer from key issues such as poor durability, short battery life (2-4 years), and unstable connectivity (Bluetooth signal).

To address these challenges, the LIGO AIR series was developed — a new generation of wireless fuel level sensors engineered for superior reliability, long battery life, and stable long-range communication in all environments.

The LIGO AIR series offers three specialized versions, each optimized to meet specific operational demands — from cost efficiency to long-range communication and extended battery life as bellow:

* '''LIGO AIR LxS:''' The standard version of the LIGO AIR sensor is designed as a cost-effective solution that fulfills essential monitoring needs while maintaining reliable performance (Trucks, excavators, cement mixer truck, heavy construction machines…)
* '''LIGO AIR LxT:''' The extended-battery version of the LIGO AIR sensor is designed for applications that demand long operational life (8-12 years) and reliable performance in harsh environments, including high-temperature conditions.
* '''LIGO AIR PRO:''' The long-range version of the LIGO AIR sensor is designed for applications requiring extended transmission distances or operation in environments with significant obstacles (Marine vessels, electric generators, Industrial oil storage tanks, stationary storage tanks…)

The following table summarizes the performance differences between LIGO AIR models and competitive products in terms of battery life and transmission distance:

{| class="wikitable" style="text-align:center;"
|-
! rowspan="2" | Comparison product
! Competitive products on the market
! Standard version
! Extended battery life
! Extended transmission range
|-
! Product
! LIGO AIR LxS
! LIGO AIR LxT
! LIGO AIR Pro LxS
|-
| style="text-align:left;" | Battery life || 0.4 x Standard (2-4 years) || Standard (6-8 years) || 1.5x Standard (8-12 years) || Standard (6-8 years)
|-
| style="text-align:left;" | Transmission range || 0.6 x Standard || Standard || Standard || 2x standard
|}

== Technical Specifications ==

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! LIGO AIR LxS !! LIGO AIR LxT) !! LIGO AIR-PRO
|-
| style="text-align:left;" | Standard length (L), mm || colspan="3" | 700, 1000, 1500...up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Bluetooth specs || colspan="3" | Bluetooth 5.4, IEEE 802.15.4-2006, 2.4 GHz, -95 dBm sensitivity
|-
| style="text-align:left;" | TX power max || colspan="2" | 6 dBm || 19.5 dBm
|-
| style="text-align:left;" | Advertising Protocol || colspan="3" | - SOJI Protocol (default)<br>- Mielta Protocol (setting in mobile app)<br>- Escort Protocol (setting in mobile app)
- Technoton Protocol (setting in mobile app)

- Eurosen Protocol (setting in mobile app)
|-
| style="text-align:left;" | Power supply || 3.6V * 2600mAh || 3.6V * 2400mAh || 3.6V * 3600mAh
|-
| style="text-align:left;" | Current consumption in working mode (uA) || colspan="2" | 9 || 27
|-
| style="text-align:left;" | Measurement interval (second) || colspan="3" | From 5 to 10
|-
| style="text-align:left;" | Advertising message interval (second) || colspan="2" | From 5 to 10 || From 10 to 15
|-
| style="text-align:left;" | Waterproof standard (Ingress protection rating, IP) || colspan="3" | IP69K
|-
| style="text-align:left;" | Operating temperature (°C) || colspan="3" | -40...+85
|-
| style="text-align:left;" | Resolution (bit) || colspan="3" | 12
|-
| style="text-align:left;" | Accelerometer || N/A || built-in || Built-in
|-
| style="text-align:left;" | Memory || colspan="3" | Built-in 32Mb EEPROM
|-
| style="text-align:left;" | Average sampling period, s || colspan="3" | 5 to 60
|-
| style="text-align:left;" | Absolute error in temperature measurement within the entire temperature measuring range, °С || colspan="3" | ±2
|-
| style="text-align:left;" | Average service life, years (expected) || colspan="3" | 10 years
|}

=== Dimensions ===
<div style="text-align:center;">
[[File:LIGO-AIR-fig1-dimensions.png|frameless|674px]]
<div style="font-style:italic; color:#555;">Figure 1. LIGO AIR series' overall dimensions (mm).</div>
</div>

{| class="wikitable" style="text-align:center;"
|-
! Manufacturer part number !! L (mm)
|-
| style="text-align:left;" | LIGO AIR – L7S<br>LIGO AIR – L7T<br>LIGO AIR PRO – L7S || 700 ± 3
|-
| style="text-align:left;" | LIGO AIR – L10S<br>LIGO AIR – L10T<br>LIGO AIR PRO – L10S || 1000 ± 3
|-
| style="text-align:left;" | LIGO AIR – L15S<br>LIGO AIR – L15T<br>LIGO AIR PRO – L15S || 1500 ± 3
|}

== Compliance and Certifications ==
Refer to [[LIGO AIR Certification & Approvals]] for current certificate status.''

=== Warranty ===

* The warranty period is 3 years from the date of shipment by the manufacturer.
* The warranty period and service life do not apply to the battery.
* Compliance with the specified operating, transport, and storage conditions is a prerequisite for the manufacturer's guarantee.
* The manufacturer reserves the right to modify the design and composition of the product without prior notice to the customer.

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ]]

LIGO PRO Protocol

2026-06-24T10:57:09Z

Admin: Initial Release [release]

== General Introduction ==

LLS Protocol is used in LIGO RS232 / RS485 fuel level sensor with the following parameters:

* Baud rate: 2400,4800,9600,19200,38400,115200 (can be configured by software on PC)
* Data bits: 8
* Parity: None
* Stop bits: 1
* Flow control: None

LIGO fuel level sensor has 2 working modes:

# '''Slave mode:''' In this mode, the sensor will respond to all requests from the external device (master device). Each sensor in the network will be distinguished by different addresses configured with the LIGO Configurator software
# '''Master mode:''' In this mode the sensor will automatically send data to the external device with a preset interval (message interval)

To enable this mode on the LIGO Configurator software, do the following:

* Automatic transmission: select HEX (binary) or ASCII or ASCII EXT

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Automatic-Transmission.png|frameless|219px]]
<div style="font-style:italic; color:#555;">Automatic transmission setting in LIGO Configurator</div>
</div>

* Set the time of each transfer (Message interval)

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Message-Interval.png|frameless|228px]]
<div style="font-style:italic; color:#555;">Message interval setting in LIGO Configurator</div>
</div>

== Exchange Protocol Description ==

The LLS protocol supports two types of exchange protocols: binary (HEX) and character view (transmission of ASCII sequences). It is recommended to use binary exchange protocol.

=== Format of Binary Protocol Messages ===

All the commands of the binary communication protocol have the same standardized format which is given in the table:

{| class="wikitable"
|-
! Sequential number of the field !! Field name !! Field size, byte !! Description
|-
| style="text-align:center;" | 1 || Prefix || style="text-align:center;" | 1 || The field is a marker of the message beginning shall have prefix 31h, and an outcoming messages shall be displayed with 3Eh prefix by the program.
|-
| style="text-align:center;" | 2 || Network address || style="text-align:center;" | 1 || For prefix 31h specify the network address of the recipient. <br>For prefix 3Eh specify the network address of the sender.
|-
| style="text-align:center;" | 3 || Operation code || style="text-align:center;" | 1 || For prefix 31h specify the code of operation which the program shall perform For Eh prefix specify the code of operation to which the response is given
|-
| style="text-align:center;" | 4 || Data || style="text-align:center;" | It depends on the operation code || Data composition and format of the field depends on the operation code
|-
| style="text-align:center;" | 5 || Checksum || style="text-align:center;" | 1 || The field is used to control over data integrity
|}

=== Single-Stage Data Reading (command 06h) ===

The command is designed for reading of the current data: relative level, temperature, frequency. The data are transmitted with a lower byte ahead.

==== Command format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | The checksum
|}

==== Response format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output (command 07h) ===

Command is designed to switch on periodic data output.

After the command is processed, the sensor starts sending data periodically — level, temperature, and frequency — with the time interval prescribed by the 13h command.

Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power power supply (if the data output mode is not istalled by default).

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Periodic data output format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output Interval Adjustment (13h command) ===

Command is designed to set up interval of periodic data output.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 0…255 || style="text-align:left;" | Interval of the data output in seconds
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Default Data Output Mode (command 17h) ===

This command determines the order of data output after the sensor is powered on or the processor is reset. After the power is on or the processor is reset, the program will send data periodically via the interface at the time interval prescribed by the 13h command.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="4" | +3 || rowspan="4" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The data are output in binary form
|-
| 02h || style="text-align:left;" | The data are output in character-coded form (ASCII mode)
|-
| 03h || style="text-align:left;" | The data are output in character-coded form (ASCII EXT mode)
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h…FFh || style="text-align:left;" | Checksum
|}

== Description of Commands for the Text-Based Protocol ==

Data exchange via the text-based protocol includes receipt and sending of ASCII symbols sequence interpreted and the request and response commands.

=== Reading the Data ===

The command is designed for reading of the current data: relative level, temperature, frequency. The command is a sequence of symbols ASCII "D" and "O". After receipt of the "DO" command the program will response in the form of ASCII symbols sequence.

For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. All values are in hexadecimal form.

In case the frequency value exceeds FFFh, the data are considered invalid.

=== Periodic Data Output ===

The command is designed to switch on periodic data output. After processing the command, the sensor performs periodic data output in the text-based form (ASCII codes) of the following data: relative level, temperature, frequency.

The data are being output periodically with an interval set up when cofiguring the sensor (LIGO Configurator software). In case the data output interval is set to zero, the data output won't be performed.

Switching on of the periodic data output is done by sending of the "DP" symbols in line. After processing of the command, the symbols line will be received. For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power supply.

== Checksum Calculation Algorithm ==

The checksum is calculated using Dallas APPLICATION NOTE 27 table method: ''Understanding and Using Cyclic Redundancy Checks with Dallas Semiconductor iButton Products''. One can use the following algorithms to calculate the checksum with a polynom <code>x^8 + x^5 + x^4 + 1</code> (C language):

<syntaxhighlight lang="c" line>
U8 CRC8(U8 data, U8 crc)
{
U8 i = data ^ crc;
crc = 0;
if (i & 0x01) crc ^= 0x5e;
if (i & 0x02) crc ^= 0xbc;
if (i & 0x04) crc ^= 0x61;
if (i & 0x08) crc ^= 0xc2;
if (i & 0x10) crc ^= 0x9d;
if (i & 0x20) crc ^= 0x23;
if (i & 0x40) crc ^= 0x46;
if (i & 0x80) crc ^= 0x8c;
return crc;
}
</syntaxhighlight>

<div class="noprint">
== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO ]]

Category:LIGO PRO Protocol

2026-06-24T10:57:01Z

Admin: Auto-created category for LIGO PRO Protocol

{{DEFAULTSORT:05 LIGO PRO Protocol}}

[[Category:LIGO PRO]]

LIGO PRO Protocol

2026-06-24T10:57:01Z

Admin: Create page

== General Introduction ==
<div class="dim">

''Brief introduction to the protocol per IEC/IEEE standards for wireless data protocols.''

'''What to fill in:'''
* '''Protocol name and version''' — full name + version number (vd: SOJI Protocol v2.1)
* '''Purpose''' — what data the protocol transmits and to whom
* '''Transport layer''' — Bluetooth 5.4 BLE / WiFi / LoRa / proprietary RF
* '''Frequency & modulation''' — 2.4 GHz GFSK / LoRa CSS / ...
* '''Operating mode''' — Advertising-only (one-way broadcast) / Connection-based / Mesh
* '''Compatible devices''' — list of sensors / receivers supporting this protocol
* '''Reference standards''' — IEEE 802.15.4, Bluetooth Core 5.4, etc.

'''Example structure:'''
* Paragraph 1: "The [Protocol Name] is a [type] protocol defined by SOJI Electronics for [purpose]..."
* Paragraph 2: "It operates over [transport] at [frequency] and is supported by [device list]..."

'''Optional sub-sections:'''
* === Protocol Stack === — layered diagram of protocol stack
* === Roles === — Broadcaster / Observer / Central / Peripheral
* === Security === — encryption, authentication, password protection

</div>

== Advertising Message Format ==
<div class="dim">

''Byte-by-byte breakdown of the BLE advertising packet payload.''

'''What to fill in:'''
* '''Packet overview''' — total packet length, manufacturer ID, structure summary
* '''Field table''' — every field with offset, length, value, description

'''Example field breakdown table:'''

{| class="wikitable" style="width:100%;"
|-
! Offset !! Length (bytes) !! Field Name !! Value / Format !! Description
|-
| 0x00 || 1 || AD Length || 0xXX || Length of the advertising data structure
|-
| 0x01 || 1 || AD Type || 0xFF || Manufacturer Specific Data (per Bluetooth Core spec)
|-
| 0x02 || 2 || Company ID || 0xXXXX (LE) || SOJI Electronics SIG-assigned Company ID
|-
| 0x04 || 1 || Protocol ID || 0xXX || SOJI Protocol identifier
|-
| 0x05 || 1 || Frame Type || 0xXX || Frame type (data frame, status frame, ...)
|-
| 0x06 || N || Payload || ... || Sensor data payload (see Payload Structure below)
|-
| 0x06+N || 2 || CRC-16 || 0xXXXX || CRC-16/CCITT checksum over Offset 0x00 to 0x05+N
|}

'''Sub-sections to consider:'''
* === Packet Overview === — total length, byte order (LE/BE), encoding
* === Field Definitions === — main field table above
* === Payload Structure === — detailed payload fields (level, temperature, battery, RSSI, etc.) with units and scaling
* === Frame Types === — enumeration of frame types if multiple exist
* === CRC / Checksum === — algorithm (CRC-16/CCITT, polynomial, init value, XOR-out)
* === Example Raw Frame === — hex dump of a real advertising packet with field annotations
* === Decoding Pseudocode === — short code snippet (C / Python) showing how to parse a frame

'''Example raw frame block:'''
<syntaxhighlight lang="text">
Raw bytes (hex):
0E FF 5A A5 01 02 03 04 ...

Decoded:
AD Length = 0x0E (14 bytes)
AD Type = 0xFF (Manufacturer Specific)
Company ID = 0xA55A (SOJI Electronics)
Protocol ID = 0x01 (SOJI Protocol)
Frame Type = 0x02 (Data Frame)
...
</syntaxhighlight>

'''Example decoding pseudocode:'''
<syntaxhighlight lang="python">
def decode_soji_frame(adv_data: bytes) -> dict:
if adv_data[1] != 0xFF:
return None
company_id = int.from_bytes(adv_data[2:4], 'little')
protocol_id = adv_data[4]
frame_type = adv_data[5]
payload = adv_data[6:-2]
crc = int.from_bytes(adv_data[-2:], 'little')
# ... validate CRC, parse payload
return { ... }
</syntaxhighlight>

</div>

<div class="noprint">
== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO ]]

LIGO PRO BLE Protocol

2026-06-24T10:56:28Z

Admin: Initial Release [release]

== General Introduction ==

LLS Protocol is used in LIGO RS232 / RS485 fuel level sensor with the following parameters:

* Baud rate: 2400,4800,9600,19200,38400,115200 (can be configured by software on PC)
* Data bits: 8
* Parity: None
* Stop bits: 1
* Flow control: None

LIGO fuel level sensor has 2 working modes:

# '''Slave mode:''' In this mode, the sensor will respond to all requests from the external device (master device). Each sensor in the network will be distinguished by different addresses configured with the LIGO Configurator software
# '''Master mode:''' In this mode the sensor will automatically send data to the external device with a preset interval (message interval)

To enable this mode on the LIGO Configurator software, do the following:

* Automatic transmission: select HEX (binary) or ASCII or ASCII EXT

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Automatic-Transmission.png|frameless|219px]]
<div style="font-style:italic; color:#555;">Automatic transmission setting in LIGO Configurator</div>
</div>

* Set the time of each transfer (Message interval)

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Message-Interval.png|frameless|228px]]
<div style="font-style:italic; color:#555;">Message interval setting in LIGO Configurator</div>
</div>

== Exchange Protocol Description ==

The LLS protocol supports two types of exchange protocols: binary (HEX) and character view (transmission of ASCII sequences). It is recommended to use binary exchange protocol.

=== Format of Binary Protocol Messages ===

All the commands of the binary communication protocol have the same standardized format which is given in the table:

{| class="wikitable"
|-
! Sequential number of the field !! Field name !! Field size, byte !! Description
|-
| style="text-align:center;" | 1 || Prefix || style="text-align:center;" | 1 || The field is a marker of the message beginning shall have prefix 31h, and an outcoming messages shall be displayed with 3Eh prefix by the program.
|-
| style="text-align:center;" | 2 || Network address || style="text-align:center;" | 1 || For prefix 31h specify the network address of the recipient. <br>For prefix 3Eh specify the network address of the sender.
|-
| style="text-align:center;" | 3 || Operation code || style="text-align:center;" | 1 || For prefix 31h specify the code of operation which the program shall perform For Eh prefix specify the code of operation to which the response is given
|-
| style="text-align:center;" | 4 || Data || style="text-align:center;" | It depends on the operation code || Data composition and format of the field depends on the operation code
|-
| style="text-align:center;" | 5 || Checksum || style="text-align:center;" | 1 || The field is used to control over data integrity
|}

=== Single-Stage Data Reading (command 06h) ===

The command is designed for reading of the current data: relative level, temperature, frequency. The data are transmitted with a lower byte ahead.

==== Command format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | The checksum
|}

==== Response format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output (command 07h) ===

Command is designed to switch on periodic data output.

After the command is processed, the sensor starts sending data periodically — level, temperature, and frequency — with the time interval prescribed by the 13h command.

Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power power supply (if the data output mode is not istalled by default).

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Periodic data output format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output Interval Adjustment (13h command) ===

Command is designed to set up interval of periodic data output.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 0…255 || style="text-align:left;" | Interval of the data output in seconds
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Default Data Output Mode (command 17h) ===

This command determines the order of data output after the sensor is powered on or the processor is reset. After the power is on or the processor is reset, the program will send data periodically via the interface at the time interval prescribed by the 13h command.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="4" | +3 || rowspan="4" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The data are output in binary form
|-
| 02h || style="text-align:left;" | The data are output in character-coded form (ASCII mode)
|-
| 03h || style="text-align:left;" | The data are output in character-coded form (ASCII EXT mode)
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h…FFh || style="text-align:left;" | Checksum
|}

== Description of Commands for the Text-Based Protocol ==

Data exchange via the text-based protocol includes receipt and sending of ASCII symbols sequence interpreted and the request and response commands.

=== Reading the Data ===

The command is designed for reading of the current data: relative level, temperature, frequency. The command is a sequence of symbols ASCII "D" and "O". After receipt of the "DO" command the program will response in the form of ASCII symbols sequence.

For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. All values are in hexadecimal form.

In case the frequency value exceeds FFFh, the data are considered invalid.

=== Periodic Data Output ===

The command is designed to switch on periodic data output. After processing the command, the sensor performs periodic data output in the text-based form (ASCII codes) of the following data: relative level, temperature, frequency.

The data are being output periodically with an interval set up when cofiguring the sensor (LIGO Configurator software). In case the data output interval is set to zero, the data output won't be performed.

Switching on of the periodic data output is done by sending of the "DP" symbols in line. After processing of the command, the symbols line will be received. For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power supply.

== Checksum Calculation Algorithm ==

The checksum is calculated using Dallas APPLICATION NOTE 27 table method: ''Understanding and Using Cyclic Redundancy Checks with Dallas Semiconductor iButton Products''. One can use the following algorithms to calculate the checksum with a polynom <code>x^8 + x^5 + x^4 + 1</code> (C language):

<syntaxhighlight lang="c" line>
U8 CRC8(U8 data, U8 crc)
{
U8 i = data ^ crc;
crc = 0;
if (i & 0x01) crc ^= 0x5e;
if (i & 0x02) crc ^= 0xbc;
if (i & 0x04) crc ^= 0x61;
if (i & 0x08) crc ^= 0xc2;
if (i & 0x10) crc ^= 0x9d;
if (i & 0x20) crc ^= 0x23;
if (i & 0x40) crc ^= 0x46;
if (i & 0x80) crc ^= 0x8c;
return crc;
}
</syntaxhighlight>

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO BLE ]]

Category:LIGO PRO BLE Protocol

2026-06-24T10:56:18Z

Admin: Auto-created category for LIGO PRO BLE Protocol

{{DEFAULTSORT:05 LIGO PRO BLE Protocol}}

[[Category:LIGO PRO BLE]]

LIGO PRO BLE Protocol

2026-06-24T10:56:18Z

Admin: Create page

LIGO AIR Protocol

2026-06-24T10:55:44Z

Admin: Initial Release [release]

== 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:''' <code>0x0CFFFC0D024D0100241F000600</code>

{| class="wikitable" style="width:100%;"
|-
! Sequence number of bytes !! Description !! Example
|-
| 0 || Length of field || <code>0x0C</code>
|-
| +1 || Type of field (Manufacturer data) || Always <code>0xFF</code>
|-
| +2 || Company ID || <code>0x0DFC</code>
|-
| +4 || Hardware ID (type of device) || <code>0x02</code> — LIGO Air |
|-
| +5 and further || Payload (sensor parameters) || <code>0x4D0100241F000600</code>
|}

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.

{| class="wikitable"
|-
! Byte of Hardware ID !! Type of Hardware
|-
| <code>0x02</code> || LIGO Air
|-
| <code>0x03</code> || LIGO Air Pro
|}

''The list of hardware may be expanded.''

'''Payload data format of LIGO AIR (Hardware ID <code>0x02</code>) and LIGO AIR Pro (Hardware ID <code>0x03</code>).'''

LIGO Air and LIGO Air Pro have the same payload data format. The structure of the payload is listed in the table below:

{| class="wikitable" style="width:100%;"
|-
! Sequence number of bytes !! Parameter type !! Parameter length (bytes) !! Range !! Unit of measurement
|-
| 0 || Fuel level || 2 || 0 to 1023 (option), <br>0 to 4095 (default), <br>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 <br>1: Storage Mode
|}

'''Example Payload data:''' <code>0x4D0100241F000600</code>
{| style="border-collapse:collapse;margin:0 auto;text-align:center;font-family:Arial,sans-serif;font-size:11pt;"
|-
| style="border:none;background:transparent;" |
| colspan="7" style="border:none;background:transparent;padding:0 0 6px 0;font-size:50pt;font-family:Consolas,'Courier New',monospace;font-weight:bold;letter-spacing:1px;text-align:center;" | <span style="color:#222">0x</span><span style="color:#5E7440">4D01</span><span style="color:#C99D3F">00</span><span style="color:#3170A8">24</span><span style="color:#1F2D52">1F</span><span style="color:#6E408A">00</span><span style="color:#1A1A1A">06</span><span style="color:#7BC571">00</span>
|-
| style="border:none;background:transparent;" |
! style="background:#5E7440;color:#fff;padding:10px 18px;font-weight:bold;min-width:80px;" | 4D01
! style="background:#C99D3F;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | NA
! style="background:#3170A8;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 24
! style="background:#1F2D52;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 1F
! style="background:#6E408A;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | NA
! style="background:#1A1A1A;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 06
! style="background:#7BC571;color:#fff;padding:10px 18px;font-weight:bold;min-width:50px;" | 00
|-
| style="border:none;background:transparent;" |
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Fuel level
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Reserved
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Battery voltage
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Temperature
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Reserved
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Firmware version
| style="border:1px solid #d0d0d0;padding:8px 12px;background:#fafafa;" | Operation Mode
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to little-endian (hex)
| style="padding:6px 12px;" | 014D
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 24
| style="padding:6px 12px;" | 1F
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 06
| style="padding:6px 12px;" | 00
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to decimal
| style="padding:6px 12px;" | 333
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 36
| style="padding:6px 12px;" | 31
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 006
| style="padding:6px 12px;" | 0
|-
| style="text-align:right;padding:6px 14px 6px 0;font-style:italic;color:#333;border:none;background:transparent;white-space:nowrap;" | Convert to value
| style="padding:6px 12px;" | 333 (unit or liter)
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 3.6 Volt
| style="padding:6px 12px;" | 31 ºC
| style="padding:6px 12px;" | NA
| style="padding:6px 12px;" | 0.0.6
| style="padding:6px 12px;" | Working mode
|}

<div class="noprint">

== Related Documents ==
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO AIR ]]

Category:LIGO AIR Protocol

2026-06-24T10:55:35Z

Admin: Auto-created category for LIGO AIR Protocol

{{DEFAULTSORT:05 LIGO AIR Protocol}}

[[Category:LIGO AIR]]

LIGO AIR Protocol

2026-06-24T10:55:35Z

Admin: Create page

MediaWiki:Common.js

2026-06-24T10:55:05Z

Admin: Update

LIGO PRO 2 Protocol

2026-06-24T10:52:21Z

Admin: Initial Release [release]

== General Introduction ==

LLS Protocol is used in LIGO RS232 / RS485 fuel level sensor with the following parameters:

* Baud rate: 2400,4800,9600,19200,38400,115200 (can be configured by software on PC)
* Data bits: 8
* Parity: None
* Stop bits: 1
* Flow control: None

LIGO fuel level sensor has 2 working modes:

# '''Slave mode:''' In this mode, the sensor will respond to all requests from the external device (master device). Each sensor in the network will be distinguished by different addresses configured with the LIGO Configurator software
# '''Master mode:''' In this mode the sensor will automatically send data to the external device with a preset interval (message interval)

To enable this mode on the LIGO Configurator software, do the following:

* Automatic transmission: select HEX (binary) or ASCII or ASCII EXT

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Automatic-Transmission.png|frameless|219px]]
<div style="font-style:italic; color:#555;">Automatic transmission setting in LIGO Configurator</div>
</div>

* Set the time of each transfer (Message interval)

<div style="text-align:center;">
[[File:LLS-Protocol-Configurator-Message-Interval.png|frameless|228px]]
<div style="font-style:italic; color:#555;">Message interval setting in LIGO Configurator</div>
</div>

== Exchange Protocol Description ==

The LLS protocol supports two types of exchange protocols: binary (HEX) and character view (transmission of ASCII sequences). It is recommended to use binary exchange protocol.

=== Format of Binary Protocol Messages ===

All the commands of the binary communication protocol have the same standardized format which is given in the table:

{| class="wikitable"
|-
! Sequential number of the field !! Field name !! Field size, byte !! Description
|-
| style="text-align:center;" | 1 || Prefix || style="text-align:center;" | 1 || The field is a marker of the message beginning shall have prefix 31h, and an outcoming messages shall be displayed with 3Eh prefix by the program.
|-
| style="text-align:center;" | 2 || Network address || style="text-align:center;" | 1 || For prefix 31h specify the network address of the recipient. <br>For prefix 3Eh specify the network address of the sender.
|-
| style="text-align:center;" | 3 || Operation code || style="text-align:center;" | 1 || For prefix 31h specify the code of operation which the program shall perform For Eh prefix specify the code of operation to which the response is given
|-
| style="text-align:center;" | 4 || Data || style="text-align:center;" | It depends on the operation code || Data composition and format of the field depends on the operation code
|-
| style="text-align:center;" | 5 || Checksum || style="text-align:center;" | 1 || The field is used to control over data integrity
|}

=== Single-Stage Data Reading (command 06h) ===

The command is designed for reading of the current data: relative level, temperature, frequency. The data are transmitted with a lower byte ahead.

==== Command format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | The checksum
|}

==== Response format: ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 06h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output (command 07h) ===

Command is designed to switch on periodic data output.

After the command is processed, the sensor starts sending data periodically — level, temperature, and frequency — with the time interval prescribed by the 13h command.

Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power power supply (if the data output mode is not istalled by default).

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of recipient
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Periodic data output format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 07h || style="text-align:left;" | Operation code
|-
| +3 || 1 || -128…127 || style="text-align:left;" | Temperature in in degrees Celsius
|-
| +4 || 2 || 0000h…FFFFh || style="text-align:left;" | Relative level
|-
| +6 || 2 || 0000h…FFFFh || style="text-align:left;" | Frequency value
|-
| +8 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Periodic Data Output Interval Adjustment (13h command) ===

Command is designed to set up interval of periodic data output.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| +3 || 1 || 0…255 || style="text-align:left;" | Interval of the data output in seconds
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 3Eh || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | The Network address of the sender
|-
| +2 || 1 || 13h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

=== Default Data Output Mode (command 17h) ===

This command determines the order of data output after the sensor is powered on or the processor is reset. After the power is on or the processor is reset, the program will send data periodically via the interface at the time interval prescribed by the 13h command.

==== Command format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="4" | +3 || rowspan="4" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The data are output in binary form
|-
| 02h || style="text-align:left;" | The data are output in character-coded form (ASCII mode)
|-
| 03h || style="text-align:left;" | The data are output in character-coded form (ASCII EXT mode)
|-
| +4 || 1 || 00h..FFh || style="text-align:left;" | Checksum
|}

==== Response format ====

{| class="wikitable" style="text-align:center;"
|-
! Offset, bytes !! Field size, bytes !! Value !! Description
|-
| 0 || 1 || 31h || style="text-align:left;" | Prefix
|-
| +1 || 1 || 00h..FFh || style="text-align:left;" | Network address of the recipient
|-
| +2 || 1 || 17h || style="text-align:left;" | Operation code
|-
| rowspan="2" | +3 || rowspan="2" | 1 || 00h || style="text-align:left;" | The command has been executed successfully
|-
| 01h || style="text-align:left;" | The command cannot be executed
|-
| +4 || 1 || 00h…FFh || style="text-align:left;" | Checksum
|}

== Description of Commands for the Text-Based Protocol ==

Data exchange via the text-based protocol includes receipt and sending of ASCII symbols sequence interpreted and the request and response commands.

=== Reading the Data ===

The command is designed for reading of the current data: relative level, temperature, frequency. The command is a sequence of symbols ASCII "D" and "O". After receipt of the "DO" command the program will response in the form of ASCII symbols sequence.

For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. All values are in hexadecimal form.

In case the frequency value exceeds FFFh, the data are considered invalid.

=== Periodic Data Output ===

The command is designed to switch on periodic data output. After processing the command, the sensor performs periodic data output in the text-based form (ASCII codes) of the following data: relative level, temperature, frequency.

The data are being output periodically with an interval set up when cofiguring the sensor (LIGO Configurator software). In case the data output interval is set to zero, the data output won't be performed.

Switching on of the periodic data output is done by sending of the "DP" symbols in line. After processing of the command, the symbols line will be received. For example, F=0AF9 t=1A N=03FF.0 <CR><LF>, where F is the current frequency value, t is the current value of temperature in Celcius degrees, N is the level value. Turning off of the periodic data output is performed after receipt of any true command, reset of the processor or disconnection of power supply.

== Checksum Calculation Algorithm ==

The checksum is calculated using Dallas APPLICATION NOTE 27 table method: ''Understanding and Using Cyclic Redundancy Checks with Dallas Semiconductor iButton Products''. One can use the following algorithms to calculate the checksum with a polynom <code>x^8 + x^5 + x^4 + 1</code> (C language):

<syntaxhighlight lang="c" line>
U8 CRC8(U8 data, U8 crc)
{
U8 i = data ^ crc;
crc = 0;
if (i & 0x01) crc ^= 0x5e;
if (i & 0x02) crc ^= 0xbc;
if (i & 0x04) crc ^= 0x61;
if (i & 0x08) crc ^= 0xc2;
if (i & 0x10) crc ^= 0x9d;
if (i & 0x20) crc ^= 0x23;
if (i & 0x40) crc ^= 0x46;
if (i & 0x80) crc ^= 0x8c;
return crc;
}
</syntaxhighlight>

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO 2]]

Category:LIGO PRO 2 Protocol

2026-06-24T10:52:11Z

Admin: Auto-created category for LIGO PRO 2 Protocol

{{DEFAULTSORT:05 LIGO PRO 2 Protocol}}

[[Category:LIGO PRO 2]]

LIGO PRO 2 Protocol

2026-06-24T10:52:11Z

Admin: Create page

MediaWiki:Common.js

2026-06-24T10:51:32Z

Admin: Update

LIGO PRO 2 Datasheet

2026-06-24T10:45:32Z

Admin: Initial Release [release]

== Product Overview ==

The Ligo PRO 2 Fuel Level Sensor is produced and developed by SOJI Electronics JSC. The device is designed to measure the level of liquid fuel and other non-conductive liquids in vehicle tanks and stationary fuel storage, applicable across different fields. The measured values are transmitted to an external device as output signals such as Analog, Frequency, RS232, or RS485.

Ligo PRO 2 was created to satisfy the increasing demand of the transport telematics market for improved reliability of design, data accuracy, and ease of installation. The sensor is integrated with Bluetooth Low Energy (BLE) making installation more convenient, easier, and faster.

In addition, the heavy-duty metal structure helps increase protection against electrostatic, electromagnetic and conducted interference. The Ligo PRO 2 is also designed with IP69K waterproof standards and superior shock and vibration resistance.

== Key Features ==

*High accuracy up to 99.5%
*Wide range input voltage: 6-40V
*Galvanic isolation up to 2500V
*Configurable length up to 6000mm
*Operating temperature: -40°C to +85°C
*Built-in anti-mud oil filter and anti-vibration springs
*IP69K waterproof standard
*Integrated BLE technology for smartphone configuration

== Applications ==

*Trucks, excavators, heavy construction machines
*Marine vessels and electric generators
*Off-highway machinery including high-temperature and vibration environments
*Industrial oil storage tanks or stationary storage tanks

== Product Variants / Ordering Information ==

== Technical Specifications ==

{| class="wikitable" style="text-align:center;"
|-
! Parameter !! AF !! RS232 !! RS485
|-
| style="text-align:left;" | Standard length (L), mm || colspan="3" | 700, 1000, 1500 ... up to 6000 mm
|-
| style="text-align:left;" | Measuring error, % || colspan="3" | ± 0.5 %
|-
| style="text-align:left;" | Output signal || Analog (0-9V) || RS232 || RS485
|-
| style="text-align:left;" | Baud rate, bit/sec || colspan="3" | 2400, 4800, 9600, 19200, 38400, 57600, 115200
|-
| style="text-align:left;" | Power supply (DC input voltage, V) || colspan="3" | 6-40V
|-
| style="text-align:left;" | Supply protection (Over-voltage 100 VDC for 2 min. Reverse polarity) || colspan="3" | Yes
|-
| style="text-align:left;" | Maximum power consumption, mA || colspan="3" | 20
|-
| style="text-align:left;" | Waterproof standard (IP) || colspan="3" | IP69K
|-
| style="text-align:left;" | Operating temperature, °C || colspan="3" | -40 ... +85
|-
| style="text-align:left;" | Maximum allowed humidity level, % || colspan="3" | 100
|-
| style="text-align:left;" | Resolution, bit || colspan="3" | 12
|-
| style="text-align:left;" | Output range (min level) || Analog (0...8V) || 0 || 0
|-
| style="text-align:left;" | Output range (max level) || Analog (1...9V) || 4095 || 4095
|-
| style="text-align:left;" | Average sampling period, s || colspan="3" | 0 ... 255
|-
| style="text-align:left;" | Message interval, s || Continuous || 1 ... 255 || 1 ... 255
|-
| style="text-align:left;" | Absolute error in temperature measurement, °C || colspan="3" | ±1
|-
| style="text-align:left;" | Bluetooth specs || colspan="3" | Bluetooth 5.1, IEEE 802.15.4-2006, 2.4 GHz, -95 dBm sensitivity, +8 dBm TX Power
|-
| style="text-align:left;" | Average service life, years (expected) || colspan="3" | 10
|}

=== Dimensions ===

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig1-dimensions.jpg|frameless|915px]]
<div style="font-style:italic; color:#555;">Figure 1. Ligo PRO 2 overall dimensions (cm)</div>
</div>

=== Wiring Connection ===

==== AF (Analog & Frequency) ====

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig2-wiring-AF.png|frameless|892px]]
<div style="font-style:italic; color:#555;">Figure 2. Wiring diagram – Analog and Frequency output signals</div>
</div>

==== RS232 ====

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig3-wiring-RS232.png|frameless|903px]]
<div style="font-style:italic; color:#555;">Figure 3. Wiring diagram – RS232 output signals</div>
</div>

==== RS485 ====

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig4-wiring-RS485.png|frameless|867px]]
<div style="font-style:italic; color:#555;">Figure 4. Wiring diagram – RS485 output signals</div>
</div>

=== Connector ===

<div style="text-align:center;">
[[File:LIGO-PRO-2-fig5-connector.png|frameless|703px]]
<div style="font-style:italic; color:#555;">Figure 5. Connector pin details</div>
</div>

==== AF / RS232 Pinout ====

{| class="wikitable" style="text-align:center;"
|-
! Pin !! Description !! Wire Color
|-
| 1 || GND || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div>
|-
| 2 || NC (Not connected) || NC
|-
| 3 || VCC (6-40V) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div>
|-
| 4 || TXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div>
|-
| 5 || Analog Output || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#fff;border:1px solid #999;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">White</span></div>
|-
| 6 || RXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#7b3f00;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Brown</span></div>
|}

==== RS485 Pinout ====

{| class="wikitable" style="text-align:center;"
|-
! Pin !! Description !! Wire Color
|-
| 1 || GND || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#000;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Black</span></div>
|-
| 2 || RS485 (B) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#2e8b2e;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Green</span></div>
|-
| 3 || VCC (6-40V) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#d63a3a;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Red</span></div>
|-
| 4 || TXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#3b8dd9;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Blue</span></div>
|-
| 5 || RS485 (A) || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#f4d03f;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Yellow</span></div>
|-
| 6 || RXD || <div style="display:flex;align-items:center;justify-content:center;gap:8px;"><span style="display:inline-block;width:32px;height:14px;background:#7b3f00;"></span><span style="min-width:60px;text-align:left;font-weight:bold;">Brown</span></div>
|}

== Compliance and Certifications ==
Refer to [[LIGO PRO 2 Certification & Approvals]] for current certificate status.

<div class="noprint">

== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO 2 ]]

Category:LIGO PRO 2 Datasheet

2026-06-24T10:45:23Z

Admin: Auto-created category for LIGO PRO 2 Datasheet

{{DEFAULTSORT:05 LIGO PRO 2 Datasheet}}

[[Category:LIGO PRO 2]]

LIGO PRO 2 Datasheet

2026-06-24T10:45:23Z

Admin: Create page

== Product Overview ==
<div class="dim">

''Brief 1–2 paragraph introduction to the product per IEC/IEEE 82079-1.''

'''What to fill in:'''
* Product name, category, primary function
* Key technology and target environment
* Value proposition for B2B customers

'''Example structure:''' "The [Product Name] is a [type] device designed for [primary application]. It features [key technology] and is built for [target environment]."

</div>

== Key Features ==
<div class="dim">

''Bullet list of top 5–7 differentiating features.''

'''What to fill in:'''
* Each bullet = 1 key feature with measurable value
* Focus on: accuracy, connectivity, durability, compatibility
* Examples of features to cover:
** Measurement specifications (accuracy, range, response time)
** Connectivity (Bluetooth/WiFi/Cellular protocol + version)
** Power (battery life, voltage range)
** Environmental rating (IP, operating temperature)
** Compatibility (telematics platforms, software)

</div>

== Applications ==
<div class="dim">

''Typical use cases and industries the product serves.''

'''What to fill in:''' bullet list of applications (4–6 items)
* Each bullet = 1 specific industry/use case
* Common categories:
** Transportation/Fleet (trucks, buses, trailers)
** Telecom (backup generators, base stations)
** Industrial (storage tanks, process monitoring)
** Marine (bunker fuel, hydraulic systems)
** Mining (heavy equipment, refueling stations)

</div>

== Product Variants / Ordering Information ==
<div class="dim">

''Table of all product SKUs available for ordering.''

'''What to fill in:''' table with columns:
* '''Model''' — short product code (e.g., LIGO-AIR-STD)
* '''Part Number''' — internal SKU (e.g., SKU-001)
* '''Description''' — variant differences (cable length, certification, etc.)
* '''Region''' — geographic availability (Global, EU/APAC, US only, etc.)

'''Common variants:''' Standard / Extended / Industrial-grade / ATEX-certified

</div>

== Technical Specifications ==
<div class="dim">

''Detailed technical parameters of the product.''

'''What to fill in:''' specification table with columns Parameter / Value / Unit / Descriptions

'''Parameters to cover:'''
* '''Electrical''': Operating voltage, Operating current (avg/peak/sleep), Power consumption
* '''Performance''': Measurement range, Accuracy, Resolution, Response time, Sampling rate
* '''Wireless''' (if applicable): Protocol, Frequency band, Output power, Receiver sensitivity, Range
* '''Environmental''': Operating temperature, Storage temperature, Humidity, Ingress protection (IP)
* '''Mechanical''': Dimensions (L × W × H), Weight, Mounting interface
* '''Service life''': Expected years at typical operation

'''Optional sub-sections:''' If product has many specs, split into <code><nowiki>=== Performance ===</nowiki></code>, <code><nowiki>=== Electrical ===</nowiki></code>, <code><nowiki>=== Wireless ===</nowiki></code>, <code><nowiki>=== Environmental ===</nowiki></code>, <code><nowiki>=== Memory ===</nowiki></code>, <code><nowiki>=== Mechanical Dimensions ===</nowiki></code>, <code><nowiki>=== Interface / Connectivity ===</nowiki></code>, each with its own table.

</div>

== Compliance and Certifications ==
<div class="dim">

''Regulatory certifications and standards compliance.''

'''What to fill in (sub-sections):'''

* '''Wireless / Radio''' — bullet list of certifications by region:
** CE RED (EU) — certificate number
** FCC Part 15 (US) — FCC ID
** IC (Canada) — IC number
** Bluetooth SIG QDID (if BLE)
** RoHS 3

* '''Environmental''' — standards compliance:
** RoHS 3 (Directive 2015/863/EU)
** REACH (EC 1907/2006)
** WEEE (Directive 2012/19/EU)
** IP rating per IEC 60529

* '''Mechanical / Safety''' — test standards:
** IEC 60068-2-6 — Vibration
** IEC 60068-2-27 — Shock
** IEC 60068-2-30 — Damp heat
** IEC 61010-1 — Electrical safety

* '''Industry-Specific''' (remove if N/A):
** ATEX / IECEx — for hazardous environments
** MID — Measuring Instruments Directive
** Automotive E-Mark — for vehicle applications
** Marine certification — DNV / ABS / Lloyd's Register

* '''Warranty''':
** Standard warranty period (years from shipment)
** Extended warranty options
** NOT covered items
** Void conditions
** Cross-reference to [[Warranty Terms and Conditions]]

</div>
<div class="noprint">
== Related Documents ==
''Cross-references to other documents.''
{{RelatedDocuments}}
</div>

== Revision History ==
<div class="revision-history-auto">
<span class="dim">Loading revision history...</span>
</div>

[[Category:LIGO PRO 2 ]]

LIGO PRO 2 User Guide

2026-06-24T10:44:27Z

Admin: Initial Release [release]

Category:LIGO PRO 2 User Guide

2026-06-24T10:44:14Z

Admin: Auto-created category for LIGO PRO 2 User Guide

{{DEFAULTSORT:05 LIGO PRO 2 User Guide}}

[[Category:LIGO PRO 2]]