Difference between revisions of "GPS Electronic Logbook"

From Wiki Knowledge Base | Teltonika GPS
Line 112: Line 112:
  
 
=== Prerequisites ===
 
=== Prerequisites ===
 +
First of all, in order to parse packets with GPS electronic logbook records it is mandatory to open TCP or UDP port. Instructions can be found [[Opening TCP/UDP port|'''here''']].
 +
 +
After establishing TCP or UDP port, packets can be parsed automatically. In order to learn how it is done, please visit '''[[Java Parser First Start Guide]]'''.
  
 
=== Parsing example ===
 
=== Parsing example ===
−
 
+
{| class="nd-othertables_2" style="width:100%;"
 +
! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
 +
|-
 +
| style="vertical-align: middle; text-align: center;" | 000000000000004608010000017501DAF828010F0E4792209AC4FB00C200D70C0000<span style="background:#0b9768">F9</span>0D06EF01F00
 +
01503C8004501<span style="background:#0b9768">F900</span>B50005B6000342334D43000044000002F10000601A100000000000010000732E
 +
|}
 +
{| class="nd-othertables_2" style="width:100%;"
 +
|-
 +
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
 +
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Zero Bytes
 +
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Data Field Length
 +
| style="vertical-align: middle; text-align: center;" |00 00 00 D6
 +
|-
 +
| 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;" |Number of Data 1 (Number of Total Records)
 +
| style="vertical-align: middle; text-align: center;" |01
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Timestamp
 +
| style="vertical-align: middle; text-align: center;" |00 00 01 75 01 DA F8 28 (Wed Oct 07 06:58:49 UTC 2020)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Priority
 +
| style="vertical-align: middle; text-align: center;" |01
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Longitude
 +
| style="vertical-align: middle; text-align: center;" |0F 0E 47 92
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Latitude
 +
| style="vertical-align: middle; text-align: center;" |20 9A C4 FB
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Altitude
 +
| style="vertical-align: middle; text-align: center;" |00 C2
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Angle
 +
| style="vertical-align: middle; text-align: center;" |00 D7
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Satellites
 +
| style="vertical-align: middle; text-align: center;" |0C
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Speed
 +
| style="vertical-align: middle; text-align: center;" |00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Event IO ID
 +
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">F9 (AVL ID: 249, Name: Jamming)</span>
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |N of Total ID
 +
| style="vertical-align: middle; text-align: center;" |00 0D
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
 +
| style="vertical-align: middle; text-align: center;" |06
 +
|-
 +
| 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;" |1’st IO Value
 +
| style="vertical-align: middle; text-align: center;" |01
 +
|-
 +
| 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;" |2’nd IO Value
 +
| style="vertical-align: middle; text-align: center;" |00
 +
|-
 +
| 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;" |3’rd IO Value
 +
| style="vertical-align: middle; text-align: center;" |03
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |C8 (AVL ID: 200, Name: Sleep Mode)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |45 (AVL ID: 69, Name: GNSS Status)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |01
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |6'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">F9 (AVL ID: 249, Name: Jamming) </span>
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |6'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 (0 – jamming stop, 1 – jamming start)</span>
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |N1 of Two Byte IO
 +
| style="vertical-align: middle; text-align: center;" |05
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |1’st IO ID
 +
| style="vertical-align: middle; text-align: center;" |B5 (AVL ID: 181, Name: GNSS PDOP)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |1’st IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 05
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
 +
| style="vertical-align: middle; text-align: center;" |B6 (AVL ID: 182, Name: GNSS HDOP)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 03
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
 +
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, Name: External Voltage)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
 +
| style="vertical-align: middle; text-align: center;" |33 4D
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |43 (AVL ID: 67, Name: Battery Voltage)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |44 (AVL ID: 68, Name: Battery Current)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |N4 of Four Bytes IO
 +
| style="vertical-align: middle; text-align: center;" |02
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |1’st IO ID
 +
| style="vertical-align: middle; text-align: center;" |F1 (AVL ID: 241, Name: Active GSM Operator)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |1’st IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00 60 1A
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
 +
| style="vertical-align: middle; text-align: center;" |10 (AVL ID: 16, Name: Total Odometer)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |N8 of Eight Bytes IO
 +
| style="vertical-align: middle; text-align: center;" |00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
 +
| style="vertical-align: middle; text-align: center;" |01
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |CRC-16
 +
| style="vertical-align: middle; text-align: center;" |00 00 73 2E
 +
|}
 
== In platform ==
 
== In platform ==

Revision as of 16:43, 15 January 2021

Main Page > General Information > Usage scenarios > GPS Electronic Logbook

Project description

It is a good practice for the companies all over the world a vehicle log to be kept for each automobile so that a fleet manager can keep tracking the operational cost of any particular car and/or the entire fleet. Although, manually handled paper reports leave a lot of space for failure. Starting of basic human errors, paperwork overload, lack of drivers accountability, communication and coordination issues, chaotic routing, excessive idling and up to no clear differentiation between business and personal vehicle use. These challenges will inevitably take an effect on the fleet operational cost, company cash flow, competitive advantage and reputation. All these obstacles can not be ignored and should be taken into account. And that is where Teltonika GPS electronic logbook solution comes into the play.

Teltonika GPS electronic logbook offers two operational modes: Private Mode and Business Mode. In the latter mode - location and the date of departure, driver's ID, mileage at the beginning and the end of the journey (distance travelled in total), green driving parameters, purpose of the trip will be tracked automatically. If Private Mode is chosen by the driver, the logbook will be turned off and no events will be registered.

We are glad that You decided to test our "GPS electronic logbook" solution.

Here You will find how to prepare and to test this solution.

What will You need for the solution?

  • Teltonika FM device which is compatible with this use case. Recommended products: FMB001, FMC001, FMM001, FM3001, FMU126, FMB002, FMB010, FMB003 or FMB020.
  • The SIM card in order to receive data to Your server.
  • Teltonika Configurator to set up FM device correctly for the solution.
  • FOTA WEB to remotely send the configuration to the device.
  • BTAPP / Driver application for Private Mode or Business Mode selection.

Installation

Most of recommended products are "Plug and Play" devices. It means that devices are directly plugged into vehicles OBDII socket and after configuration is complete - devices are set. Although, if plugged OBDII device is too hard to reach and vehicle parts are interfering with GPS signal or vehicle parts need to be removed/opened to access OBDII socket and afterwards parts no longer fit or close - Teltonika offers OBDII extension cable. [1]

Keep in mind, that FMU126 device is not "Plug and Play" type and requires more advanced installation. [2] Also, particular FM device is specially built for Thailand region.

Apart from device configuration (more later) and installation into vehicle, GPS electronic logbook doesn't require additional hands on work.

Configuration

Prerequisites

Before configuring GPS electronic logbook solution it is mandatory to set up GPRS settings for a device. Quick first start guide can be found here.

Configuring GPS electronic logbook

After familiarizing with devices first start guide and device's GPRS settings are set - configuration for GPS electronic logbook can be done.

Trip settings.png

Parameter ID - Parameter name

Trip settings:

  • 11800 - Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic).
  • 11801 - Eventual settings (0 - Disable, 1 - Enable), if disabled - trip settings will come with periodical data.
  • 11802 - Mode (0 - Continuous, 1 Between Records). If Between Records option is selected distance will be counted until any record is made. Then odometer will be reset to zero and start counting until next record is made.
  • 11803 - Start Speed (km/h).
  • 11804 - Ignition OFF timeout (s).
  • 7031 - ID of SMS recipient.
  • 8031 - SMS Text.


  • 700 - Eco Score Allowed Events.
  • 11806 - Odometer Calculation Source (0 - GNSS, 1 - OBD).
  • 11807 - current Odometer Value (km). Odometer data will be counted from provided value.
Green - Eco driving.png


Eco/Green Driving settings:

  • 11000 - Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic).
  • 11004 - Maximum Acceleration (m/s2).
  • 11005 - Maximum Braking (m/s2)
  • 11006 - Maximum Cornering (m/s2)


  • 11007 - Source (0 - GPS, 1 - Accelerometer). Green driving scenario according to selected data source.
  • 11019 - Advanced Eco Driving (0 - Disable, 1 - Enable). If enabled, Eco Driving Average (ID.: 11011) and / or Eco Driving Maximum (ID.: 11015) settings can be changed.
  • 11008 - Eco/Green Driving Duration (0 - Disable, 1 - Enable).
  • 7034 - ID of SMS recipient.
  • 8034 - SMS Text.
    Note: Maximum acceleration, braking and cornering values should be set according to vehicle type, power, weight and etc. Best values can be approached by practical testing.
Idlingg.png


Excessive Idling settings:

  • 11200 - Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic).
  • 11203 - Eventual settings (0 - Disable, 1 - Enable), if disabled - excessive idling data will come with periodical data.
  • 11205 - Time To Stopped (s). Represents how long vehicle should not move with engine ON.
  • 11206 - To To Moving (s). Represents how long vehicle should be moving with engine ON, to exit idle state.
  • 7033 - ID of SMS recipient.
  • 8033 - SMS Text.


Quick start: From default configuration to GPS electronic logbook records in one SMS:

" setparam 11800:1;11801:0;11806:1;11000:2;11007:1;11200:2"

This SMS will set up Your device to send Trip, Eco/Green driving and Excessive idling data to Your previously provided server.

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

BTAPP Mobile application

Business private.png

After making configuration for Your device, it is time to download BTAPP. Keep in mind, app and device connection is established via Blue-tooth. Devices by default come with Blue-tooth enabled and visible. After pairing to device - You can change the trip type of Your trips by performing a long press on the icon and confirming the change.





Parsing GPS electronic logbook records

Prerequisites

First of all, in order to parse packets with GPS electronic logbook records it is mandatory to open TCP or UDP port. Instructions can be found here.

After establishing TCP or UDP port, packets can be parsed automatically. In order to learn how it is done, please visit Java Parser First Start Guide.

Parsing example

Unparsed received data in hexadecimal stream
000000000000004608010000017501DAF828010F0E4792209AC4FB00C200D70C0000F90D06EF01F00

01503C8004501F900B50005B6000342334D43000044000002F10000601A100000000000010000732E

AVL Data Packet Part HEX Code Part
Zero Bytes 00 00 00 00
Data Field Length 00 00 00 D6
Codec ID 08 (Codec 8)
Number of Data 1 (Number of Total Records) 01
Timestamp 00 00 01 75 01 DA F8 28 (Wed Oct 07 06:58:49 UTC 2020)
Priority 01
Longitude 0F 0E 47 92
Latitude 20 9A C4 FB
Altitude 00 C2
Angle 00 D7
Satellites 0C
Speed 00 00
Event IO ID F9 (AVL ID: 249, Name: Jamming)
N of Total ID 00 0D
N1 of One Byte IO 06
1’st IO ID EF (AVL ID: 239, Name: Ignition)
1’st IO Value 01
2’nd IO ID F0 (AVL ID: 240, Name: Movement)
2’nd IO Value 00
3’rd IO ID 15 (AVL ID: 21, Name: GSM Signal)
3’rd IO Value 03
4'th IO ID C8 (AVL ID: 200, Name: Sleep Mode)
4'th IO Value 00
5'th IO ID 45 (AVL ID: 69, Name: GNSS Status)
5'th IO Value 01
6'th IO ID F9 (AVL ID: 249, Name: Jamming)
6'th IO Value 00 (0 – jamming stop, 1 – jamming start)
N1 of Two Byte IO 05
1’st IO ID B5 (AVL ID: 181, Name: GNSS PDOP)
1’st IO Value 00 05
2’nd IO ID B6 (AVL ID: 182, Name: GNSS HDOP)
2’nd IO Value 00 03
3’rd IO ID 42 (AVL ID: 66, Name: External Voltage)
3’rd IO Value 33 4D
4'th IO ID 43 (AVL ID: 67, Name: Battery Voltage)
4'th IO Value 00 00
5'th IO ID 44 (AVL ID: 68, Name: Battery Current)
5'th IO Value 00 00
N4 of Four Bytes IO 02
1’st IO ID F1 (AVL ID: 241, Name: Active GSM Operator)
1’st IO Value 00 00 60 1A
2’nd IO ID 10 (AVL ID: 16, Name: Total Odometer)
2’nd IO Value 00 00 00 00
N8 of Eight Bytes IO 00
Number of Data 2 (Number of Total Records) 01
CRC-16 00 00 73 2E

In platform

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=GPS_Electronic_Logbook&oldid=61959"