SmartMotion® MEMS Motion Sensors

Hi,
DMP_FEATURE_ANDROID_ORIENT allows 4 possibilities defined in:
inv_mpu_dmp_motion_driver.h
#define ANDROID_ORIENT_PORTRAIT (0x00)
#define ANDROID_ORIENT_LANDSCAPE (0x01)
#define ANDROID_ORIENT_REVERSE_PORTRAIT (0x02)
#define ANDROID_ORIENT_REVERSE_LANDSCAPE (0x03)

I need all 6 possibilities like detecting 6 sides of a cube.
Is there a possibility to get 6 orinetation ? How can i do to modify the code (adding mask) to get all 6 sides?
Thanks in advance.

I am trying to use the motion_driver_6.12 with a teensy 3.1.
Now as soon as inv_execute_on_data with INV_PRIORITY_QUATERNION_GYRO_ACCEL as parameter is called my program get stuck and nothing happens any more.
To be more precise the last call I could track was "result = inv_data_builder.process[kk].func(&sensors);" which I assume calls a function in the compiled
libmpllib.

Calling inv_enable_fast_nomot does lead to "no response" as well but I am not sure yet if this is due to the same problem.

Those features are enabled:

Hi,
I am having trouble setting up the orientation matrix, defined initially as:

signed char gyro_orientation[9] = { 1, 0, 0,
0, 1, 0,
0, 0, 1};

This works fine for the sensor flat relative to gravity but how do I modify this matrix for a sensor that is mounted vertically?

Motion driver 6.0
MPU9150

Thank you

Rich

Hi! I have MPU-9255, what kind of data I can get from DMP? Actualy I want to use 9255 instead of 9250. Is it possible?

I'm porting Motion Driver to STM32F429-Discovery

I'm using gcc-arm-none-eabi-4_9-2015q3 from launchpad

gcc reported :

arm-none-eabi/lib/armv7e-m/fpu/libm.a(lib_a-wf_sqrt.o): In function sqrtf':
wf_sqrt.c:(.text.sqrtf+0x76): undefined reference to__aeabi_d2f'

but I tried use sqrt(20.0f) it worked. Don't know why the use in DMP (it seems to be usage in mlmath.c) failed to build.

my options for gcc

Hi,

With the mpu6500, do I need to activate both the gyroscope & the accelerometer to have the pedometer feature fully operational ?
The step counting results greatly differs with or without the gyroscope sensor activated.

With kind regards,
Paul

HI,
Currently DMP sensor fusion works only with gyro at +-2000dps and accel +-2G. Is there any plans to make a release where DMP works at accel value +/- 4G/8G?
Regards
Puneet

hi everybody,

I have buy a mcu6050, and i would like to programm the dmp.
To do it I have download the last pakage with the source folder with the files : inv_mpu_dmp_motion_driver etc...
It is say that we can replace the i2c_write method by another.
As my application is on raspberry pi, i would use wiringPi lib.

source code inv_mpu.c:
int mpu_write_mem(unsigned short mem_addr, unsigned short length,
unsigned char *data)
{
unsigned char tmp[2];

Hi,

We are using MPU9250 in our wearable smart watch application. Just wanted to confirm with you whether the placement of this sensor on bottom of PCB is acceptable ?

Our understanding is that if we place the IC in the bottom, the X,Y and Z readings will be negated and requires software correction / modifications. [i.e the value read X (-1)]

Need your help to know whether our understanding is right!

Regards,
Naveen Kumar S B
naveen.b@aricent.com

Hello everyone,

I've a small doubt about the quaternion data validation of MPU 9250.

When I place two devices on a table and record the data, as per my understanding I should receive same data from both the motion processors. Because, MPU considers the earth coordinate system as its coordinate system. But they record different data, i.e., different angles.
So, when both are placed on a table, they should record the same data, and the orientation of the device doesn't matter. Correct me if I'm wrong.

Thanks.