ESCORT TD-150 FUEL SENSOR: Difference between revisions
No edit summary |
No edit summary |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
== Product Specification == | == Product Specification == | ||
[[File:Escort.png|right|280px]] | |||
{| class="wikitable" style="width: | {| class="wikitable" style="width: 50%;" | ||
! style="background-color:#800020; white-space:nowrap; color:white;" | Parameter | ! style="background-color:#800020; white-space:nowrap; color:white;" | Parameter | ||
! style="background-color:#800020; white-space:nowrap; color:white;" | Value | ! style="background-color:#800020; white-space:nowrap; color:white;" | Value | ||
| Line 32: | Line 32: | ||
|- | |- | ||
| Weight (kg) || 0.35 + 0.4 × L (L = sensor length in meters) | | Weight (kg) || 0.35 + 0.4 × L (L = sensor length in meters) | ||
|- | |||
| Supported by || <div class="mw-collapsible mw-collapsed"> <div class="mw-collapsible-content"><p> | |||
DISCOVERY-126A, DISCOVERY-226A, DISCOVERY-296A</p> | |||
|} | |} | ||
| Line 50: | Line 53: | ||
|} | |} | ||
== | ==Configuration Guide== | ||
This guide outlines how to configure the RS485-based ESCORT 485 fuel sensor on '''Transight Telematics''' devices using commands. | |||
== Step 1: Select and Enable the Fuel Sensor Type == | |||
Defines the sensor model and number of sensors. | |||
'''• Command Format''' | |||
<pre> | |||
SET CUFUELTYPE:<Sensor Model>,<Number of Sensors> | |||
</pre> | |||
'''• Example''' | |||
<pre> | |||
SET CUFUELTYPE:ESCORT485,1 | |||
</pre> | |||
'''• Expected Response''' | |||
<pre> | |||
IMEI: 862942074896044 | |||
Command: SET CUFUELTYPE:ESCORT485,1 | |||
Response: ESCORT485, | |||
Error : 0 | |||
</pre> | |||
'''• Verification Command''' | |||
<pre> | <pre> | ||
GET CUFUELTYPE | |||
</pre> | </pre> | ||
'''• Expected Response''' | |||
<pre> | |||
IMEI: 862942074896044 | |||
Command: GET CUFUELTYPE | |||
Response: ESCORT485,1 | |||
== | Error : 0 | ||
</pre> | |||
== Step 2: Configure Fuel Sensor Communication Parameters == | |||
Set communication mode and output settings. | |||
'''• Command Format''' | |||
<pre> | <pre> | ||
SET | SET CUFUELDATACFG:<Sensor>,<Index>,<Network Address>,<Mode>,<Filter Type>,<Filter>,<Interval> | ||
</pre> | </pre> | ||
'''• Example''' | |||
<pre> | |||
SET CUFUELDATACFG:ESCORT,1,00,PASSIVE1023,SMART,SMART_0 | |||
</pre> | |||
'''• Expected Response''' | |||
<pre> | |||
IMEI: 862942074896044 | |||
Command: SET CUFUELDATACFG:ESCORT,1,00,PASSIVE1023,SMART,SMART_0 | |||
Response: | |||
Error : 0 | |||
</pre> | |||
'''• Verification Command''' | |||
<pre> | |||
GET CUFUELDATACFG:ESCORT,1 | |||
</pre> | |||
'''• Expected Response''' | |||
<pre> | |||
IMEI: 862942074896044 | |||
Command: GET CUFUELDATACFG:ESCORT,1 | |||
Response: Mode: 0, Address: 0, Filter Type: 0, Filter: 0 Interval: 0 | |||
Error : 0 | |||
</pre> | |||
== Parameter Reference Table == | |||
{| class="wikitable" | |||
! style="background-color:#680022; color:white;" | Parameter | |||
! style="background-color:#680022; color:white;" | Value Example | |||
! style="background-color:#680022; color:white;" | Description | |||
|- | |||
| Param1 || ESCORT || Sensor type identifier | |||
|- | |||
| Param2 || Index = 1 || Defines sensor instance (1 to 3 supported) | |||
|- | |||
| Param2 || Network Address = 0x01 || RS485 address (0x00 to 0xE7) | |||
|- | |||
| Param3 || Mode = PASSIVE1023 || Modes: PASSIVE / FREQUENCY / PERIODIC with 1023 or 4095 resolution | |||
|- | |||
| Param4 || Filtertype = SMART || Type of filtering: SMART or MEDIAN | |||
|- | |||
| Param5 || Filter = SMART_0 || Filter preset: SMART_UPTO_200, SMART_200_1000, MEDIAN_0 to MEDIAN_9 | |||
|- | |||
| Param6 || Output interval = 10 || Time between sensor readings (in seconds) | |||
|} | |||
== Step 3: Set Fuel Sensor Output Interval == | |||
Configures periodic data transmission interval. | |||
'''• Command Format''' | |||
<pre> | |||
SET CUFUELMODE:<SENSOR INDEX>,<Mode (1=Request, 0=Periodic)>,<Interval> | |||
</pre> | |||
'''• Example''' | |||
<pre> | |||
SET CUFUELMODE:1,1,15 | |||
</pre> | |||
'''• Expected Response''' | |||
<pre> | |||
IMEI: 862942074896044 | |||
Command: SET CUFUELMODE:1,1,15 | |||
Response: | |||
Error : 0 | |||
</pre> | |||
== ⚠️ Mandatory Save Command == | |||
After completing all configurations, save them with: | |||
<pre> | |||
SET CUMR:2 | |||
</pre> | |||
==Step 4: Verify Fuel Data Transmission == | |||
Once configured, the device will transmit fuel data via telemetry. | |||
'''🔍 Validation Checklist''' | |||
* Monitor incoming telemetry on your server | |||
* Confirm: | |||
** Fuel level values are present | |||
** Values update periodically | |||
** Readings are consistent and accurate | |||
===Product Link=== | |||
[[https://www.fmeter.ru/en/produktsiya/datchik-urovnja-topliva/eskort-td-150/ Escort FLS]] | |||
Latest revision as of 06:07, 22 October 2025
Introduction to the Product
The sensor ESCORT TD-150 determines the fill level of light oils in reservoirs (storage tanks). It is used as a fuel sensor in the automotive engineering field, and also as a level sensor for any light oils in industrial applications. The sensor converts the calculated fuel level into a digital code, frequency, or analog signals. It is a complete, finished solution.
To ensure explosion protection, it is necessary to connect a resistor of the appropriate rating to the power supply circuit. The presence of a resistor depends on the scope of delivery.
Product Specification

| Parameter | Value |
|---|---|
| Power supply voltage | 7 – 80 V |
| Current, no more | 30 mA |
| Reduced measurement error in the effective range | up to 1% UML22 |
| Operating modes | Digital, Frequency, Analog |
| Sensitivity (Receiver / Transmitter) | -96 dBm / 4 dBm |
| Operating frequency range (BLE) | 2.402 – 2.480 GHz |
| Ambient temperature | -45 to +50 °C |
| Extreme ambient temperature | -60 to +85 °C |
| Air pressure | 84 – 106.7 kPa |
| Suitable for explosion hazardous areas | Zones 0, 1, and 2 |
| Weight (kg) | 0.35 + 0.4 × L (L = sensor length in meters) |
| Supported by | DISCOVERY-126A, DISCOVERY-226A, DISCOVERY-296A |
Wiring Information
| Wire Color | Function |
|---|---|
| Red | Power |
| Black | GND |
| Orange | RS485 A |
| White | RS485 B |
Configuration Guide
This guide outlines how to configure the RS485-based ESCORT 485 fuel sensor on Transight Telematics devices using commands.
Step 1: Select and Enable the Fuel Sensor Type
Defines the sensor model and number of sensors.
• Command Format
SET CUFUELTYPE:<Sensor Model>,<Number of Sensors>
• Example
SET CUFUELTYPE:ESCORT485,1
• Expected Response
IMEI: 862942074896044 Command: SET CUFUELTYPE:ESCORT485,1 Response: ESCORT485, Error : 0
• Verification Command
GET CUFUELTYPE
• Expected Response
IMEI: 862942074896044 Command: GET CUFUELTYPE Response: ESCORT485,1 Error : 0
Step 2: Configure Fuel Sensor Communication Parameters
Set communication mode and output settings.
• Command Format
SET CUFUELDATACFG:<Sensor>,<Index>,<Network Address>,<Mode>,<Filter Type>,<Filter>,<Interval>
• Example
SET CUFUELDATACFG:ESCORT,1,00,PASSIVE1023,SMART,SMART_0
• Expected Response
IMEI: 862942074896044 Command: SET CUFUELDATACFG:ESCORT,1,00,PASSIVE1023,SMART,SMART_0 Response: Error : 0
• Verification Command
GET CUFUELDATACFG:ESCORT,1
• Expected Response
IMEI: 862942074896044 Command: GET CUFUELDATACFG:ESCORT,1 Response: Mode: 0, Address: 0, Filter Type: 0, Filter: 0 Interval: 0 Error : 0
Parameter Reference Table
| Parameter | Value Example | Description |
|---|---|---|
| Param1 | ESCORT | Sensor type identifier |
| Param2 | Index = 1 | Defines sensor instance (1 to 3 supported) |
| Param2 | Network Address = 0x01 | RS485 address (0x00 to 0xE7) |
| Param3 | Mode = PASSIVE1023 | Modes: PASSIVE / FREQUENCY / PERIODIC with 1023 or 4095 resolution |
| Param4 | Filtertype = SMART | Type of filtering: SMART or MEDIAN |
| Param5 | Filter = SMART_0 | Filter preset: SMART_UPTO_200, SMART_200_1000, MEDIAN_0 to MEDIAN_9 |
| Param6 | Output interval = 10 | Time between sensor readings (in seconds) |
Step 3: Set Fuel Sensor Output Interval
Configures periodic data transmission interval.
• Command Format
SET CUFUELMODE:<SENSOR INDEX>,<Mode (1=Request, 0=Periodic)>,<Interval>
• Example
SET CUFUELMODE:1,1,15
• Expected Response
IMEI: 862942074896044 Command: SET CUFUELMODE:1,1,15 Response: Error : 0
⚠️ Mandatory Save Command
After completing all configurations, save them with:
SET CUMR:2
Step 4: Verify Fuel Data Transmission
Once configured, the device will transmit fuel data via telemetry.
🔍 Validation Checklist
- Monitor incoming telemetry on your server
- Confirm:
- Fuel level values are present
- Values update periodically
- Readings are consistent and accurate