#24 crash detection params

[David Culp]

I'd like to see something like this in the config file:

<crash-detection>
<altitude-agl>0</altitude-agl>
<g-z-max>11.0</g-z-max>
<g-z-min>5.0</g-z-min>
<g-x-max>20</g-x-max>
<g-x-min>20</g-x-min>
<qbar>1089.0</qbar>
<pitch-rate>3.7</pitch-rate>
<yaw-rate>3.5</yaw-rate>
<mach>0.99</mach>
</crash-detection>

This is where the user could specify conditions that can
trigger a crash. If the condition is exceeded, then a
crash message will be sent to the console, and a
"crashed" property will be set to true.

Crash handling, i.e. what to do with the simulation once a
crash is detected, should be left to the controlling
application.

[Jon S. Berndt]

Logged In: YES
user_id=144031

I'm wondering if this is really in scope for an FDM. Or, might it
be a subsystem for FlightGear, for instance, that takes FDM
paramaters and determines crash characteristics?

[Nobody/Anonymous]

Logged In: NO

actually, this sounds like a pretty good idea, however it
would probably make sense to allow specification of multiple
different crash "profiles" or rather "crash configurations",
i.e. conditions that are known to be problematic/unflyable.

On the other hand, using/extending the current nasal based
limits.nas file ($FG_ROOT/Aircraft/Generic/limits.nas) might
really be a better and more generic approach, instead of
harcoding support for something like this into an FDM engine.

[David Culp]

Logged In: YES
user_id=893393
Originator: YES

This can now be handled using JSBSim systems.