I've just released ArduPlane 2.73 as a bug fix release for several important bugs in 2.72
The main reasons for this release are:
This release does not contain the new attitude controllers that I previously said would be in 2.73. Paul and I decided that it would be better to hold those over to the next release, and get this release out with just the above critical bug fixes.
The airspeed problem stemmed from a changed introduced in 2.72 to make ArduPlane automatically scale analog inputs with board voltage. That change was good for voltage and current sensing, but it added a lot of noise to airspeed sensing as the 3DR airspeed sensor is ratiometric (the sensor output scales with the supply voltage). The fix was to add support for ratiometric analog inputs. This release also fixes a bug in the airspeed ratio handling. To confirm the fix I have been driving around in my car with an APM2 and PX4 logging airspeed and GPS speed - that test confirmed the airspeed sensing is now accurate.
The flyaway bug in L1 was caused by an unusual situation where the previous waypoint was equal to the next waypoint, which can happen when a mission is interrupted and restarted. The L1 controller would then level the wings and fly straight ahead until the operator intervened. The bug fix was to make the L1 controller detect this situation and track directly to the next waypoint. I don't think many users would have seen this bug, but it definitely could happen and warranted a bug fix release.
The GPS handling bug was related to the MTK GPS, which can be very slow to report loss of GPS lock, which could lead to very poor attitude from DCM and even a crash if the plane tries to turn while the GPS is reporting incorrect velocity information. The fix was to watch the satellite count, and stop using the GPS velocity for accelerometer correction when it had less than 6 satellites. This is selectable with the new AHRS_GPS_MINSATS option.
While this release doesn't have the new attitude controllers I decided to leave in some other smaller changes that have been made since the 2.72 release that I consider to be low risk, including:
Of these, perhaps the most useful is the ELEVON_OUTPUT option. That makes it possible to setup your transmitter with normal aileron/elevator and get the APM to do a software elevon mixer on output. That gives better control in FBWA mode than the previous elevon options.
I recommend that all users of 2.72 upgrade to 2.73. Happy flying!
i have the same problem tested with Arduplane 2.72, 2.74b: Actually it starts with around 90 degree positive pitch and later on all of the angles go crazy. I can only fly with manual mode.
with the same configuration: Xplane9, Missinon Planner 1.2.50, APM2.5, Turnigy 9X Tx/Rx
Great work on the development - you guys really are doing a fantastic job.
Can you (or someone else) please help with approach/glide settings... I can't seem to find the solution to:
> I would like to set up a long approach, motor-off, with APM using pitch control to maintain a predefined airspeed. The approach is over several waypoints and I would like to adjust the target airspeed for each leg (reducing from ~45kts to 20kts in stages over ~5 legs). What parameters in MP do I need to adjust at each WP in order to achieve this?
The most important aspect is 'motor-off'.
Apologies if this isn't the correct place to post.
Thank you Graham.
It seems that from 2.71 onward there are some bugs which may jeopardise the safety of our UAV. It is now safe to use 2.73 for serious mapping works ?
Currently I'm using 2.69 which work great for me, hold very nice grid line in auto navigation. I may need to increase the NAV_PITCH gain to hold more constant altitude. Now it can be off about 15 meter when there is thermal but it won't decent more than 10 meter.
A big thank you for Andrew and the teams. Great work
Can Arduplane run on the new PX4 ?
If this is not the place for this question please forgive me.
I got it working by downloading and compiling it myself.
I´m not sure if I had the flyaway bug or another bug with 2.72. In the figure can be show that only could do the mission the first time because the alt_error_nav was increasing! despite it was the same mission. The other 2 times, in auto mode the X8 was trying to go much higher above the waypoints. Any help is apreciated.
I have never had luck trying to repeat a mission UNLESS I reset the mission either via the restart mission button on MP or using my gear channel switch I have setup for resetting the mission. Works every time using either of those methods.
Kurt do you mean the DO_JUMP command? I know you have to add a dummy waypoint after DO_Jump to get it to work.