Changes

2,690 bytes added , 16:22, 28 December 2023

m

Text replacement - "Bluetooth(?!®)" to "Bluetooth®"

Line 1: Line 1: −

== ~~Project~~ description ==

+

==Solution description==

−

~~It is a good practice for the companies all over the world a vehicle log to be kept for each automobile so that a fleet manager can keep tracking the operational cost~~ of ~~any particular car and/~~or ~~the entire~~ fleet~~. Although~~, ~~manually handled paper reports leave a lot of space~~ for ~~failure~~. ~~Starting of basic human errors, paperwork overload, lack of drivers accountability, communication and coordination issues, chaotic routing, excessive idling and up~~ to ~~no clear differentiation between business and personal vehicle use. These challenges will inevitably take an effect on the fleet operational cost, company cash flow~~, ~~competitive advantage and reputation. All these obstacles~~ can ~~not be ignored~~ and ~~should be taken into account. And that is where Teltonika~~ GPS electronic logbook ~~solution comes into the play~~.

+

If you are one of those drivers or fleet managers who find doing your logbook a tedious and time-consuming process, we have got good news for you. Thanks to Teltonika GPS trackers, you can automate nearly the whole process by using an accurate and reliable GPS electronic logbook.

−

Teltonika GPS electronic logbook offers two operational modes: Private Mode and Business Mode. In the latter mode - location and the date of departure, driver's ID, mileage at the beginning and the end of the journey (distance travelled in total), green driving parameters, purpose of the trip will ~~be tracked automatically. If Private Mode is chosen by the driver, the logbook will be turned off~~ and ~~no events will be registered~~.

+

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

−

~~We are glad that You decided to test our "GPS electronic logbook"~~ solution.

+

==What you need for the solution?==

−

~~Here You will find how~~ to ~~prepare and~~ to ~~test this~~ solution.

+

*

+

*Teltonika FM device which is compatible with this use case. Recommended products are: [[FMB001]], [[FMC001]], [[FMM001]], [[FM3001]], [[FMB002]], [[FMB010]], [[FMB003]], [[FMB020]], [[FMP100]] ( FMP100 is connected via cigarette light socket).

+

*The SIM card in order to receive data to Your server.

+

*[[Teltonika Configurator]] to set up FM device correctly for the solution.

+

*[[FOTA WEB]] to remotely send the configuration to the device.

+

*[[BTAPP Mobile application|BTAPP]] / Driver application for Private Mode or Business Mode selection.

−

== ~~What will You need for the solution?~~ ==

+

==Installation==

+

All of the recommended products are "Plug and Play" devices. It means that devices are directly plugged into vehicles OBDII socket and after configuration is complete - devices are set for use. Although, if plugged OBDII device is too hard to reach and vehicle parts are interfering with GPS signal or vehicle parts need to be removed/opened to access OBDII socket and afterward parts no longer fit or close - Teltonika offers OBDII extension cable. [https://teltonika-gps.com/product/obdii-cable/]

−

*

+

Apart from device configuration (more later) and installation into the vehicle, the GPS electronic logbook doesn't require additional hands-on work.

−

* Teltonika FM device ~~which is compatible with this use case. Recommended products are: FMB001, FMC001~~, ~~FMM001, FM3001, FMU126, FMB002, FMB010, FMB003 or FMB020.~~

−

* The SIM card in order to receive data to Your server.

−

* [[Teltonika Configurator]] to set up FM device correctly for the solution.

−

* [[FOTA WEB]] to remotely send the configuration to the ~~device.~~

−

* [[BTAPP Mobile application|BTAPP]] / Driver application for Private Mode or Business Mode selection.

−

== ~~Installation~~ ==

+

==Configuration==

−

Most of recommended products are "Plug and Play" devices. It means that devices are directly plugged into vehicles OBDII socket and after configuration is complete - devices are set for use. Although, if plugged OBDII device is too hard to reach and vehicle parts are interfering with GPS signal or vehicle parts need to be removed/opened to access OBDII socket and afterwards parts no longer fit or close - Teltonika offers OBDII extension cable. [https://teltonika-gps.com/product/obdii-cable/]

−

~~Keep in mind, that FMU126 device is not "Plug and Play" type and requires more advanced installation~~. ~~[https~~:~~//wiki.teltonika-gps.com/view/FMU126_First_Start] Also, particular FM device is specially built for Thailand region.~~

+

=== '''1. Prerequisites:'''===

−

~~Apart from device configuration (more later) and installation into vehicle, GPS electronic logbook doesn't require additional hands on work~~.

+

====1.1. Read through [https://wiki.teltonika-gps.com/view/FMB001_First_Start First start guide]====

−

== Configuration ==

+

=== '''2. Configuration of GPS electronic logbook scenario:'''===

+

[[File:Gprs settings.png|left|thumb|225x225px]]''Parameter ID'' - ''Parameter name''

+

*2001 – APN

+

*2002 – APN username (if there are no APN username, empty field should be left)

+

*2003 – APN password (if there are no APN password, empty field should be left)

+

[[File:Server settings.png|left|thumb|222x222px]]

+

+

+

+

Server settings:

+

*2004 – Domain

+

*2005 – Port

+

*2006 – Data sending protocol (0 – TCP, 1 – UDP

+

+

+

After successful GPRS/SERVER settings configuration, device will '''synchronize time''' and '''update records''' to '''the configured server'''. Time intervals and default I/O elements can be changed by using [[Teltonika Configurator]] or [[FMB920 Parameter list|SMS parameters]].

−

~~=== Prerequisites ===~~

−

~~Before configuring GPS electronic logbook solution it is mandatory to set up GPRS settings for a device. Quick first start guide can be found [[FMB001 First Start|'''here''']].~~

−

~~=== Configuring GPS electronic logbook ===~~

−

~~After familiarizing with devices first start guide and device's GPRS settings are set - configuration for GPS electronic logbook can be done. Configuration:~~

[[File:Trip settings.png|left|thumb|439x439px]]

−

~~''Parameter ID'' - ''Parameter name''~~

+

+

Configuration of Trip scenario:

−

~~'''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.

+

*11802 - Mode (0 - Continuous, 1 Between Records). If the ''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 the next record is made. If the ''Continues'' option is selected - the distance will continue counting between the trip start and trip stop and the odometer will not reset.

−

* 11803 - Start Speed (km/h).

+

*11803 - Start Speed (km/h). When selecting a value for Start Speed - only after this value (speed) is exceeded, the Trip scenario will be activated. If the Start Speed value is set to 0 (km/h) - the scenario will be activated after the ignition turns on. ''More about ignition settings - below.''

−

* 11804 - Ignition OFF timeout (s).

+

*11804 - Ignition OFF timeout (s).

* 7031 - ID of SMS recipient.

−

* 8031 - SMS Text.

+

*8031 - SMS Text.

−

* 700 - Eco Score Allowed Events.

+

*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.

+

[[File:Screenshot 2021-03-07 162223.png|left|thumb|231x231px]]

+

Configuration of Ignition Source:

+

* 101 - Ignition Settings ( Ignition has 14 different settings, for more information click [[FMB001 Parameter list|'''here''']]).

+

'''Note''': if Ignition Source is selected only to Accelerometer - ignition will be activated when the vehicle starts moving. Engine RPM - cannot be used for every vehicle model. Direct OBDII devices gather information received via the OBDII socket. If the vehicle doesn't provide Engine RPM via mentioned socket - Engine RPM cannot be used as Ignition Source.

+

* 104 - High Voltage ( value range: 13200 - 30000 mV).

+

* 105 - Low Voltage ( value range: 0 - 29999 mV).

[[File:Green - Eco driving.png|left|thumb|348x348px]]

−

~~ ~~

+

−

~~ ~~

+

−

+

Configuration of Eco/Green driving scenario:

−

~~ ~~

−

~~'''~~Eco/Green ~~Driving settings'''~~:

*11000 - Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic).

−

~~ ~~

+

−

* 11004 - Maximum Acceleration (m/s2).

+

*11004 - Maximum Acceleration (m/s2).

−

* 11005 - Maximum Braking (m/s2)

+

*11005 - Maximum Braking (m/s2)

−

* 11006 - Maximum Cornering (m/s2)

+

*11006 - Maximum Cornering (m/s2)

*11007 - Source (0 - GPS, 1 - Accelerometer). Green driving scenario according to selected data source.

−

* 11019 - Advanced Eco Driving (0 - Disable, 1 - Enable). If enabled, Eco Driving Average (ID.: 11011) and / or Eco Driving Maximum (ID.: 11015) settings can be changed.

+

*11019 - Advanced Eco Driving (0 - Disable, 1 - Enable). If enabled, Eco Driving Average (ID.: 11011) and/or Eco Driving Maximum (ID.: 11015) settings can be changed.

* 11008 - Eco/Green Driving Duration (0 - Disable, 1 - Enable).

−

* 7034 - ID of SMS recipient.

+

*7034 - ID of SMS recipient.

−

* 8034 - SMS Text. '''Note''': Maximum acceleration, braking and cornering values should be set according to vehicle type, power, weight and etc. Best values can be approached by practical testing.

+

*8034 - SMS Text.

−

+

+

+

'''Note''': Maximum acceleration, braking, and cornering values should be set according to vehicle type, power, weight and etc. Best values can be approached by practical testing. E.g. testing cornering parameters - take the same turn at a different speed (30km/h, 20 km/h, 40 km/h) and check if Eco/Green Driving event has been triggered for cornering - if it feels as turning on 30km/h is harsh but the event is not triggered - lower Max Cornering values and reattempt the test.

+

[[File:Idlingg.png|left|thumb|240x240px]]

−

+

Configuration of Excessive idling scenario:

−

~~'''~~Excessive ~~Idling settings'''~~:

*11200 - Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic).

−

* 11203 - Eventual settings (0 - Disable, 1 - Enable), if disabled - excessive idling data will come with periodical data.

+

*11203 - Eventual settings (0 - Disable, 1 - Enable), if disabled - excessive idling data will come with periodical data.

−

* 11205 - Time To Stopped (s). Represents how long vehicle should not move with engine ON.

−

* 11206 - To To Moving (s). Represents how long vehicle should be moving with engine ON, to exit idle state.

−

* 7033 - ID of SMS recipient.

−

* 8033 - SMS Text.

+

*11205 - Time To Stopped (s). Represents how long vehicle should not move with engine ON.

+

*11206 - To To Moving (s). Represents how long vehicle should be moving with engine ON, to exit idle state.

+

*7033 - ID of SMS recipient.

+

*8033 - SMS Text.

+

+

+

+

−

'''Quick start:''' From default configuration to GPS electronic logbook records in one SMS:

+

'''Quick start:''' From default configuration to [[FMB001_SMS/GPRS_Commands|GPS electronic logbook records in one SMS]]:

−

" setparam 11800:1;11801:0;11806:1;11000:2;11007:1;11200:2"

+

" setparam 2001:APN;2002:APN_username;2003:APN_password;2004:Domain;2005:Port;2006:0;11800:1;11801:0;11806:1;11000:2;11007:1;11200:2"

−

This SMS will set up Your device to send Trip, Eco/Green driving and Excessive idling data to Your previously provided server.

+

This SMS will set up Your device to send Trip, Eco/Green driving, and Excessive idling data to Your previously provided server.

−

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

+

'''Note''': Before SMS text, two space symbols should be inserted if no SMS username or password was set in [[FMB001_SMS/Call_settings|SMS / Call settings]].

−

=== BTAPP Mobile application ===

+

===3. BTAPP Mobile application===

[[File:Business private.png|left|thumb|253x253px]]

−

After making configuration for Your device, it is time to [[BTAPP Mobile application|'''download BTAPP''']]. Keep in mind, app and device connection is established via Blue-tooth. Devices by default come with ~~Blue-tooth~~ enabled and visible. After pairing to device - You can change the trip type of Your trips by performing a long press on the icon and confirming the change.

+

After making configuration for Your device, it is time to [[BTAPP Mobile application|'''download BTAPP''']]. Keep in mind, app and device connection is established via Blue-tooth. Devices by default come with Bluetooth® enabled and visible. After pairing to the device - You can change the trip type of Your trips by performing a long press on the icon and confirming the change.

Line 106: Line 137:

−

~~== Parsing GPS electronic logbook records ==~~

−

=== Prerequisites ===

+

==Parsing information==

−

~~First of all, in order to parse packets with GPS electronic logbook records it is mandatory to open TCP or UDP port~~. ~~Instructions can be found~~ [[Opening TCP/UDP port|~~'''here'''~~]].

+

==='''1. Prerequisites:'''===

+

==== 1.1. Open [[Opening TCP/UDP port|TCP/UDP port]] ====

−

~~After establishing TCP or UDP port, packets can be parsed automatically~~. ~~In order~~ to ~~learn how it is done, please visit '''~~[[Java Parser First Start Guide]]~~'''.~~

+

==== 1.2. Go to [[Java Parser First Start Guide|Java parser first start guide]] ====

−

=== Parsing example ===

+

==='''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

Line 127: Line 160:

! 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;" | Zero Bytes

| style="vertical-align: middle; text-align: center;" |00 00 00 00

|-

Line 142: Line 175:

| style="vertical-align: middle; text-align: center;" |00 00 01 77 16 AE 03 D8 (Mon Jan 18 18:07:19 UTC 2021)

|-

−

| style="vertical-align: middle; text-align: center;" |Priority

+

| style="vertical-align: middle; text-align: center;" | Priority

| style="vertical-align: middle; text-align: center;" |01

|-

Line 184: Line 217:

| 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;" | 3’rd IO ID

| style="vertical-align: middle; text-align: center;" |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;" | 3’rd IO Value

| style="vertical-align: middle; text-align: center;" |05

|-

−

|style="vertical-align: middle; text-align: center;" |4'th IO ID

+

| style="vertical-align: middle; text-align: center;" |4'th IO ID

−

|style="vertical-align: middle; text-align: center;" |50 (AVL ID: 80, Name: Data mode)

+

| style="vertical-align: middle; text-align: center;" |50 (AVL ID: 80, Name: Data mode)

|-

−

|style="vertical-align: middle; text-align: center;" |4'th IO Value

+

| style="vertical-align: middle; text-align: center;" |4'th IO Value

−

|style="vertical-align: middle; text-align: center;" |01

+

| style="vertical-align: middle; text-align: center;" |01

|-

| style="vertical-align: middle; text-align: center;" |5'th IO ID

Line 200: Line 233:

|-

| 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;" | 00

|-

| style="vertical-align: middle; text-align: center;" |6'th IO ID

Line 206: Line 239:

|-

| style="vertical-align: middle; text-align: center;" |6'th IO Value

−

| style="vertical-align: middle; text-align: center;" |01

+

| style="vertical-align: middle; text-align: center;" | 01

|-

−

|style="vertical-align: middle; text-align: center;" |7'th IO ID

+

| style="vertical-align: middle; text-align: center;" |7'th IO ID

−

|style="vertical-align: middle; text-align: center;" |01 (AVL ID: 1, Name: Digital Input 1)

+

| style="vertical-align: middle; text-align: center;" |01 (AVL ID: 1, Name: Digital Input 1)

|-

−

|style="vertical-align: middle; text-align: center;" |7'th IO Value

+

| style="vertical-align: middle; text-align: center;" |7'th IO Value

−

|style="vertical-align: middle; text-align: center;" |01

+

| style="vertical-align: middle; text-align: center;" |01

|-

| style="vertical-align: middle; text-align: center;" |8'th IO ID

Line 220: Line 253:

| style="vertical-align: middle; text-align: center;" |03 (01 - harsh acceleration, 02 - harsh braking, 03 - harsh cornering)

|-

−

|style="vertical-align: middle; text-align: center;" |9'th IO ID

+

| style="vertical-align: middle; text-align: center;" |9'th IO ID

−

|style="vertical-align: middle; text-align: center;" |FE (AVL ID: 254, Name: Green Driving Value)

+

| style="vertical-align: middle; text-align: center;" |FE (AVL ID: 254, Name: Green Driving Value)

|-

−

|style="vertical-align: middle; text-align: center;" |9'th IO Value

+

| style="vertical-align: middle; text-align: center;" |9'th IO Value

−

|style="vertical-align: middle; text-align: center;" |23 ( Depending on green driving type: if harsh acceleration or braking - g*100 (value 123 ->1,23g). If Green driving source is "GPS" - harsh cornering value is rad/s*100. If source is "Accelerometer" - g*100.

+

| style="vertical-align: middle; text-align: center;" |23 ( Depending on green driving type: if harsh acceleration or braking - g*100 (value 123 ->1,23g). If Green driving source is "GPS" - harsh cornering value is rad/s*100. If source is "Accelerometer" - g*100.

|-

−

| style="vertical-align: middle; text-align: center;" |N2 of Two Byte IO

+

| style="vertical-align: middle; text-align: center;" | N2 of Two Byte IO

| style="vertical-align: middle; text-align: center;" |0B

|-

Line 259: Line 292:

| style="vertical-align: middle; text-align: center;" |0F 8A

|-

−

|style="vertical-align: middle; text-align: center;" |6'th IO ID

+

| style="vertical-align: middle; text-align: center;" | 6'th IO ID

−

|style="vertical-align: middle; text-align: center;" |44 (AVL ID: 68, Name: Battery Current)

+

| style="vertical-align: middle; text-align: center;" |44 (AVL ID: 68, Name: Battery Current)

|-

−

|style="vertical-align: middle; text-align: center;" |6'th IO Value

+

| style="vertical-align: middle; text-align: center;" |6'th IO Value

−

|style="vertical-align: middle; text-align: center;" |00 00

+

| style="vertical-align: middle; text-align: center;" |00 00

|-

| style="vertical-align: middle; text-align: center;" |7'th IO ID

Line 289: Line 322:

| style="vertical-align: middle; text-align: center;" |FB D9

|-

−

|style="vertical-align: middle; text-align: center;" |11'th IO ID

+

| style="vertical-align: middle; text-align: center;" |11'th IO ID

−

|style="vertical-align: middle; text-align: center;" |0F (AVL ID: 15, Name: Eco score)

+

| style="vertical-align: middle; text-align: center;" |0F (AVL ID: 15, Name: Eco score)

|-

−

|style="vertical-align: middle; text-align: center;" |11'th IO Value

+

| style="vertical-align: middle; text-align: center;" |11'th IO Value

−

|style="vertical-align: middle; text-align: center;" |03 84

+

| style="vertical-align: middle; text-align: center;" |03 84

|-

−

|style="vertical-align: middle; text-align: center;" |N4 of Four Byte IO

+

| style="vertical-align: middle; text-align: center;" |N4 of Four Byte IO

−

|style="vertical-align: middle; text-align: center;" |02

+

| style="vertical-align: middle; text-align: center;" |02

|-

−

|style="vertical-align: middle; text-align: center;" |1'st IO ID

+

| style="vertical-align: middle; text-align: center;" |1'st IO ID

−

|style="vertical-align: middle; text-align: center;" |02 C7(AVL ID: 199, Name: Trip Odometer)

+

| style="vertical-align: middle; text-align: center;" |02 C7(AVL ID: 199, Name: Trip Odometer)

|-

−

|style="vertical-align: middle; text-align: center;" |1’st IO Value

+

| style="vertical-align: middle; text-align: center;" |1’st IO Value

−

|style="vertical-align: middle; text-align: center;" |00 00 03 BD

+

| style="vertical-align: middle; text-align: center;" | 00 00 03 BD

|-

−

|style="vertical-align: middle; text-align: center;" |2’nd IO ID

+

| style="vertical-align: middle; text-align: center;" |2’nd IO ID

−

|style="vertical-align: middle; text-align: center;" |10 03(AVL ID: 16, Name: Total Odometer)

+

| style="vertical-align: middle; text-align: center;" |10 03(AVL ID: 16, Name: Total Odometer)

|-

−

|style="vertical-align: middle; text-align: center;" |2’nd IO Value

+

| style="vertical-align: middle; text-align: center;" |2’nd IO Value

−

|style="vertical-align: middle; text-align: center;" |06 68 80 20

+

| style="vertical-align: middle; text-align: center;" |06 68 80 20

|-

−

|style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)

+

| 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;" |01

|-

−

|style="vertical-align: middle; text-align: center;" |CRC-16

+

| style="vertical-align: middle; text-align: center;" |CRC-16

−

|style="vertical-align: middle; text-align: center;" |00 00 5F 75

+

| style="vertical-align: middle; text-align: center;" |00 00 5F 75

|}

−

== In platform ==

+

==Demonstration in platform==

−

Packet information can be displayed visually. In the picture below, event location is displayed on the map. ~~Dot~~ on the map represents a record. By clicking on it, it is possible to see what kind of information is gathered in the particular entry.

+

Packet information can be displayed visually. In the picture below, the event location is displayed on the map. The dot on the map represents a record. By clicking on it, it is possible to see what kind of information is gathered in the particular entry.

+

In order to visually see received information on the platforms:

+

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

[[File:Viz.png|center|thumb|1024x1024px]]

−

~~In order to visually see received information on the platforms:~~

−

* '''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.

+

−

* '''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.

+

'''[https://gurtam.com/en/wialon WIALON]''': Open WIALON → open messages → push unit ( select your device) → choose the date from which to show the records → select message (data messages) → push execute button and you will see all information. (Note''':''' ''Figure below is an example and doesn't represent the actual visualization of the packet in the parsing example'').[[File:Wialon snip.png|center|thumb|1028x1028px]]

+

[[Category:Usage scenarios]]

+

'''BTAPP''': [[File:Eco.PNG|left|thumb|600x600px]]

+

Bluetooth® connection to monitor and score driver behavior. Real-time events notifications about harsh acceleration, braking, cornering, overspeeding, idling, and RPM. Solution designed to improve driver behavior and productivity.

+

*You must connect to the FMB device by clicking the Bluetooth® icon, and selecting your FMB device.

+

*Each event that was detected by the FMB device will be displayed in the application as well. Users can be notified visually, the event icon will turn yellow and the event count will be increased accordingly, and by sound alert as well (can be optionally enabled in application settings).

+

*Eco score is calculated by FMB device depending on total event amount and trip distance.

+

Eco score, distance, and duration are being updated periodically automatically.

+

*Trip status can be Ongoing and Finished. The trip finish is decided by FMB configuration. If the application will be connected to an FMB device during an ongoing trip – the application will update event count, score, distance, and trip duration for an ongoing trip.

Arnas.Zeb

Administrators

4,542

edits

Namespaces

Variants

Views

More

Search

Changes

GPS Electronic Logbook (view source)

Revision as of 16:22, 28 December 2023

Navigation menu

Personal tools

NAVIGATION

Tools

Categories