Line 1: |
Line 1: |
| | | |
− | ==Project description== | + | ==Solution 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. | | 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. |
| | | |
Line 9: |
Line 9: |
| ==What you need for a solution?== | | ==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 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. |
| | | |
| *The SIM card in order to get data to your server. | | *The SIM card in order to get data to your server. |
Line 43: |
Line 43: |
| | | |
| * 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. 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. |
− | * 11803 - Start Speed (km/h). If start speed selected 0 the trip only will work then ignition is on. | + | * 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. |
− | * 11804 - Ignition OFF timeout (s). | + | * 11804 - Ignition OFF timeout (s) is the timeout value to detect Trip end once the Ignition (configured ignition source) is off. |
| * 7031 - ID of SMS recipient. | | * 7031 - ID of SMS recipient. |
| | | |
Line 51: |
Line 51: |
| | | |
| | | |
− | * 700 - Eco Score Allowed Events.
| |
| | | |
| | | |
Line 59: |
Line 58: |
| * 11807 - current Odometer Value (km). Odometer data will be counted from provided value. | | * 11807 - current Odometer Value (km). Odometer data will be counted from provided value. |
| | | |
− | [[File:Screenshot 2021-03-07 162223.png|left|thumb|230x230px]]
| |
| | | |
| | | |
| | | |
| | | |
| + | Ignition source will be used to determine ignition of vehicle. |
| + | |
| + | Possible ignition sources: |
| + | |
| + | * '''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]] |
| | | |
| | | |
Line 87: |
Line 97: |
| [[File:Obd22 new.jpg|frameless|719x719px]] | | [[File:Obd22 new.jpg|frameless|719x719px]] |
| | | |
− | ==Parsing Fleet Maintenance Schedule records== | + | ==Parsing information== |
| | | |
| ==='''1.Prerequisites:'''=== | | ==='''1.Prerequisites:'''=== |
Line 239: |
Line 249: |
| |} | | |} |
| | | |
− | ==In platform== | + | ==Demonstration 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. | | 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 246: |
Line 256: |
| 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. | | 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]] | | [[File:Turbo kosmos.jpg|left|frameless|1138x1138px]] |
| + | |
| + | [[Category: Usage scenarios]] |