Difference between revisions of "How to read ELD data with FM3001?"

From Wiki Knowledge Base | Teltonika GPS
m (Text replacement - "Bluetooth(?!®)" to "Bluetooth®")
(5 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
===Introduction===
 
===Introduction===
−
This document contains information required for developing an application for receiving Electronic Logging Devices data via Bluetooth® from [[FM3001]] series devices.  
+
This document contains information required for developing an application for receiving Electronic Logging Devices data via Bluetooth from FM3001 series devices.  
  
 
Acronyms and terms used in the document:
 
Acronyms and terms used in the document:
−
*BT – Bluetooth®
+
*BT – Bluetooth
 
*ELD – Electronic Logging Devices
 
*ELD – Electronic Logging Devices
  
Line 60: Line 60:
  
 
ELD data packets have JSON structure as shown below: <br>
 
ELD data packets have JSON structure as shown below: <br>
−
<code>
 
 
{ <br>
 
{ <br>
 
"dashboard_mileage": "919483",<br>
 
"dashboard_mileage": "919483",<br>
Line 72: Line 71:
 
“can_data”:”0”.<br>
 
“can_data”:”0”.<br>
 
}<br>
 
}<br>
−
</code>
+
 
 
Braces “{” and “}” marks packet start and end.
 
Braces “{” and “}” marks packet start and end.
  
 
===Parameters definitions===
 
===Parameters definitions===
  
−
{| class="nd-othertables"
+
{| class="wikitable"
 
|+
 
|+
−
! style="width:5%; text-align: center; vertical-align: middle;" | Parameter name
+
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Parameter name
−
! style="width:15%; text-align: center; vertical-align: middle;" | Parameter definition
+
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Parameter definition
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" | ''dashboard_mileage''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | ''dashboard_mileage''
−
| style="text-align: center; vertical-align: middle;" | Units in km, vehicle Total Distance PGN 65217 SPN 917
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | Units in km, vehicle Total Distance PGN 65217 SPN 917
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" | ''obd_rpm''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | ''obd_rpm''
−
| style="text-align: center; vertical-align: middle;" | Vehicle RPM PGN 61444 SPN 19065217 SPN 917
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | Vehicle RPM PGN 61444 SPN 19065217 SPN 917
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" |''obd_vin''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" |''obd_vin''
−
| style="text-align: center; vertical-align: middle;" | Vehicle VIN PGN 65260 SPN 237
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | Vehicle VIN PGN 65260 SPN 237
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" | ''ignition''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | ''ignition''
−
| style="text-align: center; vertical-align: middle;" | Ignition state according to RPM, possible values: 0 – RPM=0 or 1– RPM>0
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | Ignition state according to RPM, possible values: 0 – RPM=0 or 1– RPM>0
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" | ''loc''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | ''loc''
−
| style="text-align: center; vertical-align: middle;" | Current coordinates (longitude and latitude), example value "-10310092,3517679”, actual position is lon=-103.10092, lat=35.17679
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | Current coordinates (longitude and latitude), example value "-10310092,3517679”, actual position is lon=-103.10092, lat=35.17679
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" | ''obd_speed''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | ''obd_speed''
−
| style="text-align: center; vertical-align: middle;" | Units in km/h, wheel based speed PGN 65265 SPN 84
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | Units in km/h, wheel based speed PGN 65265 SPN 84
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" | ''engine_hours''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | ''engine_hours''
−
| style="text-align: center; vertical-align: middle;" | Total Engine hours PGN 65253 SPN 247
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | Total Engine hours PGN 65253 SPN 247
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" | ''time''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | ''time''
−
| style="text-align: center; vertical-align: middle;" | A point in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970. Current timestamp used in FM3001 record saving.
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | A point in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970. Current timestamp used in FM3001 record saving.
 
|-
 
|-
−
| style="text-align: center; vertical-align: middle;" | ''Can_data''
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | ''Can_data''
−
| style="text-align: center; vertical-align: middle;" | Shows whether CAN data is being read. 0 – CAN data is not being read; 1 – CAN data is being read.
+
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; background: white; text-align: center;" | Shows whether CAN data is being read. 0 – CAN data is not being read; 1 – CAN data is being read.
 
|}
 
|}
  

Revision as of 13:01, 27 February 2019

Introduction

This document contains information required for developing an application for receiving Electronic Logging Devices data via Bluetooth from FM3001 series devices.

Acronyms and terms used in the document:

  • BT – Bluetooth
  • ELD – Electronic Logging Devices

Configurable parameters

ELD functionality has 3 additional parameters: ELD data send period and ELD VIN.

Parameter ID Parameter Type Default Value Value Range Value Parameter Name
Min Max
40000 Uint8 1 0 2 0 - Disable

1 - OBD
2 - ELD

OBD Feature
40002 Uint16 10 2 65535 Seconds ELD data send period
40003 String "" 17 17 Charactes ELD VIN


ELD VIN number has to be exactly 17-character long, contain uppercase letters and do not include letters I(i), O(o) and Q(q) (to avoid confusion with numerals 1 and 0).

ELD APP workflow

ELD functionality start to send data periodically via BT right after external BT device has been connected if OBD Feature (parameter ID 40000) is set to ELD (option 2). ELD data sending is paused if Configurator is connected. ELD data is resumed after configurator disconnects. ELD data sending resumes automatically when external BT device reconnects after connection loss.

ELD data packet structure

ELD data packets have JSON structure as shown below:
{
"dashboard_mileage": "919483",
"obd_rpm": "0",
"obd_vin": "4V4NC9EH4FN187825",
"ignition": "0",
"loc": "-10310092,3517679",
"obd_speed": "4",
"engine_hours": "0",
"time": "1518588000",
“can_data”:”0”.
}

Braces “{” and “}” marks packet start and end.

Parameters definitions

Parameter name Parameter definition
dashboard_mileage Units in km, vehicle Total Distance PGN 65217 SPN 917
obd_rpm Vehicle RPM PGN 61444 SPN 19065217 SPN 917
obd_vin Vehicle VIN PGN 65260 SPN 237
ignition Ignition state according to RPM, possible values: 0 – RPM=0 or 1– RPM>0
loc Current coordinates (longitude and latitude), example value "-10310092,3517679”, actual position is lon=-103.10092, lat=35.17679
obd_speed Units in km/h, wheel based speed PGN 65265 SPN 84
engine_hours Total Engine hours PGN 65253 SPN 247
time A point in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970. Current timestamp used in FM3001 record saving.
Can_data Shows whether CAN data is being read. 0 – CAN data is not being read; 1 – CAN data is being read.


Bw nb.png Can_data parameter has been added from firmware version 03.18.00.


Ignition is set depending on RPM value received from TLT chip:

  • ignition is set to 1 if RPM is more than 0 and is set to 0 if RPM is equal to 0.


RPM and Speed are also saved to Engine RPM and Vehicle Speed OBD IO elements.

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=How_to_read_ELD_data_with_FM3001%3F&oldid=28639"