View source for TFT100 Features settings

==Eco/Green Driving==
{| style="width: 100%"
|[[Image:_Eco_Green_Driving_TFT100.png|right]]
When vehicle parameters exceed the values of ''Max Acceleration'', ''Max Braking'' or ''Max Cornering'' parameters, the scenario is activated: a record is generated and digital output status is changed to 1 when configured. You can configure all three parameters in m/s<sup>2</sup> units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below the set parameter value.<br />Parameters used with ''Eco/Green Driving'' functionality are given in a table below.

<table class="nd-othertables" style="width: 68%;">
 <tr>
        <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
        <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
    </tr>
<tr>
        <td style="width: 8%; text-align:left;">Scenario Settings</td>
        <td style="width: 8%; text-align:left">Enable/Disable Green driving functionality</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Max Acceleration</td>
        <td style="width: 8%; text-align:left">Value which can be reached while accelerating without triggering harsh acceleration event.</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Max Braking Acceleration</td>
        <td style="width: 8%; text-align:left">Value which can be reached while braking without triggering harsh braking event.</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Max Cornering Acceleration</td>
        <td style="width: 8%; text-align:left">Value which can be reached while cornering without triggering harsh cornering event.</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Source</td>
        <td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>
    </tr>
</table>

Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server TFT100 must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.

*<b>Output Control</b> - Scenario will activate the selected output.
**<code>None</code> - If event happens, it will not affect DOUT state. 
**<code>DOUT1</code> - If event happens, Digital output 1 will be activated.
**<code>DOUT2</code> - If event happens, Digital output 2 will be activated.<br>Digital output 1 or digital output 2 can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to [[DOUT_controls|DOUT controls]].

|}

===Auto calibration===
----
The auto-calibration process is following:

#The vehicle is stopped.
#There is a straight road ahead.
#Send SMS ''"auto_calibrate:set"'' to the TFT100 device.
#Accelerate to >7 km/h for 5 sec.
#TFT100 will send a response when calibration is completed successfully.

Calibration is saved to internal flash memory, which means it will stay after a reset.
To check auto-calibration status send a following short text message to the TFT100 device: ''"auto_calibrate:get"''.

==Over Speeding==
{| style="width: 100%"
|[[Image:TFT100_Over_Speeding.png|right]]
When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated and digital output status is changed to 1 when configured.<br />Scenario is active until detected speed decreases below the set parameter value.

*<b>Output Control</b> - Scenario will activate the selected output.
**<code>None</code> - If event happens, it will not affect DOUT state. 
**<code>DOUT1</code> - If event happens, Digital output 1 will be activated.
**<code>DOUT2</code> - If event happens, Digital output 2 will be activated.<br>Digital output 1 or digital output 2 can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to [[DOUT_controls|DOUT controls]].
|}

==Jamming==
{| style="width: 100%"
[[Image:TFT100_Jamming.png|frameless|right]]
When GSM signal jamming is detected the scenario is activated, an event record is generated and digital output status is changed to 1 when configured once ''Jamming'' timeout runs out. If jamming ends during timeout countdown no event will be generated| and output will not be controlled.<br />''Eventual Records'' parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise it will be appended only to eventual records.
*<b>Output Control</b> - Scenario will activate the selected output.
**<code>None</code> - If event happens, it will not affect DOUT state. 
**<code>DOUT1</code> - If event happens, Digital output 1 will be activated.
**<code>DOUT2</code> - If event happens, Digital output 2 will be activated.<br>Digital output 1 or digital output 2 can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to [[DOUT_controls|DOUT controls]].
|}

== DOUT Control Via Call==
{| style="width: 100%"
|[[Image:TFT100_DOUT_Control_Via_Call.png|right]]
Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>
Call control functionality is following:
* When TFT100 is configured to control DOUT1/DOUT2 the device waits for an incoming call from a configured secure number. If a call is received TFT100 turns on DOUT1/DOUT2 for a user defined ''Duration Timeout''. If duration timeout set to "0" DOUT1/DOUT2 will be OFF.

*<b>Output Control</b> - Scenario will activate the selected output.
**<code>None</code> - If event happens, it will not affect DOUT state. 
**<code>DOUT1</code> - If event happens, Digital output 1 will be activated.
**<code>DOUT2</code> - If event happens, Digital output 2 will be activated.<br>Digital output 1 or digital output 2 can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to [[DOUT_controls|DOUT controls]].
|}

==Immobilizer==
{| style="width: 100%"
|[[Image:TFT100_Immobilizer.png|right]]
If ''DOUT Control'' is disabled, scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled DOUT1/DOUT2 turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, DOUT1/DOUT2 turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, authorization will be successful only if the attached iButton is specified in iButton list.

*<b>Eventual records</b> - Scenario status value will be appended only to eventual records if this feature is enabled. When it is disabled , scenario status will be appended in each AVL record.
*<b>Output Control</b> - Scenario will activate the selected output.
**<code>None</code> - If event happens, it will not affect DOUT state. 
**<code>DOUT1</code> - If event happens, Digital output 1 will be activated.
**<code>DOUT2</code> - If event happens, Digital output 2 will be activated.<br>Digital output 1 or digital output 2 can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to [[DOUT_controls|DOUT controls]].
*<b>iButton List Check</b> - Parameter lets the user to use this scenario for authorization.
**<code>Disable</code> - Disables the iButton list check.
**<code>Enable</code> - The iButton list check is enabled. In order to work properly, at least 1 iButton ID must be written to the iButton list.
**<code>Beacon</code> -The Beacon list check is enabled. In order to work properly, at least 1 Beacon ID must be written to the Beacon list.
**<code>Both</code> - The iButton list check the Beacon list check are enabled. In order to work properly, at least 1 iButton ID or 1 Beacon ID must be configured.
*<b>Depend on ignition</b> - defines if the immobilizer scenario should depend on ignition or not. If disabled, the immobilizer functionality will be activated not depending on ignition. If enabled, immobilizer will be activated when the ignition is detected.
*<b>Ignition Off timeout</b> - Duration after which authorization is activated, when the ignition is turned off. For example, if Ignition off timeout is set to 30 seconds, when the driver turns the ignition off, he has 30 seconds until the immobilizer security check turns on again. In other words, if the driver turns off the ignition and turns it back on in less than 30 seconds, then he will not have to attach the iButton to the reader again.


'''IMMOBILIZER EXAMPLES can be found [[Immobilizer configuration explained|here]]'''

'''DETAILED IMMOBILIZER WIRING for testing can be found [[How to test 12V Relay with immobilizer scenario|here]]'''
|}

==iButton Read Notification==
{| style="width: 100%"
|[[Image:TFT100_iButton_Read_Notification.png|right]]
This functionality allows user to see when iButton is read. DOUT1/DOUT2 turns on for a configured duration and after DOUT ON duration ends DOUT1/DOUT2 does not turn on even if iButton is left attached.

*<b>Output Control</b> - Scenario will activate the selected output.
**<code>None</code> - If event happens, it will not affect DOUT state. 
**<code>DOUT1</code> - If event happens, Digital output 1 will be activated.
**<code>DOUT2</code> - If event happens, Digital output 2 will be activated.<br>Digital output 1 or digital output 2 can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to [[DOUT_controls|DOUT controls]].
|}

==FallDown==
{| style="width: 100%"
|[[Image:Falldown feature ss.png|right]]
This feature allows to detect if the device has fallen on one of the sides after the base device position was saved via autocalibration. <br/><br/>

<table class="nd-othertables" style="width: 68%;">

 <tr>
        <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
        <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Scenario Settings</td>
        <td style="width: 8%; text-align:left">Enable/Disable FallDown scenario</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Generate event</td>
        <td style="width: 8%; text-align:left">When the event will be generated</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Angle</td>
        <td style="width: 8%; text-align:left">Determines at what angle difference from base position event is generated</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Timeout</td>
        <td style="width: 8%; text-align:left">Duration (in seconds) after which FallDown event is generated</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Send SMS To</td>
        <td style="width: 8%; text-align:left">GSM number which should receive an SMS regarding generated FallDown event</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">SMS Text</td>
        <td style="width: 8%; text-align:left">SMS Text which will be included in FallDown event SMS notification</td>
    </tr>
</table>
|}

==Last Known Position==
{| style="width: 100%;"
|[[Image:Last_Known_Position.png|right]]
This feature adds low priority record <code>AVL ID 386</code> to all records.<br> 
The record shows how much time in seconds has passed since last GNSS fix.<br>

If the last good coordinate at the time the record is created is older than 60 seconds, then the new <b>high priority</b> record <code>AVL ID 69</code> will be sent immediately after GNSS fix appears. No matter how many different records have been created when there was no GNSS fix, only one high priority <code>AVL ID 69</code> record will be created when GNSS fix appears.

==DOUT Control Via Ignition==
{| style="width: 100%"
|[[Image:DOUT control via ignition ss.png|right]]
This feature allows direct control of DOUT by configured ignition source status. When enabled, the function will start to monitor ignition status, and once the ignition changes state from On to Off after configured Ignition Off timeout, selected DOUT (Digital Output) will be turned On.<br/><br/>

Turning DOUT Off is possible with enough voltage applied to the configured DIN (Digital Input).<br/>
<u>Voltage requirements:</u><br/>
DIN1 and DIN2 – '''2.5V''' (if ''Analog input value range'' is configured to 15V) and '''8.5V''' (if ''Analog input value range'' is configured to 150V.<br/><br/>


<table class="nd-othertables" style="width: 68%;">
 <tr>
        <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
        <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">DOUT Control</td>
        <td style="width: 8%; text-align:left">Scenario controls configured DOUT if ignition timeout exceeds its limit</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">DOUT Deactivation Via DIN</td>
        <td style="width: 8%; text-align:left">DOUT is turned off if configured DIN is in on (voltage applied) state </br> '''NOTE:''' ''Configured DIN cannot match with Ignition source DIN.''</td>
    </tr>
<tr>
        <td style="width: 8%; text-align:left">Ignition Off timeout</td>
        <td style="width: 8%; text-align:left">Duration (in seconds) after which DOUT is turned on, when ignition is turned off</td>
    </tr>
</table>
|}

==Ignition On Counter==
{| style="width: 100%"
|[[Image:Ignition On Counter.png|right]]
This feature adds a time counter that monitors the time a device spends in Ignition mode.

Two configuration parameters are added:
*Ignition On Counter - Used to disable/enable the feature. 
*Ignition On Counter Value (s) -  Used to set the initial value. 


<b>Important:</b> Ignition On Counter Value cannot be set to 0 with TCP configuration to prevent accidental client-caused counter resets. In case counter reaches maximum value, it will reset to 0 and count from the start.
|}

[[Category:TFT100 Configuration]]
|}