INV_MSG_MOTION_EVENT and INV_MSG_NO_MOTION_EVENT

By karchie , 17 February 2013
Forums
SmartMotion® MEMS Motion Sensors

Hi

I want to use those motion/no-motion evets for "zero velosity update" alorithm.
It seems that no-motion detection takes a lot of time. Is there a way to adjust the sensitivity of this detection and shorten this this time?

In MotionFit SDK 4.1 the motion/no-motion update was done by interrupt. In the new 5.1 SDK it is done by the message mechanism. Is it still interrupt initiated or the message comes whenever the MSP comes back from sleep?

Thanks in advance.
Regards.

guy_mcilroy

13 years 1 month ago

Please refer to the MotionFit 5.1 API Specification document, which outlines the parameters of the no-motion interrupt. You'll need to modify the code to add this functionality, but the no-motion features are a good starting point for Zero-Velocity-Update.

phpbb Post ID
22521

markw

13 years 1 month ago

hi,

I configure the registers for zero motion interrupt (threshold and duration) in LPA mode. It seems the duration is dependent from the frequency of the accelerometer. It is not specified in the datasheet.
Is the zero motion detection module is working in LPA mode as it should work in normal mode (CYCLE_BIT = 0) ?

phpbb Post ID
22524

guy_mcilroy

13 years ago

This refers to the no-motion events available in the eMPL API, which detect with the device is put to rest, allowing calibration and estimates of velocity. This software feature is not related to the LPA. When using eMPL, the library will control the rate of the accel data, which is required to be operating in full power mode at 200 Hz.

phpbb Post ID
22527
phpbb Topic ID
15078