ArduPlane 2.40 has now been released. Many thanks to everyone who gave flight test feedback on the beta release!

Note that ArduPlane now uses MAVLink 1.0, so you'll need to update your Mission Planner to the newer version, which supports that. You'll find it in the same directory as your current Mission Planner, in a file called ArduPilotMegaPlanner10.exe

For a list of feature changes, see the ArduPlane-2.40-beta announcement. Since the beta the following things have changed:

  • auto-configuration of UBlox GPSes. It should now be possible to attach a UBlox GPS in just about any state and the APM GPS code will re-configure it appropriately. The configuration isn't saved, so if you power cycle the GPS it will revert to what was set before, but it should now be possible for the APM to use a UBlox in factory default config. It's still a good idea to setup your UBlox correctly (38400 baud in UBX binary mode) as that will make the detection faster on startup, but it should work regardless.
  • updated Camera and Mount control code from Amilcar Lucus and Greg Fletcher. These are not enabled by default, and I have not tested them myself, so I'm hoping Amilcar and Greg will be able to answer any questions that come up. Many thanks to Amilcar and Greg for all their work on this!

Happy flying!

Views: 2812

Reply to This

Replies to This Discussion

Run your terminal see if it getting errors running there the startup. Sometimes the dataflash needs to be removed and moved back then upload the firmware and it works properly.

Hi Jim, I'm seeing this exact same issue as well, its really frustrating. Have you found a solution?

Jim, I managed to find a solution to this, thanks to Doug:

http://www.diydrones.com/forum/topics/2-40-firmware-won-t-save-conf...

Thanks Mike, I will try to do the procedure.

For me, manual level does not works anymore. It tells me; "Failed to level: AP 2.32+ is required"

If i can level it somehow, i will try 2.40 tomorrow.

Ignore that. It is a bug. It's already filed, I think it is bug #668 (from memory).

It does level. Click [ok] and don't touch the APM until the LEDs stop blinking.

Maybe there is something wrong on Mission Planner.  I'm sure it will be fixed soon if a problem exist.

In the mean time this is how I set the level of my Bixler on the bench.

1- Using Mission Planner Set MANUAL_LEVEL param to 0

2 - Level the Plane(APM) and keep it level.

3- Reset APM and wait for the light show to finished.

4 - Using Mission Planner Set MANUAL_LEVEL param to 1.

5 - done.

I checked from time to time the level of the Bixler and to be honest I never had to worrie about leveling the thing anymore....Using stabilise mode on the ground ... helped me confirmed the level.

The MANUAL_LEVEL param is documented on the Wiki

 

There is. It is a cosmetic bug. Leveling works. http://code.google.com/p/ardupilot-mega/issues/detail?id=663&can=6

I remembered wrong, it is filed as bug#663

Ok, i will.

Thank you Mike! :)

Also,

I use a modified code for MinimOsd. Added a few things.

Now i can't use it. I would put my code in the so9urce, but i can't download the new code. Only the old can be found.

Because of this, i have to go back to 2.34. :(

I did find the new code so, i implanted our code. (Air speed, ground speed in km/h, home alt, battery remaining)

In case someone needs it: Link

Also uploaded 2.40

Hope it will fly well. Will test it soon.

There was a bug in home alt. Fixed it. The link is the same.

RSS

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Groups

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service