Difference between revisions of "FLEET MAINTENANCE SCHEDULES (DELIVERY)"

Revision as of 17:29, 25 January 2021

Main Page > General Information > Usage scenarios > FLEET MAINTENANCE SCHEDULES (DELIVERY)

Project description

Delivery service is a business where efficiency is everything. Customers expect their goods to be delivered in time and meeting these expectations is a must if the company wants to make a solid profit. Anything what causes delays should be minimized or eliminated. Facilitated by GPS devices, timely vehicle maintenance can greatly reduce the number of irregularities and, thus, help the business grow.

We glad that you decide to test our “FLEET MAINTENANCE SCHEDULES (DELIVERY)” solution.

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

What you need for a solution?

Teltonika FM device which is compatible with this use case and have OBD connection.
The SIM card in order to get data to your server.
FOTA WEB to remotely send the configuration to the device.
Teltonika Configurator to set up FM device correctly for the solution.

Installation

First step you need to finde in your car OBD connector to do this visit Location of OBD plug

Second step it just connect your FMB device to OBD connector.

Configuration

1. Prerequisites:

1.1. Read through First start guide

1.2. Understanding of possible Sleep modes.

2. Configuring FLEET MAINTENANCE SCHEDULES:

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.
11806 - Odometer Calculation Source (0 - GNSS, 1 - OBD).
11807 - current Odometer Value (km). Odometer data will be counted from provided value.

Ignition Source

101 - Eventual settings (1 - DIN 1, 2 - Accelerometer, 4 - Power Voltage, 8 - Engine RPM).

104 - Hight Voltage ( MIN - 0, MAX - 30000).
105 - Low Voltage ( MIN - 0, MAX - 29999).

Quick start: From default configuration to FLEET MAINTENANCE SCHEDULES in one SMS:

"  setparam 11800:1;11801:0;101:4;104:30000;105:12000"

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

After configuration device start parameters now we go to configure OBD II elements.

In the photo below (this is example case) you see where you must go to configurate main parameter that you need to have from device.

In OBD II window you see lot of I/O elements in this window you will configure device in your needed scenario.

Parsing FLEET MAINTENANCE SCHEDULES records

1.Prerequisites:

1.1. Open TCP/UDP port

1.2. Go to Java parser first start guide

2.Parsing example:

Unparsed received data in hexadecimal stream
00000000000004d608130000017738b113a8000efcea74209c63c200b60 096050010000c05ef01f0011505c800450105b50008b600074230fc430f3d44006b02f10000601a1000038753000 000017738b11790000efceb6e209c63d300b5004905000e000c05ef01f0011505c800450105b50008b600074230 ff430f3d44006b02f10000601a1000038753000000017738b11f60000efcec79209c63b200b50067050008000c05ef01f0011505

AVL Data Packet Part	HEX Code Part
Zero Bytes	00 00 00 00
Data Field Length	00 00 04 d6
Codec ID	08 (Codec 8)
Number of Data 1 (Number of Total Records)	13
Timestamp	00 00 01 77 38 b1 13 a8 (Mon Jan 25 08:37:46 UTC 2021)
Priority	00
Longitude	00 01 77 38
Latitude	b1 13 a8 00
Altitude	0e fc
Angle	ea 74
Satellites	20
Speed	9c 63
N of Total ID	12
N1 of One Byte IO	09
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	01
3’rd IO ID	15 (AVL ID: 21, Name: GSM Signal)
3’rd IO Value	05
4'th IO ID	50 (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
N2 of Two Byte IO	5
1’st IO ID	B5 (AVL ID: 181, Name: GNSS PDOP)
1’st IO Value	8
2’nd IO ID	B6 (AVL ID: 32, Name: Coolant Temperature)
2’nd IO Value	61
3’rd IO ID	42 (AVL ID: 66, Name: External Voltage)
3’rd IO Value	30 FC
4'th IO ID	43 (AVL ID: 67,Name: Battery Voltage)
4'th IO Value	0F 3D
5'th IO ID	24 (AVL ID: 36, Name: Engine RPM)
5'th IO Value	06 A2
N4 of Four Byte IO	02
1'st IO ID	(AVL ID: 41, Name: Throttle Position)
1’st IO Value	5E
2’nd IO ID	(AVL ID: 16, Name: Total Odometer)
2’nd IO Value	03 87 53

In platform

TAVL: Open TAVL → select client → select Street Map → select device → choose the date from which to which to show the records → push advanced → push show button and then you will see in left down corner all information.

@@ Line 1: / Line 1: @@
-==Solution description==
+==Project description==
 Delivery service is a business where efficiency is everything. Customers expect their goods to be delivered in time and meeting these expectations is a must if the company wants to make a solid profit. Anything what causes delays should be minimized or eliminated. Facilitated by GPS devices, timely vehicle maintenance can greatly reduce the number of irregularities and, thus, help the business grow.
-We glad that you decide to test our “Fleet Maintenance Schedules (Delivery)” solution.
+We glad that you decide to test our “FLEET MAINTENANCE SCHEDULES (DELIVERY)” solution.
 Here you will find how to prepare and to test this solution.
@@ Line 9: / Line 9: @@
 ==What you need for a solution?==
-*Teltonika FM device which is compatible with this use case and have OBD connection and can read OBDII data. Recommended devices: [https://wiki.teltonika-gps.com/view/FMB001 FMB001], [https://wiki.teltonika-gps.com/view/FMC001 FMC001], [https://wiki.teltonika-gps.com/view/FMM001 FMM001], [https://wiki.teltonika-gps.com/view/FMB003 FMB003], [https://wiki.teltonika-gps.com/view/FMB002 FMB002]. Also, it is possible to use [[FMP100]] via Bluetooth® function but it requires Bluetooth® OBDII dongle.
+*Teltonika FM device which is compatible with this use case and have OBD connection.
 *The SIM card in order to get data to your server.
-*[https://wiki.teltonika-gps.com/view/FOTA FOTA]  to remotely send the configuration to the device.
+*FOTA WEB to remotely send the configuration to the device.<br />
 * [[Teltonika Configurator]] to set up FM device correctly for the solution.
 ==Installation==
+First step you need to finde in your car OBD connector to do this visit [https://www.outilsobdfacile.com/location-plug-connector-obd.php#:~:text=Since%20the%20implementation%20of%20the,not%20be%20easy%20to%20locate. Location of OBD plug]
-Connecting the device to the vehicle:
+Second step it just connect your FMB device to OBD connector.
-* Before connecting the device to the OBDII socket, make sure that ≥3A fuse is present on OBD connector power supply.
-* Find OBDII connector in your vehicle ( Figure 1.) if you need more accurate location please visit [https://www.outilsobdfacile.com/location-plug-connector-obd.php#:~:text=Since%20the%20implementation%20of%20the,not%20be%20easy%20to%20locate. Location of OBD plug].
-[[File:Obd connections.png|none|thumb|397x397px|Figure 1. Most common OMBDII connector locations]]
 ==Configuration==
@@ Line 31: / Line 26: @@
 ====1.1. Read through [https://wiki.teltonika-gps.com/view/FMB001_First_Start First start guide]====
 ====1.2. Understanding of possible [https://wiki.teltonika-gps.com/view/FMB001_System_settings#Sleep_Mode Sleep modes].====
-<br>
+<br />
-==='''2. Configuring Fleet Maintenance Schedules:'''===
+==='''2. Configuring FLEET MAINTENANCE SCHEDULES:'''===
-[[File:Trip settings.png|left|thumb|476x476px]]
+[[File:Trip settings.png|left|thumb|439x439px]]
 ''Parameter ID'' - ''Parameter name''
-Trip settings:
+'''Trip settings''':
 *<span style="background-color:#91b9d4;">11800</span> - Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic).
+<br>
 *<span style="background-color:#91d4b9;">11801</span> - Eventual settings (0 - Disable, 1 - Enable), if disabled - trip settings will come with periodical data.
+<br>
-* 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. When it is set to Continuous, Trip distance is going to be counted continuously (from Trip start to Trip end) and written to I/O Trip Odometer value field. When Trip is over and the next Trip begins, Trip Odometer value is reset to zero.
+* 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). This parameter is needed if you want to start the trip on specific speed, If start speed selected 0 the trip only will work then ignition is on.
+* 11803 - Start Speed (km/h).
-* 11804 - Ignition OFF timeout (s) is the timeout value to detect Trip end once the Ignition (configured ignition source) is off.
+* 11804 - Ignition OFF timeout (s).
 * 7031 - ID of SMS recipient.
 * 8031 - SMS Text.
+* 700 - Eco Score Allowed Events.
+<br>
+*<span style="background-color:#b991d4;">11806</span> - Odometer Calculation Source (0 - GNSS, 1 - OBD).
+* 11807 - current Odometer Value (km). Odometer data will be counted from provided value.
 *<span style="background-color:#b991d4;">11806</span> - Odometer Calculation Source (0 - GNSS, 1 - OBD).
 * 11807 - current Odometer Value (km). Odometer data will be counted from provided value.
+[[File:Deliveri case 2.jpg|left|frameless]]
+'''Ignition Source'''
-Ignition source will be used to determine ignition of vehicle.
+*<span style="background-color:#91b9d3;">101</span> - Eventual settings (1 - DIN 1, 2 - Accelerometer,  4 - Power Voltage, 8 - Engine RPM).
+<br>
+*<span style="background-color:#91d4b8;">104</span> - Hight Voltage ( MIN - 0, MAX - 30000).
+*<span style="background-color:#91d4b8;">105</span> - Low Voltage ( MIN - 0, MAX - 29999).
-Possible ignition sources:
+<br>
+'''Quick start:''' From default configuration to [[FMB001_SMS/GPRS_Commands|FLEET MAINTENANCE SCHEDULES in one SMS]]:
-* '''DIN 1''' (Digital Input 1) - if ''DIN1'' is 1 - ignition is ON; if ''DIN1'' value is 0 - ignition is OFF;
-* '''Power Voltage''' - if voltage is between High Voltage Lever and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON; if voltage is higher than High Voltage Lever or lower than Low Voltage Level - ignition is OFF.
-* '''Engine RPM''' - if ''RPM'' from OBD II or CAN is higher than 0 - ignition is ON; if ''RPM'' from OBD II or CAN is equal to 0 - ignition is OFF;
-* '''Accelerometer''' - if movement sensor detects movement - ignition is ON; if movement is not detected - ignition is OFF;
-More than one ignition source can be selected at the same moment. When there are 2 or more sources selected, at least one condition has to be met to change Ignition status.
-'''Example:''' DIN1 and Accelerometer are selected as the Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. Users can select movement start and movement stop delay time - those parameters are used when the accelerometer is selected as an ignition source. Ignition status is used in power management and the following functionalities: [[FMB001 Features settings#Eco.2FGreen%20Driving|Eco/Green Driving]], [[FMB001 Accelerometer Features settings#Excessive%20Idling|Excessive Idling]], Fuel Consumption, [[FMB001 Features settings#Over%20Speeding|Over Speeding]], [[FMB001 Accelerometer Features settings#Towing%20Detection|Towing Detection]] and [[FMB001 Trip/Odometer settings|Trip]].[[File:Screenshot 2021-03-07 162223.png|left|thumb|230x230px]]
-Ignition Source:
-* <span style="background-color:#91b9d3;">101</span> - Eventual settings (1 - DIN 1, 2 - Accelerometer,  4 - Power Voltage, 8 - Engine RPM).
-*<span style="background-color:#91d4b8;">104</span> - Hight Voltage ( MIN - 0, MAX - 30000).
-* <span style="background-color:#91d4b8;">105</span> - Low Voltage ( MIN - 0, MAX - 29999).
-<br><br>'''Quick start:''' From default configuration to Fleet Maintenance Schedules in one [[FMB001 SMS/GPRS Commands|SMS]]:
   "  setparam <span style="background-color:#91b9d4;">11800</span>:1;<span style="background-color:#91d4b9;">11801</span>:0;<span style="background-color:#91b9d3;">101</span>:4;<span style="background-color:#91d4b8;">104</span>:30000;<span style="background-color:#91d4b8;">105</span>:12000"
@@ Line 93: / Line 72: @@
 In the photo below (this is example case) you see where you must go to configurate main parameter that you need to have from device.
-In OBD II window you see a lot of I/O elements to configure the device properly you will need to know which parameters can be read from the vehicle using our OBD trackers. To know what parameters can be read please visit [https://wiki.teltonika-gps.com/view/How_to_check_available_OBDII_data%3F How to check available OBDII data].
+In OBD II window you see lot of I/O elements in this window you will configure device in your needed scenario.
-[[File:Obd22 new.jpg|frameless|719x719px]]
+[[File:Turbo_paaishkinimas.jpg|alt=|frameless|872x872px]]
-==Parsing information==
+==Parsing FLEET MAINTENANCE SCHEDULES records==
 ==='''1.Prerequisites:'''===
@@ Line 109: / Line 88: @@
 ! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
 |-
-| style="vertical-align: middle; text-align: center;" |00000000000004d608130000017738b113a8000efcea74209c63c200b60096050010000c05ef01f0011505c800
+| style="vertical-align: middle; text-align: center;" |00000000000004d608130000017738b113a8000efcea74209c63c200b60
-b50008b600074230f<span style="background:#0b9768">B6</span>c430f3d44006b02f10000601a1000038753000
+096050010000c05ef01f0011505c800450105b50008b600074230fc430f3d44006b02f10000601a1000038753000
-000017738b1<span style="background-color:#91b9d4">24</span>1790000efceb6e
+000017738b11790000efceb6e209c63d300b5004905000e000c05ef01f0011505c800450105b50008b600074230
+ff430f3d44006b02f10000601a1000038753000000017738b11f60000efcec79209c63b200b50067050008000c05ef01f0011505
-c63d05b50008b600074230
-ff430f3d44006b020000601a10000387530000<span style="background-color:#b991d4">29</span>00017738b11f600001f0011505
 |}
 {| class="nd-othertables_2" style="width:100%;"
@@ Line 206: / Line 183: @@
 |-
 | style="vertical-align: middle; text-align: center;" |2’nd IO ID
-| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">B6 (AVL ID: 32, Name: Coolant Temperature)</span>
+| style="vertical-align: middle; text-align: center;" |B6 (AVL ID: 32, Name: Coolant Temperature)
 |-
 | style="vertical-align: middle; text-align: center;" |2’nd IO Value
-| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">61</span>
+| style="vertical-align: middle; text-align: center;" |61
 |-
 | style="vertical-align: middle; text-align: center;" |3’rd IO ID
@@ Line 224: / Line 201: @@
 |-
 | style="vertical-align: middle; text-align: center;" | 5'th IO ID
-| style="vertical-align: middle; text-align: center;" |<span style="background-color:#91b9d4">24 (AVL ID: 36, Name: Engine RPM)</span>
+| style="vertical-align: middle; text-align: center;" |24 (AVL ID: 36, Name: Engine RPM)
 |-
 | style="vertical-align: middle; text-align: center;" |5'th IO Value
-| style="vertical-align: middle; text-align: center;" |<span style="background-color:#91b9d4">06 A2</span>
+| style="vertical-align: middle; text-align: center;" |06 A2
 |-
 | style="vertical-align: middle; text-align: center;" |N4 of Four Byte IO
@@ Line 233: / Line 210: @@
 |-
 | style="vertical-align: middle; text-align: center;" |1'st IO ID
-| style="vertical-align: middle; text-align: center;" |<span style="background-color:#b991d4">29 (AVL ID: 41, Name: Throttle Position)</span>
+| style="vertical-align: middle; text-align: center;" |(AVL ID: 41, Name: Throttle Position)
 |-
 | style="vertical-align: middle; text-align: center;" |1’st IO Value
-| style="vertical-align: middle; text-align: center;" |<span style="background-color:#b991d4">5E</span>
+| style="vertical-align: middle; text-align: center;" | 5E
 |-
 | style="vertical-align: middle; text-align: center;" |2’nd IO ID
@@ Line 243: / Line 220: @@
 | style="vertical-align: middle; text-align: center;" |2’nd IO Value
 | style="vertical-align: middle; text-align: center;" |03 87 53
-|-
-| style="vertical-align: middle; text-align: center;" |CRC-16
-| style="vertical-align: middle; text-align: center;" |00 00 73 2E
-|-
 |}
-==Demonstration in platform==
+==In platform==
 TAVL: Open TAVL → select client → select Street Map → select device → choose the date from which to which to show the records → push advanced → push show button and then you will see in left down corner all information.
 [[File:Tavl delivery.jpg|left|frameless|1137x1137px]]
-WIALON: Open WIALON → open messages → push unit ( select your device) → choose the date from which to which to show the records → select message (data messages) → push execute button and you will see all information.
-[[File:Turbo kosmos.jpg|left|frameless|1138x1138px]]
-[[Category: Usage scenarios]]

Namespaces

Variants

Views

More

Search

Difference between revisions of "FLEET MAINTENANCE SCHEDULES (DELIVERY)"

Revision as of 17:29, 25 January 2021

Contents