FXLS896xAF AN12004 - 'No Motion' vs 'Freefall'

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

FXLS896xAF AN12004 - 'No Motion' vs 'Freefall'

400件の閲覧回数
andrewneil
Contributor III

In the AN12004 Application Note, the basis for detecting  both 'No Motion' (3.2) and  'Freefall' (3.4) is that all 3 axes are within some threshold.

So that's the key to distinguishing 'No Motion' and  'Freefall' - as they're both detected on the same basis?

ラベル(1)
0 件の賞賛
3 返答(返信)

375件の閲覧回数
TomasVaverka
NXP TechSupport
NXP TechSupport

Hello Andrew,

The key to distinguishing between the two lies in the setting of the debounce time (2.55s vs. 100ms). And yes, we also recommend to use slightly different threshold values (±100mg vs. ±200mg).

BR, Tomas

 

0 件の賞賛

371件の閲覧回数
andrewneil
Contributor III

So you're just assuming that a "brief" period of "no motion" must be "freefall" ?


The other difference is that the "no motion" example uses the Data[n]-Data[n-1] reference update mode, whereas "freefall" uses the Absolute mode.

What's the significance in that?

 

0 件の賞賛

319件の閲覧回数
andrewneil
Contributor III

Still wondering about the significance of Data[n]-Data[n-1] vs Absolute reference?

 

Also, rather than using the 'AND' logic of all 3 axes, what would be the pros/cons of just using the VECM (vector magnitude) ?

0 件の賞賛