NonConformalMapping

I never managed to solve this. Gave up on the project after a while.

Up. Does anyone know of an example sketch that does this?

Has anyone made any progress with this "hacked" version of MPU6050_9Axis_MotionApps41.h? I mean, a version that can handle the Honeywell magnetometer?

Anyone? Dear Jeff? EDIT: Here is an example - the outputs (x,y,z are just the Euler angles, I named them that for... convenience, I guess?) when the sensor is completely static: x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -2.615318 y -0.133159 z 0.058574 x -142.529541 y 0.266016 z -0.325795 x -86.919456 y 40.571777 z -23.873074 x -87.119164 y 5.026152 z 20.263960 x -87.159348 y 4.718861 z 17.872175 x -81.674042 y -30.620316 z -27.208601 As you can see, right towards the end, the angles start to oscillate without no apparent logic. They keep on doing that until they get to this pattern: x -266.105682 y 0.266038 z -180.324097 x -266.105652 y 0.266006 z -180.324081 x -266.105652 y 0.266007 z -180.323959 x -266.105713 y 0.265985 z -180.324173 x -266.105652 y 0.266005 z -180.324036 x -266.105713 y 0.265982 z -180.323883 x 93.894287 y 0.266016 z -180.323959 x -266.105682 y 0.266042 z -180.323853 x 93.894287 y 0.266016 z -180.323975 x -266.105652 y 0.266008 z -180.324158 x -266.105652 y 0.266010 z -180.324005 x -266.105713 y 0.265985 z -180.324020 x -266.105652 y 0.266009 z -180.323959 x 93.894287 y 0.266016 z -180.324020 x -266.105713 y 0.265984 z -180.323944 x -266.105652 y 0.266011 z -180.323807 x -266.105652 y 0.266011 z -180.323776 I don't think the values matter all that much, but I'm posting them so anyone reading this would get the gist of what's going on. Could it be a missing bit or something? I mean, perhaps the FIFO buffer gets "shifted" somehow so all the numbers get screwed up.

Hi everyone, I'm working on a project with an Arduino Teensy 3.2 and the MPU-6050. My method to sample the IMU is based on the "MPU6050_DMP6.ino" example in the library. I modified the program and made it into a function that returns three or four values (angles/accelerations or quaternion), instead of printing them to the serial port. Not much of a change. Anyway - the program works well for a minute or two (sometimes even five). It prints out the angles to the serial monitor and they all seem to make sense. But, after said minute or two (or five) - it all goes to... crap. Instead of "roll 29 pitch 0.1 yaw 1.4" (just an example) I'm suddenly seeing "roll -150 pitch nan yaw 300". Then the outputs go crazy and change values frantically for another minute or so - after which they seem to stop at a certain set of angles (roll -180, pitch 0, yaw -180). And by "stop", I mean they don't change even when I move the MPU around. EDIT: I just noticed that it goes back to normal after a long while. Like after ten minutes, the values would be normal again for one to two minutes. Then it goes mental once more. Does anyone have an idea what the problem might be? I thought it might be FIFO overflow but I don't see any messages in my log. Any help would be greatly appreciated, as always.

Hey all, I have an MPU-6050 connected to a simple board, with only SCL, SDA and voltage/GND outputs. Meaning, no INT pin to connect to my Arduino (I am using Teensy 3.2). Now I don't know a whole lot about these things, but going by the sketches I've seen so far (well, basically the one sketch by the almighty Jeff) - it is required to use the INT pin in order to access the DMP. Is that just the way the sketch is built, or am I screwed by this board not having the INT output? Because I would really love to get Euler angles or quaternions but I've only seen these calculations done reliably through the DMP. Any help would be appreciated.