#24 crash detection params

closed
nobody
None
1
2012-10-31
2005-06-15
David Culp
No

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.

Discussion

  • Jon S. Berndt

    Jon S. Berndt - 2005-06-18

    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

    David Culp - 2008-01-23

    Logged In: YES
    user_id=893393
    Originator: YES

    This can now be handled using JSBSim systems.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks