Hotkey for Emergency Checklist + Naming Convention

[Mark(Guest)]

After reading through the User's Guide (updated 8/26/05) I've got to say I'm concerned about one major lack of functionality in the menu setup. Emergency checklists are buried several layers deep in button pushes, requiring you to make the following button push sequence (assuming no menu items are displayed initially):

1) any button to turn on menus
2) LIST (softkey 4)
3) user defined softkey for emergency checklist

In the interest of safety, when a pilot needs to access an emergency checklist he doesn't have time to search for the right softkey. I would like to suggest that Dynon take a long hard look at their checklist function and implement a hotkey to access an emergency checklist. Such a hotkey might require the pilot to push the power button three times in rapid succession. When this button push sequence is detected the display should automatically change to the pre-defined emergency checklist. This keystroke sequence needs to be set up so the pilot doesn't have to look at the screen to know which button to push - it has to be instinctive.

The military inisists on this kind of hotkey setup for their displays, so a pilot may make critical selections even if the display goes blank (things like accessing the zeroize function for data loaders so crypto keys don't fall into enemy hands...). The FAA also mandates similar intuitive functionality for TSO'd EFIS and EICAS systems. There's no reason why an EFIS like the Dynon product shouldn't offer the same degree of functionality when it comes to emergency checklists. After all, this equipment is supposed to ease pilot workload, not increase it, especially during an emergency.

Also, one other major beef is with the naming conventions used on the softkeys. Yes, I know, you're limited to only 6 characters. Since this is the case, Checklist should be abbreviated to CHKLST. Similarly, for BUGS, the toggle function should be labelled ON/OFF as the term "toggle" means nothing in normal aviation vernacular. It means a lot to electrical engineers, but is totally meaningless to pilots. The same thing applies to the DIM function - the buttons should read BRT and DIM, the same as we've been seeing on brightness controls for years. Stick to pre-existing naming conventions, please!

I'm by no means a human factors expert, but the above shortcomings in the Dynon EFIS design are absolutely glaringly obvious and need to be fixed in order to bring this equipment more in line with standard cockpit procedures and terminology.

 

[sonex293]

Re: Hotkey for Emergency Checklist + Naming Conven

I was thinking along the same lines. My thought was to press and hold any button to get an Emergency Checklist up.

--Michael

 

[dynonsupport]

Re: Hotkey for Emergency Checklist + Naming Conven

Hi,

One of the things we strive for are good compromises between flexibility, usability, and complexity. This is inherently difficult when designing for a wide cross section of users. Dynon pilots have backgrounds that vary widely. At one end we have customers that have been flying relatively basic VFR panels before their Dynon. They benefit from a user interface that is discoverable and does not require a Sporty's or King Schools "how to" DVD to demystify its features. At the other end of the spectrum are fighter pilots that can cope with the most complex HOTAS (hands on throttle and stick) arrangements and prefer lightning quick access to every function, even if it requires more up-front learning to become fluent. We do try to accommodate everyone as best we can. In some ways, Honeywell and other military contractors have an easier job designing their systems because they know exactly how proficient their customer is and know the exact configuration and specifications of the aircraft and systems their units are going into.

An example of where we think we have a good trade-off between flexibility and simplicity is the exact emergency checklist access that you have mentioned. While the menu system verbosely directs a new user into the many (up to 25) possible checklist and aviation data screens that can be stored on the EFIS, a power user can perform the following steps to get quick access to a particular custom emergency checklist that you've written and uploaded with the PC support program:

1) button 4 to turn on menus
2) button 4 to go to LISTS
3) button 4 to go to the list of emergency lists
4) button 4 to go to the particular emergency list under button 4 (buttons 1-5 would presumably have emergency checklists for different types of emergencies)

This is one button push more than specified, but fits in the paradigm that I think you are after. We also have the issue that there is not just one emergency checklist. There is one for fire, one for engine out, one for power failure, etc. Having a hotkey go to one emergency checklist doesn't always make it easier for the pilot if that checklist doesn't relate to the emergency they are having. By leading the user down the same menu path that they use every day, the stress level can be kept low and the information can be brought up rapidly.

Soft-key naming is difficult for similar reasons. For example, the LISTS button actually used to be named CHKLST but was recently changed as we expanded the amount data storage area available. Now, there is room to include any data you'd like to upload to the EFIS. Example lists that we pre-upload here at the factory include the aviation alphabet, template POH data, time zone information, and other data that is not encompassed by simply calling that button CHKLST. In a similar way, we call the dimming buttons "BRITR" and "DARKR" because we don't just have two stages of brightness, we have about 10. Thus "BRIGHT" and "DIM" can be misleading because they are more indicitave of two states, not the motion between many states.

In any case, we really appreciate the feedback and will continue to use it to build products that meet the requirements of as many customers as possible.

 

[Mark(Guest)]

Re: Hotkey for Emergency Checklist + Naming Conven

Thanks for the quick response. Your comments are in line with what I expected them to be. Your description of the use of a common key to get to emerg checklists does indeed follow the paradigm I had in mind.