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: 182, Name: GNSS HDOP) |
| 2’nd IO Value | 7 |
| 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 | 44 (AVL ID: 68, Name: Battery Current) |
| 5'th IO Value | 6B |
| N4 of Four Byte IO | 02 |
| 1'st IO ID | (AVL ID: 241, Name: Active GSM Operator) |
| 1’st IO Value | 60 1A |
| 2’nd IO ID | (AVL ID: 16, Name: Total Odometer) |
| 2’nd IO Value | 03 87 53
In platformTAVL: 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.  |
