Teltonika Telematics Wiki - User contributions [en]

EU Data Act

2025-09-15T04:55:10Z

Edgardas.zapolskis:

=1. Introduction to EU Data Act=

According to '''Regulation (EU) 2023/2854, Article 3''', users of connected products and related services must be provided with transparent information on how data is generated, accessed, and shared.

In particular, Article 3 requires manufacturers and service providers to inform users, before they purchase or use a product, about:
* what data will be generated,
* how the data can be accessed,
* how the user may share the data with third parties, and
* any applicable restrictions.

This statement explains how Teltonika Telematics complies with these obligations.

=2. Our Obligations under the Data Act=

In line with Regulation (EU) 2023/2854, we confirm:
* We will '''not use your device, FOTA WEB or TachoSync data''' to compete against you or to obtain unfair advantages.
* We will '''not impose restrictions''' preventing you from accessing or transferring your data.
* We will '''clearly inform you''' what data categories are generated and how they can be accessed.
* We will provide '''interoperable interfaces (e.g., APIs, data export functions)''' for effective data portability.

=3. Sharing Data with Third Parties=

Under '''Article 3 of the EU Data Act''', you have the right to decide whether and how your data is shared with third parties. Teltonika Telematics fully supports this principle.

==3.1. Your Right to Share Data==
* You may instruct us to make your data directly available to a third party of your choice.
* We will not restrict or block this transfer.
* We will not make it conditional on additional fees or unfair contract terms.

==3.2. Safeguards==

* We apply appropriate measures to protect:
* Trade secrets (ensuring sensitive business information is not exposed beyond what is necessary).
* Security and privacy (preventing unauthorized access or misuse of shared data).
* These safeguards will not be misused to deny or limit your right to share data.

=4. Devices and related services=
==4.1. What Data is Generated by Teltonika Telematics Devices==

Our telematics devices may generate the following categories of data:
* '''Vehicle operation data''' – ignition status, speed, acceleration, braking, fuel level, odometer readings ant etc..
* '''Location and movement data''' – GPS position, routes, geofencing information, trip history etc..
* '''Driver behaviour data''' – harsh braking/acceleration, idling, eco-driving parameters etc..
* '''Device and system data''' – connectivity status, error codes, firmware information, sensor readings from connected accessories (e.g., temperature, door sensors, CAN bus) etc..

All devices' generated data is described under every device's ''Data sending parameters list'', for example, [https://wiki.teltonika-gps.com/view/FMB910_Teltonika_Data_Sending_Parameters_ID FMB910 Data Sending Parameters ID]

This data supports product functionality and customer fleet operations, and does not extend beyond the intended purpose.

===4.1.1. Who and how Can Access the Telematics Devices Data===
* '''You, the customer''', have the right to access all data generated by your Teltonika devices.
* Data is provided in a '''structured, commonly used, machine-readable format''' ([https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols Data Sending Protocol])
* Data is accessible in '''real time''' as data is sent to '''your configured server'''.

==4.2. What Data is Generated by the Teltonika Telematics FOTA WEB platform==

FOTA WEB is our remote device management platform, used to configure, update, and monitor devices. It may generate or process the following data:
* '''Device data''' – IMEI, firmware information, model type , etc.
* '''Vehicle data''' - VIN number, vehicle information

All the connected Telematics device generated and to the FOTA WEB transmitted data can be found [https://wiki.teltonika-gps.com/view/FOTA_WEB_data FOTA WEB data]

This data supports product functionality and customer fleet operations, and does not extend beyond the intended purpose.

===4.2.1. Who and how Can Access the FOTA WEB Data===

* '''You, the customer''', have the right to access all data generated by your Teltonika devices.
* Data is provided in a '''structured, commonly used, machine-readable format'''.
* Data is accessible through:
** '''APIs''' (real-time access/integration) - [https://wiki.teltonika-gps.com/view/FOTA_WEB_Getting_Started_API FOTA WEB Getting Started API]
** '''FOTA WEB dashboards''' - [https://wiki.teltonika-gps.com/view/Dashboard FOTA WEB dashboards]
** '''Exports/reports''' (CSV, XML) - [https://wiki.teltonika-gps.com/view/FOTA_WEB_Devices#Export FOTA WEB Export]

==4.3. What Data is Generated by the Teltonika Telematics TachoSync platform==
The related service generates the following categories of data:
* '''Tachograph file data''' – vehicle unit and driver card.
* '''Company card data''' - card ID, expiration date .
* '''Driver data''' - name, activity information .

All the connected Telematics device generated and to the TachoSync transmitted data can be found [https://wiki.teltonika-gps.com/view/TachoSync_data TachoSync Data]

This data supports product functionality and customer fleet operations, and does not extend beyond the intended purpose.

===4.3.1. Who and how Can Access the Data===

* '''You, the customer''', have the right to access all data generated by your Teltonika devices.
* Data is provided in a '''structured, commonly used, machine-readable format'''.
* Data is accessible through:
** '''APIs''' (real-time access/integration)
** '''TachoSync dashboards'''
** '''Exports''' (.DDD, .TGD, .V1B, .C1B)

=5. Support and Contact =
If you have any questions about your data rights or how to access or share data from Teltonika Telematics products, please fill in HelpDesk ticket or contact us via [https://www.teltonika-gps.com/contact-us Form].

2021-03-09T16:47:52Z

Edgardas.zapolskis:

==Project description==

One of the more advanced features of GPS trackers is the ability to create Geofence scenarios in a real-time with triggered alerts. Geofences are designated areas or zones that can be defined on a map or as a distance from the specific location. The feature may help to comply with some pandemic lockdown measures and greatly benefit private car owners, families, corporate fleet managers and business owners. All Teltonika GPS tracker models have Geofence as a standard feature.

==What you need for a solution?==

*Geofence solution is supported by '''all Teltonika devices'''. To show this scenario, we will be using the [[FMM130]] model.
*The SIM card in order to receive data to your server.
*[[Teltonika Configurator]] to make the configurations for your Teltonika device.
*[[FOTA WEB]] to send the configurations to your device remotely.

==Installation==

Since Geofence can be used in all of Teltonika devices, it is important to follow your specific device [https://wiki.teltonika-gps.com/view/FMM130_First_Start#Mounting_recommendations mounting recommendations]. This is because if you were to install the tracker following the instructions of a different one, your device may not work properly in the end. Also, we offer a wide range of trackers that have different connectors, some of the devices we offer are "Plug and Track" (devices that have OBD-II connectors), other may demand more wiring work to be done. The list of all Teltonika Fleet Management devices can be found [[Fleet management | here]].

==Configuration==

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

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

====1.2. Understanding what [https://wiki.teltonika-gps.com/view/FMM130_Manual_Geofence_settings manual Geofence] has to offer.====

'''2. Configuration of Manual Geofence feature'''[[File:GPRS settings.png|alt=|left|frame]]

[[FMM001 Parameter list|Parameter ID]] – Parameter name GPRS settings: 
 
 
*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|alt=|left|frame]]
 
 
 
 

 Server settings:

*2004 – Domain
*2005 – Port
*2006 – Data sending protocol (0 – TCP, 1 – UDP)
 
 
 

After successful GPRS/SERVER settings configuration, FMM130 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 [[FMM130 Parameter list|SMS parameters]]. 

[[File:manual_geofence_selection.jpg|alt=|left|665x665px|thumb]]

Manual Geofence settings:

*20100 - Feature priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic)

*20101 - Generate Event (0 - No Event, 1 - On Exit, 2 - On Entrance, 3 - On Both)
* 20102 - Eventual Records (0 - Disable, 1 - Enable)
 

* 20103 - Frame Border (m)
*20104 - Shape Type (0 - Circle, 1 - Rectangle)
* 20105 - Radius (m)
*20106 - Coordinate Y1
*20107 - Coordinate X1
*20108 - Coordinate Y2
*20109 - Coordinate X2
 

* 20110 - Overspeeding (0 - Disable, 1 - Enable)

* 20111 - Max allowed speed (km/h)

* 7025 - Phone Number
* 8025 - SMS Text
 
 
 
 
 
 
'''Note''': Radius is only calculated if the chosen Shape Type is a Circle. In this example, Radius cannot be seen since the shape chosen is the Rectangle. Also, Latitude Y2 and Longitude X2 are only used when Rectangle is the chosen shape.

 

[[File:Manual geofence map.jpg|left|frameless|394x394px]]
It is also important to mention that the map in the Manual Geofence function section has a few features as well if you wish to make some adjustments using the interface:

It is possible to draw the Geofence area manually by selecting the Rectangle or the Circle icon on the left. That way, it is not necessary to know the exact coordinates of the wanted area, as long as it is marked on the map correctly.

Once that is done, the latitude and the longitude fields will be filled in automatically.

If you wish to delete your Geofence area, you can click the "Delete geozone" button. That way, the area is deleted and the configurations made are restored to default settings.

In case there are more than one zones available, by clicking on one of them will bring up its layout details.

The last button on the interface is used to zoom in on all of the available geozones.

 
 
 

'''Quickstart:''' From default configuration to Geofence crossing detection in two SMS:
" setparam 2001:APN;2002:APN_username;2003:APN_password;2004:Domain;2005:Port;2006:0"

" setparam 20100:2;20101:2;20104:1;20106:latitudeY1;20107:longitudeX1;20108:latitudeY2;20109:longitudeX2"

This SMS will set up your device to report Geofence Crossing Detection scenario to the server.

'''Note''': We're sending two instead of one configuration messages since one SMS can contain up to 160 characters. For this scenario, we exceed the maximum allowed character amount. Therefore, we split the message into two.

==Parsing Geofence records==

==='''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;" | 00000000000000460801000001776D581890010F07C39A
209CE0C2009C009D05000F9B0D06EF01F0001505C80045019B0105B5000BB6000
A424257430F8044000002F1000060191000000BE1000100005139
|-
|}

{| class="nd-othertables_2" style="width:100%;"
|+
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! 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 46
|-
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |08 (Codec 8)
|-
| 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 77 49 BC 8E 70 (Thursday, February 4, 2021 2:00:26 PM)
|-
| 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 07 C3 9A
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |20 9C E0 C2
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 9C
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 9D
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 0F
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |9B (AVL ID: 155, Name: Geofence zone 01)
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |0D
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |06
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |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;" |F0 (AVL ID: 240, Name: Movement)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| 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;" |05
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |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;" |45 (AVL ID: 69, Name: GNSS Status)
|-
| style="vertical-align: middle; text-align: center;" |5'th IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |6'th IO ID
| style="vertical-align: middle; text-align: center;" |9B (AVL ID: 155, Name: Geofence zone 01)
|-
| style="vertical-align: middle; text-align: center;" |6'th IO Value
| style="vertical-align: middle; text-align: center;" |01 (00 – target left zone, 01 – target entered zone, 02 – over speeding end, 03 – over speeding start)

|-
| style="vertical-align: middle; text-align: center;" |N1 of Two Byte IO
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |B5 (AVL ID: 181, Name: GNSS PDOP)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 0B
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |B6 (AVL ID: 182, Name: GNSS HDOP)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00 0A
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, Name: External Voltage)
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |42 57
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |43 (AVL ID: 67, Name: Battery Voltage)
|-
| style="vertical-align: middle; text-align: center;" |4'th IO Value
| style="vertical-align: middle; text-align: center;" |0F 80
|-
| style="vertical-align: middle; text-align: center;" |5'th IO ID
| style="vertical-align: middle; text-align: center;" |44 (AVL ID: 68, Name: Battery Current)
|-
| style="vertical-align: middle; text-align: center;" |5'th IO Value
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N4 of Four Bytes IO
| 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;" |F1 (AVL ID: 241, Name: Active GSM Operator)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 00 60 19
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |10 (AVL ID: 16, Name: Total Odometer)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |00 00 0B E1
|-
| style="vertical-align: middle; text-align: center;" |N8 of Eight Bytes IO
| style="vertical-align: middle; text-align: center;" |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 51 39
|-
|}

==In platform==
[[Category:Usage scenarios]]

TAVL:

TAVL: Open TAVL → select client → Events → Geozones. Firstly, a geozone needs to be chosen in order to see the event of the device crossing it (just like in the configurator). Depending on what is needed, additional zone rules and warning rules need to be created. When opening the Console window, the events of crossing are displayed, with the location of where did that happen, was it on entrance or on exit, etc.
[[File:Tavl_test.jpeg|alt=|frameless|1153x1153px]]

Template:Usage Scenarios

2021-03-04T07:37:21Z

Edgardas.zapolskis:

2019-05-28T07:30:42Z

Edgardas.zapolskis:

GSM / GPRS / GNSS features:
* Teltonika TM2500 quad band module (GSM 850 / 900 / 1800 / 1900 MHz);
* GPRS class 12 (up to 240 kbps);
* GPRS Mobile Station Class B
* SMS (text, data);

Blue-tooth:
* Blue-tooth specification V4.0
* Blue-tooth transceiver fully complaint with Blue-tooth specification V4.0 for external peripherals:
** Voice calls over Blue-tooth
** Configuration via Blue-tooth

GNSS features:
* Tracking: 33/ 99 acquisition channels
* -165 dBM sensitivity
* Hot start <1s
* Warm Start < 25s
* Cold start < 35s
* NMEA-183 protocol
* GPS, GLONASS, GALILEO, BEIDOU, SBAS, QZSS, DGPS, AGPS
* Accuracy < 3m

FMB640 firmware errata

2019-01-04T14:45:42Z

Edgardas.zapolskis: