ACRO bug (fixed in 2.9.1b): while doing flips in ACRO mode, if you switch to Stabilize while inverted your throttle will go to minimum. To regain throttle control you need to switch back to ACRO then back to Stabilize again (i.e. switch to stabilize twice). You never lose control of roll/pitch/yaw.
Loiter/AltHold/Auto/RTL bug: if you switch into these modes with throttle at zero motors will go to minimum until you raise the throttle.
Auto mode altitude bug (fixed in 2.9.1b): setting a waypoint altitude greater than 320m over home altitude may wrap around and instead be interpreted as a low altitude.
ArduCopter 2.9 is now in the mission planner and the downloads area!
The major improvement is we use inertial navigation to improve altitude hold. This increased reliance on the accelerometers means you must do some additional set-up before flying:
3. If upgrading from 2.8.1, modify the throttle and altitude PID values:
Here is the list of major changes (a more detailed list can be found in the release notes):
As per usual PIDs are optimised for the 3DR/jDrones quad with 850 motors and 10" props. If you're using more powerful motors/props and are seeing bad flight behaviour in stabilize, start by turning down Rate Roll P in 25% steps.
Special thanks to our testing team lead Marco and the dedicated bunch on the 2.8.1 release thread who put their copters at risk while testing the pre-release version. Some of their videos are here: 1 2 3 4 5 6 7 8
Please feel free to report issues you find in the discussion below and/or add them to the issues list.
Here is my current set up. It is an APM 2.0. This unit was first put on a F550 hex in a similar way and worked well on 2.8.1. The 550 was upgraded to an APM 2.5 mounted in the same location. I decided against putting anything between the deck plates because of the integrated power board in the bottom plate possibly affecting the compass. The other thing I have definitely noticed is the Castle Creations 10A switching style BEC cannot be close to the APM or it will twitch randomly. This unit is mounted on foam for when I go back to 2.9 which I tried briefly. On 2.8.1, and the GPS upgraded to 1.9, it Loiters reasonably well. I upgraded the hex to the APM 2.5 to improve the Loiter capability for camera work. This quad is aimed at sport flying so Loiter is less important.
'Russle any jimmies', I like it...
The 450 at the top?
My 450, you mean ;)
Yup I was the only one that wasn't getting rained on when the video needed releasing
This is the 'all-up' test rig, allow me to introduce you....
I've tried in include a few vital tips for an 'all up f450 frame'
Only things different from the in video is I have added snow skids so had to move the gimbal our front instead of underneath, and therefore slide one of the 4s 4000mah battery backwards a bit to sort the centre of gravity.
I should mention that I deliberately put the apm high up, away from the frame, for vibration isolation and to get it away from the power lines. It also give me a crash box and some waterproofing.
You can stick a naza in the frame (it's effectively just in antivibe box) and stick the mag and gps up on a stick.
You can do the same with APM if you like, just use external mag and gps on a stick.
I've had a f450 quad with the apm and mag stuck to the power distro boards, right inside the frame.
It wasn't very clever in loiter or auto, but it would rtl ok so i used it for fast fpv fun in stab and alt-hold, then I put an external mag on a stick and it did everything else well too.
hope that helps
Thanks Dave for the video! I pretty much knew that it was made for me ;-)
While I'm not doubting that your quad doesn't fly well in stab mode(mine does as well), it's the outdoors flying and crashing that everyone is experiencing, GPS drift, compass/mag problems, etc that worry us.
But if this is what works then later, I'm going to post (YOU KNOW THE RULES!!) my current setup) then I'm going to tear the thing apart and make it a platformed beast like yours and lift up the APM with a aluminum plate on top and a CD cover for protection.
Cause this compass drift and interference is killing me. Thanks again for the vid.!
Because now, my Jimmies are Russled and I want to get this thing flying!!
Test Failsafe at night
That was the battery failsafe you were testing? looked pretty good!
I can't test is it. Because, I not have power module. But, I maybe order it next time.
I'm forgot attach log and tlog file on video.
This is a tx/rx failsafe side, not the battery, right?
ํYes, tx/rx only.
I'm a little surprised that it took so long to come down. When I do the radio failsafe my copter comes home immediately.
Today I have made my first flight my homemade octocopter, and I have some issues:
1- Stabilize works great with stock values except in P that I have 0.90 because I use 400kv motors, but the copter starts to yaw slowly.
2- Alt hold not works as I wish, the octa is more like an kangaroo, I'm using an XL-EZ0 but I don't know if is a problem of sonar or the baro.
3- Position mode works great if you don't use the sticks, only the throttle is used. (windy day), but maybe I have saw an issue using this mode, when the copter is in Position mode, the mission planner shows "unknown" and the yaw value is freeze (but the copter is yawing slowly as I said) but while I don't touch the stick the mode works fine. When I try to change the position without leave the "Position mode" the copter flies well but when I release the stick start to fall and I have to change to stabilize mode to be able to get the control and in the mission planner shows the actual yaw value instead of the freeze value.
My config is APM1 + sonar + mediatek 1.9 + compass + 3dr radio link.
I have attached the logs and the video showing the position mode working (not when its falls).
P.D. I'm sorry for my bad English.
I have a very similar setup (hardware) and a homebuilt frame as well. Mine yaws too, but was able to resolve that as follows:
- move the APM away from the power distribution board.
- move ESC's away from the APM.
- and most importantly: use compass calibration based on log files. The log file I used was a very short log file in which I made sure that I was taking off, hover, then rotate the copter clockwise in a slow movement and again in fast movement. Then do the same counter clockwise. Then load that log to calibrate the compass.
Hope it helps for you too!
PS: this was in 2.8.1 and I suspect I need to do the same in 2.9.x. Just waiting for the weather to warm up.