Jump to content
I2Cdevlib Forums

nicososa

Members
  • Posts

    3
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Uruguay

nicososa's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I am having problems to interprete the yaw angle I get. With the IMU stable on a table, no matter the orientation, the yaw angles stabilizes at first at about 60 degrees (around 10 seconds after turned on). So we don’t understand how the yaw angle is measured. Which is the fixed referenced that is chosen? Pitch and roll are almost zero at horizontal position. I guess that with calibration they will become zero. We are new at working with IMU, so this kind of help is really important for us. Thank you
  2. Hello. I have a similar issue. After a minute of working properly, the dmp output data gets messed. I dumped the fifo count and I get a count not proportional to 48, for example 52 (actually it with mpu-9150). How is that this happens and how can it be avoided? Thank you very much
  3. Hello! My name is Nicolas, I am from Uruguay and I am currently working on an University project with MPU-9150 integrated with a GPS. First of all, I would like to congratulate for the work with the library. It has really helped me. I have a question regarding the DMP6 example. In the loop(), after the mpuInterrupt appears, the while is stopped and you check the Interrupt Status Register: // otherwise, check for DMP data ready interrupt (this should happen frequently) } else if (mpuIntStatus & 0x02) { // wait for correct available data length, should be a VERY short wait while (fifoCount < packetSize) fifoCount = mpu.getFIFOCount(); // rest of the code } After having some issues integrating with gps data, I have checked the MPU 9150 Map Register and found that Interrupt Status Register bit 0 is the one that represents the Data Ready Interrupt. So why compare with 0x02 and not to 0x01? Thank you very much
×
×
  • Create New...