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.
Where is your throttle stick when you're hovering in manual mode? It may be that you're underpowered and need to adjust the throttle curve on your RC Tx.
Marco, I normally always fly with the 3DR radios. Sadly, a few days ago one of the two 3DR radios broke down (unknown as to why). I have ordered one new Tx/Rx and waiting for a new one. Otherwise I may have been able to do that, but sadly I was today not able to communicate with the laptop.
Herewith the log files. There are a couple (the last ones) but it seems that nothing has been recorded(?)
Maybe you can still extract something usefull??
so many new things and most of them work perfect..pfff,you
I don't know if it has any relevance, but you say sonar and optical flow disabled. Are they still electrical connected to the APM?
Have used cable ties, elastic bands, neoprene foam rubber, etc, etc. No difference! BUT that was prior to v2.9
Probably more important to find the vibration source, rather than protecting against it somewhere else. Problem is, is that the APM isn't very heavy, makes it hard to filter out vibration...
Any suggestions as to what could have caused this?
Sounds to me that you lost r/c communication!
As a last attempt to get it down, you could change to Stabilize and shut the throttle (or even disarm) but of course, you need r/c link to do this!
Stephen, Methinks there are two reasons for the current avalanche of questions, making v2.9 sound as if it's buggy!
An explosion in new APM owners, & the changes in some of the setting up procedures in v2.9
Sorry if this is not the appropriate thread, but I started up MP today, it started to auto update, and failed with the message:
"Update Failed The volume for a file has been externally altered so that the opened file is no longer valid."
Is there something I did wrong, or is there a bug in the 1.2.32 update?
ThisWikipedia: This, in the English language, is the singular proximal demonstrative. →
Yes I´m using the default params. Ok next days I will test it. I think I had to make some PID settings.If I have time I make a video from it, it´s better to explain it to you.
I also have trouble with calibration : my HUD isnt level at all :(
Do I need to change any of my telemetry settings for CLI to work over it? When I go to the CLI screen I get a bunch of "gibberish" characters rolling down...
I also have a telemetry module (TMM1000) on my DX8 and while the quad was flying, I could still see live telemetry data such as battery voltage, and frame loss or packet loss (this was not the case), which is what leads me to believe that I could not have had lost (complete) r/c communication. Also, I was at a distance of 20 meters, which makes it hard to believe it was an r/c problem.
Again, I don't know could have gone wrong, but just replying factually to your suggestion.