0
edits
Changes
Template:FMB640 Features settings (view source)
Revision as of 18:42, 27 November 2018
, 18:42, 27 November 2018no edit summary
==Green Driving==
==Green Driving==
{{{pic_greendriving|[[Image:FMB640_green_driving.png|300px|right]]}}}
{{{pic_greendriving|[[Image:Green driving.JPG|300px|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 ''Green Driving'' functionality are given in a table below.
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 ''Green Driving'' functionality are given in a table below.
| style="text-align: left; vertical-align: top;" | Value which can be reached while cornering without triggering harsh cornering event.
| style="text-align: left; vertical-align: top;" | Value which can be reached while cornering without triggering harsh cornering event.
|-
|-
! style="text-align: left; vertical-align: top;" | ''Acceleration Active Output Duration''
! style="text-align: left; vertical-align: top;" | ''DOUT ON Duration''
| style="text-align: left; vertical-align: top;" | Set active output duration after harsh acceleration event detected.
| style="text-align: left; vertical-align: top;" | Set active output duration after harsh event detected.
|-
|-
! style="text-align: left; vertical-align: top;" | ''Braking Active Output Duration''
! style="text-align: left; vertical-align: top;" | ''DOUT OFF Duration''
| style="text-align: left; vertical-align: top;" | Set active output duration after harsh braking event detected.
| style="text-align: left; vertical-align: top;" | Set active output duration after harsh event ended.
|-
|-
|}
|}
==Over Speeding==
==Over Speeding==
{{{pic_overspeeding|[[Image:FMB640 over speeding.png|300px|right]]}}}
{{{pic_overspeeding|[[Image:Over speeding.JPG|300px|right]]}}}
When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br/>Scenario is active until detected speed decreases below the set parameter value.
When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br/>Scenario is active until detected speed decreases below the set parameter value.
==Jamming==
==Jamming==
{{{pic_jamming|[[Image:FMB640_jamming.png|300px|right]]}}}
{{{pic_jamming|[[Image:Jamming.JPG |300px|right]]}}}
When jamming is detected the scenario is activated, an event record is generated{{{text_dout| 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{{{text_dout| 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.
When jamming is detected the scenario is activated, an event record is generated{{{text_dout| 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{{{text_dout| 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.
==Immobilizer==
==Immobilizer==
{{{pic_jamming|[[Image:FMB640_immobilizer.png|300px|right]]}}}
{{{pic_jamming|[[Image:Immobilizer.JPG|300px|right]]}}}
Vehicle can be used only if iButton is connected. In this scenario iButton list is not used; connect any iButton to pass Immobilizer security. Selected DOUT is controlled by scenario for user needs.
Vehicle can be used only if iButton is connected. In this scenario iButton list is not used; connect any iButton to pass Immobilizer security. Selected DOUT is controlled by scenario for user needs.
==iButton Read Notification==
==iButton Read Notification==
{{{pic_jamming|[[Image:FMB640_iButtonReadNotification.png|250px|right]]}}}
{{{pic_jamming|[[Image:I button.JPG|300px|right]]}}}
If scenario is enabled, when iButton is attached and is successfully read, configured DOUT goes ON for configurable amount of time (min: 0.1 s; max: 5.00 s; default: 0.2 s). If Immobilizer scenario is enabled and iButton’s indication scenario is enabled and the same DOUT controls are chosen then in case iButton is attached DOUT is not affected.
If scenario is enabled, when iButton is attached and is successfully read, configured DOUT goes ON for configurable amount of time (min: 0.1 s; max: 5.00 s; default: 0.2 s). If Immobilizer scenario is enabled and iButton’s indication scenario is enabled and the same DOUT controls are chosen then in case iButton is attached DOUT is not affected.
==Short burst data settings==
==Short burst data settings==
{{{pic_overspeeding|[[Image:Short_burst.JPG|300px|right]]}}}
{{{short_burst|[[Image:Short_burst.JPG|300px|right]]}}}
FMB640 supports Iridium devices which can send short burst data (SBD) to server. This means that some data can be sent from FM device to server through satellites.
FMB640 supports Iridium devices which can send short burst data (SBD) to server. This means that some data can be sent from FM device to server through satellites.
