Teltonika Telematics Wiki - User contributions [en]

FMC650 TCA

2026-04-08T02:35:32Z

Wasiqchaudhry:

=Introduction=
The document explains how providers can integrate Teltonika’s TCA approved devices with their platform. Device data sending protocol is still the same with some slight changes made to comply with TMA Level 2 requirements. The purpose of this document is to provide TCA and ASPs the necessary guidance on how to implement the TCA compliant solution with FMC650.

'''Device''': FMC650 
'''Firmware''': 03.00.16.Rev.304_1059 
'''Protocol''': Teltonika [[Codec|Codec8 Extended]] 

=Firmware changelog=
'''Previous firmware''': 03.00.16.Rev.303_1059 
'''New firmware''': 03.00.16.Rev.304_1059 
'''Changelog''': 
* Added fixes where device was sending records every second once the ignition has
been turned off.
* Added fixes where device was generating data at 28th second instead of the
configured 30th (Min Period).
*Added fixes to eliminate record sending delay after vehicles enters or exits the
tunnel.

=Identification of lost GPS Fix=
The base protocol remains the same as of Teltonika’s proprietary [[Codec|'''CODEC 8 EXTENDED''']]. Changes specific to TCA in SPEC ID 1059 are described below.

'''Via longitude & Latitude values''' 
After the device’s GNSS Fix is lost, the device sends the following values as latitude and longitude instead of the last known locat on or 0/0.

'''Latitude''': 0xFFFFFFFF 
'''Longitude''': 0xFFFFFFFF 

The values are not plottable on the map and integrators can identify and discard these values.

'''Via GNSS Status Flag (AVL ID 71)''' 
GNSS Status Flag (AVL ID 71) can be used to identify a lost GNSS Fix. Refer to the table below for more details:
{| class="wikitable"
|+
! rowspan="7" |GNSS Status (71)
!Value
!Status
|-
|0
|GNSS OFF
|-
|1
|GNSS ON, no GPS
|-
|2
|GNSS ON, without fix
|-
|3
|GNSS ON, with fix
|-
|4
|GNSS SLEEP
|-
|5
|GNSS Overcurrent/protect state
|}

As mentioned in the table above, GNSS Fix is only valid when the value for AVL ID 71 is “3”. If the GNSS status value (71) not 3, value of longitude and longitude can be discarded

=Device configuration guide=
Device configuration can be changed according to the described guidelines. Note that any changes should comply with the TCA guidelines.

'''Key''': 

● locked parameters / not available to be changed 
●Can be changed but change should comply with TCA guidelines or as instructed. 
● Can be changed. 
● Any other changes to the config that are not covered below should be consulted with Teltonika & TCA. 

'''Note''': Any changes made to the config must not impact the data acquisition settingsand settings related to base parameters (time (data sending time), longitude, latitude & speed).

==Config sections that can be reconfigured as needed by the ASPs==
[[File:2025-02-28 1.png]] 
 

==Security configuration==

[[File:2025-02-28 2.png]] 
 

==GPRS configuration==
[[File:2025-02-28 3.png]]

==Data Acquisition configuration==
[[File:2025-02-28 4.png]]

==Features & Accelerometers Features configuration==
Scenarios can be activated but '''must''' be set to low priority only. Any eventual data should be disabled.
By default, all the scenarios are disabled.

==IO configuration==
[[File:2025-02-28 5.png]]

==Configuration File==
Base configuration file that has been approved by TCA can be provided by Teltonika via Helpdesk.

===Additional salient guidelines to maintain compliance===
# The following 3 parameters should be discarded by ASP from data received from device or should only be used for internal purposes. TCA’s solution should not have the visibility for it.
## Number of satellites
## HDOP
## PDOP
# All peripherals (RS232/RS485, Video Solutions, Digital I/O, FMS, MobilEye, Tacho, Bluetooth etc.) are disabled* by default. To use any peripherals (including any that are not listed otherwise), approval from TCA and Teltonika is needed. *The only peripheral enabled by default is USB. The interface can be used to load the initial configurations, e.g., APN, server domain & port etc., as per the instructions provided in [[Device configuration guide]].
# External power voltage and Ignition Status is sent with the AVL data and is contained in each packet.
# SD card slot has not been used since internal memory is enough to hold records for up to 6 hours. In case external SD card is needed, approval is required from TCA and Teltonika.
# Device is not password protected by default and can be accessed through USB. ASPs should add keyword protection for serial interface over USB. Refer to [[Security Configuration]] guide.

===Declarations===
#The date and time data collected by the telematics device is within:
## 1 second from UTC when using GNSS signals &
## 10 seconds from UTC when not using GNSS signals for 24 hours.

===FAQs===
'''Q:''' How the Real-Time Clock (RTC) operates and is affected by the internal battery? 

'''A:''' If external power is gone device works from battery without any issues in same manner as with external power supply.

'''Q:''' Clarification on how the internal battery affects timestamp generation and record creation when the device is powered off for several days? 

'''A:''' Internal battery did not affect anything regarding record creation or timestamp. This only depends how log battery will maintain power for device.

'''Q:''' Understanding of how long the device can generate records once the external power source is disconnected and the internal battery is depleted just an estimate will be enough? 

'''A:''' The amount of time the device will work from internal battery depends on the battery health, how often the device saves/sends information to the server, external peripherals connected to the device and the results may also differ depending on firmware used.

For general comparison purpose, and to see what results can be achieved, you can refer to the following internal test results in different modes and sending frequencies:

{| class="wikitable"
|+
!Mode:
!Min Period (data
saving

frequency)
!Send Period (data
sending

frequency)
!Starting
Voltage
!Cut off Voltage
!Time achieved
|-
|Operating
|10 seconds
|60 seconds
|10.1V
|7.0V
|452 min (7 hours 32
minutes)
|-
|Operating
|60 seconds
|60 seconds
|10.1V
|7.0V
|507 min (8 hours 27
minutes)
|-
|Deep Sleep
|12 hours
|12 hours
|10.2V
|8.2V
|5040 min (84 hours 0
minutes)
|-
|Online Deep Sleep
|12 hours
|12 hours
|10.2V
|8.6V
|1440 min (24 hours 0
minutes)
|}

'''Q:''' What happens when the device is turned back on and how it recovers its clock and data saving capabilities? 

'''A:''' When device is turned on after long time it try to sync RTC time with configured source, record generation capabilities depend on configuration.

'''Intellectual property rights'''
The Customer acknowledges that UAB TELTONIKA TELEMATICS shall be the exclusive owner of all intellectual property rights used in connection with the products and/or Services the Customer purchases.

=Atachments=
You can download this informatin about FMC650 TCA in a document, by clicking [[Media:TELTONIKA FMCT650 TCA GUIDELINES 2v4.pdf|here]].

[[Category:FMC650 Manual]]

Frequently Asked Questions - FAQ

2026-01-28T05:25:11Z

Wasiqchaudhry: Undo revision 110831 by Wasiqchaudhry (talk)

__TOC__

==FM devices==
*[[Preparing for the 2G and 3G Sunsets]]

*[[Starting with Teltonika Telematics]]
*[[Recommendations for filling a query description]]
*[[How to start with FMB devices and Beacons?]]
*[[Teltonika Vehicle Telematics device mounting instructions]]

*[[RMA guidelines]]
*[[Helpdesk query filling recommendations| How to correctly fill the Helpdesk ticket?]]

*[[How to capture remote log from FM device?]]
*[[How to capture remote Tacho log from FM device?]]
*[[Why my device is not sending data to server?]]
*[[Where can I find PDF versions of FM manuals?]]
*[[Requirements for eSIM]]
*[[Sending SMS to FMB devices with 1nce platform]]
*[[Auto APN feature for FM trackers]]
*[[How to set up Eco Driving in Wialon app]]
*[[Frequency Bands]]
*[[Firmware versions]]
*[[Which data protocol to choose Codec 8 or Codec 8 Extended]]
*[[How to Fix Fuel Level Jumps in CAN or OBD Data in Teltonika FMB Devices]]

==FT devices==
*[[AVL ID differences between FMB and FT platforms]]
*[[Dead Reckoning feature]]

==CAN bus adapters==
{{FAQ_can_adapters}}

==EYE Accessories==
*[[EYE FAQ|Table of contents]]
*[[EYE FAQ#Questions%20about%20Power%20and%20Electrical%20characteristics|Questions about Power and Electrical characteristics]]
*[[EYE FAQ#Questions%20about%20EYE%20Accessory%20configuration%20.28EYE%20APP.29|Questions about EYE Accessory configuration (EYE APP)]]
*[[EYE FAQ#Questions%20about%20FMBxxx%20compatibility%20with%20EYE%20Accessories|Questions about FMBxxx compatibility with EYE Accessories]]
*[[EYE FAQ#Questions%20about%20Protocols|Questions about Protocols]]
*[[EYE FAQ#Other%20questions%20.28Questions%20without%20category.29|Other questions (Questions without category)]]

==Bluetooth® solutions==
*[[How to connect OBD II Bluetooth® Dongle to FMB device|How to connect OBD II Bluetooth® Dongle to FMB device?]]
*[[How to connect Bluetooth® Hands Free adapter to FMB device|How to connect Bluetooth® Hands Free adapter to FMB device?]]
*[[How to add a BLE preset to the configurator|How to add a BLE preset to the configurator?]]
*[[How to debug FMB device over Android smartphone?]]
*[[Making Custom BLE Sensor configuration and preset]]
*[[How to capture ELA Beacon internal battery voltage?]]
*[[How to read data from TZ-BT04/05/05B sensor]]
*[[How to read data from BLE Sensors]]
*[[How to read data from BLE Beacons]]
*[[Advanced Beacon Capturing Configuration]]
*[[BLE broadcast service ID configuration]]

==OBD solutions==
*[[How to check available OBDII data?]]
*[[How to capture OBDII data log?]]
*[[OBD supported vehicle list]]
*[[OEM_Parameters|How to enable OEM Parameters?]]
*[[OBD II TO FMS ADAPTER AND J1939 SUPPORT IN FMx003]]
*[[OBDII EV Parameters|How to read OBDII EV Parameters?]]
*[[Distance since refuel]]
*[[OBD Tracker Configuration for Electrical Vehicles – Basic Recommendations]]

==Serial interface solutions==
*[[Modbus slave integration with FMX125/FMX640]]

==Selling solutions as your own==
*[[Changing brand on OEM devices]]

==IoT portal==
*[https://wiki.teltonika-gps.com/view/IoT_Platform_SMS_Messaging_Feature| Sending free and unlimited SMS with IoT Platform 1Global]
*[https://wiki.teltonika-gps.com/view/Rules_%26_Alerts| Creating Auto Top Up / Expiration monitoring rule 1Global]
*[https://wiki.teltonika-gps.com/view/Reports_%26_Analytics#Data_Usage_Report| How to check data usage with IoT Platform 1Global]
*[https://wiki.teltonika-gps.com/view/Preparing_for_the_2G_and_3G_Sunsets| 2G and 3G Sunsets dates]

==Encryption==
*[[TLS/DTLS implementation for Flespi using OpenSSL]]

[[Category:Main Page]]

Frequently Asked Questions - FAQ

2026-01-28T04:43:28Z

Wasiqchaudhry:

__TOC__

==FM devices==
*[[Preparing for the 2G and 3G Sunsets]]

*[[Starting with Teltonika Telematics]]
*[[Recommendations for filling a query description]]
*[[How to start with FMB devices and Beacons?]]
*[[Teltonika Vehicle Telematics device mounting instructions]]

*[[RMA guidelines]]
*[[Helpdesk query filling recommendations| How to correctly fill the Helpdesk ticket?]]

*[[How to capture remote log from FM device?]]
*[[How to capture remote Tacho log from FM device?]]
*[[Why my device is not sending data to server?]]
*[[Where can I find PDF versions of FM manuals?]]
*[[Requirements for eSIM]]
*[[Sending SMS to FMB devices with 1nce platform]]
*[[Auto APN feature for FM trackers]]
*[[How to set up Eco Driving in Wialon app]]
*[[Frequency Bands]]
*[[Firmware versions]]
*[[Which data protocol to choose Codec 8 or Codec 8 Extended]]
*[[How to Fix Fuel Level Jumps in CAN or OBD Data in Teltonika FMB Devices]]

==FT devices==
*[[AVL ID differences between FMB and FT platforms]]
*[[Dead Reckoning feature]]

==CAN bus adapters==
{{FAQ_can_adapters}}

==EYE Accessories==
*[[EYE FAQ|Table of contents]]
*[[EYE FAQ#Questions%20about%20Power%20and%20Electrical%20characteristics|Questions about Power and Electrical characteristics]]
*[[EYE FAQ#Questions%20about%20EYE%20Accessory%20configuration%20.28EYE%20APP.29|Questions about EYE Accessory configuration (EYE APP)]]
*[[EYE FAQ#Questions%20about%20FMBxxx%20compatibility%20with%20EYE%20Accessories|Questions about FMBxxx compatibility with EYE Accessories]]
*[[EYE FAQ#Questions%20about%20Protocols|Questions about Protocols]]
*[[EYE FAQ#Other%20questions%20.28Questions%20without%20category.29|Other questions (Questions without category)]]

==Bluetooth® solutions==
*[[How to connect OBD II Bluetooth® Dongle to FMB device|How to connect OBD II Bluetooth® Dongle to FMB device?]]
*[[How to connect Bluetooth® Hands Free adapter to FMB device|How to connect Bluetooth® Hands Free adapter to FMB device?]]
*[[How to add a BLE preset to the configurator|How to add a BLE preset to the configurator?]]
*[[How to debug FMB device over Android smartphone?]]
*[[Making Custom BLE Sensor configuration and preset]]
*[[How to capture ELA Beacon internal battery voltage?]]
*[[How to read data from TZ-BT04/05/05B sensor]]
*[[How to read data from BLE Sensors]]
*[[How to read data from BLE Beacons]]
*[[Advanced Beacon Capturing Configuration]]
*[[BLE broadcast service ID configuration]]

==OBD solutions==
*[[How to check available OBDII data?]]
*[[How to capture OBDII data log?]]
*[[OBD supported vehicle list]]
*[[OEM_Parameters|How to enable OEM Parameters?]]
*[[OBD II TO FMS ADAPTER AND J1939 SUPPORT IN FMx003]]
*[[OBDII EV Parameters|How to read OBDII EV Parameters?]]
*[[Distance since refuel]]
*[[OBD Tracker Configuration for Electrical Vehicles – Basic Recommendations]]

==Serial interface solutions==
*[[Modbus slave integration with FMX125/FMX640]]

==Selling solutions as your own==
*[[Changing brand on OEM devices]]

==IoT portal==
*[https://wiki.teltonika-gps.com/view/IoT_Platform_SMS_Messaging_Feature Sending free and unlimited SMS with IoT Platform 1Global]
*[https://wiki.teltonika-gps.com/view/Rules_%26_Alerts Creating Auto Top Up / Expiration monitoring rule 1Global]
*[https://wiki.teltonika-gps.com/view/Reports_%26_Analytics#Data_Usage_Report How to check data usage with IoT Platform 1Global]
*[https://wiki.teltonika-gps.com/view/Preparing_for_the_2G_and_3G_Sunsets 2G and 3G Sunsets dates]

==Encryption==
*[[TLS/DTLS implementation for Flespi using OpenSSL]]

[[Category:Main Page]]

FMC150 General description

2025-11-17T08:23:10Z

Wasiqchaudhry:

{{Template:FMB General description|model=FMC150}}

==Package contents==
The FMC150 device is supplied to the customer in a cardboard box containing all the equipment that is necessary for operation. The package contains:
* FMC150 device;
* Input and output power supply cable with 2x6 connection pins;
* 3.7 V 170 mAh rechargeable Li-ion battery.

==Basic characteristics==

GSM / GPRS / GNSS features:
* Name QJIB0: Quectel EG915U-EU with Teltonika TM2500, QKIB0: Quectel EG915U-LA with Teltonika TM2500;
* Technology LTE(CaT1)/2G(GSM/GPRS)/GNSS/BLUETOOTH;
* SMS (text, data);
* Integrated GNSS receiver;
* Up to -165 dBm GNSS receiver sensitivity.

CELLULAR:
{| class="wikitable"
|style="background: #0054A6; color:white" |'''Technology'''
|style="background: #0054A6; color:white" |'''Supported bands'''
|-
| rowspan="2" |2G bands
|FMC150-QJIB0: GSM: B2/B3/B5/B8
|-
|FMC150-QKIB0: GSM: B2/B3/B5/B8
|-
| rowspan="2" |4G bands
|FMC150-QJIB0: LTE FDD: B1/B3/B5/B7/B8/B20/B28

|-
|FMC150-QKIB0: LTE FDD: B2/B3/B4/B5/B7/B8/B28/ B66
|-
| rowspan="3" |Data transfer
|LTE: LTE FDD: Max 10Mbps (DL)/Max 5Mbps (UL)
|-
|GSM: GPRS: Max 85.6Kbps (DL)/Max 85.6Kbps (UL)
|}

{{FMB140 Hardware features}}

{{FMB140 Interface features|FMB140=3
}}

{{Template:FMB1 Special features|spec=*Color ribbon non-detachable cable;|sim=}}

{{Template:FMB1 Supply voltage 10 30}}

==Technical features==
 

<table class="nd-othertables" style="width: 40%;">
<tr>
<th style="width: 20%; text-align:center; vertical-align:middle; color: black">Part name</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color: black">Physical specification</th>
</tr>
<tr>
<td style="vertical-align:middle">Navigation indication</td>
<td>LED</td>
</tr>
<tr>
<td style="vertical-align:middle">Modem indication</td>
<td style="vertical-align:middle">LED</td>
</tr>
<tr>
<td style="vertical-align:middle">CAN indication</td>
<td style="vertical-align:middle">LED</td>
</tr>
<tr>
<td style="vertical-align:middle">Socket</td>
<td style="vertical-align:middle">Soldered inner socket</td>
</tr>
<tr>
<td style="vertical-align:middle">USB</td>
<td>Micro USB socket</td>
</tr>
<tr>
<td style="vertical-align:middle">GNSS</td>
<td style="vertical-align:middle">Internal GNSS antenna</td>
</tr>
<tr>
<td style="vertical-align:middle">GSM</td>
<td>Internal GSM antenna</td>
</tr>
</table>
 

<table class="nd-othertables" style="width: 70%;">
<tr>
<th colspan="2" style="width: 70%; text-align:center; vertical-align:middle; color: black">Technical details</th>
</tr>
<tr>
<td style="vertical-align:middle; width: 40%">2 W max. Current consumption at 12 V (Power supply 6...30 V DC) </td>
<td style="vertical-align:middle; width: 30%"> GPRS: average 73.6 mA Nominal: average 25.2 mA GNSS sleep: average 11.6 mA Deep Sleep: average 5.3 mA Online Deep Sleep: average 5.6 mA Ultra Deep Sleep: average 3.5 mA</td>
</tr>
<tr>
<td style="vertical-align:middle">Battery charge current</td>
<td style="vertical-align:middle">Average 140 mA</td>
</tr>
<tr>
<td style="vertical-align:middle">Operating temperature (without battery)</td>
<td style="vertical-align:middle">-40..+85 °C</td>
</tr>
<tr>
<td style="vertical-align:middle">Storage temperature (without battery)</td>
<td style="vertical-align:middle">-40..+85 °C</td>
</tr>
<tr>
<td style="vertical-align:middle">Storage relative humidity</td>
<td>5..95% (no condensation)</td>
</tr>
<tr>
<td style="vertical-align:middle">Device + case + battery weight</td>
<td>55 g</td>
</tr>
</table>
 

Dimension drawing:

[[Image:FMB130 dimension.png|500px|none]]
 

==Technical information about internal battery==

{{Template:FMB Battery information}}

{{Template:FMB1 Electrical characteristics
|input_resistence_din2=38.45
|input_resistence_range1=38.45
|input_resistence_range2=38.45
}}

[[Category:FMC150 Manual|1]]

FMC650 TCA

2025-11-14T01:26:20Z

Wasiqchaudhry:

=Introduction=
The document explains how providers can integrate Teltonika’s TCA approved devices with their platform. Device data sending protocol is still the same with some slight changes made to comply with TMA Level 2 requirements. The purpose of this document is to provide TCA and ASPs the necessary guidance on how to implement the TCA compliant solution with FMC650.

'''Device''': FMC650 
'''Firmware''': 03.00.16.Rev.304_1059 
'''Protocol''': Teltonika [[Codec|Codec8 Extended]] 

=Firmware changelog=
'''Previous firmware''': 03.00.16.Rev.303_1059 
'''New firmware''': 03.00.16.Rev.304_1059 
'''Changelog''': 
* Added fixes where device was sending records every second once the ignition has
been turned off.
* Added fixes where device was generating data at 28th second instead of the
configured 30th (Min Period).
*Added fixes to eliminate record sending delay after vehicles enters or exits the
tunnel.

=Identification of lost GPS Fix=
The base protocol remains the same as of Teltonika’s proprietary [[Codec|'''CODEC 8 EXTENDED''']]. Changes specific to TCA in SPEC ID 1059 are described below.

'''Via longitude & Latitude values''' 
After the device’s GNSS Fix is lost, the device sends the following values as latitude and longitude instead of the last known locat on or 0/0.

'''Latitude''': 0xFFFFFFFF 
'''Longitude''': 0xFFFFFFFF 

The values are not plottable on the map and integrators can identify and discard these values.

'''Via GNSS Status Flag (AVL ID 71)''' 
GNSS Status Flag (AVL ID 71) can be used to identify a lost GNSS Fix. Refer to the table below for more details:
{| class="wikitable"
|+
! rowspan="7" |GNSS Status (71)
!Value
!Status
|-
|0
|GNSS OFF
|-
|1
|GNSS ON, no GPS
|-
|2
|GNSS ON, without fix
|-
|3
|GNSS ON, with fix
|-
|4
|GNSS SLEEP
|-
|5
|GNSS Overcurrent/protect state
|}

As mentioned in the table above, GNSS Fix is only valid when the value for AVL ID 71 is “3”. If the GNSS status value (71) not 3, value of longitude and longitude can be discarded

=Device configuration guide=
Device configuration can be changed according to the described guidelines. Note that any changes should comply with the TCA guidelines.

'''Key''': 

● Must not be changed 
●Can be changed but change should comply with TCA guidelines or as instructed. 
● Can be changed. 
● Any other changes to the config that are not covered below should be consulted with Teltonika & TCA. 

'''Note''': Any changes made to the config must not impact the data acquisition settingsand settings related to base parameters (time (data sending time), longitude, latitude & speed).

==Config sections that can be reconfigured as needed by the ASPs==
[[File:2025-02-28 1.png]] 
 

==Security configuration==

[[File:2025-02-28 2.png]] 
 

==GPRS configuration==
[[File:2025-02-28 3.png]]

==Data Acquisition configuration==
[[File:2025-02-28 4.png]]

==Features & Accelerometers Features configuration==
Scenarios can be activated but '''must''' be set to low priority only. Any eventual data should be disabled.
By default, all the scenarios are disabled.

==IO configuration==
[[File:2025-02-28 5.png]]

==Configuration File==
Base configuration file that has been approved by TCA can be provided by Teltonika via Helpdesk.

===Additional salient guidelines to maintain compliance===
# The following 3 parameters should be discarded by ASP from data received from device or should only be used for internal purposes. TCA’s solution should not have the visibility for it.
## Number of satellites
## HDOP
## PDOP
# All peripherals (RS232/RS485, Video Solutions, Digital I/O, FMS, MobilEye, Tacho, Bluetooth etc.) are disabled* by default. To use any peripherals (including any that are not listed otherwise), approval from TCA and Teltonika is needed. *The only peripheral enabled by default is USB. The interface can be used to load the initial configurations, e.g., APN, server domain & port etc., as per the instructions provided in [[Device configuration guide]].
# External power voltage and Ignition Status is sent with the AVL data and is contained in each packet.
# SD card slot has not been used since internal memory is enough to hold records for up to 6 hours. In case external SD card is needed, approval is required from TCA and Teltonika.
# Device is not password protected by default and can be accessed through USB. ASPs should add keyword protection for serial interface over USB. Refer to [[Security Configuration]] guide.

===Declarations===
#The date and time data collected by the telematics device is within:
## 1 second from UTC when using GNSS signals &
## 10 seconds from UTC when not using GNSS signals for 24 hours.

===FAQs===
'''Q:''' How the Real-Time Clock (RTC) operates and is affected by the internal battery? 

'''A:''' If external power is gone device works from battery without any issues in same manner as with external power supply.

'''Q:''' Clarification on how the internal battery affects timestamp generation and record creation when the device is powered off for several days? 

'''A:''' Internal battery did not affect anything regarding record creation or timestamp. This only depends how log battery will maintain power for device.

'''Q:''' Understanding of how long the device can generate records once the external power source is disconnected and the internal battery is depleted just an estimate will be enough? 

'''A:''' The amount of time the device will work from internal battery depends on the battery health, how often the device saves/sends information to the server, external peripherals connected to the device and the results may also differ depending on firmware used.

For general comparison purpose, and to see what results can be achieved, you can refer to the following internal test results in different modes and sending frequencies:

{| class="wikitable"
|+
!Mode:
!Min Period (data
saving

frequency)
!Send Period (data
sending

frequency)
!Starting
Voltage
!Cut off Voltage
!Time achieved
|-
|Operating
|10 seconds
|60 seconds
|10.1V
|7.0V
|452 min (7 hours 32
minutes)
|-
|Operating
|60 seconds
|60 seconds
|10.1V
|7.0V
|507 min (8 hours 27
minutes)
|-
|Deep Sleep
|12 hours
|12 hours
|10.2V
|8.2V
|5040 min (84 hours 0
minutes)
|-
|Online Deep Sleep
|12 hours
|12 hours
|10.2V
|8.6V
|1440 min (24 hours 0
minutes)
|}

'''Q:''' What happens when the device is turned back on and how it recovers its clock and data saving capabilities? 

'''A:''' When device is turned on after long time it try to sync RTC time with configured source, record generation capabilities depend on configuration.

'''Intellectual property rights'''
The Customer acknowledges that UAB TELTONIKA TELEMATICS shall be the exclusive owner of all intellectual property rights used in connection with the products and/or Services the Customer purchases.

=Atachments=
You can download this informatin about FMC650 TCA in a document, by clicking [[Media:TELTONIKA FMCT650 TCA GUIDELINES 2v4.pdf|here]].

[[Category:FMC650 Manual]]

DualCam Firmware errata

2025-07-24T03:44:52Z

Wasiqchaudhry:

__TOC__

==Firmware Version==

We are always improving our device's performance, stability, and reliability. 
This document describes '''DualCAM platform and FMX125''' devices' firmware improvements, changes, new features implementations as well as current firmware release version.

'''NOTE: Starting from 2025-06-16, our camera firmware has been merged into the FMC650 base firmware with Spec ID 1111.'''

'''To make it visible in the Configurator support, you need to enter a special key.When you open the Configurator, press the key combination Ctrl + Alt + I, then enter the provided key.'''

<pre style="margin-left: 0px;">
E+qh2Nyp3aP7XQZsUr/CxcCC0Xnsj+LPKmKRLsJJYioAAADPA1SQjH4rJsK6oOVY1m8oOi/GttDkvdLnMLVpTwNDKHFKwUbfiEP8uNKdKIXGD4f+bC3iVtJqX9x+8GUpHA/4sidJEpSAO1xinj2MOXQu7lQyrtRzX479iDxQjMeuLMH2r6M7ZD4+5P7vu5cN6uhgXx4RANoUksShK4uLqJg6g6UNboHLsIHfE3eGECDCDrGOhQAEAAAAAAAIix8=
</pre>

'''In the "New key" section, press "Register". After that, the Configurator will recognize the device and the new firmware.'''

[[File:Screenshot_2025-06-30_093721.jpg|frameless]]

'''You only need to enter the code once on the computer where you are using the configurator. If you use a different computer, you will need to enter the code again.'''

==Firmware download for FMC125/FMC225/FMC650==

You can download all necessary firmware by clicking [[Firmware_versions#Video_Solutions|here]].

==Firmware for FMC650==

{| class="wikitable" style="width: 100%;"
|+
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.01.00.Rev.22''' ,'''Spec ID 1111'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2025-06-16}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Iridium SBD transmission improvement.
* Base firmware merge with Spec ID 1111
* Additional network fixes.
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.00.16.Rev.104'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-11-12}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Support DSM FW 2.4.0 added.
* Port tacho border crossing IO.

|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.00.16.Rev.101'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-08-06}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Geofence functionality pictures receiving fix.
* Green Driving pictures receiving fix.
* File transfer modem rebooting state fix.
* Additional verbal information by request/download/upload pictures.
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.00.16.Rev.100'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-06-12}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Port Tacho Border Crossing IO.
* VDO Counter functionality fix.
* Full Base Support
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.00.14.Rev.116'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-04-05}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* '''NEW:''' ADAS support.
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.00.14.Rev.114'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-03-01}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Stable work with DualCam/DashCam.
* '''NEW:''' Two camera support.
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.00.14.Rev.112'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-11-23}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added DualCam/DashCam support for FMC650.
|-
|}

==Firmware for FMC125==

{| class="wikitable" style="width: 100%;"
|+
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''04.00.00.Rev.371'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2025-06-19}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Full base update
* NEW: QT and MEIG modem support
* Network stability improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.29.00.Rev.534'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-07-15}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Full base update
* Port stability related changes
* Metadata version 4 support for DualCam and DashCam
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.29.00.Rev.531'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-02-15}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Full base update
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.13.Rev.663'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-07-31}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Network stability improvements.
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.13.Rev.662'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-06-05}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* DualCam capture buffer loop
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.13.Rev.661'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-03-27}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Only one video download with video priority selected
* Camera state check logic fixed
* DualCam time zone in metadata changed to Unix time (UTC+0)
* Option to select file priority for Dual Cam
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.13.Rev.367'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-11-29}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Metadata duplicate
* Gnss sync issues. Mrg of 03.27.13.Rev.441 meig branch
* Metadata overwritten when 2 or more files queued for upload
* Timestamp drift after long time period in deep sleep
* MEIG modem throws errors and callstacks under heavy load
* SMS request response when video buffer is empty
* Periodic image buffer issues in deep sleep
* MEIG GPRS quality update
* Video buffer stuck after wrong timestamp
* Modem unstable at full DualCam buffer
* Camreq identical metadata issue
* DualCam video trigger max value
* DualCam custom image resolution
* DualCam fw version not available in logs
* SD card format response issue

|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.13.Rev.362'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-06-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* NITZ gives unstable time
* Single side of camera footage is uploaded
* MEIG modem file upload issue
* DualCam base update for MEIG support
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.07.Rev.365'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-03-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Minor improvements
* DualCam metadata timestamp mismatch
* Increased timeout for video data pack request
* CRC calculation mismatch after file upload resume
* Periodic image sending
* Add camera time zone parameter
* Added periodic time check and sync for the camera
* Adjusted DualCam command timeouts
* Added fixes and workarounds for cam command fails
* FPS parameter added to the meta data command
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.07.Rev.361'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-09-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Minor improvements
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.07.Rev.360'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-08-30}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Extended video and image sending configuration
* Added Domain and Port parameters to “camreq” command
* Extended “camreq” response
* Added “camgetver” command
* Fixed timestamp for video meta data
* Improved system stability and fixed general bugs
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.03.Rev.104'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-06-18}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added image sending trigger
* Ability to configure multiple video triggers
* Always enabled DualCam scenario support
* Improved system stability and fixed general bugs
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''03.27.00.Rev.100'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-02-19}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Initial release
|-
|}

==Firmware for DualCam ==
{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |DUALCAM FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''V2.2.3'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-05-20}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added watch dog for camera to restart it self if camera will stuck
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''V2.2.2'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-01-06}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added video buffer pool,repair the write rate of the SD card
* Solved the bug when 35min can not download video
* Changed the logic of FPS setting and switching,the video saves the exact FPS of each video packet in the PTM_FRAME
* Improved the picture and video quality,image edge trimming
* Added flash upgrade mode
* Modified command to get Image quality
* Resolved the problem that the camera restarts after switching the OSD switch
* Optimized setting video frame rate without restarting the camera
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''V1.9.3'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-07-15}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Improved stability and fixes of camera data packets
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''V1.9.2'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-06-02}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed issue with front camera crash if picture size is too large
* Added command to check the camera version
* Improved system stability and fixed general bugs
|-

| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{fw|'''V1.9.0'''}}} 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021- 02-19}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Initial release
|-
|}

[[Category:Teltonika DualCam]]

DSM FAQ

2024-12-12T01:21:49Z

Wasiqchaudhry: /* Frequently asked questions regarding DSM solution */

__TOC__

'''Here you will find answers to the most frequently asked questions about DSM.''' Please check answers here, if you will not find answer then fill the Helpdesk query.

==Frequently asked questions regarding DSM solution==
{| class="wikitable"
! style="background: #0054A6; color: white;" |Question
! style="background: #0054A6; color: white;" |Comments
|-
|What is maximum SD Card capacity?
|The maximum SD card capacity is 256 GB
|-
|Waht is the camera angle degree?
|88 degree
|-
|Recommended device placing location
|A device is recommended to be installed next to A-pillar between the driver face and the top of the dash board.
|-
|Is drowsiness warning working OK when a driver wears sunglasses?
|Yes
|-
|How long it takes to transfer photo to server ?
|About 10 sec
|-
|What is the weight of 1 photo ?
|About 20 Kb
|-
|How long it will take to install DSM with FMC640 into vehicle ?
|Around 3 hours if doing it for the first time.
|-
|Where is recommended DSM camera placing location in vehicle?
|DSM camera is recommended to be attach next to A-pillar
|-
|What is the video length for 128GB ?
|Around 40 hours.
|-
|How can I review video files ?
|By extracting SD card from the device and inserting it into PC. Download the files from the SD card and run them on a video player.
|-
|Will I get photos only from camera functionality (Drowsiness, distraction, yawing) ?
|No, DSM camera has periodic image setting, minimum interval is 60 secs and maximum is 3600 secs.
|-
|Will I get photos if FMC640 is not connected to DSM?
|No, a connection between the FMX6 Series device and DSM is required.
|-
|With what Teltonika devices DSM has integration ?
|FMX6 Series
|-
|How far is DSM working distance?
|80-100 cm
|-
|Is mask detection available ?
|Yes, the DSM camera will notfy if mask is worn.
|-
|What will happen if driver will cover DSM camera ?
|Camera will start making notification sounds until the view is clear.
|-
|Is it possible to connect 2 video solution devices with FMC650 ?
|Yes it is possible to connect 2 video solution devices. Here are the possible combinations for connecting two video solution devices with the FMC650:
DSM + DualCam, DSM + DashCam, DualCam + DashCam, DualCam + DualCam, DashCam + DashCam, ADAS + DSM, ADAS + DashCam, and ADAS + DualCam.
|}
[[Category: DSM]]

DualCam FAQ

2024-05-24T04:54:45Z

Wasiqchaudhry:

'''Here you will find answers to the most frequently asked questions about DualCam.

Please check answers here, if you will not find answer then fill the Helpdesk query.

===<big>Frequently asked questions regarding Dualcam solution</big>===

{| class="wikitable"
|+
! style="background: #0054A6; color: white;" |Question
! style="background: #0054A6; color: white;" |Comments
|-
|What is the best device to use DualCam with?
|Our FMX125 family devices are integrated to work best with DualCam solution, these include [https://wiki.teltonika-gps.com/view/FMC125 FMC125], [https://wiki.teltonika-gps.com/view/FMB125 FMB125] or [https://wiki.teltonika-gps.com/view/FMB225 FMB225] [https://wiki.teltonika-gps.com/view/FMC225 FMC225].
|-
|Firmware to install on FMX125 device for best DualCam support?
|The latest current firmware to use on FMX125 devices is 03.29.00.Rev.530 and latest for DualCam solution is V2.2.3, please see the link for the latest Firmware versions [[DualCam_Firmware_errata|here]]
|-
|Picture quality received is very blurry, what can I do?
|Please visit your configuration settings in RS232/RS485 Tab, in there you should see DualCam selected. With this selection, you should be able to see DualCam Feature Settings with available resolutions. There is a variety of different resolutions available ranging from 160x120 px to 1920x1080 px. Please note that selecting highest possible resolution will make a bigger file which will take longer to upload and consume more data compared to 1280x720 px size. We advice 1280x720 px as best choice.
|-
| MicroSD card is not detected, how to fix this?
|It is possible that your microSD card is formated under different file system, please format the card on the computer with the FAT32 file system and then try re-inserting the card again.
|-
|How can I quickly check if my camera is recording or whether it is in working order?
|It is advisable to test the camera upon arrival with our videoplayer.exe software [https://wiki.teltonika-gps.com/view/Data_image/video_review#How_to_read_camera_data_from_SD_card here], the link to download it can be found on our wiki page. Simply download and click on .exe file extension and the program will open. In there, please follow the following steps as described in our wiki page here.
|-
|My FMX device does not send photo to server even with camreq:1,1 command, received packet is empty. What can I do?
| Camera image sending is not being sent as AVL data, it requires special protocol from the server side to be implemented. More information can be found on our wiki page here.
|-
|Can I configure my DualCAM over RS485 input for faster data transfer?
|Our DualCAM solution only works with RS232 input for more efficient development and lower power consumption.
|-
|I do not see DualCam as selection on my RS232 input, what to do?
| Please ensure that the configurator and firmware of your device is at the recommended version. If you are not sure which version of configurator you need, please contact your sales manager or create Helpdesk query.
|-
|Why do I not see time and date on my photos and videos as seen in some other camera brands?
|This function is toggle-able and in order to turn it on, please go to your RS232/RS482 tab on your Configurator. In there please navigate to Camera Feature Settings and enable OCD Display. This feature will allow your camera to display date and time on pictures and videos.
|-
|I am not able to request photos to my Wialon server, the command is either unresponsive or shows me invalid command error.
|We have created a guide which you can follow step by step in order to set up your camera to Wialon servers. It is advisable to read through all of it as the there are specific steps to be taken in order to receive the photo, you can read more [[Wialon+DUAL CAM solution|here]].
|-
|There are further issues with my Wialon server, who to turn to for assistance and help?
|For any server-related issues please contact Wialon directly on support@gurtam.com.
|-
| What is the IP Rating of our Dual camera?
|The IP rating of Dualcam is IP41.
|-
|Is DualCam compatible with FMC225?
|Dualcam is compatible with FMC225. As [https://wiki.teltonika-gps.com/view/FMC225 FMC225] is developed on the existing platform, it keeps all the functionalities from [https://wiki.teltonika-gps.com/view/FMC125 FMC125].
|-
|Having configured the device when activating DIN1 to take an image (Front & Rear), and additionally capture a video (5 before & 5 after), which element will be sent first, we get only the image but not the video.
|The first item to be addressed will be the photo, as it has a higher priority. This issue has been resolved in the new firmware version 03.27.13.Rev:661, where you can now select the priority for either video or photo.
|-
|Is it possible to configure the device to capture an image from either the front or rear camera exclusively using the image sending trigger?
|No, the device cannot be configured to capture an image from a single camera (either front or rear) using the image sending trigger. When the image sending trigger is activated, the device will send photos from both the front and rear cameras. Camera selection is only available for periodic image sending.
|-
|In case there is no coverage and an on state is generated (DIN1 = 1), the images and videos are stored for later sending? This is not happening.
|It will be stored in the buffer, and if there is no server connection for a long time, it will be removed. Only video can be requested again using a timestamp.
|-
|Using the Codec12 protocol it is possible to send a packet to request a multimedia capture to the equipment (only the requests by sms are working).
|Yes, it is possible, some platforms like Wialon using the GPRS command to ask for a video.
|-
|Our configuration on the Teltonika models regarding communication is using Codec 8 Extended over UDP, the transmission of multimedia data is by TCP, in case we want to send a request (OTA) it must be sent to the UDP or TCP socket. Both communication methods can coexist without problems in the device.
|It must be sent via TCP. We cannot guarantee that sending it via UDP will work, so only TCP is supported.
|-
|Dual Cam, does it record video constantly on the SD and send it on request, or does it only record when requested or by a trigger?
|It records video constantly and after a request, it cut off the video that you request.
|-
|What is the power consumption of Dual Cam in full operation?
|220mA night mode can reach up to 280mA
|-
|For the request of a video (by sms), using the command 'camreq:0,2,1684865884,5', understanding that 1684865884 is Unix time, if you want to take the video from the moment the request arrives at the Teltonika device is it possible? what happens if you put a value in Unix time lower than the current time, or a later one, for example, half an hour ahead of the present time?
|If the camera was working before the request arrived at the device, then it is possible. The camera can store up to 40 hours of video, so you should receive it if you request a video within this timeframe. However, please note that the request must be made when the camera was operational. If you request video from a time when the camera was powered off, you will not receive any video.
|-
|The requests (by sms) generate an answer, and in all of them appears the sentence 'Another footage upload is already in progress', even when we have not made another request.
|It is possible that the device is sending a video or attempting to send another file. It is better to have a LOG file that shows when you sent an SMS and what happens in the device when the request arrives.
|}

[[Category:Teltonika DualCam]]

Iridium Edge Firmware errata

2024-03-27T05:47:13Z

Wasiqchaudhry: Link for Firmware update for FMX125

__TOC__

==Firmware Version==

We are always improving our device's performance, stability, and reliability. 
This document describes firmware improvements, changes, new features implementations as well as current firmware release version.

==Firmware download for FMX125==

Link: [https://drive.teltonika.lt/f/748d0a59de274545abef/?dl=1 Firmware]

==Firmware errata==

===Firmware errata for FMX125===

{| class="wikitable" style="width: 100%;"
|+
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.29.00.Rev.720'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2024-02-20}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Full base update
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.06.Rev.323'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-04-04}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*SBD data usage limit reset on 11th day
*Periodic record generation when iridium turned off
*Panic record generation when buffer is full
*Iridium Edge accessory detection (rs232 accesory 7)
*Panic records generated when Io turned off
*Din/dout byte invalid data
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.104'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-11-29}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Added SBD message buffer limit of 300 messages
*Fixed part of SBD records that were of empty size
*Fixed Iridium initialization
*Fixed incorrect timestamp from SBD Buffer
*Added ability to use SBD buffer in transmitting
*Added ability to generate SBD records with AVL id
*Added ability to read messages from SBD Buffer
*Added ability to save messages to SBD Buffer
*Fixed Iridium not detecting GSM connection
*Fixed Iridium communication issues
*Fixed incorrect data usage calculation
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.100'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-06-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added data usage limit for sending via Iridium
* Added Iridium data sending logic
* Added Iridium FSM for parsing iridium edge terminal messages
* Added Irdium RS232 support
* Added SBD Record format
* Added implementation of configuration parameters for Iridium Edge control
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-03-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed Lipo battery max voltage limit increased
* Fixed no SMS response to short number
* Fixed parameter 11712 cannot be configured with value 10
* Added cpureset command to only work with external power
* Added iButton file open/close traces
* Fixed FMP100 LED constantly on after fw update
* Added road sign CAN elements
* Fixed security states P2 bitfield map fix
* Fixed Jamming records saved as low priority
* Fixed Fluid Market GGPS command
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.03.Rev.01'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-09-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Initial release
|-
|}

===Firmware errata for FMX640/641/650===
{| class="wikitable" style="width: 100%;"
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.00.13.Rev.05''' ( Firmware release version for {{{model|FMX650}}})
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2023-03-03}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Base FW.
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.24.Rev.00''' (Latest firmware release version for {{{model|FMX640}}})
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-11-29}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Improvements for manufacturing process. (No any functionality improvements made)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.18.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-12-23
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added advanced BLE Advertisement data are not send on server completely.
* Fixed no ID [1077]: 4 event generated after "Time TO Clear ID" timer ran out.
* Fixed event ID [1077]: 4 generation and DOUT setting to '1' on key clear timer exparation code added.
* Fixed FMB640 DOUTs bug fix, when DOUTs turns on for a moment after startup.
* Fixed CAN2 bus normal mode is not working.
* Added no BT changes and version/mod fix.
* Fixed after DriverAuthorization device does not send SMS bug fix.
* Added Contipressure new parameters.
* Fixed device reset after configuration saving
* Added Iridium Edge support Fixed AVL unnecessary records after restart.
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.17.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-05-24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed FMC640 Improve gprs context opening.
* Fixed FMC640 Improve new gprs configuration for BG96.
* Added LVCAN adapter compatibility over RS232 functionality.
* Fixed periodic AVL packet sending (when connecting to DDD server).
* Fixed RS232 Buffered long message when SD storage is used
* Added periodic total odometer value save (if moving).
* Added total odometer value save (on stop).
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.16.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-05-24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added allow not available (3,7) value for tachoraph driver.id IO.
* Fixed scenarios are saving records even if not enabled
* Fixed unstable additional beacons
* Fixed FMC64 stability (try socket connection once)
* Fixed jamming detection for FMC64 devices
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.15.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-04-15
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Initial release
|-
|}
[[Category: Iridium Edge]]