I've just released ArduPlane 2.69 [UPDATE: revised to version 2.70 after bug fix (see comments). This release includes a lot of internal changes, principally the AP_HAL changes, which is why it took so long. I've also been doing a lot of test flights to try to ensure that all these large changes haven't broken anything.
As has been discussed previously, the biggest change in this release is the move to the new AP_HAL hardware abstraction layer. This was a large internal change, that by itself didn't change the behaviour of ArduPlane, but did allow us to make ArduPlane much more portable. As a result, this is the first release of ArduPlane that works on the new PX4 autopilot board. Unfortunately the documentation on how to setup ArduPlane on PX4 is still lacking, so if you have a PX4 and want to run the 2.69 release then you will either have to dive into things a bit yourself to get it to work or wait a bit longer for the documentation updates. Sorry about that!
Of course we still support the APM1 and APM2 and I plan on keeping ArduPlane working on both those boards as long as possible. What I expect to happen is that some new features in future releases will only be enabled on the PX4, but for now ArduPlane on the PX4 works just the same as it does on the APM1 and APM2.
As you might expect from the fact that it has been over 2 months since the last ArduPlane release, there have also been quite a few changes not related to the AP_HAL and PX4 work. Many thanks to everyone who has contributed patches and ideas that made it into this release! I know not every requested feature made it in, but I thought it was better to get the new release out now.
Some of the key changes in this release are:
One of the changes I am most pleased with is the addition of a new flight mode called TRAINING mode. This mode was developed in cooperation with a MAAA flight instructor, and is designed to help people to learn R/C manual flying. When you are in TRAINING mode you have manual control over roll until you reach the LIM_ROLL_CD roll limit, at which point the plane won't roll over any more. The same applies to pitch - you have manual pitch control until you reach LIM_PITCH_MIN or LIM_PITCH_MAX, at which point the plane won't pitch beyond those limits. This means that as long as you stay within the configured limits you are flying the plane manually, and you can quickly learn to fly an R/C plane manually, knowing that the APM will prevent the plane from going upside down. I'll do a separate blog post about how we are using TRAINING mode to teach new pilots good R/C manual piloting skills.
Another significant change in mode behaviour is that CIRCLE mode now holds altitude. This is important because CIRCLE is used in the first stage of failsafe conditions, and if your plane is badly trimmed it could lose quite a lot of altitude before the RTL stage of failsafe kicks in. Note that this doesn't mean that CIRCLE is now the same as LOITER - in a LOITER the plane will adjust its roll to keep going around the target position, whereas in CIRCLE the position of the plane isn't considered - it just holds a small roll angle, which results in a large circle that drifts with the wind. This is deliberate as we want CIRCLE to not be dependent on the GPS, and to involve no sharp turns.
The other change that is probably worth expanding on is the ability to mount the APM in many possible orientations. This has been an open request for a long time as for certain types of airframes it is very useful. Just set the AHRS_ORIENTATION parameter to one of the supported orientations and your APM will quite happily work upside down or sideways.
I'm expecting it won't be 2 months till the next release, as I have a bunch of other changes pending that I held off for this release (for example, the AP_Mission code from Brandon, and the new AP_Scheduler code), but meanwhile I'm very happy with how this release is flying, and I hope you all will be too!
None of the tabs in CLI are responsive.
Hi Reid and Khairul,
One thing to be careful of when switching between releases is that the 2.68 and earlier releases used a different dataflash format to the 2.69 and later releases.
That means when it boots it will reformat the dataflash, which takes a minute or so. That means you need to be patient on the first boot with the changed firmware version.
SO it looks like you have to give it a couple minutes, you have to connect via CLI and wait. After 3 minutes click on log download and it will work.
I tested with a few of my APMs and the rest works fine. This particular one i have even when i got it to boot, the accelerometers are not responding in any version beit ArduPlane or Arducopter.so im pretty sure its hardware related. I also used the reset function in CLI everytime i reflash different versions to ensure no conflicts. Most of the time this Apm when i connect power it doesnt initialise and only LED C, the Blue light comes on .
I let it sit for at least ten minutes numerous times... I just emailed 3D robotics also
Can you send me the mission file you were using? Unfortunately it isn't in the log.
Thats great news. I need to make a new purchase. SHould it be an APM 2.5 or PX4 ?
Need the best reliability and hopefully be future proof ( for at least a few months )
Tridge, what happened to apm1.4(with atmega1280) firmware updates? Recently I've flashed 2.70 from MP to it, but CLI says 2.65. Is it not supported anymore?
Can you pse post a download or source control link for that? I can't find it.
The 1280 should still work with ArduPlane (but not with ArduCopter). Perhaps something went wrong with the MissionPlanner firmware download for 1280.
I'll have a look when I get a chance.
I have made a new tlog and mission file for the autolaunch problem where the flying wing dives instead of climbing. There should be 2 failed autolaunches at the beginning. Climb angle set to 8°.
Afterwards I let the plane circle a bit in guided mode, I upload a new mission with autoland, switch to auto and the plane lands itself. So successfull test of uploading a new mission in flight.
But I'd really like to get to the bottom of this diving problem.