Difference between revisions of "Private/Business Driving Mode Functionality"
| Line 15: | Line 15: | ||
==Installation== | ==Installation== | ||
| − | The device is easy to install, but keep in mind that although the | + | The device is easy to install, but keep in mind that although the device have high-gain antennas, it is important to mount the device with engraving on top and in metal-free space. For example if you have several 12V sockets in a van, you should not choose one in the back cabin. |
Revision as of 12:11, 29 December 2021
Main Page > General Information > Usage scenarios > Private/Business Driving Mode FunctionalitySolution description
Allowing employees to drive company vehicles for personal reasons is a widespread practice. It is an attractive perk for employees, assisting business owners to hire skilled people and boost its competitiveness. But how to effectively monitor and manage this process, generate reports and avoid a car misuse trouble-free way? To assist businesses with this, Teltonika Telematics has developed a special GPS tracker mode.
This solution will allow your company car to be used by employees for personal purposes without violating the EU General Data Protection Regulations. Moreover, self-employed people can easily convert their own car into a business asset and ensure that the data provided (such as distance traveled) is correct, because using FMP100 is simple as it can be.
What you need for a solution?
- FMP100 device
- Teltonika Configurator to set up FM device correctly for the solution.
- Dedicated firmware version 03.27.07.Rev.461 (please contact you sales manager for the newest version)
- SIM card in order to get data to your server
- FOTA WEB to remotely send the configuration to the device.
Installation
The device is easy to install, but keep in mind that although the device have high-gain antennas, it is important to mount the device with engraving on top and in metal-free space. For example if you have several 12V sockets in a van, you should not choose one in the back cabin.
Configuration
1. Prerequisites:
1.1. Read through First start guide
1.2. Understanding of possible Sleep modes.
2. Configuring Private/Business Mode Scenario
- Configure the APN in GPRS settings.
- 2001 – APN
- 2002 – APN username (No APN username > leave the field blank)
- 2003 – APN password (No APN password > leave the field blank)
- Configure the server in GPRS settings.
- 2004 – Domain
- 2005 – Port
- 2006 – Data sending protocol (0 – TCP, 1 – UDP)
- Enable Codec 8 Extended in System settings.
- Parameter ID: 113 – 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.
- Select priority in Trip \ Odometer.
- Parameter ID: 11800 – Priority settings (0 – Disable, 1 – Low priority, 2 - High priority, 3 - Panic priority)
- Enable Eventual Records in Trip \ Odometer.
- Parameter ID: 11814 – Eventual Records (0 – Disable, 1 – Enable)
- Choose a trigger to change trip mode in Trip \ Odometer.
- Parameter ID: 11811 – Triggers (16 – BTApp, 32 – NBL-1 Button1, 64 – NBL-1 Button2, 128 – FMP100 Button, 255 – Enable All)
- Choose what position should device send when Private mode is enabled in Trip \ Odometer.
- Parameter ID: 11813 – GPS Data Masking (0 – Normal, 1 – Data sent as Zero, 2 – Last good known position)
- Choose whether the distance traveled in private mode should be included in the total odometer in Trip \ Odometer.
- Parameter ID: 11815 – Odometer calculation (0 – Disable, 1 – Enable)
- Choose by what event device should deactivate Private mode in Trip \ Odometer.
- Parameter ID: 11816 – Deactivate by (0 – Disable, 1 – Towing detection, 2 – Unplug detection, 4 – Crash detection, 8 – Autogeofence, 15 – Enable All)
- Choose what trigger type will enable Private mode in Trip \ Odometer.
- Parameter ID: 11849 – Trigger Type (0 – External, 1 – Weekly Schedule)
Quickstart: From default configuration to Pay As You Drive solution in one SMS:
<SMS Login> <SMS Password> setparam 113:1;11800:1;11814:1;11811:128;11813:2;11815:1;11816:4;11849:0
Parsing information
1.Prerequisites
1.1. Open TCP/UDP port
1.2. Read Java parser first start guide
2. Parsing example
| Unparsed received data in hexadecimal stream |
|---|
| AVL Data Packet Part | HEX Code Part |
|---|---|
| Zero Bytes | 00 00 00 00 |
| Data Field Length | |
| Codec ID | 8E (Codec 8 Extended) |
| Number of Data 1 (Number of Total Records) | |
| Timestamp | |
| Priority | |
| Longitude | |
| Latitude | |
| Altitude | |
| Angle | |
| Satellites | |
| Speed | |
| Event IO ID | |
| N of Total ID | |
| N1 of One Byte IO | |
| 1’st IO ID | |
| 1’st IO Value | |
| 2’nd IO ID | |
| 2’nd IO Value | |
| 3’rd IO ID | |
| 3’rd IO Value | |
| 4’th IO ID | |
| 4’th IO Value | |
| 5’th IO ID | |
| 5’th IO Value | |
| N2 of Two Bytes IO | |
| 1’st IO ID | |
| 1’st IO Value | |
| 2’nd IO ID | |
| 2’nd IO Value | |
| 3’rd IO ID | |
| 3’rd IO Value | |
| 4’th IO ID | |
| 4’th IO Value | |
| N4 of Two Bytes IO | |
| 1’st IO ID | |
| 1’st IO Value | |
| 2’nd IO ID | |
| 2’nd IO Value | |
| N8 of Two Bytes IO | |
| NX of X Byte IO | |
| Number of Data 2 (Number of Total Records) | |
| CRC-16 |
Server response: 00000001
Please see Codec 8 Extended for more information.
