MSP500 Accelerometer Features settings: Difference between revisions

(4 intermediate revisions by the same user not shown)

Line 11:

Note: moving forward along any axis will generate negative values. This means acceleration will generate -X values, accordingly breaking will generate X values. Same goes for other axes.

~~Configurable parameters can be found at [[{{{model|FMB1YX}}}_System_settings#Accelerometer_Auto_Calibration|System Settings Accelerometer Auto Calibration]]~~

Commands that can be used during calibration:

Line 29:

Line 27:

|}

</center>

====Auto calibration ~~before firmware version 03.25.07.Rev.00.~~====

====Auto calibration Source====

Accelerometer auto calibration functionality has one purpose - determine how ~~FMB~~ device

Accelerometer auto calibration functionality has one purpose - determine how MSP500 device

is mounted in a vehicle. After the calibration process ''eco driving'' functionality becomes active

and calibration data will be used to determine harsh acceleration, braking and cornering events.

Line 38:

Line 36:

*If the device receives an SMS/GPRS message with ''auto_calibrate:set'' text.

After functionality has started ~~FMB~~ device periodically checks current appliance GNSS,

After functionality has started MSP500 device periodically checks current appliance GNSS,

ignition and movement source parameters and if the conditions match:

Line 48:

Line 46:

Then first vector is taken. Saved vector will be considered as ground vector and it will be

used at further calibration calculations.

''Note: When ~~FMB~~ device saves first ground vector vehicle must be parked on flat ground''.

''Note: When MSP500 device saves first ground vector vehicle must be parked on flat ground''.

Crooked vector may have an impact on further calculations.

Afterwards first ground vector was taken, device analyses conditions:

Line 112:

Line 110:

{{{pic_unplug|[[Image:unplug.gif|right]]}}}

An event will be generated when {{{model|~~FMB1YX~~}}} is unplugged from {{{txt_src|external power}}} or plugged back in again.

An event will be generated when {{{model|MSP500}}} is unplugged from {{{txt_src|external power}}} or plugged back in again.

===Scenario settings===

* '''Disable''' - disable scenario.

Line 118:

Line 116:

* '''High Priority''' - module makes additional record with High priority flag and '''sends event packet immediately''' to the server by

'''GPRS'''.

* '''Panic Priority''' - triggers same actions as High priority, but if '''GPRS fails''', it sends AVL packet using '''SMS mode''' if SMS is enabled in [[{{{model|~~FMB1YX~~}}}_SMS/Call_settings#SMS_Data_Sending|SMS Data Sending]] settings.

* '''Panic Priority''' - triggers same actions as High priority, but if '''GPRS fails''', it sends AVL packet using '''SMS mode''' if SMS is enabled in [[{{{model|MSP500}}}_SMS/Call_settings#SMS_Data_Sending|SMS Data Sending]] settings.

===Eventual Records===

Line 131:

Line 129:

}}}

<youtube>CjIYGWDPJ3s</youtube>

====Limp Mode====

Scenario is used to prevent disconnection of speed sensor. When Limp Mode is activated vehicle speed will be limited to configured Limp mode max speed. In this case, speed source is GNSS speed.

To activate Limp Mode one of these conditions must be met:

External power unplugged.

Speed sensor is disconnected and sensor speed is 0 km/h (refer to Speed Sensor Voltage Ranges).

[[Image:Limp Mode.gif|center]]

Current working algorithm of the Limp Mode is described below:

[[Image:limp_mode_fsm.png|center]]

==Towing Detection==

{{{pic_Towing|[[Image:Towingdet.gif|right]]}}}

''Towing Detection'' feature helps to inform the driver about unexpected car movement when it was parked. {{{model|~~FMB1YX~~}}} generates an event when a car is being towed or lifted, for example, in a case of vehicle evacuation. {{{model|~~FMB1YX~~}}} activates the towing function when the following conditions are met:

''Towing Detection'' feature helps to inform the driver about unexpected car movement when it was parked. {{{model|MSP500}}} generates an event when a car is being towed or lifted, for example, in a case of vehicle evacuation. {{{model|MSP500}}} activates the towing function when the following conditions are met:

#Ignition (configured Ignition Source) is OFFF.

#''Activation Timeout'' is reached.

When the towing function is engaged {{{model|~~FMB1YX~~}}} monitors accelerometer data. If acceleration ''Threshold'' or ''Angle'' reach configured values for a configured ''Duration'', and Ignition is still OFF for a period of time that is longer than ''Event Timeout'', then an event is generated. When configured, ''Make Call To'' and ''Send SMS To'' functions make a call or send an SMS to a predefined phone number. The towing function will be reactivated after {{{model|~~FMB1YX~~}}} detects a change of Ignition state from ON to OFF or if the configured ''Activation Timeout'' is reached again.

When the towing function is engaged {{{model|MSP500}}} monitors accelerometer data. If acceleration ''Threshold'' or ''Angle'' reach configured values for a configured ''Duration'', and Ignition is still OFF for a period of time that is longer than ''Event Timeout'', then an event is generated. When configured, ''Make Call To'' and ''Send SMS To'' functions make a call or send an SMS to a predefined phone number. The towing function will be reactivated after {{{model|MSP500}}} detects a change of Ignition state from ON to OFF or if the configured ''Activation Timeout'' is reached again.

{{{txt_towingdout|

The digital output can be activated for a period of time to warn the driver. Output on-time is configured separately for each featuring case. For more information please refer to [[DOUT controls]]}}}.