2022-02-27 09:46 AM
2022-02-28 02:09 AM
Hi,
2022-02-28 10:33 AM
Hi Petr,
In the image attached, I get non-zero accelerometer values till sample number 491. This makes sense as I have kept the sensortile kit in motion. However, after sample # 491, the acceleration values are not correct because my sensortile kit is stationary (expecting no acceleration) and I still get non-zero acceleration along the 3 axis. Why is that so? Please throw some light on this issue.
2022-03-01 12:46 AM
Could you please send me your datalog for simulations? The one you displayed in graphs would be perfect.
2022-03-05 10:39 AM
Hi @Petr S_O ,
Sorry for the late response. I have re-plotted the graphs with the same type of movement. I rotated the sensortile kit both clockwise and anticlockwise and then left it stationary after 400th sample. Please see attached graphs and corresponding datalog given in excel file. I look forward to your response. Thank you.
2022-03-07 07:26 AM
Hi Community Members,
Any guidance related to the issue will be appreciated. Looking forward to your responses.
2022-03-07 12:56 PM
2022-06-13 12:09 AM
Hi @Petr S_O
I am using Motion_DI Library for ISM330DLC sensor and getting some output. How can i validate that data and could you please log the data for longer period by changing it's positions and send us for reference. As in the above data is logged for less than 1 second. In above pic i have logged the Yaw,Pitch,Roll. data when the sensor is in steady position.
Thank you.
2022-07-14 08:51 AM
MEMS accelerometer sensor is based on sensing mass micro-element movement and position inside sensor component body. Movement of micro-element is caused by acceleration of sensor component.
This means, while in still position, only gravitation acceleration does apply to sensor component and thus the total acceleration vector is equal to gravitation acceleration of typical value:
1 g == 9.81 m/s^2
Rotation itself does not change acceleration vector size only its direction (with respect to sensor component). On contrary the linear movement adds linear acceleration vector to total acceleration vector and changes size and usually direction of resulting acceleration vector.
Looking to Datalog.xlsx data you have sent it seems X, Y, Z acceleration data are raw accelometer data converted from [mg] units to [m/s^2] units.
Calculating magnitude of acceleration:
acc = sqrt(acc_x ** 2 + acc_y ** 2 + acc_z ** 2)
for all values the results are as follows:
In case real linear acceleration results (i.e.: without gravity vector) are needed, there is output of
MotionDI library - linear_acceleration:
typedef struct
{
float rotation[MDI_NUM_AXES]; /* 6 axes yaw, pitch and roll */
float quaternion[MDI_QNUM_AXES]; /* 6 axes quaternion */
float gravity[MDI_NUM_AXES]; /* 6 axes device frame gravity */
float linear_acceleration[MDI_NUM_AXES]; /* 6 axes device frame linear acceleration */
} MDI_output_t;
See also results from DynamicInclinometer application based on MotionDI library (screenshot taken from Unicleo-GUI:(