Difference between revisions of "Template:FM36YX Scenarios settings"
From Wiki Knowledge Base | Teltonika GPS
| (14 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
Digital Output (open drain grade) usage in scenarios: | Digital Output (open drain grade) usage in scenarios: | ||
* [[{{{model|FM36YX}}}_Features_settings#Green_Driving|Green Driving]] | * [[{{{model|FM36YX}}}_Features_settings#Green_Driving|Green Driving]] | ||
| − | * [[{{{model|FM36YX}}}_Features_settings# | + | * [[{{{model|FM36YX}}}_Features_settings#Scenarios_settings|Over Speeding]] |
* [[{{{model|FM36YX}}}_Features_settings#Excessive_Idling_Detection|Excessive Idling Detection]] | * [[{{{model|FM36YX}}}_Features_settings#Excessive_Idling_Detection|Excessive Idling Detection]] | ||
* [[{{{model|FM36YX}}}_Features_settings#Jamming_detection|Jamming detection]] | * [[{{{model|FM36YX}}}_Features_settings#Jamming_detection|Jamming detection]] | ||
* [[{{{model|FM36YX}}}_Features_settings#Authorized_driving|Authorized driving]] | * [[{{{model|FM36YX}}}_Features_settings#Authorized_driving|Authorized driving]] | ||
* [[{{{model|FM36YX}}}_Features_settings#Immobilizer|Immobilizer]] | * [[{{{model|FM36YX}}}_Features_settings#Immobilizer|Immobilizer]] | ||
| − | |||
<br><br> | <br><br> | ||
===Green Driving=== | ===Green Driving=== | ||
---- | ---- | ||
Helps to prevent and inspect driver about harsh driving. Scenario continuously monitors: accelerating force, braking force and cornering angles. Warns driver if needed. DOUT1 or DOUT2 is controlled by scenario for user needs, for example buzzer or LED. <br> | Helps to prevent and inspect driver about harsh driving. Scenario continuously monitors: accelerating force, braking force and cornering angles. Warns driver if needed. DOUT1 or DOUT2 is controlled by scenario for user needs, for example buzzer or LED. <br> | ||
| − | To save 3G | + | To save 3G/GPRS traffic Green Driving '''event''' will be '''generated (included into sent records) only''' when measured values are higher than those set in configuration, without additional I/O settings.<br> |
To prevent generating false events, harsh acceleration and harsh braking is monitored only when following conditions are fulfilled: | To prevent generating false events, harsh acceleration and harsh braking is monitored only when following conditions are fulfilled: | ||
* Ignition is ON (DIN1 = 1) | * Ignition is ON (DIN1 = 1) | ||
| Line 22: | Line 21: | ||
* Ignition is ON (DIN1 = 1) | * Ignition is ON (DIN1 = 1) | ||
* Vehicle speed is equal or higher than 30km/h | * Vehicle speed is equal or higher than 30km/h | ||
| + | <font size="+1"> | ||
{| class="wikitable" style="border-style: solid; border-width: 0px" | {| class="wikitable" style="border-style: solid; border-width: 0px" | ||
|+ | |+ | ||
| Line 28: | Line 28: | ||
| style="text-align: left; background: #F6F6FB;" | Note: Green Driving Scenario is a factor on various cars and various drivers testing phase and can be subject to changes. Teltonika is constantly working on improvement of the functionality of the devices, and strongly recommends using the latest version of the firmware. | | style="text-align: left; background: #F6F6FB;" | Note: Green Driving Scenario is a factor on various cars and various drivers testing phase and can be subject to changes. Teltonika is constantly working on improvement of the functionality of the devices, and strongly recommends using the latest version of the firmware. | ||
|} | |} | ||
| − | + | </font> | |
| − | + | ||
| + | DOUT1 is ON (if selected DOUT1) for: | ||
* 3sec. if detected value is over (0; 30] % from preconfigured allowed value; | * 3sec. if detected value is over (0; 30] % from preconfigured allowed value; | ||
* 5sec. if detected value is over (30; 50] % from preconfigured allowed value; | * 5sec. if detected value is over (30; 50] % from preconfigured allowed value; | ||
* 7sec. if detected value is over (50; -] % from preconfigured allowed value. | * 7sec. if detected value is over (50; -] % from preconfigured allowed value. | ||
| − | After period of time | + | After period of time DOUT1 is turned OFF.<br><br> |
===Over Speeding=== | ===Over Speeding=== | ||
---- | ---- | ||
| − | + | DOUT1 is ON (if selected DOUT1), while vehicle speed exceeds parameter value. DOUT1 is activated until current speed decreases below parameter value.<br><br> | |
| − | |||
| − | |||
| − | |||
===Excessive Idling Detection=== | ===Excessive Idling Detection=== | ||
---- | ---- | ||
| − | |||
| − | |||
If ignition is ON and no movement, event will be generated when TMO reached. User can enable this functionality, select timeouts for stationary time and for movement time.<br><br> | If ignition is ON and no movement, event will be generated when TMO reached. User can enable this functionality, select timeouts for stationary time and for movement time.<br><br> | ||
| − | |||
===Jamming detection=== | ===Jamming detection=== | ||
---- | ---- | ||
| − | + | DOUT1 is ON (if selected DOUT1), while modem is fixing radio frequency jamming. After jamming is over, DOUT1 is deactivated.<br><br> | |
| − | |||
| − | |||
| − | |||
| − | |||
===Authorized driving=== | ===Authorized driving=== | ||
---- | ---- | ||
| − | + | DOUT2 is continuously OFF. Dout2 (if selected DOUT2) turns ON if Ignition turns ON (configured Ignition Source=1). After authorizing iButton (iButton ID is read and it matches the ID from the iButton list), DOUT2 turns OFF. After successful authorization ignition can be turned OFF (configured Ignition Source =0) for no longer than 30 seconds, otherwise authorization must be repeated.<br><br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
===Immobilizer=== | ===Immobilizer=== | ||
---- | ---- | ||
| − | + | (if selected DOUT2) DOUT2 is continuously OFF. Dout2 turns ON if Ignition turns ON (configured Ignition Source = 1). After iButton ID is read (any iButton is attached), DOUT2 turns OFF. After iButton identification, ignition can be turned OFF (configured Ignition Source = 0) for no longer than 30 seconds, otherwise immobilizer must be repeated.<br><br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 07:20, 1 June 2018
In Scenarios window six different scenarios are available: Green driving, Over Speeding, Excessive Idling, Immobilizer, iButton List checking and Jamming. All scenarios can use DOUT together, but if DOUT1 is assigned to Immobilizer, other scenarios can’t control it.
Digital Output (open drain grade) usage in scenarios:
- Green Driving
- Over Speeding
- Excessive Idling Detection
- Jamming detection
- Authorized driving
- Immobilizer
Green Driving
Helps to prevent and inspect driver about harsh driving. Scenario continuously monitors: accelerating force, braking force and cornering angles. Warns driver if needed. DOUT1 or DOUT2 is controlled by scenario for user needs, for example buzzer or LED.
To save 3G/GPRS traffic Green Driving event will be generated (included into sent records) only when measured values are higher than those set in configuration, without additional I/O settings.
To prevent generating false events, harsh acceleration and harsh braking is monitored only when following conditions are fulfilled:
- Ignition is ON (DIN1 = 1)
- Vehicle speed is equal or higher than 10km/h
Harsh cornering is monitored only when following conditions are fulfilled:
- Ignition is ON (DIN1 = 1)
- Vehicle speed is equal or higher than 30km/h
|
Note: Green Driving Scenario is a factor on various cars and various drivers testing phase and can be subject to changes. Teltonika is constantly working on improvement of the functionality of the devices, and strongly recommends using the latest version of the firmware. |
DOUT1 is ON (if selected DOUT1) for:
- 3sec. if detected value is over (0; 30] % from preconfigured allowed value;
- 5sec. if detected value is over (30; 50] % from preconfigured allowed value;
- 7sec. if detected value is over (50; -] % from preconfigured allowed value.
After period of time DOUT1 is turned OFF.
Over Speeding
DOUT1 is ON (if selected DOUT1), while vehicle speed exceeds parameter value. DOUT1 is activated until current speed decreases below parameter value.
Excessive Idling Detection
If ignition is ON and no movement, event will be generated when TMO reached. User can enable this functionality, select timeouts for stationary time and for movement time.
Jamming detection
DOUT1 is ON (if selected DOUT1), while modem is fixing radio frequency jamming. After jamming is over, DOUT1 is deactivated.
Authorized driving
DOUT2 is continuously OFF. Dout2 (if selected DOUT2) turns ON if Ignition turns ON (configured Ignition Source=1). After authorizing iButton (iButton ID is read and it matches the ID from the iButton list), DOUT2 turns OFF. After successful authorization ignition can be turned OFF (configured Ignition Source =0) for no longer than 30 seconds, otherwise authorization must be repeated.
Immobilizer
(if selected DOUT2) DOUT2 is continuously OFF. Dout2 turns ON if Ignition turns ON (configured Ignition Source = 1). After iButton ID is read (any iButton is attached), DOUT2 turns OFF. After iButton identification, ignition can be turned OFF (configured Ignition Source = 0) for no longer than 30 seconds, otherwise immobilizer must be repeated.
