Jump to content
  • EN

Test-AC: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
No edit summary
 
(73 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=SECO Scenario=
The Integrated Tariff of the Republic of Lithuania (LITAR) code is the initial eight-digit code used to uniquely identify the set of information on EU tariff measures and national taxes as well as some import and export restrictions and prohibitions. <br>


===<u> Introduction </u>===
==Description==
[[File:FTX SECO.png|right|500px]]
LITAR is an instrument intended for the search of the EU tariff and some non-tariff information as well as information on national tax (excise and VAT) rates; however, a computerized database is not a legislative act, therefore LITAR itself does not have the status of a legal instrument. In order to explore customs duties and other taxes as well as conditions of their implementation, you should find out a relevant legislation (EC regulation, Excise or VAT Law of the Republic of Lithuania, etc.).
Data collected by LITAR:


The SECO scenario (Secure Engine Cut Off) is a static scenario module responsible for controlling a digital output (DOUT) to cut off the engine based on configurable speed and movement conditions. It is typically triggered by remote commands (SMS or GPRS) and is used for security or immobilization purposes.
*Combined Nomenclature data (chapters, headings, subheadings, preliminary provisions of the Combined Nomenclature, chapter and chapter notes, subheading notes and additional notes);
*Explanatory Notes to the Combined Nomenclature;
*TARIC subheadings and lists, additional commodity codes and lists thereof;
*Details of any additional units of measurement applicable to the goods, together with their specifications and descriptions;
*Details of prohibitions and restrictions on goods, customs and tax rates, and export refund opportunities;
*Country codes, names, country group codes;
*Document codes and their lists;
*Data on tariff quotas (tariff quota numbers, periods of validity, quantities, balances, statuses);
*Alphabetical index of goods for classification of goods;
*Validity periods for all of the above. <br>
{{#switch: {{{model}}}


===<u>Prerequisites</u>===
| #default =  
*At least one '''DOUT''' is available.
*'''SECO functionality''' should have DOUT control priority higher than '''Immobilizer''' scenario.
===<u>How It Works</u>===


The SECO scenario supports three distinct engine cut-off modes, each designed for different operational requirements.
==LITAR code for FM units==
LITAR code is using the same for all FM units (FM, FMB, FMC, FMM, FMU family and [[FMT100]], [[MTB100]] devices) except OBD family. The code is '''85269120'''.<br>
LITAR code for OBD family ([[FMB001]], [[FMC001]], [[FMM001]] etc ). The code is '''85269180'''.<br>


'''First Mode'''
| LV-CAN200 | ALL-CAN300 | CAN-CONTROL | SIMPLE-CAN | MINI-CAN | ECAN01 | ECAN02 =


*In the first mode, DOUT control starts when the vehicle speed goes below a configured speed threshold and remains below this threshold for a specified speed check period.
==LITAR code for CAN adapters units==
 
The same LITAR code is used for all CAN adapters ([[LV-CAN200]], [[ALL-CAN300]], [[CAN-CONTROL]], [[SIMPLE-CAN]], [[MINI-CAN]] and [[ECAN01]]). The code for LV-CAN200 is '''85371091'''.<br>
*In this configuration, the DOUT is activated instantly when the speed condition is met.
 
*If the speed check period timer is running and the vehicle speed increases above the configured speed threshold before the timer expires, the timer will be reset.
 
:''Example:''
::*Speed threshold: 70 km/h
::*Speed check period: 10 second
 
'''Second Mode'''
 
*The second mode requires a GNSS fix to be present before DOUT control begins.
 
*In this mode, DOUT pulsing starts when the vehicle speed drops below a configured speed pulse threshold and the speed remains below this threshold for a specified speed check period.
 
*While pulsing is ongoing, when the vehicle speed drops below a configured speed threshold, the system switches from pulsing to steady DOUT control.
 
*If the speed check period timer is running and the vehicle speed increases above the configured speed pulse threshold before the timer expires, the timer will be reset.
 
:''Example:''
::*Speed pulse threshold: 70 km/h
::*Speed threshold: 40 km/h
::*Speed check period: 10 seconds
::*Pulsing enabled: Yes
 
'''Third Mode'''
 
*The third mode is used when a GNSS fix is not available, no vehicle movement is detected anymore, and the configured movement timeout has passed.
 
*In this mode, the system initiates DOUT control only if the vehicle is stationary, location data is unavailable, and the movement timeout condition is met, providing an additional layer of security.
 
*If the movement timeout has not been reached and movement is detected, the DOUT will not be activated, and the movement timeout will be reset.
 
:''Example:''
 
::*Movement timeout: 20 seconds
 
=== <u> Parameters list </u>===  
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> SECO DOUT status </td>
<td style="vertical-align: middle; text-align: center;"> 396</td>
<td style="vertical-align: middle; text-align: center;"> SECO DOUT status. </td>
<td style="vertical-align: middle; text-align: left;">'''0''' = SECO DOUT is '''OFF''' <br> '''1''' = SECO DOUT is '''pulsing''' <br> '''2''' = SECO DOUT is '''ON''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Priority </td>
<td style="vertical-align: middle; text-align: center;"> 1039600 </td>
<td style="vertical-align: middle; text-align: center;"> SECO scenario priority. </td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = SECO  scenario is '''disabled''' <br> '''1''' = SECO scenario is '''low''' <br> '''2''' = SECO scenario is '''high''' <br>
</td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Speed </td>
<td style="vertical-align: middle; text-align: center;"> 12254 </td>
<td style="vertical-align: middle; text-align: center;"> Speed threshold at which the configured digital output (DOUT) will be activated. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''255''' <br> Default value = '''10''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Speed pulse scenario </td>
<td style="vertical-align: middle; text-align: center;"> 12259 </td>
<td style="vertical-align: middle; text-align: center;">
Speed threshold at which the configured digital output (DOUT) will be toggled. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0'''<br> Maximum value = '''255''' <br>Default value = '''10''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">
Speed check period </td>
<td style="vertical-align: middle; text-align: center;"> 12255 </td>
<td style="vertical-align: middle; text-align: center;"> Time span during which speed must be lower than configured for output to activate (GNSS on). </td>
<td style="vertical-align: middle; text-align: left;">  Minimum value = '''0'''<br> Maximum value = '''65535''' <br>Default value = '''10''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">
Movement timeout</td>
<td style="vertical-align: middle; text-align: center;"> 12256 </td>
<td style="vertical-align: middle; text-align: center;"> Duration after which the DOUT will be activated if no movement is detected and GNSS is off. </td>
<td style="vertical-align: middle; text-align: left;">  Minimum value = '''0'''<br> Maximum value = '''65535''' <br>Default value = '''30''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">Eventual records</td>
<td style="vertical-align: middle; text-align: center;"> 1039604</td>
<td style="vertical-align: middle; text-align: center;">Eventual records.</td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = SECO status will be sent with both eventual and periodical records. <br> '''1''' = SECO status will be sent only when the event happens (an eventual record).</td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">Output control</td>
<td style="vertical-align: middle; text-align: center;">12252</td>
<td style="vertical-align: middle; text-align: center;">
SECO output control. </td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = DOUT control is disabled <br> '''1''' = DOUT1 is controlled <br> '''2''' = DOUT2 is controlled <br> '''3''' = DOUT3 is controlled <br> '''4''' = DOUT4 is controlled</td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">Output pulse</td>
<td style="vertical-align: middle; text-align: center;">12253</td>
<td style="vertical-align: middle; text-align: center;">Pulse functionality adds additional output control which helps to slow down vehicle before fully disabling fuel pump.</td>
<td style="vertical-align: middle; text-align: left;"> '''0''' = Disabled <br> '''1''' = Enabled </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">
DOUT on duration</td>
<td style="vertical-align: middle; text-align: center;">12257</td>
<td style="vertical-align: middle; text-align: center;"> Duration for how long DOUT should be active.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''10'''<br> Maximum value = '''5000''' <br>Default value = '''1000''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">DOUT off duration</td>
<td style="vertical-align: middle; text-align: center;">12258</td>
<td style="vertical-align: middle; text-align: center;"> A value in milliseconds, for how long DOUT should be inactive. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''10'''<br> Maximum value = '''5000''' <br>Default value = '''1000''' </td>
 
</tr>
</table>
 
 
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DOUT1}}{{FTX Pin Support List|model={{{model}}}|pin=DOUT2}}{{FTX Pin Support List|model={{{model}}}|pin=DOUT3}}
|
===SECO Commands===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:20%; vertical-align: middle; text-align: left;">COMMAND</th>
<th style="width:45%; vertical-align: middle; text-align: left;">DESCRIPTION</th>
<th style="width:35%; vertical-align: middle; text-align: left;">SYNTAX EXAMPLE</th>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">[[SMS/GPRS command - secooff|secooff]]</td>
<td style="vertical-align: middle; text-align: left;">Deactivate SECO scenario.</td>
<td style="vertical-align: middle; text-align: left;"><code>secooff</code></td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: left;">[[SMS/GPRS command - secoon|secoon]]</td>
<td style="vertical-align: middle; text-align: left;">Activate SECO scenario.</td>
<td style="vertical-align: middle; text-align: left;"><code>secoon</code></td>
</tr>
</table>
}}
}}
 
==External links==
=GNSS Fuel Counter=
https://ec.europa.eu/taxation_customs/dds2/taric/taric_consultation.jsp?Lang=en <br>
 
https://litarweb.lrmuitine.lt/taric/web/main_EN
The Fuel Counter GNSS scenario provides fuel consumption estimation using GNSS-derived distance and user-configured fuel rate. It calculates the amount of fuel used by multiplying traveled distance by the average fuel rate and converting it to appropriate units. It is a software-based alternative  when fuel flow sensors are not available.
 
=== <u> Parameters list </u>===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Scenario priority </td>
<td style="vertical-align: middle; text-align: center;"> 1001200<br>(12)</td>
<td style="vertical-align: middle; text-align: center;">Priority levels of how events are being sent to the server. Low priority events are added to periodical record and high priority records are sent immediately. </td>
<td style="vertical-align: middle; text-align: left;">  '''0'''=Disable <br>  '''1'''=Low priority <br>  '''2'''=High priority </td>
 
 
</tr> 
<tr>
 
<td style="vertical-align: middle; text-align: center;"> Average consumption </td>
<td style="vertical-align: middle; text-align: center;"> 11902 </td>
<td style="vertical-align: middle; text-align: center;">Average fuel consumption as specified in the technical documentation of the vehicle.</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''50.0''' <br> Default value = '''0.0''' </td>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: center;">
Fuel counter value</td>
<td style="vertical-align: middle; text-align: center;"> 11910 </td>
<td style="vertical-align: middle; text-align: center;"> Initial fuel counter value measured in liters. This parameter can be used as a starting value or can be reset to current one. </td>
<td style="vertical-align: middle; text-align: left;"> Minimum value = '''0.0'''<br> Maximum value = '''4294967.2''' <br> Default value = '''0.0''' </td>
 
 
</tr>
</table>

Latest revision as of 12:08, 4 June 2026

The Integrated Tariff of the Republic of Lithuania (LITAR) code is the initial eight-digit code used to uniquely identify the set of information on EU tariff measures and national taxes as well as some import and export restrictions and prohibitions.

Description

LITAR is an instrument intended for the search of the EU tariff and some non-tariff information as well as information on national tax (excise and VAT) rates; however, a computerized database is not a legislative act, therefore LITAR itself does not have the status of a legal instrument. In order to explore customs duties and other taxes as well as conditions of their implementation, you should find out a relevant legislation (EC regulation, Excise or VAT Law of the Republic of Lithuania, etc.). Data collected by LITAR:

  • Combined Nomenclature data (chapters, headings, subheadings, preliminary provisions of the Combined Nomenclature, chapter and chapter notes, subheading notes and additional notes);
  • Explanatory Notes to the Combined Nomenclature;
  • TARIC subheadings and lists, additional commodity codes and lists thereof;
  • Details of any additional units of measurement applicable to the goods, together with their specifications and descriptions;
  • Details of prohibitions and restrictions on goods, customs and tax rates, and export refund opportunities;
  • Country codes, names, country group codes;
  • Document codes and their lists;
  • Data on tariff quotas (tariff quota numbers, periods of validity, quantities, balances, statuses);
  • Alphabetical index of goods for classification of goods;
  • Validity periods for all of the above.

LITAR code for FM units

LITAR code is using the same for all FM units (FM, FMB, FMC, FMM, FMU family and FMT100, MTB100 devices) except OBD family. The code is 85269120.
LITAR code for OBD family (FMB001, FMC001, FMM001 etc ). The code is 85269180.

External links

https://ec.europa.eu/taxation_customs/dds2/taric/taric_consultation.jsp?Lang=en
https://litarweb.lrmuitine.lt/taric/web/main_EN

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Test-AC&oldid=114061"