4,628
edits
Changes
FMP100 Accelerometer Features settings (view source)
Revision as of 14:00, 20 December 2021
, 14:00, 20 December 2021no edit summary
{{
{{Template:FMX Accelerometer Features settings
Template:FMB Accelerometer Features settings
|unplug_feature= ==Unplug Detection==
|model=FMP100
|pic_idling=[[Image:Fmt100 excessive idling.png|right]]
{{{pic_unplug|[[Image:unplug.gif|right]]}}}
'''In 03.25.15.Rev.122 version:'''
If unplug detection scenario is enabled, conditions to determine unplug state are checked every second.
Initially external power is checked to set device to appropriate unplug state. If external power is less than 5.25 volts, unplugged state is set, on the other hand, if external power is higher than or equal 5.25 volts, plugged state is set.
There are two configurable (id: 11502) unplug detection modes: simple and advanced.
'''If simple mode is configured:'''
*Unplug scenario changes states from plugged to unplugged, when external power is less than 5.25 volts AND unplug detection pin is high (meaning that device is pulled out of holder).<br>
*Unplug scenario changes states from unplugged to plugged, when external power is higher than or equal 5.25 volts OR unplug detection pin is low (meaning that device in pushed into the holder) OR these both conditions are true.<br>
'''If advanced mode is configured:'''
*Unplug scenario changes states from plugged to unplugged, when unplugged detected by accelerometer flag is set to true AND unplug detection pin is high (meaning that device is pulled out of holder). This unplugged detected by accelerometer flag is set to true when external power is less than 5.25 volts and measured accelerometer threshold exceeds 0.31 mg. Once accelerometer threshold exceeds 0.31 mg it is not going to be measured again until external power will be higher or equal to 5.25 volts.<br>
*Unplug scenario changes states from unplugged to plugged, when external power is higher than or equal 5.25 volts OR unplug detection pin is low (meaning that device in pushed into the holder) OR these both conditions are true.<br>
In '''03.27.02.Rev.160''' version after base update to 03.27.02.Rev.01 additional condition was introduced when calculating accelerometer measured values in configured advanced mode. This workaround came from version 03.25.15.Rev.03, if no movement detected, z axis is ignored.
<br><youtube>CjIYGWDPJ3s</youtube><br>
}}
}}