[CLOSED] Problem with IMU?
Posted: Tue Jan 13, 2015 10:14 pm
Hi guys,
I haven't really played with my CF2 as much as I would like and that's because I suspect there is a slight problem with the acel/gyro on board.
Basically when I fly (or pick up and put down) the CF the roll axis takes a little while to settle even though the flie is still. I previously posted about this and Marcus advised it was most likely because the props were unbalanced, I now have balanced them as good as I can (spent an hour) and the problem is still there.
It doesn't sound like much of an issue but sometimes when flying I seem to loose roll in one direction and I'm constantly Left and right with the trim.
Here is a video of the flight data and the plotter with me picking the flie up, giving it a quick shake and then setting it down. At first I thought it may be the PID loop recovering from "error" but then I figured that the PID(s) must only output on target data and not actual?
http://youtu.be/Va5RZ-2vxeU
The Video is not the best instance of this happening but you can get the idea, Especially right at the start of the vid.
Could anyone give any insight as to whether this is "normal behaviour" or I may be seeing a fault with the HW?
Thanks in advance,
Cab
I haven't really played with my CF2 as much as I would like and that's because I suspect there is a slight problem with the acel/gyro on board.
Basically when I fly (or pick up and put down) the CF the roll axis takes a little while to settle even though the flie is still. I previously posted about this and Marcus advised it was most likely because the props were unbalanced, I now have balanced them as good as I can (spent an hour) and the problem is still there.
It doesn't sound like much of an issue but sometimes when flying I seem to loose roll in one direction and I'm constantly Left and right with the trim.
Here is a video of the flight data and the plotter with me picking the flie up, giving it a quick shake and then setting it down. At first I thought it may be the PID loop recovering from "error" but then I figured that the PID(s) must only output on target data and not actual?
http://youtu.be/Va5RZ-2vxeU
The Video is not the best instance of this happening but you can get the idea, Especially right at the start of the vid.
Could anyone give any insight as to whether this is "normal behaviour" or I may be seeing a fault with the HW?
Thanks in advance,
Cab