Changes

     </tr>

     </tr>

<tr>

<tr>

         <td style="width: 8%; text-align:left;">Scenario Settings</td>

         <td style="width: 8%; text-align:left;">Output Control</td>

         <td style="width: 8%; text-align:left">Enable/Disable Green driving functionality</td>

         <td style="width: 8%; text-align:left">Enable/Disable Green driving functionality and Activate/Deactivate DOUT.</td>

     </tr>

     </tr>

<tr>

<tr>

<tr>

<tr>

         <td style="width: 8%; text-align:left">Source</td>

         <td style="width: 8%; text-align:left">Source</td>

         <td style="width: 8%; text-align:left">Which source data will be collected from.</td>

         <td style="width: 8%; text-align:left">Which source data will be collected from:

* '''GNSS''' - GPS Data will be used to detect harsh driving. (This algorithm was used in FM53, FM63 devices) <br>

</td>

     </tr>

     </tr>

</table>

</table>

 

{{{pic_accelerometerposition|[[Image:FMB640accelerometerposition.png|300px|right]]}}} [[FMB640]] Device accelerometer position. (With positive Z axis pointing to Ground and antennas face forward in the vehicle). Before operation with the vehicle on level ground user must send “setacc” SMS.

<b>Note:</b> To use “Accelerometer Algorithm A1” option user need to install device as in Figure 1. {{{pic_accelerometerposition|[[Image:FMB640accelerometerposition.png|300px|right]]}}} FM64 Device accelerometer position. (With positive Z axis pointing to Ground and antennas face forward in vehicle). Before operation with vehicle on level ground user must send “setacc” SMS.

 

 

 

===Auto calibration===

===Auto calibration===

----

----

The auto-calibration process is following:

The auto-calibration process is the following:

# The vehicle is stopped.

# The vehicle is stopped.

# There is a straight road ahead.

# There is a straight road ahead.

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.<br/>{{{over_speeding_dout|info}}}

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.<br/>{{{over_speeding_dout|info}}}

DOUT1, DOUT2 or DOUT3 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]].

DOUT1, DOUT2 or DOUT3 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]].

<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>

<br/><br/><br/><br/><br/>

==Jamming==

==Jamming==

{{{pic_jamming|[[Image:Jamming.JPG |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.

<br/><br/><br/><br/><br/><br/><br/><br/><br/>

<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>

 

 

 

<br/><br/><br/>

==Authorized driving/Immobilizer==

==Authorized driving/Immobilizer==

{{{pic_jamming|[[Image:FMB640_authorizedD.png|250px|right]]}}}

{{{pic_immobilizer|[[Image:FMB640_authorizedD.png|300px|right]]}}}

*If DOUT Control is disabled, the 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).  

*If DOUT Control is disabled, the 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/DOUT3 turns OFF.  

* After any iButton ID is attached, DOUT1/DOUT2/DOUT3 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, the authorization will be successful only if the attached iButton is specified in the iButton list. <br/>

* 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, the authorization will be successful only if the attached iButton is specified in the iButton list. <br/>

* Ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off. <br/>

* Ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off. <br/>

* Authorization off timeout parameter is used to set the duration of how long the user has time to authorize after switching ignition on. <br/>

* Authorization off timeout parameter is used to set the duration of how long the user has time to authorize after switching the ignition ON. <br/>

* iButton list gives the ability to use the vehicle for 1000 specific iButton owners (specified in iButton list). Selected DOUT is controlled by scenario for user needs, to manage buzzer, LED, etc.

* iButton list gives the ability to use the vehicle for 1000 specific iButton owners (specified in iButton list). Selected DOUT is controlled by scenario for user needs, to manage buzzer, LED, etc.

<!--

<!--

-->

-->

<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>

{{{txt_br|<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}

==iButton Read Notification==

==iButton Read Notification==

{{{pic_jamming|[[Image:I button.JPG|300px|right]]}}}

{{{pic_ibutton|[[Image:I button.JPG|300px|right]]}}}

* If the scenario is enabled, when iButton is attached and is successfully read, configured DOUT goes ON for configurable amount of time (min: 0.00 s; max: 5.00 s; default: 0.2 s). <br>

* If the scenario is enabled, when iButton is attached and is successfully read, configured DOUT goes ON for configurable amount of time (min: 0.00 s; max: 5.00 s; default: 0.2 s). <br>

'''Confirmation about successful iButton identification with configured DOUT ON indication'''

'''Confirmation about successful iButton identification with configured DOUT ON indication'''

If DOUTX iButton read notification parameter is configured to control DOUTX and DOUTX is ON, then when new iButton is successfully read, DOUTX is turned OFF for 0,5 seconds and then turned back ON. By “new iButton” it is meant that the value read by (let’s say Driver’s) iButton reader is either different compared to what was read before or it’s the first time this iButton is read.

If DOUTX iButton read notification parameter is configured to control DOUTX and DOUTX is ON, then when new iButton is successfully read, DOUTX is turned OFF for 0,5 seconds and then turned back ON. By “new iButton” it is meant that the value read by (let’s say Driver’s) iButton reader is either different compared to what was read before or it’s the first time this iButton is read.

==Short burst data settings==

==Short burst data settings==

{{{short_burst|[[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 the server. This means that some data can be sent from FM device to the server through satellites.  

FMB640 will enable satellite mode only if device can not send data via GPRS. Satellite mode has his own Save/Send period. If timeout is set to 0 no periodic records will be made. It is not recommended to save records often because of satellites traffic price. 8 kilobytes monthly data limit is hardcoded in firmware. If data limit is reached – data limit counter will reset automatically only on next month first day or you can rest counter by SMS command “sbdlimitsreset”.

[[FMB640]] will enable satellite mode only if a device can not send data via GPRS. Satellite mode has his own Save/Send period. If timeout is set to 0 no periodic records will be made. It is not recommended to save records often because of satellite traffic prices. 8 kilobytes monthly data limit is hardcoded in firmware. If the data limit is reached – the data limit counter will reset automatically only on next month first day or you can rest counter by SMS command ''“sbdlimitsreset”''.

In addition, you can select which IO element can generate Satellite record. In order to do that you need to go to IO tab select IO record priority Panic and check checkbox “Satellite I/O” what you want to get that data through satellites if there is no GSM connection.

In addition, you can select which IO element can generate Satellite records. In order to do that you need to go to I/O tab select IO record priority Panic and check the checkbox “Satellite I/O” what you want to get that data through satellites if there is no GSM connection.

Record which will be sent through Iridium satellites network will be different than the regular record. It will contain: 4 bytes timestamp, 3 bytes longitude, 3 bytes latitude, 1 byte record generation info, 1 byte DIN,DOUT info, 1 byte speed value.

Record which will be sent through the Iridium satellite network will be different than the regular record. It will contain 4 bytes timestamp, 3 bytes longitude, 3 bytes latitude, 1 byte record generation info, 1 byte DIN, DOUT info, 1 byte speed value.

{{{pic_overspeeding|[[Image:connection.JPG|300px|center]]}}}

{{{pic_connection|[[Image:connection.JPG|300px|center]]}}}

'''NOTE''': Port1/2 cable from FM package can be used for TSM232 connection. For this you need to cut a D-SUB connector and connect wires according instruction above (PIN 4 to TSM GND, PIN5 to TSM Rx, PIN6 to TSM Tx).

'''NOTE''': Port1/2 cable from FM package can be used for [[TSM232]] connection. For this you need to cut a D-SUB connector and connect wires according to the instruction above (PIN 4 to TSM GND, PIN5 to TSM Rx, PIN6 to TSM Tx).

{{{pic_overspeeding|[[Image:connector.JPG|600px|center]]}}}

{{{pic_connector|[[Image:connector.JPG|600px|center]]}}}

'''NOTE''': SBD data is limited to 8000 Bytes per month. For firmware with bigger SBD data limit, please ask your sales manager.

'''NOTE''': SBD data is limited to 8000 Bytes per month. For firmware with a bigger SBD data limit, please ask your sales manager.

If data limit is reached you can reset it with SMS command “sbdlimitsreset”

If the data limit is reached you can reset it with SMS command ''“sbdlimitsreset”''.