ITALON FUEL SENSOR: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 23: | Line 23: | ||
| Measurement range of digital interface | | Measurement range of digital interface | ||
| 0…4095 | | 0…4095 | ||
|- | |||
| Supported by || <div class="mw-collapsible mw-collapsed"> <div class="mw-collapsible-content"><p> | |||
DISCOVERY-126A, DISCOVERY-226A, DISCOVERY-296A,</p> | |||
|} | |} | ||
| Line 53: | Line 56: | ||
'''🔹 Command Format''' | '''🔹 Command Format''' | ||
<pre> | <pre> | ||
SET CUFUELTYPE:<Sensor Model>,<Number of Sensors> | SET CUFUELTYPE:<Sensor Model>,<Number of Sensors> | ||
</pre> | </pre> | ||
| Line 59: | Line 61: | ||
'''🔹 Example''' | '''🔹 Example''' | ||
<pre> | <pre> | ||
SET CUFUELTYPE:OMNICOM485,1 | SET CUFUELTYPE:OMNICOM485,1 | ||
</pre> | </pre> | ||
| Line 65: | Line 66: | ||
'''🔹 Expected Response''' | '''🔹 Expected Response''' | ||
<pre> | <pre> | ||
IMEI: 862942074896044 | IMEI: 862942074896044 | ||
Command: SET CUFUELTYPE:OMNICOM485,1 | Command: SET CUFUELTYPE:OMNICOM485,1 | ||
Response: OMNICOM485, | Response: OMNICOM485, | ||
Error: 0 | Error: 0 | ||
</pre> | </pre> | ||
| Line 77: | Line 74: | ||
'''🔹 Verification Command''' | '''🔹 Verification Command''' | ||
<pre> | <pre> | ||
GET CUFUELTYPE | GET CUFUELTYPE | ||
</pre> | </pre> | ||
| Line 83: | Line 79: | ||
'''🔹 Expected Verification Response''' | '''🔹 Expected Verification Response''' | ||
<pre> | <pre> | ||
IMEI: 862942074896044 | IMEI: 862942074896044 | ||
Command: GET CUFUELTYPE | Command: GET CUFUELTYPE | ||
Response: OMNICOM485,1 | Response: OMNICOM485,1 | ||
Error: 0 | Error: 0 | ||
</pre> | </pre> | ||
== Step 2: Configure Fuel Sensor Communication Parameters == | == Step 2: Configure Fuel Sensor Communication Parameters == | ||
| Line 182: | Line 174: | ||
After completing configuration, execute this command to save settings: | After completing configuration, execute this command to save settings: | ||
<pre> | <pre> | ||
SET CUMR:2 | |||
</pre> | |||
== Step 3: Verify Fuel Data Transmission == | == Step 3: Verify Fuel Data Transmission == | ||
Latest revision as of 05:14, 22 October 2025
Introduction to the Product
ITALON Fuel Level Sensors (FLS) measure fuel level in fuel tanks of the vehicles and stationary objects. ITALON FLS are connected to GPS devices which in turn transfer all the data along with the fuel information to a server part of the solution.
| Parameter | Value |
|---|---|
| Error in measurement | ± 0.5% |
| Interface | RS-485 |
| Power supply voltage | 7…40V |
| Insulation breakdown protection | 2500V |
| Operating temperature | -40…+85°C |
| Measurement range of digital interface | 0…4095 |
| Supported by | DISCOVERY-126A, DISCOVERY-226A, DISCOVERY-296A, |
Wiring Information
| Wire Colour | Function |
|---|---|
| Brown | Power |
| White | GND |
| Orange | RS485A |
| Blue | RS485B |
Configuration Guide
This guide provides the configuration steps for RS485-based fuel sensors (e.g., OMNICOM485) with Transight Telematics devices using commands.
Step 1: Select and Enable the Fuel Sensor Type
Defines the fuel sensor model and how many sensors are connected.
🔹 Command Format
SET CUFUELTYPE:<Sensor Model>,<Number of Sensors>
🔹 Example
SET CUFUELTYPE:OMNICOM485,1
🔹 Expected Response
IMEI: 862942074896044 Command: SET CUFUELTYPE:OMNICOM485,1 Response: OMNICOM485, Error: 0
🔹 Verification Command
GET CUFUELTYPE
🔹 Expected Verification Response
IMEI: 862942074896044 Command: GET CUFUELTYPE Response: OMNICOM485,1 Error: 0
Step 2: Configure Fuel Sensor Communication Parameters
Defines communication mode, baud rate, address, output interval, and format.
🔹 Command Format
SET CUFUELDATACFG:<Sensor Model>,<Index>,<Mode>,<Baud Rate>,<Network Address>,<Output Interval>,<Output Format>,<Range>
Example
SET CUFUELDATACFG:OMNICOM,1,MASTER_BINARY,19200,02,12,BINARY,1023
🔹 Expected Response
IMEI: 862942074896044 Command: SET CUFUELDATACFG:OMNICOM,1,MASTER_BINARY,19200,02,12,BINARY,1023 Response: Error: 0
🔹 Verification Command
GET CUFUELDATACFG:OMNICOM,1
🔹 Expected Verification Response
IMEI: 862942074896044 Command: GET CUFUELDATACFG:OMNICOM,1 Response: Mode: 1, BaudRate: 19200, Address: 2, Interval: 12, Default Output: 1 Error: 0
Parameter Reference Table
| Parameter | Value Example | Description |
|---|---|---|
| <Sensor Model> | OMNICOM | Sensor type (OMNICOM485, TECHNO485, ESCORT485, OFF) |
| <Index> | 1 | Sensor index (0–3) |
| <Mode> | MASTER_BINARY | Communication mode: SLAVE, MASTER_BINARY, MASTER_ASCII |
| <Baud Rate> | 19200 | Communication speed (in bps) |
| <Network Address> | 02 | RS485 device address (Hexadecimal 00–FF) |
| <Output Interval> | 12 | Interval in seconds between sensor readings |
| <Output Format> | BINARY | Data format (BINARY or ASCII) |
| <Range> | 1023 | Raw value range of the sensor output (e.g., 1023 or 4095) |
⚠️ Mandatory Save Command
After completing configuration, execute this command to save settings:
SET CUMR:2
Step 3: Verify Fuel Data Transmission
After configuration, the device starts transmitting real-time fuel data via telemetry packets.
🔍 Validation Steps
- Monitor server-side data packets.
- Confirm:
- Fuel data values are present.
- Updates occur at the configured interval.
- Values are within the expected range.
Note: If fuel data does not appear in packets, recheck wiring and configuration.