Pro MFD Checklist
The checklist is one of the most versatile applications in the Pro MFD series, being that it is almost completely dynamic. All of the information, including the checklist names and checklist items can be changed via external files as is explained below.
 |
How the checklist works...
The checklist is very simple in operation. It consists of open and closed loop items which are activated by mouse clicks and keyboard shortcuts respectively. If an item has a keyboard shortcut assigned to it, the software will automatically interpret it as a closed loop item and there will be no checkbox for that item. Those items must be activated/deactivated using keyboard commands. The keyboard shortcuts can be produced using a keyboard emulator the keyboard interface as given by the site, http://www.777Project.cjb.net, or just a standard keyboard. When these items are activated, the checklist automatically checks off these items, even if they are toggled while not on the corresponding screen.
 |
The menu screens can be used to navigate the various checklist screens more quickly than with the checklist override (CHKL OVRD) button. Their operation is basically self-explanatory and is really no more than point and click. The menus are dynamic as well so they consist of data that can be changed via the external files.
Customizing the Checklist
The program is about 95% dynamic, so you can customize the checklist for any aircraft you'd like. There are two different files to understand in order to fully exploit the customizability of this software. Here is an explanation of each file:
Data.ini
The data.ini file is a VERY important file to understand in
order to be able to completely utilize this software. It is possible to add checklists,
add checklist items, and create closed loop (auto-check) items by properly editing this
file.The software does not start reading file data until the "---NORMAL---" or
"---NON-NORMAL---" sections are reached, so all text, above these markers in the
file, is treated as commented code.
Here is an excerpt from the included 777 checklist file and the definition of each line:
 |
---
- Indicates a new
checklist section
Before Start
- The Name of the checklist section
F/O Challenge - Pilot Challenging
Captain Respond -
Pilot Responding
Cockpit Windows ; CLOSED & LOCKED(F,C)- A checklist item
Seat Belt Sign ; ON ; b
- A checklist item
...Up to 12 checklist items are currently supported
In order to make the "Pilot Challenging" and "Pilot
Responding" fields blank, use a single hyphen "-", on each line.
Each station can be customized as well to create realistic effects in
the simulator as well. As in the actual aircraft, opened and closed loop items are also
simulated. To make these, use the following format.
Gear ; UP ; 1 ; 2
Gear - The name of the checklist item
Up - The expected response
1 - the activation key (places a check in the box near any
"Landing Gear Up" item when pressed)
2 - the deactivation key (removes the check from any
""Landing Gear Up" item when pressed)
Closed loop items are presented on the screen with no check box and
can only be bypassed by pressing the proper keyboard shortcut button or by clicking
"ITEM OVRD". When the computer receives the activation signal from the landing
gear (possibly the letter "g") the software will automatically know to place a
check by the item. Semi Colons should separate each area of information.
There is now a data.ini function which allows users to activate closed loop items at startup. This will allow you o initially have the items for gears-down, flaps-up, etc. at program startup. This can be done as follows.
1. Make at the end of the checklist file called "[INITIALS]"
2. On the next line, type in each letter you want synthetically produced at program startup; Each should be seperated by a colon and a SINGLE space as shown in the following example:
[INITIALS]
2 : f : q
In this example, as used with the default 777data.ini file, the landing
gears would be indicated to be down (caused by "2"), the fuel control switches
would be indicated as cutoff (caused by "f"), and the fuel pumps would be
indicated as off (caused by "q"). You can alter these values as necessary to
suit the aircraft you are building.
Checklist Data Files
No additional profiles available
Please submit any new checklist data files to Robert Prather at prather@ProMFD.cjb.net and I'de be more than
happy to post them here!