Jump to content
I2Cdevlib Forums

Different values from .dmpGetGyro and .getMotion6


Recommended Posts

Hi,

I've been trying to get an the MPU to work on an UNO and run into a couple problems. The first I think is a hardware issue. The gyro Z axis seems stuck. I've ordered a replacement.

The second seems to be a code bug in the library, but I'm not sure. I get different results with the two MPU6050 member functions:

    mpu.dmpGetGyro(&agy, fifoBuffer);
    mpu.getMotion6(&ax, &ay, &az, &gx, &gy, &gz);

I'm using the MPU6050_DMP6 and MPU6050_raw sketches as examples. I get unexpectedly low values from dmpGetGyro() when I move the MPU-6050 break out board. I know I've been moving it faster than 250º/s. I've been hoping to use the DMP functions as I would like to have auto-leveling functionality in my sketch. I would also expect more efficiency using the interrupt and reading from the FIFO buffer to be more efficient (is that so?)

I'm not an expert in electronics, but I'm inferring from the data sheet that to convert the raw values (that I expected from both functions) to degrees per second is to divide by 131.0. Is that correct?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...