Teltonika Telematics Wiki - User contributions [en]

File:DS-FTC164.pdf

2026-04-17T12:39:10Z

Martynas.juozaitis:

FTM164

2026-04-07T07:23:27Z

Martynas.juozaitis: Created page with "{{Template:FTX Main|model=FTM164}}"

File:FTM164 side.png

2026-04-07T07:23:15Z

Martynas.juozaitis:

FTX164 getting started

2026-01-30T11:37:39Z

Martynas.juozaitis: Dimensions

== 1. Preparing the Telematics configuration tool ==
1. First step is to set up Your workstation to be able to use Telematics configuration tool (TCT).
This can be done by following the guidelines from our Wiki:
https://wiki.teltonika-gps.com/view/Getting_started_with_TCT

2. Once You have successfully installed and launched TCT, a special user key must be added, in order to gain access to FTX164 devices.
In the top right corner of the TCT, click on the cog to open the Settings menu. Click on the “User keys” option.
[[File:FTX164_COG.png]]
[[File:FTX164_User_keys.png]]

3. Copy the following User key from start to finish:
BEGIN TCT KEY
description: For testing FTC164 with development firmware
type: ExpFWKey
key: a3869a45-009e-44c7-b7de-8f3735c997e8
expires: 2026-10-09
signature: v1|KAOELk+DNGqxxf2cKf2MCLq3wBXIDKsBsNV/HbDPkESxzf+VRWaVwChjt5Qkw81ScT/FiRF1ls0SKGnV1CZ3f1Fdpr+hAKhcNn8HAsiFxWzJRfqvLkXo4Gp+K554tI5H9erDqZasqNXob9AN65/BM3oAHFUDdi2CcR0D6vn6YVvLVbn+BprNlQOXwUuyDMzH6R7p7IHFlaI2+J6S06bLDebkO/0jPjrplTyEyiPP5xK1zAIXXrw87fw0vttGo0pkFSb0YaUoSNZuCT7PGNBuJDmEf7NWvM1jIOPLUMwQ2CBi5Azq8dj0OA8B9WgyhqYi8ftX1vHc7DtpAepfrYFL5Q==
END TCT KEY

Paste the User key into the “Add new key” field. Click on the “Add key” button.
[[File:FTX164_User_Key2.png]]

4. Restart the Telematics configuration tool. A new window will open.
Select “FTC164 with development firmware” and click “Apply”.

[[File:FTX164_Development_FW2.png]]

Now You’re ready to use the TCT!

== 2. Device preparation ==

[[File:Set up FTX164.jpg]]

'''Note: step #3 should only be completed once the device is configured.
'''
== 3. Device configuration ==

=== Configure Your APN and Server settings ===
in the “Mobile network” tab, You will find the following parameters which must be configured, in order to receive data to Your server: [[File:FTX164_Mobile_Network.png]]

[[File:FTX164_Server_Settings.png]]

=== Power off sleep mode with scheduled wake ups ===

One of the main goals during the development of this device was to ensure extended operation when working from the internal battery. This has been achieved not only with the use of a larger battery with a capacity of 2600mAh, but also by implementing new sleep mode logic that significantly reduces power consumption while in power off sleep.

Power off sleep used together with scheduled wake ups allows for extremely low power consumption in sleep, while maintaining the capability of the device to wake up based on pre-defined times.

Here is how You can enable these two features:

[[File:FTX164_P0S.jpg]]

[[File:FTX164 P0S22.png]]

During our internal current consumption tests, the FTX164 was consuming roughly 200uA per hour while it was in the power off sleep state, working only from the internal battery:

{| class="wikitable"
|style="background: #0054A6; color:white" |'''Sleep mode'''
|style="background: #0054A6; color:white" |'''Current consumption (mA)'''
|-
| rowspan="2" |Online deep sleep
|@12V Online Deep sleep: 10,34
|-
|@4V Online deep sleep: 24,36
|-
| rowspan="2" |Deep sleep
|@12V Deep sleep: 2,56
|-
|@4V Deep sleep: 6,81
|-
| rowspan="3" |Power off sleep
|@12V Power off sleep: 0,28
|-
|@4V Power off sleep: 0,19
|}

More information about sleep modes, such as, sleep exit/enter conditions, list of modules which are disabled during sleep modes can be found here https://wiki.teltonika-gps.com/view/FTC927_System#Power_Saving_settings.

=== Software defined pins ===
One of the key innovations introduced with the new hardware and firmware architecture is Software-Defined Pins (SDP). While this functionality is still limited in the current engineering sample, we encourage giving it a try!
The SDP feature allows flexible reconfiguration of pin assignments. At this stage, SDP configuration can only be performed through TCT, with the device physically connected. However remote configuration capabilities will be introduced in a future release.

[[File:FTX164_SDP11.png]]
[[File:FTX164_SDP22.png]]

=== Additional note regarding configuration ===

The FTX164 comes with many other features, which you will see in the TCT. However, as this is an engineering sample which comes with an ''evaluation'' firmware, keep in mind that some of the features visible in TCT, might not yet be fully tested, documented or have the latest fixes ''in this specific firmware version.''

== Known limitations ==

*Digital Ground sense feature is not available on these engineering samples.

*On the firmware versions 3.7.rc-13 and 3.7.rc-15 , the internal battery ''percentage'' IO element will not show the accurate percentage of the internal battery. Instead, please use internal battery voltage IO element, which can be used to calculate the real capacity of the internal battery using the below provided table:

[[File:Battery discharge table FTX164.jpg]]

== Basic Characteristics ==

<table class="nd-othertables_2" style="width:90%;">
<tr>
<th rowspan="1" style="width:30%; vertical-align: middle; text-align: left;">Module</th>
<th rowspan="1" style="width:60%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Name</th>
<td style="vertical-align: middle; text-align: left; ">FTC164-MEAB0<br>FTC164-MDAB0
FTM164-Q3AB0<br>
FTM164-Q2AB0<br>
FTM164-Q5AB0<br>
</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Technology</th>
<td style="vertical-align: middle; text-align: left; ">FTC164-MDAB0 -LTE CAT 1/GSM/GPRS/GNSS
FTC164-MEAB0 -LTE CAT 1/GSM/GPRS/GNSS

FTM164-Q2AB0 LTE CAT M1/GSM/GPRS/GNSS

FTM164-Q3AB0 LTE CAT M1/ CAT NB2/GSM/GPRS/GNSS

FTM164-Q5AB0 LTE CAT M1/CAT NB2/GNSS
</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">GNSS</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">GNSS</th>
<td style="vertical-align: middle; text-align: left; ">GPS, GLONASS, GALILEO, BEIDOU</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Receiver</th>
<td style="vertical-align: middle; text-align: left; ">135 tracking/acquisition channels</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Tracking sensitivity</th>
<td style="vertical-align: middle; text-align: left; ">-165 dBm</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Position Accuracy</th>
<td style="vertical-align: middle; text-align: left; ">< 1.8 m CEP</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Velocity Accuracy</th>
<td style="vertical-align: middle; text-align: left; ">< 0.1 m/s (within +/- 15% error)</td>
</tr>

<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Cellular</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th></tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">2G bands</th>
<td style="vertical-align: middle; text-align: left; ">'''FTC164-MDAB0 -''' GSM: B2/B3/B5/B8
'''FTC164-MEAB0''' - GSM: B2/B3/B5/B8
'''FTM164-Q3AB0''' - GSM: B2/B3/B5/B8</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">4G bands</th>
<td style="vertical-align: middle; text-align: left; "> '''FTC164-MDAB0 -''' LTE FDD (CAT 1): B1/B3/B5/B7/B8/B20/B28
'''FTC164-MEAB0''' - LTE FDD (CAT 1): B1/B3/B5/B7/B8/B28/B66<br>'''FTM164-Q2AB0''' - CAT M1 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
'''FTM164-Q3AB0''' - CAT M1 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
CAT NB2 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85<br>
'''FTM164-Q5AB0''' - CAT M1 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
CAT NB2 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85
</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Data transfer</th>
<td style="vertical-align: middle; text-align: left; ">LTE FDD (CAT 1): Max. 10 Mbps (DL) / Max. 5 Mbps (UL)
GSM (GPRS): Max. 85.6 Kbps (DL) / Max. 85.6 Kbps (UL)
LTE CAT M1: LTE: Max. 588Kbps (DL)/Max.1119Kbps (UL)
GPRS: Max. 107Kbps (DL)/Max. 85.6Kbps (UL)"
</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Transmit power</th>
<td style="vertical-align: middle; text-align: left; ">Class 5 for GSM850/900: 30±5dBM <br> Class 3 for GSM1800/1900: 29±5dBM <br>Class 3 for LTE-FDD: 26±5dBM </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Data support</th>
<td style="vertical-align: middle; text-align: left; ">SMS (TEXT, PDU), Network protocols (TCP, UDP)</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Power</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Input voltage range</th>
<td style="vertical-align: middle; text-align: left; ">8- 32 V DC</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Back-up battery</th>
<td style="vertical-align: middle; text-align: left; ">2600 mAh Li-Ion battery, 3.7 V </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Internal fuse</th>
<td style="vertical-align: middle; text-align: left; ">3A, 125V</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Power Consumption</th>
<td style="vertical-align: middle; text-align: left; ">TBA </td>
</tr><tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Interface</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Digital Inputs</th>
<td style="vertical-align: middle; text-align: left; ">5 (configurable)</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Digital Outputs</th>
<td style="vertical-align: middle; text-align: left; ">4</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Analog Inputs</th>
<td style="vertical-align: middle; text-align: left; ">5 (configurable)</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">GNSS antenna</th>
<td style="vertical-align: middle; text-align: left; ">Internal High Gain </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">GSM antenna</th>
<td style="vertical-align: middle; text-align: left; ">Internal High Gain </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">USB</th>
<td style="vertical-align: middle; text-align: left; ">2.0 USB Type-C</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">LED indication</th>
<td style="vertical-align: middle; text-align: left; ">2 status LED lights</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">SIM</th>
<td style="vertical-align: middle; text-align: left; ">Nano-SIM</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Memory</th>
<td style="vertical-align: middle; text-align: left; ">NAND 1Gbit</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Physical Specification</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Dimensions</th>
<td style="vertical-align: middle; text-align: left; ">87.75 x 106.40 x 29.70 mm </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Weight</th>
<td style="vertical-align: middle; text-align: left; ">6-</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Operating Environment</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Operating temperature (without battery)</th>
<td style="vertical-align: middle; text-align: left; ">-30°C to +80 °C</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Storage temperature (without battery)</th>
<td style="vertical-align: middle; text-align: left; ">-40 °C to +85 °C</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Operating temperature (with battery)</th>
<td style="vertical-align: middle; text-align: left; ">'''0 °C to +40 °C'''</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Storage temperature (with battery)</th>
<td style="vertical-align: middle; text-align: left; ">-20 °C to +60 °C</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Operating humidity</th>
<td style="vertical-align: middle; text-align: left; ">5% to 95% non-condensing</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Ingress protection rating</th>
<td style="vertical-align: middle; text-align: left; ">IP69K</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Battery storage
conditions</th>
<td style="vertical-align: middle; text-align: left; ">-10 °C to +50 °C for 1 month<br> -10 °C to +35 °C for 3 months<br> 0 °C to +30 °C for 1 year </td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Data Codec</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Codec support</th>
<td style="vertical-align: middle; text-align: left; ">[https://wiki.teltonika-gps.com/view/Codec#Codec_8_Extended Codec 8 Extended]</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Features</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Sensors</th>
<td style="vertical-align: middle; text-align: left; ">Accelerometer</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Scenarios</th>
<td style="vertical-align: middle; text-align: left; ">Crash Detection, Private/Business mode, overspeeding, Trip, Odometer, Eco driving, Excesive idling, Network jamming detection, immobilizer, Unplug detection, Auto Geofence, Manual geofence, Towing detection, Static navigation, Custom Scenarios, software defined pins, </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Sleep modes</th>
<td style="vertical-align: middle; text-align: left; ">[https://wiki.teltonika-gps.com/view/FTC305_Sleep_modes Online sleep, Deep sleep, Power off sleep]</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Configuration and firmware update</th>
<td style="vertical-align: middle; text-align: left; ">[https://wiki.teltonika-gps.com/view/FOTA_WEB FOTA WEB], [https://wiki.teltonika-gps.com/view/Telematics_Configuration_Tool_(TCT) Telematics Configuration Tool (TCT)]</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">SMS</th>
<td style="vertical-align: middle; text-align: left; ">Configuration, DOUT control, Debug</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">GPRS commands</th>
<td style="vertical-align: middle; text-align: left; ">Configuration, DOUT control, Debug</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Time Synchronization</th>
<td style="vertical-align: middle; text-align: left; ">GNSS, NTP, NITZ</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Ignition detection</th>
<td style="vertical-align: middle; text-align: left; ">Digital Input 1, Accelerometer, External Power Voltage</td>
</tr>
</table>

== Help ==

If You have faced issues during the testing of Your FTX164 device, please create a helpdesk ticket and include the following information:

1. Detailed description of the issue You've encountered, how often and when it occurs.

2. IMEI of Your device.

3. Mounting and/or wiring photos (ideally)

File:DS-FTM134.pdf

2026-01-20T09:11:48Z

Martynas.juozaitis:

File:DS-FTC134.pdf

2025-12-29T11:01:32Z

Martynas.juozaitis:

File:FTC134 side.png

2025-12-29T09:24:42Z

Martynas.juozaitis: Martynas.juozaitis uploaded a new version of File:FTC134 side.png

FTX164 getting started

2025-12-03T14:36:04Z

Martynas.juozaitis:

== 1. Preparing the Telematics configuration tool ==
1. First step is to set up Your workstation to be able to use Telematics configuration tool (TCT).
This can be done by following the guidelines from our Wiki:
https://wiki.teltonika-gps.com/view/Getting_started_with_TCT

2. Once You have successfully installed and launched TCT, a special user key must be added, in order to gain access to FTX164 devices.
In the top right corner of the TCT, click on the cog to open the Settings menu. Click on the “User keys” option.
[[File:FTX164_COG.png]]
[[File:FTX164_User_keys.png]]

3. Copy the following User key from start to finish:
BEGIN TCT KEY
description: For testing FTC164 with development firmware
type: ExpFWKey
key: a3869a45-009e-44c7-b7de-8f3735c997e8
expires: 2026-10-09
signature: v1|KAOELk+DNGqxxf2cKf2MCLq3wBXIDKsBsNV/HbDPkESxzf+VRWaVwChjt5Qkw81ScT/FiRF1ls0SKGnV1CZ3f1Fdpr+hAKhcNn8HAsiFxWzJRfqvLkXo4Gp+K554tI5H9erDqZasqNXob9AN65/BM3oAHFUDdi2CcR0D6vn6YVvLVbn+BprNlQOXwUuyDMzH6R7p7IHFlaI2+J6S06bLDebkO/0jPjrplTyEyiPP5xK1zAIXXrw87fw0vttGo0pkFSb0YaUoSNZuCT7PGNBuJDmEf7NWvM1jIOPLUMwQ2CBi5Azq8dj0OA8B9WgyhqYi8ftX1vHc7DtpAepfrYFL5Q==
END TCT KEY

Paste the User key into the “Add new key” field. Click on the “Add key” button.
[[File:FTX164_User_Key2.png]]

4. Restart the Telematics configuration tool. A new window will open.
Select “FTC164 with development firmware” and click “Apply”.

[[File:FTX164_Development_FW2.png]]

Now You’re ready to use the TCT!

== 2. Device preparation ==

[[File:Set up FTX164.jpg]]

'''Note: step #3 should only be completed once the device is configured.
'''
== 3. Device configuration ==

=== Configure Your APN and Server settings ===
in the “Mobile network” tab, You will find the following parameters which must be configured, in order to receive data to Your server: [[File:FTX164_Mobile_Network.png]]

[[File:FTX164_Server_Settings.png]]

=== Power off sleep mode with scheduled wake ups ===

One of the main goals during the development of this device was to ensure extended operation when working from the internal battery. This has been achieved not only with the use of a larger battery with a capacity of 2600mAh, but also by implementing new sleep mode logic that significantly reduces power consumption while in power off sleep.

Power off sleep used together with scheduled wake ups allows for extremely low power consumption in sleep, while maintaining the capability of the device to wake up based on pre-defined times.

Here is how You can enable these two features:

[[File:FTX164_P0S.jpg]]

[[File:FTX164 P0S22.png]]

During our internal current consumption tests, the FTX164 was consuming roughly 200uA per hour while it was in the power off sleep state, working only from the internal battery:

{| class="wikitable"
|style="background: #0054A6; color:white" |'''Sleep mode'''
|style="background: #0054A6; color:white" |'''Current consumption (mA)'''
|-
| rowspan="2" |Online deep sleep
|@12V Online Deep sleep: 10,34
|-
|@4V Online deep sleep: 24,36
|-
| rowspan="2" |Deep sleep
|@12V Deep sleep: 2,56
|-
|@4V Deep sleep: 6,81
|-
| rowspan="3" |Power off sleep
|@12V Power off sleep: 0,28
|-
|@4V Power off sleep: 0,19
|}

More information about sleep modes, such as, sleep exit/enter conditions, list of modules which are disabled during sleep modes can be found here https://wiki.teltonika-gps.com/view/FTC927_System#Power_Saving_settings.

=== Software defined pins ===
One of the key innovations introduced with the new hardware and firmware architecture is Software-Defined Pins (SDP). While this functionality is still limited in the current engineering sample, we encourage giving it a try!
The SDP feature allows flexible reconfiguration of pin assignments. At this stage, SDP configuration can only be performed through TCT, with the device physically connected. However remote configuration capabilities will be introduced in a future release.

[[File:FTX164_SDP11.png]]
[[File:FTX164_SDP22.png]]

=== Additional note regarding configuration ===

The FTX164 comes with many other features, which you will see in the TCT. However, as this is an engineering sample which comes with an ''evaluation'' firmware, keep in mind that some of the features visible in TCT, might not yet be fully tested, documented or have the latest fixes ''in this specific firmware version.''

== Known limitations ==

*Digital Ground sense feature is not available on these engineering samples.

*On the firmware versions 3.7.rc-13 and 3.7.rc-15 , the internal battery ''percentage'' IO element will not show the accurate percentage of the internal battery. Instead, please use internal battery voltage IO element, which can be used to calculate the real capacity of the internal battery using the below provided table:

[[File:Battery discharge table FTX164.jpg]]

== Basic Characteristics ==

<table class="nd-othertables_2" style="width:90%;">
<tr>
<th rowspan="1" style="width:30%; vertical-align: middle; text-align: left;">Module</th>
<th rowspan="1" style="width:60%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Name</th>
<td style="vertical-align: middle; text-align: left; ">FTC164-MEAB0<br>FTC164-MDAB0
FTM164-Q3AB0<br>
FTM164-Q2AB0<br>
FTM164-Q5AB0<br>
</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Technology</th>
<td style="vertical-align: middle; text-align: left; ">FTC164-MDAB0 -LTE CAT 1/GSM/GPRS/GNSS
FTC164-MEAB0 -LTE CAT 1/GSM/GPRS/GNSS

FTM164-Q2AB0 LTE CAT M1/GSM/GPRS/GNSS

FTM164-Q3AB0 LTE CAT M1/ CAT NB2/GSM/GPRS/GNSS

FTM164-Q5AB0 LTE CAT M1/CAT NB2/GNSS
</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">GNSS</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">GNSS</th>
<td style="vertical-align: middle; text-align: left; ">GPS, GLONASS, GALILEO, BEIDOU</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Receiver</th>
<td style="vertical-align: middle; text-align: left; ">135 tracking/acquisition channels</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Tracking sensitivity</th>
<td style="vertical-align: middle; text-align: left; ">-165 dBm</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Position Accuracy</th>
<td style="vertical-align: middle; text-align: left; ">< 1.8 m CEP</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Velocity Accuracy</th>
<td style="vertical-align: middle; text-align: left; ">< 0.1 m/s (within +/- 15% error)</td>
</tr>

<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Cellular</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th></tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">2G bands</th>
<td style="vertical-align: middle; text-align: left; ">'''FTC164-MDAB0 -''' GSM: B2/B3/B5/B8
'''FTC164-MEAB0''' - GSM: B2/B3/B5/B8
'''FTM164-Q3AB0''' - GSM: B2/B3/B5/B8</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">4G bands</th>
<td style="vertical-align: middle; text-align: left; "> '''FTC164-MDAB0 -''' LTE FDD (CAT 1): B1/B3/B5/B7/B8/B20/B28
'''FTC164-MEAB0''' - LTE FDD (CAT 1): B1/B3/B5/B7/B8/B28/B66<br>'''FTM164-Q2AB0''' - CAT M1 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
'''FTM164-Q3AB0''' - CAT M1 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
CAT NB2 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85<br>
'''FTM164-Q5AB0''' - CAT M1 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85
CAT NB2 LTE-FDD: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85
</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Data transfer</th>
<td style="vertical-align: middle; text-align: left; ">LTE FDD (CAT 1): Max. 10 Mbps (DL) / Max. 5 Mbps (UL)
GSM (GPRS): Max. 85.6 Kbps (DL) / Max. 85.6 Kbps (UL)
LTE CAT M1: LTE: Max. 588Kbps (DL)/Max.1119Kbps (UL)
GPRS: Max. 107Kbps (DL)/Max. 85.6Kbps (UL)"
</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Transmit power</th>
<td style="vertical-align: middle; text-align: left; ">Class 5 for GSM850/900: 30±5dBM <br> Class 3 for GSM1800/1900: 29±5dBM <br>Class 3 for LTE-FDD: 26±5dBM </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Data support</th>
<td style="vertical-align: middle; text-align: left; ">SMS (TEXT, PDU), Network protocols (TCP, UDP)</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Power</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Input voltage range</th>
<td style="vertical-align: middle; text-align: left; ">8- 32 V DC</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Back-up battery</th>
<td style="vertical-align: middle; text-align: left; ">2600 mAh Li-Ion battery, 3.7 V </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Internal fuse</th>
<td style="vertical-align: middle; text-align: left; ">3A, 125V</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Power Consumption</th>
<td style="vertical-align: middle; text-align: left; ">TBA </td>
</tr><tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Interface</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Digital Inputs</th>
<td style="vertical-align: middle; text-align: left; ">5 (configurable)</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Digital Outputs</th>
<td style="vertical-align: middle; text-align: left; ">4</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Analog Inputs</th>
<td style="vertical-align: middle; text-align: left; ">5 (configurable)</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">GNSS antenna</th>
<td style="vertical-align: middle; text-align: left; ">Internal High Gain </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">GSM antenna</th>
<td style="vertical-align: middle; text-align: left; ">Internal High Gain </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">USB</th>
<td style="vertical-align: middle; text-align: left; ">2.0 USB Type-C</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">LED indication</th>
<td style="vertical-align: middle; text-align: left; ">2 status LED lights</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">SIM</th>
<td style="vertical-align: middle; text-align: left; ">Nano-SIM</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Memory</th>
<td style="vertical-align: middle; text-align: left; ">NAND 1Gbit</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Physical Specification</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Dimensions</th>
<td style="vertical-align: middle; text-align: left; ">77 x 63 x 21.5 mm (L x W x H)</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Weight</th>
<td style="vertical-align: middle; text-align: left; ">6-</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Operating Environment</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Operating temperature (without battery)</th>
<td style="vertical-align: middle; text-align: left; ">-30°C to +80 °C</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Storage temperature (without battery)</th>
<td style="vertical-align: middle; text-align: left; ">-40 °C to +85 °C</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Operating temperature (with battery)</th>
<td style="vertical-align: middle; text-align: left; ">'''0 °C to +40 °C'''</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Storage temperature (with battery)</th>
<td style="vertical-align: middle; text-align: left; ">-20 °C to +60 °C</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Operating humidity</th>
<td style="vertical-align: middle; text-align: left; ">5% to 95% non-condensing</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Ingress protection rating</th>
<td style="vertical-align: middle; text-align: left; ">IP69K</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Battery storage
conditions</th>
<td style="vertical-align: middle; text-align: left; ">-10 °C to +50 °C for 1 month<br> -10 °C to +35 °C for 3 months<br> 0 °C to +30 °C for 1 year </td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Data Codec</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Codec support</th>
<td style="vertical-align: middle; text-align: left; ">[https://wiki.teltonika-gps.com/view/Codec#Codec_8_Extended Codec 8 Extended]</td>
</tr>
<tr>
<th rowspan="1" style="width:15%; vertical-align: middle; text-align: left;">Features</th>
<th rowspan="1" style="width:35%; vertical-align: middle; text-align: left;"></th>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Sensors</th>
<td style="vertical-align: middle; text-align: left; ">Accelerometer</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Scenarios</th>
<td style="vertical-align: middle; text-align: left; ">Crash Detection, Private/Business mode, overspeeding, Trip, Odometer, Eco driving, Excesive idling, Network jamming detection, immobilizer, Unplug detection, Auto Geofence, Manual geofence, Towing detection, Static navigation, Custom Scenarios, software defined pins, </td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Sleep modes</th>
<td style="vertical-align: middle; text-align: left; ">[https://wiki.teltonika-gps.com/view/FTC305_Sleep_modes Online sleep, Deep sleep, Power off sleep]</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Configuration and firmware update</th>
<td style="vertical-align: middle; text-align: left; ">[https://wiki.teltonika-gps.com/view/FOTA_WEB FOTA WEB], [https://wiki.teltonika-gps.com/view/Telematics_Configuration_Tool_(TCT) Telematics Configuration Tool (TCT)]</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">SMS</th>
<td style="vertical-align: middle; text-align: left; ">Configuration, DOUT control, Debug</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">GPRS commands</th>
<td style="vertical-align: middle; text-align: left; ">Configuration, DOUT control, Debug</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Time Synchronization</th>
<td style="vertical-align: middle; text-align: left; ">GNSS, NTP, NITZ</td>
</tr>
<tr>
<th style="border-bottom: 1px solid #E8E8E8; vertical-align: middle; text-align: left; color:black">Ignition detection</th>
<td style="vertical-align: middle; text-align: left; ">Digital Input 1, Accelerometer, External Power Voltage</td>
</tr>
</table>

== Help ==

If You have faced issues during the testing of Your FTX164 device, please create a helpdesk ticket and include the following information:

1. Detailed description of the issue You've encountered, how often and when it occurs.

2. IMEI of Your device.

3. Mounting and/or wiring photos (ideally)

File:QM-FTM134.pdf

2025-12-03T14:05:29Z

Martynas.juozaitis:

2025-12-01T14:14:17Z

Martynas.juozaitis:

FTX164 getting started

2025-12-01T13:52:00Z

Martynas.juozaitis:

2025-12-01T13:30:11Z

Martynas.juozaitis:

File:FTX164 User Key2.png

2025-12-01T13:28:42Z

Martynas.juozaitis:

File:FTX164 User keys.png

2025-12-01T13:28:09Z

Martynas.juozaitis:

File:FTX164 COG.png

2025-12-01T13:27:10Z

Martynas.juozaitis:

FTX164 getting started

2025-12-01T13:20:19Z

Martynas.juozaitis:

This is the page where clients given engineering samples will be pointed to via QR code

== 1. Preparing the Telematics configuration tool ==
First step is to set up Your workstation to be able to use Telematics configuration tool (TCT).
This can be done by following the guidelines from our Wiki:
https://wiki.teltonika-gps.com/view/Getting_started_with_TCT

Once You have successfully installed and launched TCT, a special user key must be added, in order to gain access to FTX164 devices.

In the top right corner of the TCT, click on the cog to open the Settings menu. Click on the “User keys” option.

In the archive provided to You by Your sales manager, you will find a text document named “FTX164 TCT Key.txt”. Copy the whole text from the text file. Paste the User key into the “Add new key” field. Click on the “Add key” button.

Paste the User key into the “Add new key” field. Click on the “Add key” button.
4. Restart the Telematics configuration tool. A new window will open:

Select “FTC164 with development firmware” and click “Apply”.
Now You’re ready to use TCT!

== 2. Device preparation ==

[[File:Set up FTX164.jpg]]

'''Note: step #3 should only be completed once the device is configured.
'''
== 3. Device configuration ==

=== Configure Your APN and Server settings ===
in the “Mobile network” tab, You will find the following parameters which must be configured, in order to receive data to Your server: [[File:FTX164_Mobile_Network.png]]

[[File:FTX164_Server_Settings.png]]

=== Power off sleep mode with scheduled wake ups (optional) ===

One of the main goals during the development of this device was to ensure extended operation when working from the internal battery. This has been achieved not only with the use of a larger battery with a capacity of 2600mAh, but also by implementing new sleep mode logic that significantly reduces power consumption while in power off sleep.

Power off sleep used together with scheduled wake ups allows for extremely low power consumption in sleep, while maintaining the capability of the device to wake up based on pre-defined times.

Here is how You can enable these two features:

[[File:FTX164_P0S.jpg]]

[[File:FTX164 P0S22.png]]

During our internal current consumption tests, the FTX164 was consuming roughly 200uA per hour while it was in the power off sleep state, working only from the internal battery:

{| class="wikitable"
|style="background: #0054A6; color:white" |'''Sleep mode'''
|style="background: #0054A6; color:white" |'''Current consumption (mA)'''
|-
| rowspan="2" |Online deep sleep
|@12V Online Deep sleep: 10,34
|-
|@4V Online deep sleep: 24,36
|-
| rowspan="2" |Deep sleep
|@12V Deep sleep: 2,56
|-
|@4V Deep sleep: 6,81
|-
| rowspan="3" |Power off sleep
|@12V Power off sleep: 0,28
|-
|@4V Power off sleep: 0,19
|}

More information about sleep modes, such as, sleep exit/enter conditions, list of modules which are disabled during sleep modes can be found here.

=== Software defined pins (optional) ===
One of the key innovations introduced with the new hardware and firmware architecture is Software-Defined Pins (SDP). While this functionality is still limited in the current engineering sample, we encourage giving it a try!
The SDP feature allows flexible reconfiguration of pin assignments. At this stage, SDP configuration can only be performed through TCT, with the device physically connected. However remote configuration capabilities will be introduced in a future release.

[[File:FTX164_SDP11.png]]
[[File:FTX164_SDP22.png]]

Figure 2 Software defined pins configuration

=== Additional note regarding configuration ===

The FTX164 comes with many other features, which you will see in the TCT. However, as this is an engineering sample which comes with an ''evaluation'' firmware, keep in mind that some of the features visible in TCT, might not yet fully tested, documented or confirmed by our QA in this specific firmware version.
<in progress>
Limitations-> no concrete battery discharge % use this table for conversion

== Known limitations ==
*On the firmware version 3.7.rc-13, the internal battery ''percentage'' IO element will not show the accurate percentage of the internal battery.
Instead, please use the below provided conversion table.

[[File:Battery discharge table FTX164.jpg]]

*Digital Ground sense feature is not available on these engineering samples.

== Help ==

If You have faced issues during the testing of Your FTX164 device, please create a helpdesk ticket and include the following information:

1. Detailed description of the issue You've encountered, how often and when it occurs.

2. IMEI of Your device.

3. Mounting and/or wiring photos (ideally)

File:FTX164 SDP22.png

2025-12-01T13:19:20Z

Martynas.juozaitis:

2025-12-01T13:06:39Z

Martynas.juozaitis:

File:FTX164 Mobile Network.png

2025-12-01T13:06:16Z

Martynas.juozaitis:

FTX164 getting started

2025-12-01T13:01:39Z

Martynas.juozaitis:

This is the page where clients given engineering samples will be pointed to via QR code

== 1. Preparing the Telematics configuration tool ==
First step is to set up Your workstation to be able to use Telematics configuration tool (TCT).
This can be done by following the guidelines from our Wiki:
https://wiki.teltonika-gps.com/view/Getting_started_with_TCT

Once You have successfully installed and launched TCT, a special user key must be added, in order to gain access to FTX164 devices.

In the top right corner of the TCT, click on the cog to open the Settings menu. Click on the “User keys” option.

In the archive provided to You by Your sales manager, you will find a text document named “FTX164 TCT Key.txt”. Copy the whole text from the text file. Paste the User key into the “Add new key” field. Click on the “Add key” button.

Paste the User key into the “Add new key” field. Click on the “Add key” button.
4. Restart the Telematics configuration tool. A new window will open:

Select “FTC164 with development firmware” and click “Apply”.
Now You’re ready to use TCT!

== 2. Device preparation ==

[[File:Set up FTX164.jpg]]

'''Note: step #3 should only be completed once the device is configured.
'''
== 3. Device configuration ==

=== Configure Your APN and Server settings ===
in the “Mobile network” tab, You will find the following parameters which must be configured, in order to receive data to Your server:

=== Power off sleep mode with scheduled wake ups (optional) ===
One of the main goals during the development of this device was to ensure extended operation when working from the internal battery. This has been achieved not only with the use of a larger battery with a capacity of 2600mAh, but also by implementing new sleep mode logic that significantly reduces power consumption while in power off sleep.
[[File:FTX164_P0S.jpg]]

[[File:FTX164 P0S22.png]]
Power off sleep used together with scheduled wake ups allows for extremely low power consumption in sleep, while maintaining the capability of the device to wake up based on pre-defined times.
During our internal current consumption tests, the FTX164 was consuming roughly 200uA per hour while it was in the power off sleep state, working only from the internal battery.

{| class="wikitable"
|style="background: #0054A6; color:white" |'''Sleep mode'''
|style="background: #0054A6; color:white" |'''Current consumption (mA)'''
|-
| rowspan="2" |Online deep sleep
|@12V Online Deep sleep: 10,34
|-
|@4V Online deep sleep: 24,36
|-
| rowspan="2" |Deep sleep
|@12V Deep sleep: 2,56
|-
|@4V Deep sleep: 6,81
|-
| rowspan="3" |Power off sleep
|@12V Power off sleep: 0,28
|-
|@4V Power off sleep: 0,19
|}
table 1. Preliminary FTC164 current consumption tests

Figure 1 Wakeup schedule weekly matrix

More information about sleep modes, such as, sleep exit/enter conditions, list of modules which are disabled during sleep modes can be found here.

=== Software defined pins (optional) ===
One of the key innovations introduced with the new hardware and firmware architecture is Software-Defined Pins (SDP). While this functionality is still limited in the current engineering sample, we encourage giving it a try!
The SDP feature allows flexible reconfiguration of pin assignments. At this stage, SDP configuration can only be performed through TCT, with the device physically connected. However remote configuration capabilities will be introduced in a future release.

[[File:FTX164 SDP1.jpg]]
[[File:FTX164 SDP2.jpg]]

Figure 2 Software defined pins configuration

=== Additional note regarding configuration ===

The FTX164 comes with many other features, which you will see in the TCT. However, as this is an engineering sample which comes with an ''evaluation'' firmware, keep in mind that some of the features visible in TCT, might not yet fully tested, documented or confirmed by our QA in this specific firmware version.
<in progress>
Limitations-> no concrete battery discharge % use this table for conversion

== Known limitations ==
*On the firmware version 3.7.rc-13, the internal battery ''percentage'' IO element will not show the accurate percentage of the internal battery.
Instead, please use the below provided conversion table.

[[File:Battery discharge table FTX164.jpg]]

*Digital Ground sense feature is not available on these engineering samples.

== Help ==

If You have faced issues during the testing of Your FTX164 device, please create a helpdesk ticket and include the following information:

1. Detailed description of the issue You've encountered, how often and when it occurs.

2. IMEI of Your device.

3. Mounting and/or wiring photos (ideally)

File:FTX164 P0S22.png

2025-12-01T13:00:21Z

Martynas.juozaitis:

File:FTX164 P0S.jpg

2025-12-01T12:54:03Z

Martynas.juozaitis:

FTX164 getting started

2025-12-01T12:40:00Z

Martynas.juozaitis:

This is the page where clients given engineering samples will be pointed to via QR code

== 1. Preparing the Telematics configuration tool ==
First step is to set up Your workstation to be able to use Telematics configuration tool (TCT).
This can be done by following the guidelines from our Wiki:
https://wiki.teltonika-gps.com/view/Getting_started_with_TCT

Once You have successfully installed and launched TCT, a special user key must be added, in order to gain access to FTX164 devices.

In the top right corner of the TCT, click on the cog to open the Settings menu. Click on the “User keys” option.

In the archive provided to You by Your sales manager, you will find a text document named “FTX164 TCT Key.txt”. Copy the whole text from the text file. Paste the User key into the “Add new key” field. Click on the “Add key” button.

Paste the User key into the “Add new key” field. Click on the “Add key” button.
4. Restart the Telematics configuration tool. A new window will open:

Select “FTC164 with development firmware” and click “Apply”.
Now You’re ready to use TCT!

== 2. Device preparation ==

[[File:Set up FTX164.jpg]]

'''Note: step #3 should only be completed once the device is configured.
'''
== 3. Device configuration ==

=== Configure Your APN and Server settings ===
in the “Mobile network” tab, You will find the following parameters which must be configured, in order to receive data to Your server:

=== Power off sleep mode with scheduled wake ups (optional) ===
One of the main goals during the development of this device was to ensure extended operation when working from the internal battery. This has been achieved not only with the use of a larger battery with a capacity of 2600mAh, but also by implementing new sleep mode logic that significantly reduces power consumption while in power off sleep.

Power off sleep used together with scheduled wake ups allows for extremely low power consumption in sleep, while maintaining the capability of the device to wake up based on pre-defined times.
During our internal current consumption tests, the FTX164 was consuming roughly 200uA per hour while it was in the power off sleep state, working only from the internal battery.

{| class="wikitable"
|style="background: #0054A6; color:white" |'''Sleep mode'''
|style="background: #0054A6; color:white" |'''Current consumption (mA)'''
|-
| rowspan="2" |Online deep sleep
|@12V Online Deep sleep: 10,34
|-
|@4V Online deep sleep: 24,36
|-
| rowspan="2" |Deep sleep
|@12V Deep sleep: 2,56
|-
|@4V Deep sleep: 6,81
|-
| rowspan="3" |Power off sleep
|@12V Power off sleep: 0,28
|-
|@4V Power off sleep: 0,19
|}
table 1. Preliminary FTC164 current consumption tests

Figure 1 Wakeup schedule weekly matrix

More information about sleep modes, such as, sleep exit/enter conditions, list of modules which are disabled during sleep modes can be found here.

=== Software defined pins (optional) ===
One of the key innovations introduced with the new hardware and firmware architecture is Software-Defined Pins (SDP). While this functionality is still limited in the current engineering sample, we encourage giving it a try!
The SDP feature allows flexible reconfiguration of pin assignments. At this stage, SDP configuration can only be performed through TCT, with the device physically connected. However remote configuration capabilities will be introduced in a future release.

[[File:FTX164 SDP1.jpg]]
[[File:FTX164 SDP2.jpg]]

Figure 2 Software defined pins configuration

=== Additional note regarding configuration ===

The FTX164 comes with many other features, which you will see in the TCT. However, as this is an engineering sample which comes with an ''evaluation'' firmware, keep in mind that some of the features visible in TCT, might not yet fully tested, documented or confirmed by our QA in this specific firmware version.
<in progress>
Limitations-> no concrete battery discharge % use this table for conversion

== Known limitations ==
*On the firmware version 3.7.rc-13, the internal battery ''percentage'' IO element will not show the accurate percentage of the internal battery.
Instead, please use the below provided conversion table.

[[File:Battery discharge table FTX164.jpg]]

*Digital Ground sense feature is not available on these engineering samples.

== Help ==

If You have faced issues during the testing of Your FTX164 device, please create a helpdesk ticket and include the following information:

1. Detailed description of the issue You've encountered, how often and when it occurs.

2. IMEI of Your device.

3. Mounting and/or wiring photos (ideally)

2025-12-01T11:19:38Z

Martynas.juozaitis:

FTX164 getting started

2025-12-01T11:06:02Z

Martynas.juozaitis:

This is the page where clients given engineering samples will be pointed to via QR code

== 1. Preparing the Telematics configuration tool ==
First step is to set up Your workstation to be able to use Telematics configuration tool (TCT).
This can be done by following the guidelines from our Wiki:
https://wiki.teltonika-gps.com/view/Getting_started_with_TCT

Once You have successfully installed and launched TCT, a special user key must be added, in order to gain access to FTX164 devices.

In the top right corner of the TCT, click on the cog to open the Settings menu. Click on the “User keys” option.

In the archive provided to You by Your sales manager, you will find a text document named “FTX164 TCT Key.txt”. Copy the whole text from the text file. Paste the User key into the “Add new key” field. Click on the “Add key” button.

Paste the User key into the “Add new key” field. Click on the “Add key” button.
4. Restart the Telematics configuration tool. A new window will open:

Select “FTC164 with development firmware” and click “Apply”.
Now You’re ready to use TCT!

== 2. Device preparation ==

[[File:Set up FTX164.jpg]]

'''Note: step #3 should only be completed once the device is configured.
'''
== 3. Device configuration ==

Configure Your APN and Server settings
in the “Mobile network” tab, You will find the following parameters which must be configured, in order to receive data to Your server:

Configure other features that You would like to test
One of the main goals during the development of this device was to ensure extended operation when working from the internal battery. This has been achieved not only with the use of a larger battery with a capacity of 2600mAh, but also by implementing new sleep mode logic that significantly reduces power consumption while in power off sleep.

Moreover, the FTX164 comes with many other features, which you will see in the TCT. However, as this is an engineering sample which comes with an evaluation firmware, keep in mind that some of the features visible in TCT, might not yet fully tested, documented or confirmed by our QA.

Therefore, we recommend to first focus the testing on the following recommended features:
Power off sleep mode with scheduled wake ups
This is a combination of two features, allowing extremely low power consumption while in sleep, while maintaining the capability of the device to wake up based on pre-defined times.
During our internal current consumption tests, the FTX164 was consuming roughly 200uA per hour while it was in the power off sleep state, working only from the internal battery. O

Figure 1 Wakeup schedule weekly matrix

More information about sleep modes, such as, sleep exit/enter conditions, list of modules which are disabled during sleep modes can be found here.

Software defined pins
One of the key innovations introduced with the new hardware and firmware architecture is Software-Defined Pins (SDP). While this functionality is still limited in the current engineering sample, we encourage giving it a try!
The SDP feature allows flexible reconfiguration of pin assignments. At this stage, SDP configuration can only be performed through TCT, with the device physically connected. However remote configuration capabilities will be introduced in a future release.

[[File:FTX164 SDP1.jpg]]
[[File:FTX164 SDP2.jpg]]

Figure 2 Software defined pins configuration

Testing Device Operation on Internal Battery
The primary focus during the development of this device was to ensure extended operation on the internal battery. This has been achieved not only through the use of a larger battery but also by implementing a new sleep mode logic that significantly reduces power consumption.
We recommend testing the following power management features:
• Power-off Sleep Mode — Enables maximum power savings.
• Power-off Sleep Mode with Scheduled Wake-ups — Provides very low power consumption while maintaining the ability to periodically generate records and send them to the server.
• Online Deep Sleep — Allows reduced power usage while remaining connected.

Limitations-> no concrete battery discharge % use this table for conversion
________________________________________
Testing Software-Defined Pins (SDP)
One of the key innovations introduced with the new hardware and firmware architecture is Software-Defined Pins (SDP). While this functionality is still limited in the current engineering sample, we encourage
The SDP feature allows flexible reconfiguration of pin assignments. At this stage, configuration can only be performed through TCT, but remote configuration capabilities will be introduced in a future release.

Preliminary internal tests with FTC164
Sleep mode Current consumption(mA)
12V Online Deep Sleep 10.34
12V Deep Sleep 2.56
12V Power Off Sleep 0.28
Battery Online Deep Sleep 24.36
Battery Deep Sleep 6.81
Battery Power Off Sleep 0.19

More information about sleep modes can be found here.

File:FTX164 SDP2.jpg

2025-12-01T11:05:28Z

Martynas.juozaitis: