Just uploaded latest firmware 2.33, and APM 1.1.73.
Have an twinstar II with ardupilot mega and oilpan shield, gps, airspeed, magnatometer.
Setup flew last fall perfectly. I added the battery monitor, the attopilot 90 and a power switch. Sadly, I didn't try it prior to adding those items, so I'm not sure if they are causing problems or not. Nothing is different if I don't have the attopilot sensing wires connected or not.
The elevator servo is "frozen" when in stabilize mode. ie, it works in manual mode, but in stabilize mode it always stays put-- even if I tilt the plane.
The roll(ailerons react appropriately)
In the APM status view, I can see the radio inputs for the elevator (channel 2) does change as I move the stick, it just has no effect. It also does not move when I pitch the airplane.
Once back to manual mode it works fine.
I'm at a loss on what to do now.
Thanks for any idea's. Lincoln
And this last time it just rebooted itself-- in stabilize mode and it was a bit crazy.
So after doing the CLI mode, reset, reflash, reset, redo setup a few times and getting my usb oscilliscope some workout here is what I think is going on.
1) after reset with apu steady it looks fine.
2) All inertial data is slowed down-- like the filter is super-strong. Thus in stabilize it also is like molasses.
3) within 15-30seconds the IMU goes wacko. Including compass. large random movements with board just sitting there.
- so stabilize mode goes berserk
4) I ordered the new purple board (back on april 6th) -- Nothing like replacing the complete brains, so that should solve this particular problem. Sigh.
I saw another thread - http://diydrones.com/forum/topics/erratic-imu-in-apm-2?xg_source=ac... and he was seeing same thing as me. However, seems like his fix was simply factory reset and that is not working for me.
We tried to auto-level our UAV but after the process something went wrong. Before that the ailerons and the pitch elevator worked well in Stabilized mode "in the room" but now they operate really slowly. We reseted everything to the factory defaults, cleared the EPROOM and and relaibrated the RC but it didn't solve the problem. Our firmware version is 2.34.
Does anyone have any suggestions?
I never did figure it out, ordered the purple version of the hardware as my solution. Which version of the hardware do you have? I also feel like it is a software problem, but perhaps is limited to a certain hardware board -- I was going to downgrade the software to the version I was using last year, but ran out of time to try that. Although I may do that next week. I wonder if it has something to do with a change on the purple hardware board to all new (and better) accelerometer's/gyro's. I think they changed the software to use the hardware error correction etc in the accelerometer/gyro chip instead of software; Anyway, am really grasping at straws in regards to the problem. I do hope you figure it out or find a solution, as I would like to get a 2nd plane running.
David, are you powering up your receiver before APM2? Quite a while back I had a strange thing where all the sensors would go in slow motion if I did that, had to power up the APM first, let it finish booting and then power the Rx.