Leaderboard

Recently, when I tried to control MPU6050 via Mediatek Linkit One, I found that there seems a problem in readBytes() function in i2cdevlib. Since the I2C buffer of Linkit One is really small, the following code will loop more than one time. Using logic analyzer, I found that the I2C write address will be incorrect after first iteration because of the line 278. Will you guys think that the line 278 needs to be modified to Wire.write(regAddr+k) ? PS. The DMP operates correctly after this modification. 276 for (uint8_t k = 0; k < length; k += min(length, BUFFER_LENGTH)) { 277 Wire.beginTransmission(devAddr); 278 Wire.write(regAddr); 279 Wire.endTransmission(); 280 Wire.beginTransmission(devAddr); 281 Wire.requestFrom(devAddr, (uint8_t)min(length - k, BUFFER_LENGTH)); 282 Thanks

in this code there is a boolean (mpuIntStatus & 0x02) mpuIntStatus = mpu.getIntStatus(); // get current FIFO count fifoCount = mpu.getFIFOCount(); // check for overflow (this should never happen unless our code is too inefficient) if ((mpuIntStatus & 0x10) || fifoCount == 1024) { // reset so we can continue cleanly mpu.resetFIFO(); Serial.println(F("FIFO overflow!")); // otherwise, check for DMP data ready interrupt (this should happen frequently) } else if (mpuIntStatus & 0x02) when i look at the register where mpu.getIntStatus() gets his value ...Register 58 – Interrupt Status mpu6050 .. I see bit 1 is empty (has no purpose) soo i dont understand the boolean (mpuIntStatus & 0x02) ... witch seem to do a logic AND operation with this bit i must be seeing something wrong ... could anybody help me explaining the boolean (mpuIntStatus & 0x02 ?? grtz Ido

Hi All I'm very new to the world of accelerometers gyro's etc, and I've recently purchased a MPU-6050, which I promptly dropped from a height of approximately 2 feet or so, onto my wooded desk top right out of the packaging. This poor thing bounced around a fair bit before coming to a stop. The data sheet states it can handle 10000 G’s, but this value doesn’t mean anything to me. Does anyone know how many G’s my device would have experienced in this unfortunate adventure? One more thing, the data sheet also states the accelerometer data is returned in 16 bits two’s complement form. To ask a question to what might seem like an obvious answer, is it correct that, to get back the raw data I would have to subtract one first, and then invert the whole 16 bits? OR have I missed something? cheers, and thanks.

Could someone point me in the direction of some documentation on how to conect the MPU_6050 to an Audrino, please? Is there pre-defined pins or how do i define them? Im just looking for the raw data also. Thanks in advance. Pingu22