lectroidmarc

I'm sorry, I meant +/- 2G's... This would be to get yaw/pitch/roll data in a high-power rocket. If course the rocket would be pulling in the neighborhood of 50Gs for a few seconds, followed by freefall (in actuality coasting) followed an ejection charge explosion which presents it's own reasonably high G forces. I'm kind of assuming that the high G's would render the DMP capabilities at +/- 2G's moot.

As I recall, because of the proprietary nature, the 6050 DMP can only be used at +/- 3G. This is enough, of course, to get yaw/pitch/roll data out of the chip under limited Gs, but what about in high-G environments? In short, with the yaw/pitch/roll data generated by the DMP still be accurate when subjected to greater than 3G acceleration? Greater than 16Gs? Thanks, Marc

Ah, that works, thanks!

Aw well. No worries. I've really enjoyed using the I2Cdev package for other sensors, so I just got spoiled . Keep up the good work!

Ugh. Oh well, it's not the end of the world . This does beg another question tho, I tried setting the sensitivity settings *before* the DMP was initialized and it seemed to have no effect. Is that expected? Thanks!

Hi all, Even when running the MPU6050_DPM6 test sketch, if I change the acceleration range to the MPU's full +/- 16G range it seems to "break" the DMP functionality. By "break" I mean the DMP can no longer seem to properly remove gravity from the various axis'. Looking at the output, it almost appears like it's trying to remove the gravity but the DMP is still assuming a +/- 2G range setting, so the output is extra odd, like showing gravity at around 3 G's. Is it possible to have the accelerometer set to a +/1 16G range (or 8 or 4) and still utilize the DMP? Or is it just me ? Thanks

In the MPU6050_DMP6 demo can someone explain the difference between the OUTPUT_READABLE_REALACCEL output and the OUTPUT_READABLE_WORLDACCEL output? I'm having a tough time wrapping my head around the two and how they impact the resulting acceleration numbers. Thanks, Marc

Hello, I see the MPL3115A2 in the list of supported devices, but it doesn't seem to be present in the code. Even the github link on http://www.i2cdevlib.com/devices/mpl3115a2#source points to code that doesn't exist. I just got one of these so if it's really supported, that would be great. Thanks, Marc