Escort Knowledge Base - User contributions [en]

DU-BLE

2026-05-06T08:23:57Z

ANATOLYI: /* Vertical rotation control */

[[RU:DU-BLE| Русская версия]]
[[es:DU-BLE| Versión en español]]

= <big>'''Definition and purpose of the sensor'''</big> =
[[File:Current DU-BLE design.png|thumb|Current DU-BLE design]]
Definition and purpose of the sensor

The wireless angle sensor with autonomous power supply '''DU-BLE''' of the ESCORT trademark (hereinafter referred to as the measuring device, product, angle sensor, DU-BLE) is designed to measure the angular position of deflecting parts of various machines and mechanisms relative to the Earth's gravitational field, determine the direction of rotation (in the corresponding modes) and transmit this data via a radio channel at a frequency of 2.4 GHz.

The measuring device (sensor) "DU-BLE" is used in automotive equipment and other objects where angle measurement is required.

DU-BLE is a completely wireless sensor with autonomous power supply. Sensor data is transmitted in the form of Bluetooth packets in '''Advertising''' mode; the frequency of data sending is every 3 seconds.

More detailed technical specifications are presented in [https://www.fmeter.ru/download/_ftp/eng/datchik-ugla-naklona/eskort-du-ble/Escort%20DU-BLE%20datasheet.pdf?v=071220114144 the device's data sheet.]

= '''<big>Basic Terms and Concepts</big>''' =
'''Serial Number''' - a code consisting of a series of letters or numbers assigned to a product (sensor).

'''Sensor Name''' - sensor designation among BLE devices, consisting of the first two letters of the sensor model and the last 6 values of the '''serial number''', for example, DU_100100

'''MAC Address''' - a unique identifier assigned to each unit of active equipment. It is used to identify devices in the network.

'''Data Packet''' - a set of values transmitted by a device equipped with a Bluetooth transmitter, the structure of which is specified by the data transfer protocol.

'''Data Transfer Protocol''' - a set of specific rules or agreements of the logical level interface that determines the exchange of data between different programs or devices. In the case of the DU-BLE sensor, the Escort BLE protocol is used to transfer data packets.

'''Advertising Mode''' - a data transfer mode in which the device “distributes” data packets at a certain frequency, regardless of the presence of a device receiving the data.

'''Connection Mode''' - a data transfer mode in which the transmitter waits for a connection to the receiving device in order to start transmitting data packets.

'''BLE-RS485 base''' - a device that retransmits data transmission and converts it from a Bluetooth packet into a data packet transmitted via the RS-485 interface in accordance with the LLS protocol.

'''BA-BLE base''' - a device that retransmits data transmission and converts it from a Bluetooth packet into a data packet transmitted via the RS-485 and RS-232 interfaces in LLS and MODBUS protocols.

= '''<big>DU-BLE sensor's design</big>''' =

=== '''<big>First generation DU-BLE design</big>''' ===
[[File:Design DU-BLE first generation.png|800x800px]]

=== '''<big>Second generation DU-BLE design</big>''' ===
[[File:Design DU-BLE second generation.png|800x800px]]

= '''<big>Connecting sensor to a smartphone</big>''' =
To configure the DU-BLE sensor, calibrate it and calibrate the tank, you should use the Escort Configurator application, available on [https://apps.apple.com/ru/app/escort-sensor-configurator/id1483425085 iOS] and [https://play.google.com/store/apps/details?id=ru.fmeter.config Android] devices (hereinafter referred to as the “'''application'''” or "'''app'''").

== '''<big>Geolocation</big>''' ==
Launch the app and activate '''Bluetooth''' and '''geolocation''' on your smartphone also check if application have access to geolocation.

[[File:Screenshot_20240221-094919_One_UI_Home.png|664x664px]] [[File:Screenshot_20240221-095105_Permission_controller.png|667x667px]]

== '''<big>Connecting sensor</big>''' ==
[[File:Connecting to DU-BLE.gif]]

Press the '''Sensor Settings''' button. Next, select '''DU-BLE'''.

[[File:Sensor_settings._Main_page.png|frameless]] [[File:Selecting DU-BLE.png|666x666px]]

Find the required sensor by typing the last 6 digits of its serial number. You can find the serial number on the sensor head.

You can also simply select the required sensor from the list and click the '''Connect''' button. On an '''Android''' device, you can click on the sensors name, and a package of data received in '''advertising''' mode will be displayed.

[[File:Searching DU-BLE.png|675x675px]] [[File:Advertising DU-BLE.png|675x675px]]

== '''<big>Setting a password</big>''' ==
It is strongly recommend that you set a password on the sensor in order to restrict access to its settings. When you connect for the first time, the application will ask you to set a password automatically.

You can set, change and delete a password in the '''Additional Features'''.

[[File:Additional features DU-BLE.png|609x609px]]

Then, in the field that appears named "Password for changing settings", enter the password that you want be used later and click '''Enter'''.

[[File:TD-150_BLE_setting_password_.png|frameless]]<blockquote>'''<big>PLEASE NOTE THAT THE PASSWORD RESET PROCEDURE CAN BE VERY TIME-CONSUMING. WE RECOMMEND THAT YOU TAKE A RESPONSIBLE APPROACH IN SETTING YOUR PASSWORD AND SAVING IT.</big>'''</blockquote>'''<big>Also note that the password cannot start with 0.</big>'''

To delete a previously set password, you must enter it in the Password field, and then press the '''Enter''' and then the '''Delete''' buttons.

'''Attention!''' By default, there is no password set on the sensor! If you connected the sensor and a password was already set on it, contact technical support.

== '''<big>Main sensor parameters</big>''' ==

To see the main parameters of the sensor go to the '''Data''' tab. There you can see the following parameters:
# '''RSSI''' - Received signal strength indicator, which indicates how well your smartphone receives sent data. This parameter is not transmitted by the sensor, but is calculated by the receiving device
# '''Vbat''' or sensor battery charge (3.5V or higher indicates the battery is fully charged; 3.2V or lower indicates the battery is low and should be replaced)
# Sensor serial number
# Firmware version ('''FW''') installed in the sensor
# Current '''Operating mode''' set on the sensor
# The '''sensor's MAC address''' is used to connect the sensor to compatible external devices
# Current sensors readings in selected working mode
# Button for setting 0 as current angle of the sensor

[[File:DU-BLE Data.png|799x799px]]

'''The battery voltage drops to 3.2V for 10-15 seconds''' - this is normal (especially if this happens after rebooting the sensor by removing the sensor battery and then installing the battery back). This is due to the fact that all processes in the sensor (measuring level, temperature and battery voltage, as well as sending a data packet) are launched simultaneously, thus energy consumption increases, which leads to a temporary decrease in battery voltage.

= '''<big>Operating mode</big>''' =
Для установки режима работы на датчике, перейдите в меню настройки.

[[File:Going to settings DU-BLE.png|583x583px]]
{| class="wikitable"
|'''<big>Name of the mode</big>'''
|'''<big>Description of the mode</big>'''
|'''<big>Format of transmitted data</big>'''
|-
|'''Transportation'''
|Used for transporting and storing the sensor. The accelerometer is turned off to save power; no measurements are taken.
|
|-
|'''Vertical rotation control'''
| rowspan="2" |It is used to determine the direction of rotation of the sensor in a plane parallel to the plane of the sensor installation (except for rotation parallel to the ground plane) and/or counting revolutions and speed (rpm).
'''Horizontal rotation''' - the sensor is installed along the axis of rotation of the concrete mixer with the convex part of the body at 90° relative to the ground.

'''Vertical rotation''' - the sensor is installed perpendicular to the axis of rotation of the concrete mixer.
| rowspan="2" |

'''1. Direction only'''

0 - no rotation

1 - left rotation

2 - right rotation

(you can set these values yourself)

'''2. Number of revolutions, rotation speed (rpm), direction of rotation is shown as + or -'''
|-
|'''Horizontal rotation control'''
|-
|'''Container'''
|It is used to control the loading of equipment, for example, a garbage truck
|The tilt angle and the container cumulative counter are transmitted
|-
|'''Bucket'''
|Serves to determine the operation or downtime of an excavator and similar equipment
|The tilt angle and operation are transmitted depending on whether the equipment is working or idle
|-
|'''Plow'''
|Serves to determine the operation of the snowplow blade of snow removal machines and similar equipment
|The tilt angle and operation are transmitted depending on whether the equipment is working or idle
|-
|'''Angle control'''
|Serves to determine the angle of inclination of parts of mechanisms relative to the horizon. Triggering events occur when a certain angle set by the user is reached.
|The tilt angle and response are transmitted depending on whether the control element of the equipment is lowered or raised, respectively
|-
|'''Horizontal inclinometer'''
|In the “'''Single-axis'''” measurement mode, the sensor records deviations only along one axis - the pitch axis - from the zero point, which must be set after selecting the mode and installing the sensor at the moment when the mechanism is on a flat surface in the stowed position. The angle is measured from 0 to 360 degrees.
In the “'''Two-axis'''” mode, you can track the tilt angle along each measurement axis separately.
|The roll (and pitch) angle(s) is transmitted.
'''0-360''' for one axis

'''0-180''' for the other axis
|-
|'''Verticalinclinometer'''
|In the “'''Single-axis'''” measurement mode, the sensor records deviations only along one axis - the pitch axis - from the zero point, which must be set after selecting the mode and installing the sensor at the moment when the mechanism is on a flat surface in the stowed position. The angle is measured from 0 to 360 degrees.
In the “Two-axis” mode, you can track the tilt angle along each measurement axis separately.
|The roll (and pitch) angle(s) is transmitted.
'''0-360''' for one axis

'''0-180''' for the other axis
|}

== '''<big>Vertical rotation control</big>''' ==

[[File:Vertical rotation control.png|710x710px]] [[File:Vertical rotation control settings.png|710x710px]]

# Selecting the format of transmitted data ('''Direction only or Speed and rpm''')
# Selecting the transmitted values of rotation left and right, available only in the "'''direction only'''" transmission format

The sensor is installed at the ends of the mixer.

This mode has '''2 formats of transmitted data:'''

1) '''Direction only''' - used, for example, to control the direction of rotation of a concrete mixer. Depending on the direction of rotation around the axis, a trigger event is transmitted: when rotating to the right, the value 1 will be transmitted, when rotating to the left - the value 2, if there is no rotation, 0 will be transmitted.

You can change the value of rotation to the left and to the right (from 1 ... 255)

2) '''Speed and rpm'''. The sensor will transmit the number of complete revolutions and the rotation speed in rpm. The rotation speed will be calculated by the sensor after the first three full revolutions. The speed will be positive in one direction, negative in the other. You can learn more about how to set up speed recognition on the monitoring platform in [https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing this manual]

[[File:F0cc0683-1aae-4b82-be4f-aa5230b8e6ce.png|948x948px]]

[[File:Vertical rotation control diagram.png]]

[[File:Vertical rotation control example.png|806x806px]]

== '''<big>Horizontal rotation control</big>''' ==
[[File:Horizontal rotation control.png|710x710px]] [[File:Vertical rotation control settings.png|710x710px]]

#Selecting the format of transmitted data ('''Direction only or Speed and rpm''')
# Selecting the transmitted values of rotation left and right, available only in the "'''direction only'''" transmission format

The sensor is installed at the ends of the mixer.

This mode has '''2 formats of transmitted data:'''

1) '''Direction only''' - used, for example, to control the direction of rotation of a concrete mixer. Depending on the direction of rotation around the axis, a trigger event is transmitted: when rotating to the right, the value 1 will be transmitted, when rotating to the left - the value 2, if there is no rotation, 0 will be transmitted.

You can change the value of rotation to the left and to the right (from 1 ... 255)

2) '''Speed and rpm'''. The sensor will transmit the number of complete revolutions and the rotation speed in rpm. The rotation speed will be calculated by the sensor after the first three full revolutions. The speed will be positive in one direction, negative in the other. You can learn more about how to set up speed recognition on the monitoring platform in [https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing this manual]

The sensor is installed on the side surface of the mixer.<blockquote>'''<big>In horizontal rotation, the sensor is installed with the convex/semi-circular part up or down! When installed with the convex/semi-circular part to the left or right, rotations will not be counted!</big>'''</blockquote>
[[File:Horizontal rotation control diagram.png]]

[[File:Horizontal rotation control example.png|851x851px]]

== '''<big>Container</big>''' ==
[[File:Container mode.png|750x750px]] [[File:Container mode settings.png|750x750px]]

Serves to control unloading and loading on equipment types such as garbage trucks, dump trucks, etc., as well as for more precise control of hatch cover opening.

After installing the sensor, zero should be set. The equipment should be located on a level surface. When crossing the lower and upper threshold values, the number of trips will increase and the total activation counter will be transmitted.

[[File:Container mode explanation.png|718x718px]]

When crossing the blue line (Upper threshold value), the counter increases by 1, for repeated triggering it is necessary to cross the green line (Lower threshold value)

Black line - Zero

Green line - Lower threshold value

Blue line - Upper threshold value

The counter will continue to increase with each container up to the maximum value of 65535. After which it will reset to zero and continue to increase again. With 100 containers per day, the counter will last for 1-2 years.

The settings for the received readings on the platform are shown in [https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing this manual]

== '''<big>Bucket</big>''' ==

[[File:Bucket mode.png|750x750px]] [[File:Bucket mode settings.png|750x750px]]

This mode is intended for use on excavators to monitor bucket operation or idle time.

'''Filtration level''' - how much the tilt angle data will be filtered during sudden changes.

'''Delta''' - the minimum angle value at which the triggering occurs.

'''Measurement interval''' - the time period after which the tilt angle is compared to calculate the delta.

'''Turn OFF delay''' - the time period during which the work will be transmitted.

'''Transmit as event notification'''- the value that will be transmitted as work.

"'''Measurement interval'''" sets the time during which the sensor measures the angle values. After the measurement interval, the current value is compared with the previous value. If the difference is a certain angle that is greater than or equal to the "'''Delta'''" value, then the triggering will occur, which will signal the excavator bucket is working. The "'''Delta'''" parameter sets the minimum angle value at which the triggering occurs. If the bucket operation is stopped, the angle difference will not exceed the set value "'''Delta'''", the "'''Turn OFF delay'''" is started, no triggering occurs (the value "0" is transmitted). In this way, the bucket operation and downtime are separated, eliminating false triggering.

The setup of the received readings on the platform is shown in [https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing this manual]<blockquote>'''<big>When installing tilt angle sensors on excavator manipulators, it is recommended to place the sensor on the knee of the manipulator, which is the most active at the time the excavator is performing work and makes a greater number of movements with a greater amplitude of angle change.</big>'''</blockquote>[[File:Bucket mode diagram.png]]

[[File:Bucket mode example.png|697x697px]]

== '''<big>Plow</big>''' ==
[[File:Plow mode.png|750x750px]] [[File:Plow mode settings.png|750x750px]]

The mode is designed for installation on "blade" type devices, such as snow blowers used for clearing roads, or a bulldozer.

'''Filtration level''' - how much the tilt angle data will be filtered during sudden changes.

'''Upper limit''' - the tilt angle threshold above which the alarm stops.

'''Lower limit''' - the tilt angle threshold below which the alarm starts after the turn-on delay.

'''Turn ON delay''' - the number of seconds the sensor must be below the lower threshold to start the alarm.

'''Turn OFF delay''' - the number of seconds the sensor must be between the upper and lower angles to stop the alarm.

'''Transmit as event notification''' - the value that will be transmitted as the job.<blockquote>'''<big>Important! It is not recommended to use the sensor to control mechanisms whose deviation amplitude is less than 10 degrees. For example, the middle blade of a grader.</big>'''</blockquote>When crossing the "'''LOW'''" boundary towards a smaller angle, the turn-on delay timer is started. If the current angle does not exceed the "'''LOW'''" boundary upon expiration of the turn-on delay timer, the triggering event will occur (the value "1" or another value that you set is transmitted).

When crossing the "'''LOW'''" boundary towards a larger angle, the turn-off delay timer is started. If the current angle remains greater than the "'''LOW'''" boundary upon expiration of the turn-off delay timer, the triggering will be reset (the value "'''0'''" is transmitted).

If, at the moment of counting down the turn-off delay timer, the sensor crosses the "'''LOW'''" boundary back towards a smaller angle, the started turn-off timer is reset.

When crossing the "'''UP'''" boundary towards a larger angle, the triggering will be reset instantly.

This is done to obtain more visual readings of the sensor triggering (short-term raising and lowering of the implement during obstacle avoidance and turns are excluded).<blockquote><big>'''The "0" is set in the working position.'''</big></blockquote>[[File:Plow mode diagram.png|740x740px]]

[[File:Plow mode diagram 2.png]]

The setup of the received readings on the platform is shown in [https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing this manual]

== '''<big>Angle Control</big>''' ==
[[File:Angle control.png|750x750px]] [[File:Angle control settings.png|750x750px]]

The "Angle Control" operating mode can be used, for example, to control the operation of a garbage truck, dump truck, and other working units of special equipment.

The 3-axes accelerometer used in the sensor cannot ignore vibrations, acceleration and deceleration of the vehicle/unit the sensor is installed on. It also cannot ignore the inclination of the terrain the vehicle/unit moves across.

Due to that the sensor is less suited for the monitoring of machinery units that are operated when on the move, f.e. dump trucks that are gradually unloaded with their boxes are lifted and they slowly move forward. There will be factors mentioned above that will affect the sensor's readings and cause random angle changes that will be impossible to reliably validate by the vehicle's speed.

In other cases the sensor's readings can be validated by the vehicle's speed.

More on that in [https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing this manual (p. 19)]

The sensor also has its own filtration/smoothing algorithm. However, the higher the level of that filtration is, the slower the current angle reading is calculated and that could lead to the actual movements of the mechanism the sensor is installed on to get missed.

One more option is to install 2 sensors: one on the vehicle's (unit's frame) and another - on the mechanism that needs to be monitored. More on that in [https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing this manual (p. 17)]

'''Filtration level''' - how much the tilt angle data will be filtered during sudden changes.

'''Upper limit'''- the tilt angle threshold above which the triggering occurs.

'''Lower limit'''- the tilt angle threshold below which the triggering stops.

'''Transmit as event notification''' - the value that will be transmitted as work.

When the angle increases and the upper limit is reached, the sensor is triggered; when moving backwards and crossing the lower limit, the triggering is reset (the value "0" is transmitted).

[[File:Angle control diagram.png]]

The setup of the received readings on the platform is shown in [https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing this manual]

== '''Horizontal inclinometer''' ==
[[File:Horizontal inclinometer.png|750x750px]] [[File:Inclinometer settings.png|750x750px]]

The inclinometer mode is designed to measure the angle and direction of tilt.

'''Filtration level''' - how much the tilt angle data will be filtered during sudden changes.

'''Single-axis mode''': measures the rotation angle along the X axis (roll) in the horizontal position, i.e. the ZY plane is perpendicular to the installation plane. It is possible to set zero. The measurement range is 360°. There is no trigger event.

'''Dual-axis mode''': measures the rotation angle along the Y axis (roll) and the rotation angle along the X axis (pitch) in the horizontal position. It is possible to set zero. The measurement range is 180°. There is no trigger event.<blockquote><big>'''Data transfer in Horizontal inclinometer mode is supported only when using [[BA-BLE]]'''</big></blockquote>[[File:Horizontal inclinometer diagram.png]]

== '''<big>Vertical inclinometer</big>''' ==
[[File:Vertical inclinometer.png|750x750px]] [[File:Inclinometer settings.png|750x750px]]

The inclinometer mode is designed to measure the angle and direction of tilt.

'''Filtration level''' - how much the tilt angle data will be filtered during sudden changes.

'''Single-axis mode''': measures the rotation angle along the X axis (roll) in the horizontal position, i.e. the ZY plane is perpendicular to the installation plane. It is possible to set zero. The measurement range is 360°. There is no trigger event.

'''Dual-axis mode''': measures the rotation angle along the Y axis (roll) and the rotation angle along the X axis (pitch) in the horizontal position. It is possible to set zero. The measurement range is 180°. There is no trigger event.<blockquote><big>'''Data transfer in Vertical inclinometer mode is supported only when using [[BA-BLE]]'''</big></blockquote>[[File:Vertical inclinometer diagram.png]]

= <big>'''Sealing and installation'''</big> =

== '''<big>Connection dimensions</big>''' ==

=== '''<big>Connection dimensions of the DU-BLE of the former design</big>''' ===
[[File:Connection dimensions DU-BLE former design .png]]

[[File:Dimensions of former design DU-BLE.png]]

=== '''<big>Connection dimensions of the DU-BLE of the current design</big>''' ===
[[File:Connection dimensions DU-BLE current design .png]]

[[File:Dimensions of current design DU-BLE.png]]

== <big>'''Sensor sealing'''</big> ==

=== <big>'''Sealing DU-BLE of the former design'''</big> ===
To seal the sensor and prevent unauthorized access to it, install the protective cover and pass the seal through the special holes in the cover. Tighten the seal against its end into the special hole in the seal. Cut off the excess wire of the seal.

[[File:Sealing former design DU-BLE.png]]

=== <big>'''Sealing DU-BLE of the current design'''</big> ===
You will need the sensor protective cover and the seal provided in the kit<gallery widths="300" heights="300">
File:New_design_cap.png|'''<big>Protective cover DU-BLE</big>'''
File:New_design_seal.png|'''<big>DU-BLE seal</big>'''
</gallery>The cover is attached to the sensor head
[[File:TD-BLE_with_cap.png|none|thumb|455x455px|'''<big>DU-BLE with cap</big>''']]

Then the seal itself is fixed in a special hole (it must be inserted to the end, with the '''closed end facing outward''')<gallery widths="350" heights="350">
File:Installing_TD-BLE_seal.png|'''<big>Installing DU-BLE seal</big>'''
File:Installed_TD-BLE_seal.png|'''<big>Installed DU-BLE seal</big>'''
</gallery>To remove the seal, screw in the special key from the kit (you can also use any self-tapping screw of suitable size) and pull it towards yourself.
[[File:Removing_seal.png|none|thumb|493x493px|'''<big>Removing seal</big>''']]
[[File:Seal_after_removal.png|none|thumb|'''<big>Seal after removal</big>''']]
This makes it impossible to remove the seal without damaging it. This provides additional protection against unauthorized access.

=== '''<big>Alternative sealing for DU-BLE of the current design</big>''' ===
Also included with the current DU-BLE is an alternative seal if a numbered seal is required.

* The wire must be threaded through the hole in the sensor cover

[[File:Alternative_sealing_step_1.png|frameless|433x433px]]

* Thread both ends of the cable through the hole in the sensor head

[[File:Alternative_sealing_step_2.png|frameless|519x519px]]

* Pass both ends through the seal, tighten the cable and install the seal by pressing the protruding part of the seal

[[File:Alternative_sealing_step_3.png|frameless|543x543px]]

== <big>'''Mounting and direction'''</big> ==
The most common mounting method is self-tapping screws with a sealing washer. It is also possible to install on threaded crimp nuts, welded bushings and other structural elements. The sensor can be mounted on pre-prepared places using screws and bolts with strength class not less than 4.8. It is necessary to ensure tightness of the connection between the sensor body and the tank. For additional protection it is allowed to use automotive oil and gasoline resistant sealant.

For plastic tanks rivets and bolts can be used.

[[File:Antenna_direction.png|frameless|768x768px]]

== <big>'''How hard to screw in self-tapping screws'''</big> ==

== [[File:How_to_hard_to_tighten_the_screws.png|frameless|512x512px]] ==

= '''<big>Firmware update (FW)</big>''' =
[[File:DU-BLE update.gif]]

To update the firmware on the DU-BLE:

* Download the current firmware version as a file to the phone memory
* Connect to the sensor
* Go to “'''Additional Features'''”
[[File:Additional features DU-BLE.png|546x546px]]

* Go to FW update
[[File:FW update menu.png|577x577px]]

* Select the firmware file ('''1''') from the phone memory (The firmware file is the .zip archive itself, no need to unzip it) and start the flashing process ('''2'''). '''These actions should be performed within 30 seconds after entering update mode!'''
[[File:Start_of_TD-BLE_update.png|frameless|732x732px]]

* The flashing process should start. '''Do not close or minimize the application during the flashing process!'''
[[File:TD-BLE_update_process.jpg|frameless|728x728px]]

* When the updating is completed, a window will pop up indicating that the update was successful
[[File:The_TD-BLE_update_has_been_completed.jpg|frameless|741x741px]]

Firmware update via the IOS mobile application is shown in [https://youtu.be/rPsI1AdrTQs this video]

Up-to-date firmware can be found in the [https://www.fmeter.ru/en/download/?product=DUBLE#escort-duble Download materials]

The firmware file is the .zip archive itself, no need to unzip.

= '''<big>Useful links</big>''' =

* '''<big>[https://www.fmeter.ru/download/_ftp/eng/datchik-ugla-naklona/eskort-du-ble/Escort%20DU-BLE%20datasheet.pdf?v=071220114144 Technical data sheet of the device]</big>'''
* '''<big>[https://www.fmeter.ru/en/produktsiya/besprovodnoy-datchik-ugla-naklona/eskort-du-ble/#active Product page]</big>'''
* '''<big>[https://www.fmeter.ru/en/download/?product=DUBLE#escort-duble Download materials]</big>'''
* '''<big>[[Table of compatibility of BLE sensors with trackers and other devices]]</big>'''
* '''<big>[https://docs.google.com/document/d/13xV8zCP8JVlJ-dzKR4HQJ8sr28X-L5w_0APE2Nq293E/edit?usp=sharing Setting up the received readings on the platform]</big>'''

File:F0cc0683-1aae-4b82-be4f-aa5230b8e6ce.png

2026-05-06T08:23:13Z

ANATOLYI:

Installation example du ble rotation

Media center

2026-03-18T11:34:01Z

ANATOLYI: /* Sell */

[[RU:Медиацентр| Русская версия]]
[[es:Centro de medios| Versión en español]]

[[File:Header eng.png|frameless|938x938px]]

== '''Escort = Support''' ==
We believe that support is one of the greatest values we can offer our partners.
On this page, we've gathered materials that will help you sell our products, increase your average transaction value, and make the process easier.

Here you will find:

* links to useful resources and training courses,
* convenient commercial proposals that are easy for end customers to understand,
* materials for placing on your websites.

== '''Learn''' ==
Here we've gathered materials to help your new managers gain knowledge about our sensors, and for experienced ones to refresh theirs.

# '''[[Main Page|Knowledge Base]]''' is the Escort wiki, where sensors’ documentation is collected.
# '''[https://go.teachbase.ru/login?lang=en “Fuel Level Sensors” course]''' on the Escort training platform.[[File:FLS course.jpg|803x803px]]
# '''[https://go.teachbase.ru/login?lang=en “Tilt Angle Sensors” course]''' on the Escort training platform. [[File:DU course.jpg|805x805px]]
# Training videos on '''[https://www.youtube.com/@escortsensors1697 Youtube].'''

== '''Sell''' ==

# Commercial proposals featuring ready-made solutions for owners of various types of machinery.

'''How to use:''' choose the solution you need, add your contact information – and the document is ready to be sent to the end customer.

You can download the ready-made commercial offers via the [https://www.fmeter.ru/download/_ftp/marketing/English_Commercial_proposal.pptx link] (29.5 MB).

[[File:Commercial proposal .gif]]

2. Explore our '''use cases''' [https://esensor.ae/cases/ here] – they demonstrate how our solutions work in real projects and can help you effectively communicate their value to your clients.

== '''Present''' ==

=== '''1. Photos of Escort sensors and additional equipment''' ===
'''How to use:''' high-resolution images are suitable for use on your website.

You can download sensor photos [https://www.fmeter.ru/download/_ftp/marketing/Escort_sensors_photos.zip here] (207 MB).

Photos of consumables are available [https://www.fmeter.ru/download/_ftp/marketing/Disposables-20250604T132503Z-1-001.zip here] (342 MB).

Product descriptions can be taken from the product cards in our [https://esensor.ae/catalog/ catalog].

The Escort logo in various formats for use in presentations, websites, and commercial proposals is available [https://www.fmeter.ru/download/_ftp/archive_marketing/Logotipy_GK_Eskort-20250515T130355Z-1-001.zip here] (113 KB).

=== '''2. Presentations about Escort products''' ===
'''How to use:''' the presentations are in editable .pptx format. You can use the product descriptions and use cases to present our solutions to end customers during personal meetings, conferences, and webinars.

# The '''master presentation''' with a full description of Escort company, its products, and helpful case studies can be downloaded [https://www.fmeter.ru/download/_ftp/marketing/MasterPresentationEnglish.pptx here] (40.2 MB).
# The presentation describing the '''eCargosens axle load monitoring system''' is available at this [https://www.fmeter.ru/download/_ftp/marketing/eCargosens.pptx link] (18.9 MB).
# The presentation about the '''DU-BLE tilt angle sensor''' – what it is, what tasks it solves, and which industries it applies to – can be downloaded [https://www.fmeter.ru/download/_ftp/marketing/Presentation_DU-BLE.pptx here] (28 MB).

=== 3. Escort Monitoring Systems Guideline (Identity Guide) ===
'''How to use:''' the rules for using the logo, font, and types of souvenirs will help you apply the branded elements of Escort correctly. You can download it from the [https://www.fmeter.ru/download/_ftp/marketing/guidebook_english.pdf link].

[[File:English_Guidebook.png|681x681px]]

=== 4. Escort News ===
'''How to use:''' post important news on your website and social media – hardware updates, new tools for applications, and more. You can find the news [https://esensor.ae/category/company-news/ here].

== '''Stay in touch!''' ==
We announce all news and updates on our social media channels. Join us!

[https://linkedin.com/company/escort-monitoring-systems LinkedIn page]

[https://www.facebook.com/WeWalkIoT/ Facebook page]

[https://www.youtube.com/@escortsensors1697 YouTube channel]

Teltonika-BLE

2026-02-19T11:44:37Z

ANATOLYI: /* Connecting BLE via adapter (BLE-Rs485 base) */

[[es:TD-BLE]]

= <big>'''Quick start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)
1.Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2).
{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Imagesbsb.png|353x353px]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}
2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below

[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows:

- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4).

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6):

- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE, “Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

== I/O tab settings ==
6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level).

In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

== System settings ==
7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8)

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9).

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10)

[[File:Antenna direction.png]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows:

== [[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]] ==
Fig. 11 Connections and IO list

11. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes.

[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =
1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13).

[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14)

[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15)
{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17)
{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18)

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19)

[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20)

[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''.

The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]

Fig. 21 I/O tab LLS parameters

9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below

[[File:Photo 5418063427176959131 x.jpg]]

[[File:Таблица данных на телтонику.png]]

Fig. 22 io_ list (partial)

10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB'''

[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24)

[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]

Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

== Lost Connection ==
If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data.

Before installing a BLE sensor and a tracker, you need to check the stability of the Bluetooth connection to select the best spot to install the GPS tracker/gateway (or BLE-RS485-RS232 adapter) at to minimize the risks of connection losses happening in the future.

To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, you should calculate the average RSSI (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on.

The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range.

In case of the Bluetooth 4.0 the connection stability range is the value from -35 dBm to -85 dBm. If the average RSSI is less than -85 dBm (for example, -90 dBm), placing the tracker/gateway where it was during the RSSI check will most probably lead to the connection instability. As a result, not all the sensor's data packages will be received by the tracker.

The solution is to try and turn the tracker around a bit or move it closer to the sensor and placing it at a spot where the average RSSI will be within the -35...-85 dBm range. Alternatively, you could install our BLE-RS485-RS232 BA_BLE adapter/base that tends to perform better than the Bluetooth modules of the trackers.

Please, note that the RSSI is calculated by the receiver, so the connection quality is determined by the receiver and also depends on the receiver's sensitivity.

== Presets ==
You can also downolad our '''TD 150 BLE''' and '''DU BLE''' presets for Teltonika tracker manually

# First of all, download preset file from the links below: [https://drive.google.com/file/d/1_wiyNRlUvUn0JarXYwcJNpeahZNlH1Fw/view TD 150 BLE] [https://drive.google.com/file/d/1xQgTjlbQ8W2oOb8Owpj2Jr_U7xh4-2a0/view DU BLE]
# .Follow the Teltonika settings in the right corner below in the configurator [[File:Imageaaveda.png|833x833px]]
# Open Preset Settings and find preset file, that you downloaded earlier [[File:Imageacacac.png|839x839px]]
# Choose the downloaded preset file [[File:Imagecavcf.png|837x837px]] [[File:Imageavdsfbdn.png|837x837px]]
# After that you will find our preset file in the preset list [[File:Imageacevsd.png|837x837px]]

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

File:Таблица данных на телтонику.png

2026-02-19T11:44:22Z

ANATOLYI:

advsbra

ALS

2026-02-05T09:45:11Z

ANATOLYI: /* Preparing the sensor tubes */

= '''<big>Definition and purpose of the sensor</big>''' =
[[RU:ALS| Русская версия]]
[[File:Current design of ALS.jpg|thumb|[https://wikiru.fmeter.ru/images/thumb/8/8d/%D0%A2%D0%B5%D0%BA%D1%83%D1%89%D0%B8%D0%B9_%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD_ALS.jpg/723px-%D0%A2%D0%B5%D0%BA%D1%83%D1%89%D0%B8%D0%B9_%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD_ALS.jpg?20241218111713 '''<big>Current design of ALS</big>''']]]
Escort's high-precision water level sensors ("WLS" or "ALS", also referred to as "gauges" or "sensors") are designed to determine the fill level of water in containers, tanks, and storage vessels. The ALS gauge is used in specialized equipment as a water level indicator and in industry as a level sensor for liquids with properties similar to water. The measurement principle of Escort's WLS is capacitive, relying on the dielectric permittivity of the medium; in this case, it measures the level of non-aggressive liquids such as water, aqueous solutions, liquid fertilizers, etc. Materials in contact with the measured liquid include aluminum alloy (AD-31) and polyacetal (PA-6).

''Note:'' The ALS sensor is not intended for use with liquid food products, such as milk, juices, fermented dairy products, etc., as it is not certified for these applications.

More detailed technical characteristics are presented in the [https://www.fmeter.ru/download/_ftp/eng/water-level-sensor/Datasheet%20Escort%20ALS.pdf?v=220225205325#page=21 technical data sheet of the device]

= <big>'''Basic terms and concepts'''</big> =
'''''Aqua Level Sensor (ALS)''''' - device which is used for measuring water level.

'''''Serial number''' -'' code consisting of letters and numbers assigned to a device (sensor).

'''''CNT''' -'' an oscillatory circuit, thanks to which the basic level of filling of the sensor measuring tubes with water is calculated. This level is converted to a final value determined by the data interface.

'''''Data transfer protocol''''' - a set of specific logical-level rules or conventions that govern the exchange of data between different programs or devices. For TD-150, the main transmission protocol is '''LLS via the RS-485 interface'''.

'''''Data transfer mode''''' - this is a type of boundary between two objects or nodes, which are regulated by a special accepted standard and implemented using established methods, tools and rules. TD-150 has the following operating modes:

* '''RS-485 (Passive and Active)'''
* '''Analog'''
* '''Frequency'''

'''''Interface''''' - a physical connection method and/or a set of software tools that allows data to be transferred between two or more devices.

'''''RS-485''''' - digital data transmission mode. The sensor waits for a corresponding request from the receiving device. Works using the LLS protocol. Based on CNT, a value is generated in conventional units of the selected range (1-1023 units or 1-4095 units)

'''''Converter''''' - digital converter RS-485 to USB (С200М или С200М2) for configuring wired sensors.

'''''Active (periodic) RS-485''''' - operating mode in which the sensor, without waiting for a request from the receiver, itself transmits packets with command data within 2 seconds.

'''''Analog''''' - mode in which a corresponding voltage is generated based on the CNT in the approximate range of 0.2-9V.

'''''Frequency''''' - mode in which the corresponding frequency in Hz is generated based on the CNT (301-1323 Hz with a value range of 1-1023; 301-4395 Hz with a value range of 1-4095).

'''''Navigation terminal''''' - the main element of the system for monitoring the operation of transportation carried out by means of satellite communication. Without it, it is impossible to control transportation, to determine the coordinates of the vehicle location. It collects information from sensors and on-board system of the vehicle, and then transmits it to the device/server, which belong to the controlling specialist.

= '''<big>Preparation</big>''' =

'''Why Should the Sensor Be Installed at the Geometric Center of a Mobile Tank?'''

The highest point of the tank should be selected to ensure the sensor can measure the entire liquid level within the tank without any blind spots.

The liquid level readings from a sensor installed at the center of the tank will be least affected by movement and sloshing of the liquid inside the tank.

If it is not possible to install the sensor at the center of the tank, consider the option of installing two sensors diagonally at opposite corners. When liquid shifts towards one side of the tank, the corresponding sensor will show an increase in level, while the opposite sensor will show a decrease. This way, the average liquid level will remain unchanged.

'''Video Example:'''

[https://youtu.be/3psA2ACmw7w?si=zQ7n_N6h0HseNdfF A video demonstrating the importance of sensor installation at the geometric center of the tank, using a fuel tank as an example.]
<blockquote>'''Attention:''' Before starting the calibration, the vehicle/tank must be positioned level with respect to the horizon, i.e., on a flat surface without any incline.</blockquote>If the tank has an irregular shape, the sensor should be installed at the point of maximum depth, as close to the geometric center as possible.
[[File:The_sensor_is_installed_in_the_highest_place_of_the_tank.png|none|thumb|874x874px|'''<big>The sensor is installed in the highest place of the tank</big>''']]
[[File:Ladder_tank.png|frameless|470x470px]]

[[File:Ladder_tank_I.png|frameless|451x451px]]

When installation at the center is not possible – use two or more sensors.

To increase accuracy and reduce level fluctuations, two sensors are installed in one tank. This solution is primarily used for tanks with a capacity of more than 600 liters and a length of at least 1500 mm. Sensors should not be installed directly against the tank walls.

Additionally, two or more sensors should be installed if it is not possible to position a sensor at the center of the tank and/or if the tank has an elongated shape, meaning the length of the tank is significantly greater than its height.
[[File:Two_sensors_installed_diagonally.png|none|thumb|885x885px|'''<big>Two sensors installed diagonally</big>''']]
'''Note:''' Installing a single sensor in an elongated tank will allow for detecting draining and filling. However, increased level fluctuations during movement may prevent the monitoring platform from accurately calculating the liquid consumption. Therefore, installing two sensors is preferred.

== '''<big>Installation locations in tanks of complex shapes</big>''' ==

=== '''<big>Saddle-Style Fuel Tanks</big>''' ===
In this case, it is desirable to install two fuel level sensors in the deepest places along the geometric center of the depressions

=== [[File:Saddle_shape.png|frameless|749x749px]] ===
[[File:Saddle_shape_top_view.png|frameless|749x749px]]

[[File:Saddle_shape_side_view.png|frameless|749x749px]]

=== '''<big>Cylindrical tank</big>''' ===
In this case, the sensor must be installed in the geometric center of the tank.

[[File:Cylindrical_tank.png|frameless|750x750px]]

[[File:Cylindrical_tank_top_view.png|frameless|750x750px]]

[[File:Cylindrical_tank_inside_view.png|frameless|750x750px]]

==== '''<big>Long cylindrical tank</big>''' ====
In the case of elongated cylindrical tanks, to improve readings while driving, it is necessary to install two sensors at an equal distance from the geometric center of the tank.

[[File:Cylindrical_tank_long.png|frameless|750x750px]]

[[File:Cylindrical_tank_long_inside_view.png|frameless|750x750px]]

==== '''<big>Ladder shape tank</big>''' ====
If there is a difference in height in the tank and there is no common bed, it may be necessary to install two water level sensors.

[[File:Ladder_2_tank.png|frameless|782x782px]]

[[File:Ladder_2_tank_inside_view.png|frameless|750x750px]]

===== '''<big>Ladder shape tank's tank calibration</big>''' =====
During calibration, two tables need to be created: one for "Sensor 1" (ДУВ 1) and another for "Sensor 2" (ДУВ 2).

Let's assume the calibration step is 10 liters.

At the beginning of the calibration, when the liquid is in the "Red Zone," level changes will only occur on "Sensor 2," so we directly add the calibration steps of 10 liters to the table for "Sensor 2."

When the liquid is in the "Yellow Zone," changes will occur on both "Sensor 1" and "Sensor 2." In this interval, we record changes in both tables with half-step increments. This means we add 10 liters, but in each sensor's table, we record 5 liters.

When the liquid is in the "Green Zone," changes will occur only on "Sensor 1," so we directly add the calibration steps of 10 liters to the table for "Sensor 1."

On the platform, "Sensor 1" and "Sensor 2" are configured as separate sensors with their own tables, and then a third virtual sensor is created, which sums the liters from both sensors. An example of configuring two sensors on the platform is shown. [https://docs.google.com/document/d/1nZHXENAhi-Do6VU2j5PE9KCO3n76H2fw-wBG70zncXg/edit?usp=sharing in this instruction..]

[[File:ALS example1.png|frameless|680x680px]]

== '''<big>Preparing the sensor</big>''' ==

=== '''<big>Preparing the sensor tubes</big>''' ===
Before calibrating the sensor, you should '''determine the future length''' of the measuring tubes in accordance with the height of the tank and '''cut or extend them'''. The length of the tubes should be calculated according to the following formula:

'''L = H - 15 mm,'''

where L - tubes length after changing the length

and

H - height of the tank at the installation point.<blockquote>'''<big>ATTENTION!!!</big>''' The ALS sensor is available with tube lengths of 950mm, 1450mm, 1950mm, and 2450mm.</blockquote>
Use a hacksaw to cut the tubes . Be careful during the cutting process to avoid damaging the connection between the tubes and the PCB inside the sensor head, as well as the insulating material of the inner tube.

'''After cutting the sensor tubes, use the special insulating heat shrink cap included with the sensor for insulating the inner tube. Use a heat gun or any other heating element to shrink the cap properly.'''

Example:

'''Take this plastic insulation cap'''

[[File:Photo 2022-10-24 14-24-42.jpg|990x990px]]

'''Cover the inner tube with this cap'''

[[File:Photo 2022-10-24 14-24-42 (2).jpg|993x993px]]

'''Press down on cover cap'''

[[File:Photo 2022-10-24 14-19-54.jpg|992x992px]]

'''Use hot air gun to finish the insultion'''

[[File:Https s3.eu-central-1.wasabisys.comincoming-chat-api20221024861320276a824-1f9f-4c3c-a37c-3a1a00e28910.jpg|1000x1000px]]

The extension of the water level sensor tubes is not allowed due to the design features of the inner tube.

== '''<big>Connection dimensions</big>''' ==
[[File:Dimenstions_TD_150.png|none|thumb|702x702px|'''<big>Connection dimensions of the wired FLS</big>''']]

= '''<big>Connection to the sensor, setup, calibration and calibration via [https://www.fmeter.ru/download/_ftp/all/dut/FLS_Configurator.zip?v=210521143455 the configurator on a PC]</big>''' =

== '''<big>Installation of the configurator and connection to the sensor</big>''' ==
The sensor can be configured using [https://www.fmeter.ru/download/_ftp/all/dut/FLS_Configurator.zip?v=210521143455 '''<big>the configurator on a PC</big>'''] (From here onwards- "'''configurator'''").

'''Connect the sensor to the USB-RS-485 converter using a 6-pin MOLEX connector''' or using cable clamps if a cable route is connected to the sensor. Orange wire is line A of the RS-485 sensor interface, white wire is line B of the RS-485 sensor interface, black wire is GND, red is PWR.
[[File:Sensor_connected_via_MOLEX.png|none|thumb|731x731px|'''<big>Sensor connected via MOLEX</big>''']]
[[File:Sensor_connected_via_cables_and_cable_clamps.png|none|thumb|731x731px|'''<big>Sensor connected via cables and cable clamps</big>''']]
We recommend using our Escort C200M/C200M2 USB-RS-485 converter, since we cannot guarantee 100% compatibility of our devices with converters from other brands.

When working with a laptop, we recommend connecting it to the power supply and/or connecting an additional USB cable to the ADD connector of the PWR C200M. Otherwise, there may not be enough power to operate the sensor and transmitter.

Along with installing the configurator 1.0.2.38, the drivers for the C200M will be installed automatically.

If you use C200M2 on Windows 10 and 11 operating systems, drivers should be installed automatically from Windows Update, on the Windows 7 operating system and below, you may need to [https://windowsreport.com/driver-signature-enforcement-windows-10/ disable the electronic signature of drivers] and manually install [https://www.fmeter.ru/download/_ftp/eng/escort_c-200m/Escort%20driver%20C-200M2.zip?v=050623134319 drivers for the С200M2].

If the driver was installed correctly, then after connecting the converter to your PC/laptop, you will see the STMicroelectronics Virtual COM Port ('''1''')(C200M) or USB-SERIAL CH341A ('''2''')(C200M2) device in the COM and LPT ports section of the Windows device manager " to enter this menu, press '''win+r''' and enter '''devmgmt.msc''' and press '''OK''' ('''3''') and then expand the com ports submenu ('''4''')"

The com port number displayed in this menu is also needed to connect the sensor.

[[File:Com_ports_connected.png|frameless|796x796px]]

After connecting the converter, sensor to it and checking the installation of drivers by checking the com port number of the converter, you need to open the configurator, select the desired com port which we could find in the device manager ('''1''') and press the '''FLS''' button ('''2''').

[[File:Com_ports_selection.png|frameless|657x657px]]<blockquote>The connection to the FLS should be made '''within 15 seconds after the sensor has been connected''' to power, if the sensor operating mode has been changed from RS-485 to any other. </blockquote>After connecting the sensor you should see this menu:

[[File:Main_page_PC_configurator.png|frameless|751x751px]]

#Sensor serial number
# Sensor firmware version (FW)
# Sensor temperature
# Current sensor level
# Current CNT level (raw level value) of the sensor
# LLS network addresses connected to this converter (if there is more than one address in this list, it means either more than one sensor is connected to the line at the same time or there is interference on the line, in this case it is necessary to check the connection to the ALS for the presence of other conflicting devices and it is necessary to close other programs using the com ports for example tracker configurator)
# Network address of the polled sensor (This address is used when connecting in RS485 mode)
# Current sensor operating mode
# Current range of output values (1-1023 or 1-4095)
# Current filtration type and degree
# Connected sensor model

== '''<big>Sensor calibration</big>''' ==
[[File:FLS_calibration_PC.gif|frameless|647x647px]]

After you have lengthened or shortened the sensor tubes, you need to carry out the sensor calibration procedure.

To do this you need:

* Go to menu '''"Sensor calibration"'''

[[File:TD_150_calibration.png|frameless|734x734px]]

* '''IMPORTANT! DO NOT INVERT THE SENSOR OR INTRODUCE LIQUID INTO THE INTERNAL TUBING IN A MANNER ANALOGOUS TO FUEL SENSORS. CALIBRATE THE SENSOR EXCLUSIVELY BY SUBMERGING THE TURBOC INTO A RESERVOIR CONTAINING THE FLUID IN WHICH THE SENSOR WILL BE OPERATED.'''
*The water level sensor is designed based on a fuel sensor platform; therefore, the calibration menu will display the label "Calibration without fuel."
*Wait for the CNT level to stabilize ('''1''')
* Deselect the '''"Calibration without fuel'''" slider ('''2''')
* Click '''"Full"''' ('''3''')
* The value '''"Full"''' ('''4''') should change to a value close to the value of the current CNT ('''1'''), but not equal to it, since this value is set according to the temperature compensation of the sensor

[[File:Wired_calibration.png|frameless|366x366px]]
*Empty the pipes of fuel, leave the centralizer in the pipes
* Wait for CNT to stabilize (1)
* Click '''"Empty"''' ('''2''')
* The value '''"Empty"''' ('''3''') should change to a value close to the value of the current CNT ('''1'''), but not equal to it, since this value is set according to the temperature compensation of the sensor
* Click '''"OK"'''

[[File:PC_Empty_calibration.png|frameless|366x366px]]

*The sensor level should display as 1, the sensor calibration process is complete. Thus, CNT should increase as the sensor tubes fill with fuel. It should change from a value close to the Empty calibration value to the Full calibration value.

'''<big>WARNING! For the ALS sensor, it is strongly advised to avoid using the automatic dry calibration function (formally labeled as "Calibration without fuel").</big>'''

== '''<big>Setting the calibration value Full and Empty manually</big>''' ==
We do not recommend using this functionality, but you can set the Full and Empty calibration values manually to save time when you are using sensors of the same length in the same tanks.<blockquote>'''<big>Attention!!! Setting calibration values manually will most likely increase the sensor error! We do not recommend doing this!</big>'''</blockquote>To do this, enter the Full and Empty calibration values of the previously calibrated sensor into the appropriate fields in the configurator.

[[File:Wired_advanced_menu.png|frameless|733x733px]]

[[File:Wired_advanced_menu_page.png|frameless|669x669px]]

[[File:Wired_manual_Empty-Full.png|frameless|667x667px]]

== '''<big>Setting the mode, range and network address</big>''' ==

=== '''<big>Setting the mode</big>''' ===
In the main menu, you can change the operating mode of the sensor. The name of the mode coincides with the interface that is used to physically connect the sensor to the GPS terminal

Select the mode you need('''1''') and click '''“Save parameters to device”'''('''2''')

[[File:Wire_mode_settings.png|frameless|572x572px]]

- '''Passive RS485''' should be selected when you plan to connect to line A and B of the terminal's RS-485 interface. The terminal must have the function of polling sensors, for example, requesting information from them. The terminal must be able to interrogate sensors in accordance with the '''LLS protocol'''.

- '''Frequency mode''' is used when connecting to a GPS terminal to inputs that can receive and read signals in the range '''300 Hz … 1323 Hz''' or '''300 Hz … 4395 Hz'''.

- '''Active RS485''' mode should be used if the terminal has an RS-485 connection interface, but cannot independently poll the sensor, for example, request information from it; the sensor will send its readings independently every 2 seconds.<blockquote>'''<big>Note: The analog output of the ALS is always active on the green wire in the 0.2-9V range, there is no need to turn it on separately</big>'''</blockquote>

=== '''<big>Setting the range</big>''' ===
If you are configuring the sensor to operate in RS-485, Active RS-485, or Frequency modes, you can select the range '''1-1023 or 1-4095''' ('''1''') . In frequency mode, the range will be from '''300Hz to 1323Hz or 300Hz to 4395Hz'''.

After changing the range, click “'''Save the parameters to device'''” ('''2''').

[[File:Wire_range_settings.png|frameless|561x561px]]

'''The range 1-1023''' is most often used for sensors that are '''shorter than 1 meter'''. However, if we are talking about a stationary tank, the height of which is small, but the length and width are more than 2-3 m, it is better to choose the range 1-4095.

=== '''<big>Setting the network address</big>''' ===
The default network address of the sensor is 1; if more than one unit is installed or other ALS devices are added, the network address on the sensor may need to be changed. The network address of each sensor must also be specified in the settings of the receiving device (navigation terminal).<blockquote>'''<big>Attention!!! There cannot be two devices with the same network address on the same line; this will cause a conflict.</big>'''</blockquote>To change the network address, enter a new address in the range '''0-255''' in the '''“Change network address”''' field ('''1''') and click '''“Save the parameters to device”''' ('''2'''), after which the configurator should switch to the new sensor address and display the new sensor address in the field '''"Available units"''' ('''3''') and '''"Poll network address"''' ('''4''').
[[File:Wired_before_changing_Network_address.png|none|thumb|611x611px|'''<big>Before changing network address</big>''']]
[[File:After_changing_network_address.png|none|thumb|614x614px|'''<big>After changing network address</big>''']]

== '''<big>Tank calibration</big>''' ==
'''The process is carried out similarly to the calibration procedure used with fuel sensors. For example, when using a sensor based on the''' [[TD-150]]

== '''<big>Setting and removing a password</big>''' ==
If necessary, you can set a password on the sensor to change settings.

To do this:

* Click on the '''"Service"''' button ('''1''') and then '''"Security"''' ('''2''')

[[File:Wired_security_menu.png|frameless|780x780px]]
* In the menu that opens, you can enter a password consisting of numbers and then click set password. '''Also note that the password cannot start with 0.''' [[File:Password_menu_wired.jpg|frameless|777x777px]]
*After successfully setting the password, a red lock should appear next to the FLS icon [[File:PC_password_set_menu.png|frameless|781x781px]]

<blockquote>'''<big>PLEASE NOTE THAT THE PASSWORD RESET PROCEDURE CAN BE VERY TIME-CONSUMING. WE RECOMMEND THAT YOU TAKE A RESPONSIBLE APPROACH IN SETTING YOUR PASSWORD AND SAVING IT.</big>'''</blockquote>
To change the settings of a password-protected sensor or remove a password, you need to perform the password removal procedure

* Click on the '''"Service"''' button ('''1''') and then '''"Security"''' ('''2''')

[[File:Wired_security_menu.png|frameless|776x776px]]

* In the menu that opens, enter your password (or if you have lost your password, the master password provided by technical support) and click '''"Remove password"'''

[[File:PC_wired_security_remove_password.png|frameless|768x768px]]

* If the password was successfully removed, the lock should turn green

[[File:PC_wired_no_password_menu.png|frameless|719x719px]]

'''Attention!''' By default, there is no password set on the sensor! If you connected the sensor and a password was already set on it, contact technical support.

= '''<big>Connecting the sensor to the GPS terminal</big>''' =

== '''<big>Connection diagrams</big>''' ==
In order to connect the sensor to the GPS terminal and to the power source, use the diagram presented below
[[:File:Wired RS-485 no R.png|[[File:Wired_RS-485_no_R.png|link=|class=mw-file-element|512x512px]]]]
[[File:Wired_Frequency_mode.png|none|thumb|512x512px|'''<big>Wiring diagram for Frequency output</big>''']]
[[File:Wired_Analog_mode.png|none|thumb|512x512px|'''<big>Analog output wiring diagram</big>''']]
<blockquote>'''<big>The ALS sensor has analog mode always enabled; it does not need to be enabled in the configurator!</big>'''</blockquote>

= '''<big>Sensor and cable sealing</big>''' =

== '''<big>Sealing sensor of the current design</big>''' ==
You will need a sensor protective cover and a seal from the kit.<gallery widths="300" heights="300">
File:Protective_cover_for_wired_FLS.png|'''<big>Protective cover for wired FLS</big>'''
File:New_design_seal.png|'''<big>Seal TD-150</big>'''
</gallery>The cover is attached to the sensor head
[[File:Wired_FLS_with_protective_cover.png|none|thumb|411x411px|'''<big>Wired FLS with protective cover</big>''']]
Then the seal itself is fixed in a special hole (it must be inserted to the end, with the '''closed end facing outwards''')<gallery widths="400" heights="400">
File:Installing_a_seal_on_a_wired_FLS.png|'''<big>Installing a seal on a wired FLS</big>'''
File:Installed_seal_on_the_wired_FLS.png|'''<big>Installed seal on a wired FLS</big>'''
</gallery>To remove the seal, screw the special key from the kit into it (you can also use any self-tapping screw of a suitable size) and pull it towards you.
[[File:Removal_of_the_seal_of_the_wired_FLS.png|none|thumb|515x515px|'''<big>Removal of the seal of the wired FLS</big>''']]
[[File:Seal_after_removal.png|none|thumb|'''<big>Seal after removal</big>''']]
Thus, it will be impossible to remove the seal without damaging it. This provides additional protection against unauthorized access.

=== '''<big>Alternative sealing of a current sample sensor</big>''' ===

Also included with the sensor of the current sample is an alternative seal if a numbered seal is required.

* It is necessary to pass the cable through the hole in the sensor cover
* [[File:Alternative_sealing_of_wired_FLS_step_1.png|frameless|432x432px]]

* Pass both ends of the cable through the hole in the sensor head
* [[File:Alternative_sealing_of_wired_FLS_step_2.png|frameless|435x435px]]

* Pass both ends through the seal, tighten the cable and install the seal by pressing on the protruding part
* [[File:Alternative_sealing_of_wired_FLS_step_3.png|frameless|555x555px]]

== '''<big>Sealing sensor of the former design</big>''' ==
[[File:Sealing_sensor_of_the_former_design.png|frameless|512x512px]]

== '''<big>Cable sealing</big>''' ==
To seal the sensor connector, insert a plastic seal into the special hole on the sensor connector

[[File:Wire_sealing.png|frameless|493x493px]]

= '''<big>Updating the sensor firmware</big>''' =
'''[https://docs.google.com/document/d/16KhS0ZV5Hrb44J66LmGOy7Gy2TKcuEqU/edit?usp=sharing&ouid=116383505004193584732&rtpof=true&sd=true Firmware update instructions]'''

'''[https://youtu.be/BVCs-LiWLVs There is also a video instructional guide]'''

'''You can find the latest firmware version in the [https://www.fmeter.ru/en/download/#td150 downloads section of our website]'''

= '''<big>Common problems and solutions</big>''' =

== '''<big>Level 7000</big>''' ==
'''Error Code 7000: Short Circuit.''' This error indicates that water has infiltrated the sensor head, for example, due to improper calibration practices such as inverting the sensor and introducing water into the sensor tubes, akin to the calibration method used for fuel sensors. '''This practice is strictly prohibited.''' Alternatively, the error may occur if foreign particles have entered between the tubes, causing a short circuit.

You should clean the sensor tubes—preferably by blowing them out through the drainage holes using compressed air.

If this error occurred after the start of operation of the sensor, it means that most likely these impurities got into the sensor tubes from the container and in this case it is also needed to ensure that the tank itself doesn't contain any contaminations. Clean the container, if necessary. Note that an ALS installed outside a contaminated container may function correctly, but the same sensor installed in such container may generate this error code.

== '''<big>Level 6500</big>''' ==
This code may indicate that the tubes have lost contact. This error code may be generated immediately after cutting the tubes. In this case, simply calibrate the sensor.

If this does not help, check the CNT. If the CNT is below 10,000, it is very likely that the tubes are not in contact with the sensor board.

Take a photo of the sensor head (the sensor serial number should be visible), its tubes (the correspondence or discrepancy of the tubes length should be clearly visible), take a screenshot of the main screen of the sensor and the Settings menu page in the application and send these data to tech support.

== '''<big>The sensor does not connect or is not recognized in the application</big>''' ==
If the sensor does not connect to the configurator, do the following:

* Make sure that the correct COM port number is selected and that drivers and libraries are installed (STMicroelectronics Virtual COM Port ('''1''')(C200M) or USB-SERIAL CH341A ('''2''')(C200M2) in the COM and LPT ports section of the Windows device manager "to enter this menu, press '''win+r''' and enter '''devmgmt.msc''' and press '''OK''' ('''3''') and then expand the com ports submenu ('''4''')"
** [[File:Com_ports_connected.png|frameless|786x786px]]
** [[File:Com_ports_selection.png|frameless|722x722px]]
** If possible, connect another sensor that is sure to work; if it connects, then there are no problems with the COM port or converter
** Connect another USB cable to the C200M (ADD PWR connector); check if the USB cable is working
** If another converter is used, ensure that sufficient power is supplied to the sensor (12 volts is optimal)
** When connecting the sensor, press Search for sensors within 15 seconds after power is applied to the sensor
** If the above does not help, reflash the FW of the sensor
** If you cannot complete the firmware, contact our technical support

== '''<big>Checking the connection between the sensor and the terminal via RS-485</big>''' ==
If the sensor, for some reason, after you have configured everything correctly, does not transmit data to the terminal, you need to find out whether data is being exchanged between devices.

To do this, connect the sensor to the terminal via RS-485. Connect power to both devices.

After that, take the RS-485-USB converter and connect it between the sensor and the terminal as shown below:

For RS-485, lines A and B of the converter must be connected to lines A and B of the sensor
[[File:RS-485_Logging_Connections_.png|none|thumb|648x648px|'''<big>RS-485 Logging Connections</big>''']]
Run [https://drive.google.com/file/d/10i7v4TZ9-JDJYPAh-9JSh4x6vkM93BVV/view?usp=sharing terminal.exe] and configure the COM port as shown below:

Baud rate – 19200, Parity – None, Stop-bits – 1, Handshaking – None

Also, check HEX or ASCII depending on the format in which information from the sensor will be transmitted. For all sensors except the TD-600 configured in RS-232 mode, you must select HEX.

After connecting the converter correctly, select the COM port and click Connect. If the sensor is polled by the terminal and responds, then everything is in order.
[[File:Sensor_responds_to_the_terminal_via_RS-485.png|none|thumb|572x572px|'''<big>Sensor responds to the terminal via RS-485</big>''']]
If there is no communication between the two devices, try polling the sensor manually.

To do this, enter the request '''31$01$06$6C''' for the sensor with network address 1 and click '''Send'''
[[File:Sending_a_request_to_the_sensor.png|none|thumb|585x585px|'''<big>Sending a request to the sensor</big>''']]
The structure of the request depends on the network address of the sensor. If you change the sensor address to 255, for example, then the request would look like this

'''31$FF$06$29'''

'''FF''' - 255 in HEX

'''29''' - '''CRC''' checksum calculated for a specific request

In order to calculate the checksum, you can go to the '''[https://crccalc.com/ crccalc]''' website and enter your request without the '''$''' sign, select HEX, CRC-8/MAXIM and click Calc CRC-8
[[File:CRC_calculation_for_address_255.png|none|thumb|665x665px|'''<big>CRC calculation for address 255</big>''']]
If the sensor is polled by the terminal and responds, then everything is in order.

If the sensor does not respond to the terminal, but responds to a request you send manually, you should check your terminal's RS-485 ports.

If the sensor does not respond to anything, the standard ALS diagnostic procedure should be carried out.

= '''<big>Description of the LLS protocol</big>''' =
The protocol is described in this [https://docs.google.com/spreadsheets/d/1maRSrToEaYtOP0sQz69Qq3e0iA0dBRos/edit?usp=drive_link&ouid=113197106569288024895&rtpof=true&sd=true document]

Example of a request and response for 1 network address:

Request: '''''31 01 06 6C'''''

Response from sensor: '''''3E 01 06 19 01 00 92 5D BE'''''

= '''<big>Purpose of contacts and wires</big>''' =
[[File:Pinout_TD-150.png|frameless|828x828px]]

= '''<big>Useful links</big>''' =

*'''<big>[https://www.fmeter.ru/download/_ftp/eng/water-level-sensor/Datasheet%20Escort%20ALS.pdf?v=220225205325#page=21 Technical data sheet of the device]</big>'''
* '''<big>[https://www.fmeter.ru/en/produktsiya/water-level-sensor/escort-als/#active Product page]</big>'''
* '''<big>[https://www.fmeter.ru/en/download/#ALS Download materials]</big>'''

ALS

2026-02-05T09:40:08Z

ANATOLYI: /* Preparing the sensor tubes */

= '''<big>Definition and purpose of the sensor</big>''' =
[[RU:ALS| Русская версия]]
[[File:Current design of ALS.jpg|thumb|[https://wikiru.fmeter.ru/images/thumb/8/8d/%D0%A2%D0%B5%D0%BA%D1%83%D1%89%D0%B8%D0%B9_%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD_ALS.jpg/723px-%D0%A2%D0%B5%D0%BA%D1%83%D1%89%D0%B8%D0%B9_%D0%B4%D0%B8%D0%B7%D0%B0%D0%B9%D0%BD_ALS.jpg?20241218111713 '''<big>Current design of ALS</big>''']]]
Escort's high-precision water level sensors ("WLS" or "ALS", also referred to as "gauges" or "sensors") are designed to determine the fill level of water in containers, tanks, and storage vessels. The ALS gauge is used in specialized equipment as a water level indicator and in industry as a level sensor for liquids with properties similar to water. The measurement principle of Escort's WLS is capacitive, relying on the dielectric permittivity of the medium; in this case, it measures the level of non-aggressive liquids such as water, aqueous solutions, liquid fertilizers, etc. Materials in contact with the measured liquid include aluminum alloy (AD-31) and polyacetal (PA-6).

''Note:'' The ALS sensor is not intended for use with liquid food products, such as milk, juices, fermented dairy products, etc., as it is not certified for these applications.

More detailed technical characteristics are presented in the [https://www.fmeter.ru/download/_ftp/eng/water-level-sensor/Datasheet%20Escort%20ALS.pdf?v=220225205325#page=21 technical data sheet of the device]

= <big>'''Basic terms and concepts'''</big> =
'''''Aqua Level Sensor (ALS)''''' - device which is used for measuring water level.

'''''Serial number''' -'' code consisting of letters and numbers assigned to a device (sensor).

'''''CNT''' -'' an oscillatory circuit, thanks to which the basic level of filling of the sensor measuring tubes with water is calculated. This level is converted to a final value determined by the data interface.

'''''Data transfer protocol''''' - a set of specific logical-level rules or conventions that govern the exchange of data between different programs or devices. For TD-150, the main transmission protocol is '''LLS via the RS-485 interface'''.

'''''Data transfer mode''''' - this is a type of boundary between two objects or nodes, which are regulated by a special accepted standard and implemented using established methods, tools and rules. TD-150 has the following operating modes:

* '''RS-485 (Passive and Active)'''
* '''Analog'''
* '''Frequency'''

'''''Interface''''' - a physical connection method and/or a set of software tools that allows data to be transferred between two or more devices.

'''''RS-485''''' - digital data transmission mode. The sensor waits for a corresponding request from the receiving device. Works using the LLS protocol. Based on CNT, a value is generated in conventional units of the selected range (1-1023 units or 1-4095 units)

'''''Converter''''' - digital converter RS-485 to USB (С200М или С200М2) for configuring wired sensors.

'''''Active (periodic) RS-485''''' - operating mode in which the sensor, without waiting for a request from the receiver, itself transmits packets with command data within 2 seconds.

'''''Analog''''' - mode in which a corresponding voltage is generated based on the CNT in the approximate range of 0.2-9V.

'''''Frequency''''' - mode in which the corresponding frequency in Hz is generated based on the CNT (301-1323 Hz with a value range of 1-1023; 301-4395 Hz with a value range of 1-4095).

'''''Navigation terminal''''' - the main element of the system for monitoring the operation of transportation carried out by means of satellite communication. Without it, it is impossible to control transportation, to determine the coordinates of the vehicle location. It collects information from sensors and on-board system of the vehicle, and then transmits it to the device/server, which belong to the controlling specialist.

= '''<big>Preparation</big>''' =

'''Why Should the Sensor Be Installed at the Geometric Center of a Mobile Tank?'''

The highest point of the tank should be selected to ensure the sensor can measure the entire liquid level within the tank without any blind spots.

The liquid level readings from a sensor installed at the center of the tank will be least affected by movement and sloshing of the liquid inside the tank.

If it is not possible to install the sensor at the center of the tank, consider the option of installing two sensors diagonally at opposite corners. When liquid shifts towards one side of the tank, the corresponding sensor will show an increase in level, while the opposite sensor will show a decrease. This way, the average liquid level will remain unchanged.

'''Video Example:'''

[https://youtu.be/3psA2ACmw7w?si=zQ7n_N6h0HseNdfF A video demonstrating the importance of sensor installation at the geometric center of the tank, using a fuel tank as an example.]
<blockquote>'''Attention:''' Before starting the calibration, the vehicle/tank must be positioned level with respect to the horizon, i.e., on a flat surface without any incline.</blockquote>If the tank has an irregular shape, the sensor should be installed at the point of maximum depth, as close to the geometric center as possible.
[[File:The_sensor_is_installed_in_the_highest_place_of_the_tank.png|none|thumb|874x874px|'''<big>The sensor is installed in the highest place of the tank</big>''']]
[[File:Ladder_tank.png|frameless|470x470px]]

[[File:Ladder_tank_I.png|frameless|451x451px]]

When installation at the center is not possible – use two or more sensors.

To increase accuracy and reduce level fluctuations, two sensors are installed in one tank. This solution is primarily used for tanks with a capacity of more than 600 liters and a length of at least 1500 mm. Sensors should not be installed directly against the tank walls.

Additionally, two or more sensors should be installed if it is not possible to position a sensor at the center of the tank and/or if the tank has an elongated shape, meaning the length of the tank is significantly greater than its height.
[[File:Two_sensors_installed_diagonally.png|none|thumb|885x885px|'''<big>Two sensors installed diagonally</big>''']]
'''Note:''' Installing a single sensor in an elongated tank will allow for detecting draining and filling. However, increased level fluctuations during movement may prevent the monitoring platform from accurately calculating the liquid consumption. Therefore, installing two sensors is preferred.

== '''<big>Installation locations in tanks of complex shapes</big>''' ==

=== '''<big>Saddle-Style Fuel Tanks</big>''' ===
In this case, it is desirable to install two fuel level sensors in the deepest places along the geometric center of the depressions

=== [[File:Saddle_shape.png|frameless|749x749px]] ===
[[File:Saddle_shape_top_view.png|frameless|749x749px]]

[[File:Saddle_shape_side_view.png|frameless|749x749px]]

=== '''<big>Cylindrical tank</big>''' ===
In this case, the sensor must be installed in the geometric center of the tank.

[[File:Cylindrical_tank.png|frameless|750x750px]]

[[File:Cylindrical_tank_top_view.png|frameless|750x750px]]

[[File:Cylindrical_tank_inside_view.png|frameless|750x750px]]

==== '''<big>Long cylindrical tank</big>''' ====
In the case of elongated cylindrical tanks, to improve readings while driving, it is necessary to install two sensors at an equal distance from the geometric center of the tank.

[[File:Cylindrical_tank_long.png|frameless|750x750px]]

[[File:Cylindrical_tank_long_inside_view.png|frameless|750x750px]]

==== '''<big>Ladder shape tank</big>''' ====
If there is a difference in height in the tank and there is no common bed, it may be necessary to install two water level sensors.

[[File:Ladder_2_tank.png|frameless|782x782px]]

[[File:Ladder_2_tank_inside_view.png|frameless|750x750px]]

===== '''<big>Ladder shape tank's tank calibration</big>''' =====
During calibration, two tables need to be created: one for "Sensor 1" (ДУВ 1) and another for "Sensor 2" (ДУВ 2).

Let's assume the calibration step is 10 liters.

At the beginning of the calibration, when the liquid is in the "Red Zone," level changes will only occur on "Sensor 2," so we directly add the calibration steps of 10 liters to the table for "Sensor 2."

When the liquid is in the "Yellow Zone," changes will occur on both "Sensor 1" and "Sensor 2." In this interval, we record changes in both tables with half-step increments. This means we add 10 liters, but in each sensor's table, we record 5 liters.

When the liquid is in the "Green Zone," changes will occur only on "Sensor 1," so we directly add the calibration steps of 10 liters to the table for "Sensor 1."

On the platform, "Sensor 1" and "Sensor 2" are configured as separate sensors with their own tables, and then a third virtual sensor is created, which sums the liters from both sensors. An example of configuring two sensors on the platform is shown. [https://docs.google.com/document/d/1nZHXENAhi-Do6VU2j5PE9KCO3n76H2fw-wBG70zncXg/edit?usp=sharing in this instruction..]

[[File:ALS example1.png|frameless|680x680px]]

== '''<big>Preparing the sensor</big>''' ==

=== '''<big>Preparing the sensor tubes</big>''' ===
Before calibrating the sensor, you should '''determine the future length''' of the measuring tubes in accordance with the height of the tank and '''cut or extend them'''. The length of the tubes should be calculated according to the following formula:

'''L = H - 15 mm,'''

where L - tubes length after changing the length

and

H - height of the tank at the installation point.<blockquote>'''<big>ATTENTION!!!</big>''' The ALS sensor is available with tube lengths of 950mm, 1450mm, 1950mm, and 2450mm.</blockquote>
Use a hacksaw to cut the tubes . Be careful during the cutting process to avoid damaging the connection between the tubes and the PCB inside the sensor head, as well as the insulating material of the inner tube.

'''After cutting the sensor tubes, use the special insulating heat shrink cap included with the sensor for insulating the inner tube. Use a heat gun or any other heating element to shrink the cap properly.'''

Example:

# Take this plastic insulation cap [[File:Photo 2022-10-24 14-24-42.jpg|990x990px]]
# Cover the inner tube with this cap [[File:Photo 2022-10-24 14-24-42 (2).jpg|993x993px]]
# Press down on cover cap [[File:Photo 2022-10-24 14-19-54.jpg|992x992px]]
# Use hot air gun to finish the insultion [[File:Https s3.eu-central-1.wasabisys.comincoming-chat-api20221024861320276a824-1f9f-4c3c-a37c-3a1a00e28910.jpg|1000x1000px]]

The extension of the water level sensor tubes is not allowed due to the design features of the inner tube.

== '''<big>Connection dimensions</big>''' ==
[[File:Dimenstions_TD_150.png|none|thumb|702x702px|'''<big>Connection dimensions of the wired FLS</big>''']]

= '''<big>Connection to the sensor, setup, calibration and calibration via [https://www.fmeter.ru/download/_ftp/all/dut/FLS_Configurator.zip?v=210521143455 the configurator on a PC]</big>''' =

== '''<big>Installation of the configurator and connection to the sensor</big>''' ==
The sensor can be configured using [https://www.fmeter.ru/download/_ftp/all/dut/FLS_Configurator.zip?v=210521143455 '''<big>the configurator on a PC</big>'''] (From here onwards- "'''configurator'''").

'''Connect the sensor to the USB-RS-485 converter using a 6-pin MOLEX connector''' or using cable clamps if a cable route is connected to the sensor. Orange wire is line A of the RS-485 sensor interface, white wire is line B of the RS-485 sensor interface, black wire is GND, red is PWR.
[[File:Sensor_connected_via_MOLEX.png|none|thumb|731x731px|'''<big>Sensor connected via MOLEX</big>''']]
[[File:Sensor_connected_via_cables_and_cable_clamps.png|none|thumb|731x731px|'''<big>Sensor connected via cables and cable clamps</big>''']]
We recommend using our Escort C200M/C200M2 USB-RS-485 converter, since we cannot guarantee 100% compatibility of our devices with converters from other brands.

When working with a laptop, we recommend connecting it to the power supply and/or connecting an additional USB cable to the ADD connector of the PWR C200M. Otherwise, there may not be enough power to operate the sensor and transmitter.

Along with installing the configurator 1.0.2.38, the drivers for the C200M will be installed automatically.

If you use C200M2 on Windows 10 and 11 operating systems, drivers should be installed automatically from Windows Update, on the Windows 7 operating system and below, you may need to [https://windowsreport.com/driver-signature-enforcement-windows-10/ disable the electronic signature of drivers] and manually install [https://www.fmeter.ru/download/_ftp/eng/escort_c-200m/Escort%20driver%20C-200M2.zip?v=050623134319 drivers for the С200M2].

If the driver was installed correctly, then after connecting the converter to your PC/laptop, you will see the STMicroelectronics Virtual COM Port ('''1''')(C200M) or USB-SERIAL CH341A ('''2''')(C200M2) device in the COM and LPT ports section of the Windows device manager " to enter this menu, press '''win+r''' and enter '''devmgmt.msc''' and press '''OK''' ('''3''') and then expand the com ports submenu ('''4''')"

The com port number displayed in this menu is also needed to connect the sensor.

[[File:Com_ports_connected.png|frameless|796x796px]]

After connecting the converter, sensor to it and checking the installation of drivers by checking the com port number of the converter, you need to open the configurator, select the desired com port which we could find in the device manager ('''1''') and press the '''FLS''' button ('''2''').

[[File:Com_ports_selection.png|frameless|657x657px]]<blockquote>The connection to the FLS should be made '''within 15 seconds after the sensor has been connected''' to power, if the sensor operating mode has been changed from RS-485 to any other. </blockquote>After connecting the sensor you should see this menu:

[[File:Main_page_PC_configurator.png|frameless|751x751px]]

#Sensor serial number
# Sensor firmware version (FW)
# Sensor temperature
# Current sensor level
# Current CNT level (raw level value) of the sensor
# LLS network addresses connected to this converter (if there is more than one address in this list, it means either more than one sensor is connected to the line at the same time or there is interference on the line, in this case it is necessary to check the connection to the ALS for the presence of other conflicting devices and it is necessary to close other programs using the com ports for example tracker configurator)
# Network address of the polled sensor (This address is used when connecting in RS485 mode)
# Current sensor operating mode
# Current range of output values (1-1023 or 1-4095)
# Current filtration type and degree
# Connected sensor model

== '''<big>Sensor calibration</big>''' ==
[[File:FLS_calibration_PC.gif|frameless|647x647px]]

After you have lengthened or shortened the sensor tubes, you need to carry out the sensor calibration procedure.

To do this you need:

* Go to menu '''"Sensor calibration"'''

[[File:TD_150_calibration.png|frameless|734x734px]]

* '''IMPORTANT! DO NOT INVERT THE SENSOR OR INTRODUCE LIQUID INTO THE INTERNAL TUBING IN A MANNER ANALOGOUS TO FUEL SENSORS. CALIBRATE THE SENSOR EXCLUSIVELY BY SUBMERGING THE TURBOC INTO A RESERVOIR CONTAINING THE FLUID IN WHICH THE SENSOR WILL BE OPERATED.'''
*The water level sensor is designed based on a fuel sensor platform; therefore, the calibration menu will display the label "Calibration without fuel."
*Wait for the CNT level to stabilize ('''1''')
* Deselect the '''"Calibration without fuel'''" slider ('''2''')
* Click '''"Full"''' ('''3''')
* The value '''"Full"''' ('''4''') should change to a value close to the value of the current CNT ('''1'''), but not equal to it, since this value is set according to the temperature compensation of the sensor

[[File:Wired_calibration.png|frameless|366x366px]]
*Empty the pipes of fuel, leave the centralizer in the pipes
* Wait for CNT to stabilize (1)
* Click '''"Empty"''' ('''2''')
* The value '''"Empty"''' ('''3''') should change to a value close to the value of the current CNT ('''1'''), but not equal to it, since this value is set according to the temperature compensation of the sensor
* Click '''"OK"'''

[[File:PC_Empty_calibration.png|frameless|366x366px]]

*The sensor level should display as 1, the sensor calibration process is complete. Thus, CNT should increase as the sensor tubes fill with fuel. It should change from a value close to the Empty calibration value to the Full calibration value.

'''<big>WARNING! For the ALS sensor, it is strongly advised to avoid using the automatic dry calibration function (formally labeled as "Calibration without fuel").</big>'''

== '''<big>Setting the calibration value Full and Empty manually</big>''' ==
We do not recommend using this functionality, but you can set the Full and Empty calibration values manually to save time when you are using sensors of the same length in the same tanks.<blockquote>'''<big>Attention!!! Setting calibration values manually will most likely increase the sensor error! We do not recommend doing this!</big>'''</blockquote>To do this, enter the Full and Empty calibration values of the previously calibrated sensor into the appropriate fields in the configurator.

[[File:Wired_advanced_menu.png|frameless|733x733px]]

[[File:Wired_advanced_menu_page.png|frameless|669x669px]]

[[File:Wired_manual_Empty-Full.png|frameless|667x667px]]

== '''<big>Setting the mode, range and network address</big>''' ==

=== '''<big>Setting the mode</big>''' ===
In the main menu, you can change the operating mode of the sensor. The name of the mode coincides with the interface that is used to physically connect the sensor to the GPS terminal

Select the mode you need('''1''') and click '''“Save parameters to device”'''('''2''')

[[File:Wire_mode_settings.png|frameless|572x572px]]

- '''Passive RS485''' should be selected when you plan to connect to line A and B of the terminal's RS-485 interface. The terminal must have the function of polling sensors, for example, requesting information from them. The terminal must be able to interrogate sensors in accordance with the '''LLS protocol'''.

- '''Frequency mode''' is used when connecting to a GPS terminal to inputs that can receive and read signals in the range '''300 Hz … 1323 Hz''' or '''300 Hz … 4395 Hz'''.

- '''Active RS485''' mode should be used if the terminal has an RS-485 connection interface, but cannot independently poll the sensor, for example, request information from it; the sensor will send its readings independently every 2 seconds.<blockquote>'''<big>Note: The analog output of the ALS is always active on the green wire in the 0.2-9V range, there is no need to turn it on separately</big>'''</blockquote>

=== '''<big>Setting the range</big>''' ===
If you are configuring the sensor to operate in RS-485, Active RS-485, or Frequency modes, you can select the range '''1-1023 or 1-4095''' ('''1''') . In frequency mode, the range will be from '''300Hz to 1323Hz or 300Hz to 4395Hz'''.

After changing the range, click “'''Save the parameters to device'''” ('''2''').

[[File:Wire_range_settings.png|frameless|561x561px]]

'''The range 1-1023''' is most often used for sensors that are '''shorter than 1 meter'''. However, if we are talking about a stationary tank, the height of which is small, but the length and width are more than 2-3 m, it is better to choose the range 1-4095.

=== '''<big>Setting the network address</big>''' ===
The default network address of the sensor is 1; if more than one unit is installed or other ALS devices are added, the network address on the sensor may need to be changed. The network address of each sensor must also be specified in the settings of the receiving device (navigation terminal).<blockquote>'''<big>Attention!!! There cannot be two devices with the same network address on the same line; this will cause a conflict.</big>'''</blockquote>To change the network address, enter a new address in the range '''0-255''' in the '''“Change network address”''' field ('''1''') and click '''“Save the parameters to device”''' ('''2'''), after which the configurator should switch to the new sensor address and display the new sensor address in the field '''"Available units"''' ('''3''') and '''"Poll network address"''' ('''4''').
[[File:Wired_before_changing_Network_address.png|none|thumb|611x611px|'''<big>Before changing network address</big>''']]
[[File:After_changing_network_address.png|none|thumb|614x614px|'''<big>After changing network address</big>''']]

== '''<big>Tank calibration</big>''' ==
'''The process is carried out similarly to the calibration procedure used with fuel sensors. For example, when using a sensor based on the''' [[TD-150]]

== '''<big>Setting and removing a password</big>''' ==
If necessary, you can set a password on the sensor to change settings.

To do this:

* Click on the '''"Service"''' button ('''1''') and then '''"Security"''' ('''2''')

[[File:Wired_security_menu.png|frameless|780x780px]]
* In the menu that opens, you can enter a password consisting of numbers and then click set password. '''Also note that the password cannot start with 0.''' [[File:Password_menu_wired.jpg|frameless|777x777px]]
*After successfully setting the password, a red lock should appear next to the FLS icon [[File:PC_password_set_menu.png|frameless|781x781px]]

<blockquote>'''<big>PLEASE NOTE THAT THE PASSWORD RESET PROCEDURE CAN BE VERY TIME-CONSUMING. WE RECOMMEND THAT YOU TAKE A RESPONSIBLE APPROACH IN SETTING YOUR PASSWORD AND SAVING IT.</big>'''</blockquote>
To change the settings of a password-protected sensor or remove a password, you need to perform the password removal procedure

* Click on the '''"Service"''' button ('''1''') and then '''"Security"''' ('''2''')

[[File:Wired_security_menu.png|frameless|776x776px]]

* In the menu that opens, enter your password (or if you have lost your password, the master password provided by technical support) and click '''"Remove password"'''

[[File:PC_wired_security_remove_password.png|frameless|768x768px]]

* If the password was successfully removed, the lock should turn green

[[File:PC_wired_no_password_menu.png|frameless|719x719px]]

'''Attention!''' By default, there is no password set on the sensor! If you connected the sensor and a password was already set on it, contact technical support.

= '''<big>Connecting the sensor to the GPS terminal</big>''' =

== '''<big>Connection diagrams</big>''' ==
In order to connect the sensor to the GPS terminal and to the power source, use the diagram presented below
[[:File:Wired RS-485 no R.png|[[File:Wired_RS-485_no_R.png|link=|class=mw-file-element|512x512px]]]]
[[File:Wired_Frequency_mode.png|none|thumb|512x512px|'''<big>Wiring diagram for Frequency output</big>''']]
[[File:Wired_Analog_mode.png|none|thumb|512x512px|'''<big>Analog output wiring diagram</big>''']]
<blockquote>'''<big>The ALS sensor has analog mode always enabled; it does not need to be enabled in the configurator!</big>'''</blockquote>

= '''<big>Sensor and cable sealing</big>''' =

== '''<big>Sealing sensor of the current design</big>''' ==
You will need a sensor protective cover and a seal from the kit.<gallery widths="300" heights="300">
File:Protective_cover_for_wired_FLS.png|'''<big>Protective cover for wired FLS</big>'''
File:New_design_seal.png|'''<big>Seal TD-150</big>'''
</gallery>The cover is attached to the sensor head
[[File:Wired_FLS_with_protective_cover.png|none|thumb|411x411px|'''<big>Wired FLS with protective cover</big>''']]
Then the seal itself is fixed in a special hole (it must be inserted to the end, with the '''closed end facing outwards''')<gallery widths="400" heights="400">
File:Installing_a_seal_on_a_wired_FLS.png|'''<big>Installing a seal on a wired FLS</big>'''
File:Installed_seal_on_the_wired_FLS.png|'''<big>Installed seal on a wired FLS</big>'''
</gallery>To remove the seal, screw the special key from the kit into it (you can also use any self-tapping screw of a suitable size) and pull it towards you.
[[File:Removal_of_the_seal_of_the_wired_FLS.png|none|thumb|515x515px|'''<big>Removal of the seal of the wired FLS</big>''']]
[[File:Seal_after_removal.png|none|thumb|'''<big>Seal after removal</big>''']]
Thus, it will be impossible to remove the seal without damaging it. This provides additional protection against unauthorized access.

=== '''<big>Alternative sealing of a current sample sensor</big>''' ===

Also included with the sensor of the current sample is an alternative seal if a numbered seal is required.

* It is necessary to pass the cable through the hole in the sensor cover
* [[File:Alternative_sealing_of_wired_FLS_step_1.png|frameless|432x432px]]

* Pass both ends of the cable through the hole in the sensor head
* [[File:Alternative_sealing_of_wired_FLS_step_2.png|frameless|435x435px]]

* Pass both ends through the seal, tighten the cable and install the seal by pressing on the protruding part
* [[File:Alternative_sealing_of_wired_FLS_step_3.png|frameless|555x555px]]

== '''<big>Sealing sensor of the former design</big>''' ==
[[File:Sealing_sensor_of_the_former_design.png|frameless|512x512px]]

== '''<big>Cable sealing</big>''' ==
To seal the sensor connector, insert a plastic seal into the special hole on the sensor connector

[[File:Wire_sealing.png|frameless|493x493px]]

= '''<big>Updating the sensor firmware</big>''' =
'''[https://docs.google.com/document/d/16KhS0ZV5Hrb44J66LmGOy7Gy2TKcuEqU/edit?usp=sharing&ouid=116383505004193584732&rtpof=true&sd=true Firmware update instructions]'''

'''[https://youtu.be/BVCs-LiWLVs There is also a video instructional guide]'''

'''You can find the latest firmware version in the [https://www.fmeter.ru/en/download/#td150 downloads section of our website]'''

= '''<big>Common problems and solutions</big>''' =

== '''<big>Level 7000</big>''' ==
'''Error Code 7000: Short Circuit.''' This error indicates that water has infiltrated the sensor head, for example, due to improper calibration practices such as inverting the sensor and introducing water into the sensor tubes, akin to the calibration method used for fuel sensors. '''This practice is strictly prohibited.''' Alternatively, the error may occur if foreign particles have entered between the tubes, causing a short circuit.

You should clean the sensor tubes—preferably by blowing them out through the drainage holes using compressed air.

If this error occurred after the start of operation of the sensor, it means that most likely these impurities got into the sensor tubes from the container and in this case it is also needed to ensure that the tank itself doesn't contain any contaminations. Clean the container, if necessary. Note that an ALS installed outside a contaminated container may function correctly, but the same sensor installed in such container may generate this error code.

== '''<big>Level 6500</big>''' ==
This code may indicate that the tubes have lost contact. This error code may be generated immediately after cutting the tubes. In this case, simply calibrate the sensor.

If this does not help, check the CNT. If the CNT is below 10,000, it is very likely that the tubes are not in contact with the sensor board.

Take a photo of the sensor head (the sensor serial number should be visible), its tubes (the correspondence or discrepancy of the tubes length should be clearly visible), take a screenshot of the main screen of the sensor and the Settings menu page in the application and send these data to tech support.

== '''<big>The sensor does not connect or is not recognized in the application</big>''' ==
If the sensor does not connect to the configurator, do the following:

* Make sure that the correct COM port number is selected and that drivers and libraries are installed (STMicroelectronics Virtual COM Port ('''1''')(C200M) or USB-SERIAL CH341A ('''2''')(C200M2) in the COM and LPT ports section of the Windows device manager "to enter this menu, press '''win+r''' and enter '''devmgmt.msc''' and press '''OK''' ('''3''') and then expand the com ports submenu ('''4''')"
** [[File:Com_ports_connected.png|frameless|786x786px]]
** [[File:Com_ports_selection.png|frameless|722x722px]]
** If possible, connect another sensor that is sure to work; if it connects, then there are no problems with the COM port or converter
** Connect another USB cable to the C200M (ADD PWR connector); check if the USB cable is working
** If another converter is used, ensure that sufficient power is supplied to the sensor (12 volts is optimal)
** When connecting the sensor, press Search for sensors within 15 seconds after power is applied to the sensor
** If the above does not help, reflash the FW of the sensor
** If you cannot complete the firmware, contact our technical support

== '''<big>Checking the connection between the sensor and the terminal via RS-485</big>''' ==
If the sensor, for some reason, after you have configured everything correctly, does not transmit data to the terminal, you need to find out whether data is being exchanged between devices.

To do this, connect the sensor to the terminal via RS-485. Connect power to both devices.

After that, take the RS-485-USB converter and connect it between the sensor and the terminal as shown below:

For RS-485, lines A and B of the converter must be connected to lines A and B of the sensor
[[File:RS-485_Logging_Connections_.png|none|thumb|648x648px|'''<big>RS-485 Logging Connections</big>''']]
Run [https://drive.google.com/file/d/10i7v4TZ9-JDJYPAh-9JSh4x6vkM93BVV/view?usp=sharing terminal.exe] and configure the COM port as shown below:

Baud rate – 19200, Parity – None, Stop-bits – 1, Handshaking – None

Also, check HEX or ASCII depending on the format in which information from the sensor will be transmitted. For all sensors except the TD-600 configured in RS-232 mode, you must select HEX.

After connecting the converter correctly, select the COM port and click Connect. If the sensor is polled by the terminal and responds, then everything is in order.
[[File:Sensor_responds_to_the_terminal_via_RS-485.png|none|thumb|572x572px|'''<big>Sensor responds to the terminal via RS-485</big>''']]
If there is no communication between the two devices, try polling the sensor manually.

To do this, enter the request '''31$01$06$6C''' for the sensor with network address 1 and click '''Send'''
[[File:Sending_a_request_to_the_sensor.png|none|thumb|585x585px|'''<big>Sending a request to the sensor</big>''']]
The structure of the request depends on the network address of the sensor. If you change the sensor address to 255, for example, then the request would look like this

'''31$FF$06$29'''

'''FF''' - 255 in HEX

'''29''' - '''CRC''' checksum calculated for a specific request

In order to calculate the checksum, you can go to the '''[https://crccalc.com/ crccalc]''' website and enter your request without the '''$''' sign, select HEX, CRC-8/MAXIM and click Calc CRC-8
[[File:CRC_calculation_for_address_255.png|none|thumb|665x665px|'''<big>CRC calculation for address 255</big>''']]
If the sensor is polled by the terminal and responds, then everything is in order.

If the sensor does not respond to the terminal, but responds to a request you send manually, you should check your terminal's RS-485 ports.

If the sensor does not respond to anything, the standard ALS diagnostic procedure should be carried out.

= '''<big>Description of the LLS protocol</big>''' =
The protocol is described in this [https://docs.google.com/spreadsheets/d/1maRSrToEaYtOP0sQz69Qq3e0iA0dBRos/edit?usp=drive_link&ouid=113197106569288024895&rtpof=true&sd=true document]

Example of a request and response for 1 network address:

Request: '''''31 01 06 6C'''''

Response from sensor: '''''3E 01 06 19 01 00 92 5D BE'''''

= '''<big>Purpose of contacts and wires</big>''' =
[[File:Pinout_TD-150.png|frameless|828x828px]]

= '''<big>Useful links</big>''' =

*'''<big>[https://www.fmeter.ru/download/_ftp/eng/water-level-sensor/Datasheet%20Escort%20ALS.pdf?v=220225205325#page=21 Technical data sheet of the device]</big>'''
* '''<big>[https://www.fmeter.ru/en/produktsiya/water-level-sensor/escort-als/#active Product page]</big>'''
* '''<big>[https://www.fmeter.ru/en/download/#ALS Download materials]</big>'''

File:Https s3.eu-central-1.wasabisys.comincoming-chat-api20221024861320276a824-1f9f-4c3c-a37c-3a1a00e28910.jpg

2026-02-05T09:39:37Z

ANATOLYI:

Result of insultion

File:Photo 2022-10-24 14-19-54.jpg

2026-02-05T09:36:11Z

ANATOLYI:

cap on the inner tube 2

File:Photo 2022-10-24 14-24-42 (2).jpg

2026-02-05T09:17:53Z

ANATOLYI:

cap on the inner tube

File:Photo 2022-10-24 14-24-42.jpg

2026-02-05T09:16:05Z

ANATOLYI:

insulation cap

Teltonika-BLE

2026-01-15T07:31:39Z

ANATOLYI: /* Presets */

[[es:TD-BLE]]

= <big>'''Qiuck start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)
1.Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2).
{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Imagesbsb.png|353x353px]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}
2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below

[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows:

- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4).

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6):

- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE, “Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

== I/O tab settings ==
6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level).

In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

== System settings ==
7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8)

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9).

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10)

[[File:Antenna direction.png]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows:

== [[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]] ==
Fig. 11 Connections and IO list

11. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes.

[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =
1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13).

[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14)

[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15)
{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17)
{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18)

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19)

[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20)

[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''.

The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]

Fig. 21 I/O tab LLS parameters

9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below

[[File:Photo 5418063427176959131 x.jpg]]

[[File:Imageacas.png]]

Fig. 22 io_ list (partial)

10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB'''

[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24)

[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]

Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

== Lost Connection ==
If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data.

Before installing a BLE sensor and a tracker, you need to check the stability of the Bluetooth connection to select the best spot to install the GPS tracker/gateway (or BLE-RS485-RS232 adapter) at to minimize the risks of connection losses happening in the future.

To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, you should calculate the average RSSI (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on.

The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range.

In case of the Bluetooth 4.0 the connection stability range is the value from -35 dBm to -85 dBm. If the average RSSI is less than -85 dBm (for example, -90 dBm), placing the tracker/gateway where it was during the RSSI check will most probably lead to the connection instability. As a result, not all the sensor's data packages will be received by the tracker.

The solution is to try and turn the tracker around a bit or move it closer to the sensor and placing it at a spot where the average RSSI will be within the -35...-85 dBm range. Alternatively, you could install our BLE-RS485-RS232 BA_BLE adapter/base that tends to perform better than the Bluetooth modules of the trackers.

Please, note that the RSSI is calculated by the receiver, so the connection quality is determined by the receiver and also depends on the receiver's sensitivity.

== Presets ==
You can also downolad our '''TD 150 BLE''' and '''DU BLE''' presets for Teltonika tracker manually

# First of all, download preset file from the links below: [https://drive.google.com/file/d/1_wiyNRlUvUn0JarXYwcJNpeahZNlH1Fw/view TD 150 BLE] [https://drive.google.com/file/d/1xQgTjlbQ8W2oOb8Owpj2Jr_U7xh4-2a0/view DU BLE]
# .Follow the Teltonika settings in the right corner below in the configurator [[File:Imageaaveda.png|833x833px]]
# Open Preset Settings and find preset file, that you downloaded earlier [[File:Imageacacac.png|839x839px]]
# Choose the downloaded preset file [[File:Imagecavcf.png|837x837px]] [[File:Imageavdsfbdn.png|837x837px]]
# After that you will find our preset file in the preset list [[File:Imageacevsd.png|837x837px]]

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

Teltonika-BLE

2026-01-15T07:30:23Z

ANATOLYI: /* Presets */

[[es:TD-BLE]]

= <big>'''Qiuck start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)
1.Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2).
{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Imagesbsb.png|353x353px]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}
2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below

[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows:

- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4).

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6):

- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE, “Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

== I/O tab settings ==
6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level).

In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

== System settings ==
7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8)

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9).

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10)

[[File:Antenna direction.png]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows:

== [[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]] ==
Fig. 11 Connections and IO list

11. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes.

[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =
1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13).

[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14)

[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15)
{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17)
{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18)

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19)

[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20)

[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''.

The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]

Fig. 21 I/O tab LLS parameters

9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below

[[File:Photo 5418063427176959131 x.jpg]]

[[File:Imageacas.png]]

Fig. 22 io_ list (partial)

10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB'''

[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24)

[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]

Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

== Lost Connection ==
If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data.

Before installing a BLE sensor and a tracker, you need to check the stability of the Bluetooth connection to select the best spot to install the GPS tracker/gateway (or BLE-RS485-RS232 adapter) at to minimize the risks of connection losses happening in the future.

To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, you should calculate the average RSSI (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on.

The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range.

In case of the Bluetooth 4.0 the connection stability range is the value from -35 dBm to -85 dBm. If the average RSSI is less than -85 dBm (for example, -90 dBm), placing the tracker/gateway where it was during the RSSI check will most probably lead to the connection instability. As a result, not all the sensor's data packages will be received by the tracker.

The solution is to try and turn the tracker around a bit or move it closer to the sensor and placing it at a spot where the average RSSI will be within the -35...-85 dBm range. Alternatively, you could install our BLE-RS485-RS232 BA_BLE adapter/base that tends to perform better than the Bluetooth modules of the trackers.

Please, note that the RSSI is calculated by the receiver, so the connection quality is determined by the receiver and also depends on the receiver's sensitivity.

== Presets ==
You can also downolad our '''TD 150 BLE''' and '''DU BLE''' presets for Teltonika tracker manually

# First of all, download preset file from the links below: [https://drive.google.com/file/d/1_wiyNRlUvUn0JarXYwcJNpeahZNlH1Fw/view TD 150 BLE] [https://drive.google.com/file/d/1xQgTjlbQ8W2oOb8Owpj2Jr_U7xh4-2a0/view DU BLE]2.Follow the Teltonika settings in the right corner below in the configurator [[File:Imageaaveda.png|833x833px]] 3. Open Preset Settings and find preset file, that you downloaded earlier [[File:Imageacacac.png|839x839px]] 4. Choose the downloaded preset file [[File:Imagecavcf.png|837x837px]] [[File:Imageavdsfbdn.png|837x837px]] 5. After that you will find our preset file in the preset list [[File:Imageacevsd.png|837x837px]]

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

Teltonika-BLE

2026-01-15T07:27:38Z

ANATOLYI: /* 11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24) */

[[es:TD-BLE]]

= <big>'''Qiuck start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)
1.Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2).
{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Imagesbsb.png|353x353px]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}
2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below

[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows:

- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4).

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6):

- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE, “Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

== I/O tab settings ==
6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level).

In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

== System settings ==
7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8)

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9).

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10)

[[File:Antenna direction.png]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows:

== [[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]] ==
Fig. 11 Connections and IO list

11. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes.

[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =
1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13).

[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14)

[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15)
{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17)
{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18)

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19)

[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20)

[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''.

The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]

Fig. 21 I/O tab LLS parameters

9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below

[[File:Photo 5418063427176959131 x.jpg]]

[[File:Imageacas.png]]

Fig. 22 io_ list (partial)

10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB'''

[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24)

[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]

Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

== Lost Connection ==
If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data.

Before installing a BLE sensor and a tracker, you need to check the stability of the Bluetooth connection to select the best spot to install the GPS tracker/gateway (or BLE-RS485-RS232 adapter) at to minimize the risks of connection losses happening in the future.

To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, you should calculate the average RSSI (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on.

The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range.

In case of the Bluetooth 4.0 the connection stability range is the value from -35 dBm to -85 dBm. If the average RSSI is less than -85 dBm (for example, -90 dBm), placing the tracker/gateway where it was during the RSSI check will most probably lead to the connection instability. As a result, not all the sensor's data packages will be received by the tracker.

The solution is to try and turn the tracker around a bit or move it closer to the sensor and placing it at a spot where the average RSSI will be within the -35...-85 dBm range. Alternatively, you could install our BLE-RS485-RS232 BA_BLE adapter/base that tends to perform better than the Bluetooth modules of the trackers.

Please, note that the RSSI is calculated by the receiver, so the connection quality is determined by the receiver and also depends on the receiver's sensitivity.

== Presets ==
You can also downolad our '''TD 150 BLE''' and '''DU BLE''' presets for Teltonika tracker manually

# First of all, download preset file from the links below: [https://drive.google.com/file/d/1_wiyNRlUvUn0JarXYwcJNpeahZNlH1Fw/view TD 150 BLE] [https://drive.google.com/file/d/1xQgTjlbQ8W2oOb8Owpj2Jr_U7xh4-2a0/view DU BLE]2.Follow the Teltonika settings in the right corner below in the configurator [[File:Imageaaveda.png|833x833px]] 3. Open Preset Settings and find preset file, that you downloaded earlier [[File:Imageacacac.png|839x839px]] 4. Choose the downloaded preset file [[File:Imagecavcf.png|837x837px]] [[File:Imageavdsfbdn.png|837x837px]]5. After that you will find our preset file in the preset list [[File:Imageacevsd.png|837x837px]]

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

Teltonika-BLE

2026-01-14T11:44:03Z

ANATOLYI: /* Direct BT connection (no adapter) */

[[es:TD-BLE]]

= <big>'''Qiuck start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)
1.Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2).
{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Imagesbsb.png|353x353px]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}
2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below

[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows:

- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4).

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6):

- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE, “Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

== I/O tab settings ==
6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level).

In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

== System settings ==
7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8)

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9).

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10)

[[File:Antenna direction.png]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows:

== [[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]] ==
Fig. 11 Connections and IO list

11. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes.

[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =
1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13).

[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14)

[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15)
{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17)
{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18)

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19)

[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20)

[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''.

The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]

Fig. 21 I/O tab LLS parameters

9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below

[[File:Photo 5418063427176959131 x.jpg]]

[[File:Imageacas.png]]

Fig. 22 io_ list (partial)

10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB'''

[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

=== 11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24) ===
[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]

Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

== Lost Connection ==
If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data.

Before installing a BLE sensor and a tracker, you need to check the stability of the Bluetooth connection to select the best spot to install the GPS tracker/gateway (or BLE-RS485-RS232 adapter) at to minimize the risks of connection losses happening in the future.

To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, you should calculate the average RSSI (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on.

The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range.

In case of the Bluetooth 4.0 the connection stability range is the value from -35 dBm to -85 dBm. If the average RSSI is less than -85 dBm (for example, -90 dBm), placing the tracker/gateway where it was during the RSSI check will most probably lead to the connection instability. As a result, not all the sensor's data packages will be received by the tracker.

The solution is to try and turn the tracker around a bit or move it closer to the sensor and placing it at a spot where the average RSSI will be within the -35...-85 dBm range. Alternatively, you could install our BLE-RS485-RS232 BA_BLE adapter/base that tends to perform better than the Bluetooth modules of the trackers.

Please, note that the RSSI is calculated by the receiver, so the connection quality is determined by the receiver and also depends on the receiver's sensitivity.

== Presets ==
You can also downolad our '''TD 150 BLE''' and '''DU BLE''' presets for Teltonika tracker manually

# First of all, download preset file from the links below: [https://drive.google.com/file/d/1_wiyNRlUvUn0JarXYwcJNpeahZNlH1Fw/view TD 150 BLE] [https://drive.google.com/file/d/1xQgTjlbQ8W2oOb8Owpj2Jr_U7xh4-2a0/view DU BLE]2.Follow the Teltonika settings in the right corner below in the configurator [[File:Imageaaveda.png|833x833px]] 3. Open Preset Settings and find preset file, that you downloaded earlier [[File:Imageacacac.png|839x839px]] 4. Choose the downloaded preset file [[File:Imagecavcf.png|837x837px]] [[File:Imageavdsfbdn.png|837x837px]]5. After that you will find our preset file in the preset list [[File:Imageacevsd.png|837x837px]]

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

Teltonika-BLE

2026-01-14T11:41:53Z

ANATOLYI: /* Direct BT connection (no adapter) */

[[es:TD-BLE]]

= <big>'''Qiuck start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)

=== 1.Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2). ===
{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Imagesbsb.png|353x353px]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}

=== 2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below ===
[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

=== 3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows: ===
- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

=== 4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4). ===

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

=== 5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6): ===
- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE, “Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

== I/O tab settings ==

=== 6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level). ===
In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

== System settings ==

=== 7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8) ===

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

=== 8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9). ===

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

=== 9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10) ===

[[File:Antenna direction.png]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

=== 10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows: ===

== [[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]] ==
Fig. 11 Connections and IO list

=== 11. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes. ===
[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =

=== 1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13). ===
[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

=== 2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14) ===
[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

=== 3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15) ===
{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

=== 4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17) ===
{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

=== 5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18) ===

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

=== 6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19) ===
[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

=== 7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20) ===
[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

=== 8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''. ===
The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]

Fig. 21 I/O tab LLS parameters

=== 9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below ===
[[File:Photo 5418063427176959131 x.jpg]]

[[File:Imageacas.png]]

Fig. 22 io_ list (partial)

=== 10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB''' ===
[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

=== 11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24) ===
[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]

Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

== Lost Connection ==
If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data.

Before installing a BLE sensor and a tracker, you need to check the stability of the Bluetooth connection to select the best spot to install the GPS tracker/gateway (or BLE-RS485-RS232 adapter) at to minimize the risks of connection losses happening in the future.

To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, you should calculate the average RSSI (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on.

The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range.

In case of the Bluetooth 4.0 the connection stability range is the value from -35 dBm to -85 dBm. If the average RSSI is less than -85 dBm (for example, -90 dBm), placing the tracker/gateway where it was during the RSSI check will most probably lead to the connection instability. As a result, not all the sensor's data packages will be received by the tracker.

The solution is to try and turn the tracker around a bit or move it closer to the sensor and placing it at a spot where the average RSSI will be within the -35...-85 dBm range. Alternatively, you could install our BLE-RS485-RS232 BA_BLE adapter/base that tends to perform better than the Bluetooth modules of the trackers.

Please, note that the RSSI is calculated by the receiver, so the connection quality is determined by the receiver and also depends on the receiver's sensitivity.

== Presets ==
You can also downolad our '''TD 150 BLE''' and '''DU BLE''' presets for Teltonika tracker manually

# First of all, download preset file from the links below: [https://drive.google.com/file/d/1_wiyNRlUvUn0JarXYwcJNpeahZNlH1Fw/view TD 150 BLE] [https://drive.google.com/file/d/1xQgTjlbQ8W2oOb8Owpj2Jr_U7xh4-2a0/view DU BLE]2.Follow the Teltonika settings in the right corner below in the configurator [[File:Imageaaveda.png|833x833px]] 3. Open Preset Settings and find preset file, that you downloaded earlier [[File:Imageacacac.png|839x839px]] 4. Choose the downloaded preset file [[File:Imagecavcf.png|837x837px]] [[File:Imageavdsfbdn.png|837x837px]]5. After that you will find our preset file in the preset list [[File:Imageacevsd.png|837x837px]]

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

Teltonika-BLE

2026-01-14T11:37:18Z

ANATOLYI: /* Direct BT connection (no adapter) */

[[es:TD-BLE]]

= <big>'''Qiuck start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)

== 1.Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2). ==
{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Imagesbsb.png|353x353px]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}

== 2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below ==
[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

== 3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows: ==
- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

== 4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4). ==

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

== 5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6): ==
- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE, “Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

== 6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level). ==
In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

== 7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8) ==

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

== 8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9). ==

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

== 9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10) ==

[[File:Antenna direction.png]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

== 10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows: ==

== [[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]] ==
Fig. 11 Connections and IO list

== 11. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes. ==
[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =

== 1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13). ==
[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

== 2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14) ==
[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

== 3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15) ==
{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

== 4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17) ==
{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

== 5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18) ==

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

== 6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19) ==
[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

== 7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20) ==
[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

== 8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''. ==

The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]

Fig. 21 I/O tab LLS parameters

== 9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below ==
[[File:Photo 5418063427176959131 x.jpg]]

[[File:Imageacas.png]]

Fig. 22 io_ list (partial)

== 10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB''' ==
[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

== 11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24) ==
[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]

Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

== Lost Connection ==
If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000/300 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor if it was connected via the BLE base, or '''0\-4\65532''' in the fuel data.

Before installing a BLE sensor and a tracker, you need to check the stability of the Bluetooth connection to select the best spot to install the GPS tracker/gateway (or BLE-RS485-RS232 adapter) at to minimize the risks of connection losses happening in the future.

To determine if the connection between the Bluetooth transmitter of the sensor and the Bluetooth receiver is stable or not, you should use the RSSI parameter. When you search for a place to install the GPS tracker, you should calculate the average RSSI (Received Signal Strength Indicator) by taking into account the 10 or more measurements of the RSSI taken over the course of 2-3 minutes while the engine of the vehicle is running and all electronics inside the cab and around the vehicle are switched on.

The reason why the RSSI should be taken as the average value is that the RSSI itself is a dynamic parameter, its value changes constantly. This average value must be within the connection stability range.

In case of the Bluetooth 4.0 the connection stability range is the value from -35 dBm to -85 dBm. If the average RSSI is less than -85 dBm (for example, -90 dBm), placing the tracker/gateway where it was during the RSSI check will most probably lead to the connection instability. As a result, not all the sensor's data packages will be received by the tracker.

The solution is to try and turn the tracker around a bit or move it closer to the sensor and placing it at a spot where the average RSSI will be within the -35...-85 dBm range. Alternatively, you could install our BLE-RS485-RS232 BA_BLE adapter/base that tends to perform better than the Bluetooth modules of the trackers.

Please, note that the RSSI is calculated by the receiver, so the connection quality is determined by the receiver and also depends on the receiver's sensitivity.

== Presets ==
You can also downolad our '''TD 150 BLE''' and '''DU BLE''' presets for Teltonika tracker manually

# First of all, download preset file from the links below: [https://drive.google.com/file/d/1_wiyNRlUvUn0JarXYwcJNpeahZNlH1Fw/view TD 150 BLE] [https://drive.google.com/file/d/1xQgTjlbQ8W2oOb8Owpj2Jr_U7xh4-2a0/view DU BLE]2.Follow the Teltonika settings in the right corner below in the configurator [[File:Imageaaveda.png|833x833px]] 3. Open Preset Settings and find preset file, that you downloaded earlier [[File:Imageacacac.png|839x839px]] 4. Choose the downloaded preset file [[File:Imagecavcf.png|837x837px]] [[File:Imageavdsfbdn.png|837x837px]]5. After that you will find our preset file in the preset list [[File:Imageacevsd.png|837x837px]]

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

File:Imageacevsd.png

2026-01-14T11:35:03Z

ANATOLYI:

vsfdbsrg

File:Imageavdsfbdn.png

2026-01-14T11:33:42Z

ANATOLYI:

sfbfs

File:Imagecavcf.png

2026-01-14T11:32:32Z

ANATOLYI:

advxva

File:Imageacacac.png

2026-01-14T11:30:55Z

ANATOLYI:

wacscavds

File:Imageaaveda.png

2026-01-14T11:29:17Z

ANATOLYI:

srvsvve

File:Imagesbsb.png

2026-01-14T11:23:05Z

ANATOLYI:

ssbsdb

File:Imageacas.png

2026-01-14T11:14:40Z

ANATOLYI:

dawca

Teltonika-BLE

2026-01-13T12:33:31Z

ANATOLYI: /* Полезные ссылки */

[[es:TD-BLE]]

= <big>'''Qiuck start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)

# Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2).

{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Photo 5418063427176959103 m.jpg|frameless]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}
2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below

[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows:

- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4).

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6):

- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE

“Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level).

In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8)

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9).

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10)

[[File:Photo 5418063427176959103 mыкм.jpg|frameless]] [[File:Photo 5418063427176959117 m.jpg|frameless|298x298px]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows:

[[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]]

Fig. 11 Connections and IO list

11. If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor.

12. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes.

[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =
1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13).

[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14)

[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15)

{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17)

{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18)

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19)

[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20)

[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''.

The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]Fig. 21 I/O tab LLS parameters

9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below

[[File:Photo 5418063427176959131 x.jpg]]

Fig. 22 io_ list (partial)

10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB'''

[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24)

[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

Teltonika-BLE

2026-01-13T12:33:05Z

ANATOLYI: Polniy prernos kak est'

[[es:TD-BLE]]

= <big>'''Qiuck start: Connecting Escort BLE sensors to Teltonika trackers via Bluetooth'''</big> =

= Direct BT connection (no adapter) =
Currently, '''the TD-BLE, DU-BLE and TL-BLE are compatible with certain Teltonika models''' (see the list on the last page of this document; note that it is not definitive; for a more precise list, please, contact Teltonika’s tech support).

* Up to 4 sensors can be connected to the majority of different Teltonika models via Bluetooth
* In case your tracker has the Rs485 port, the sensors can be connected to such tracker by means of the BLE-Rs485 adapter (also called ‘'''base'''’ sometimes)

# Before connecting the sensor, find '''its MAC address''' via Escort app for Android devices (Apple devices don’t give access to MAC addresses of any devices) or directly on the sensor’s body (Fig.1 and Fig.2).

{| class="wikitable"
|[[File:Imageфсы.png|frameless]]
|[[File:Photo 5418063427176959103 m.jpg|frameless]]
|-
|Fig.1 MAC address in the app
|Fig.2 MAC address on the sensor’s head
|}
2. In the Teltonika configurator, go to the '''Bluetooth''' tab first. Make sure that everything is configured as shown on the Fig. 3 below

[[File:Photo 5418063427176959105 x.jpg|frameless|408x408px]]

3. On the '''Bluetooth 4.0 tab''' (Fig. 4), configure '''the''' '''BLE Scan settings''' as follows:

- disable the '''Non Stop Scan'''

- set '''update frequency''' at 30 seconds (this is the min value)

- BLE '''scan duration''' should be 15-20 seconds

- Scan retries until error can be left at 30 (this is actually how many times the tracker will try to get any data from the sensor before sending a connection error code in case of a loss of connection with the sensor)

- Set '''BT Power level''' to 7

- switch the '''BLE Connection control''' to '''Allow'''

4. Further below you have 4 '''Connection slots''' to connect up to 4 sensors (those can be any TD, DU or TL sensors). Click on the '''Advanced''' button and then '''enter the MAC address''' of the sensor (Fig. 4).

[[File:Photo 5418063427176959106 xs.jpg|frameless|495x495px]]

5.Then, click on the '''preset button''' (Fig. 5) and select '''the preset required for a certain sensor model''' and click on the '''Load''' button (Fig. 6):

- “escort fuel” for TD-BLE,

- “escort luminosity” or “escort temperature” for TL-BLE

“Escort_DU-BLE_Angle_sensor” for DU-BLE

[[File:Photo 5418063427176959107 x.jpg|frameless|645x645px]]

[[File:Photo 5418063427176959111 x.jpg|frameless|645x645px]]

6. Next, go to the I/O tab (Fig. 7) and select the '''Low option in the Priority column''' for the '''BLE Fuel Level''' and '''BLE Temperature''' (BLE Battery Charge is optional) parameters for TD or TL-BLE sensors (luminosity = fuel level).

In case of a DU-BLE, you may want to set the '''Operand''' option to the '''On Change''' and configure the '''Event Only''' option as '''Yes''' for the BLE Temperature parameter that corresponds to the Event notification sent by the sensor. Then, whenever the '''sensor’s Event Notification''' changes (it might be happening every time the tap of a hatch is opened, for example), the tracker will transmit an extra message to the server immediately upon receiving a new Event Notification.

[[File:Photo 5418063427176959112 x.jpg|frameless|700x700px]]

Fig. 7 I/O tab

To find the io_ you need on the monitoring platform, check the following table:

[[File:Photo 5418063427176959113 x.jpg|frameless|700x700px]]

7.In the '''System''' tab, click on the '''Codec 8 Extended''' option (Fig. 8)

[[File:Photo 5418063427176959114 x.jpg|frameless|635x635px]]

Fig. 8 System. Data Protocol. Codec 8 Extended

8. When selecting the installation spot for the tracker, check the '''RSSI (Signal Strength)''' in the Bluetooth 4.0 tab by clicking on the '''Discover BLE''' button during 2-3 minutes (Fig. 9).

The average value must be from '''-45 to -85 dB''' for optimal connection stability.

[[File:Photo 5418063427176959116 x.jpg|frameless|570x570px]] Fig. 9 Checking RSSI is vital

9. Remember to orient the sensor with the tracker so that the sensor’s and the tracker’s Bluetooth antenna were facing each other (Fig. 10)

[[File:Photo 5418063427176959103 mыкм.jpg|frameless]] [[File:Photo 5418063427176959117 m.jpg|frameless|298x298px]]

Fig. 10 Sensor and tracker orientation (applicable to both TD-BLE and DU-BLE models)

10. The “io_” parameters (Fig. 11) you need to find in the tracker’s messages on the platform are as follows:

[[File:Photo 5418063427176959129 x.jpg|frameless|523x523px]]

Fig. 11 Connections and IO list

11. If there is a connection loss, after several attempts to collect the data (the '''Scan retries until error''' setting in the Bluetooth 4.0 tab) the tracker will transmit the error '''code 3000 in the temperature io'''. The level value will be transmitted as the last reading transmitted by the sensor.

12. Remember to click on the '''Save to device''' button after changing any configurations in the Teltonika configurator to apply the changes.

[[File:Photo 5418063427176959118 x.jpg|frameless|573x573px]]

Fig. 12 Saving the changes

= Connecting BLE via adapter (BLE-Rs485 base) =
1. First, connect the adapter to your C200M or other Rs485-USB converter and connect the USB cable of the converter to your laptop or computer. It is better if all 4 wires of the adapter are connected to the converter: orange to orange ('''Rs485 Line A'''), white to white ('''Rs485 Line B'''), black to black ('''GND''') and red to red ('''PWR''') (Fig. 13).

[[File:Photo 5418063427176959119 x.jpg|frameless|495x495px]]

Fig. 13 Connecting the adapter to the C200M and to the PC

2. In the Escort configurator for PC, select the COM port that corresponds to the converter that you are using to connect the adapter (to find its number, check the Windows Device manager’s COM and LPT ports section; C200M will be defined there as '''STMicroelectronics Virtual COM port''' device). Then go to the '''BLE''' then click '''BLE adapter settings''' (Fig. 14)

[[File:Photo 5418063427176959122 x.jpg|frameless|372x372px]][[File:Photo 5418063427176959123 m.jpg|frameless]]

Fig. 14 Connecting the adapter in the configurator (the screenshots are taken from 2 different computers this is why the COM number doesn’t coincide)

3. You will see 4 different cells to connect up to 4 sensors (if the base has the '''FW 2.3.8''' and the configurator is of the '''1.0.2.38 version''', you need to scroll down to see more cells) (Fig. 14 and 15)

{| class="wikitable"
|[[File:Photo 5418063427176959892 m.jpg|frameless|275x275px]]
|[[File:Photo 5418063427176959893 m.jpg|frameless]]
|-
|Fig. 14 FW 2.3.5 or older of the base
and the configurator 1.0.2.37 or older
|Fig. 15 FW 2.3.8 or newer of the base
and the configurator 1.0.2.38 or newer
|}

4. Connect the sensor to the first cell before anything else. Click '''Connect sensor''' (Fig. 16) and then enter the '''first letters''' of the sensor’s model (TD, DU, TL or TH), the lower dash _ will appear automatically. Then enter the '''6-digit serial number''' of the sensor, its password and then click '''Establish connection''' (Fig. 17)

{| class="wikitable"
|[[File:Photo 5418063427176959124 m.jpg|frameless]]
|[[File:Photo 5418063427176959125 m.jpg]]
|-
|Fig. 16 Click Connect sensor or Connect another
|Fig. 17 Enter sensor´s letters with serial number
and the password and click '''Establish connection'''
|}

5. For each sensor the base can use 1 or 2 network addresses to transmit the 2 main parameters via the main one and the 2 additional parameter via the auxiliary address. The additional parameters can be switched off (Fig. 18)

'''TD-BLE''': level and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''TL-BLE''': luminosity and temperature via the main address, the battery charge (3.5-3.7V) and the RSSI value via the auxiliary address

'''DU-BLE''': angle value and battery charge (3.5-3.7V) via the main address, the event notification and the RSSI value via the auxiliary address (if the FW of the base is 2.3.8 or newer; in the base with the FW 2.3.3 or older the event notification and the battery charge are switched)

[[File:Photo 5418063427176959126 x.jpg|474x474px]]Fig. 18 Switching the additional parameters off

6. Once the sensor or several sensors are connected to the base, make sure to configure the Rs485 tab of the Teltonika configurator so that the tracker were able to send requests to the network addresses that the base uses to “channel” the data that comes from the sensors (Fig. 19)

[[File:Photo 5418063427176959127 x.jpg|699x699px]]

Fig. 19 Configuring network addresses

7. Then '''disconnect the base from the C200M''' or other converter, connect it to the power supply (black and red wires, the fuse from the kit must be installed in the red wire between the adapter and the power supply) and the '''orange to the line A Rs485''' of the tracker and '''white to the line B Rs485''' (Fig. 20)

[[File:Photo 5418063427176959128 x.jpg]]Fig. 20 Wiring of the base and the tracker via the Rs485 port

8. In the '''I/O tab''' of the Teltonika configurator, select the priority Low (Fig. 21). For DU-BLE’s event notification consider setting '''Event Only''' to '''Yes''' and the '''Operand''' to '''On Change'''.

The '''DU-BLE’s event notification''' can be transmitted either as a '''LLS Fuel Level''' parameter (if the adapter/base has the FW 2.3.8 or newer) or as a '''LLS Temperature''' parameter (FW 2.3.3 or older).

[[File:Photo 5418063427176959129 x.jpg]]Fig. 21 I/O tab LLS parameters

9. The io list for the wired adapter (as well as for the wired sensors) is partially shown below

[[File:Photo 5418063427176959131 x.jpg]]

Fig. 22 io_ list (partial)

10. When selecting the spot to install the adapter on, be sure to assess its average '''RSSI value''' over the course of 2-3 minutes in the '''Escort configurator''' (Fig. 23). It must be falling into the range from '''-45 to -85 dB'''

[[File:Photo 5418063427176959132 x.jpg]]Fig. 23 RSSI check

11. Properly orient the Bluetooth antennas of the sensor and the adapter (Fig. 24)

[[File:Photo 5418063427176959103 mыкм.jpg]][[File:Photo 5418063427176959133 m.jpg]]

Fig. 24 Orienting the adapter and the sensor

= Connecting TH-BLE via Rs485-BLE adapter/base =
The TH-BLE sensor can be connected to any Teltonika only via the BLE-Rs485 adapter (as of 1st of July, 2021).

The sensor transmits several parameters. Their list varies from one (earlier release) version to the other (newer release) version.

They are: '''atmospheric pressure''' (earlier release only), '''temperature''', '''humidity''', '''luminosity''' (newer release only), '''battery charge'''.

The RSSI parameter is calculated by the BLE-Rs485 adapter. It is not transmitted by the sensor.

In case of a TH-BLE, the adapter/base can use up to 2 addresses to channel the data that comes from the sensor.

Depending on the preset you select, the order in which the parameters are transmitted to the tracker changes (Fig. 25 and 26).

[[File:Photo 5418063427176959135 x.jpg]]

[[File:Photo 5418063427176959136 x.jpg]]Fig. 25 Selecting preset
Fig. 26 Parameters transmitted via addresses 1 and 2

= BLE Fuel Level missing in I/O =
'''If you cannot find the BLE Fuel Level parameter in the I/O tab''' of a newer version of Teltonika configurator, please, use one of the old ones available via the links below.

The links allow you to download a compressed file with an old FW version (you don’t need to install it onto the tracker) and an older version of the configurator for different tracker models.

The password for the compressed file is '''1234'''

= Compatibility list =
'''FMB110, FMB120, FMB122, FMB125, FMB130, FMB900, FMB920, FMB001, FMB010, FMB202, FMB204, FMB962, FMB964, FM3001'''

FW: 03.25.15.Rev.01

Configurator: 1.5.5_B.3.25_C.100

Link:https://drive.google.com/open?id=1_QeVFGrHnaVOtXIrmK2oZH7CouotzCYV

'''FMU125, FMU130, FMM125, FMM130, FMC125, FMC130'''

FW: 03.25.15.Rev.87

Configurator: 1.5.6_E.3.25_C.083

Link:https://drive.google.com/open?id=1GP-rGLIcjRqO4afI7aufZx_arwy32z8Y

'''FMB140'''

FW: 03.25.15.Rev.143

Configurator: 1.5.5_E.3.25_C.142

Link:https://drive.google.com/open?id=1ANb4mzA6RIqGTvAuEM97NiPc2FnNVqDS

= '''<big>Полезные ссылки</big>''' =

File:Photo 5418063427176959136 x.jpg

2026-01-13T12:32:29Z

ANATOLYI:

dawfavawf

File:Photo 5418063427176959135 x.jpg

2026-01-13T12:32:07Z

ANATOLYI:

dawdawf

File:Photo 5418063427176959133 m.jpg

2026-01-13T12:31:15Z

ANATOLYI:

acacadw

File:Photo 5418063427176959132 x.jpg

2026-01-13T12:29:43Z

ANATOLYI:

avavav

File:Photo 5418063427176959131 x.jpg

2026-01-13T12:29:21Z

ANATOLYI:

cawaca

File:Photo 5418063427176959128 x.jpg

2026-01-13T12:27:08Z

ANATOLYI:

avbravb

File:Photo 5418063427176959127 x.jpg

2026-01-13T12:26:41Z

ANATOLYI:

cafvavaw

File:Photo 5418063427176959126 x.jpg

2026-01-13T12:25:51Z

ANATOLYI:

awfaefa

File:Photo 5418063427176959125 m.jpg

2026-01-13T12:25:02Z

ANATOLYI:

acaedawd

File:Photo 5418063427176959893 m.jpg

2026-01-13T12:23:41Z

ANATOLYI:

wvevsev

File:Photo 5418063427176959892 m.jpg

2026-01-13T12:22:18Z

ANATOLYI:

acvadvava

File:Photo 5418063427176959124 m.jpg

2026-01-13T12:17:10Z

ANATOLYI:

фмфмыаи

File:Photo 5418063427176959123 m.jpg

2026-01-13T12:16:45Z

ANATOLYI:

фмфмфму

File:Photo 5418063427176959122 x.jpg

2026-01-13T12:15:36Z

ANATOLYI:

фымыиитеикы

File:Photo 5418063427176959119 x.jpg

2026-01-13T12:14:50Z

ANATOLYI:

фсфмвмф

File:Photo 5418063427176959118 x.jpg

2026-01-13T12:13:02Z

ANATOLYI:

сфмвмм

File:Photo 5418063427176959129 x.jpg

2026-01-13T12:11:48Z

ANATOLYI:

ымкиы

File:Photo 5418063427176959103 mыкм.jpg

2026-01-13T12:09:10Z

ANATOLYI:

мыкиуеткыи аи

File:Photo 5418063427176959117 m.jpg

2026-01-13T12:08:34Z

ANATOLYI:

фмфвмф

File:Photo 5418063427176959116 x.jpg

2026-01-13T12:04:23Z

ANATOLYI:

фцфаф

File:Photo 5418063427176959114 x.jpg

2026-01-13T12:03:27Z

ANATOLYI:

ывмывм

File:Photo 5418063427176959113 x.jpg

2026-01-13T11:59:51Z

ANATOLYI:

сфмыы

File:Imageсфысф.png

2026-01-13T11:57:34Z

ANATOLYI:

фм аыиимумф

File:Photo 5418063427176959112 x.jpg

2026-01-13T11:55:46Z

ANATOLYI:

acavsdv