Stuart.

Just came in from the garden and saw your reply.

In real life checklists get much, much more complicated when he aircraft has 
systems. A glider or a basic Cessna will be quite simple.

I would prefer that the author can add his own page breaks.  The checklist 
cards that I working on at the moment are organised in that manner. For 
example my "Entering Cockpit" checklist is split into 9 separate cards, 
which are meant to be used in a left to right order - starting with the rear 
left hand console panel, working forwards to the instrument panels and the 
rearwards along the right hand console. There is one card per panel. The 
take-off, engine start and other drills are similarly split into logical 
sections.

Yes, our simulator had visits from Boeing and other overseas companies. We 
displayed at Farnborough and on BBC TV. As you know, the VC10 was the last 
large aircraft that was a solely UK project. This simulator was built to a 
systems training simulator standard, which made it practically the same as a 
full simulator , but without visual or motion systems. I was given a  PDP 
11/45, practically fully expanded and costing about 100,000$, to host the 
FDM, autopilot and navigation. A second team had a PDP11/20 and a PDP 11/05 
to handle the systems (including checklists) and drive the CRT display 
hardware. Prices and computer power have changed since then.

Alan



-----Original Message----- 
From: Stuart Buchanan
Sent: Monday, February 18, 2013 1:26 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Aircraft Checklists

On Sun, Feb 17, 2013 at 11:56 PM, Alan Teeder wrote:
> The reason for my query was that I have found making a representative set 
> of
> checklists is becoming  very unwieldy.
>
> With just my "entering the cockpit checks", I have already made 9 separate
> checklist.  Each one has about 10 checks. I have made one checklist per
> check list card on the real aircraft. These  checklist items disappear off
> the top of the menu list screen, and there is no indications as to which
> checklists/cards have been completed, or which is the next to do.
>
> Having got this far it is obvious that the current system will not cope 
> for
> the rest of the aircraft checklists that I intend to replicate.

OK,  sounds like you've got much longer checklists than I have encountered
myself.

I'll see what I can do to support multi-page checklists.  I can probably add
Next and Previous buttons to page through the checklist.

One question:  Would you prefer that the UI itself split the checklist up,
or for the checklist author to do it themselves?  The former would be
automatic, but wouldn't allow the author to place the page-break where
they wished.

> Yes, my level of simulation will include such detail as the "fail to 
> relight
> in 20 seconds" scenario.

Very good :)

> For background info my suggestions were based upon an interactive 
> checklist
> system that I was involved with in the 1980´s as part of a joint 
> BAC/Hawker
> Siddeley  glass cockpit simulation. This was before the two companies 
> merged
> to form BAe.  AFAIK this was the first glass cockpit project to have an in
> depth simulator evaluation. Our two target aircraft were the VC10 (
> completely eliminating the flight engineer station) and the A300 which was
> state of the art at that time.
>
> This electronic checklist also bought up the relevant systems displays on
> one or more other front panel CRT´s . In normal use (e.g. start-up) the
> electronic checklist was selected by the crew, but the relevant set of
> checks were automatically initiated when aircraft failures were detected.
> The system was intelligent enough to follow the sequence of events 
> following
> an emergency (e.g. my relight scenario) , and also had a priority system 
> to
> deal with the major faults (engine failure, fire, etc)  before lesser 
> ones.
>
> At the moment my TSR2 is not a glass cockpit, but having a usable 
> checklist
> system would save a lot of paper.
>
> AS an old fogey I am not up to speed with current developments in this
> field, but am sure that some of our work has a modern counterpart.

Yup, and I think that would be the glass cockpit of the aircraft itself 
rather
than the simulator UI.

> Anyway - you asked for comments on your checklist system ;)

Yup, and very good feedback it is as well.  Thanks.

-Stuart

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly 
thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel 


------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to