1. Use of Software from Cockpit Equipment in the Training Environment
Take your title slide (minus any graphics you may have on the slide) and make it the first slide of your presentation. This is the slide that will show up when searching for your presentations within PowerPoint.
Kevin O’Brien
Program Manager
Honeywell Training Solutions

2. Purpose of this Presentation
Inform AICC members with experience gained from a true avionics Rehost
Help align AICC efforts with best practices identified from that experience
Identify overlapping or exclusive areas of influence between system engineers and content/lesson authors
AICC
System Engineers
Content Authors
Here are the basic elements of the Honeywell PowerPoint template. The Walk-away message box and the Subhead are not part of the master page because of the limitation in PowerPoint to one title and one text area.
Generate the discussion

3. Introduction
AICC and Airline calls for rehosted Flight Management System drove the need
Honeywell was beginning development of new Integrated Avionics system call Primus Epic®
Hardware resembles PC cards
Software written in C/C++
Represented best opportunity yet for a rehost

4. Epic Rehost Project Objectives
Enable use of Epic aircraft software for pilot training
Classroom operation should have high fidelity
Minimize number of changes to rehosted aircraft software
Updates to field are quick, and training kept current
Should not require extraordinary PC host
Rehosted software should run in 50% of 2 GHz Pentium 4 PC

5. Project History
Honeywell hosted an industry meeting in April of 2002 to define the requirements and determine feasibility.
Chose the Dassault Falcon 900EX EASy
Meeting resulted in the first formal Application Specification
Team chose to build infrastructure from the ground up in order to avoid existing obstacles.
Proof of concept occurred in July 2002
Relied on Moore’s Law during development

6. Definitions Rehosted vs. Reimplemented GGF’s ASCB-D
During our development we came across issues in the aircraft code that Windows couldn’t cope with i.e. null references.
Made those changes and communicated back with product engineering to make changes for next aircraft software release.
Needed to define the difference between “touched” and “untouched” code.
Reimplemented meant “dropped in” code.
GGF’s
Graphics executables with a .exe extension OpenGL based
ASCB-D
Primus Epic’s primary communication bus
DEOS-Digital Engine Operating System
Aircraft’s Operating System

7. Scope of the Rehost
Build an abstraction layer and services on top of Windows, that looks like DEOS. Result was EASE.
Rehost the FMS and GGF’s applications on top of EASE.
Holy Cow, it worked!!!!
The “why not?” approach expanded even further to include
Monitor Warning
Central Maintenance
Electronic Checklists
Terrain Display
Radio Tuning
….AFCS, WX Radar, MCDU, Flight Plan uploading.

8. Technical Approach
2. Port graphics and Flight Management software to the PC
1. Create a software environment that allows use of Epic applications on an ordinary PC
3. Wrap around pilot lesson plans and flight simulation

9. Honeywell Content Aircraft Software
Displays
All the Graphics Generation Function (GGF) processes
Graphics Control
CALF and DUCTL
Flight Management System
Monitor Warning Function
Electronic Checklist
Epic Application Simulation Environment
Provides a PC environment that appears like the aircraft to Epic applications
DEOS API, Epic ASCB communication, File System and Core Graphics software, …

10. PFD with Flight Management Window
This picture represents an aircraft parked on the ground and displays fuel and weight parameters

11. Honeywell/Vendor Software Interfaces
Aircraft data, two options:
GenericPddClient capability allows aircraft simulation software (ordinary Windows processes) to produce or consume ASCB data
Reuse EASE interface for Epic Test Interface Unit (TIU)
Graphics rendering
Honeywell provides specification for rendering Epic graphics as well as source code for our implementation of rendering process
CCD input
EASE reuses the Epic CCD specification
Platform control
Honeywell provides DLLs for controlling rehosted software,
Start, Stop, Suspend, Resume, TimesN
Snapshot/Recall, Reposition, Freezes
Relation to Snapshot Data Model??? XML?

12. GenericPddClient Process
In the aircraft, PDD requires that the process that produces IRS data be named “genIo”
IRS
“genIo”
PDD
ASCB
ARINC 429
MAU proc card
In EASE, we use GenericPddClient to replace the “genIo” process and transfer simulated IRS data to ASCB
Aircraft simulation
ASCB simulation
GPC “genIo”
PDD
EASE platform

13. System Architecture DU1 DU2 FMS Graphics Rendering Simulated ASCB Bus
Epic Application Simulation Environment
DU1
DU2
FMS
Graphics Rendering
Simulated ASCB Bus
GPC
TiuFBS
Pilot Training Software
Flight Simulator
Lesson Control

14. Epic Rehost runs on an ordinary Windows PC
Host Hardware
Windows XP or 2000
2 GHz Pentium 4 processor
Game-grade video card
Laptop or Desktop
Epic Rehost runs on an ordinary Windows PC

15. Other Uses of EASE in Honeywell
Epic testers are using EASE for DU1310 V&V (Falcon and Gulfstream)
GGF, CALF, MWF and ECLF
Test development
Run-for-score
FMS developers
Investigating EASE for use with TOLD development and FMS testing
Miscellaneous other uses
Epic programmer training
Flight plan development
Verifying NAV databases

16. Customer Benefits
Development time to integrate vs. development time of reverse-engineering (or source/object rehosting and retargeting).
Avoids the “It doesn’t look like my aircraft” syndrome
Looks just like the airplane
Updates to the HI product coincide can occur simultaneously with updates to the field
System architecture allows for fast end-item update
Independent of training device implementation

17. Drawbacks Not easily customizable.
It is actual airplane software
Requires some knowledge of target system interface/operation
All necessary internal variables must be addressed.

18. Observations System engineers are not content developers
Unaware of initiatives like AICC CMI, SCORM
It’s all about the interface
The less we exposed the content developers to Epic, the better off we were
Reusabilty isn’t always the best thing
Needed to abandon previous attempts to rehost parts of the system
Rehost engineers had no idea what they were looking at when successful

19. Quick Demo

20. Conclusion Rehosting of aircraft avionics will become more prevalent
Have proof of concept for all Pegasus FM
Plans to rehost the A380
Are standards needed, and if so, what/where?
If communications modules are standard i.e. ASCB, is all that is needed is an interface spec?
LMS interoperability

21.
This is the closing slide that should appear at the end of all presentations. If you are using an existing presentation, you should copy this slide and insert it at the end. The old Honeywell closing slide, with the red background and tagline “Helping You Control Your World” should not be used.
This slide should not be altered in anyway. Do not add any additional elements to the slide, alter the web address, add additional copy, etc.
Use it as it appears here. 18 4 4

22. If you are giving your presentation electronically, it is always good to insert a black slide at the end. This ensures that the computer will not jump back to the Windows screen or program manager, and distract the audience from your closing remarks