Aircraft checklists: Difference between revisions

Jump to navigation Jump to search
Line 183: Line 183:


Obviously, additional logic can be included in the binding if you want the autostart menu to toggle between autostart and shutdown.
Obviously, additional logic can be included in the binding if you want the autostart menu to toggle between autostart and shutdown.
Sometimes, a checklist binding will do something like display a dialog, e.g. fuel and payload dialog. It would be irritating to the pilot if these things happened during automated execution. These bindings can make use of the <code>sim/checklists/auto/active</code> property, which will be <tt>true</tt> when the checklist binding is being run by the autochecklist script and <tt>false</tt> otherwise.


==== Expedited checklists ====
==== Expedited checklists ====
Line 196: Line 198:
</syntaxhighlight>
</syntaxhighlight>


Clearly the checklist sequence used for in-air start should be different from a ground start and should put the aircraft into a flying state, e.g. gear up, flaps up. Bindings can use the property <tt>sim/checklists/auto/expedited</tt> to check if the execution is expedited, i.e. there is no wait between items. Note that the expedited flag does not in itself indicate whether a binding is being run as part of an automated checklist. You would normally need to test both the <tt>sim/checklists/auto/active</tt> and <tt>sim/checklists/auto/expedited</tt> properties, e.g.
Clearly the checklist sequence used for in-air start should be different from a ground start and should put the aircraft into a flying state, e.g. gear up, flaps up. Bindings can use the property <code>sim/checklists/auto/expedited</code> to check if the execution is expedited, i.e. there is no wait between items. Note that the expedited flag does not in itself indicate whether a binding is being run as part of an automated checklist. You would normally need to test both the <code>sim/checklists/auto/active</code> and <code>sim/checklists/auto/expedited</code> properties, e.g.


<syntaxhighlight lang="nasal">
<syntaxhighlight lang="nasal">
Line 237: Line 239:


=== Other features and ideas ===
=== Other features and ideas ===
Sometimes, a checklist binding will do something like display a dialog, e.g. fuel and payload dialog. It would be irritating to the pilot if these things happened during automated execution. These bindings can make use of the <code>sim/checklists/auto/active</code> property, which will be <tt>true</tt> when the checklist binding is being run by the autochecklist script and <tt>false</tt> otherwise.


Automated checklist execution is not restricted to autostart and shutdown. If you have an "After Landing" checklist that switches landing lights off, raises flaps and turns taxi lights on, for example, you could assign that to a keyboard shortcut. Rollout and taxi is a busy time on some aircraft and it's often not easy to find the switches and controls necessary to complete this kind of checklist.
Automated checklist execution is not restricted to autostart and shutdown. If you have an "After Landing" checklist that switches landing lights off, raises flaps and turns taxi lights on, for example, you could assign that to a keyboard shortcut. Rollout and taxi is a busy time on some aircraft and it's often not easy to find the switches and controls necessary to complete this kind of checklist.
149

edits

Navigation menu