Template:FMB640 Features settings: Difference between revisions

From Teltonika Telematics Wiki
VisualWikitext
 
(76 intermediate revisions by 11 users not shown)
Line 1: Line 1:
==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.


{| class="wikitable"
<table class="nd-othertables" style="width: 68%;">
|+
<tr>
! style="width: 150px; background: black; color: white;" | Parameter name
        <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
! style="width: 500px; background: black; color: white;" | Description
        <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
|-
    </tr>
! style="text-align: left; vertical-align: top;" | ''Scenario Settings''
<tr>
| style="text-align: left; vertical-align: top;" | Enable/Disable Green driving functionality.
        <td style="width: 8%; text-align:left;">Output Control</td>
|-
        <td style="width: 8%; text-align:left">Enable/Disable Green driving functionality and Activate/Deactivate DOUT.</td>
! style="text-align: left; vertical-align: top;" | ''Max Acceleration''
    </tr>
| style="text-align: left; vertical-align: top;" | Value which can be reached while accelerating without triggering harsh acceleration event.
<tr>
|-
        <td style="width: 8%; text-align:left">Max Acceleration</td>
! style="text-align: left; vertical-align: top;" | ''Max Braking Acceleration''
        <td style="width: 8%; text-align:left">Value which can be reached while accelerating without triggering harsh acceleration event.</td>
| style="text-align: left; vertical-align: top;" | Value which can be reached while braking without triggering harsh braking event.
    </tr>
|-
<tr>
! style="text-align: left; vertical-align: top;" | ''Max Cornering Acceleration''
        <td style="width: 8%; text-align:left">Max Braking Acceleration</td>
| style="text-align: left; vertical-align: top;" | Value which can be reached while cornering without triggering harsh cornering event.
        <td style="width: 8%; text-align:left">Value which can be reached while braking without triggering harsh braking event.</td>
|-
    </tr>
! style="text-align: left; vertical-align: top;" | ''Source''
<tr>
| style="text-align: left; vertical-align: top;" | Which source (GPS or accelerometer) data will be collected from.
        <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 data will be collected from:
* '''GNSS''' - When selected source (11007) is GPS device calculates harsh driving values from GPS data at 1 Hz frequency. This means green driving time accuracy is 1s (no ms). Acceleration is calculated every 1 second, based on speed difference between GPS samples. Vehicle speed must be equal or greater than 10 km/h for acceleration/braking and equal or greater than 30 km/h for cornering.<br>
* '''Accelerometer''' – Accelerometer data will be used to detect harsh driving. (This algorithm is from FMB device family). Accelerometer calibration needs to be performed with ''“auto_calibrate:set”'' command. <br>
*  '''GNSS Algorithm A1''' – GPS data will be used to detect harsh driving. (This algorithm is used in FMA11 devices). The main difference from FM53 is cornering detection which uses advanced math to more precisely calculate harsh cornering value across different vehicle speeds. <br>
* '''Accelerometer Algorithm A1''' - Accelerometer data will be used to detect harsh driving. (This algorithm is used in FMA11 device family) <br>
<b>Note:</b> To use ''“Accelerometer Algorithm A1”'' option user need to install device as in Figure 1.
</td>
    </tr>
</table>
{{{pic_accelerometerposition|[[Image:FMB640accelerometerposition.png|300px|right]]}}} {{{model|}}} 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.


===Data output===
===Auto calibration===
----
----
Data from accelerometer/GPS are continiously monitored and processed and are used to decide whether a harsh event has occured. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server ({{{model|FMB640}}} must be properly configured in order to send the record). Event value is multiplied by 10 before sending/saving record to get more precision when displaying data.{{{text_dout|<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.}}}
The auto-calibration process is the following:
# The vehicle is stopped.
# There is a straight road ahead.
# Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMB}}} device.
# Accelerate to >30 km/h for 5 sec.
# {{{model_2|FMB}}} 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 {{{model_2|FMB}}} device: ''"auto_calibrate:get"''.


==Over Speeding==
==Over Speeding==


{{{pic_overspeeding|[[Image:FMB640 over speeding.png|300px|right]]}}}
{{{pic_overspeeding|[[Image:FMB640_overspeeding.png|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.<br/>{{{over_speeding_dout|info}}}
<br/><br/><br/><br/><br/><br/><br/>
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/>


==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.
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>


==Immobilizer==
==DOUT Control via Call==
 
{{{pic_DOUTCONTROL|[[Image:FMB640 DOUT.png|300px|right]]}}}
 
Activates DOUT on incoming call. <br/>
The scenario is activated and digital output is ON when a call is received from a number which is in authorized numbers list.
Call control functionality: <br/>
* When FMB64 is configured to control DOUT1/DOUT2/DOUT3/DOUT4 device waits for an incoming call from the configured secure number. If the call is received FMB64 turns on DOUT1/DOUT2/ DOUT3/DOUT4 for user-defined Duration timeout (s). If the Duration timeout set to „0“(s), DOUT1/DOUT2/ DOUT3/DOUT4 will be OFF. <br/>
* DOUT1/ DOUT2/DOUT3/DOUT4 can be turned off by Duration timeout (s) or by digital input 1, digital input 2, digital input 3, or digital input 4 (DOUT deactivation settings). <br/>
* DOUT1/DOUT2/DOUT3/DOUT4 can be turned off before Duration timeout (s) by selected DIN (DOUT deactivation settings).<br/>
* DOUT1/DOUT2/DOUT3/DOUT4 always will be ON, if DOUT deactivation set to DIN1 for example, but DIN1 will be never turned ON or set Duration timeout to Max value (2147483647) it is about 68 years.
<br/><br/><br/>
 
==Authorized driving/Immobilizer==


{{{pic_jamming|[[Image:FMB640_immobilizer.png|300px|right]]}}}
{{{pic_immobilizer|[[Image:FMB640_authorizedD.png|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.
*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).
<br/><br/><br/><br/><br/><br/>
* 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/>
* 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 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.
<!--
* Buzzer duration
New parameter implemented - Buzzer duration. Measured in minutes. <br>
After the ignition is turned ON, the configured immobilizer output control parameter turns ON (unless it's Disabled or configured as no DOUT control). DOUT can be deactivated by the iButton read from iButton1 or iButton2 readers or if the Buzzer duration parameter timeout occurs. Usage example: Driver or passenger enters the vehicle, turns the ignition ON (DIN1=1) and buzzer (DOUT2) is also turned ON. The buzzer will be ON as long as Buzzer Duration timeout occurs or until iButton will be successfully read.
* Passenger iButton
New IO element Passenger iButton added. <br>
New parameter Passenger iButton source implemented. Min: none (0); Max: DIN4 (4); Default: none (0). Parameter configuration id: 11714.
In order to distinguish driver and passenger iButtons while both iButton readers are on the same 1-wire line, special logic applied: if there is no voltage on configured Passenger iButton source DINX then it is taken that Passenger iButton is attached. The value of reading Passenger iButton ID is saved to Passenger iButton IO element. This functionality works with an immobilizer scenario only.
-->
{{{txt_br|<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}


==Authorized driving==
==iButton Read Notification==


{{{pic_jamming|[[Image:FMB640_authorizedD.png|300px|right]]}}}
[[Image:IButton_Read_Notification .png|{{{general|size}}}||right]]
Output control parameter lets the user choose which DOUT will iButton blink. After connecting iButton, DOUT will blink for a period of time, which is configured in DOUT ON Duration parameter. The iButton List checking parameter configures whether the device reads the iButton ID from iButton list or not. For example if configured as Enabled, device will not blink DOUT unless the iButton is in the iButton list.
If Depend on Ignition parameter is enabled, then Output will be triggered only if ignition is off (in addition to being in a list if iButton List Checking is also enabled).
Output control examples when iButton is detected (if None is selected in Output Control – all of the following steps will be skipped):
 
*If both iButton List Checking and Depend on Ignition are disabled – Output is triggered.
*If iButton List Checking is enabled and Depend on Ignition is disabled – Output is triggered only if iButton is in the list.
*If iButton List Checking is disabled but Depend on Ignition is enabled – Output is triggered only if ignition is off.
*If both iButton List Checking and Depend on Ignition are enabled – Output will trigger if iButton is in the list and ignition is off.
 
iButton Read Notification parameters:
 
*Output control – available scenario settings for module Digital output activation/deactivation
*DOUT ON duration – a value in seconds, for how long {{{text_dout|DOUT1/DOUT2/DOUT3}}} should be active.
*iButton List checking - parameter configures that device reads the iButton ID from list or not.
*Depend on Ignition - Output will be triggered only if ignition is off
<br/><br/>
 
==Short burst data settings==
 
 
{{{model|}}} 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.
 
In order to properly connect the Iridium device to {{{device|}}}, Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally '''Pin No. 6''' - power control (reference in the image below) must be connected to one of the {{{model|}}} DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information about SBD can be found here [[{{{model|}}} _Short_Burst_Data|Short Burst Data]].
 
Iridium Edge pinout and RS232 COM 1/2 connection:
 
[[File:Iridium Edge pinout.png|left]]
[[File:FMX640 and RS232 illustration v1.2.png|right|450x201px]]
<br></br><br></br><br></br><br></br><br></br><br></br>
[[File:SBD settings.gif|right]]
When the Iridium edge device is connected '''''Power control DOUT''''' configures DOUT pin which can control Iridium Edge ON/OFF pin. Configure if DOUT pin is connected. Respective power control DOUT to which the Iridium device's ''PIN6'' is connected must be selected.
 
 
'''''Save/Send period''''' configures how long will FMB device wait after losing the signal to generate SBD packet. If the signal is not recovered, it will send it indefinitely (or till the SBD Upload limit is reached, if such is set).
 
'''''SBD Upload Limit''''' is configurable and resets every month. This option can ensure that no additional data is used so that no unexpected costs are experienced by the customer. The default value is 8000 (for 8KB plan). This option can be disabled by setting the Upload limit to 0. The monthly data usage counter can be reset by using the SMS/GPRS command - '''sbdlimitsreset'''.
 
'''''SBD IO source''''' configures IO source which can trigger SBD record saving.  9 elements can generate an Alarm for SDB sending. These elements are:
* Digital input 1
* Digital input 2
* Digital input 3
* Digital input 4
* Digital output 1
* Digital output 2
* Digital output 3
* Digital output 4
* Speed
<br></br>
Configurator parameter IDs and their explanation:
{| class="nd-othertables_2" style="width:100%;"
|- style="font-weight:bold; text-align:center;"
! '''Parameter ID'''<br />
! '''Parameter name'''
! colspan="3" | '''Values'''
! '''Explanation'''
|- style="font-weight:bold; text-align:center;"
| style="font-weight:normal;" |
| style="font-weight:normal;" |
| '''Min'''
| '''Max'''
| '''Default'''
| style="font-weight:normal;" |
|-
| 99420
| Iridium Edge
| 0
| 1
| 0
| This parameter enables or disables Iridium Edge functionality
|-
| 99421
| Save/Send period
| 0
| 1440
| 1440
| This parameter lets to configure Iridium Edge sending period
|-
| 99422
| SBD IO source'''*'''
| 0
| 8
| 0
| SBD IO elements which when enabled are included into the SBD record
|-
| 99423
| SBD UploadLimit
| 0
| 30000
| 8000
| Limit to save user from exceeding the monthly plan. Max limit of 30000 due to 30KB plan. If set to 0 – limit will be off.
|-
| 99424
| Power control DOUT
| 1
| 5
| 0
| Device DOUT which can control ON/OFF pin of the Iridium Edge
|-
| 151
| RS232 Mode
| 0
| 23
| 0
| RS-232 mode selection. "Satellite backup" - 15
|}
 
<br></br>
'''*''' SBD IO source parameter is configured with bitmasks:
*eSBD_IO_Bit_Disabled    = 0x00,
*eSBD_IO_Bit_Din1        = 0x01,
*eSBD_IO_Bit_Din2        = 0x02,
*eSBD_IO_Bit_Din3        = 0x04,
*eSBD_IO_Bit_Din4        = 0x08,
*eSBD_IO_Bit_Do1          = 0x10,
*eSBD_IO_Bit_Do2          = 0x20,
*eSBD_IO_Bit_Do3          = 0x40,
*eSBD_IO_Bit_Do4          = 0x80,
*eSBD_IO_Bit_Speed        = 0x100
<br></br>
For example: to enable Din1, Din3 and Do4: 0x01 + 0x04 + 0x80 = 0x85 convert to decimal --> 133.
 
==Impulse Counters Settings==
 
{{{Impulse counter settingsFM6|[[Image:Impulse counter settingsFM6.png|300px|right]]}}}
 
Pulse counter functionality enables the FMX640 devices to count digital impulses going to Digital and Analog Inputs. This means that these inputs of the FMX640 devices can now be used for precise fuel flow meter data reading. Impulse based fuel usage monitoring is much more accurate than a different type of fuel metering sensors and it makes the FMX640 devices a perfect solution for high fuel usage machines like cranes, construction vehicles, mining machines, agriculture equipment.
<br>
<br>
'''How does it work?'''
<br>
When "Impulse Counter 1/2 input" is selected and "Fuel Counter/Impulse Counter 2" IO elements are enabled, device will count every input state change to HIGH and send the counted number with the next record. Pulse counter value is reset after sending the record.
<br>
'''NOTE''': Impulse Counters feature is available from FW ver. 01.02.02
------
'''I/O elements''' - Each counter has a corresponding IO elements for "Impulse Frequency" - value in Hz and "Impulse RPM" - impulse count per minute.
<br>
<br>
[[Image:Image-2021-09-07-18-10-28-631.png]]
<br>
<br>
<br>
<br>
----
'''Additionally''' - some fuel meters have a return flow counter as well:
<br>
[[File:400px-FMB640 Impulse meter.png]]
<br>
<br>
In this case - you can select which inputs are used for direct (''Impulse counter 1'') and return (''Impulse counter 2'') lines and enable "Return Flow" - when this parameter is enabled - "Fuel Counter" IO element will have a value of Direct Flow impulses substracted by Return Flow impulses.


Gives ability to use vehicle for 500 specific iButton owners (specified in iButton list). Selected DOUT is controlled by scenario for user needs, to manage buzzer, LED etc.
For example:
{{{template_link|}}}
<br>
* Direct Flow=50 impulses.
* Return Flow=10 impulses
* Fuel Counter=40 - if "Return Flow" is enabled.
<br>
Note that each Input has a specific requirements for signal frequency and threshold:
<table class="nd-othertables_2" style="width: 30%;">
<tr>
        <th style="width: 10%; text-align:center; vertical-align:middle;">Input</th>
        <th style="width: 10%; text-align:center; vertical-align:middle;">Max frequency (Hz)</th>
        <th style="width: 10%; text-align:center; vertical-align:middle;">Min Voltage threshold (V)</th>


{{{par_dout|==DOUT controls==
    </tr>
Please refer to [[FMB640 DOUT controls|DOUT controls]].}}}
        <tr>
        <td style="width: 10%; text-align:center; vertical-align:middle;">DIN1</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">50</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">7.5</td>
    </tr>
        <tr>
        <td style="width: 10%; text-align:center; vertical-align:middle;">DIN2</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">30 000</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
    </tr>
        <tr>
        <td style="width: 10%; text-align:center; vertical-align:middle;">DIN3</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">30 000</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
    </tr>
        <tr>
        <td style="width: 10%; text-align:center; vertical-align:middle;">DIN4</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">30 000</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
    </tr>
        <tr>
        <td style="width: 10%; text-align:center; vertical-align:middle;">AIN1</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">10 000</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
    </tr>
        <tr>
        <td style="width: 10%; text-align:center; vertical-align:middle;">AIN2</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">10 000</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
    </tr>
        <tr>
        <td style="width: 10%; text-align:center; vertical-align:middle;">AIN3</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">10 000</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
    </tr>
        <tr>
        <td style="width: 10%; text-align:center; vertical-align:middle;">AIN4</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">10 000</td>
        <td style="width: 10%; text-align:center; vertical-align:middle;">2.5</td>
    </tr>
</table>

Latest revision as of 16:15, 14 November 2022

Green Driving

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/s2 units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below the set parameter value.
Parameters used with Green Driving functionality are given in a table below.

Parameter name Description
Output Control Enable/Disable Green driving functionality and Activate/Deactivate DOUT.
Max Acceleration Value which can be reached while accelerating without triggering harsh acceleration event.
Max Braking Acceleration Value which can be reached while braking without triggering harsh braking event.
Max Cornering Acceleration Value which can be reached while cornering without triggering harsh cornering event.
Source Which source data will be collected from:
  • GNSS - When selected source (11007) is GPS device calculates harsh driving values from GPS data at 1 Hz frequency. This means green driving time accuracy is 1s (no ms). Acceleration is calculated every 1 second, based on speed difference between GPS samples. Vehicle speed must be equal or greater than 10 km/h for acceleration/braking and equal or greater than 30 km/h for cornering.
  • Accelerometer – Accelerometer data will be used to detect harsh driving. (This algorithm is from FMB device family). Accelerometer calibration needs to be performed with “auto_calibrate:set” command.
  • GNSS Algorithm A1 – GPS data will be used to detect harsh driving. (This algorithm is used in FMA11 devices). The main difference from FM53 is cornering detection which uses advanced math to more precisely calculate harsh cornering value across different vehicle speeds.
  • Accelerometer Algorithm A1 - Accelerometer data will be used to detect harsh driving. (This algorithm is used in FMA11 device family)

Note: To use “Accelerometer Algorithm A1” option user need to install device as in Figure 1.

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.

Auto calibration

The auto-calibration process is the following:

  1. The vehicle is stopped.
  2. There is a straight road ahead.
  3. Send SMS "auto_calibrate:set" to the FMB device.
  4. Accelerate to >30 km/h for 5 sec.
  5. FMB 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 FMB device: "auto_calibrate:get".

Over Speeding

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.
Scenario is active until detected speed decreases below the set parameter value.
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.




Jamming

When 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.
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.









DOUT Control via Call

Activates DOUT on incoming call.
The scenario is activated and digital output is ON when a call is received from a number which is in authorized numbers list. Call control functionality:

  • When FMB64 is configured to control DOUT1/DOUT2/DOUT3/DOUT4 device waits for an incoming call from the configured secure number. If the call is received FMB64 turns on DOUT1/DOUT2/ DOUT3/DOUT4 for user-defined Duration timeout (s). If the Duration timeout set to „0“(s), DOUT1/DOUT2/ DOUT3/DOUT4 will be OFF.
  • DOUT1/ DOUT2/DOUT3/DOUT4 can be turned off by Duration timeout (s) or by digital input 1, digital input 2, digital input 3, or digital input 4 (DOUT deactivation settings).
  • DOUT1/DOUT2/DOUT3/DOUT4 can be turned off before Duration timeout (s) by selected DIN (DOUT deactivation settings).
  • DOUT1/DOUT2/DOUT3/DOUT4 always will be ON, if DOUT deactivation set to DIN1 for example, but DIN1 will be never turned ON or set Duration timeout to Max value (2147483647) it is about 68 years.




Authorized driving/Immobilizer

  • 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 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.
  • Ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off.
  • Authorization off timeout parameter is used to set the duration of how long the user has time to authorize after switching the ignition ON.
  • 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 Read Notification

Output control parameter lets the user choose which DOUT will iButton blink. After connecting iButton, DOUT will blink for a period of time, which is configured in DOUT ON Duration parameter. The iButton List checking parameter configures whether the device reads the iButton ID from iButton list or not. For example if configured as Enabled, device will not blink DOUT unless the iButton is in the iButton list. If Depend on Ignition parameter is enabled, then Output will be triggered only if ignition is off (in addition to being in a list if iButton List Checking is also enabled). Output control examples when iButton is detected (if None is selected in Output Control – all of the following steps will be skipped):

  • If both iButton List Checking and Depend on Ignition are disabled – Output is triggered.
  • If iButton List Checking is enabled and Depend on Ignition is disabled – Output is triggered only if iButton is in the list.
  • If iButton List Checking is disabled but Depend on Ignition is enabled – Output is triggered only if ignition is off.
  • If both iButton List Checking and Depend on Ignition are enabled – Output will trigger if iButton is in the list and ignition is off.

iButton Read Notification parameters:

  • Output control – available scenario settings for module Digital output activation/deactivation
  • DOUT ON duration – a value in seconds, for how long DOUT1/DOUT2/DOUT3 should be active.
  • iButton List checking - parameter configures that device reads the iButton ID from list or not.
  • Depend on Ignition - Output will be triggered only if ignition is off



Short burst data settings

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.

In order to properly connect the Iridium device to , Iridium has to be connected to the device via RS-232 - COM1 or COM2 (with RJ-45 connector, where 4 pin is GND, 5 pin is RS232 Rx and 6 PIN is RS232 Tx). Additionally Pin No. 6 - power control (reference in the image below) must be connected to one of the DOUTs (1/2/3/4), in order to allow the device to power ON/OFF Iridium device on demand. More information about SBD can be found here Short Burst Data.

Iridium Edge pinout and RS232 COM 1/2 connection:













When the Iridium edge device is connected Power control DOUT configures DOUT pin which can control Iridium Edge ON/OFF pin. Configure if DOUT pin is connected. Respective power control DOUT to which the Iridium device's PIN6 is connected must be selected.


Save/Send period configures how long will FMB device wait after losing the signal to generate SBD packet. If the signal is not recovered, it will send it indefinitely (or till the SBD Upload limit is reached, if such is set).

SBD Upload Limit is configurable and resets every month. This option can ensure that no additional data is used so that no unexpected costs are experienced by the customer. The default value is 8000 (for 8KB plan). This option can be disabled by setting the Upload limit to 0. The monthly data usage counter can be reset by using the SMS/GPRS command - sbdlimitsreset.

SBD IO source configures IO source which can trigger SBD record saving. 9 elements can generate an Alarm for SDB sending. These elements are:

  • Digital input 1
  • Digital input 2
  • Digital input 3
  • Digital input 4
  • Digital output 1
  • Digital output 2
  • Digital output 3
  • Digital output 4
  • Speed



Configurator parameter IDs and their explanation:

Parameter ID
 Parameter name Values Explanation
Min Max Default
99420 Iridium Edge 0 1 0 This parameter enables or disables Iridium Edge functionality
99421 Save/Send period 0 1440 1440 This parameter lets to configure Iridium Edge sending period
99422 SBD IO source* 0 8 0 SBD IO elements which when enabled are included into the SBD record
99423 SBD UploadLimit 0 30000 8000 Limit to save user from exceeding the monthly plan. Max limit of 30000 due to 30KB plan. If set to 0 – limit will be off.
99424 Power control DOUT 1 5 0 Device DOUT which can control ON/OFF pin of the Iridium Edge
151 RS232 Mode 0 23 0 RS-232 mode selection. "Satellite backup" - 15



* SBD IO source parameter is configured with bitmasks:

  • eSBD_IO_Bit_Disabled = 0x00,
  • eSBD_IO_Bit_Din1 = 0x01,
  • eSBD_IO_Bit_Din2 = 0x02,
  • eSBD_IO_Bit_Din3 = 0x04,
  • eSBD_IO_Bit_Din4 = 0x08,
  • eSBD_IO_Bit_Do1 = 0x10,
  • eSBD_IO_Bit_Do2 = 0x20,
  • eSBD_IO_Bit_Do3 = 0x40,
  • eSBD_IO_Bit_Do4 = 0x80,
  • eSBD_IO_Bit_Speed = 0x100



For example: to enable Din1, Din3 and Do4: 0x01 + 0x04 + 0x80 = 0x85 convert to decimal --> 133.

Impulse Counters Settings

Pulse counter functionality enables the FMX640 devices to count digital impulses going to Digital and Analog Inputs. This means that these inputs of the FMX640 devices can now be used for precise fuel flow meter data reading. Impulse based fuel usage monitoring is much more accurate than a different type of fuel metering sensors and it makes the FMX640 devices a perfect solution for high fuel usage machines like cranes, construction vehicles, mining machines, agriculture equipment.

How does it work?
When "Impulse Counter 1/2 input" is selected and "Fuel Counter/Impulse Counter 2" IO elements are enabled, device will count every input state change to HIGH and send the counted number with the next record. Pulse counter value is reset after sending the record.
NOTE: Impulse Counters feature is available from FW ver. 01.02.02

I/O elements - Each counter has a corresponding IO elements for "Impulse Frequency" - value in Hz and "Impulse RPM" - impulse count per minute.





Additionally - some fuel meters have a return flow counter as well:


In this case - you can select which inputs are used for direct (Impulse counter 1) and return (Impulse counter 2) lines and enable "Return Flow" - when this parameter is enabled - "Fuel Counter" IO element will have a value of Direct Flow impulses substracted by Return Flow impulses.

For example:

  • Direct Flow=50 impulses.
  • Return Flow=10 impulses
  • Fuel Counter=40 - if "Return Flow" is enabled.


Note that each Input has a specific requirements for signal frequency and threshold:

Input Max frequency (Hz) Min Voltage threshold (V)
DIN1 50 7.5
DIN2 30 000 2.5
DIN3 30 000 2.5
DIN4 30 000 2.5
AIN1 10 000 2.5
AIN2 10 000 2.5
AIN3 10 000 2.5
AIN4 10 000 2.5
Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Template:FMB640_Features_settings&oldid=77888"