TELEMATICS FOR AGRICULTURE AND FARMING INDUSTRY: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
m (Text replacement - "Bluetooth(?!®)" to "Bluetooth®")
 
(5 intermediate revisions by one other user not shown)
Line 7: Line 7:


==Solution description==
==Solution description==
Thanks to the fast-developing IoT technologies, agriculture-specific equipment, farming implements, and/or accessories tracking and management can be successfully achieved by combining GPS devices, CAN Bus data adaptors, and Bluetooth Low Energy 4.X (BLE) ID beacons. The ultimate choice for this matter - Teltonika ADVANCED category GPS tracker FMB140 with built-in CAN data reading feature and advanced software version supporting agriculture type vehicles (aka ALL-CAN300 option). The main advantage is the ability to receive specific agricultural vehicle data via the CAN bus via the Agricultural State Flag parameter. It is possible to obtain such special data as the position of the joystick, the position and status of hydraulic tools, the status of the grain tank and more.
Thanks to the fast-developing IoT technologies, agriculture-specific equipment, farming implements, and/or accessories tracking and management can be successfully achieved by combining GPS devices, CAN Bus data adaptors, and Bluetooth® Low Energy 4.X (BLE) ID beacons. The ultimate choice for this matter - Teltonika ADVANCED category GPS tracker FMB140 with built-in CAN data reading feature and advanced software version supporting agriculture type vehicles (aka ALL-CAN300 option). The main advantage is the ability to receive specific agricultural vehicle data via the CAN bus via the Agricultural State Flag parameter. It is possible to obtain such special data as the position of the joystick, the position and status of hydraulic tools, the status of the grain tank and more. Also, using BLE sensors and beacons, you can get additional parameters that are not provided by standard sensors. This can be raising or lowering of the dump truck body and cab, temperature and humidity in the chamber. You can also track expensive equipment using BLE beacons.


==What you need for a solution?==
==What you need for a solution?==
Line 29: Line 29:


<br />
<br />
[[File:Ble mount.jpg|thumb500x600px]]


 
The installation of BLE sensors and beacons is quite simple, you need to install the sensor in a suitable place using screws or double-sided tape and install the required configuration in the tracker and sensor. This gives a huge advantage over wired sensors, since there is no need to pull wires, which means you can seriously save on the services of an electrician!
<br />
==Configuration==
==Configuration==


Line 139: Line 141:
<br />
<br />
<br />
<br />
'''Quickstart:''' From default configuration to Car sharing solution in one SMS:
<br />
<br />
<br />
<br />
'''Quickstart:''' From default configuration to AGRICULTURE AND FARMING INDUSTRY solution in one SMS:
  "  setparam <span style="background-color:#91b9d4;">2001</span>:APN;<span style="background-color:#91d4b9;">2002</span>:APN_user;<span style="background-color:#b991d4;">2003</span>:APN_password;<span style="background-color:#b9d491;">2004</span>:Domain;<span style="background-color:#d491b9;">2005</span>:Port;<span style="background-color:#d4b991;">2006</span>:0;<span style="background:#05CC6F">102</span>:3;<span style="background:#E18DE7">45002</span>:Program number;<span style="background-color:#dee11d;">45001</span>:0;<span style="background-color:#1de1d2;"> 45100</span>:1;<span style="background-color:#e1701d;"> 45160</span>:1;<span style="background-color:#bce5d7;"> 45130</span>:1;<span style="background-color:#e1701d;"> 45140</span>:1;<span style="background-color:#e1701d;"> 46060</span>:1;<span style="background-color:#02BD2F;"> 113</span>:1"
  "  setparam <span style="background-color:#91b9d4;">2001</span>:APN;<span style="background-color:#91d4b9;">2002</span>:APN_user;<span style="background-color:#b991d4;">2003</span>:APN_password;<span style="background-color:#b9d491;">2004</span>:Domain;<span style="background-color:#d491b9;">2005</span>:Port;<span style="background-color:#d4b991;">2006</span>:0;<span style="background:#05CC6F">102</span>:3;<span style="background:#E18DE7">45002</span>:Program number;<span style="background-color:#dee11d;">45001</span>:0;<span style="background-color:#1de1d2;"> 45100</span>:1;<span style="background-color:#e1701d;"> 45160</span>:1;<span style="background-color:#bce5d7;"> 45130</span>:1;<span style="background-color:#e1701d;"> 45140</span>:1;<span style="background-color:#e1701d;"> 46060</span>:1;<span style="background-color:#02BD2F;"> 113</span>:1"
This SMS will set up your device to report object location to the server and possibility for read Engine RPM, Fuel level in %, Fuel level in ltr*10 and Vehicle speed parameters.
This SMS will set up your device to report object location to the server and possibility for read Engine RPM, Fuel level in %, Fuel level in ltr*10 and Vehicle speed parameters.


'''Note''': Before SMS text, two space symbols should be inserted if no SMS username or password was set in SMS \ Call settings.
'''Note''': Before SMS text, two space symbols should be inserted if no SMS username or password was set in SMS \ Call settings.
<br />
<br />
To use BLE sensors, use the configurator in online mode (tracker is connected) or offline (tracker is disabled). When using the configurator in offline mode, you can remotely download the configuration via FOTA WEB.
[[File:BLE SET.jpg|thumb|1200x1200px]]
[[File:BLE IO.jpg|thumb|alt=|left|1200x1200px]]
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />


==Parsing information==
==Parsing information==
Line 157: Line 195:
! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
|-
|-
| style="vertical-align: middle; text-align: center;" | 00000000000000848E010000017CE9B241900000000000000000000000000000000000000015000700EF0100F00100150500C800004502<span style="background:#0b9768">0051</span>00005900000900B5000000B600000042385C0043000000440000001A090E00680023
| style="vertical-align: middle; text-align: center;" | 00000000000000848E010000017CE9B241900000000000000000000000000000000000000015000700EF0100F00100150500C800004502<span style="background:#0b9768">0051</span>00005900000900B5000000B600000042385C0
<span style="background:#0b9768">0054</span>0000<span style="background:#0b9768">0055</span>0000000400F10000646600100000000001D400FDFFFF<span style="background:#0b9768">0057</span>000000000001<span style="background:#0b9768">0208</span>000000000000000000000100000647
<br />
043000000440000<span style="background:#0b9768">001A</span>090E<span style="background:#0b9768">0068</span>0023
<span style="background:#0b9768">0054</span>0000<span style="background:#0b9768">0055</span>0000000400F100006466001000000000<span style="background:#0b9768">01D4</span>00FDFFFF<span style="background:#0b9768">0057</span>000000000001<span style="background:#0b9768">0208</span>000000000000000000000100000647




Line 171: Line 211:
|-
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 53
| style="vertical-align: middle; text-align: center;" |00 00 00 84
|-
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |08 (Codec 8)
| style="vertical-align: middle; text-align: center;" |8E (Codec 8 Extended)
|-
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Number of Total Records)
Line 180: Line 220:
|-
|-
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 7C E4 AD 48 70 (03.11.2021  7:22:14)
| style="vertical-align: middle; text-align: center;" |00 00 01 7C E9 B2 41 90 (04.11.2021  6:45:46)
|-
|-
| style="vertical-align: middle; text-align: center;" | Priority
| style="vertical-align: middle; text-align: center;" | Priority
Line 204: Line 244:
|-
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00
| style="vertical-align: middle; text-align: center;" |00 00
|-
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |17
| style="vertical-align: middle; text-align: center;" |00 21
|-
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |07
| style="vertical-align: middle; text-align: center;" |00 07
|-
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |EF (AVL ID: 239, Name: Ignition)
| style="vertical-align: middle; text-align: center;" |00 EF (AVL ID: 239, Name: Ignition)
|-
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |1’st IO Value
Line 219: Line 259:
|-
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |F0  (AVL ID: 240, Name: Movement)
| style="vertical-align: middle; text-align: center;" |00 F0  (AVL ID: 240, Name: Movement)
|-
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
Line 225: Line 265:
|-
|-
| style="vertical-align: middle; text-align: center;" | 3’rd IO ID
| style="vertical-align: middle; text-align: center;" | 3’rd IO ID
| style="vertical-align: middle; text-align: center;" |15 (AVL ID: 21, Name: GSM Signal)
| style="vertical-align: middle; text-align: center;" |00 15 (AVL ID: 21, Name: GSM Signal)
|-
|-
| style="vertical-align: middle; text-align: center;" | 3’rd IO Value
| style="vertical-align: middle; text-align: center;" | 3’rd IO Value
Line 231: Line 271:
|-
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |C8 (AVL ID: 200, Sleep Mode)
| style="vertical-align: middle; text-align: center;" |00 C8 (AVL ID: 200, Sleep Mode)
|-
|-
| style="vertical-align: middle; text-align: center;" |4'th IO Value
| style="vertical-align: middle; text-align: center;" |4'th IO Value
Line 237: Line 277:
|-
|-
| style="vertical-align: middle; text-align: center;" |5'th IO ID
| style="vertical-align: middle; text-align: center;" |5'th IO ID
| style="vertical-align: middle; text-align: center;" |45 (AVL ID: 69, GNSS Status)
| style="vertical-align: middle; text-align: center;" |00 45 (AVL ID: 69, GNSS Status)
|-
|-
| style="vertical-align: middle; text-align: center;" |5'th IO Value
| style="vertical-align: middle; text-align: center;" |5'th IO Value
Line 243: Line 283:
|-
|-
| style="vertical-align: middle; text-align: center;" |6'th IO ID
| style="vertical-align: middle; text-align: center;" |6'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">51</span> (AVL ID: 81, Vehicle Speed)
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 51</span> (AVL ID: 81, Vehicle Speed)
|-
|-
| style="vertical-align: middle; text-align: center;" |6'th IO Value
| style="vertical-align: middle; text-align: center;" |6'th IO Value
Line 249: Line 289:
|-
|-
| style="vertical-align: middle; text-align: center;" |7'th IO ID
| style="vertical-align: middle; text-align: center;" |7'th IO ID
| style="vertical-align: middle; text-align: center;" |59 (AVL ID: 89, Fuel level)
| style="vertical-align: middle; text-align: center;" |00 59 (AVL ID: 89, Fuel level)
|-
|-
| style="vertical-align: middle; text-align: center;" |7'th IO Value
| style="vertical-align: middle; text-align: center;" |7'th IO Value
Line 255: Line 295:
|-
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Byte IO
| style="vertical-align: middle; text-align: center;" |N2 of Two Byte IO
| style="vertical-align: middle; text-align: center;" |07
| style="vertical-align: middle; text-align: center;" |00 09
|-
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |B5 (AVL ID: 181, GNSS PDOP)
| style="vertical-align: middle; text-align: center;" |00 B5 (AVL ID: 181, GNSS PDOP)
|-
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |1’st IO Value
Line 264: Line 304:
|-
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |B6 (AVL ID: 182, GNSS HDOP)
| style="vertical-align: middle; text-align: center;" |00 B6 (AVL ID: 182, GNSS HDOP)
|-
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
Line 271: Line 311:
|-
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, External Voltage)
| style="vertical-align: middle; text-align: center;" |00 42 (AVL ID: 66, External Voltage)
|-
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |32 35
| style="vertical-align: middle; text-align: center;" |38 5C
|-
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |43 (AVL ID: 67, Battery Voltage)
| style="vertical-align: middle; text-align: center;" |00 43 (AVL ID: 67, Battery Voltage)
|-
|-
| style="vertical-align: middle; text-align: center;" |4'th IO Value
| style="vertical-align: middle; text-align: center;" |4'th IO Value
Line 283: Line 323:
|-
|-
| style="vertical-align: middle; text-align: center;" |5'th IO ID
| style="vertical-align: middle; text-align: center;" |5'th IO ID
| style="vertical-align: middle; text-align: center;" |44 (AVL ID: 68, Battery Current)
| style="vertical-align: middle; text-align: center;" |00 44 (AVL ID: 68, Battery Current)
|-
|-
| style="vertical-align: middle; text-align: center;" |5'th IO Value
| style="vertical-align: middle; text-align: center;" |5'th IO Value
Line 289: Line 329:
|-
|-
| style="vertical-align: middle; text-align: center;" |6'th IO ID
| style="vertical-align: middle; text-align: center;" |6'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">54</span> (AVL ID: 84, Fuel level)
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 1A</span> (AVL ID: 26, BLE Temperature #2)
|-
|-
| style="vertical-align: middle; text-align: center;" |6'th IO Value
| style="vertical-align: middle; text-align: center;" |6'th IO Value
| style="vertical-align: middle; text-align: center;" |00 00
| style="vertical-align: middle; text-align: center;" |09 0E
|-
|-
| style="vertical-align: middle; text-align: center;" |7'th IO ID
| style="vertical-align: middle; text-align: center;" |7'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">55</span> (AVL ID: 85, Engine RPM)
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 68</span> (AVL ID: 26, BLE Humidity #2)
|-
|-
| style="vertical-align: middle; text-align: center;" |7'th IO Value
| style="vertical-align: middle; text-align: center;" |7'th IO Value
| style="vertical-align: middle; text-align: center;" |00 23
|-
| style="vertical-align: middle; text-align: center;" |8'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 54</span> (AVL ID: 84, Fuel level)
|-
| style="vertical-align: middle; text-align: center;" |8'th IO Value
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |9'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 55</span> (AVL ID: 85, Engine RPM)
|-
| style="vertical-align: middle; text-align: center;" |9'th IO Value
| style="vertical-align: middle; text-align: center;" |00 00
| style="vertical-align: middle; text-align: center;" |00 00
|-
|-
| style="vertical-align: middle; text-align: center;" |N4 of Four Byte IO
| style="vertical-align: middle; text-align: center;" |N4 of Four Byte IO
| style="vertical-align: middle; text-align: center;" |02
| style="vertical-align: middle; text-align: center;" |00 04
|-
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |F1 (AVL ID: 241, Active GSM Operator)
| style="vertical-align: middle; text-align: center;" |00 F1 (AVL ID: 241, Active GSM Operator)
|-
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |1’st IO Value
Line 310: Line 362:
|-
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |10 (AVL ID: 16, Total Odometer)
| style="vertical-align: middle; text-align: center;" |00 10 (AVL ID: 16, Total Odometer)
|-
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
Line 316: Line 368:
|-
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">57</span> (AVL ID:87, Total Mileage)
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">01 D4</span> (AVL ID: 468, BLE 2 Custom #3)
|-
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |00 FD FF FF
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 57</span> (AVL ID:87, Total Mileage)
|-
| style="vertical-align: middle; text-align: center;" |4'th IO Value
| style="vertical-align: middle; text-align: center;" |00 00 00 00
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
|-
| style="vertical-align: middle; text-align: center;" |N8 of Eight Byte IO
| style="vertical-align: middle; text-align: center;" |N8 of Eight Byte IO
| style="vertical-align: middle; text-align: center;" |00
| style="vertical-align: middle; text-align: center;" |00 01
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">02 08</span> (AVL ID: 520, Agricultural State Flags_P4)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 00 00 00 00 00 00 00
|-
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
Line 328: Line 392:
|-
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 65 12
| style="vertical-align: middle; text-align: center;" |00 00 06 47
|}
|}
 
<br />
 
<br />
<br />
<br />
[[File:Asf.jpg|thumb750x600px]]
<br />
<br />
The Agricultural State Flag can be interpreted from this table, which can be found [https://wiki.teltonika-gps.com/view/FMB140_CAN_adapters#ALL-CAN300_Agricultural_State_Flags'''here.'''] Each bit carries useful information that can be obtained.
==Demonstration in platform==
==Demonstration in platform==



Latest revision as of 15:28, 28 December 2023

Main Page > General Information > Usage scenarios > TELEMATICS FOR AGRICULTURE AND FARMING INDUSTRY


Introduction

To satisfy the growing demand for farming produce and tackle many challenges affecting the agriculture industry, present-day farmers have to be more innovative, efficient, competitive, but save resources at the same time. As a result, comprehensive, affordable, and customisable agricultural machinery tracking solutions combined with process monitoring and automation are becoming not only an attractive option but rather a necessity.

Solution description

Thanks to the fast-developing IoT technologies, agriculture-specific equipment, farming implements, and/or accessories tracking and management can be successfully achieved by combining GPS devices, CAN Bus data adaptors, and Bluetooth® Low Energy 4.X (BLE) ID beacons. The ultimate choice for this matter - Teltonika ADVANCED category GPS tracker FMB140 with built-in CAN data reading feature and advanced software version supporting agriculture type vehicles (aka ALL-CAN300 option). The main advantage is the ability to receive specific agricultural vehicle data via the CAN bus via the Agricultural State Flag parameter. It is possible to obtain such special data as the position of the joystick, the position and status of hydraulic tools, the status of the grain tank and more. Also, using BLE sensors and beacons, you can get additional parameters that are not provided by standard sensors. This can be raising or lowering of the dump truck body and cab, temperature and humidity in the chamber. You can also track expensive equipment using BLE beacons.

What you need for a solution?

  • The SIM card in order to get data to your server
  • FOTA WEB to remotely send the configuration to the device.


Installation

thumb750x600px


When installing FMB140 in a vehicle, follow the mounting recommendations. When connecting to the CAN bus, you must use the diagrams provided by our technical support engineers. The diagrams indicate in detail and clearly the connection points in the vehicle wiring and the required program number. It is also possible to obtain data from the vehicle CAN bus by performing an auto scan procedure. FMB140 has the function of working with wireless BLE sensors, supports connection of temperature sensors and iButton reader via 1-wire.


thumb500x600px

The installation of BLE sensors and beacons is quite simple, you need to install the sensor in a suitable place using screws or double-sided tape and install the required configuration in the tracker and sensor. This gives a huge advantage over wired sensors, since there is no need to pull wires, which means you can seriously save on the services of an electrician!

Configuration

1. Prerequisites:

1.1. Read through start guide

1.2. Understanding of possible Sleep modes.



Parameter ID – Parameter name GPRS settings:


  • 2001 – APN
  • 2002 – APN username (if there are no APN username, empty field should be left)
  • 2003 – APN password (if there are no APN password, empty field should be left)





Server settings:

  • 2004 – Domain
  • 2005 – Port
  • 2006 – Data sending protocol (0 – TCP, 1 – UDP)


After successful GPRS/SERVER settings configuration, FMB140 device will synchronize time and update records to the configured server. Time intervals and default I/O elements can be changed by using Teltonika Configurator or SMS parameters.


Data protocol settings:

  • 113 – Data protocol (0 – Codec8, 1 – Codec8Extended)


Note: To get OEM parameters, you need to use Codec8Extended.


Sleep settings:

  • 102 – Sleep settings (0 – Disable, 1 – Gps sleep, 2 – Deep sleep, 3 – Online Deep sleep, 4 – Ultra sleep)

Note: This scenario will not work with Deep Sleep and Ultra Sleep modes, since they disable the device's GSM module to save power.






CAN Adapter setting:

  • 45002 – The program number that is indicated in the wiring diagram.









  • 45001 – Send data with 0, if ignition is off(0 – Disable, 1 – Enable)








  • 45100 – Vehicle speed, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
  • 45130 – Fuel level in ltr*10 , Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
  • 45140 – Engine RPM, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )




  • 45160 – Fuel level in %, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )










  • 46060 – Agricultural State Flags, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )











Quickstart: From default configuration to AGRICULTURE AND FARMING INDUSTRY solution in one SMS:

"  setparam 2001:APN;2002:APN_user;2003:APN_password;2004:Domain;2005:Port;2006:0;102:3;45002:Program number;45001:0; 45100:1; 45160:1; 45130:1; 45140:1; 46060:1; 113:1"

This SMS will set up your device to report object location to the server and possibility for read Engine RPM, Fuel level in %, Fuel level in ltr*10 and Vehicle speed parameters.

Note: Before SMS text, two space symbols should be inserted if no SMS username or password was set in SMS \ Call settings.

To use BLE sensors, use the configurator in online mode (tracker is connected) or offline (tracker is disabled). When using the configurator in offline mode, you can remotely download the configuration via FOTA WEB.



























Parsing information

1.Prerequisites:

1.1. Open TCP/UDP port

1.2. Read Java parser first start guide

2. Parsing example:

Unparsed received data in hexadecimal stream
00000000000000848E010000017CE9B241900000000000000000000000000000000000000015000700EF0100F00100150500C800004502005100005900000900B5000000B600000042385C0


043000000440000001A090E00680023 0054000000550000000400F10000646600100000000001D400FDFFFF00570000000000010208000000000000000000000100000647


AVL Data Packet Part HEX Code Part
Zero Bytes 00 00 00 00
Data Field Length 00 00 00 84
Codec ID 8E (Codec 8 Extended)
Number of Data 1 (Number of Total Records) 01
Timestamp 00 00 01 7C E9 B2 41 90 (04.11.2021 6:45:46)
Priority 00
Longitude 00 00 00 00
Latitude 00 00 00 00
Altitude 00 00
Angle 00 00
Satellites 00
Speed 00 00
Event IO ID 00 00
N of Total ID 00 21
N1 of One Byte IO 00 07
1’st IO ID 00 EF (AVL ID: 239, Name: Ignition)
1’st IO Value 00
2’nd IO ID 00 F0 (AVL ID: 240, Name: Movement)
2’nd IO Value 00
3’rd IO ID 00 15 (AVL ID: 21, Name: GSM Signal)
3’rd IO Value 05
4'th IO ID 00 C8 (AVL ID: 200, Sleep Mode)
4'th IO Value 00
5'th IO ID 00 45 (AVL ID: 69, GNSS Status)
5'th IO Value 02
6'th IO ID 00 51 (AVL ID: 81, Vehicle Speed)
6'th IO Value 00
7'th IO ID 00 59 (AVL ID: 89, Fuel level)
7'th IO Value 00
N2 of Two Byte IO 00 09
1’st IO ID 00 B5 (AVL ID: 181, GNSS PDOP)
1’st IO Value 00 00
2’nd IO ID 00 B6 (AVL ID: 182, GNSS HDOP)
2’nd IO Value 00 00
3’rd IO ID 00 42 (AVL ID: 66, External Voltage)
3’rd IO Value 38 5C
4'th IO ID 00 43 (AVL ID: 67, Battery Voltage)
4'th IO Value 00 00
5'th IO ID 00 44 (AVL ID: 68, Battery Current)
5'th IO Value 00 00
6'th IO ID 00 1A (AVL ID: 26, BLE Temperature #2)
6'th IO Value 09 0E
7'th IO ID 00 68 (AVL ID: 26, BLE Humidity #2)
7'th IO Value 00 23
8'th IO ID 00 54 (AVL ID: 84, Fuel level)
8'th IO Value 00 00
9'th IO ID 00 55 (AVL ID: 85, Engine RPM)
9'th IO Value 00 00
N4 of Four Byte IO 00 04
1’st IO ID 00 F1 (AVL ID: 241, Active GSM Operator)
1’st IO Value 00 00 64 66
2’nd IO ID 00 10 (AVL ID: 16, Total Odometer)
2’nd IO Value 00 00 00 00
3’rd IO ID 01 D4 (AVL ID: 468, BLE 2 Custom #3)
3’rd IO Value 00 FD FF FF
4'th IO ID 00 57 (AVL ID:87, Total Mileage)
4'th IO Value 00 00 00 00
N8 of Eight Byte IO 00 01
1’st IO ID 02 08 (AVL ID: 520, Agricultural State Flags_P4)
1’st IO Value 00 00 00 00 00 00 00 00
Number of Data 2 (Number of Total Records) 01
CRC-16 00 00 06 47





thumb750x600px

The Agricultural State Flag can be interpreted from this table, which can be found here. Each bit carries useful information that can be obtained.

Demonstration in platform

WIALON: Open WIALON → Open Messages → Select your device → Select the date interval → Select Message (data messages) → Select execute and you will see all the information.