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: 2813

Reply to This

Replies to This Discussion

In this version there's still the same issue I don't understand like in previous ones. When looking at calc_nav_pitch() there is a command

nav_pitch = -g.pidNavPitchAirspeed.get_pid(airspeed_error, dTnav); (2 parameters call)

However, get_pid definition is

PID::get_pid(int32_t error, uint16_t dt, float scaler) (3 parameters definition)

How can it be like this? Can you explain me?

Why is elevator reversed in FBW_B?

How can i make it work normal?

Have i misunderstood something? :)

Hi Gabor,
It seems like the philosophy is that the plane will give down elevator to increase speed and up to decrease. So testing on the ground elevator will give down to get to your target airspeed :) ...
On my test A380 it work perfectly to control speed, altitude not yet.

Purple Dragon

Thank you Dragon, but i mean in the air.

When i pull the elevator, the plane should climb, but it does the opposite.

And when i push, the plane climbs but it should.....

Will test FBWB evantually... I notice the same beahvihor some time ago.

Until i installed Pito tube on the Bixler I guess I will never know.

FBWB works??? or not?

Dude that tested it! please speak up!

Eric

Hi Eagle,

It does work, but elevator is rewersed.

Thanks Gabor. Will install Pito tube soon.  But is it reverse or not? Purple Dragon seems ok with it.  He mention altitude issues but otherwise controlled wise it is fine. No?

Yes elevator is reversed. Also my plane waves a bit in fbw_b but i think it is because of my pusher prop. When it gives throttle the plane pitches down a bit. I wil solve this somehow.

Could someone upload a parm file of a usual flight?
I would like to test my minimosd code.
THX

Hi.  I must add a *fake* last waypoint in a Mission in order to use DO_JUMP command to have a looping Mission? If I don't include the *fake* waypoint the plane will circle over home and not repeat mission.

 

This is working:

WP 1

WP 2

WP 3

DO_JUMP WP#1

WP *fake*

----------------------------------------------

This is not working:

WP 1

WP 2

WP 3

DO_JUMP WP#1

 

I'm fine with adding the fake waypoint for the mission to work but could this might hide a bug... or maybe I missed something.... again ;)

 

Do you have a parm file of your mission? :)

mission file attached.  Without WP4, the mission don't loop.

Attachments:

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