Yes we already tried to setup some parameters in there. But not all, because
we first wanted to test if it is flying at all or not. This morning we
looked again but haven’t understand how we can define the table date for
CL_due_to_alpha or CD_due_to_alpha or even the wingarea / CoG.
When using JSBSim, JSBSim is solely responsible for determining the
aerodynamics. ArduPilot's only job is to fly the vehicle JSBSim is
The Parameters I was refering to were ArduPilot's parameters helping
to define the vehicle's own concept of its outputs and its responses to
the input that the simulated vehicle is supplying - so definition of which
outputs are on which (virtual) servo outputs, PID settings, that sort of
Or differently asked where does ardupilot takes its aerodynamic form? Is
this hidden in the parameter files of ArduPlane / quadplane? Or uses
ardupilot therefore the standard vehicle “Rascal”?
(When typing in “sim_vehicle.py -j4 -f quadplane -L KSFO”)
The quadplane model is in-built. The code for this is present in
theArduPilot source tree - when running with this model, the same binary
also pretends to be a plane.
More than enough use of the word "coefficient" to satisfy most people:
It's a VERY simply quadplane model - really just bolting a quad onto a
plane. Improvements are very welcome, of course!