Template:FMU Features settings: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Eco/Green Driving== | ==Eco/Green Driving== | ||
[[Image:{{{model| | [[Image:{{{model|FMU1YX}}}_Eco_Green_Driving.png|{{{eco_green|size}}}|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. | 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. | ||
| Line 38: | Line 38: | ||
===Data output=== | ===Data output=== | ||
---- | ---- | ||
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| | 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|FMU1YX}}} 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.{{{text_dout|<br/>{{{dout|info}}}}}} | ||
===Auto calibration=== | ===Auto calibration=== | ||
| Line 45: | Line 45: | ||
# The vehicle is stopped. | # The vehicle is stopped. | ||
# There is a straight road ahead. | # There is a straight road ahead. | ||
# Send SMS ''"auto_calibrate:set"'' to the {{{model_2| | # Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMU}}} device. | ||
# Accelerate to >30 km/h for 5 sec. | # Accelerate to >30 km/h for 5 sec. | ||
# {{{model_2| | # {{{model_2|FMU}}} will send a response when calibration is completed successfully. | ||
Calibration is saved to internal flash memory, which means it will stay after a reset. | 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| | To check auto-calibration status send a following short text message to the {{{model_2|FMU}}} device: ''"auto_calibrate:get"''. | ||
==Over Speeding== | ==Over Speeding== | ||
[[Image:{{{model| | [[Image:{{{model|FMU1YX}}}_Over_Speeding.png|{{{over_speed|size}}}|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.<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}}} | ||
| Line 60: | Line 60: | ||
==Jamming== | ==Jamming== | ||
[[Image:{{{model| | [[Image:{{{model|FMU1YX}}}_Jamming.png|frameless|{{{jamming|size}}}|right]] | ||
When GSM signal 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/>{{{jamming_dout|info}}} | When GSM signal 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/>{{{jamming_dout|info}}} | ||
| Line 69: | Line 69: | ||
{{{dout_control_via_call_feature|== DOUT Control Via Call== | {{{dout_control_via_call_feature|== DOUT Control Via Call== | ||
[[Image:{{{model| | [[Image:{{{model|FMU1YX}}}_DOUT_Control_Via_Call.png|{{{dout_control_via_call|size}}}|right]] | ||
Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/> | 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: | Call control functionality is following: | ||
* When {{{model| | * When {{{model|FMU1YX}}} is configured to control {{{text_dout|DOUT1/DOUT2}}} the device waits for an incoming call from a configured secure number. If a call is received {{{model|FMU1YX}}} turns on {{{text_dout|DOUT1/DOUT2}}} for a user defined ''Duration Timeout''. If duration timeout set to "0" {{{text_dout|DOUT1/DOUT2}}} will be OFF. | ||
* {{{text_dout|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din|digital input 1, digital input 2 or digital input 3}}}. | * {{{text_dout|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din|digital input 1, digital input 2 or digital input 3}}}. | ||
* {{{text_dout|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to maximum value (2147483647) which is about 68 years. | * {{{text_dout|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to maximum value (2147483647) which is about 68 years. | ||
| Line 82: | Line 82: | ||
{{{immobilizer_feature|==Immobilizer== | {{{immobilizer_feature|==Immobilizer== | ||
[[Image:{{{model| | [[Image:{{{model|FMU1YX}}}_Immobilizer.png|{{{immobilizer|size}}}|right]] | ||
If ''DOUT Control'' is disabled, scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout|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.<br/>{{{immobilizer_dout|info}}} | If ''DOUT Control'' is disabled, scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID is attached, {{{text_dout|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.<br/>{{{immobilizer_dout|info}}} | ||
| Line 91: | Line 91: | ||
{{{ibutton_feature|==iButton Read Notification== | {{{ibutton_feature|==iButton Read Notification== | ||
[[Image:{{{model| | [[Image:{{{model|FMU1YX}}}_iButton_Read_Notification.png|{{{ibutton_read_notification|size}}}|right]] | ||
This functionality allows user to see when iButton is read. {{{text_dout|DOUT1/DOUT2}}} turns on for a configured duration and after DOUT ON duration ends {{{text_dout|DOUT1/DOUT2}}} does not turn on even if iButton is left attached.<br/>{{{ibutton_dout|info}}} | This functionality allows user to see when iButton is read. {{{text_dout|DOUT1/DOUT2}}} turns on for a configured duration and after DOUT ON duration ends {{{text_dout|DOUT1/DOUT2}}} does not turn on even if iButton is left attached.<br/>{{{ibutton_dout|info}}} | ||
| Line 98: | Line 98: | ||
==GNSS Fuel Counter== | ==GNSS Fuel Counter== | ||
[[Image:{{{model| | [[Image:{{{model|FMU1YX}}}_GNSS_Fuel_Counter.png|{{{gnss_fuel_counter|size}}}|right]] | ||
# To configure ''Fuel Counter'' parameters use fuel consumption norms which are presented in technical documentation of the vehicle. By default speeds for these fuel consumption norms are: City – 30 km/h, Average - 60 km/h, Highway - 90 km/h. These values can be changed. | # To configure ''Fuel Counter'' parameters use fuel consumption norms which are presented in technical documentation of the vehicle. By default speeds for these fuel consumption norms are: City – 30 km/h, Average - 60 km/h, Highway - 90 km/h. These values can be changed. | ||
# When speed is higher than the highway fuel consumption speed, x% of highway fuel consumption is added every extra y km/h, by default {{{model| | # When speed is higher than the highway fuel consumption speed, x% of highway fuel consumption is added every extra y km/h, by default {{{model|FMU1YX}}} adds 20% every 50 km/h of extra speed. For example, the fuel consumption is (1.2 * (Highway Fuel Consumption)) at 140 km/h and (1.4 * (Highway Fuel Consumption)) at 190 km/h. | ||
# ''Correction coefficient'' is used to correct every value of fuel consumption which is sent to the server through an expression of ((Used Fuel) * ''Correction coefficient''). By default it is 1, with minimum and maximum values of accordingly 0.01 and 2. For example, when correction coefficient is 1 and {{{model| | # ''Correction coefficient'' is used to correct every value of fuel consumption which is sent to the server through an expression of ((Used Fuel) * ''Correction coefficient''). By default it is 1, with minimum and maximum values of accordingly 0.01 and 2. For example, when correction coefficient is 1 and {{{model|FMU1YX}}} calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server. | ||
# ''Fuel Consumption on Idling'' is used to calculate fuel consumption when ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars. | # ''Fuel Consumption on Idling'' is used to calculate fuel consumption when ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars. | ||