Jump to content

TEST-DM: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
 
(154 intermediate revisions by the same user not shown)
Line 1: Line 1:
{| class="wikitable" style="width: 100%;
==Parameter list (short)==
|-
https://wiki.teltonika-gps.com/view/FTC134_Features#Parameter_list
! PARAMETER !! ID !! DESCRIPTION !! colspan="2" | VALUES !! RELATED AVL ID
 
|-
==Parameter list (full)==
| rowspan="4" | Scenario settings || rowspan="4" | 11400 || rowspan="4" | Sets the scenario priority level. || 0 = Disable || Disable scenario. || rowspan="4" | 247
Rules:
|-
* Avoid inline formatting
| 1 = Low priority || Device makes an additional record with indication of event cause.  
* For DESCRIPTION and UNITS/VALUES, if there are multiple items - separate them by <nowiki><br></nowiki>
|-
<!---
| 2 = High priority || Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS.  
Table for full parameter lists (in separate param list pages).
|-
FULL WIDTH (style=width:100%).
| 3 = Panic priority || Triggers the same actions as high priority, but if GPRS fails, the device sends an AVL packet via SMS (if enabled in SMS settings).  
10, 15, 10, 33, 8, 8, 8, 8
|-
--->
| Duration || 11401 || Sets the minimal time period for how long the acceleration value should be higher than "Threshold" to trigger the event. || colspan="2" | Min: 0, Max: 1000 (ms) || -
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
|-
<tr>
| Threshold || 11402 || Sets the acceleration threshold value to detect the event. || colspan="2" | Min:100, Max: 6000 (mG) || -
<th style="width:10%;">PARAMETER ID</th>
|-
<th style="width:15%;" ">NAME</th>
| Send SMS to || 7037 || Sets the GSM number of SMS event recipient. || colspan="2" | Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings” || -
<th style="width:27%;">DESCRIPTION</th>
|-
<th style="width:28%;">UNITS/VALUES</th>
| SMS Text || 8037 || Sets the SMS text that will be sent to SMS recipient when the event is triggered. || colspan="2" | Max length: 160 symbols || -
<th style="width:5%;">TYPE</th>
|-
<th style="width:5%;">MIN</th>
| rowspan="2" | Crash Counter || rowspan="2" | 11415 || rowspan="2" | Toggle crash counter. This allows relating the eventual record of a particular crash with its trace packets by adding IO ID 317 to both. “Crash Counter“ and “Crash Trace“ must be enabled. The first crash will send an eventual record with IO ID 317 value 1. Subsequent crashes will add 1 to the value, overflowing at 255 and starting again from 0. || 0 = Disable || Disable feature. || rowspan="2" | 317
<th style="width:5%;">MAX</th>
|-
<th style="width:5%;">DEFAULT</th>
| 1 = Enable || Enable feature.
</tr>
|-
<tr>
| rowspan="4" | Crash Trace || rowspan="4" | 11406 || rowspan="4" | Enable tracing of crash events to get additional data about the crash. Related parameters: "Trace ODR", "Accel duration", "GNSS duration". || 0 = Disable || Generates only an eventual crash record. || rowspan="4" | 257
<td>11816</td>
|-
<td>Private mode deactivation triggers</td>
| 1 = Trace Changes || Records timestamps, GNSS data and acceleration values ONLY WHEN acceleration values change my 50 mG or more (saves mobile data).
<td>Private mode deactivation triggers. When a trigger is activated it deactivates the private mode. Implemented using bit mask so that multiple choices could be selected.</td>
|-
<td>0 - no trigger; <br>1 - Towing detected; <br>2 - Unplug detected; <br>3 - Towing or Unplug detected; <br>4 - Crash detected; <br>5 - Towing or Crash detected; <br>6 - Unplug or Crash detected; <br>7 - Towing, Unplug or Crash detected; <br>8 - Autogeofence triggered; <br>9 - Towing or Autogeofence triggered; <br>10 - Unplug or Autogeofence triggered; <br>11 - Towing, Unplug or Autogeofence triggered; <br>12 - Crash or Autogeofence triggered; <br>13 - Towing, Crash or Autogeofence triggered; <br>14 - Unplug, Crash or Autogeofence triggered; <br>15 - Towing, Unplug, Crash or Autogeofence triggered</td>
| 2 = Trace Full || Records timestamps, GNSS data and acceleration values.
<td>Uint16</td>
|-
<td>0</td>
| 3 = Trace Full with IOs || Records timestamps, GNSS data and acceleration values, together with IO elements configured as "Crash" (see "I/O" menu).
<td>15</td>
|-
<td>15</td>
| Trace ODR || 11410 || Sets the output data rate (frequency) of crash event data recording. || colspan="2" | Min: 20, Max: 200 (Hz) || -
</tr>
|-
<tr>
| Accel Duration || 11407 || Sets monitoring duration of linear accelerometer values before and after crash event. || colspan="2" | Min: 2, Max: 15 (s) || -
<td>900007</td>
|-
<td>Speed limit</td>
| GNSS Duration || 11408 || Sets monitoring duration of GNSS data before and after the crash event. || colspan="2" | Min: 2, Max: 30 (s) || -
<td>Speed threshold which determines when to generate speeding start/stop events.</td>
|-
<td>km/h</td>
| rowspan="2" |Trace Filter
<td>Uint16</td>
| rowspan="2" |11412
<td>0</td>
| rowspan="2" |Toggle filtering of accelerometer data in the crash trace. IF enabled, data is passed through EMA filter with 0.4 beta value (can be changed throught serial command).
<td>1000</td>
|0 = Disable
<td>0</td>
|Disable feature.
</tr>
| rowspan="2" | -
<tr>
|-
<td>1024900</td>
|1 = Enable
<td>Network jamming detection</td>
|Enable feature.
<td>The feature detects GSM jamming, initiates actions using an output, and helps to prevent vehicle theft when jamming devices are used. A low signal level is not equal to GSM jamming, the device recognizes these events.</td>
|}
<td>0 = Disable; <br>1 = Low priority; <br>2 = High priority</td>
<td>Uint8</td>
<td>0</td>
<td>2</td>
<td>0</td>
</tr>
<tr>
<td>899901 (DOUT1)<br>899911 (DOUT2)<br>899921 (DOUT3)</td>
<td>Activation timing</td>
<td>Select Activation timing when the event will be triggered.<br>Control mode - Persistent:
*Outside activation timing, selected DOUT will start being controlled while the device is outside of the geozone and will stop being controlled while the device is inside of the geozone. If the device is outside of multiple geozones, selected DOUT will continue being controlled until the device enters one of the geozones.
*Inside activation timing, selected DOUT will start being controlled while the device is inside the geozone and will stop being controlled while the device is outside of the geozone. If Output control according to speed limit is set, selected DOUT will start being controlled while the device is exceeding the speed limit inside the geozone. If the device is inside multiple geozones, selected DOUT will continue being controlled until the device is outside of all geozones (or stops exceeding the speed limit, if configured).
Control mode - Event:
*Outside activation timing, selected DOUT will be triggered once you exit the configured geozone.
*Inside activation timing, selected DOUT will be triggered once you enter the configured geozone.</td>
<td>1=Outside<br>2=Inside</td>
<td>Uint8</td>
<td>1</td>
<td>2</td>
<td>1</td>
</tr>
</table>
 
==AVL ID list==
Rules:
* Avoid inline formatting
* For DESCRIPTION, if there are multiple items - separate them by <nowiki><br></nowiki>
* Do not leave cells empty - write "-" if there is no value
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:10%">AVL ID</th>
<th style="width:15%">NAME</th>
<th style="width:5%">BYTES</th>
<th style="width:5%">TYPE</th>
<th style="width:5%">MIN</th>
<th style="width:5%">MAX</th>
<th style="width:5%">MULTIPLIER</th>
<th style="width:5%">UNITS</th>
<th style="width:55%;">DESCRIPTION</th>
</tr>
<tr>
<td>16</td>
<td>Total Odometer</td>
<td>4</td>
<td>Unsigned</td>
<td>0</td>
<td>2147483647</td>
<td>-</td>
<td>m</td>
<td>Virtual odometer value</td>
</tr>
<tr>
<td>69</td>
<td>GNSS Status</td>
<td>1</td>
<td>Unsigned</td>
<td>0</td>
<td>3</td>
<td>-</td>
<td>-</td>
<td>0 - GNSS OFF; <br>1 - GNSS ON with fix; <br>2 - GNSS ON without fix; <br>3 - GNSS sleep</td>
</tr>
<tr>
<td>181</td>
<td>GNSS PDOP</td>
<td>2</td>
<td>Unsigned</td>
<td>0</td>
<td>500</td>
<td>-</td>
<td>m</td>
<td>GNSS position dilution of precision. Normal PDOP is below 3 – the lower the number, the more accurate reported location is.</td>
</tr>
<tr>
<td>13377</td>
<td>Neighbouring Cell 2 RSSI</td>
<td>1</td>
<td>Unsigned</td>
<td>0</td>
<td>63</td>
<td>-</td>
<td>dB</td>
<td>Signal strength of Cell #2. Included in records as Permanent I/O when LBS mode is configured as "Location Source".</td>
</tr>
<tr>
<td>157</td>
<td>Manual Geofence Speeding event</td>
<td>1</td>
<td>Unsigned</td>
<td>0</td>
<td>1</td>
<td>-</td>
<td>-</td>
<td>0 - Speeding stop event; <br>1 - Speeding start event</td>
</tr>
</table>
 
==Pinout==
Rules:
* Avoid inline formatting, except for COLOR
** Example of multicolor formatting <nowiki><td style="color:lightgray;">'''White'''<span style="color:green">'''Green'''</span></td></nowiki>
*** user the same color name for "color", except use "color:lightgray" for white
<table style="width:100%; border-collapse:collapse;">
<!---nested table with two columns: left for pin table, right for pinout image --->
<tr>
<!--- start of left column--->
<td style="width:60%; vertical-align:top; padding-right:4px;">
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
  <th style="width:10%;">PIN</th>
  <th style="width:15%;">COLOR</th>
  <th style="width:25%;">NAME</th>
  <th style="width:50%;">DESCRIPTION</th>
</tr>
<tr>
<td>1</td>
<td style="color:red;">'''Red'''</td>
<td>VCC</td>
<td>Power supply (+8-32V V DC) (+)</td>
</tr>
<tr>
<td>2</td>
<td style="color:gray">'''Gray'''</td>
<td>DOUT3</td>
<td>Digital output channel 3</td>
</tr>
<tr>
<td>3</td>
<td style="color:lightgray">'''White'''</td>
<td>DIN3/AIN3</td>
<td>Digital input channel 3 / Analog input channel 3</td>
</tr>
<tr>
<td>4</td>
<td style="color:lightgray;">'''White'''<span style="color:green">'''Green'''</span></td>
<td>DIN4/AIN4/DGS</td>
<td>Digital input channel 4 / Analog input channel 4 / Ground sense</td>
</tr>
<tr>
<td>5</td>
<td style="color:yellow;">'''Yellow'''</td>
<td>DIN1/AIN1</td>
<td>Digital input 1 / Analog input 1</td>
</tr>
<tr>
<td>6</td>
<td style="color:lightgray;">'''White'''<span style="color:blue;">'''Blue'''</span></td>
<td>INPUT6</td>
<td>TX EXT (LVCAN – TX)</td>
</tr>
<tr>
<td>7</td>
<td style="color:black;">'''Black'''</td>
<td>GND</td>
<td>Ground (-)</td>
</tr>
<tr>
<td>8</td>
<td style="color:lightgray;">'''White'''<span style="color:orange;">'''Orange'''</span></td>
<td>DOUT1</td>
<td>Digital output channel 1</td>
</tr>
<tr>
<td>9</td>
<td style="color:purple;">'''Purple'''</td>
<td>DOUT2</td>
<td>Digital output channel 2</td>
</tr>
<tr>
<td>10</td>
<td style="color:blue;">'''Blue'''</td>
<td>1WIRE POWER</td>
<td> +3.8 V output for 1-Wire devices</td>
</tr>
<tr>
<td>11</td>
<td style="color:green;">'''Green'''</td>
<td>DIN2/AIN2/1WIRE DATA</td>
<td>Digital input channel 2 / Analog input 2 / Data for 1-Wire devices</td>
</tr>
<tr>
<td>12</td>
<td style="color:lightgray;">'''White'''<span style="color:yellow;">'''Yellow'''</span></td>
<td>INPUT5</td>
<td>RX EXT (LVCAN – RX)</td>
</tr>
</table>
</td>
<!--- start of right column--->
<td style="width:40%; vertical-align:top; horizontal-align:right; padding-left:4px;">
[[Image:FTC134_pinout.png|frameless|500px]]
</td>
</tr>
<!--- end of the whole nested table--->
</table>
 
==PCN==
Rules:
* Avoid inline formatting
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th>ITEM</th>
<th>iNFORMATION</th>
</tr>
<tr>
<th colspan="2" style="text-align:left;">Change details</th>
</tr>
<tr>
<td>Change type</td>
<td>Firmware update</td>
</tr>
<tr>
<td>Description</td>
<td>Key improvements from last production firmware are listed in errata: [[{{{model}}} Firmware Changelog]]</td>
</tr>
<tr>
<td>Previous firmware version</td>
<td>0.26.2</td>
</tr>
<tr>
<td>New firmware version</td>
<td>2.1.1</td>
</tr>
<tr>
<td>Change reason</td>
<td>{{{model}}} base firmware version update</td>
</tr>
<tr>
<td>Product release date</td>
<td>2025 June</td>
</tr>
<tr>
<th colspan="2" style="text-align:left;">Affected products</th>
</tr>
<tr>
<td>Model</td>
<td>{{{model}}}</td>
</tr>
<tr>
<td>Affected order codes</td>
<td>All order codes</td>
</tr>
<tr>
<td>Order code change</td>
<td>New firmware version</td>
</tr>
<tr>
<th colspan="2" style="text-align:left;">Impact</th>
</tr>
<tr>
<td>Risk assessment</td>
<td>During the transition period, clients might receive devices manufactured with the previous firmware version.</td>
</tr>
</table>
 
==LED Behavior==
Rules:
* Avoid inline formatting
* Do not leave cells empty - write "-" if there is no value
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th></th>
<th>'''STATUS LED (WHITE)'''</th>
<th>'''NAVIGATION LED (BLUE)'''</th>
</tr>
<tr>
<td>ON</td>
<td>Device is working, GPRS session not active</td><td>GNSS is working, position fix not acquired</td></tr><tr><td>BLINK every 1 second</td>
<td>Device is working, GPRS session active</td>
<td> -</td>
</tr>
<tr>
<td>SHORT BLINK every 1 second</td>
<td> -</td>
<td>GNSS is working, position fix acquired</td>
</tr>
<tr>
<td>OFF</td>
<td>Device is not working</td>
<td>GNSS is powered off (device not working or in sleep mode)</td>
</tr>
</table>
 
==Electrical Specifications==
Rules:
* Avoid inline formatting
* Leave cells without any data empty (''as opposed to other tables'')
<table class="nd-othertables_2" style="width:60%; border-collapse: collapse;">
<tr>
<th style="width:55%">SPECIFICATION</th>
<th style="width:15%">MIN</th>
<th style="width:15%">MAX</th>
<th style="width:15%">UNITS</th>
</tr>
<tr>
<th colspan="4" style="text-align:left;">Supply</th><td></td></tr>
<tr>
<td>Supply  Voltage</td>
<td>10</td>
<td>97</td>
<td>V</td>
</tr>
<tr>
<td>Supply Protection Voltage  (Absolute Maximum Ratings, Reverse/Forward Polarity)</td>
<td>-100</td>
<td>100</td>
<td>V</td>
</tr>
<tr>
<th colspan="4" style="text-align:left;">Inputs</th><td></td></tr>
<tr>
<td>Analog Input 1 Voltage</td>
<td>0</td>
<td>100</td>
<td>V</td>
</tr>
<tr>
<td>Analog Input 1 Current (At  100V Input)</td>
<td></td>
<td>0.7</td>
<td>mA</td>
</tr>
<tr>
<td>Digital Input 1 Voltage (DIN  state 0->1)</td>
<td>2.5</td>
<td>100</td>
<td>V</td>
</tr>
<tr>
<td>Digital Input 1 Current (At  100V Input)</td>
<td></td>
<td>0.7</td>
<td>mA</td>
</tr>
<tr>
<th colspan="4" style="text-align:left;">Outputs</th><td></td></tr>
<tr>
<td>Digital Output 1 Voltage</td>
<td>0</td>
<td>100</td>
<td>V</td>
</tr>
<tr>
<td>Digital Output 1 Current</td>
<td>0</td>
<td>500</td>
<td>mA</td>
</tr>
<tr>
<td>Digital Output 1 Overcurrent  Threshold</td>
<td></td>
<td>800</td>
<td>mA</td>
</tr>
<tr>
<td>Digital Output 2 Voltage</td>
<td>0</td>
<td>100</td>
<td>V</td>
</tr>
<tr>
<td>Digital Output 2 Current</td>
<td>0</td>
<td>500</td>
<td>mA</td>
</tr>
<tr>
<td>Digital Output 2 Overcurrent  Threshold</td>
<td></td>
<td>800</td>
<td>mA</td>
</tr>
</table>

Latest revision as of 14:50, 27 March 2026

Parameter list (short)

https://wiki.teltonika-gps.com/view/FTC134_Features#Parameter_list

Parameter list (full)

Rules:

  • Avoid inline formatting
  • For DESCRIPTION and UNITS/VALUES, if there are multiple items - separate them by <br>
PARAMETER ID NAME DESCRIPTION UNITS/VALUES TYPE MIN MAX DEFAULT
11816 Private mode deactivation triggers Private mode deactivation triggers. When a trigger is activated it deactivates the private mode. Implemented using bit mask so that multiple choices could be selected. 0 - no trigger;
1 - Towing detected;
2 - Unplug detected;
3 - Towing or Unplug detected;
4 - Crash detected;
5 - Towing or Crash detected;
6 - Unplug or Crash detected;
7 - Towing, Unplug or Crash detected;
8 - Autogeofence triggered;
9 - Towing or Autogeofence triggered;
10 - Unplug or Autogeofence triggered;
11 - Towing, Unplug or Autogeofence triggered;
12 - Crash or Autogeofence triggered;
13 - Towing, Crash or Autogeofence triggered;
14 - Unplug, Crash or Autogeofence triggered;
15 - Towing, Unplug, Crash or Autogeofence triggered
Uint16 0 15 15
900007 Speed limit Speed threshold which determines when to generate speeding start/stop events. km/h Uint16 0 1000 0
1024900 Network jamming detection The feature detects GSM jamming, initiates actions using an output, and helps to prevent vehicle theft when jamming devices are used. A low signal level is not equal to GSM jamming, the device recognizes these events. 0 = Disable;
1 = Low priority;
2 = High priority
Uint8 0 2 0
899901 (DOUT1)
899911 (DOUT2)
899921 (DOUT3)
Activation timing Select Activation timing when the event will be triggered.
Control mode - Persistent:
  • Outside activation timing, selected DOUT will start being controlled while the device is outside of the geozone and will stop being controlled while the device is inside of the geozone. If the device is outside of multiple geozones, selected DOUT will continue being controlled until the device enters one of the geozones.
  • Inside activation timing, selected DOUT will start being controlled while the device is inside the geozone and will stop being controlled while the device is outside of the geozone. If Output control according to speed limit is set, selected DOUT will start being controlled while the device is exceeding the speed limit inside the geozone. If the device is inside multiple geozones, selected DOUT will continue being controlled until the device is outside of all geozones (or stops exceeding the speed limit, if configured).

Control mode - Event:

  • Outside activation timing, selected DOUT will be triggered once you exit the configured geozone.
  • Inside activation timing, selected DOUT will be triggered once you enter the configured geozone.
1=Outside
2=Inside
Uint8 1 2 1

AVL ID list

Rules:

  • Avoid inline formatting
  • For DESCRIPTION, if there are multiple items - separate them by <br>
  • Do not leave cells empty - write "-" if there is no value
AVL ID NAME BYTES TYPE MIN MAX MULTIPLIER UNITS DESCRIPTION
16 Total Odometer 4 Unsigned 0 2147483647 - m Virtual odometer value
69 GNSS Status 1 Unsigned 0 3 - - 0 - GNSS OFF;
1 - GNSS ON with fix;
2 - GNSS ON without fix;
3 - GNSS sleep
181 GNSS PDOP 2 Unsigned 0 500 - m GNSS position dilution of precision. Normal PDOP is below 3 – the lower the number, the more accurate reported location is.
13377 Neighbouring Cell 2 RSSI 1 Unsigned 0 63 - dB Signal strength of Cell #2. Included in records as Permanent I/O when LBS mode is configured as "Location Source".
157 Manual Geofence Speeding event 1 Unsigned 0 1 - - 0 - Speeding stop event;
1 - Speeding start event

Pinout

Rules:

  • Avoid inline formatting, except for COLOR
    • Example of multicolor formatting <td style="color:lightgray;">'''White'''<span style="color:green">'''Green'''</span></td>
      • user the same color name for "color", except use "color:lightgray" for white
PIN COLOR NAME DESCRIPTION
1 Red VCC Power supply (+8-32V V DC) (+)
2 Gray DOUT3 Digital output channel 3
3 White DIN3/AIN3 Digital input channel 3 / Analog input channel 3
4 WhiteGreen DIN4/AIN4/DGS Digital input channel 4 / Analog input channel 4 / Ground sense
5 Yellow DIN1/AIN1 Digital input 1 / Analog input 1
6 WhiteBlue INPUT6 TX EXT (LVCAN – TX)
7 Black GND Ground (-)
8 WhiteOrange DOUT1 Digital output channel 1
9 Purple DOUT2 Digital output channel 2
10 Blue 1WIRE POWER +3.8 V output for 1-Wire devices
11 Green DIN2/AIN2/1WIRE DATA Digital input channel 2 / Analog input 2 / Data for 1-Wire devices
12 WhiteYellow INPUT5 RX EXT (LVCAN – RX)

PCN

Rules:

  • Avoid inline formatting
ITEM iNFORMATION
Change details
Change type Firmware update
Description Key improvements from last production firmware are listed in errata: [[{{{model}}} Firmware Changelog]]
Previous firmware version 0.26.2
New firmware version 2.1.1
Change reason {{{model}}} base firmware version update
Product release date 2025 June
Affected products
Model {{{model}}}
Affected order codes All order codes
Order code change New firmware version
Impact
Risk assessment During the transition period, clients might receive devices manufactured with the previous firmware version.

LED Behavior

Rules:

  • Avoid inline formatting
  • Do not leave cells empty - write "-" if there is no value
STATUS LED (WHITE) NAVIGATION LED (BLUE)
ON Device is working, GPRS session not activeGNSS is working, position fix not acquired
BLINK every 1 second Device is working, GPRS session active -
SHORT BLINK every 1 second - GNSS is working, position fix acquired
OFF Device is not working GNSS is powered off (device not working or in sleep mode)

Electrical Specifications

Rules:

  • Avoid inline formatting
  • Leave cells without any data empty (as opposed to other tables)
SPECIFICATION MIN MAX UNITS
Supply
Supply Voltage 10 97 V
Supply Protection Voltage (Absolute Maximum Ratings, Reverse/Forward Polarity) -100 100 V
Inputs
Analog Input 1 Voltage 0 100 V
Analog Input 1 Current (At 100V Input) 0.7 mA
Digital Input 1 Voltage (DIN state 0->1) 2.5 100 V
Digital Input 1 Current (At 100V Input) 0.7 mA
Outputs
Digital Output 1 Voltage 0 100 V
Digital Output 1 Current 0 500 mA
Digital Output 1 Overcurrent Threshold 800 mA
Digital Output 2 Voltage 0 100 V
Digital Output 2 Current 0 500 mA
Digital Output 2 Overcurrent Threshold 800 mA