0
edits
Changes
Created page with " ==Introduction== With the market penetration of telematics companies in the B2C segment being quite limited, this use case is a great platform for Telematics Service Provide..."
==Introduction==
With the market penetration of telematics companies in the B2C segment being quite limited, this use case is a great platform for Telematics Service Providers to reach new target groups such as the owners of private vehicles. Pay As You Drive is a fairly well-known business model, which provides better risk management tools for insurance companies and better service quality and commercial conditions to the drivers willing to install GPS trackers and comply to road rules.
==Solution description==
This solution allows vehicles to be used in Pay As You Drive applications by retrieving the '''total driven distance''', also known as odometer data directly from vehicle's CAN-BUS. Therefore, it is no longer necessary to obtain this value from GPS calculations. The accuracy of GPS calculations is suitable in most of the applications, but it still has some limitations – driving in tunnels and other locations where GPS signal is blocked might affect the overall value of a driven distance. Also, to calculate the total driven distance via GPS, a driver needs to enter the first value manually and synchronize it later. It might become a major administrative task.
One of the most important features needed in Pay As You Drive applications is the ability to analyze a driver’s performance – harsh acceleration, harsh braking and harsh cornering. This can be analyzed with [[FMB003_Features_settings#Over_Speeding|Overspeeding]] and [[Green_Driving_Solution|Green Driving]] scenarios. [[FMB003_Accelerometer_Features_settings#Crash_Detection|Crash detection]] is another helpful scenario for insurance companies. It is a practical solution that collects and analyzes data right before the crash happened and during the crash.
Even more, FMB003 has a unique feature providing a driver with both '''Real Fuel''' and '''Real Odometer''' data. It means you can read an actual odometer data from your vehicle dashboard now and get the correct data online.
==What you need for a solution?==
*'''[https://teltonika-gps.com/product/fmb003/ FMB003]''' to read the real odometer data from the vehicle dashboard via the vehicle’s OBD port.
'''Other devices that work with this solution:''' '''[https://teltonika-gps.com/product/fmp100/ FMP100]'''/ ''It has the advantage of simple installation.''
*'''[[Teltonika_Configurator|Teltonika Configurator]]''' to set up FM device correctly for the solution.
*'''[[FOTA_WEB|FOTA WEB]]''' to remotely send the configuration to the device for cloud-based VIN decoding combined with OEM data requests database.
*'''SIM card''' to access FOTA WEB and send data to the server by accessing the GSM network.
==Installation==
FMB003, our new generation ultra-small, plug and play OBDII tracker with the benefits of very fast and easy installation. Even end-users can install the device themselves. The new housing of FMB003 device is remarkably small which is advantageous in vehicles with limited space for GPS tracker installation.
Installing the OBDII device to the vehicle:
* 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 Location of OBD plug].
* Before connecting the device to the OBDII socket, make sure that ≥3A fuse is present on OBD connector power supply.
[[File:Obd connections.png|none|thumb|397x397px|Figure 1. Most common OMBDII connector locations]]
==Configuration==
==='''1. Prerequisites'''===
* The vehicle must be supported by the FMB003 device. ''How to learn?'' Please contact your Teltonika Sales Manager with the make, model and model year of your vehicle.
* Turn the ignition ON.
* FMB003 must get VIN from the vehicle ([[FMB003_Teltonika_Data_Sending_Parameters_ID#OBD_elements|AVL ID: 256]]). If not? Check the section [[Pay_As_You_Drive#Common_Issues|Common issues]].
* FMB003 must connect to [[FOTA_WEB|FOTA WEB]] to get the OBD configuration for the vehicle. Please make sure [[FOTA_WEB_Getting_Started#Default_FOTA_WEB_configuration_settings:|the device configuration settings for FOTA WEB]] are correct.
* FMB003 must get OBD OEM Total Mileage from the vehicle ([[FMB003_Teltonika_Data_Sending_Parameters_ID#OBD_OEM_elements|AVL ID: 389]]). If not? Check the section [[Pay_As_You_Drive#Common_Issues|Common issues]].
==='''2. Configuring scenario'''===
* Configure the APN in '''GPRS settings'''.
[[File:Gprs settings.png|alt=|left|thumb|259x259px]]
<br />
*<span style="background-color:#91b9d4;">2001</span> – APN
*<span style="background-color:#91d4b9;">2002</span> – APN username (No APN username > leave the field blank)
*<span style="background-color:#b991d4;">2003</span> – APN password (No APN password > leave the field blank)
<br />
* Configure the server in '''GPRS settings'''.
[[File:Server settings.png|alt=|left|thumb|259x259px]]
<br />
*<span style="background-color:#b9d491;">2004</span> – Domain
*<span style="background-color:#d491b9;">2005</span> – Port
*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)
<br />
* Enable Codec 8 Extended in '''System settings'''.
[[File:Codec8ExtendedPositive.png|alt=|left|thumb|259x259px]]
<br />
*<span style="background-color:#91b9d4;">Parameter ID: 113</span> – Codec 8 Extended (0 – Codec 8, 1 – Codec 8 Extended)
AVL parameters greater than 255 (HEX 0xFF) require “Codec 8 extended” to be sent to the server. See [[FMB003_System_settings#Data_Protocol|here]] for more details.
<br />
* Enable OBD Feature in '''OBD II settings'''.
[[File:OBDsettings.png|alt=|left|thumb|259x259px]]
<br />
*<span style="background-color:#91d4b9;">Parameter ID: 40000</span> – OBD Feature (0 – Disable, 1 – Enable)
<br />
* Select Auto for VIN Source in '''OBD II settings'''.
[[File:VINsettings.png|alt=|left|thumb|259x259px]]
<br />
*<span style="background-color:#b9d491;">Parameter ID: 40005</span> – OBD Feature (0 – Auto, 1 – Manual)
<br />
* Enable (i.e. set a Priority for) OEM Total Mileage in '''OBD II settings'''.
[[File:OEMTotalMileage.png|alt=|left|thumb|259x259px]]
<br />
*<span style="background-color:#d491b9;">Parameter ID: 40430</span> – OBD Feature (Priorities: 0 – None, 1 – Low, 2 - High, 3 - Panic)
<br />
'''Quickstart:''' From default configuration to Pay As You Drive solution in one SMS:
''<SMS Login> <SMS Password>'' '''setparam 113:1;40000:1;40005:0;40430:1'''
Please review other features to improve this use case:
* [[FMB003_Features_settings#Over_Speeding|Overspeeding]]
* [[FMB003_Features_settings#Eco.2FGreen_Driving|Eco/Green Driving]]
* [[FMB003_Accelerometer_Features_settings#Crash_Detection|Crash detection]] for the corresponding configuration settings.
'''Configuration changes also can be made via [https://teltonika-gps.com/product/fota/ FOTA WEB]''' ''or to some extent via '''FMBT Mobile application'''''.
==='''3. FMBT Mobile application'''===
You can view the current status of the parameters ''including AVL ID: 389 - OBD OEM Total Mileage''.
The application can also configure:
[[File:Fmbt 3.png|link=Special:Redirect/file/Fmbt_3.png|alt=|left|thumb|259x259px]]
*APN (APN, APN username, APN password)
*Server (domain, port, data sending protocol)
<br/><br/><br/><br/><br/><br/><br/>
==='''4. Teltonika Data Sending Parameters'''===
Teltonika Data Sending Parameter for OBD OEM Total Mileage is AVL ID 389 (Unit: km). You can get the current value from the vehicle with '''Ignition ON''':
''<SMS Login> <SMS Password>'' '''[[FMB_readio|readio]] 389'''
==Parsing information==
==='''1.Prerequisites'''===
==== 1.1. Open [https://wiki.teltonika-gps.com/view/Opening_TCP/UDP_port TCP/UDP port]====
==== 1.2. Read Java parser [https://wiki.teltonika-gps.com/view/Java_Parser_First_Start_Guide first start guide]====
=== '''2. 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;" | 00000000000000548E010000017CA68CAE50010F0E4D4D209A8D40005C00000B00000000000B000500EF0100F0010015
0300C8000025000004004238DD0043102F00440028002403400002<span style="background:#0b9768">0185<span style="background:#d4f991">0003DC0C</span></span>0186000000C8000000000100003C34
|}
{| 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 54
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |8E (Codec 8 Extended)
|-
| 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 7C A6 8C AE 50
|-
| 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 4D 4D
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |20 9A 8D 40
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 5C
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |0B
|-
| 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;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 0B
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 05
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 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;" |00 F0 (AVL ID: 240, Name: Movement)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |00 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;" |00 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;" |00 25 (AVL ID: 37, Name: Vehicle Speed)
|-
| style="vertical-align: middle; text-align: center;" |5’th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 04
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 42 (AVL ID: 66, Name: External Voltage)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |38 DD
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 43 (AVL ID: 67, Name: Battery Voltage)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |10 2F
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |00 44 (AVL ID: 68, Name: Battery Current)
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |00 28
|-
| style="vertical-align: middle; text-align: center;" |4’th IO ID
| style="vertical-align: middle; text-align: center;" |00 24 (AVL ID: 36, Name: Engine RPM)
|-
| style="vertical-align: middle; text-align: center;" |4’th IO Value
| style="vertical-align: middle; text-align: center;" |03 40
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 02
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">01 85</span> (AVL ID: 389, Name: OBD OEM Total Mileage)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00 03 DC 0C</span>
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |01 86 (AVL ID: 134, Name: Trip Distance)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00 00 00 C8
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |NX of X Byte IO
| style="vertical-align: middle; text-align: center;" |00 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 3C 34
|}
Server response: 00000001
Please see '''[[Codec#Codec_8_Extended|Codec 8 Extended]]''' for more information.
==Demonstration on Platform==
For [[Teltonika_TAVL|TAVL]] Users:
* '''TAVL''' > Select Client
* '''Objects''' > Press "Filter" > Find Object
* '''Track''' > Choose dates > Press "Advanced" > Press "Show"
[[File:TAVL-Deividas.png|alt=|left|thumb|1250x1250px]]
==Common issues==
{| class="wikitable"
|+
!Issue
!How to check?
!What to do next?
|-
|The device is not configured to send OBDII parameters.
|Check the section [https://wiki.teltonika-gps.com/wikibase/index.php?title=EnginPayAsyouDriveCase&action=submit#Configuration Configuring scenario].
|
* Make any necessary corrections in the configuration.
|-
|The vehicle's ignition is not turned ON.
|Send the following SMS/GPRS command to the device:
''<SMS Login> <SMS Password>'' '''readio 239''' ''(Values - “0”: Ignition OFF, “1”: Ignition ON)''
|
* Turn the ignition ON.
|-
|The vehicle does not support the OBDII protocol.
|Send the following SMS/GPRS command to the device with '''Ignition ON''':
''<SMS Login> <SMS Password>'' '''[[FMB_obdinfo|obdinfo]]'''
|
* The device response of the p1-4 protocols consisting of data indicates that data is received.
''Prot:6,VIN:WVWZZZAUZFW125650,TM:15,CNT:12,ST:DATA REQUESTING,<span style="background:#d491b9">P1:0xBFBFB993,P2:0x8007E019,P3:0xFED00000,P4:0x0</span>,MIL:0,DTC:0,ID3,Hdr:7E8,Phy:0''
* The device response of the p1-4 protocols consisting of zeros indicates that no data is received.
''Prot:0,VIN:N/A,TM:10,CNT:0,ST:OFF,<span style="background:#d491b9">P1:0x0,P2:0x0,P3:0x0,P4:0x0</span>,MIL:0,DTC:0,ID0,Hdr:0,Phy:0''
|-
|[[FMB003_Teltonika_Data_Sending_Parameters_ID#OBD_elements|VIN]] is not received.
|Send the following SMS/GPRS command to the device with '''Ignition ON''':
''<SMS Login> <SMS Password>'' '''[[FMB_obdinfo|obdinfo]]'''
|
* The device response with VIN:<VIN> indicates that VIN is received.
''Prot:6,<span style="background:#d4f991">VIN:WVWZZZAUZFW125650</span>,TM:15,CNT:12,ST:DATA REQUESTING,P1:0xBFBFB993,P2:0x8007E019,P3:0xFED00000,P4:0x0,MIL:0,DTC:0,ID3,Hdr:7E8,Phy:0''
* The device response with VIN:N/A indicates that no VIN is received.
''Prot:0,<span style="background:#d4f991">VIN:N/A</span>,TM:10,CNT:0,ST:OFF,P1:0x0,P2:0x0,P3:0x0,P4:0x0,MIL:0,DTC:0,ID0,Hdr:0,Phy:0''
* Configure VIN manually if vehicle does not return VIN.
[[File:OBDVINsettingsmanual.png|alt=|left|thumb|259x259px]]
''<SMS Login> <SMS Password>'' '''setparam 40005:1'''
''<SMS Login> <SMS Password>'' '''setparam 40003:<VIN>'''
|-
|[[FMB003_Teltonika_Data_Sending_Parameters_ID#OBD_OEM_elements|OBD OEM Total Mileage]] is not received.
|
'''Turn the ignition ON.'''
*'''Configurator:''' Check if OEM Total Mileage (Parameter ID: 40430) is received in I/O settings.
*'''Server:''' Check if OBD OEM Total Mileage (AVL ID: 389) is coming to your server.
*'''SMS/GPRS command:''' Check with '''readio''' SMS/GPRS command. ''SMS command structure: <SMS Login> <SMS Password> readio 389''
|
*Contact your Teltonika Sales Manager with the make, model and model year of your vehicle.
*Contact Teltonika support via VIP HelpDesk with the make, model and model year of your vehicle. Also share device response to '''obdinfo''' SMS/GPRS command with ignition ON.
|}
[[Category: Usage scenarios]]
