d42 - users guide for the ma-afas avionics rig...me1 2xx england tel. 01634 844400 fax. 01634 816721...

MA-AFAS IN STRICT CONFIDENCE Contract No. G4RD-2000-00228 Report No. 560/80240 Issue 1.0

IN STRICT CONFIDENCE Page i

CONTRACT N° : G4RD-2000-00228 PROJECT N° : GRD1-1999-10516 ACRONYM : MA-AFAS TITLE : THE MORE AUTONOMOUS - AIRCRAFT IN THE FUTURE

AIR TRAFFIC MANAGEMENT SYSTEM

D42 - Users Guide for the MA-AFAS Avionics Rig

AUTHOR: BAE SYSTEMS PROJECT CO-ORDINATOR : BAE SYSTEMS PRINCIPAL CONTRACTORS :

Airtel ATN Ltd (Ireland) QinetiQ (UK) ETG (Germany) EUROCONTROL (France) NLR (Netherlands)

ASSISTANT CONTRACTORS:

AMS (Italy) DLR (Germany) ENAV (Italy) FRQ (Austria) Galileo Avionica (Italy) Indra Sistemas (Spain) NATS (UK) SCAA (Sweden) S-TT (Sweden) Skysoft (Portugal) SOFREAVIA (France) Stasys Limited (UK) Thales-ATM (France)

Report Number : 560/80240 Project Reference number : MA-AFAS – WP4.1-BAESYSTEMS Date of issue of this report : 17 June 2003 Issue No: 1.0 PROJECT START DATE : 1/3/2000 DURATION : 36 months

Project funded by the European Community under the ‘Competitive and Sustainable Growth’ Programme (1998-2002)

This document is proprietary of the MA-AFAS consortium members listed on the front page of this document. The document is supplied on the express understanding that it is to be treated as confidential and may not be used or disclosed to others in whole or in part for any purpose except as expressly authorised under the terms of CEC Contract number G4RD-2000-00228

Comment: Click here for access to the MCDU pages

Comment: Click here for access to the NDU Softkeys


IN STRICT CONFIDENCE Page ii

All enquiries related to this publication should be referred to:

AVIONIC SYSTEMS

Airport Works, Rochester, Kent. ME1 2XX England

Tel. 01634 844400 Fax. 01634 816721

D42 - Users Guide for the MA-AFAS Avionics Rig

Document No. 560/80240

Issue 1.0

Contains 203 pages total

Comprising:

12 pages front matter

191 pages text and figures

Compiled by: Title: Principal Systems Engineer Barry Darlington Date:


IN STRICT CONFIDENCE Page iii

LIST OF EFFECTIVE PAGES AND CHANGE HISTORY Insert latest changed pages. Destroy superseded pages

TOTAL NUMBER OF PAGES IN THIS PUBLICATION IS 203

CONSISTING OF THE FOLLOWING Page No. Date Issue DCR Page No. Date Issue DCR All 0.00 -


IN STRICT CONFIDENCE Page iv

DISTRIBUTION LIST This Document is distributed as below.

Additional copies held by unnamed recipients will not be updated. Paper Copies Name Address

MASTER Library BAE SYSTEMS, Rochester MA-AFAS Library Avionic Systems

Electronic Copies

Name Address

European Commission EC, Brussels MA-AFAS Consortium Members [email protected]

MA-AFAS Web Site


IN STRICT CONFIDENCE Page v

Contents 1 SCOPE ........................................................................................................................................ 13

1.1 Purpose ....................................................................................................................................13 1.2 System Overview......................................................................................................................13 1.3 Document Overview .................................................................................................................13 1.4 Applicability...............................................................................................................................13

2 REFERENCED DOCUMENTS.................................................................................................... 16

3 OPERATING ENVIRONMENTS ................................................................................................. 17

3.1 Physical Characteristics ...........................................................................................................17 3.1.1 Development Environments ........................................................................................17

3.1.1.1 Rochester Development Environment ........................................................................17 3.1.1.2 On-Site Development Environment.............................................................................17

3.1.2 Flight Environment ......................................................................................................18 3.2 Powering Up the System..........................................................................................................18

3.2.1 MA-AFAS Avionics Rig................................................................................................18 3.2.2 MCDU..........................................................................................................................18 3.2.3 Navigation Display Unit ...............................................................................................18

3.3 Initialisation...............................................................................................................................18 3.4 System Indicators .....................................................................................................................19 3.5 An Overview of the System Operation .....................................................................................19

3.5.1 System Initialisation.....................................................................................................20 3.5.2 Route Planning............................................................................................................20 3.5.3 Communications Functions .........................................................................................20 3.5.4 In Air Functions............................................................................................................21

3.6 System Reset ...........................................................................................................................21 3.7 Powering Down the System .....................................................................................................21

3.7.1 Extraction of Data Logs ...............................................................................................21 3.7.1.1 Extracting Logged Data From Bench Rigs..................................................................21 3.7.1.2 Extracting Logged Data From Aircraft .........................................................................21

4 OPERATOR ACTIONS ............................................................................................................... 23

4.1 MCDU.......................................................................................................................................23 4.1.1 MCDU Display.............................................................................................................23

4.1.1.1 The Scratchpad ...........................................................................................................23 4.1.2 MCDU Controls ...........................................................................................................24

4.2 MCDU Pages............................................................................................................................25 4.2.1 FMS Initialisation Pages..............................................................................................26 4.2.2 FMS Ident ....................................................................................................................28 4.2.3 System Initialisation (INIT/REF) ..................................................................................29

4.2.3.1 Position Update (POS INIT) ........................................................................................31 4.2.3.2 FMS Set Up (SET UP) ................................................................................................33 4.2.3.3 Aircraft Load Display (FUEL).......................................................................................38 4.2.3.4 CM Logon (CM LOGON).............................................................................................39 4.2.3.5 Date and Time Entry Page (DATE TIME) ...................................................................40

4.2.4 Route Planner (RTE)...................................................................................................41 4.2.4.1 Company Route Selection (CO ROUTES)..................................................................43

4.2.5 Departures and Arrivals (DEP ARR) ...........................................................................45 4.2.5.1 Arrivals.........................................................................................................................46 4.2.5.2 Departures...................................................................................................................48

4.2.6 Waypoint Entry (LEGS) ...............................................................................................50 4.2.6.1 Waypoint Selection......................................................................................................51 4.2.6.2 Turn Type ....................................................................................................................51


IN STRICT CONFIDENCE Page vi

4.2.6.3 Altitude Constraints .....................................................................................................52 4.2.6.4 Disconnects.................................................................................................................52 4.2.6.5 Legs Lat/Long..............................................................................................................53 4.2.6.6 Legs RTA.....................................................................................................................54

4.2.7 Progress Reports (PROG) ..........................................................................................55 4.2.7.1 Progress Report 1 .......................................................................................................55 4.2.7.2 Progress Report 2 .......................................................................................................56 4.2.7.3 Progress Report 3 .......................................................................................................57 4.2.7.4 Progress Report 4 .......................................................................................................58 4.2.7.5 Progress Report 5 .......................................................................................................59

4.2.8 Air Traffic Control Uplink Functions (ATC) ..................................................................60 4.2.8.1 Variants on ATC Uplink Message Pages ....................................................................61

4.2.9 Air Traffic Control Downlink Functions (ATC) .............................................................69 4.2.9.1 Aircraft to ATC Downlink Functions (AIR/ATC)...........................................................70 4.2.9.2 Route Clear (ROUTE CLR) .........................................................................................71 4.2.9.3 ATC Downlink Message Log .......................................................................................73 4.2.9.4 ATC Downlink Text Entry ............................................................................................74 4.2.9.5 ATC CPDLC Connection Status..................................................................................75

4.2.10 ASAS Functions (ASAS) .............................................................................................76 4.2.10.1 ASAS Manoeuvre – Remain ...................................................................................77 4.2.10.2 ASAS Manoeuvre – Change...................................................................................78 4.2.10.3 ASAS Manoeuvre – Merge .....................................................................................79 4.2.10.4 ASAS Manoeuvre – Cross ......................................................................................80 4.2.10.5 ASAS Manoeuvre – Pass .......................................................................................81 4.2.10.6 ASAS Manoeuvre – Resume ..................................................................................82

4.2.11 Vertical Navigation (VNAV) .........................................................................................83 4.2.11.1 Phase Table ............................................................................................................84 4.2.11.2 Constraints ..............................................................................................................85

4.2.12 Holding Pattern (HOLD) ..............................................................................................86 4.2.13 Fix Data Entry (FIX).....................................................................................................86 4.2.14 Aircraft Operations Centre Communications (AOC) ...................................................87

4.2.14.1 Flight Plan Display (FLIGHT PLAN)........................................................................88 4.2.14.2 Loadsheet Display (LOADSHEET) .........................................................................90 4.2.14.3 Departure Slot Display (DEP SLOT).......................................................................92 4.2.14.4 Snag Report Display (MALFUNCTION)..................................................................93 4.2.14.5 In Flight Traffic Management Display (IFTM) .........................................................94 4.2.14.6 Received Free Text Menu Page(s) (FREE TEXT).................................................96 4.2.14.7 Meteorological Data Request Menu (METEO) .....................................................100 4.2.14.8 Message Composition Display (COMP MSG) ......................................................104 4.2.14.9 Meteorological Data Request (REQ METEO) ......................................................105 4.2.14.10 AOC Disable (DISABLE).......................................................................................106

4.2.15 Flight Information Services – Broadcast Communications (FIS-B)...........................107 4.2.15.1 FIS-B SIGMET (SIGMET).....................................................................................108 4.2.15.2 FIS-B ATIS (ATIS).................................................................................................111 4.2.15.3 FIS-B METAR (METAR) .......................................................................................118 4.2.15.4 FIS-B RVR (RVR) .................................................................................................124 4.2.15.5 FIS-B Send Request (SEND)................................................................................127 4.2.15.6 FIS-B Airport Message Display (MSG) .................................................................128 4.2.15.7 FIS-B Requested Information Display (REQ INFO)..............................................129 4.2.15.8 FIS-B Disable Control Display (DISABLE)............................................................130

4.3 Navigation Display Unit Displays............................................................................................131 4.3.1 NDU Softkeys Interface.............................................................................................131

4.3.1.1 Top Level Softkey Menu............................................................................................131 4.3.1.2 DCP Softkey Menu....................................................................................................132 4.3.1.3 ATC Softkey Menu ....................................................................................................134 4.3.1.4 ASAS Softkey Menu..................................................................................................136

4.3.2 Navigation Displays...................................................................................................144 4.3.2.1 Map Mode Displays ...................................................................................................144 4.3.2.2 Plan Mode Display ....................................................................................................146


IN STRICT CONFIDENCE Page vii

4.3.2.3 Profile Mode NDU Display.........................................................................................147 4.3.2.4 Taxi Map Mode NDU Display ....................................................................................148 4.3.2.5 Taxi Plan Mode NDU Display....................................................................................149 4.3.2.6 Taxi Airport Mode NDU Display ................................................................................149 4.3.2.7 Approach Mode NDU Display ...................................................................................149 4.3.2.8 NDU Symbology Components ..................................................................................150 4.3.2.9 Cursor Control Device Operation ..............................................................................157

4.3.3 Display Control Panel................................................................................................157 4.3.4 Autopilot Control Unit ................................................................................................159

4.3.4.1 BAC1-11 Autopilot.....................................................................................................159 4.3.4.2 ATTAS Autopilot ........................................................................................................159

5 SOFTWARE UPDATES ............................................................................................................ 161

6 CUSTOMISATION..................................................................................................................... 162

7 MAINTENANCE ACTIVITIES ................................................................................................... 163

7.1 MCDU.....................................................................................................................................163 7.1.1 Parallax Adjustment Page .........................................................................................164 7.1.2 MCDU Part Number Page.........................................................................................165 7.1.3 MCDU Maintenance Password Page........................................................................166 7.1.4 MCDU Maintenance Menu........................................................................................167 7.1.5 MCDU Configuration Page........................................................................................168 7.1.6 MCDU ARINC 429 Interface .....................................................................................169

APPENDIX A DEVELOPMENT ENVIRONMENT INITIALISATION.............................................. 171

A1 Development Environment Initialisation .................................................................................171 A2 Database Modification............................................................................................................171

A2.1 Data File Formats......................................................................................................172 A2.1.1 NDU Data ..................................................................................................................172 A2.1.2 Navigation Database Data ........................................................................................172 A2.1.3 Navigation Aids (D,DB) .............................................................................................173 A2.1.4 Waypoints (EA, PC) ..................................................................................................173 A2.1.5 Procedures (PD, PE, PF) ..........................................................................................173 A2.1.6 Company Route File..................................................................................................174 A2.1.7 MCDU Menus Data ...................................................................................................175

A2.2 Creating Supplementary File Information..................................................................175 A2.2.1 File Location ..............................................................................................................175 A2.2.2 Configuration File Changes.......................................................................................175 A2.2.3 Memory Usage And Requirements. ..........................................................................176

A2.3 Transferring Data To/From the Hard Drive ...............................................................177 A3 Example Files .........................................................................................................................178

A3.1 Airport Waypoint File .................................................................................................178 A3.2 Airport SID File ..........................................................................................................178 A3.3 Airport STAR File.......................................................................................................178 A3.4 Airport Approach File.................................................................................................179 A3.5 Company Route File..................................................................................................179

A4 Blueprint Files.........................................................................................................................181 A4.1 I/O Ports Definition ....................................................................................................183

A4.1.1 IP Address Modification.............................................................................................183 A4.1.2 TCP/IP Port Numbers................................................................................................183 A4.1.3 RS232/RS422 Port Definition....................................................................................184 A4.1.4 ARINC 429 Configuration..........................................................................................184

A4.2 Blueprint File Attas.bpt ..............................................................................................185 A4.3 Slave MCDU..............................................................................................................188 A4.4 Comms Configuration Files .......................................................................................188

A4.4.1 File cfgB_R1.sh / cfgC_R1.sh ...................................................................................188 A4.4.2 File AirAOCConfigurationData.txt..............................................................................188 A4.4.3 File cms_cfg_data.txt ................................................................................................188


IN STRICT CONFIDENCE Page viii

A4.4.4 File cms_script_cfg.txt ...............................................................................................190 A4.4.5 Ground Server Configuration ....................................................................................190

APPENDIX B SCRIPT TEMPLATES ............................................................................................. 191

B1 FMU Script Template..............................................................................................................192 B2 CMU Script Template .............................................................................................................194 B3 Logged Data Extraction Script................................................................................................197

APPENDIX C SCRATCHPAD MESSAGES................................................................................... 198

APPENDIX D OH, AND BY THE WAY........................................................................................... 202

D1 System Power Up...................................................................................................................202 D1.1 SBAS and GBAS.......................................................................................................202

D2 Initialisation.............................................................................................................................202 D2.1 Precision Approach Setup.........................................................................................202 D2.2 Configuration File NDBconfiguration.txt ....................................................................202

D3 ATTAS System Usage ...........................................................................................................202 D3.1 Date ...........................................................................................................................202 D3.2 Heading .....................................................................................................................202

D4 BAC1-11 Configuration Usage ...............................................................................................203 D4.1 Time Data ..................................................................................................................203

Figures Figure 1 Bench Avionics Rig ..............................................................................................................14 Figure 2 Flying Avionics Rig for the BAC1-11....................................................................................15 Figure 3 MA-AFAS MCDU .................................................................................................................24 Figure 4 MCDU Menu Page 1 ............................................................................................................26 Figure 5 MCDU Menu Page 2 ............................................................................................................26 Figure 6 MCDU Menu Page 1 ............................................................................................................27 Figure 7 FMS Ident Screen ................................................................................................................28 Figure 8 INIT/REF Screen 1...............................................................................................................29 Figure 9 INIT/REF Screen 2...............................................................................................................29 Figure 10 Initial Position Screen (POS INIT)...............................................................................31 Figure 11 Position Reference Screen (POS REF) ......................................................................31 Figure 12 FMS Set Up Screen (SET UP) ....................................................................................33 Figure 13 Transponder Settings Screen) ....................................................................................34 Figure 14 Navigation Data Source Selection Screen (NAV DATA SOURCE) ............................35 Figure 15 Navigation Data Display Screen (REF NAV DATA)....................................................36 Figure 16 Example Navigation Data Display Screen ..................................................................36 Figure 17 Message Recall Screen (MESSAGE RECALL) ..........................................................37 Figure 18 Aircraft Load Page (FUEL) ..........................................................................................38 Figure 19 CM LOGON Page (CM LOGON) ................................................................................39 Figure 20 Date and Time Entry Page (DATE/TIME) ...................................................................40 Figure 21 Route Planner Page (RTE) .........................................................................................41 Figure 22 Company Routes Selection Page (CO ROUTES) ......................................................43 Figure 23 Company Route Details Page.....................................................................................44 Figure 24 Departures and Arrivals Page (DEP ARR)..................................................................45 Figure 25 Airport Arrivals Data Page(s).......................................................................................46 Figure 26 Selected Airport Arrivals Data Page............................................................................46 Figure 27 Airport Departures Data Page(s).................................................................................48 Figure 28 Selected Airport Departures Data Page......................................................................48 Figure 29 Initial Waypoint Id Data Entry/Display Page................................................................50 Figure 30 Waypoint Id Data Entry/Display Page(s).....................................................................51 Figure 31 Waypoint Selection Page ............................................................................................52 Figure 32 Waypoint Lat/Long Data Entry/Display Page(s)..........................................................53 Figure 33 Waypoint ETA Data Entry/Display Page(s).................................................................54


IN STRICT CONFIDENCE Page ix

Figure 34 Trajectory Progress Page 1.........................................................................................55 Figure 35 Trajectory Progress Page 2.........................................................................................56 Figure 36 Trajectory Progress Page 3.........................................................................................57 Figure 37 Trajectory Progress Page 4.........................................................................................58 Figure 38 Trajectory Progress Page 5.........................................................................................59 Figure 39 Single ATC Message Page (ATC)...............................................................................60 Figure 40 Multiple ATC Messages Page 1 (ATC) .......................................................................60 Figure 41 Long ATC Message – First/Middle Page(s) ................................................................61 Figure 42 Long ATC Message - Last Page .................................................................................61 Figure 43 Received Tactical Message ........................................................................................62 Figure 44 Received Resume Message .......................................................................................63 Figure 45 Received Response Message.....................................................................................64 Figure 46 Received WILCO Message.........................................................................................65 Figure 47 Received UNABLE Message ......................................................................................66 Figure 48 Received Formatted Reply Message Page 1..............................................................67 Figure 49 Received Formatted Reply Message Page.................................................................67 Figure 50 Received Formatted Reply Message Summary Page ................................................68 Figure 51 ATC Downlink Menu Page ..........................................................................................69 Figure 52 ATC Downlink Menu Page ..........................................................................................70 Figure 53 ATC Downlink Route Clear Page................................................................................71 Figure 54 ATC Downlink Menu Page ..........................................................................................72 Figure 55 ATC Downlink Message Log Pages............................................................................73 Figure 56 ATC Downlink Text Entry Page...................................................................................74 Figure 57 ATC CPDLC Connection Status Page ........................................................................75 Figure 58 Initial ASAS Menu Page ..............................................................................................76 Figure 59 ASAS Menu Page .......................................................................................................76 Figure 60 ASAS Remain Manoeuvre Page.................................................................................77 Figure 61 ASAS Change Spacing Page......................................................................................78 Figure 62 ASAS Merge Manoeuvre Page ...................................................................................79 Figure 63 ASAS Crossing Manoeuvre Page ...............................................................................80 Figure 64 ASAS Passing Manoeuvre Page.................................................................................81 Figure 65 ASAS Resume Parameter Page .................................................................................82 Figure 66 Vertical Navigation Menu Page...................................................................................83 Figure 67 Phase Table Edit/Display Page...................................................................................84 Figure 68 Trajectory Constraints Page........................................................................................85 Figure 69 AOC Menu Page (AOC) ..............................................................................................87 Figure 70 Flight Plan Page 1 (FLIGHT PLAN) ............................................................................88 Figure 71 Flight Plan Page 2 .......................................................................................................88 Figure 72 Loadsheet Page 1 (LOADSHEET)..............................................................................90 Figure 73 Loadsheet Page 2 .......................................................................................................90 Figure 74 Departure Slot Page (DEP SLOT)...............................................................................92 Figure 75 Snag Report Generation Page (MALFUNCTION) ......................................................93 Figure 76 IFTM Page 1 (IFTM)....................................................................................................94 Figure 77 IFTM Page2.................................................................................................................94 Figure 78 Received Free Text Messages Menu (FREE TEXT) ..................................................96 Figure 79 Received Free Text Message Details .........................................................................97 Figure 80 Free Text Message Composition Page (COMPOSE).................................................98 Figure 81 Old Received Free Text Messages Menu (OLD FREE TEXT) ...................................99 Figure 82 Meteorological Data Request Menu Page(s) (METEO)...........................................100 Figure 83 Received TAF Report Page (TAF) ............................................................................101 Figure 84 Received METAR Report Page (METAR) ................................................................102 Figure 85 Received SIGMET Report Page (SIGMET) ..............................................................103 Figure 86 Request Meteorological Data Page (REQ METEO) .................................................105 Figure 87 AOC Disabled Page (DISABLE)................................................................................106 Figure 88 FIS-B Menu Page (FIS-B) .........................................................................................107 Figure 89 Received SIGMET Menu Page(s) SIGMET).............................................................108 Figure 90 Received SIGMET Message Page............................................................................109 Figure 91 Received SIGMET Free Text Message Page ...........................................................110 Figure 92 Received ATIS Message Menu (ATIS) .....................................................................111


IN STRICT CONFIDENCE Page x

Figure 93 ATIS Message Data Display Page 1.........................................................................112 Figure 94 ATIS Message Data Display Page2..........................................................................113 Figure 95 ATIS Message Data Display Page3..........................................................................114 Figure 96 ATIS Message Data Display Page4..........................................................................115 Figure 97 Received ATIS Trend Report Page (TREND RPT)...................................................116 Figure 98 Received ATIS Text Report Page (TEXT RPT) ........................................................117 Figure 99 Received METAR Messages Menu Page(s) (METAR).............................................118 Figure 100 Received METAR Message Page.............................................................................119 Figure 101 METAR Page 2 Information Description ...................................................................120 Figure 102 METAR Page 3 Information Description ...................................................................121 Figure 103 METAR Trend Report Page (TREND RPT) ..............................................................122 Figure 104 METAR Text Report Page (TEXT RPT)....................................................................123 Figure 105 Received RVR Message Menu Page(s) (RVR) ........................................................124 Figure 106 Received RVR Message Page 1...............................................................................125 Figure 107 Received RVR Message Page 2...............................................................................126 Figure 108 Send Request Display (SEND) .................................................................................127 Figure 109 Received Airport Messages Menu Page (MSG) .......................................................128 Figure 110 Received Requested Information Messages Menu Page(s) (REQ INFO)................129 Figure 111 FIS-B Disabled Page (DISABLE) ..............................................................................130 Figure 112 NDU Format ..............................................................................................................131 Figure 113 NDU Softkey – Initial Menu .......................................................................................132 Figure 114 NDU Softkey – DCP Menu........................................................................................132 Figure 115 NDU Softkey – Traffic (TRFC) Functions..................................................................133 Figure 116 NDU Softkey – TAXI Functions .................................................................................133 Figure 117 NDU Softkey – MAP Functions .................................................................................134 Figure 118 NDU Softkey – ATC Normal Message Menu ............................................................134 Figure 119 NDU Softkey – ATC Uplink Answered Menu ............................................................135 Figure 120 NDU Softkey – ATC – Long Message Menu.............................................................136 Figure 121 NDU Softkey – ASAS Menu ......................................................................................136 Figure 122 NDU Softkey – RESUME Functions..........................................................................137 Figure 123 NDU Softkey – Lateral Resume Functions ...............................................................137 Figure 124 NDU Softkey – Execute Functions............................................................................138 Figure 125 NDU Softkey – Descent Resume Functions .............................................................138 Figure 126 NDU Softkey – Set Altitude Function ........................................................................139 Figure 127 NDU Softkey – Descent Resume Functions .............................................................139 Figure 128 NDU Softkey – Set Separation Function...................................................................139 Figure 129 NDU Softkey – MERGE Functions............................................................................140 Figure 130 NDU Softkey – REMAIN Functions...........................................................................140 Figure 131 NDU Softkey – PASS Functions ...............................................................................141 Figure 132 NDU Softkey – PASS BEHIND Functions.................................................................141 Figure 133 NDU Softkey – PASS BELOW Functions ................................................................142 Figure 134 NDU Softkey – PASS ABOVE Functions.................................................................142 Figure 135 NDU Softkey – Tactical Command (TC) Functions...................................................143 Figure 136 NDU Softkey – Desired Heading Entry Functions.....................................................143 Figure 137 Map Mode (Expanded) NDU Display ........................................................................145 Figure 138 Map Mode (Centered) NDU Display..........................................................................146 Figure 139 Plan Mode NDU Display............................................................................................147 Figure 140 Taxi Map Display.......................................................................................................149 Figure 141 Approach Mode .........................................................................................................150 Figure 142 IHTP Representation of the Displays Control Panel .................................................158 Figure 143 BAC1-11 AFCS Control Panel ..................................................................................159 Figure 144 ATTAS Autopilot ........................................................................................................160 Figure 145 MCDU Menu Page 2 .................................................................................................163 Figure 146 MCDU Menu Page 1 .................................................................................................164 Figure 147 MCDU Menu Page 1 .................................................................................................165 Figure 148 MCDU Maintenance Password Page........................................................................166 Figure 149 MCDU Maintenance Menu Page 1............................................................................167 Figure 150 MCDU Menu Page 1 .................................................................................................168 Figure 151 MCDU ARINC 429 Interface Page 1.........................................................................169


IN STRICT CONFIDENCE Page xi

Figure 152 MCDU ARINC 429 Interface Page 2.........................................................................169 Figure 153 MCDU ARINC 429 Interface Page 3.........................................................................170 Figure 154 Tornado Launch Window ..........................................................................................171

Tables Table 1. ARINC 429 Interface Activity Lamps....................................................................................19 Table 2. MCDU Function Keys...........................................................................................................25 Table 3. System Initialisation Menu Description ................................................................................30 Table 4. Navigation Data Source Priorities ........................................................................................35 Table 5. Loadsheet (FUEL) Page Items ............................................................................................38 Table 6. Route Planner Page Item Description (RTE).......................................................................41 Table 7. Progress Page 1 Data Items................................................................................................55 Table 8. Progress Page 2 Data Items................................................................................................56 Table 9. Progress Page 3 Data Items................................................................................................57 Table 10. Progress Page 4 Data Items .......................................................................................58 Table 11. Progress Page 5 Data Items .......................................................................................59 Table 12. ASAS Remain Manoeuvre Parameters.......................................................................77 Table 13. ASAS Merge Manoeuvre Parameters.........................................................................78 Table 14. ASAS Merge Manoeuvre Parameters.........................................................................79 Table 15. ASAS Crossing Manoeuvre Parameters.....................................................................80 Table 16. ASAS Passing Manoeuvre Parameters ......................................................................81 Table 17. Phase Table Parameters.............................................................................................84 Table 18. CONSTRAINTS Page Data Items...............................................................................85 Table 19. AOC Menu Functionality (AOC) ..................................................................................87 Table 20. Description of Parameters on Flight Plan Pages ........................................................89 Table 21. Loadsheet Parameters Description (LOADSHEET)....................................................91 Table 22. IFTM Page Parameter Description..............................................................................95 Table 23. SIGMET Information Description...............................................................................109 Table 24. ATIS Page 1 Information Description........................................................................112 Table 25. ATIS Page 2 Information Description........................................................................113 Table 26. ATIS Page 3 Information Description........................................................................114 Table 27. ATIS Page 4 Information Description........................................................................115 Table 28. METAR Page 1 Information Description ...................................................................119 Table 29. METAR Page 2 Information Description ...................................................................120 Table 30. METAR Page 3 Information Description ...................................................................121 Table 31. Received RVR Message Page 1 Description............................................................125 Table 32. ATIS Page 4 Information Description........................................................................126 Table 33. Softkey Main Menu Functionality ..............................................................................132 Table 34. Softkey DCP Menu Functionality...............................................................................132 Table 35. Softkey Traffic (TRFC) Functionality .........................................................................133 Table 36. Softkey TAXI Functionality ........................................................................................134 Table 37. Softkey MAP Functionality ........................................................................................134 Table 38. Softkey ATC Normal Message Menu........................................................................135 Table 39. Softkey ATC Uplink Answered Menu Functionality...................................................135 Table 40. Softkey ATC – Long Message Menu.........................................................................136 Table 41. Softkey ASAS Menu..................................................................................................136 Table 42. Softkey Traffic (TRFC) Functionality .........................................................................137 Table 43. Softkey Lateral Resume Functionality.......................................................................138 Table 44. Softkey Execute Functionality ...................................................................................138 Table 45. Softkey Set Altitude Function ....................................................................................138 Table 46. Softkey Descent Resume Functionality ....................................................................139 Table 47. Softkey Climb Resume Functionality.........................................................................139 Table 48. Softkey Set Separation Function...............................................................................140 Table 49. MERGE Softkey Functionality ...................................................................................140 Table 50. MERGE Softkey Functionality ...................................................................................141 Table 51. PASS Softkey Functionality.......................................................................................141


IN STRICT CONFIDENCE Page xii

Table 52. PASS BEHIND Softkey Functionality........................................................................142 Table 53. PASS BELOW Softkey Functionality .......................................................................142 Table 54. PASS ABOVE Softkey Functionality .........................................................................143 Table 55. Tactical Command (TC) Softkey Functionality..........................................................143 Table 56. Tactical Command (TC) Softkey Functionality..........................................................144 Table 57. NDU Component Symbology ....................................................................................157 Table 58. DCP Functionality......................................................................................................158 Table 59. PowerPC Processor Identification.............................................................................171 Table 60. Hard Drive Directory Structure ..................................................................................172 Table 61. Required elements for Navaid Records ....................................................................173 Table 62. Required Elements for waypoint records ..................................................................173 Table 63. Required Elements for procedure records ................................................................174 Table 64. Header information for a company route file .............................................................174 Table 65. Required information for company route leg .............................................................175 Table 66. Memory usage for record ..........................................................................................176 Table 67. Log Files Generated by the MA-AFAS Rig ...............................................................177 Table 68. Blueprint Files............................................................................................................182 Table 69. Avionics Rig Processor IP Addresses.......................................................................183 Table 70. TCP/IP Port Numbers................................................................................................184 Table 71. RS232/RS422 Serial Port Definition..........................................................................184 Table 72. DCP Rotary Switch Encoding Values .......................................................................185 Table 73. MA-AFAS Software Components..............................................................................191


IN STRICT CONFIDENCE

1 SCOPE 1.1 Purpose

This document provides guidance to users of the MA-AFAS Avionics Rig. The Rig has been designed and developed by the MA-AFAS consortium, lead by BAE SYSTEMS, for use in trials that validate the concepts explored by the programme.

1.2 System Overview

The Avionics Rig is a VME chassis containing two PowerPC single board computers, called the Flight Management Unit (FMU) and the Communications Management Unit (CMU), an ARINC429 interface card, an RS232/RS422 I/O module and a large (9.1 or 18.2 Gbyte) Hard Disk Drive (HDD). Integral to the FMU is a graphics adapter and SCSI controller (for the hard drive), whilst the CMU houses a 28VDC discrete I/O module.

The Avionics Rig software is a modular suite of software functionality that has been designed to run on PowerPC target computers. Each function in the suite can be individually configured by an initialisation script called a blueprint file.

For the hardware, four custom built VME chassis have been commissioned by BAE SYSTEMS for bench use as shown in Fig 1. A bespoke flying rig has been built for use in trials aboard the BAC1-11 and individual components have been supplied to DLR for use in their ATTAS environment.

1.3 Document Overview

This document forms part of Deliverable D42 and sets out to describe how to use the Avionics Rig functionality in its various implementations. This covers the actions required to initialise the computer system and invoke the flight software and then each of the available functions is described from an operators point of view. Note that this document does not attempt to identify what level of functionality will be available for a given hardware set-up.

This document assumes that the Avionics Rig has been installed as defined in document D41.

1.4 Applicability

This document will be updated to reflect the functionally available in the latest release of software. The software release number will be used as the issue number of the document that appears in the top right hand corner of each page. The corresponding release information can be obtained from the software by selecting the FMS IDENT page Menu Item of the MCDU (shown in Fig 7).

This document includes descriptions of the functionality available in Build E2 of the Flying software.



Figure 1 Bench Avionics Rig



Figure 2 Flying Avionics Rig for the BAC1-11



2 REFERENCED DOCUMENTS ARINC 429 ARINC Characteristic 429Pt1-15, Mark 33 Digital Information Transfer System

(DITS), Part 1, Functional Description, Electrical Interface, Label Assignments and Word Formats, Dated: September 1, 1995.

D30 Specification for the In House Test Platform, Issue 1.0, Dated: TBD.

D41 Installation Guide for the Avionics Rig, 560/78718, Issue 1.0

D54 HMI Definition Document, Issued by NLR



3 OPERATING ENVIRONMENTS 3.1 Physical Characteristics

A complete MA-AFAS comprises an Avionics Rig, a Multi-function Control and Display Unit (MCDU) and a Navigation Display (ND). These items operate in a number of test and trials environments as defined below.

In order for the MA-AFAS to operate, other peripherals are needed. These comprise a Display Control Panel (DCP), a Cursor Control Device (CCD) and an autopilot control panel, sometimes referred to as a Master Control Panel (MCP). Each installation provides specific to type units for these items.

3.1.1 Development Environments

Two development environments have been created for the MA-AFAS programme; one at Rochester, where the bulk of the development work is undertaken, and a second for use on-site.

In the development environment, the download of software and data to the PowerPCs is controlled using the Tornado 2 development system. This is achieved using two applications; the Tornado Registry and the Tornado FTP Server which are in turn controlled by the Tornado 2 application itself.

3.1.1.1 Rochester Development Environment

At Rochester, there are four development rigs housed in Lab 4. Each of these comprise an Avionics Rig, a ND, an In House Test Platform (IHTP) (either desktop or laptop) and, optionally, an MCDU. Each PowerPC and IHTP are connected to the site ethernet network.

In the lab, the IHTP provides the DCP, MCP and, optionally, MCDU functionality whilst the CCD is a standard serial (RS232) PC mouse or trackball.

The Registry and FTP Server applications are run on a dedicated PC that is also housed in Lab 4 and is attached to the company site network.

Flight software and configuration files for the FMU and CMU may be held anywhere on the Rochester site network that is accessible to the MA-AFAS programme personnel. Control of the location of the software components is provided by script files; one for each PowerPC. Details of these script files are given in Appendix B.

Database and logged data are held on the Rig Hard Drive. This can be moved between the rig and the supporting IHTP using the Tornado 2 facilities.

3.1.1.2 On-Site Development Environment

There are currently two full development environments on-site, one at QinetiQ and the other at DLR. These systems comprise an Avionics Rig, a ND, an MCDU and an IHTP. Both systems are configured the same with the IHTP performing the role of the Tornado Registry and FTP Server. Two other on-site rigs have also been deployed; one at QinetiQ and one at AMS (Rome). These are Ethernet based and comprise an Avionics Rig, a NDU and a PC that runs the IHTP (and other) software application. The full development units support the modification and patching of the flight software whilst the others just provide a host for Tornado2.

These systems are standalone; i.e. they do not connect to the Rochester site network (or, indeed, any site network). Thus all the software and configuration data are held on the IHTP Hard Drive. Only released flight software will be available initially and will use the path ‘C:/MA-AFAS/Build_xx’ where xx signifies the build (i.e. A, B, C1, C2, etc).



3.1.2 Flight Environment

In the Flight Environment, there is no associated PC to hold the operational software. Instead, all software, configuration and database data will be held on the Avionics Rig Hard Drive Unit. At switch-on, the Avionics Rig processors will automatically organise the transfer and running of the flight software without operator action.

3.2 Powering Up the System

To provide the necessary data inputs for this equipment, the system is fitted either to an aircraft, simulation rig or In House Test Platform (IHTP). The powering of these external systems is not included in this document.

3.2.1 MA-AFAS Avionics Rig

Each of the Avionics Rigs is powered from the 240VAC mains supply. To energise a unit, the On/Off switch positioned at the lower right corner of the front panel (see Figs 1 and 2) should be operated. Confirmation of the power being applied is achieved by the internal fans operating, and the status lights on the PowerPC front panels flashing.

3.2.2 MCDU

The MCDU is powered from a 28VDC supply. At Rochester, a switched outlet for this is available at each bench with the MCDU permanently connected to the outlet. When power is applied to the MCDU, it performs a switch-on BIT sequence where each lamp is tested. At this point, MCDU configuration activities may be undertaken.

When the system (Avionics Rig and MCDU) is ready for operation, the MCDU screen is set to the MCDU Menu Page 1 display.

3.2.3 Navigation Display Unit

The NDU used in the development environment is a standard PC monitor driven from the 240VAC mains supply. Most NDUs have On/Off switches and associated Power On indicators on the front panel.

In the On-site and flight environments, the display units are considered part of the local fit and are not further described here.

3.3 Initialisation

Initialisation of the MA-AFAS involves the downloading of the operating system, flight software, configuration data and database from permanent storage into the PowerPC’s. In the Flight Environment, this process is automatic as determined by the parameters stored in the non-volatile memory of each PowerPC card.

For the development environment, the loading of the operating system is automatic but the loading software and data into the PowerPCs is controlled by the operator. This process is further described in Appendix A.

During the initialisation sequence, the Navigation Display generates a test sequence of images. At the end of initialisation, if the MA-AFAS is not receiving commands and data from the aircraft systems then the last test image, a flashing rectangle, remains on the screen. Otherwise, the ND displays the image commanded by the Display Control Panel of the aircraft system.

The end of the initialisation process the MCDU generates the Aircraft Configuration Screen (Fig 3).



3.4 System Indicators

Three of the cards that make up the Avionics Rig have status indicators.

Both CPU cards are identical and host four indicator LEDs; SCSI BUSY, PIB BUSY, BFL and CPU. When being reset, all for indicators are lit as a lamp test facility. When in normal operation, only the CPU LED will be illuminated indicating the level of processor activity currently being undertaken; usually, it just flickers dimly. The BFL LED (orange) will indicate a board fault when one is detected. The PIB BUSY LED will always remain unlit as this interface is not used for MA-AFAS. The SCSI BUSY LED may be seen to flash but usually remains off.

The ARINC429 interface card hosts 16 activity LEDs and two Status LEDs. Each LED is capable of displaying off/green/red indications.

The status indicators are used to show the status of the two controlling devices on the card; each device handles eight I/O channels. When power is first applied to the card, the status LEDs will show red. When the software for the FMU has loaded and started running, the LEDs will turn green.

Activity monitors identify which channels are receiving/transmitting data according to Table 1. As with the Status monitors, green indicates correct operation and red, a malfunction. Note that for those interfaces that only output data sporadically, the LED will flash.

Channel No Usage

1 Not Used

2 Engine Management System Receive

3 Not Used

4 Not Used

5 Not Used

6 Not Used

7 MCDU Transmit

8 Autopilot Transmit

9 Not Used

10 Autopilot Receive

11 SBAS Receive

12 Data Puddle Receive

13 DADC Receive

14 GBAS Receive

15 IRS Receive

16 MCDU Receive

Table 1. ARINC 429 Interface Activity Lamps

3.5 An Overview of the System Operation

Whilst Section 4 describes the operator actions required to operate the system, this section is intended to give a brief overview of the system operation.



3.5.1 System Initialisation

For the BAC1-11 configuration, there is no initialisation required; everything is automatically configured from the initialisation files on the hard drive. For the ATTAS configuration, however, there are a couple of items that need initialisation that need to be carried out prior to successful operation of the system.

The Avionics Rig on the ATTAS uses position and time data from the VDL4 transceiver. This has to be selected manually from the NAV DATA SOURCE page (off the INIT/REF and SET UP pages - see 4.2.3.2.2).

Similarly, the Avionics Rig needs to be initialised with the current date. On the BAC1-11 configuration, this data is received from the SBAS and/or GBAS. On the ATTAS, however, this data is not available to the Avionics rig and has to be manually entered (See 4.2.3.5). Both these activities must be performed before the Avionics Rig can generate a Nav Display.

Fuel and aircraft weight are needed for the trajectory calculations. These data items can be initialised by the reception of LOADSHEET data over the datalink. Alternatively, they can be manually input using the LOAD INFO page as defined in 4.2.3.3.

3.5.2 Route Planning

The initial step following system start-up is to define a Route to fly. This is achieved using the ROUTE, LEGS, DEP/ARR and VNAV pages.

Route definition initially requires the inputting of the Origin and Destination using the ROUTE page; these definitions identify the airport and runway for the start and end of the flight. If the runways available at an airport are unknown, the ARR/DEP page cane be used to select a runway.

Next, the intermediate waypoints are defined using either the LEGS page(s) for manual entry, or the CO ROUTES page to use a pre defined set of waypoints. When manually entering or editing waypoint data, the user can define further constraints, such as turn type and time and height at waypoint.

The SID and STAR can then be selected for the Origin and destination airport using the DEP/ARR pages.

Finally, the Cruise Altitude, Estimated Off Block Time (EOBT) and Calculated Take Off Time (CTOT) are entered and the system instructed to generate a trajectory using the VNAV page.

3.5.3 Communications Functions

Whilst the MA-AFAS is active, data can be transferred between ground functions, specifically the ATC and AOC, and the aircraft via datalink.

Data received from the AOC include the loadsheet, which defines the fuel, passengers and baggage weights, Flight plan data and weather reports. These are then used by the Trajectory Generator to compute the trajectory the flight will use. The operator can also compile messages for transfer to the AOC; requests for meteorological data and Snag reports.

To receive data from the Air Traffic Controller, the MA-AFAS operator needs to Logon to the network using the LOGON page. After this, selecting the ATC Function key on the MCDU will display a received message or, if no message has been received, the message compilation page. Reception of data is signalled by a message in the scratchpad area of the MCDU.

Once data has been received, the operator can incorporate it into the MA-AFAS database for inclusion in the trajectory generation calculations.

3.5.4 In Air Functions

Once the aircraft is airborne, the MA-AFAS can be set to control the actions of the autopilot by pressing the EXECUTE programmable key on the VNAV page, or the EXEC Function key of the MCDU. This passes control of the system to the Autopilot control panel that can then be used to engage vertical, lateral and/or speed control from the MA-AFAS. During flight, the progress of the aircraft and the MA-AFAS can be monitored using the PROGRESS pages on the MCDU and the Navigation Display on the NDU (See section 4.3).

The scratchpad area of the MCDU is used to inform the operator of system activities that have occurred; e.g. data received over the datalink or system messages. Appendix C gives a description of the possible messages.

3.6 System Reset

During development and trials, it is anticipated that the system may occasionally need resetting.

For the Flying environment, this action may be performed by the re-cycling of power to the Avionics rig and/or the MCDU. Upon re-application of the power, the unit(s) will restart as described above. Note that it is possible to reset the CMU independently of the FMU by using the reset button on the CMU PowerPC but this action is not recommended.

In the development environment, Tornado2 provides a reset capability as described in Appendix A.

3.7 Powering Down the System

Powering down the system is simply a matter of removing the power feeds to each of the components. There is no recommended power down sequence.

3.7.1 Extraction of Data Logs

During every run of the Avionics Rig, a number of log files are generated. These detail the actions undertaken by the rig during the sortie and can be used to aid diagnostics in case of problems. Under normal circumstances, the files, which reside on the SCSI hard drive in the chassis, are either deleted or overwritten when the flight software is loaded and run. The method of data extraction varies depending upon the circumstances of the equipment installation.

3.7.1.1 Extracting Logged Data From Bench Rigs

For the bench rigs, and the BAC1-11 rig when running with the Tornado2 environment provided by the carry on laptop, the required ethernet cables will already be in place.

The FMU should be rebooted and when the process is complete the log extraction script should be run using the following command:

<CopyLoggedData.spt

This script, detailed in Appendix B3, copies the log files to the ‘c:/Logged Data’ directory of the laptop.

3.7.1.2 Extracting Logged Data From Aircraft

To extract the data logs for aircraft based systems, the ‘carry on’ IHTP needs to be connected to the Avionics Rig. For the BAC1-11 aircraft installation, this is accomplished by connecting the Laptop ethernet port to the hub in the avionics rig chassis using a standard ethernet cable. For the ATTAS, the ethernet port on the FMU (LAN1) should be connected, using a ‘crossover’ ethernet cable.

Note: This should be done whilst the rig is unpowered following a sortie.



The following sequence extracts the logged data:

a) Run the Tornado FTP Server on the laptop computer:

b) Power up rig

c) File transfers are automatically performed to the ‘C:/Logged Data’ directory of the laptop.

d) Switch off Avionics Rig and disconnect the ethernet cable.



4 OPERATOR ACTIONS This section describes the operator actions required to use a MA-AFAS Avionics Rig. Control of the system is provided by four operator input devices:

MCDU

NDU with Cursor Control Device (CCD)

Display Control Panel (DCP)

Autopilot Control Panel (also known as Master Control Panel (MCP))

4.1 MCDU

The MCDU is the prime operator interface for MA-AFAS and allows control of the system via a hierarchical menu structure. The full structure is defined in D54.

The MCDU (see Fig 4) provides the operator with a graphical display surface, 8 message lamps, 12 programmable function keys, 10 function keys and an alphanumeric keypad.

4.1.1 MCDU Display

The display surface comprises a 4” x 4” AMLCD that, for MA-AFAS, is used to display 14 rows of 24 alphanumeric characters. The screen is divided into 3 parts: a one line title, 12 lines of programmable key control and 1 line scratchpad area for the display of messages and the input of data.

4.1.1.1 The Scratchpad

The bottom line of the MCDU display, called the scratchpad area, is reserved for the display of Alert messages and the inputting of data to the system.

4.1.1.1.1 Scratchpad Messages

Any activity that requires the operator to be made aware that the activity has occurred will result in a message being displayed in the scratchpad area and the MSG lamp being illuminated. The colour of the text used in the scratchpad area signifies the severity of the message.

INFORMATION messages are displayed in WHITE text.

ALERT messages are displayed in AMBER text.

A list of messages is given in Appendix C of this document.

Messages can be removed (acknowledged) by use of the delete key. When acknowledged, the message is removed from the scratchpad and placed in the message log. The MSG lamp is extinguished.

4.1.1.1.2 Data Entry Using the Scratchpad

For data entry that comprises a single line, e.g. a position or altitude, the operator uses the alphanumeric keypad to type the data into the scratchpad. When complete, the data is entered into the correct field by use of the appropriate programmable key. At this point, the data entered will be tested for format and, if acceptable, entered into the relevant field.

To enter free text into the system, the operator selects the relevant text entry page and types the required information using the alphanumeric keypad. Each time the space key (SP) is pressed, the word entered is transferred from the scratchpad area to the main screen. Word wrapping is



automatically performed. If an error is detected in a word already entered into the main display, the operator can use the ‘BCK’ programmable key to select the word for editing. Once edited, the space key is used to return the word to the main screen.

Errors in the format/value of entered data are notified using the scratchpad prior to the data being used.

4.1.2 MCDU Controls

Controls for the MCDU are provided by the following buttons:

12 programmable function keys positioned either side of the display surface,

10 Function keys,

an alphanumeric keypad with characters 0 to 9, A to Z, ., +/-, /, Space and CLR,

5 control keys; MENU, PREV, NEXT, EXEC and BRT

The function keys allow quick access to the MA-AFAS functionality as defined in Table 1. Finer control and data input are provided by the programmable keys positioned to the left and right of the display panel. The function of each of the programmable keys is identified to the user on the display surface itself.

Data is entered using the alphanumeric keypad in conjunction with the scratchpad and the programmable keys.

Figure 3 MA-AFAS MCDU

Left Programmable Keys

Right Programmable Keys

Function Keys

Alphanumeric Keypad



Key Label MA-AFAS Functionality

INIT REF Allows initialisation and mode selection

RTE Provides an interface for Route inputting

DEP ARR Allows selection of arrival and departure procedures

LEGS User interface for waypoint entry

PROG Flight progress pages

ATC ATC Comms Functions

ASAS Allows ASAS functionality selection and control

VNAV User interface for Vertical Navigation functionality

HOLD Holding Pattern Entry/Review Function – Not Available in this version

FIX Fix – Not Available in this version

Table 2. MCDU Function Keys

4.2 MCDU Pages

The following sub-sections of the document detail the menu tree for each of the functions given in Table 1. To aid following a chosen path, hyperlinks have been included in the electronic version allowing the reader to click on the associated programmable key text (L1 – L6, R1 – R6) and be taken to the next menu page. Similarly, the titles of the figures include the soft key title in brackets at the end of the line.



4.2.1 FMS Initialisation Pages

M C D U M E N U 1 / 2

L1 R1

L2 R2

L3 R3

L4 R4

L5 R5

L6 R6

Figure 4 MCDU Menu Page 1

When the MCDU is initially powered, it performs a self test routine. This routine includes a lamp test that illuminates each lamp once. At the end of the tests, page 1 of the MCDU Menu is displayed; if the Avionics rig is not functioning, i.e. still initialising, switched off, etc., the rest of the display remains blank.

Following the MCDU self test routine, the operator is free to use the NEXT or PREV control key to display page 2, which gives access to the built in maintenance functions of the unit.

M C D U M E N U 2 / 2

L1 R1

L2 R2

L3 R3

L4 R4

L A M P T E S T ( O F F ) L5 ◄ S E L E C T O N P / N ► R5

L6 ◄ P A R A L L A X M A I N T ► R6


The Operating the L5 programmable key will repeat the switch-on lamps test for diagnostic purposes.

General Information and parallax adjustments are selected using the P/N (R5) and PARALLAX (L6) programmable keys. Advanced set-up parameters are available using the MAINT (R6) programmable key.

The functionality that is relevant to the configuration of the unit for MA-AFAS is described in section 7. All other functionality is described in the manufacturers documentation.

When the Avionics Rig has finished its boot procedure and has loaded and started the flight software, Page 1 of the MCDU MENU displays ‘FMS1’ in the L1 position. At this point, the system operation may be continued by pressing the L1 key. This will result in the display of the FMS Ident page.

M C D U M E N U 1 / 2

L1 ◄ F M S 1 < M E S S A G E > R1

L2 R2

L3 R3

L4 R4

L5 R5

L6 R6


Optionally, a message may be displayed following the ‘FMS1’. This message may be:

<REQUESTING> The Avionics Rig requires the operators attention

<ACTIVE> The Avionics Rig is active following a link failure but not requesting user action

<TIMED OUT> A loss of communication has been detected

4.2.2 FMS Ident

F M S I D E N T

L1 R1

N A V D A T A A C T I V E L2 E U R O P E N O V 1 0 - D E C 2 9 / 0 0 R2

L3 R3

O P P R O G R A M C F G N O L4 M A - A F A S B U I L D E 1 R4

L5 R5

L6 R6

T R A J I N I T - S U C C E S S MENU PREV NEXT INIT REF RTE DEP ARR LEGS PROG EXEC

1 2 3 ASAS ATC VNAV HOLD FIX BRT

4 5 6 A B C D E F G

7 8 9 H I J K L M N

. 0 % O P Q R S T U

/ SP V W X Y Z CLR

Figure 7 FMS Ident Screen

This page, shown in Fig 7 along with a representation of the keypad, is the initial screen presented to the operator following startup initialisation. It identifies the configuration of the system in use by displaying the Navigation Database source, the operational software Id and the software build standard.

Details of the Navigation Database are derived from the data held on the Hard Drive. The data displayed defines the area of coverage and the validity dates for the installed database.

The Operational Program item defines the name of the software used in the Avionics Rig and the CFG No defines the current build standard of the Avionics Rig software.

Once the operator is satisfied that the configuration is correct, system initialisation/operation can be started using the L6, R6 or function keys of the MCDU.

Fig 7 also shows the display of a system message in the Scratchpad area; further details of scratchpad messages are given in Appendix C.

Comment: Keys depicted on this and subsequent MCDU pages are live hyperlinks

4.2.3 System Initialisation (INIT/REF)

I N I T / R E F 1 / 2

L1 R1

L2 R3

L4 F I S - B > R4

L5 < S E T U P R5

L6 < L E G S M S G R E C A L L > R6

Figure 8 INIT/REF Screen 1

This page is displayed by selecting the INIT/REF function key or soft key and allows the operator to input and/or review initialisation parameters for the MA-AFAS.

Two INIT/REF pages, selected using the NEXT/PREV keys, provide a simple menu that allows access to the various system initialisation pages. Table 3 gives a brief description of each available key on the two screens.

I N I T / R E F 2 / 2

L1 R T E D I S C O N > R1

L2 C M L O G O N > R2

L3 D A T E T I M E > R3

L4 R4

L5 < F U E L R5

L6 < F L I G H T L O G R6

Figure 9 INIT/REF Screen 2

RTE DISCON – Not Implemented

FLIGHT LOG – Not Implemented



Function Description

IDENT Returns to the IDENT page

POS INIT Allows Position and Time initialisation

SET UP Allows Nav Display and VDL4 Transponder set up

LEGS Not Implemented in Build E

NAV DATA Displays data from the internal database to the operator

AOC Allows access to the AOC pages

FIS-B Allows the set up of FIS-B comms messages

MSG RECALL Recalls previous alert messages

FUEL Displays the fuel and weight information

FLIGHT LOG Not Implemented in Build E

RTE DISCON Not Implemented in Build E

CM LOG ON CPDLC Logon page

DATE/TIME Provides an interface for the input of Date and Time information

Table 3. System Initialisation Menu Description

4.2.3.1 Position Update (POS INIT)

P O S I N I T 1 / 2 F M S P O S G P S

L1 N 5 2 : 1 9 . 1 5 E 0 1 0 : 3 3 . 3 7 R1

R E F A I R P O R T L2 E D V E N 5 2 : 1 9 . 1 5 E 0 1 0 : 3 3 . 3 7 R2

G A T E L3 B G 1 N 5 2 : 1 9 . 2 3 E 0 1 0 : 3 4 . 0 0 R3

L4 R4

U T C D A T E L5 1 7 5 7 : 0 4 F E B 1 7 / 0 3 R5

L6 R6

Figure 10 Initial Position Screen (POS INIT)

P O S I N I T 2 / 2 F M S P O S G P S

L1 N 5 2 : 1 9 . 1 5 E 0 1 0 : 3 3 . 3 7 R1

G S 1

L2 5 K T R2

L3 R3

L4 R4

L5 R5


Figure 11 Position Reference Screen (POS REF)

These screens present the operator with the current aircraft position. Selection between the two is achieved using the NEXT/PREV keys on the MCDU.

The currently available position source is displayed at the top of page 1 in the FMS POS data item. This will display one of the following:

GPS

If data from a GPS based system is available, these pages will display the current time and position data received from that system.

If the aircraft is in the location of an airport that is held in the MA-AFAS database, then the REF AIRPORT entry will be displayed. Gate data, is only entered by the operator, however.



If a valid GPS data source is not available, the operator is able to enter values for UTC and DATE fields using the DATE TIME page.

Navigation to the INIT/REF and ROUTE MCDU pages are provided by the L6 and R6 keys, respectively.

4.2.3.2 FMS Set Up (SET UP)

F M S S E T U P D I S P L A Y ( M A G )

L1 < S E L E C T T R U E R1

L2 R2

M A P ( H E A D I N G ) L3 < S E L E C T T R A C K R3

L4 < T R A N S P O N D E R R4

L5 < N A V D A T A S O U R C E R5


Figure 12 FMS Set Up Screen (SET UP)

The FMS setup page, selected from the INIT/REF page, allows customisation of the heading information on the Navigation Display and leads to the VDL Mode 4 transponder setup page and the Navigation data source selector page.

Programmable key L1 allows the selection of True or Magnetic data for display on the Nav Display. Similarly, key L3 allows selection of Track or Heading data for display on the Nav Display. Any combination of the data is allowable.

To change between the types of data, the user operates the L1 (Mag/True) or L3 (Heading/Track) programmable keys. The current selection is shown in brackets.

4.2.3.2.1 Transponder Settings

T R A N S P O N D E R S E T T I N G S S T A T E ( O F F ) F R E Q U E N C Y

L1 < S E L E C T O N 1 3 8 . 5 0 0 M H Z R1

L2 R2

P O W E R ( H I G H ) L3 < S E L E C T L O W R3

L4 R4

M O D E ( T R A N S ) L5 < S E L E C T E T H E R N E T R5

L6 < F M S S E T U P R6

Figure 13 Transponder Settings Screen)

The VDL Mode 4 Transponder communicates via an RS232/RS422 serial link controlled by the CMU. Some of the operational parameters of the transponder are configurable using this page on the MCDU.

Note: This page is not operational for the MA-AFAS Trials.

The L6 key returns to the FMS SETUP page.

4.2.3.2.2 Navigation Data Source Selection (NAV DATA SOURCE)

N A V D A T A S O U R C E

L1 G B A S < S E L > R1

L2 S B A S R2

L3 V D L 4 R3

L4 B E S T R4

L5 I R S R5

L6 F M S S E T U P > R6

Figure 14 Navigation Data Source Selection Screen (NAV DATA SOURCE)

This page, reached from the FMS SETUP page, allows selection of the source of navigation data for use in the MA-AFAS. On initial entry, from the FMS SETUP page, the GBAS source is the one selected. The operator can select a different source by pressing the programmable key adjacent to the required source. If the chosen source is unavailable, then an alternative is chosen following the priority list given in Table 4 below

Priority Source

1 GBAS

2 SBAS

3 VDL4

4 IRS

Table 4. Navigation Data Source Priorities

The BEST option constantly monitors the sources and selects the best available according to Table 4.

Note: For the ATTAS installation, the VDL4 selection must be used.

4.2.3.2.3 Nav Data

N A V D B R E F I D

L1 - - - - - R1

L2 R2

L3 R3

L4 R4

L5 R5

L6 < I N I T / R E F R6

Figure 15 Navigation Data Display Screen (REF NAV DATA)

This page is displayed by following the NAV DATA link on the INIT/REF page. It allows interrogation of the Navigation Database using the name of an item within the database. Fig 16 gives an example of a query for an airport with the Ident EGKK (Boscombe Down).

N A V D B I N F O I D R E G I O N T Y P E

L1 E G K K E U R A I R P O R T R1

L A T - L O N G L2 N 5 1 ° 0 8 . 8 8 W 0 0 0 : 1 1 . 4 2 R2

E L E V A T I O N L3 + 1 9 6 F T R3

L4 R4

L5 R5

L6 < I N I T / R E F R6

Figure 16 Example Navigation Data Display Screen

Note: Only queries about Airports will be available for the MA-AFAS Trials.

4.2.3.2.4 Message Recall

M E S S A G E R E C A L L

L1 ! T G U N D E F I N E D E R R O R R1

N E W T R A J A V A I L A B L E L2 R2

L3 R3

L4 R4

L5 R5

L6 < I N I T / R E F R6

Figure 17 Message Recall Screen (MESSAGE RECALL)

The Message Recall screen allows the operator to review the last 10 messages generated by the MA-AFAS. No operator interaction is available on this page.



4.2.3.3 Aircraft Load Display (FUEL)

M O D F U E L D E T A I L S

L1 R1

F U E L Z F W L2 0 . 0 0 1 7 5 0 0 . 0 0 R2

C A R G O L3 0 . 0 0 R3

N O . P A S S E N G E R S L4 - - - R4

T A K E O F F W E I G H T L5 1 7 5 0 0 . 0 0 R5

L6 L O A D > R6

Figure 18 Aircraft Load Page (FUEL)

The FUEL page displays some of the data received in the Loadsheet from AOC via the datalink. The data parameters are described in Table 5. When data has been added or modified, the magenta MOD flag is displayed in the top left corner of the display, and a LOAD function enabled. The LOAD button (programmable key R6) is used to accept the data and loads it into the Trajectory Generator. Upon LOADing the data, the MOD and LOAD symbology are removed.

Parameter Description

FUEL Weight of fuel loaded into the aircraft

ZFW Zero Fuel Weight of the aircraft (e.g. ATTAS = 16500)

CARGO Weight of cargo loaded in the hold

NO PASSENGERS Number of passengers on flight (1 passenger = 75kg)

TAKEOFF WEIGHT Sum of the above components

Table 5. Loadsheet (FUEL) Page Items



4.2.3.4 CM Logon (CM LOGON)

C M L O G O N L O G O N 1

L1 A B C D E F G H R1

L O G O N 2 L2 - - - - - - - - R2

L O G O N 3 L3 - - - - - - - - R3

L O G O N 4 L4 - - - - - - - - R4

L O G O N 5 L5 - - - - - - - - R5

L6 A T C > R6

C M L O G O N S U C C E S S F U L Figure 19 CM LOGON Page (CM LOGON)

Prior to data being transmitted/received over the CPDLC link, the aircraft has to be registered on the network using the CM LOGON process. The CM LOGON page, shown as Fig 19, provides the user interface for this. For MA-AFAS testing, the ground facility Id used is ABCDEFGH. When successful, the message CM LOGON SUCCESSFUL is displayed in the scratchpad. Other messages associated with CM LOGON are !ALREADY LOGGED ON , LOG ON TIMEOUT, LOG ON FULL and FAILED TO LOG ON.



4.2.3.5 Date and Time Entry Page (DATE TIME)

M O D D A T E T I M E E N T R Y

L1 R1

D A T E L2 3 0 / A P R / 2 0 0 3 R2

T I M E L3 H H . M M . S S R3

L4 R4

L5 R5

L6 L O A D > R6

Figure 20 Date and Time Entry Page (DATE/TIME)

In the ATTAS configuration, there is no available source of GPS date information available to the Avionics Rig. This short fall is compensated for by the ability to enter the current date manually using the Date entry page shown in Fig 20.

Date information is entered using the scratchpad entry routine with the format DD/MM/YYYY (this can be truncated to DD/M/Y). When data is entered into the DATE or TIME fields, the MOD flag and LOAD> prompt are displayed until the data is LOADed into the system



4.2.4 Route Planner (RTE)

R O U T E O R I G I N D E S T

L1 E G D M - - - - R1

R U N W A Y R U N W A Y L2 - - - - - - - - R2

F L I G H T N O L3 - - - - - - - - R3

C O R O U T E L4 - - - - - - - - R4

L5 R5

L6 C O R O U T E S > R6

R W 0 5 Figure 21 Route Planner Page (RTE)

The Route Planner page allows the operator to define a route in terms of an origin airport and runway, a destination airport and runway and an identifier. This data is keyed in by the operator but may also be obtained from the Company Routes database by use of the CO ROUTES option.

Item Item Description

Origin ICAO identifier of airport at start of route

Runway Takeoff runway identifier of airport at start of route

Dest ICAO identifier of airport at end of route

Runway Landing runway identifier of airport at end of route

Flight No An alphanumeric identifier string of up to 8 characters

Co Route Display of the currently selected Company Route. Can be automatically entered using the CO ROUTES menu item (R6)

Table 6. Route Planner Page Item Description (RTE)

To enter an airport, the airport identifier, as defined by the Nav Database, is typed into the scratchpad and entered into the system as the Origin or Destination using the appropriate programmable key. If the airport identifier is recognised by the Database Manager, then the data is accepted. If the identifier is not in the database, then the message !NOT IN DATABASE is displayed. Fig 21 shows the ORIGN airport as EGDM (Boscombe Down).

Similarly, to enter a runway the operator keys the identifier into the scratchpad and enters the data using the appropriate programmable key. As before, if the identifier is not in the database, then the message !NOT IN DATABASE is displayed. The runway data is entered in the format of ‘RWnna’ where nn is the standard 2 digit numeric runway identifier (e.g. 23) and ‘a’ is the Left or Right identifier. Note, if the runway is a single one then the L or R suffix is omitted. Fig 21 shows the entry of runway 05; to complete the entry of data, the operator needs to press the L2 or R2 programmable keys.

Flight Number is an alphanumeric string of up to 8 characters entered via the scratchpad. The first character must be in the range A-Z or the message !INVALID ENTRY is displayed.



Once the ORIGIN and DEST information has been entered, the user can fill in the rest of the flight plan by selecting the LEGS option or by using the CO ROUTES menu item to select pre-entered data. When using CO ROUTE, the runway information can be entered before or after the selection of the company route.

4.2.4.1 Company Route Selection (CO ROUTES)

S E L E C T C O R O U T E 1 / 1

L1 C R 0 1 < S E L > R1

L2 C R 0 2 R2

L3 R3

L4 R4

L5 R5

L6 < R O U T E R T E D E T A I L S > R6

Figure 22 Company Routes Selection Page (CO ROUTES)

The company routes selection page(s) lists all the routes stored in the database on the system hard drive that have the destination and origin airports. Appendix A2 defines the format of this file and how to add further routes to the system. Fig 22 shows the display of two pre-defined routes in the database; CR01 and CR02 with the operator having selected CR01 as the required route using the L1 programmable key.

The selection of a route enables the RTE DETAILS option on programmable key R6. Operating this displays the details of the company route in a RTE DETAILS page as shown in Fig 23.

In case of error, deselection of a selected route is accomplished by re-selection of the route. Similarly, selection of another route may be accomplished by operating the left programmable key adjacent to the required route.



R T E D E T A I L S 1 / * V I A T O

L1 D I R E C T E G K K R1

L2 D I R E C T O C S R2

L3 R3

L4 R4

L5 R5

L6 R6

Figure 23 Company Route Details Page

The RTE DETAILS page details each waypoint in the route along with a flag to indicate whether or not the trajectory between two adjacent waypoints is DIRECT or not. Fig 23 shows that the trajectory will take the aircraft direct between the ORIGIN runway and waypoint EGKK and then direct from EGKK to OCS.

Note: only DIRECT is supported in this version of software.

4.2.5 Departures and Arrivals (DEP ARR)

D E P / A R R

L1 < D E P E G D M R1

L2 E G D M A R R > R2

L3 R3

L4 R4

L5 R5

L6 R6

Figure 24 Departures and Arrivals Page (DEP ARR)

On pressing the ARR/DEP function key, the Arrivals and Departures menu page, shown in Fig 24, is displayed. The pages associated with this function allow the display and editing of the procedures required at take off (SIDS) and landing (STARS). When initially displayed, this page identifies the departure and arrival airport entered in the ROUTE page.

Progress is made by selecting either the L1 (DEP) or R2 (ARR) programmable key.

4.2.5.1 Arrivals

A R P T A R R I V A L S 1 / * S T A R S R O U T E R U N W A Y S

L1 B I G 1 E < S E L > R W 0 8 R R1

L2 B I G 7 F R2

L3 B I G 3 A R3

L4 B I G 3 B R4

L5 B I G 3 C R5

L6 < E R A S E D E P / A R R > R6

Figure 25 Airport Arrivals Data Page(s)

This display comprises a number of pages that may be selected using the NEXT and PREV function keys. When first invoked, the Arrivals page lists the Standard Approach Routes for the Destination airport (as entered using the RTE page) on the left hand side of the page(s). This data is obtained from the Navigation Database. An example page is shown in Fig 25. The operator can then select the required procedure by using the appropriate left programmable key on the appropriate page. Once a selection is made, the list disappears and is replaced by the selected procedure name followed by <SEL> to indicate that a selection has been made. This is shown in Fig 26.

The right hand side of the Arrivals page is similar but lists the available runways (as defined by the database) at the destination airport. If a runway has already been entered in the RTE page, then this will have been pre-selected upon entry into this page (as shown in Figs 25 and 26). A destination runway selected using this page will be transferred to the ROUTE page.

E G L L A R R I V A L S 1 / 1 S T A R S R O U T E R U N W A Y S

L1 B I G 1 E < S E L > < S E L > R W 0 8 R R1 T R A N S A P P R O A C H

L2 L O G A N < S E L > P 0 8 R2

L3 R3

L4 R4

L5 R5

L6 < E R A S E D E P / A R R > R6

Figure 26 Selected Airport Arrivals Data Page

Note: selection of the R1 or L1 programmable key once a selection has been made will de-select the item and restore the list of available selections.

The displayed STARs and runways are ordered in alphabetical order; items that have been added using supplimentary files will be appended at the end of the list, also in alphabetical order.

Below the chosen STAR the Transit waypoint defined in the database is identified beside the L2 programmable key.

Once a runway has been selected, Precision Approach data is displayed under the title APPROACH. In the case of more than one option, all options shall be listed. When the operator selects the desired PA, the list is reduced to the selection, and the text <SEL> prepended to the selection name.

The erase function is not available for the MA-AFAS Trials.

4.2.5.2 Departures

A R P T D E P A R T U R E S 1 / * S I D S R O U T E R U N W A Y S

L1 B I G 3 P R W 0 8 L R1

L2 B I G 7 M R W 0 8 R R2

L3 B O G N 1 M R W 2 6 L R3

L4 C L N 5 P R W 2 6 R R4

L5 C L N 8 M R5

L6 < E R A S E D E P / A R R > R6

Figure 27 Airport Departures Data Page(s)

When first invoked, the airport departures page displays lists of the Standard Instrument Departures (SIDS) and available runways at the ORIGIN airport. This includes both the standard database information as well as any supplementary data held on the MA-AFAS hard drive. The user can then select the required procedure and runway using the appropriate left and right programmable keys.

Selecting the L3 and R1 programmable keys in Fig 27 will result in the display shown in Fig 28.

Once a selection has been made, re-selecting the L1 (SIDs) or R1 (Runways) programmable key cancels the selection and returns the full list.

Below the chosen SID, the Transit waypoint defined in the SID database is identified beside the L2 programmable key

A R P T D E P A R T U R E S 1 / 1 S I D S R T E 1 R U N W A Y S

L1 B O G N 1 M < S E L > < S E L > R W 0 8 L R1

T R A N S L2 B O G N A < S E L > R2

L3 R3

L4 R4

L5 R5

L6 < E R A S E D E P / A R R > R6

Figure 28 Selected Airport Departures Data Page



The displayed SIDs and runways are ordered in alphabetical order. Items that have been added using supplimentary files will be appended at the end of the list, also in alphabetical order.

Note that if the departure runway is specified in the ROUTE page then the full runways list is not initially made available in the DEPARTURES page. Instead the specified runway is pre-selected.

The erase function is not available for the MA-AFAS Trials.

4.2.6 Waypoint Entry (LEGS)

L E G S R T E 1 / 1 T H E N

L1 # # # # # R1

T H E N L2 # # # # # R2

D I S C O N N E C T L3 R W 0 8 R3

L4 R4

L5 R5

L6 < L A T L O N G R T A > R6

Figure 29 Initial Waypoint Id Data Entry/Display Page

These pages are used to enter and review data for the en-route waypoints between the origin and destination airports. Waypoints can be entered as points found in the nav database; Airports, navigation beacons, etc., or latitude/longitude positions. Each waypoint also has an associated aircraft height. Optionally, the time that the aircraft is to be at the waypoint can be added.

Data may be entered either manually or by use of the Company Routes supplementary database.

There are two methods of manual data entry; by Waypoint name, using the page displayed above, or by latitude/longitude co-ordinates using the LATLONG page.

When entering data manually, on initial entry to the page only the DESTINATION information will be displayed as shown in Fig 29. To enter further en-route waypoints (up to 40 points are permissible in the current build) the user must use the scratchpad data entry routine to enter the waypoint name as defined in the database. An error !NOT IN DATABASE will be generated in the waypoint name does not have a match in the database.

Once the data has been entered into the scratchpad area, the user enters it into the system using one of the Left programmable keys.

To enter the waypoint in the middle of a list, the left programmable key next to the waypoint that should follow the new waypoint should be used. E.g. in Fig 29, to enter a waypoint between D262B and GE, the L3 programmable key should be pressed.

To enter the waypoint at the end of the list, the programmable key next to the ‘#####’ placeholder should be used. Note: associated with the placeholder is the DISCONNECT flag, positioned just below the placeholder. This identifies that the initial and/or final waypoint, i.e. the destination runway as entered on the ROUTE page, is not yet connected to the rest of the waypoints. Similarly, the discontinuity will occur when a SID or STAR is used. A message, !DISCONTINUITY EXISTS will be displayed in the event that a trajectory generation is performed when there is one, or more, disconnects in the route.

M O D L E G S R T E 1 / * 1 2 3 1 7 . 2 3 N M

L1 E G G D 7 5 0 0 R1 2 7 2 2 . 5 1 N M

L2 D 2 6 2 B / O V R A 1 0 0 0 0 R2

0 7 8 1 . 7 9 N M L3 G E / A R C C R S A L T R3

0 7 8 2 . 9 4 N M L4 D 0 8 2 C B 5 0 0 0 R4

T H E N L5 # # # # # R5

L6 < L A T L O N G R T A > R6

Figure 30 Waypoint Id Data Entry/Display Page(s)

Once completed, data displayed on the LEGS RTE page for each waypoint comprises a waypoint name (green), distance and bearing to the next waypoint (white, just below the waypoint name) and an altitude at the waypoint (white at the end of the line).

Deletion of a waypoint is accomplished by use of the CLR keypad key. With the scratchpad empty, operation of the CLR key results in the word DELETE being entered into the scratchpad. Operation of any of the left programmable keys will result in the deletion of the waypoint at that position. Cancellation of the delete operation is achieved by operating the CLR key a second time.

Whenever the route data is being modified, a magenta MOD flag is positioned at the left side of the Title bar as shown in Fig 29. This is removed when a trajectory has been generated using the data.

4.2.6.1 Waypoint Selection

If the waypoint name entered by the user has more than one match with the database, the SELECT WPT page is displayed to allow the user to select the required waypoint from all the matching entries. Fig 30 shows the result if BHD is typed into the LEGS page. Selecting the relevant left programmable key (L1 or L2 in this example) returns the selected data to the LEGS page, by-passing the scratchpad.

4.2.6.2 Turn Type

For each waypoint in the list, the operator has the option of defining the type of turn that the aircraft will perform at the turn. Three turn types are supported by MA-AFAS; Turn Before (Default), Turn After (Overfly, /OVR as in Fig 28) and Turn ARC (/ARC as shown in Fig 28).

The default turn type is Turn Before and this is not displayed on the LEGS page. To modify the choice, the user types /R, /A or /B into the scratchpad area and then selects the waypoint using the appropriate left programmable key. Note that /B returns the turn to the default.



S E L E C T W P T 2 / 2

L1 B H D D M E R1 N 5 4 : 2 0 . 4 3 E 0 1 2 : 4 2 . 5 9

L2 B H D V O R R2

N 5 0 : 2 3 . 9 2 W 0 0 3 : 2 9 . 6 2 L3 R3

L4 R4

L5 R5

L6 R6

B H D Figure 31 Waypoint Selection Page

4.2.6.3 Altitude Constraints

The required altitude at a waypoint can also be specified using the LEGS page. Four options are available to the user, the cruise altitude (CRSALT) which is the default for all waypoints as entered using the VNAV page, A specific height in Ft, (e.g. waypoint EGGD in Fig 28), Below a specific height (see waypoint D082C in Fig 28) and Above a specific height (waypoint D262B in Fig 28).

If a mistake is made, the correct data can be inserted using the scratchpad. In order to return the height to the default CRSALT, the CLR key should be pressed (this will put ‘DELETE’ in the scratchpad) and the right programmable key next to the required data position pressed.

4.2.6.4 Disconnects

Once all the waypoints have been entered into the system, any discontinuities must be removed by copying an adjacent waypoint into the available waypoint slot. This is achieved by operating the programmable key adjacent to the waypoint either before or after the discontinuity to copy the data into the scratchpad, and then operating the placeholder left programmable key. At this point, the DISCONNECT flags is removed. Fig 29 shows the case where the disconnect will be identified on the next page. In this case, the NEXT/PREV keys need to be used in the sequence.

4.2.6.5 Legs Lat/Long

L E G S L A T / L O N G 1 / *

L1 S A N D Y R1

N 5 1 : 0 3 . 8 5 E 0 0 1 : 0 4 . 0 5 L2 D 1 1 6 L R2

N 5 1 : 1 5 . 3 5 E 0 0 0 : 1 9 . 8 1 L3 B I G R3

N 5 1 : 1 9 . 8 5 E 0 0 0 : 0 2 . 0 9 L4 E P M R4

N 5 1 : 1 9 . 1 7 W 0 0 0 : 2 2 . 3 2 L5 W P T 0 1 R5

N 5 1 : 2 0 . 6 7 W 0 0 0 : 2 8 . 1 7 L6 < L E G S R T A > R6

Figure 32 Waypoint Lat/Long Data Entry/Display Page(s)

An alternative way of entering or viewing waypoint data is available using the LATLONG option on the LEGS page. This displays the data in terms of the Latitude and Longitude position of the waypoint along with the waypoint name. When data is entered using this method, each waypoint is given a unique name in the format: WPTnn where nn is a unique, sequential, number.

Data is entered using the format Nddmmss.thEdddmmss.th but datafields can be progressively omitted from the right hand side if zero. Thus, N512345.45E001 and N51W00123 are valid entries.

The data is entered into the scratchpad area, as usual, and then transferred to the waypoints list using a left programmable key as before.

4.2.6.6 Legs RTA

L E G S R T A 1 / *

L1 E G G D H H M M . T R1

L2 D 1 1 6 L H H M M . T R2

L3 B I G H H M M . T R3

L4 E P M H H M M . T R4

L5 D 2 9 7 D H H M M . T R5

L6 < L E G S L A T L O N G > R6

Figure 33 Waypoint ETA Data Entry/Display Page(s)

If required, the operator can add time constraints to the waypoints using the LEGS RTA page. Initially the page is displayed with the default time constraint of HHMM.T for all waypoints (as shown in Fig 32). Entry of time constraints comprises entering the required time into the scratchpad area and pressing the relevant right programmable key.

Three types of time constraint are available for entry; AT the time specified, AFTER the time specified or BEFORE the time specified. As before, these constraints are defied by using a ‘blank’, ‘A’ or ‘B’ before the data. Thus A1234 signifies AFTER 12:34:00 and B09 signifies BEFORE 09:00:00.

Note: The current software does not perform error checking on the data.



4.2.7 Progress Reports (PROG)

Once the ROUTE and LEGS data has been input into the system and the aircraft is under way, the progress of the flight can be monitored using the 5 progress report pages. The current default page, initially page 1, is accessed using the PROG function key on the MCDU. Selection of subsequent/previous pages is achieved using the NEXT/PREV MCDU keys.

4.2.7.1 Progress Report 1

P R O G R E S S 1 / 5 0 7 9 D T G E T A

L1 E D V N 3 5 . 0 N M 1 7 5 6 R1

0 7 9 L2 E T H B 7 5 . 9 N M 1 8 3 0 R2

W I N D T K / G S L3 1 4 3 T / 0 0 5 K T 2 0 7 T / 3 4 8 K T R3

L4 R4

L5 R5

L6 R6

Figure 34 Trajectory Progress Page 1

Progress page 1 displays the current distance and ETA data fro the next 2 waypoints on the route, the wind speed and direction and the aircraft track and groundspeed. All data is refreshed at a 1Hz rate.

Data Item Description

DTG Distance To Go to the next 2 waypoints

ETA Estimated Time of Arrival at the next 2 waypoints

WIND Current values of wind speed and direction

TK/GS Current values of aircraft Track and Groundspeed

Table 7. Progress Page 1 Data Items




P R O G R E S S 2 / 5 F R O M

L1 D I R E C T R1

T O D T G L2 D 1 1 6 L 1 1 . 8 7 N M R2

N E X T L3 D 2 6 2 B 7 2 . 8 7 N M R3

D E S T L4 E G L L 2 1 9 N M R4

L5 R5

L6 R6


Progress page 2 gives the Distance To Go (DTG) between the current position and each of the next two waypoints in the trajectory and the destination. Table 8 describes each of the displayed parameters.


FROM Indicates that the leg is DIRECT from the current position to the active waypoint

TO Next (active) waypoint

DTG Column heading for the distances to the active and subsequent waypoints and the destination airport

NEXT Identifier and Distance To Go of waypoint following the active waypoint

DEST Identifier and Distance To Go of destination airport





P R O G R E S S 3 / 5 W P T

L1 G E R1

R T A L2 1 1 1 4 . 9 Z R2

C A S L3 4 8 0 K T R3

A L T L4 1 5 0 0 0 F T R4

L5 R5

L6 R6


Progress page 3 shows the trajectory data associated with the active waypoint. Table 9 describes each of the displayed parameters.


WPT Identifier of the waypoint that the data refers to

RTA Required Time of Arrival at the displayed waypoint as entered using the LEGS RTA page

CAS Calibrated Airspeed required at the identified waypoint

ALT Altitude required at the identified waypoint





P R O G R E S S 4 / 5 H E A D W I N D C R O S S W I N D

L1 - 1 K T 1 3 K T R1

H D G / D R I F T T A S L2 3 5 ° / R 0 0 0 ° 3 4 5 K T R2

M A G V A R L3 W 0 0 3 . 2 ° R3

L4 R4

G P S A L T L5 0 F T R5

L6 R6


Progress page 4 shows current aircraft data as defined in Table 10.


HEADWIND Current value of Headwind

CROSSWIND Current value of Crosswind

HDG/DRIFT Current value of Heading (0 – 360) and Drift (L180 to R180)

TAS True Air Speed

MAGVAR Current Magnetic Variation

GPS ALT Altitude received from the active GPS (GBAS, SBAS or VDL4 Transponder)





P R O G R E S S 5 / 5

L1 S E L N A V S O U R C E G B A S R1

A C T N A V S O U R C E G B A S L2 R2

L3 R3

A T K E / X T K E L4 B 0 M / L 1 4 2 M R4

R N P / A N P L5 2 . 0 N M / 0 . 0 0 N M R5

L6 N A V M O D E > R6


Progress page 5 identifies the source of the navigation data and the flight ‘accuracy’ data as defined in Table 11.


SEL NAV SOURCE Selected navigation source

ACT NAV SOURCE Actual navigation source being used

ATKE/XTKE Along/Cross Track Error values

RNP/ANP Required/Actual Navigation Performance values


For the Along Track Error (ATKE) the figure will be prepended with A (After) or B (Before). Similarly, the Cross Track Error (XTKE) will be prepended by L (Left) or R (Right).

Note: In the ATTAS installation, SEL NAV SOURCE should be VDL4. This will set the ACT NAV SOURCE to ATTAS.

4.2.8 Air Traffic Control Uplink Functions (ATC)

A T C U P L I N K 1 / 1

L1 L O A D > R1

L2 R2

L3 T E X T O F A T C U P L I N K R3

M E S S A G E I S D I S P L A Y E D L4 H E R E R4

L5 < E R A S E S T A N D B Y > R5

L6 D O W N L I N K > R6

Figure 39 Single ATC Message Page (ATC)

A T C U P L I N K 1 / *

L1 ◄ U N A B L E L O A D T O R T E ► R1

L2 ◄ S T A N D B Y W I L C O ► R2

- - - - - - - - - - - - - - - - - - - - - - L3 T E X T O F A T C U P L I N K R3

M E S S A G E 1 I S D I S P L A Y E D L4 H E R E R4

L5 R5

L6 ◄ L O G D O W N L I N K ► R6

Figure 40 Multiple ATC Messages Page 1 (ATC)



4.2.8.1 Variants on ATC Uplink Message Pages

4.2.8.1.1 Long Message

A T C U P L I N K 1 / *


L2 ◄ S T A N D B Y R2


M E S S A G E I S D I S P L A Y E D L4 H E R E . W H E N T H E R E I S A R4

M E S S A G E L O N G E R T H A N A L5 P A G E T H E D I S P L A Y L O O K S R5

L I K E T H I S L6 M O R E ► R6

Figure 41 Long ATC Message – First/Middle Page(s)

A T C U P L I N K * / *



- - - - - - - - - - - - - - - - - - - - - - L3 U N T I L I T F I N I S H E S R3

- - E N D O F M E S S A G E - - L4 R4

L5 R E T U R N ► R5


Figure 42 Long ATC Message - Last Page



4.2.8.1.2 Received Tactical Message

A T C U P L I N K 1 / 1

L1 ◄ U N A B L E A C T I V A T E ► R1




L5 C P D L C C O N N ► R5


Figure 43 Received Tactical Message



4.2.8.1.3 Received Resume Message

A T C U P L I N K 1 / 1

L1 ◄ U N A B L E R E S U M E ► R1


- - - - - - - - - - - - - - - - - - - - - - L3 R E S U M E O W N N A V I G A T I O N R3

L4 R4



Figure 44 Received Resume Message



4.2.8.1.4 Received Response Message

A T C U P L I N K 1 / 1

L1 ◄ U N A B L E A U T O R E P O R T ► R1

L2 ◄ S T A N D B Y R2





Figure 45 Received Response Message



4.2.8.1.5 Received WILCO Message

A T C U P L I N K 1 / 1

L1 L O A D T O R T E ► R1

L2 C L E A R ► R2



L5 W I L C O R5

L6 R6

Figure 46 Received WILCO Message



4.2.8.1.6 Received UNABLE Message

A T C U P L I N K 1 / 1

L1 L O A D T O R T E ► R1

L2 C L E A R ► R2



L5 U N A B L E R5

L6 R6

Figure 47 Received UNABLE Message



4.2.8.1.7 Received Formatted Reply Message

A T C U P L I N K 1 / 1

L1 ◄ U N A B L E S H O W R E P L Y ► R1

L2 R2


M E S S A G E L4 R4

L5 R5


Figure 48 Received Formatted Reply Message Page 1

A T C U P L I N K R E P L Y 1 / 1

L1 A U T O R E P L Y M E S S A G E R1

T E X T L2 R2

V A R I A B L E 1 L3 R3

V A R I A B L E 2 L4 S E N D ► R4

L5 ◄ U N A B L E R E T U R N ► R5


Figure 49 Received Formatted Reply Message Page

A T C U P L I N K 1 / 1

L1 R1

T E X T O F A T C U P L I N K



L2 M E S S A G E R2

L3 R3

T E X T O F A T C F O R M A T T E D L4 R E P L Y R4

L5 R5

L6 C L E A R ► R6

Figure 50 Received Formatted Reply Message Summary Page

4.2.9 Air Traffic Control Downlink Functions (ATC)

A T C D O W N L I N K

L1 < A I R / A T C T A X I / T W R > R1

L2 R2

L3 R3

L4 R4

L5 C P D L C C O N N > R5

L6 < L O G U P L I N K > R6

Figure 51 ATC Downlink Menu Page

This page provides menu selections for the ATC Downlink functionality of the MA-AFAS. Each of the options is described in the following sub-sections.

4.2.9.1 Aircraft to ATC Downlink Functions (AIR/ATC)

D O W N L I N K A I R A T C

L1 < F F A S E N T R Y R O U T E C L R > R1

L2 < F F A S E X I T T Y P E C L R > R2

L3 P R O C E D U R E > R3

L4 R4

L5 R5

L6 < L O G U P L I N K > R6



4.2.9.2 Route Clear (ROUTE CLR)

D O W N L I N K R O U T E C L R

L1 R1

V A L U E L2 R2

L3 R3

L4 R4

L5 R5

L6 R6

Figure 53 ATC Downlink Route Clear Page



4.2.9.2.1 Procedures (PROCEDURE)

T I T L E

L1 N O N E T A X I R1

L2 A P P R O A C H T A K E O F F R2

L3 D E P A R T U R E L A N D I N G R3

L4 F U R T H E R O C E A N I C R4

L5 S T A R T - U P E N R O U T E R5

L6 P U S H B A C K D O W N S T R E A M R6




4.2.9.3 ATC Downlink Message Log

M E S S A G E L O G 1 / * S O U R C E : S O U R C E I D

L1 M E S S A G E T E X T H E R E R1

L2 R2

L3 - - - - - - - - - - - - - - - - - - - - - - - - R3

T A R G E T : T A R G E T I D L4 M E S S A G E T E X T H E R E R4

L5 R5

L6 ◄ U P L I N K D O W N L I N K ► R6

Figure 55 ATC Downlink Message Log Pages



4.2.9.4 ATC Downlink Text Entry

A T C T E X T E N T R Y 1 / *

L1 R1

L2 R2

L3 R3

L4 R4

L5 R5

L6 ◄ R E T U R N S E N D ► R6

Figure 56 ATC Downlink Text Entry Page

4.2.9.5 ATC CPDLC Connection Status

C P D L C C O N N E C T I O N S

L1 R1

C D A L2 - - - - - - - - R2

N D A L3 - - - - - - - - R3

D D A L4 - - - - - - - - R4

L5 R5

L6 R6

Figure 57 ATC CPDLC Connection Status Page

4.2.10 ASAS Functions (ASAS)

A S A S A U T O - O P S < O F F >

L1 R1

T A R G E T I D L2 - - - - - - - - R2

L3 R3

L4 R4

L5 R5

L6 R6

Figure 58 Initial ASAS Menu Page

The initial MCDU menu presented to the operator for ASAS functions is as shown in Fig 58. This shows the current Autonomous Operations engagement state (as set using the Softkeys on the NDU; see section 4.3.1.1) and allows the input of the target aircraft using the normal scratchpad data entry routine. Once a Target Id has been entered, the MCDU display changes to that of Fig 59.

A S A S A U T O - O P S < O F F >

L1 R1 T A R G E T I D

L2 B A E 1 2 3 4 5 R E M A I N > R2

L3 M E R G E > R3

L4 C H A N G E > R4

L5 < E R A S E C R O S S > R5

L6 < R E S U M E P A S S > R6

Figure 59 ASAS Menu Page

The ASAS Menu is the initial point for the operator to set up one of the ASAS manoeuvres supported by the MA-AFAS trials equipment. Five possible manoeuvre types are available; Remain, Merge, Cross, Pass and Resume, and each one has a selection Programmable Key as shown in Fig 59. Programmable key L5 provides an Erase function that removes any manoeuvre that has been set up.

4.2.10.1 ASAS Manoeuvre – Remain

A S A S R E M A I N I N I T I A L H D G

L1 - - - R1

L2 B E A T L E A S T R2

L3 1 2 . 8 N M R3

B E H I N D L4 B A E 1 2 3 4 5 R4

E N D A T L5 - - - - R5

L6 < A S A S L O A D > R6

Figure 60 ASAS Remain Manoeuvre Page

On selection of the Remain option on the ASAS Menu page, the ASAS REMAIN page, depicted in Fig 59, is generated. This page allows the setting of various parameters that define the Remain Behind manoeuvre, currently, the only Remain manoeuvre supported by the MA-AFAS trials equipment. Table 12 identifies the parameters required.

Key Id Description

(L1) Optional operator input of the initial heading at the start of the manoeuvre. Value is in degrees in the range 0-359. Other values produce a message !INVALID ENTRY

(R2) Toggle between ‘AT LEAST’ and ‘< >’ (exactly) for the separation value entered in row 3

(R3) Operator input of required separation between ownship and target aircraft. Value must be greater than 5.0nm or message SEPARATION TOO SMALL is generated. Maximum distance is 42.5nm. Time is entered in seconds from 43

(R4) Operator input of target aircraft Identifier. Target must be in database or message is generated. Deletion of the Target Id will cancel the manoeuvre

(R5) Optional operator entry of waypoint Id that marks the end of the manoeuvre. Must be in the current trajectory or !WPT NOT IN TRAJECTORY message will be generated

ASAS Return to the ASAS Menu Page

LOAD Initiate change (only displayed when all parameters are valid)

Table 12. ASAS Remain Manoeuvre Parameters

4.2.10.2 ASAS Manoeuvre – Change

A S A S S P A C I N G

L1 R1

C H A N G E S P A C I N G T O B E L2 A T L E A S T 8 . 0 N M R2

B E H I N D L3 B A E 1 2 3 4 5 R3

C H A N G E S P E E D T O L4 2 3 4 R4

E N D A T L5 - - - - - R5


Figure 61 ASAS Change Spacing Page

On selection of the Change option on the ASAS Menu page, the ASAS SPACING page, depicted in Fig 60, is generated. This page allows the operator to change the spacing for a manoeuvre. Table 13 identifies the parameters required.

Key Id Description

(L2) Toggle between ‘AT LEAST’ and ‘< >’ (exactly) for the separation value entered in R2



(R4) Operator input of required speed, in Kts. Permissible range 0 to 600



LOAD Initiate change (only displayed when all parameters are valid)

Table 13. ASAS Merge Manoeuvre Parameters

4.2.10.3 ASAS Manoeuvre – Merge

A S A S M E R G E I N I T I A L H D G

L1 R1

A T W P T L2 - - - - - B E A T L E A S T R2

L3 1 2 0 S R3

B E H I N D L4 B A E 1 2 3 4 5 R4

E N D A T L5 - - - - - R5


Figure 62 ASAS Merge Manoeuvre Page

On selection of the Merge option on the ASAS Menu page, the ASAS MERGE page, depicted in Fig 60, is generated. This page allows the setting of various parameters that define the Merge Behind manoeuvre, currently the only Merge manoeuvre supported by the MA-AFAS trials equipment. Table 14identifies the parameters required.

Key Id Description

(L1) Optional operator input of the initial heading at the start of the manoeuvre. Value is in degrees in the range 0-359. Other values produce a message !INVALID ENTRY

(L2) Allows the operator to input the waypoint at which the manoeuvre should start. Must be in the current trajectory or !WPT NOT IN TRAJECTORY message will be generated

(R2) Toggle between ‘AT LEAST’ and ‘< >’ (exactly) for the separation entered at R3





LOAD Initiate manoeuvre (only displayed when all parameters are valid)

Table 14. ASAS Merge Manoeuvre Parameters



4.2.10.4 ASAS Manoeuvre – Cross

A S A S C R O S S I N I T I A L H D G

L1 R1

U N T I L C L E A R O F L2 B A E 1 2 3 4 5 R2

T H E N L3 R E S U M E T O - - - - R3

L4 R4

L5 R5


Figure 63 ASAS Crossing Manoeuvre Page

On selection of the Cross option on the ASAS Menu page, the ASAS CROSS page, depicted in Fig 61, is generated. This page allows the setting of various parameters that define the Cross Behind manoeuvre, currently the only Cross manoeuvre supported by the MA-AFAS trials equipment. Table 15 identifies the parameters required.

Key Id Description

(L1) Optional operator to input of the initial heading at the start of the manoeuvre. Value is in degrees in the range 0-359. Other values produce a message !INVALID ENTRY. For Crossing manoeuvres, this can be input as a heading change value (e.g. L30 or R30)

(L2) Operator input of target aircraft Identifier. Target must be in database or message is generated. Deletion of the Target Id will cancel the manoeuvre

(R3) Operator input of the waypoint where the ownship should resume its original route. Waypoint must be in the current trajectory or !WPT NOT IN TRAJECTORY message will be generated



Table 15. ASAS Crossing Manoeuvre Parameters



4.2.10.5 ASAS Manoeuvre – Pass

A S A S P A S S P A S S B E H I N D

L1 B A E 1 2 3 4 5 R1

S P A C I N G L2 1 2 . 8 N M R2

R E S U M E T O L3 - - - - R3

L4 R4

L5 R5


Figure 64 ASAS Passing Manoeuvre Page

On selection of the Pass option on the ASAS Menu page, the ASAS PASS page, depicted in Fig 63, is generated. This page allows the setting of various parameters that define the Pass Behind manoeuvre, currently the only Passing manoeuvre supported by the MA-AFAS trials equipment. Table 16 identifies the parameters required.

Key Id Description

(L1) Operator input of target aircraft Identifier. Target must be in database or message is generated. Deletion of the Target Id will cancel the manoeuvre

(L2) Operator input of required separation between ownship and target aircraft. Value must be greater than 5.0nm or message SEPARATION TOO SMALL is generated. Maximum distance is 42.5nm. Time is entered in seconds from 43

(R3) Operator input of the waypoint where the ownship should resume its original route. Waypoint must be in the current trajectory or !WPT NOT IN TRAJECTORY message will be generated



Table 16. ASAS Passing Manoeuvre Parameters



4.2.10.6 ASAS Manoeuvre – Resume

A S A S R E S U M E

L1 R E S U M E T O R1

- - - - L2 R2

L3 R3

L4 R4

L5 R5


Figure 65 ASAS Resume Parameter Page

On selection of the Resume option on the ASAS Menu page, the ASAS RESUME page, depicted in Fig 64, is generated. This page allows the setting of the Waypoint where the ownship will resume its original route following a Tactical Command. The waypoint specified must be in the current trajectory or !WPT NOT IN TRAJECTORY message will be generated. When a valid waypoint has been entered, the LOAD button will be displayed



4.2.11 Vertical Navigation (VNAV)

4 D N A V I G A T I O N C R S A L T

L1 0 F T R1

E O B T L2 - - - - . - z P H A S E T A B L E > R2

C T O T L3 - - - - . - z C O N S T R A I N T S > R3

L4 R4

D I R E C T T O L5 R5

L6 L O A D > R6

Figure 66 Vertical Navigation Menu Page

This page controls the generation of a trajectory from the initial ROUTE and LEGS data and allows the setting of the default cruise altitude. Details of the current phase table and the constraints can be reviewed by following the PHASE TABLE and CONSTRAINTS links.

Three parameters can be entered or modified using the scratchpad data entry routine. These are:

CRS ALT This programmable key enters the default cruise altitude into the system

EOBT Estimated Off Block Time

CTOT Calculated Take-Off Time

The latter items can be pre-loaded using the AOC LOADSHEET function.

Messages will be generated if the cruise altitude is over 44999Ft or less than 4501Ft (!INVALID ENTRY) or if the CTOT is earlier than the EOBT or current time (!INVALID ENTRY). The entry of time can be hhmm or hhmm.t format.

Once the ROUTE and LEGS data has been entered, the LOAD function is activated. Operation of this key (R5 programmable key) causes the Trajectory Generator to create a new trajectory. A message is generated on success (NEW TRAJ CREATED) or failure (!INVALID CONSTRAINT) of the process.

The message !DISCONTINUITY EXISTS will be displayed if the entry of the LEGS has not been completed when the LOAD is attempted.

If a trajectory has been generated, the EXEC (Execute) lamp on the MCDU will be lit.

When the aircraft systems indicate to the MA-AFAS that the aircraft is off the ground, the user can execute the trajectory by operating the EXEC Function button on the MCDU.

Trajectory re-generation is accomplished using the same procedure. If regeneration is attempted on the ground then new values for EOBT and CTOT will be required if the displayed time has passed.

In the air, the current position is used as the first constraint point and the current destination, displayed as DIRECT TO on the MCDU, is used for the second waypoint. All other waypoints in the LEGS list will remain unchanged and a new trajectory computed from the present position using these.



4.2.11.1 Phase Table

M O D P H A S E T A B L E T O C A S

L1 1 2 3 K T R1

R C C A S E C C A S L2 1 2 3 K T 1 2 3 K T R2

C R C A S L3 1 2 3 K T R3

R D C A S E D C S L4 1 2 3 K T 1 2 3 K T R4

A P C A S L5 1 2 3 K T R5

L6 L O A D > R6

Figure 67 Phase Table Edit/Display Page

This page allows the review and editing of the system phase table values. Initial values are entered via the phase table and planning values text files stored in the database on the hard drive. These predefined values can be edited for the current flight using the normal scratchpad data entry routine. When one of the values has been modified, the magenta MOD flag is displayed in the top left corner of the screen, and a LOAD function is enabled on programmable key R6. Following modification, the data must be loaded into the system before a trajectory is generated or the new values will not be used.

Table 17 lists the values that can be edited: Note that no reasonableness checks are made on data entered into the phase table.

Key Parameter

L1 Take Off Speed (TO)

L2 Regular Climb Airspeed (RC)

L3 Restricted Climb(CR)

L4 Restricted Descent (RD)

L5 Approach Speed (AP)

R2 Climb (EC)

R4 Descent (ED)

Table 17. Phase Table Parameters



4.2.11.2 Constraints

C O N S T R A I N T S 1 / * W P T

L1 R W 0 5 R1

R T A T R A J E T A L2 H H M M . T 0 0 0 0 . 0 R2

C A S T R A J C A S L3 4 8 0 K T 4 8 0 K T R3

A L T T R A J A L T L4 1 5 0 0 0 F T 1 5 0 0 0 F T R4

L5 R5

L6 R6

Figure 68 Trajectory Constraints Page

Following the creation of a trajectory, the constraint points generated by the trajectory generator can be reviewed using the Trajectory Constraints Page. Selecting CONSTRAINTS on the 4D NAVIGATION page (VNAV) produces the display, shown in Fig 68, for the first constraint point – normally the ORIGIN runway.

The field contents for the CONSTRAINTS page are described in Table 18.

Data Field Data Description

WPT Identifier of the waypoint/TCP

RTA Required Time of Arrival at the waypoint as entered in the LEGS page(s). This data is blank for TCPs.

CAS Required CAS at the waypoint. This data is blank for TCPs.

ALT Required altitude at the waypoint as entered in the LEGS page(s). This data is blank for TCPs.

TRAJ ETA Estimated Time of Arrival at the constraint point (zulu time). Time at the first constraint will be CTOT entered on the VNAV page.

TRAJ CAS Estimated speed at the constraint point

TRAJ ALT Estimated altitude at the constraint point

Table 18. CONSTRAINTS Page Data Items

If the constraints page is invoked duriong flight, page 1 displayes the data for the next constraint.



4.2.12 Holding Pattern (HOLD)

This function is not available in this version.

4.2.13 Fix Data Entry (FIX)

This function is not available in this version.



4.2.14 Aircraft Operations Centre Communications (AOC)

A O C M E N U

L1 ◄ F L I G H T P L A N M E T E O ► R1

L2 ◄ L O A D S H E E T C O M P M S G ► R2

L3 ◄ D E P S L O T R3

L4 ◄ M A L F U N C T I O N R4

L5 ◄ I F T M R E Q M E T E O ► R5

L6 ◄ F R E E T E X T D I S A B L E ► R6

Figure 69 AOC Menu Page (AOC)

The initial Aircraft Operations Centre (AOC) page provides the operator with a menu of the available MA-AFAS functionality. The options presented on this page will only be displayed if connection has been made to the ground station.

Menu Item Function Description

FLIGHT PLAN Display a received Flight Plan

LOADSHEET Display a received Loadsheet

DEP SLOT Display received Departure Slot Information

MALFUNCTION Display the operator interface for composing a snag report

IFTM

FREE TEXT Display a menu of the received free text messages

METEO Display a menu of the received meteorological messages

COMP MSG

REQ METEO Provides an operator interface to request a met report

DISABLE Disables the reception of AOC messages

Table 19. AOC Menu Functionality (AOC)



4.2.14.1 Flight Plan Display (FLIGHT PLAN)

F L I G H T P L A N 1 / * 1 - - - - - - - 2 - - - T O 3 - - -

L1 E O B T - - : - - Z A L T N - - - - R1

A L T N 2 - - - - 6 - - 7 - - - - - L2 8 - - - - - - - - - - - - - - - - - - - - R2

P A X - - - L3 1 0 - - - - - - - - - - - - - - - - - - - - - - R3

- - - - - - L4 R O U T E - - - - - - - - - - R4

E E T - - : - - N - - - - A - - - L5 R5

1 5 - - - 1 6 - - - - - - - - - A - - - L6 ◄ A O C P R I N T ► R6

Figure 70 Flight Plan Page 1 (FLIGHT PLAN)

F L I G H T P L A N 2 / * R T A - - : - - Z T B R N - - - - -

L1 T U R N T Y P E - - - - - - R1

A I R S P A C E T Y P E - - - - - - - - - - L2 R2

. L3 R3

1 5 - - - 1 6 - - - - - - - - - A 1 7 - L4 R T A - - : - - Z T B R N - - - - - R4

T U R N T Y P E - - - - - - L5 A I R S P A C E T Y P E - - - - - - - - - R5

L6 ◄ A O C P R I N T ► R6

Figure 71 Flight Plan Page 2

The Flight Plan MCDU Pages provide a display of the data received from AOC in a Flight Plan transmission. Currently, the message ‘AOC MESSAGE RECEIVED!’ is used to identify this event. Note that for MA-AFAS, this data is the same as used for the company route definition and is described in section A3.5.

At least two pages, shown as Figs 70 and 71, are needed to display all the received data; the number of pages depends upon the number of waypoints that are included in the message. Each received data item is described in Table 20. Note that the white numbers in the figures are for identification of the data fields only and do not appear on the actual display.



Field Field Description

1 1 to 8 characters showing the Flight Id

2 ICAO code of the departure airport

3 ICAO code of the arrival airport


ALTN ICAO code of the 1st alternate airport

ALTN2 ICAO code of the 2nd alternate airport

6 3 character code indicating flight rules and type of flight. First character is a hyphen, second character denotes the flight rules and the last character indicates the type of flight.

7 4 to 6 characters indicating the type of aircraft and its wake turbulence category in the format AAAA/W. AAAA indicates the type of aircraft, e.g. B747. ‘W’ indicates the wake turbulence category, e.g. 0; large wake turbulence.

8 1 to 21 characters indicating the aircraft equipment. First character should be an hyphen

PAX 1 to 3 characters defining the number of passengers

10 Free text string corresponding to other provided information

Route 5 to 10 characters indicating the company route code

EET Total estimated enroute time in the format HH:MM

N 4 characters indicating the cruising speed in Knots

A 3 characters indicating the cruising level in hundreds of feet

The following data items are repeated for each waypoint included in the Flight Plan

15 1 to 5 characters indicating the waypoint name

16 Latitude and longitude of waypoint in the format L1L1L1L1NL2L2L2L2L2W

A 3 characters indicating the required flight level at waypoint (in hundreds of feet)

RTA Required time of arrival at waypoint in the format HH:MM

TBRN 5 characters indicating the expected amount of fuel used at waypoint (in Kg)

Turn Type 2 to 6 characters indicating the turn type at waypoint

Airspace Type

3 to 10 characters indicating the airspace type at waypoint

Table 20. Description of Parameters on Flight Plan Pages



4.2.14.2 Loadsheet Display (LOADSHEET)

L O A D S H E E T 1 / 2 1 - - - - - - - 2 - - - T O 3 - - -

L1 E O B T - - : - - Z C T O T - - : - - Z R1

A C R E G - - - - - - - - 5 - - - - - - - - L2 - - - - - - - - - - - - R2

Z F W - - - - - - T O W - - - - - - L3 P A X - - - F U E L - - - - - R3

D O I - - - - D L I - - - - L4 D L M - - - - L I Z F W - - - - R4

L I T O W - - - - L I L A W - - - - L5 M A C Z F W - - - - M A C T O W - - - - R5

M A C L A W - - - - S T A B T O - - - - L6 ◄ A O C A C K ► R6

Figure 72 Loadsheet Page 1 (LOADSHEET)

L O A D S H E E T 2 / 2 6 - - - - - - - - - 7 - -

L1 6 - - - - - - - - - 7 - - R1

6 - - - - - - - - - 7 - - L2 6 - - - - - - - - - 7 - - R2

6 - - - - - - - - - 7 - - L3 6 - - - - - - - - - 7 - - R3

6 - - - - - - - - - 7 - - L4 6 - - - - - - - - - 7 - - R4

L5 R5

L6 ◄ A O C A C K ► R6

Figure 73 Loadsheet Page 2

The Loadsheet MCDU Pages provide a display of the data received from AOC in a Loadsheet transmission. Two pages, shown as Figs 72 and 73, are needed to display all the received data. Each received data item is described in Table 21. Note that the white numbers in the figures are for identification of the data fields only and do not appear on the actual display.



Item Identifier

Item Description

1 1 to 8 characters showing the Flight Id




CTOT Calculated Take Off Time

ACREG 1 to 8 characters indicating the aircraft tail number.

5 Free text string corresponding to regulations affecting the flight

ZFW Zero Fuel Weight

TOW Take Off Weight

PAX Number of Passengers

FUEL Weight of Fuel

DOI * Dry Operating Index

DLI * Deadload Index

DLM * Deadload MAC

LIZFW * Loaded Index at Zero Fuel Weight

LITOW * Loaded Index at Take Off Weight

LILAW * Loaded Index at Landing Weight

MACZFW * Mean Aerodynamic Chord Zero Fuel Weight

MACTOW * Mean Aerodynamic Chord Take Off Weight

MACLAW * Mean Aerodynamic Chord Landing Weight

STABTO * Stabiliser Trim at Take-Off

6 1 to 10 characters indicating the compartment name. Up to 8 compartment names can be received

7 1 to 3 characters indicating the number of persons in the compartment * Indicates not used for MA-AFAS trials

Table 21. Loadsheet Parameters Description (LOADSHEET)



4.2.14.3 Departure Slot Display (DEP SLOT)

D E P S L O T E O B T - - - - z

L1 C T O T - - - - z R1

L2 O T H E R I N F O R M A T I O N T E X T R2

S T R I N G L3 R3

L4 R4

L5 R5

L6 ◄ A O C R6

Figure 74 Departure Slot Page (DEP SLOT)

This page displays the information received from AOC in the Departure Slot datalink transmission. Two data items are transmitted; the Estimated Off Block Time and the Computed Take Off Time. An optional free text message can also be displayed.



4.2.14.4 Snag Report Display (MALFUNCTION)

M A L F U N C T I O N

L1 T H E S N A G R E P O R T R1

L2 C A N B E C O M P O S E D H E R E R2

L3 R3

L4 E R R O R C O D E : - - R4

L5 ◄ B C K C L R ► R5

L6 ◄ F W D S E N D ► R6

Figure 75 Snag Report Generation Page (MALFUNCTION)

This page provides the operator with a means to compose a Snag report for transmission to AOC. A Free Text message can be compiled as detailed in 4.1.1.1, and an associated 2 digit Error Code entered using the L4 programmable key.

The entire message may be cleared using the CLR function on programmable key R6.



4.2.14.5 In Flight Traffic Management Display (IFTM)

I F T M M E N U 1 / * I F T M I D E N T I F I E R - - -

L1 1 - - - T O 2 - - - R1

V A L I D U N T I L - - : - - Z L2 A T C T R A J E C T O R Y I D - - - R2

O R . C O M P A N Y R O U T E I D L3 - - - - - - - - - - R3

O R . F L I G H T P L A N I D L4 - - - - - - - - - - - - - - - - - - - - R4

O R . I F T M I D - - - L5 A C C E P T ► R5

L6 ◄ A O C R E J E C T ► R6

Figure 76 IFTM Page 1 (IFTM)

I F T M M E N U 2 / * 3 - - - - 4 - - - - - - - - - - A 5 - -

L1 R T A - - : - - Z T B R N - - - - - R1

T U R N T Y P E - - - - - - L2 A I R S P A C E T Y P E - - - - - - - - - - R2

. L3 3 - - - - 4 - - - - - - - - - - A 5 - - R3

R T A - - : - - Z T B R N - - - - - L4 T U R N T Y P E - - - - - - R4

A I R S P A C E T Y P E - - - - - - - - - - L5 A C C E P T ► R5

L6 ◄ A O C R E J E C T ► R6

Figure 77 IFTM Page2

Received IFTM data is decoded and displayed to the operator in the format depicted in Figs 76 and 77. The data fields are described in Table 22. The data in Page 2 is repeated for each waypoint in the revised flight plan.

Acceptance of the revised data is signified by the use of the R5 programmable key that enters the data into the system and replaces any flight plan already entered.

The REJECT function (programmable Key R6) clears the data from the system.



Item Description

IFTM Identifier 3 chars indicating IFTM identifier (1..256 numeric value)



Valid Until Validity time in the format HH:MM

ATC Trajectory Id

3 chars indicating ATC trajectory identifier (1..256 numeric value) (optional value)

Company Route Id

5 to 10 characters indicating originating company route (optional value)

Flight Plan Id 1 to 20 characters indicating originating flight plan (optional value)

IFTM Id 3 chars indicating originating IFTM identifier (1..256 numeric value) (optional value)

3 1 to 5 characters indicating the waypoint name

4 Latitude and longitude of waypoint in the format L1L1L1L1NL2L2L2L2L2W

A5 3 characters indicating the required altitude level at waypoint in hundreds of feet

RTA Required time of arrival at waypoint in the format HH:MM

TBRN 5 characters indicating the total amount of fuel used at waypoint in Kg

Turn Type 2 to 6 characters indicating the turn type at waypoint

Airspace Type 3 to 10 characters indicating the airspace type at waypoint

Table 22. IFTM Page Parameter Description

This function is not implemented for the MA-AFAS trials.



4.2.14.6 Received Free Text Menu Page(s) (FREE TEXT)

F R E E T E X T 1 / *

L1 ◄ F R E E T E X T M E S I D | H H : M M R1





L6 ◄ A O C O L D T X T ► R6

Figure 78 Received Free Text Messages Menu (FREE TEXT)

This menu page lists the Message Ids and time of receipt of the free text messages received from AOC that have not yet been viewed. Up to five messages can be listed on any page. Messages are listed in time of receipt order. Clicking on programmable key L1 to L5 will display the relevant message using the received message details page.



4.2.14.6.1 Received Free Text Display Page

F R E E T E X T D E T A I L S

L1 D E T A I L S O F F R E E T E X T R1

M E S S A G E A R E D I S P L A Y E D L2 H E R E R2

L3 R3

L4 R4

L5 ◄ C O M P O S E R5

L6 ◄ F R E E T E X T P A G E P R I N T ► R6

Figure 79 Received Free Text Message Details

This text display page allows the operator to view a selected message received from AOC. Messages can comprise up to 256 characters although for MA-AFAS this will be restricted to 240 to allow the use of a single page.

A link to the Free Text message compose page is included on this page to facilitate the generation and sending of a reply.

Note: the Print function is not demonstrated on the MA-AFAS programme.



4.2.14.6.1.1 Free Text Message Composition Page (COMPOSE)

C O M P O S E F R E E T E X T

L1 D E T A I L S O F F R E E T E X T R1

L2 M E S S A G E E N T E R E D A R E R2

L3 D I S P L A Y E D H E R E R3

L4 R4

L5 ◄ F W D C L R ► R5

L6 ◄ B A C K S E N D ► R6

Figure 80 Free Text Message Composition Page (COMPOSE)

This MCDU page allows the user to compose, and send, a free text message to the AOC. Message text is entered using the scratchpad entry routine with the FWD and BACK programmable key functions allowing editing of displayed text (see section 4.1.1.1.2 for details).

Once composed, the message can be transmitted to the AOC using the SEND (R6) programmable key.

Note that free text messages are limited to 256 characters but the COMPOSE page is limited to 192 for the MA-AFAS programme.



4.2.14.6.2 Old Received Free Text Menu Page(s) (OLD FREE TEXT)

O L D F R E E T E X T






L6 ◄ F R E E T E X T P A G E R6

Figure 81 Old Received Free Text Messages Menu (OLD FREE TEXT)

Free text messages that have been viewed are removed from the free text message menu and placed on the Old Free Text message menu shown above. The same format is followed for both menu pages.

A link is provided to the received free text messages menu on programmable key L6.



4.2.14.7 Meteorological Data Request Menu (METEO)

M E T E O 1 / x

L1 ◄ T A F | E G K K | 1 1 : 1 2 R1

L2 ◄ M E T A R | E G F F | 1 1 : 1 0 R2

L3 ◄ S I G M E T | E G K K | 1 1 : 0 4 R3

L4 ◄ M E T A R | E G K K | 1 1 : 0 2 R4

L5 ◄ T A F | L E I B | 1 0 : 1 0 R5

L6 ◄ A O C R6

Figure 82 Meteorological Data Request Menu Page(s) (METEO)

This menu page shows an index of all the received meteo data from the AOC. Each line of the display shows the data type (TAF, METAR or SIGMET), the airport to which the data refers and the time of reception of the data.

Selecting the appropriate Left Programmable Key (1 to 5) on the MCDU will result in the display of the received data.

In the event of more than five entries in the index, the NEXT and PREV keys can be used to navigate between the pages.



4.2.14.7.1 Received TAF Report Page (TAF)

T A F R E P O R T A I R P O R T I D - - - -

L1 I S S U E T I M E - - - - z R1

V A L I D I T Y - - 0 0 / - - 0 0 z L2 R2

T A F T E X T T A F T E X T L3 T A F T E X T T A F T E X T R3

L4 R4

L5 R5

L6 ◄ R E Q U E S T R6

Figure 83 Received TAF Report Page (TAF)

This page shows a received Terminal Area Forecast (TAF) as selected on the METEO page (Fig 82). The data displayed is for the airport identified in the first row, with time of issue and data validity shown on the next two lines. The TAF text (up to 256 characters) occupies the rest of the display area and is in the format received; no decode is provided.

The REQUEST function (programmable key L6) returns to the METEO page.



4.2.14.7.2 Received METAR Report Page (METAR)

M E T A R R E P O R T A I R P O R T I D - - - -

L1 I S S U E T I M E - - - - z R1

L2 M E T A R T E X T M E T A R T E X T R2

M E T A R T E X T M E T A R T E X T L3 R3

L4 R4

L5 R5


Figure 84 Received METAR Report Page (METAR)

This page shows a received Aviation Routine Weather Report (METAR) as selected on the METEO page (Fig 82). The data displayed is for the airport identified in the first row, with time of issue shown on the next line. The METAR text (up to 256 characters) occupies the rest of the display area and is in the format received; no decode is provided.




4.2.14.7.3 Received SIGMET Report Page (SIGMET)

S I G M E T R E P O R T I S S U E T I M E - - - - z

L1 V A L I D T O - - - - z R1

A R E A O F I N T E R E S T L2 F R O M - - - - N - - - - - E R2

T O - - - - S - - - - - W L3 R3

S I G M E T T E X T S I G M E T T E X T L4 R4

L5 R5


Figure 85 Received SIGMET Report Page (SIGMET)

This page shows a received Significant Meteorological advisory (SIGMET) as selected on the METEO page (Fig 82). The data displayed is for the airport identified in the first row, with validity data shown on the next 4 lines. The SIGMET text (up to 256 characters) occupies the rest of the display area and is in the format received; no decode is provided.




4.2.14.8 Message Composition Display (COMP MSG)

Not supported in this build.

4.2.14.9 Meteorological Data Request (REQ METEO)

R E Q M E T E O

L1 R1

A I R P O R T I D S E L E C T R E Q L2 - - - - < S E L > R E Q T A F R2

L3 R E Q M E T A R R3

L4 R E Q S I G M E T R4

L5 R5

L6 ◄ A O C S E N D ► R6

Figure 86 Request Meteorological Data Page (REQ METEO)

The REQ METEO page allows the operator to request meteorological data from AOC via the datalink. Three types of request are supported; Terminal Area Forecast (TAF), Aviation Routine Weather Report (METAR) and Significant Meteorological advisories (SIGMET).

The airport code is entered at line L1 and the type of data required requested using one of the Programmable Keys R2 to R4. This action causes the <SEL> flag to be entered against the chosen request as shown in Fig 86. Note: only one data type can be requested at a time; selecting a subsequent choice will cancel the previous one.

When the request has been compiled, the operator selects SEND> and the request is transmitted. Confirmation is given in the scratchpad by the message REPORT REQUEST SENT. An error message is displayed if no airport has been entered (!NO AIRPORT ENTERED), the input airport code is not recognised (!NOT IN DATABASE) or no report type has been selected (!NO REPORT SELECTED).

Once the request has been sent, the message in the scratchpad is cleared using the MCDU CLR key as usual. This also removes the airport entry at line L1.



4.2.14.10 AOC Disable (DISABLE)

A O C M E N U

L1 R1

L2 R2

L3 R3

L4 R4

L5 R5

L6 E N A B L E > R6

Figure 87 AOC Disabled Page (DISABLE)

This page is displayed whenever data reception from AOC is inhibited and the operator requests AOC data display or when the operator disables the reception of AOC data.

To enable data reception, the ENABLE (R6) programmable key should be selected.

4.2.15 Flight Information Services – Broadcast Communications (FIS-B)

F I S - B A R R A R P T

L1 < S I G M E T E G S S R1

U S R D E F I C A O L2 < A T I S - - - - R2

L3 < M E T A R R E Q > R3

L4 < R V R R E Q I N F O > R4

L5 O U T S T A N D I N G R E Q S > R5

L6 D I S A B L E > R6

Figure 88 FIS-B Menu Page (FIS-B)

This menu page allows access to the FIS-B messages and requests.

Received messages cn be viewed by use of the L1 to L4 programmable keys that display the index of messages received in each of the four supported message groups; SIGMET, ATIS, METAR and RVR. Programmable key R4, REQ INFO, lists messages received in all supported groups that are a result of a request being sent to AOC for specific data using the REQ (R3) function. When a request has been made and no response received, the OUTSTANDING REQS functions (R5) displays the index of the requests made.

The ARRIVALS airport field is automatically populated from the RTE information and is usually use in a request for information. Use of the USR DEF ICAO field (R2) allows the operator to request data for an airport that is not the destination (e.g. an alternate).

To disable the processing and display of received FIS-B messages, programmable key R6 is provided.

4.2.15.1 FIS-B SIGMET (SIGMET)

S I G M E T M E S S A G E 1 / x

L1 S I G M E T | L H H R | 0 0 : 2 0 R1

L2 S I G M E T | L H H R | 0 0 : 2 2 R2

L3 S I G M E T | L H H R | 0 0 : 2 3 R3

L4 S I G M E T | L H H R | 0 0 : 2 5 R4

L5 S I G M E T | L H H R | 0 0 : 2 1 R5

L6 < F I S - B R6

Figure 89 Received SIGMET Menu Page(s) SIGMET)

Received SIGMET messages are listed on this page in the order in which they were received. The displayed list identifies the type of message, the airport it is applicable to and the time of reception. Selecting the required data to view is achieved by use of the appropriate Programmable Key (L1 to L5). Further pages of data are identified by the number of pages count (shown as x in Fig 89) being set to more than 1. Navigation between the pages is available using the PREV and NEXT MCDU keys.

If no data has been received, the message ‘NO REPORTS AVAILABLE’ is displayed at the top (L1/R1) of the display



4.2.15.1.1 FIS-B SIGMET Data Display 1 (SIGMET1)

S I G M E T 1 / 1

L1 S I G M E T O R I G I N - - - - R1

S I G M E T I D - - - - L2 T I M E D A T E 2 2 . 2 2 Z O C T 1 9 / 0 1 R2

L3 C O N D I T I O N T H U N D E R S T O R M R3

V A L I D U N T I L 1 3 . 4 5 Z L4 R4

L5 ◄ P R I N T R5

L6 ◄ F I S - B T E X T R P T ► R6

Figure 90 Received SIGMET Message Page

Received SIGMET messages can be reviewed using the pages. The data received is detailed in Table 23.

Line Item Description

SIGMET Origin ICAO Number of transmitting Station

SIGMET Id Id number to identify each report

TimeDate Time and Date of SIGMET report

Condition Prevailing weather condition.

Valid Until Time of expiry of the data.

Table 23. SIGMET Information Description



4.2.15.1.2 FIS-B SIGMET Text Report Display (TEXT RPT)

S I G M E T T E X T R E P O R T 1 / x

L1 T E X T M E S S A G E D I S P L A Y E D R1

O N T H I S P A G E W H E N S E N T L2 R2

R E F . F I S - B S E R V I C E L3 D E S C R I P T I O N R3

3 . 7 . 3 L4 R4

L5 ◄ P R I N T R5

L6 ◄ F I S - B S I G M E T ► R6

Figure 91 Received SIGMET Free Text Message Page

SIGMET text messages received will be displayed using the MCDU format shown in Fig 91.

Not used in the MA-AFAS trials.

4.2.15.2 FIS-B ATIS (ATIS)

A T I S M E S S A G E 1 / x

L1 A T I S | L H H R | 0 0 : 2 1 R1

L2 A T I S | L H H R | 0 0 : 2 4 R2

L3 A T I S | L H H R | 0 0 : 2 7 R3

L4 A T I S | L H H R | 0 0 : 2 9 R4

L5 A T I S | L H H R | 0 0 : 2 0 R5

L6 < F I S - B R6

Figure 92 Received ATIS Message Menu (ATIS)

Received ATIS messages are listed on this page in the order in which they were received. The displayed list identifies the type of message, the airport it is applicable to and the time of reception. Selecting the required data to view is achieved by use of the appropriate Programmable Key (L1 to L5). Further pages of data are identified by the number of pages count (shown as x in Fig 92) being set to more than 1. Navigation between the pages is available using the PREV and NEXT MCDU keys.



4.2.15.2.1 FIS-B ATIS Data Display 1 (ATIS1)

A T I S 1 / 4 A T I S O R I G I N I C A O N U M B E R

L1 A T I S I D I D N U M B E R R1

T I M E D A T E 2 2 . 2 2 Z O C T 1 9 / 0 1 L2 A P P R O A C H T Y P E I L S C A T 1 R2

H O L D I N G D E L A Y 6 0 M I N L3 T R A N S L E V E L 3 0 0 F T R3

A I R P O R T A V A L 1 3 . 3 2 Z O P E N L4 R4

L5 ◄ P R I N T T R E N D R P T ► R5

L6 ◄ F I S - B T E X T R P T ► R6

Figure 93 ATIS Message Data Display Page 1

Data received in an ATIS message may be displayed on the MCDU as four pages of information. Page 1 is shown in Fig 93. Data items on this page are further defined in Table 24.


ATIS Origin ICAO Number of transmitting Station

ATIS Id Unique report identifier

TimeDate Time and Date of SIGMET report

Approach Type Current approach type

Holding Delay Estimated delay in holding pattern

Trans Level Altitude of transit point

Airport Avail Airport availability report

Table 24. ATIS Page 1 Information Description

Further ATIS data is available on subsequent pages by use of the PREV and NEXT MCDU keys.

ATIS Trend and Free Text Messages are available for viewing on the MCDU by selection of the TREND (R5) and TEXT (R6) programmable keys.

Note: The PRINT option is not available in this release of software.




A T I S 2 / 4

L1 W I N D D I R / S P D - - - ° / - - - K T S R1

V A R W I N D D I R / S P D L2 - - - ° / - - - K T S R2

W I N D G U S T I N D - - - K T S L3 C L O U D C O V E R A G E U N K N O W N R3

C L O U D H E I G H T - - - - - - F T L4 C L O U D T Y P E N O C L O U D S R4

V I S I B I L I T Y - - - - - M T S L5 R5

L6 ◄ F I S - B P R I N T ► R6

Figure 94 ATIS Message Data Display Page2



Wind Dir/Spd Airport wind direction (degrees) and speed (knots) data

Var Wind Dir/Spd

Variation in airport wind direction and speed

Wind Gust Ind Indicator of wind gusting conditions

Cloud Coverage Percentage cloud cover at the airport

Cloud Height Height (feet) of cloud base at airport

Cloud Type Description of clouds at airport.

Visibility Visibility (metres) at airport






A T I S 3 / 4

L1 P R E S E N T W T H R - - - - - - - R1

R E C E N T W T H R - - - - - - - L2 T E M P E R A T U R E - - - ° R2

D E W P O I N T - - - ° L3 Q N H - - - - H P A R3

R U N W A Y I D 1 5 R I G H T L4 R U N W A Y D E P S C L E A R - D R4

R U N W A Y C O N T 2 6 - 5 0 P L5 D P T H D E P O S I T 4 0 C M R5

B R A K I N G A C T I O N P O O R L6 ◄ F I S - B P R I N T ► R6




Present Wthr Current weather conditions at airport

Recent Wthr Recent weather conditions at airport

Temperature Current air temperature at airport

Dew Point Current dew point at airport

QNH Current local barometric pressure

Runway Id

Runway Deps

Runway Cont

Dpth Deposit

Braking Action






A T I S 4 / 4

L1 R E D R U N W A Y L T H 6 4 2 5 M T R S R1

R E D R U N W A Y W D T H 7 0 M T R S L2 R V R - T O U C H D O W N 1 4 7 5 M T R S R2

R V R - M I D P O I N T 1 0 0 0 M T R S L3 R V R - E N D P O I N T 2 0 0 M T R S R3

R U N W A Y U S E Y E S L4 R U N W A Y A V A L 1 3 . 3 2 Z O P E N R4

W I N D S H E A R Y E S L5 R5

L6 ◄ F I S - B P R I N T ► R6




Red Runway Lth Length (metres) of runway to be used

Re Runway Wdth Width (metres) of runway to be used

RVR-Touchdown

RVR-Midpoint

RVR-Endpoint

Runway Use

Runway Avail

Windshear





4.2.15.2.5 FIS-B ATIS Trend Report Display (TREND RPT)

A T I S T R E N D R E P O R T 1 / x

L1 T R E N D M E S S A G E D I S P L A Y E D R1


L3 R3

L4 R4

L5 ◄ P R I N T R5

L6 ◄ F I S - B A T I S ► R6

Figure 97 Received ATIS Trend Report Page (TREND RPT)



4.2.15.2.6 FIS-B ATIS Text Report Display (TEXT RPT)

A T I S T E X T R E P O R T 1 / x

L1 F R E E T E X T M E S S A G E R1

D I S P L A Y E D O N T H I S P A G E L2 W H E N S E N T R2

L3 R3

L4 T R4

L5 ◄ P R I N T R5

L6 ◄ F I S - B A T I S ► R6

Figure 98 Received ATIS Text Report Page (TEXT RPT)

4.2.15.3 FIS-B METAR (METAR)

M E T A R M E S S A G E 1 / x

L1 M E T A R | L H H R | 0 0 : 2 1 R1

L2 M E T A R | E G K K | 0 0 : 2 4 R2

L3 M E T A R | E G L L | 0 0 : 2 7 R3

L4 M E T A R | L E I B | 0 0 : 2 9 R4

L5 M E T A R | L I S B | 0 1 : 2 0 R5

L6 < F I S - B R6

Figure 99 Received METAR Messages Menu Page(s) (METAR)

Received METAR messages are listed on this page in the order in which they were received. The displayed list identifies the type of message, the airport it is applicable to and the time of reception. Selecting the required data to view is achieved by use of the appropriate Programmable Key (L1 to L5). Further pages of data are identified by the number of pages count (shown as x in Fig 99) being set to more than 1. Navigation between the pages is available using the PREV and NEXT MCDU keys.



4.2.15.3.1 FIS-B METAR Data Display 1 (METAR1)

M E T A R 1 / 3

L1 M E T A R O R I G I N I C A O N U M B E R R1

M E T A R I D I D N U M B E R L2 T I M E D A T E 2 2 . 2 2 Z O C T 1 9 / 0 1 R2

L3 R3

L4 R4

L5 ◄ P R I N T T R E N D R P T ► R5

L6 ◄ F I S - B T E X T R P T ► R6

Figure 100 Received METAR Message Page


METAR Origin ICAO Number of transmitting station

METAR Id

TimeDate Time and date of message transmission

Table 28. METAR Page 1 Information Description




M E T A R C L O U D 2 / 3

L1 W I N D D I R / S P D - - - ° / - - - K T S R1

V A R W I N D D I R / S P D L2 - - - ° / - - - K T S R2

W I N D G U S T I N D - - - K T S L3 C L O U D C O V E R A G E U N K N O W N R3

C L O U D H E I G H T - - - - - - F T L4 C L O U D T Y P E N O C L O U D S R4

V I S I B I L I T Y - - - - - M T S L5 R5

L6 ◄ F I S - B P R I N T ► R6

Figure 101 METAR Page 2 Information Description


Wind Dir/Spd Airport wind direction (degrees) and speed (knots) data

Var Wind Dir/Spd Variation in airport wind direction and speed

Wind Gust Ind

Cloud Coverage

Cloud Height Height (feet) of cloud base at airport

Cloud Type Description of clouds at airport. Can be one of:

Visibility Visibility (metres) at airport





M E T A R 3 / 3

L1 P R E S E N T W T H R - - - - - - - R1

R E C E N T W T H R - - - - - - - L2 T E M P E R A T U R E - - - ° R2

D E W P O I N T - - - ° L3 Q N H - - - - H P A R3

L4 R4

L5 R5

L6 ◄ F I S - B P R I N T ► R6

Figure 102 METAR Page 3 Information Description


Present Wthr

Recent Wthr

Temperature

Dew Point

QNH Local barometric pressure




4.2.15.3.4 FIS-B METAR Trend Report Display (TREND RPT)

M E T A R T R E N D R E P O R T 1 / x

L1 T R E N D M E S S A G E D I S P L A Y E D R1


L3 R3

L4 R4

L5 ◄ P R I N T R5

L6 ◄ F I S - B M E T A R ► R6

Figure 103 METAR Trend Report Page (TREND RPT)



4.2.15.3.5 FIS-B METAR Text Report Display (TEXT RPT)

M E T A R T E X T R E P O R T 1 / x

L1 T E X T M E S S A G E D I S P L A Y E D R1


L3 R3

L4 R4

L5 ◄ P R I N T R5

L6 ◄ F I S - B M E T A R ► R6

Figure 104 METAR Text Report Page (TEXT RPT)

4.2.15.4 FIS-B RVR (RVR)

R V R M E S S A G E 1 / x

L1 R V R | L P P T | 1 1 : 3 9 R1

L2 R V R | L H H R | 0 0 : 2 6 R2

L3 R V R | L H H R | 0 0 : 2 3 R3

L4 R V R | L H H R | 0 0 : 2 1 R4

L5 R V R | L H H R | 0 0 : 2 5 R5

L6 < F I S - B R6

Figure 105 Received RVR Message Menu Page(s) (RVR)

Received RVR messages are listed on this page in the order in which they were received. The displayed list identifies the type of message, the airport it is applicable to and the time of reception. Selecting the required data to view is achieved by use of the appropriate Programmable Key (L1 to L5). Further pages of data are identified by the number of pages count (shown as x in Fig 105) being set to more than 1. Navigation between the pages is available using the PREV and NEXT MCDU keys.



4.2.15.4.1 FIS-B RVR Data Display 1 (RVR1)

R V R 1 / 2

L1 R V R O R I G I N I C A O N U M B E R R1

R V R I D I D N U M B E R L2 T I M E D A T E 2 2 . 2 2 Z O C T 1 9 / 0 1 R2

R U N W A Y I D 1 5 R I G H T L3 B R A K I N G A C T I O N M E D / P O O R R3

R U N W A Y D E P O S I T S L4 F R O Z E N R U T S O R R I D G E ST R4

R U N W A Y C O N T A M I N A T I O N L5 5 1 - 1 0 0 P C T R5

D E P T H O F D E P O S I T S > 4 0 C M L6 ◄ F I S - B P R I N T ► R6

Figure 106 Received RVR Message Page 1


RVR Origin

RVR Id

TimeDate

Runway Id

Braking Action

Runway Deposits

Runway Contamination

Depth of Deposits

Table 31. Received RVR Message Page 1 Description

4.2.15.4.2 FIS-B RVR Data Display 2 (RVR2)

R V R 2 / 2

L1 R E D R U N W A Y L T H 6 4 2 5 M T R S R1

R E D R U N W A Y W D T H 7 0 M T R S L2 R V R - T O U C H D O W N 1 4 7 5 M T R S R2

R V R - M I D P O I N T 1 0 0 0 M T R S L3 R V R - E N D P O I N T 2 0 0 M T R S R3

R U N W A Y U S E Y E S L4 R U N W A Y A V A L 1 3 . 3 2 Z O P E N T R4

W I N D S H E A R Y E S L5 R5

L6 < F I S - B R6

Figure 107 Received RVR Message Page 2


Red Runway Lth Length (metres) of runway to be used

Re Runway Wdth Width (metres) of runway to be used

RVR-Touchdown

RVR-Midpoint

RVR-Endpoint

Runway Use

Runway Avail

Windshear

4.2.15.5 FIS-B Send Request (SEND)

S E N D R E Q U E S T A I R P O R T R E P O R T

L1 E G S S < S E L > R E Q R V R R1

L2 R E Q A T I S R2

L3 R E Q M E T A R R3

L4 R E Q S I G M E T R4

L5 R5

L6 < F I S - B S E N D > R6

Figure 108 Send Request Display (SEND)

This page is used to transmit a request for Flight Information Service (FIS) data for a specified airport. The airport code is entered at line L1 and the type of data required requested using one of the Programmable Keys R1 to R4. This action causes the <SEL> flag to be entered against the chosen request as shown in Fig 108. Note: only one data type can be requested at a time; selecting a subsequent choice will cancel the previous one.

When the request has been compiled, the operator selects SEND> and the request is transmitted. Confirmation is given in the scratchpad by the message REPORT REQUEST SENT. An error message is displayed if no airport has been entered (!NO AIRPORT ENTERED), the input airport code is not recognised (!NOT IN DATABASE) or no report type has been selected (!NO REPORT SELECTED).

Once the request has been sent, the message in the scratchpad is cleared using the MCDU CLR key as usual. This also removes the airport entry at line L1.



4.2.15.6 FIS-B Airport Message Display (MSG)

A I R P O R T M E S S A G E 1 / x

L1 ◄ M E T A R L H H R N O V 1 0 0 : 2 1 R1

L2 ◄ S I G M E T L H H R N O V 1 0 0 : 4 1 R2

L3 ◄ R V R L H H R N O V 1 0 1 : 0 1 R3

L4 ◄ A T I S L H H R N O V 1 0 1 : 1 2 R4

O T H E R A I R P O R T I C A O L5 - - - - R5

L6 ◄ F I S - B R6

Figure 109 Received Airport Messages Menu Page (MSG)

4.2.15.7 FIS-B Requested Information Display (REQ INFO)

R E Q U E S T E D I N F O 1 / x

L1 < M E T A R L H H R N O V 1 0 0 : 2 1 R1

L2 < S I G M E T L H H R N O V 1 0 0 : 4 1 R2

L3 < R V R L H H R N O V 1 0 1 : 0 1 R3

L4 < A T I S L H H R N O V 1 0 1 : 1 2 R4

L5 < M E T A R E G K K N O V 1 0 2 : 1 0 R5

L6 < F I S - B R6

Figure 110 Received Requested Information Messages Menu Page(s) (REQ INFO)

These pages display the list of FIS data that has been received in response to a request. If no reports have been received, the message ‘NO REPORTS AVAILABLE’ is displayed. The list is ordered in ‘Time of Receipt’ order.

Navigation between the pages is accomplished using the PREV and NEXT MCDU keys.



4.2.15.8 FIS-B Disable Control Display (DISABLE)

F I S - B D I S A B L E D

L1 R1

L2 R2

L3 R3

L4 R4

L5 R5

L6 E N A B L E > R6

Figure 111 FIS-B Disabled Page (DISABLE)

If the DISABLE key of the FIS-B menu is selected, the FIS processing is suspended and incoming messages are ignored. Resumption of the function is achieved using the ENABLE Programmable Key.



4.3 Navigation Display Unit Displays

The FMU hardware provides a graphical display generator in the form of a displays adapter manufactured by Peritek. This adapter provides a display interface that is the same as a normal PC (this format was chosen to facilitate the procurement of suitable display heads!) and is used to generate the Navigation Display Unit (NDU) display.

The generated image is split into three parts; the display area, which provides graphical positional information to the operator, a single line of text and the softkeys interface. This is shown in Fig 132.

Display area for pilot selected display mode.

↑ | |

5.5“ | | ↓

Text line area 0.2” Softkeys area

0.3”

← - - - - - 6” - - - - - →

Figure 112 NDU Format

4.3.1 NDU Softkeys Interface

A second Human-Machine Interface (HMI) is provided by the NDU softkeys in conjunction with the Cursor Control Device (CCD). At the bottom of the NDU display, an area of screen has been reserved for a row of Softkeys. These are analogous to the programmable keys on the MCDU. The FMU also provides a cursor on the NDU display, controlled by the CCD that is operated by the user.

Two Softkey symbols are used; one identifying that a lower level menu exists, the other signifying a function. Function Softkeys are displayed in either White (unselected) or Green (selected).

The Softkey NDU function allows the operator to enable/disable symbology (DCP), view/respond to received ATC messages (ATC), command ASAS functions (ASAS) and command Tactical Commands (TC).

4.3.1.1 Top Level Softkey Menu

The initial softkeys display is shown in Fig 133. This top level menu provides access to the softkey functionality as defined in Table 33.



DCP

ATC

ASAS

TC A-OPS

Figure 113 NDU Softkey – Initial Menu

Softkey Function

DCP Displays the DCP menu that provides for the selection/deselection of symbology on the Nav Displays

ATC Displays the ATC menu that allows viewing and/or responding to received ATC messages

ASAS Displays the ASAS menu that allows the compilation of manoeuvre commands to the MA-AFAS

TC Displays the Tactical Command (TC) menu that allows the input of Tactical Commands (from ATC) into the MA-AFAS

A-OPS Toggle switch that enables / disables Autonomous Operations. Green when active

Table 33. Softkey Main Menu Functionality

4.3.1.2 DCP Softkey Menu

The DCP Softkey menu, accessed by pressing the DCP Softkey on the Top Level menu, allows the operator access to further menus that allow modification of the Nav Display settings. Currently three options are supported as defined in Table 34.

WXR

TERR

TRFC

TAXI MAP RETURN

Figure 114 NDU Softkey – DCP Menu

Softkey Function

WXR Not available in this release

TERR Not available in this release

TRFC Displays the Traffic (TRFC) menu that allows control of symbology for external traffic objects

TAXI Displays the TAXI menu that allows control of symbology for objects displayed on the TAXI maps

MAP Displays the MAP menu that allows control of symbology for en-route objects

RETURN Return to the Top Level Menu

Table 34. Softkey DCP Menu Functionality

Comment: Keys depicted on this and subsequent NDU softkey pages are live hyperlinks



4.3.1.2.1 Traffic (TRFC) Softkey Menu

This Softkey menu allows the operator to enable or disable the display of traffic symbology on the nav display and to define what data associated with the traffic is visible. Four selections are available as defined in Fig 135 and Table 35. When selected, the Softkey symbology is set to Green. When the required selections have been made, the RETURN Softkey returns the DCP menu to the screen.

TRFC

ALT

CODE

SPD RETURN

Figure 115 NDU Softkey – Traffic (TRFC) Functions

Softkey Function

TRFC Enables/disables the display of traffic information on the NDU

ALT Enables/disables the display of relative height data associated with the traffic

CODE Enables/disables the display of the ICAO code associated with the traffic

SPD Enables/disables the display of speed data (IAS and Groundspeed) associated with the traffic

RETURN Return to the DCP Menu

Table 35. Softkey Traffic (TRFC) Functionality

4.3.1.2.2 TAXI Softkey Menu

This Softkey menu allows the operator to enable or disable the display of symbology on the Taxi Map display. Five selections are available as defined in Fig 136 and Table 36. When selected, the Softkey symbology is set to Green. When the required selections have been made, the RETURN Softkey returns the DCP menu to the screen.

VEHICL

GATE

GATE-I

TWY-ID HOLD-I RETURN

Figure 116 NDU Softkey – TAXI Functions

Softkey Function

VEHICL Enables/disables the display of ground vehicles (as identified by the TIS-B and/or ADS-B data receptions)

GATE Enables/disables the display of the gates

GATE-I Enables/disables the display of the gate Ids

TWY-ID Enables/disables the display of the Taxiways

HOLD-I Enables/disables the display of the holding identifiers




Table 36. Softkey TAXI Functionality

4.3.1.2.3 MAP Softkey Menu

This Softkey menu allows the operator to enable or disable the display of symbology on the Map display. Four selections are available as defined in Fig 137 and Table 37. When selected, the Softkey symbology is set to Green. When the required selections have been made, the RETURN Softkey returns the DCP menu to the screen.

STA

WPT

ARPT

DATA RETURN

Figure 117 NDU Softkey – MAP Functions

Softkey Function

STA Enable/disable the display of Stations (STA) and beacons

WPT Enable/disable the display of Waypoints entered on the LEGS page of the MCDU

ARPT Enable/disable the display of Airports

DATA Enable/disable the display of constraints and ETA data


Table 37. Softkey MAP Functionality

4.3.1.3 ATC Softkey Menu

When a message has been received from ATC, pressing the ATC Softkey on the Top Level Menu results in the display of one of two ATC menus, Normal Message or Long Message, dependant upon the message content.

4.3.1.3.1 ATC Normal Message Softkey Menu

This menu bar is displayed upon selection of the ATC Softkey on the top Level menu following the reception of a normal message. The menu bar, shown in Fig 138, allows a response to the message to be compiled and initiates transfer of the response to ATC. Table 38 lists the responses possible from this menu.

Above the Softkeys is a text display area that is used to display the received message and the number of received messages that have not yet been responded to. The messages are ordered in priority order.

CAN YOU ACCEPT FL190 AT BERG 1/3

AFFIRM

STBY

NEG

LOAD NEXT RETURN

Figure 118 NDU Softkey – ATC Normal Message Menu



Softkey Function

AFFIRM Sends AFFIRM to ATC and displays the ATC ANSWERED Softkey menu

STBY Sends STANDBY to ATC and disables the STBY key. Message stays in the queue until responded to

NEG Sends NEGATIVE to ATC and displays the ATC ANSWERED Softkey menu

LOAD LOADs the uplinked data to the system and displays the EXECUTE menu

NEXT Selects the next ATC uplink message for display. If no other messages have been received, this key is blanked


Table 38. Softkey ATC Normal Message Menu

4.3.1.3.1.1 ATC Uplink Answered Softkey Menu

This menu bar displays the ATC ANSWERED menu, which is accessed by pressing either the WILCO, AFFIRM, UNABLE or NEGATIVE menu buttons on any of the ATC Menus. The menu, shown in Fig 139, is used to display the message, the response, and the number of outstanding messages. Possible options are defined in Table 39.

NEGATIVE - CAN YOU ACCEPT FL190 AT BERG 1/3

CLEAR

LOAD NEXT RETURN

Figure 119 NDU Softkey – ATC Uplink Answered Menu

Softkey Function

CLEAR Removes the current message from the display to the message log and returns to the ATC Menu to displays the next message if any have been received


NEXT Selects the next ATC uplink message for display. If no other messages have been received, this key is blanked


Table 39. Softkey ATC Uplink Answered Menu Functionality

4.3.1.3.2 ATC Long Message Softkey Menu

This menu bar is displayed upon selection of the ATC Softkey on the top Level menu following the reception of a message that is longer than the text bar. The menu bar, shown in Fig 140, allows a response to the message to be compiled and initiates transfer of the response to ATC. Table 40 lists the responses possible from this menu.

Above the Softkeys, the text display area is used to display part of the received message, scrolling controls and the number of received messages that have not yet been responded to. Received messages are ordered in priority order.

BEGINNING OF MESSAGE < > 1/1

WILCO

STBY

UNABLE

LOAD RETURN

Figure 120 NDU Softkey – ATC – Long Message Menu

Softkey Function

WILCO Sends WILCO to ATC and displays the ATC ANSWERED Softkey menu

STBY Sends STANDBY to ATC and disables the STBY key

UNABLE Sends UNABLE to ATC and displays the ATC ANSWERED Softkey menu



Table 40. Softkey ATC – Long Message Menu

4.3.1.4 ASAS Softkey Menu

The ASAS Softkey menus allow the operator to define manoeuvres for the MA-AFAS. This functionality allows ATC to define required manoeuvres using voice communications only.

Four manoeuvre categories are currently supported; Resume, Merge, Remain and Pass as shown in Fig 141. The text line above the softkeys is used to display the command compiled using the ASAS Softkey functionality.

TARGET 5207

RESUME

MERGE

REMAIN

PASS RETURN

Figure 121 NDU Softkey – ASAS Menu

Softkey Function

RESUME Display the RESUME Softkey Menu

MERGE Display the MERGE Softkey Menu

REMAIN Display the REMAIN Softkey Menu

PASS Display the PASS Softkey Menu


Table 41. Softkey ASAS Menu



4.3.1.4.1 RESUME Softkey Menu

In addition to the separation distance (or time), one of three RESUME manoeuvres can be defined using this menu bar: Lateral (NAV), Descent (DESC) or Climb (CLB).

The defined manoeuvre is displayed in the text line above the softkeys.

To abort the manoeuvre definition process, the RETURN Softkey displays the ASAS Menu Bar.

CLEAR OF TARGET (XX) NM

NAV

DESC

CLB

SEP RETURN

Figure 122 NDU Softkey – RESUME Functions

Softkey Function

NAV Displays the Lateral Resume menu and invokes the Navigation function

DESC Invokes the DESCENT RESUME manoeuvre and displays the Descent Resume menu

CLB Invokes the CLIMB RESUME manoeuvre and displays the Climb Resume menu

SEP Displays the Separation menu to allow operator entry of the required separation distance for a manoeuvre

RETURN Return to the ASAS Menu

Table 42. Softkey Traffic (TRFC) Functionality

4.3.1.4.1.1 Lateral Resume (NAV) Softkey Menu

When the Lateral Resume manoeuvre is selected from the RESUME Menu Bar, the operator has the choice of LOADing the manoeuvre to the Trajectory Generator, abandoning the manoeuvre or modifying it. Fig 143 shows the resultant display for a Lateral Resume manoeuvre where the operator has yet to define which waypoint the manoeuvre uses.

CLEAR OF TARGET 5 NM RESUME TO (WPT)

LOAD DELETE RETURN

Figure 123 NDU Softkey – Lateral Resume Functions

Softkey Function

LOAD Loads the manoeuvre into the Trajectory Generator and displays the EXECUTE softkey menu

DELETE Deletes any modified data, clears the text line and returns to the ASAS menu




Table 43. Softkey Lateral Resume Functionality

4.3.1.4.1.1.1 EXECUTE Softkey Menu

When a manoeuvre has been defined, the operation of the LOAD Softkey sends the data to the Trajectory Generator and displays this EXECUTE Menu bar. At this stage, the operator can Execute the manoeuvre (EXEC), ERASE the defined manoeuvre or return to the ASAS menu page to modify the manoeuvre (RETURN).

TEXT OF MANOEUVRE

EXEC

ERASE RETURN

Figure 124 NDU Softkey – Execute Functions

Softkey Function

EXEC Causes the system to execute the chosen manoeuvre and returns to the Top Level softkey menu

ERASE Deletes any modified data and returns to the ASAS menu Bar

RETURN Return to the ASAS Menu Bar

Table 44. Softkey Execute Functionality

4.3.1.4.1.2 Descent Resume (DESC) Softkey Menu

After pressing the Descent Resume (DESC) key in the MAP or PLAN display mode:

CLEAR OF TARGET 5 NM DESCENT TO (XXX)

ALT

LOAD DELETE RETURN

Figure 125 NDU Softkey – Descent Resume Functions

Softkey Function

ALT Displays the Altitude Softkey Menu

LOAD Loads the manoeuvre into the Trajectory and displays the EXECUTE softkey menu

DELETE Deletes any modified data and returns to the ASAS menu


Table 45. Softkey Set Altitude Function

4.3.1.4.1.2.1 Altitude Softkey Menu

After pressing the Altitude (ALT) key in the Descent Resume (DESC) or Climb Resume (CLB) menus:

MESSAGE BAR TEXT

<

1000

>

OK

Figure 126 NDU Softkey – Set Altitude Function

Softkey Function

< Decrements the required altitude by 100Ft

(1000) Current Required Altitude display

> Increments the required altitude by 100Ft

OK Accepts the modified altitude data and returns to the Previously displayed menu

Table 46. Softkey Descent Resume Functionality

4.3.1.4.1.3 Climb Resume (CLB) Softkey Menu

After pressing the Climb Resume (CLB) key in the MAP or PLAN display mode:

CLEAR OF TARGET 5 NM DESCENT TO (XXX)

ALT

LOAD DELETE RETURN

Figure 127 NDU Softkey – Descent Resume Functions

Softkey Function

ALT Displays the Altitude Softkey Menu to allow operator entry of the required altitude separation distance for a manoeuvre




Table 47. Softkey Climb Resume Functionality

4.3.1.4.1.4 Separation (SEP) Softkey Menu

This Softkey display is invoked to allow entry of the required separation distance/time for a manoeuvre:

MESSAGE BAR TEXT

<

8

>

D OK

Figure 128 NDU Softkey – Set Separation Function

Softkey Function

< Decrements the required value by 1nm or 5min depending upon softkey 4 selection

(8) Current required separation display

> Increments the required value by 1nm or 5min depending upon softkey 4 (D/T) selection

D/T Defines the separation units as Distance, in nm, or Time, in minutes

OK Accepts the current value for separation and returns to the RESUME Softkey menu

Table 48. Softkey Set Separation Function

4.3.1.4.2 MERGE Softkey Menu

After pressing the MERGE softkey on the ASAS menu:

MERGE TO (WPT)

AT LST

SEP

LOAD DELETE RETURN

Figure 129 NDU Softkey – MERGE Functions

Softkey Function

AT LST Selects the AT LEAST merge behind option





Table 49. MERGE Softkey Functionality

4.3.1.4.3 REMAIN Softkey Menu

After pressing the REMAIN softkey on the ASAS menu:

REMAIN (XXX)

AT LST

UNTIL

SEP

LOAD DELETE RETURN

Figure 130 NDU Softkey – REMAIN Functions

Softkey Function

AT LST Selects the AT LEAST remain behind option



Softkey Function

UNTIL





Table 50. MERGE Softkey Functionality

4.3.1.4.4 PASS Softkey Menu

After pressing the PASS softkey on the ASAS menu:

PASS (XXX)

BEHIND

BELOW

ABOVE

RETURN

Figure 131 NDU Softkey – PASS Functions

Softkey Function

BEHIND Selects the PASS BEHIND manoeuvre menu

BELOW Selects the PASS BELOW manoeuvre menu

ABOVE Selects the PASS ABOVE manoeuvre menu


Table 51. PASS Softkey Functionality

4.3.1.4.4.1 PASS BEHIND Softkey Menu

After pressing the PASS BEHIND softkey on the PASS menu:

PASS 8 NM BEHIND TARGET THEN RESUME TO (WPT)

SEP

LOAD DELETE RETURN

Figure 132 NDU Softkey – PASS BEHIND Functions

Softkey Function




Softkey Function




Table 52. PASS BEHIND Softkey Functionality

4.3.1.4.4.2 PASS BELOW Softkey Menu

After pressing the PASS BELOW softkey on the PASS menu:

PASS BELOW TARGET 8 NM DESCENT TO (WPT)

SEP

ALT

LOAD DELETE RETURN

Figure 133 NDU Softkey – PASS BELOW Functions

Softkey Function






Table 53. PASS BELOW Softkey Functionality

4.3.1.4.4.3 PASS ABOVE Softkey Menu

After pressing the PASS ABOVE softkey on the PASS menu:

PASS ABOVE TARGET 8 NM CLIMB TO (XXX)

SEP

ALT

LOAD DELETE RETURN

Figure 134 NDU Softkey – PASS ABOVE Functions

Softkey Function


Softkey Function





Table 54. PASS ABOVE Softkey Functionality

4.3.1.4.5 Tactical Command (TC) Softkey Menu

After pressing the TC softkey on the Top Level menu:

HDG

SPD

ALT

RETURN

Figure 135 NDU Softkey – Tactical Command (TC) Functions

Softkey Function

HDG Displays the heading softkey menu to allow operator input of desired heading

SPD Not available in this release

ALT Not available in this release


Table 55. Tactical Command (TC) Softkey Functionality

4.3.1.4.5.1 Desired Heading Entry Softkey Menu

After pressing the TC softkey on the Top Level menu:

1

<

143

> ASAS RETURN

Figure 136 NDU Softkey – Desired Heading Entry Functions

Softkey Function

(1) Increment/Decrement value for Up/Down selector

< Down selector – reduces desired heading by amount shown in key 1 position

(143) Display of current desired heading

> Up selector – increases desired heading by amount shown in key 1 position



Softkey Function

ASAS Returns to the ASAS Softkey menu

EXEC Executes heading change and returns to the Top Level Softkey menu

Table 56. Tactical Command (TC) Softkey Functionality

4.3.2 Navigation Displays

The displays presented on the NDU are selected based on operator selections made using a combination of Softkey and DCP selections.

Note: the images depicted herein may slightly differ from the presented display. For accurate details, the latest version of HMI requirements document (D54) should be consulted.

4.3.2.1 Map Mode Displays

MAP mode is a plan display with a circle segment of 90° (expanded mode) or 360° (centre mode) as shown in Figs 137 and 138.

Both Map Mode displays present navigation data to the operator in a plan view (i.e. looking down on the world). Data displayed includes an abbreviated aircraft state of Groundspeed (GS), True Airspeed TAS), Wind speed and wind direction in the top left corner.

In the top right corner, the current destination waypoint is displayed with the current time (Zulu) and distance to the current destination waypoint (NM).

In the top centre of the display is the current aircraft direction data (in degrees). This is selectable between Heading or Track (HDG/TK) and Magnetic or True MAG/TRU) data using the MCDU FMS Setup page (SET UP). The default for the Map Mode displays is Magnetic Heading.

Between top centre and top right, the nav display shows the current navigation data source. Possible choices are IRS, SBAS, GBAS or VDL4.

On the body of the display is the current trajectory, shown as a purple line, and the current destination

waypoint , also known as the active waypoint. Other waypoints that are not currently being steered to (also called inactive waypoints) are shown in white.

The range of the display is set by the DCP range control. The standard ranges are 10,20,40,80,160 and 320 nautical miles and define the distance from the aircraft symbol to the outer range ring. The middle range ring is annotated with the range distance to that ring i.e. half the selected range. Fig 137 shows a selected range of 80nm.

Each Map Mode display can include navigation features and traffic information as selected on the DCP. The individual symbols are described later.



Figure 137 Map Mode (Expanded) NDU Display

The Expanded Map Mode display provides a view of the received navigation and traffic data for an area that covers a segment of ±45° ahead of the aircraft out to the range specified by the current DCP range selection. The centred map mode, however, show data for the entire 360° around the ownship, out to the selected range.

Cursor Symbol

40nm range ring



Figure 138 Map Mode (Centered) NDU Display

4.3.2.2 Plan Mode Display

PLAN mode is a magnetic north up mode with a selected waypoint (by default the active waypoint) in the centre of a 360° rose. No expanded option is available in plan mode. As with the Map Mode display, the top let and right corners give abbreviated aircraft state and active waypoint data.



Figure 139 Plan Mode NDU Display

4.3.2.3 Profile Mode NDU Display

The Profile (PROF) display presents the vertical profile of the route with the altitude scale on the left, and the time scale along the planned route horizontally (in case no active flight plan available the time along the current track direction is used). On the right a vertical speed scale is presented which is the resultant of the altitude and time axis.

The PROF display is presented in the lower area of the ND usable area. Scaling is such that the entire information content of the MAP display is still presented



4.3.2.4 Taxi Map Mode NDU Display



Figure 140 Taxi Map Display

4.3.2.5 Taxi Plan Mode NDU Display

TAXI PLAN mode is comparable with the normal PLAN mode: it is magnetic North up oriented with a 360 degrees compass rose, and is centred around the current aircraft position.

4.3.2.6 Taxi Airport Mode NDU Display

TAXI ARPT mode is a second north up mode, a 360 degrees compass rose oriented magnetic North up, and in this case centred on a selected reference point.

4.3.2.7 Approach Mode NDU Display

Approach mode is a magnetic heading up mode with a circle segment of 90 degrees (expanded mode) or 360 degrees (centre mode).



Figure 141 Approach Mode

4.3.2.8 NDU Symbology Components

The following Table details all of the component symbols used to create the NDU displays. Each symbol description includes a name, the colour(s) used to display it (White, Green, Cyan, Magenta, GRey, Yellow and Red) and the mode(s) it appears in. A graphical representation is also included.

Name Symbol Display mode Remarks Heading rose (W) Current heading (W) Heading pointer (W) Display orientation (G) Heading reference (G)

MAP TAXI-MAP APP

Selected heading indicator (M)

MAP PLAN APP



Name Symbol Display mode Remarks Selected heading line (M)

MAP PLAN APP

Line appears when pilot selects new HDG, line disappears after 10 sec.

Own aircraft symbol (W)

MAP PLAN TAXI-MAP TAXI-PLAN TAXI-ARPT

Own aircraft symbol (W)

PROF Position: low during climb (0%) mid during cruise (50%) hi during descent (100%) with a smooth transition from one position to the other

Trend vector (W)

MAP Only visible when turning

Range rings (W)

MAP APP TAXI-MAP TAXI-PLAN

2 rings for MAP and APP, 1 ring for TAXI, the middle shows a single value of 50% of the currently selected range.

Active waypoint info (M and W)

MAP PLAN PROF

Ground speed/ True airspeed indications (W)

MAP PLAN PROF TAXI-MAP TAXI-PLAN TAXI-ARPT

No TAS presented on taxi modes

Waypoints (active route) Active (M) Not active (W)

MAP PLAN

Non active waypoints are all other waypoints on active route, either being modified or not.

Waypoints (inactive route) (C)

MAP PLAN



Name Symbol Display mode Remarks Waypoints (active route) Active (M) not active (W)

PROF Symbol and colour coding identical as in MAP and PLAN.

Waypoints (not part of FMS routes) (C)

MAP PLAN

Navaids VOR (C)

MAP PLAN

Navaids DME (C)

MAP PLAN

Navaids VOR/DME (C)

MAP PLAN

Navaids NDB (C)

MAP PLAN

Airport (C)

MAP PLAN



Name Symbol Display mode Remarks Vertical profile points (G)

MAP PLAN

Indicates map position of “T/C” (Top of Climb), “T/D” (Top of Descent), “S/C” (Step Climb), “E/D” (End of Descent). Indicates intermediate T/D points during descent, level segment altitude is displayed “T/D-4000” Indicates start of deceleration to holding pattern speed, wpt speed restriction, or flaps up manoeuvring speed “DECEL” Indicates start of deceleration for airport speed restriction, no text label only green circle.

Active route (M) Modified route (W)

MAP PLAN

Magenta continuous line connecting white waypoints. Active waypoint is magenta. Modified part of the active route is displayed by white short dashes between white waypoints

Active route (M)

PROF Symbol and colour coding identical as in MAP and PLAN

Active route data (M and W)

MAP PLAN

When DATA option selected Magenta for active waypoint, white for not active waypoint

Inactive route (C)

MAP PLAN

Cyan long dashes connecting cyan waypoints

Name Symbol Display mode Remarks Offset route (M)

MAP PLAN

Magenta dot-dash line parallel to the active route

Runway (W)

MAP PLAN

For ranges <= 40 Nm Dashed centerlines extend 14.2 Nm

Runway (W)

MAP PLAN

For ranges >= 80 Nm

Vertical deviation pointer scale (W) pointer (M)

MAP During descent only Scale runs from – 400ft to +400ft. Length scale: 33mm Font height: 3.5mm Digital display of absolute value of VDEV located at bottom of scale when VDEV exceeds 400 ft and located at top of scale when VDEV falls below –400 ft

Altitude scale (W)

PROF Displayed altitude range is defined full_altrange plus 5/42 of full_altrange above it and 20/42 of full_altrange below it. Current altitude relative to altitude range: low during climb (0% of full altrange) mid during cruise (50% of full altrange) hi during descent (100% of full altrange). Last two digits in small font for STD baro setting.

Selected altitude indicator (M)

PROF



Name Symbol Display mode Remarks Selected altitude line (M)

PROF Line appears when pilot selects new altitude, line disappears after 10 sec.

Time scale (W)

PROF

Range setting for PROF mode

PROF Auto scaling is linked with MAP and PLAN range setting. Manual leaves both altitude and time scale pilot adjustable.

Vertical speed scale (W)

PROF Vertical speed scale is the resultant from the altitude and time scale setting. In auto scaling mode always full scale 500fpm or 1000 fpm depending on en-route or TMA flight phase.

Actual V/S (W)

PROF Diamond symbol on V/S scale

Selected V/S indicator (M)

PROF Magenta circle on V/S scale.

Selected V/S line (M)

PROF Line appears when pilot selects new V/S, line disappears after 10 sec. Line connects fixed a/c symbol with selected V/S symbol.

Aircraft (W)

MAP PLAN TAXI-MAP TAXI-PLAN TAXI-ARPT APP

Symbol is oriented in aircraft track. Label contains relative altitude, flight identification (callsign and BICCA code) and indicated airspeed. (switching and decluttering avail) Symbol size: 4.5x6mm Font height: 2.5mm Non scalable

Climb/descent arrow for traffic (W)

MAP PLAN APP

If aircraft V/S exceeds 500ft/min, arrow is presented. Up or down.

Menu buttons (W, G, C)

MAP PLAN APP TAXI-MAP TAXI-PLAN TAXI-ARPT

Bottom of screen below aircraft symbol. Buttons are multi functional. Button size: 17 x8 mm Font height: 3.5 mm Text centered in knob



Name Symbol Display mode Remarks Text line (G) MAP

PLAN APP TAXI-MAP TAXI-PLAN TAXI-ARPT

Between button and fixed aircraft symbol. Font height: 3.5 mm Max 50 characters in textline. If applicable, present scroll keys and msg queue number.

Taxiway (GR)

TAXI-MAP TAXI-PLAN TAXI-ARPT

Taxiway ident (Y)


Runway (l-GR)


Runway ident (Y)


Stopbar (R) TAXI-MAP TAXI-PLAN TAXI-ARPT

Only active stopbars are displayed

Holding position ident (R, W)


Intersection of taxiways (GR)


Intersection of taxiways/ runways (GR, l-GR)


Apron (GR)


Parking or stand (small / large range) (W, M)

/

/


Symbol to use depends on selected display range, white standard magenta is cleared

Stand guidance lines (W, M)


White standard, magenta is cleared

Parking ident (C)


Building (GR)




Name Symbol Display mode Remarks Ground vehicle (W)


Aircraft without heading info (W)


Taxi route (M) / TAXI-MAP TAXI-PLAN TAXI-ARPT

Full magenta line for cleared taxi route, dashed magenta line for planned but not yet cleared route. Cleared and planned route together form the active route

Table 57. NDU Component Symbology

4.3.2.9 Cursor Control Device Operation

The CCD will be a standard mouse or trackball with two select buttons. As with a PC, the left button is for selecting items on the ND while the right one is used to display detailed information, if available, on the object selected by the cursor.

4.3.3 Display Control Panel

Each installation of the MA-AFAS has a different Displays Control Panel but the functionality is the same in all cases. Fig 140 shows the IHTP representation of a DCP which is based upon the BAC1-11 unit.

Each DCP has the components identified in Table 58.



Figure 142 IHTP Representation of the Displays Control Panel

Control BAC1-11 Description ATTAS Description Nomenclature

Range Selector Rotary dial 6 positions (double legend, or selected value in display next to button)

Rotary dial 6 positions with range in nm only

Range Nm air / taxi:

10 / 0.25

20 / 0.5

40 / 1.0

80 / 2.0

16 / 4.0

320

Mode Selector Rotary dial 4 positions Rotary dial 5 positions MAP CTR (ATTAS Only)

MAP (ARC on ATTAS)

TAXI

PROF

APP

Display Mode 2 Select buttons Not available – Mode selector pre-programmed in ATTAS.bpt blueprint fie

PLAN (toggle between monitoring mode and planning mode)

CTR (toggle between 90 deg and 360 deg of rose segment)

Spares 5 Selection buttons None Not used.

Table 58. DCP Functionality



4.3.4 Autopilot Control Unit

As with the DCP, each installation of the MA-AFAS uses a different Autopilot Control Panel. All, however, provide similar functionality. The Control panels provide an interface to allow control of the aircraft by pilot, Autopilot or MA-AFAS. Three parameters are controlled; Height, Speed and Lateral Position.

4.3.4.1 BAC1-11 Autopilot

4.3.4.1.1 General

Figure 143 BAC1-11 AFCS Control Panel

4.3.4.1.2 BAC1-11 Autopilot Engagement

4.3.4.1.3 BAC1-11 Autopilot Disengagement

4.3.4.2 ATTAS Autopilot

4.3.4.2.1 General

The Autopilot fitted in the ATTAS, shown in Fig 141, provides 3 independent control channels for the Speed (S15), Heading (S16) and Altitude (S17 and S18). It also provides control and display of the aircraft vertical speed (V/S), and controls for the two Autopilots (S22 and S23) and the Autothrottle (S24). Controls also exist for altering the units of the displayed values. Speed can be displayed in Kts or m/s (S28), Direction as Heading or Track (S21) and Altitude in Ft or metres (S26).



Figure 144 ATTAS Autopilot

4.3.4.2.2 Engagement of MA-AFAS Control

The operation of the control panel whilst under manual or Autopilot control will not be included in this document which will only deal with operation under MA-AFAS control. For MA-AFAS operation however, it is required that the Autopilot and Autothrottle controls are ON (S22, S23 and S24).

For each channel, the procedure is the same. Once the MA-AFAS trajectory has been computed and loaded and the aircraft is airborne, the MA-AFAS can be commanded to provide control signals by use of the EXECUTE control on the VNAV MCDU page.

Each autopilot channel can then be engaged independently by pulling the control button momentarily; S15 for speed, S16 for lateral and S18 for vertical. When under external control, the display of the channel will be set to ‘-----‘.

4.3.4.2.3 Disengagement of MA-AFAS Control

As with engagement, disengagement of the MA-AFAS from the Autopilot is on a channel by channel basis. To disengage a channel, the control button (S15, S16 or S18) is pushed momentarily. This will engage the autopilot once more.



5 SOFTWARE UPDATES



6 CUSTOMISATION



7 MAINTENANCE ACTIVITIES 7.1 MCDU

Page 2 of the MCDU Menu gives access to the configuration pages inherent in the MCDU. Only the pages relevant to setting up the MA-AFAS will be described here.

The MCDU menu pages are accessed using the MENU function key.

M C D U M E N U 2 / 2

L1 R1

L2 R2

L3 R3

L4 R4

L A M P T E S T ( O N ) L5 ◄ S E L E C T O F F P / N ► R5

L6 ◄ P A R A L L A X M A I N T ► R6


The lamps on the MCDU are normally tested automatically at power on. Operating the L5 programmable key will repeat the switch-on test for diagnostic purposes.

General Information and parallax adjustments are selected using the P/N (R5) and PARALLAX (L6) programmable. Advanced set-up parameters are available using the MAINT (R6) programmable key.



7.1.1 Parallax Adjustment Page

P A R A L L A X A D J U S T 1 / 1

L1 - R1

L2 - M O V E U P ► R2

L3 ◄ L E F T - - M O V E - - R I G H T ► R3

L4 - M O V E D O W N ► R4

L5 - R5

L6 ◄ R E T U R N R6


On fitting the MCDU in a cockpit, it may be found that text at the edges of the display is obscured by the MCDU bezel. To correct this it is possible to move the text window within the display area using the Up (R2), Down (R4), Left (L3) and Right (R3) controls on the PARALLAX ADJUST page.



7.1.2 MCDU Part Number Page

P A R T N U M B E R 1 / 1 O P P R O G R A M P S A

L1 6 1 3 9 8 5 - 0 0 5 9 8 4 B 1 1 B 5 R1

B O O T P R O G R A M P S A L2 6 1 2 8 7 2 - 2 0 4 C D D 3 3 1 9 5 R2

C F G C R C L3 D 9 6 5 4 4 4 1 R3

L4 R4

L5 R5



The current MCDU software version information is available on the MCDU Part Number (P/N) page.



7.1.3 MCDU Maintenance Password Page

M A I N T E N A N C E 1 / 1 P A S S W O R D

L1 - - - - - R1

L2 R2

L3 R3

L4 R4

L5 R5


Figure 148 MCDU Maintenance Password Page

In order to access the detailed maintenance pages of the MCDU, a password is needed. For MA-AFAS, the default password of “CMC” has been retained. This is entered using the normal scratchpad data entry routine.



7.1.4 MCDU Maintenance Menu

M C D U M A I N T E N A N C E 1 / 1

L1 ◄ F O N T S K E Y T E S T ► R1

L2 ◄ M E M O R Y A N N U N T E S T ► R2

L3 ◄ C O N F I G C O L O R T E S T ► R3

L4 V I D E O T E S T ► R4

L5 ◄ C O M M C O N T R A S T T E S T ► R5

L6 ◄ M E S S A G E A U T O T E S T ► R6

Figure 149 MCDU Maintenance Menu Page 1

This page gives access to all the maintenance facilities of the MCDU. Only the CONFIG (L3) option is further described here; all other options are covered in the manufacturers documentation.



7.1.5 MCDU Configuration Page

C O N F I G 1 / 1

L1 ◄ A 4 2 9 I N T E R F A C E R1

L2 R2

L3 R3

L4 R4

A U T O L O G O N ( Y E S ) L5 ◄ S E L E C T N O R5



This page gives access to the ARINC429 Interface configuration page. The Auto Log function should be left in the default state of OFF.



7.1.6 MCDU ARINC 429 Interface

A 4 2 9 I N T E R F A C E 1 / 3 S P E E D I / P 1 P R O T O C O L

L1 ► L O W A 7 3 9 - 2 ◄ R1

O U T P U T L2 1 ◄ R2

S P E E D I / P 2 P R O T O C O L L3 ► L O W C M C ◄ R3

O U T P U T L4 2 ◄ R4


O U T P U T L6 ◄ R E T U R N 2 ◄ R6

Figure 151 MCDU ARINC 429 Interface Page 1


L1 ► L O W C M C ◄ R1

O U T P U T L2 2 ◄ R2


O U T P U T L4 2 ◄ R4


O U T P U T L6 ◄ R E T U R N 2 ◄ R6





L1 ► L O W C M C ◄ R1 O U T P U T

L2 2 ◄ R2

S P E E D O / P 1 L3 ► L O W R3

S P E E D O / P 2 L4 ► L O W R4

C M C L B L 3 7 7 A 7 3 9 L5 ► O U T 1 N O N E ◄ R5



These three pages allow the modification of the ARINC 429 interface properties. In the simplex MA-AFAS set-up, only input 1 and output 1 are used. These should be set up as shown in the above figures.



APPENDIX A DEVELOPMENT ENVIRONMENT INITIALISATION

A1 Development Environment Initialisation

Following power-up, the next step in initialising a system in the Development Environment is to load and run the operational software. All development rigs use scripts to control the downloading and running of software on the PowerPCs. By default, these scripts are called FmuScript.spt and CmuScript.spt. Each script identifies where the configuration (blueprint) files are stored and which software to download and run. Appendix B gives example scripts for the FMU and CMU that show the identification of the location of blueprint files, load commands and spawn (run) commands.

Each script is run within the Tornado 2 development environment. To invoke this, the user needs to log on to the PC associated with the rig; at Rochester, the normal NT user login is used whilst on-site the ihtpguest account login is used.

Once logged in, the user should navigate the Start button to run the Tornado2 application. This produces the Tornado2 workspace that allows access to the development environment functionality. No attempt will be made here to detail what the user can do with this environment; instead, a simple guide is provided that details how to initialise the MA-AFAS processors.

First, each MA-AFAS processor requires a Target Server to be initiated. This is done by using the Tools:Target Server pull-down menu item of Tornado2. Selecting this menu item should reveal the names of the two Avionics rig processors and the user should select each in turn. Table 59 identifies which processors are used in each rig. The activation of operational Target Servers will be signified by the presence of two target icons in the Windows Tool Tray display at the bottom right of the screen.

Note: It has been noted that on-site systems need extra time, up to 2 minutes, to initialise the target servers when compared to the In House systems.

Rig FMU CMU

Rig #1 MA-AFAS07 MA-AFAS08




On-Site MA-AFAS09 MA-AFAS10

Table 59. PowerPC Processor Identification

Once the Target servers have established, Shell Windows for each processor should be invoked by selecting the appropriate processor name in the Tornado Launch window (see Fig 141) and selecting

the 'Launch Shell' button .

Figure 154 Tornado Launch Window

A2 Database Modification



Data held on the hard drive is in the form of text files (with a .txt extension). The data available is stored in sub-directories of the hard drive according to the function that requires the data as defined in Table 60.

Directory Name Data Contents

/sd0/ndu Navigation Display Formats

/sd0/navdb Navigation Database

/sd0/mcdu MCDU Menus

/sd0/tg Traffic Generator parameters

/sd0/tg/bada Aircraft model parameters

/sd0/AOC

/sd0/broadcast

/sd0/ag Aircraft Guidance parameters

Table 60. Hard Drive Directory Structure

The following paragraphs define the formats of the data within the files on the hard drive. Most files will be generated from the standard ARINC424 aeronautical database so this data is for reference only. Some files, e.g. those for company routes, can be hand crafted for the specific MA-AFAS trials and this section shows how the files are formatted and copied to the hard drive.

Examples of the files are given in section A3.

A2.1 Data File Formats

A2.1.1 NDU Data

A2.1.2 Navigation Database Data

The supplementary data files should be formatted in accordance with ARINC 424 subject to the following relaxation’s.

The file can contain comment lines. Any line beginning with a “#” symbol will be treated as a comment line.

Since the database does not make use of all fields within the ARINC 424 record types, it is only necessary to specify those records that are used by the database. These are detailed below for each record type. In the tables, the reference field contains the ARINC 424 paragraph reference.



A2.1.3 Navigation Aids (D,DB)

Data Item Reference Column Length

Airport Identifier 5.6 7 to 10 4

Navaid Identifier 5.33 14 to 17 4

Navaid Class 5.35 28 to 32 5

VOR,NDB Position 5.36,5.37 33 to 51 19

DME Position 5.36,5.37 56 to 74 19

Magnetic Variation 5.66 75 to 79 5

Navaid Full Name 5.71 99 to 123 30

Table 61. Required elements for Navaid Records

A2.1.4 Waypoints (EA, PC)



Waypoint Identifier 5.33 14 to 18 5

Position 5.36,5.37 33 to 51 19

Magnetic Variation 5.66 75 to 79 5

Full Name 5.71 99 to 123 30

Table 62. Required Elements for waypoint records

A2.1.5 Procedures (PD, PE, PF)



Procedure Identifier 5.9,5.10 14 to 19 6

Route Type Code 5.7 20 1

Transition identifier 5.11 21 to 25 5

Sequence Number 5.12 27 to 29 3

Fix identifier 5.13 30 to 34 5

Fix location in database 5.4,5.5 37 to 38 2

Turn Direction 5.20 44 1

Required Navigation Performance 5.211 45 to 47 3

Path Terminator code 5.21 48 to 49 2

Recommended Navaid 5.23 51 to 54 4

Arc Radius 5.204 57 to 62 6




Theta 5.24 63 to 66 4

Rho 5.25 67 to 70 4

Magnetic course 5.26 71 to 74 4

Route Distance 5.27 75 to 78 4

Recommended navaid reference 5.4,5.5 79 to 80 2

Altitude descriptor 5.29 83 1

Altitude 5.30 85 to 89 5

Altitude 5.30 90 to 94 5

Transition Altitude 5.53 95 to 99 5

Speed limit 5.72 100 to 102 3

Vertical Angle 5.70 103 to 106 4

Centre Fix 5.144 107 to 111 5

Centre fix reference 5.4,5.4 115 to 116 2

Table 63. Required Elements for procedure records

A2.1.6 Company Route File

The company route data files use a free text format and are based upon the flight plan file format provided by Skysoft. This allows the same format to be used for both the Avionics Rig and the AGP. Each file has two parts, a header data section and a route data section.

The header section of the file contains one data item per line. The information and expected order are shown in the table below.

Tail Number

Flight ID

Primary/Alternate Tag

Flight Plan Identifier

Estimated No Of Passengers

Flight Rules

Flight Type

Aircraft Type

Wake Turbulence Category

Equipment

Departure Airport

Departure time

Estimated Off Blocks Time

Cruising Speed (ground speed)

Cruising Altitude (feet)

Rate Of Climb/Descent (feet/min)

Destination Airport

Alternate Airport

Second Alternate Airport

Comment line

Table 64. Header information for a company route file

The second section of the data file contains the route information. The information for each leg of the route should appear on a single line. The format of the line is as follows.

Data Item Notes Column Length

Waypoint name 1 1 to 5 5



Data Item Notes Column Length

Waypoint latitude 2 27 to 39 13

Waypoint longitude 3 41 to 54 14

Turn Type 4 56 to 61 6

Airspace type 5 63 to 66 4

Notes Optional 68 to end Variable

Table 65. Required information for company route leg

NOTE 1: This field can contain either a waypoint name or a procedure name. If the field contains a procedure name, then the airspace type field must be set to the procedure type.

NOTE 2: An example of the format of the latitude information is N51°07'26.40".

NOTE 3: An example of the format of the longitude information is W001°47'13.56".

NOTE 4: The turn type is optional but when it is specified, it should contain one of the following strings “none”, “before”, “arc”, “at”.

NOTE 5: The following airspace types are recognised; “none”, “TMA”, “MAS”, “FF”, “UMAS”, “SID”, “STAR”, “APP”. The airspace type will be used to set to the RNP for the route leg.

A2.1.7 MCDU Menus Data

A2.2 Creating Supplementary File Information

A2.2.1 File Location

All supplementary data files must be stored on the system hard drive, normally in the directory “/sd0/navdb”. The actual directory used should appear within the configuration file for the navigation database.

A2.2.2 Configuration File Changes

Once the supplementary files have been created and stored on the hard drive, the system needs to be able to access the information so that it can be added to the relevant parts of the navigation database.

For the system to know that the supplementary files exist, changes must be made to the file “NDBconfiguration.txt” before it is to be used. These changes are described below.

Although the process described here will show how to make use of a file containing supplementary SID information; the process is the same for all file types.

a) Search through the text file until the following set of lines is located. The text to the right of each line explains what each line contains, however these comments do not actually occur in the supplementary files.

… End of the previous database information

**Airport_SID_Database Comment line

pd.txt Text file name

5636096 Amount of memory for the database in bytes



**Supplementary_Airport_SID_Files Comment line

0 Number of supplementary files

… Start of the next database information

b) Change the Number of supplementary files to the number of files that are going to be used. If

there are no supplementary files for a particular database, leave the required number at zero.

c) Insert the names of the supplementary files that are to be used with that particular database. The filenames should be entered one per line (order is not important), between the Number of supplementary files and the Start of the next database information.

d) An example of what this file might look like is shown below.

… End of the previous database information

**Airport_SID_Database Comment line

Pd.txt Text file name

5636096 Amount of memory for the database in bytes

**Supplementary_Airport_SID_Files Comment line

2 Number of supplementary files

BoscombeSID.txt First supplementary file

RochesterSID.txt Second supplementary file

… Start of the next database information

When the databases are being created during system initialisation, the information contained in each of the supplementary files will be added to the relevant database after it has been created using the main text files.

A2.2.3 Memory Usage And Requirements.

If the current allocation of memory for any database needs to be changed, then go to that section of the “NDBconfiguration.txt” file and increase/decrease the Amount of memory for the database in bytes value (see above) as required.

The table below shows the amount by which the “Amount of memory for the database in bytes” value must be increased in order to provide one extra supplementary record to that database.

Database Name Record Size (bytes)

Navaid Record 88

Waypoint Record 336

Procedure Record1 192

Company Route 11312

Table 66. Memory usage for record

1 This is the amount of memory required for each component of a Procedure. A procedure containing 10 elements will require 1920bytes.



A2.3 Transferring Data To/From the Hard Drive

Since the MA-AFAS Hard Drive is attached to the FMU SCSI bus, data can only be transferred between the outside world and the Hard Drive via the FMU. This is accomplished using the Tornado2 development environment. Once a shell window has been established for the FMU (as described in A1 above), data held on the fileservers may be transferred in the following way.

In the FMU shell, the user types a copy command in the following format:

@cp “(full path and name of source file)”,“(full path and name of destination file)” For example, to copy a specific NDB configuration file to the correct directory on the hard drive, the following command should be used:

@cp “z:/usr/bas/build_d/NDBConfiguration.txt”,”/sd0/ndb/NDBConfiguration.txt” A resultant status of zero indicates a successful transfer.

Logged data can similarly be moved from the hard drive to the fileservers for analysis. The log files shown in Table 67 are generated during each run.

Filename Contents

/sd0/ag/AircraftGuidanceConstants.txt

/sd0/ag/HistoryFile.txt

/sd0/ag/LateralRoute.txt

/sd0/tg/TrajectoryGeneratorConstants.txt

/sd0/tg/InputTrajectoryConstraints.txt

/sd0/tg/InputFlightPhaseTable.txt

/sd0/tg/InputGeneratedRouteConst.txt

/sd0/ag/GeneratedTrajectoryInfo.txt

/sd0/comms/cm/cm_log.txt

/sd0/comms/cpdlc/cpdlc_log.txt

/sd0/comms/cpdlc/cpdlc_log.txt

Table 67. Log Files Generated by the MA-AFAS Rig

An example would be:

@cp “/sd0/ag/HistoryFile.txt”,”C:/Run1-300103/AG History File.txt” Note that the ‘@’ symbol is used to cause the FMU to transfer data to, and from, the hard drive.

Appendix B3 shows an example script that copies multiple logged data files from the hard drive in a single command.



A3 Example Files

A3.1 Airport Waypoint File # 10 20 30 40 50 60 70 80 90 00 10 20 30 # ARPT NAME__ LATITUDE_LONGITUDE_ MAG__ DESCRIPTION______________FILE_DATE T EGDM CF23 N51100120W001432280 W0400 BOSCOMBE RW23 THRESHOLD | T EGDM DM001 N51061020W001304422 W0400 BOSCOMBE SID/STAR POINT | T EGDM DM002 N51130602W001290547 W0400 BOSCOMBE SID/STAR POINT | T EGDM DM003 N51144998W001341750 W0400 BOSCOMBE SID/STAR POINT | T EGDM DM004 N51060483W001505925 W0400 BOSCOMBE SID/STAR POINT | T EGDM DM005 N50595220W001424528 W0400 BOSCOMBE SID/STAR POINT | T EGDM DM006 N51121664W001391113 W0400 BOSCOMBE SID/STAR POINT | T EGDM ESPIN N51072736W001482254 W0400 BOSCOMBE SID/STAR POINT | T EGDM INGL N51031195W001421803 W0400 BOSCOMBE SID/STAR POINT | T EGDM FRAN N50574628W001471346 W0400 BOSCOMBE SID/STAR POINT | T EGDM KATE N50581972W001423370 W0400 BOSCOMBE SID/STAR POINT | T EGDM MANS N51081343W001353161 W0400 BOSCOMBE SID/STAR POINT | T EGDM MANS2 N51071125W001330841 W0400 BOSCOMBE SID/STAR POINT | T EGDM PRICE N51001200W001401200 W0400 BOSCOMBE SID/STAR POINT | T EGDM REGIS N50490000W002500000 W0400 BOSCOMBE SID/STAR POINT | T EGDM RF001 N51132323W001321084 W0400 BOSCOMBE PA TURN CENTRE | T EGDM RF002 N51083990W001355877 W0400 BOSCOMBE PA TURN CENTRE | T EGDM RF003 N51025859W001465199 W0400 BOSCOMBE PA TURN CENTRE | T EGDM WOLFE N51042400W001470600 W0400 BOSCOMBE SID/STAR POINT |

A3.2 Airport SID File # 10 20 30 40 50 60 70 80 90 00 10 20 30 # ARPT PROCID TRNID FIXID RNP NAVID DIST ALTITUDERULE SPD FILE_DATE T EGDM SID23 1RW23 010ESPIN PC E010CA 234T0020 + 01500 05000180 | T EGDM SID23 2 010WOLFE PC L010RF 00405123800041054T0060 + 03500 05000 RF003 PC | T EGDM SID23 2 020INGL PC E010DF 0090 + 05000 05000 | T EGDM SID23 2 030PRICE PC R010RF 00405123800041054T0125 + FL060 05000 RF003 PC | T EGDM SID23 3KATE 010KATE PC R010DF 0145 + FL075 05000 |

A3.3 Airport STAR File # 10 20 30 40 50 60 70 80 90 00 10 20 30 # ARPT PROCID TRNID FIXID RNP NAVID DIST ALTITUDERULE SPD FILE_DATE T EGDM STR23 1FRAN 010FRAN PC 010IF @ FL050 | T EGDM STR23 2 010KATE PC 010DF @ FL050 | T EGDM STR23 2 020MANS2 PC 010DF @ FL050 | T EGDM STR23 3RW23 010DM001 PC 010DF @ FL040 05000180-300 |



A3.4 Airport Approach File # 10 20 30 40 50 60 70 80 90 00 10 20 30 # ARPT PROCID TRNID FIXID RNP NAVID DIST ALTITUDERULE SPD FILE_DATE T EGDM PA23A ADM001 010DM001 PC E010IF 012T0000 @ FL040 05000180-200 | T EGDM PA23A ADM001 020DM002 PC E010DF 012T0000 @ FL040 05000180-200 | T EGDM PA23A ADM001 030DM003 PC L010RF 00196300160020012T0048 @ 02500 05000180-200RF001 PC | T EGDM PA23A ADM001 040CF23 PG E010CF 234T0075 @ 00767 05000180 | T EGDM PA23B ADM001 010DM001 PC E010IF 054T0000 @ FL040 05000180-300 | T EGDM PA23B ADM001 020DM006 PC L010RF 00414105800041234T0130 @ 02500 05000180-300RF002 PC | T EGDM PA23B ADM001 030CF23 PG E010CF 234T0190 @ 00767 05000180 |

A3.5 Company Route File Tail Number Flight Id Primary or Alternate - alternate used for IFTM Route Identifier Estimated Number of Passengers Flight Rules Type of Flight Type of Aircraft Wake turbulence Category Equipment Departure Aerodrome Time [hh mm ss] -departure time EOBT [hh mm ss] Cruising Speed [Ground_speed] Cruising Level [feet] |--- used to generate levels Rate of Climb/Descent [feet/min] | Destination Aerodrome Alternate Aerodrome Second Alternate Aerodrome Other info Waypoint1 --| Waypoint2 | Waypoint3 |---------- See below for format Waypoint4 | . | Waypoint128 --|

Waypoint Not Used Latitude Longitude TurnType AirspaceType optional Notes (to EOL) Name | | | | | | | | | | | | | <---><----------------><-><-----------> <------------> <----> <--> <-----------------> OCK 11530 0 0 N51°18'18.00" W000°26'50.00" arc none OCK BOGNA 151 25 N50°42'07.00" W000°15'06.00" BOGNA BENBO 151 18 N50°27'05.00" E000°00'37.00" BENBO HAWKE 151 6 N50°22'27.00" E000°05'25.00" UMAS Example:

TN1 BA111 Primary QnQ1 20 0 0 B747 0 mlkncv EGDM 12 34 56 12 45 00 280 25000 500 EGDM EBOS EHRD other information message SID23 N51°07'26.40" W001°48'22.68" none SID KATE ENRTA N50°53'16.80" W002°55'05.88" before none ENROUTE A ENRTB N51°04'55.20" W003°00'00.00" before none ENROUTE B



A4 Blueprint Files

Configuration of the Avionics Rig software is achieved by a number of files called Blueprint Files. These reside on the development system or the hard drive of a flying system. The directory structure used is of the form:

UserSpecificId/BuildId/Dir/Filename

In the development environment, UserSpecificId will be the path to a user directory on a PC or fileserver (e.g. z:/usr/bas or c:/MA-AFAS on-site) whilst in a flying environment it will point to the hard drive (/sd0). BuildId will indicate the current build standard (e.g. build_d1) and Dir/Filename will be as shown in Table 68.

When each software module initialises, it gets its configuration data from a specific Blueprint File. The relationship between Blueprint and executable is shown in Table 69.

Directory/File Structure Description

aas_scripts cfgB.sh or cfgC.sh Configuration data for the CMU Comms partition. See A4.4.1. NOTE: Cfg B is ethernet, C is transponders (RS232)

cfgB_R1.sh or cfgC_R1.sh Configuration data for the CMU Comms partition. See A4.4.1. NOTE: Cfg B is ethernet, C is transponders (RS232), 1 is airborne and 2 is ground.

Scripts and Scenarios directories

Directory structure containing all the setup files used by the air router.

Cmu Attas.bpt See A4.2

CmuCmPart.bpt Blueprint File for the CMU Communications Manager Partition. No operator modifications necessary.

CmuDcpPart.bpt DCP configuration data including IP address for RS232 over ethernet use (See A4.1.1). Only required for BAC1-11 fit.

CmuOapPart.bpt Blueprint File for the CMU/FMU Interface. No operator modifications necessary.

CmuRollerPart.bpt Configuration data for mouse/trackball CCD. No operator modifications necessary.

GpsInterface.bpt For ATTAS use, defines the interfaces required for the Time and position data from the Aquarius GNSS to the ATTAS. See A4.1.

Comms-ConfigData AirAOCConfigurationData.txt AOC interface configuration data. See A4.4.2

cms_cfg_data.txt Context Management (CM) configuration data. See A4.4.3.

cms_script_cfg.txt CPDLC configuration data. See A4.4.4.



Directory/File Structure Description

Fmu A429InterfaceManPart.bpt ARINC 429 interfaces definition. No user modifiable data but see A4.1.4.

AircraftGuid.bpt Configuration data for the Aircraft Guidance partition; no user modifiable data.

CommsManager.bpt Blueprint file containing Comms (ATC, AOC, FIS etc) parameters. No user modifiable data.

ConflictProc.bpt Configuration data for the Conflict Processing partition; no user modifiable data.

DispManager.bpt Configuration data for the Displays Manager partition; no user modifiable data.

Fmu429ManPart.bpt Blueprint file for the aircraft data interfaces (see A 4.1.1 and A4.1.2)

FmuCmPart.bpt Blueprint File for the FMU-CMU Communications Manager Partition. No operator modifications necessary.

FmuMcduPart.bpt Blueprint file for the MCDU data interfaces (see A 4.1.1 and A4.1.2)

FmuOapPart.bpt Blueprint File for the CMU/FMU Interface. No operator modifications necessary.

NavDatabase.bpt Configuration data for the Navigation Database partition. No operator modifications necessary.

SurvDataMan.bpt Blueprint File for the Surveillance Database Manager partition. No user modifiable data.

TrajGen.bpt Configuration data for the Trajectory Generator partition. No operator modifications necessary.

Warnings.bpt Configuration data for the Warnings partition which includes the AWS (Alerts – Not currently used), ACMS and the Time Out Interfaces. See A4.1.1.

CmuResource.bpt Resource definitions file for the CMU. No user modifiable data.

FmuResource.bpt Resource definitions file for the FMU. No user modifiable data.

SystemConfig System parameters for the Avionics Rig including the IP addresses of the CMU and FMU fitted. Table 69 identifies the pre-assigned IP addresses for each rig.

Table 68. Blueprint Files



Rig FMU CMU

Rig #1 10.4.71.30 10.4.71.31

Rig #2 10.4.71.28 10.4.71.29

Rig #3 10.4.71.26 10.4.71.27

Rig #4 10.4.71.24 10.4.71.25

BAC1-11 Rig 10.4.71.32 10.4.71.33

ATTAS Rig 129.247.56.40 129.247.56.41

Table 69. Avionics Rig Processor IP Addresses

A4.1 I/O Ports Definition

A4.1.1 IP Address Modification

When the system uses ethernet to communicate to the aircraft systems, the IP address of the external system needs to be identified to the Avionics Rig. Each blueprint that requires IP data includes a NodesTable section uses the following format for the data:

BEGIN NodesTable #nodeId address #Ihtp 10.4.111.157 #IHTP on rig #3 Ihtp 10.4.111.156 #IHTP on rig #4 END NodesTable

The NodeId value is a name that ties the IP address to a connection definition. By default, a single NodeId (set to Ihtp) is used but multiple NodeId’s are possible if required. An example of this is in the Warnings.bpt where 3 separate subsystem interfaces (ACMS, AWS and Time Out to the Traffic Simulator) are defined by the blueprint. In this case, all three applications could be hosted on different machines by defining 3 different NodeIds and IP addresses.

All text preceded by a # is considered descriptive comment and does not get read by the application. Thus, in the example above, rig 4 is in use.

A4.1.2 TCP/IP Port Numbers

The following Table identifies the allocated port numbers for data transmitted via the ethernet. The direction parameter defines whether the Avionics Rig is a source or destination for the data. Note: By default, the destination equipment is the server on the link.

Port Number Usage Direction

5003 ATTAS Data Both

5005 ATTAS Time and Position Data Source

50000 MCDU Destination

50001 MCDU Source

50003 IRS Destination

50005 DADC Destination

50006 GNSS/Data Puddle Destination



Port Number Usage Direction

50007 SBAS Destination

50008 GBAS Destination

50011 Autopilot Source

50012 Autopilot Destination

50014 EMS Destination

50016 ACMS Destination

50018 AWS Source

50020 Time Output Source

50500 Slave MCDU Destination

Table 70. TCP/IP Port Numbers

A4.1.3 RS232/RS422 Port Definition

The Avionics Rig provides four RS232/RS422 serial ports. The hardware and software identification is shown in the Table below:

Software Id Hardware Id Default Baud Rate

Usage

/tyco/2 COM1 2400 CCD

/tyco/3 COM2 9600 DCP (BAC1-11), Aquarius GNSS (ATTAS)

/tyco/4 SERIAL3 - Not Used

/tyco/5 SERIAL4 19200 VDL Mode 4 Transponder

Table 71. RS232/RS422 Serial Port Definition

All physical ports are available on the front panel of the Avionics Rig, mounted on the MVME761 interface adapter.

Blueprint files allow for the allocation of a port to an application, and the definition of the speed of the port. Other parameters (e.g. number of bits) are hard coded in the application and are therefore not user alterable.

Each blueprint file that defines a serial port includes the following section:

#Definitions for serial port # Key word Port Name Port Number Baud Rate SerialPort /tyCo/ 3 9600

A4.1.4 ARINC 429 Configuration

The A429Interface.bpt file contains the configuration parameters for the ARINC 429 interfaces for the BAC1-11 fit. This data is held in a table thus:

BEGIN A429InitialiseTable #PortNumber Port Name Transmit Type Function Rate(Hz) Arinc 429 Speed Label List 2 Channel2 Rx 5 A429_SLOW EMSLabels 8 Channel8 Tx_Cyclic 5 A429_SLOW AutopilotTxLabels 10 Channel10 Rx 5 A429_FAST AutopilotRxLabels 11 Channel11 Rx 5 A429_SLOW SBASGBASLabels 12 Channel12 Rx 20 A429_SLOW DataPuddleLabels



13 Channel13 Rx 16 A429_SLOW DigitalAirDataLabels 14 Channel14 Rx 5 A429_SLOW SBASGBASLabels 15 Channel15 Rx 50 A429_FAST IRSLabels 7 Channel7 Tx_Single 333 A429_SLOW MCDUTxLabels 16 Channel16 Rx 100 A429_SLOW MCDURxLabels END

Under normal conditions there are no user modifiable parameters but this table allows the modification of the speed between SLOW (12kbps) and FAST (100kbps). Note that both ends of the link must be set to the same speed or else the link will not function.

A4.2 Blueprint File Attas.bpt

This blueprint file is only used for the ATTAS fit. It provides for identification of the Ethernet address of the ATTAS rig, the definition of the NDU views selected by the Displays Control Panel and the selection of Port or Starboard DCP.

An example of the file is shown at the end of this section. The first block of text is the standard configuration information that is in all blueprint files.

The section A3_Paramaters contains configuration data items that do not need modification so no further details will be given here.

Section ‘tcpipConnectionInfo’ identifies the TCP/IP parameters and normally does not need modification. It identifies the port number as 5003 which is set by the ATTAS (See A4.1.2).

The NodesTable section allows the setting of the IP address of the host system. This will normally be the ATTAS (129.247.58.18) but can be an IHTP address for test purposes. Note that the NodeId is ihtp – this is just a name that ties the tcpipConnectionInfo to the NodesTable (See A4.1.1).

The last section of the blueprint file, AttasDCPConfiguration, allows the customisation of the ATTAS fit with the Avionics Rig. The ATTAS control panel comprises an Autopilot control panel with two displays control panels, one either side. This is to allow each crew member to control his own Nav Display. For the MA-AFAS trials, only one display will be fitted and thus only 1 DCP will be used. The SelectedDCP parameter defines which DCP, Port or Starboard, is to be used.

Similarly, each DCP only provides a single 5 position rotary switch to control the display contents. The table at the end of this blueprint file allows the user to define what display is generated for each of the 5 switch positions. For each switch position, the following can be defined:

Parameter Range of Values Description

SwitchPosition 1,2,3,4,5 1 is fully clockwise

DisplayMode MAP, TAXI_PLAN, TAXI_MAP, PROFILE

These are defined in Section 4.1

MapMode ARC, ROSE ARC is ±45° from centreline, ROSE is 360°

ShowAirports TRUE/FALSE Enables/disables the display of Airports on the MAP

ShowNavAids TRUE/FALSE Enables/disables the display of Navaid data (type and position) on the MAP

ShowWayPoints TRUE/FALSE Enables/disables the display of entered waypoints, both on the active route and the alternate route, on the MAP

ShowAlternateRoute TRUE/FALSE Enables/disables the display of the alternate on the MAP

Table 72. DCP Rotary Switch Encoding Values



# # FILENAME : Attas.bpt # # AUTHOR : Simon Evans # # FILE VERSION : 2 # # DESCRIPTION : CMU ATTAS Blueprint File # # CHANGE HISTORY : # # Updated # Revision 2 08-11-2002 Simon Evans MB0409 # added new config parameters for ATTAS DCP # # Created # Revision 1 30-SEP-2002 Simon Evans # BEGIN A3_Parameters #Parameter Value PartitionFaultQueueName r1_fault_out NumberOfFactoryItems 10 numberOfEventItems 0 numberOfSemaphoreItems 2 numberOfBufferItems 0 numberOfBlackboardItems 0 MaxNumSamplingPorts 4 MaxNumQueuingPorts 0 #Semaphore_Name TYPE MaxValue QD ReadSem SEM 1 FIFO SendSem SEM 1 FIFO #Process_Name TYPE Base_Priority Stack_Size Period Time_Cap Proc_Type ReadATTASPort PR 48 50000 100 50 NORMAL WriteFMSData PR 48 50000 100 50 NORMAL #PortName Type Num_IPMO IPMO_1 IPMO_2 IPMO_3 IPMO_4 IPMO_5 Size Direction Refresh ATTAS_GUIDANCE_VECTOR_SP SP 1 /ATTAS_GUIDANCE_VECTOR_SP NULL NULL NULL NULL 36 destination 200 ATTAS_OUTPUT_PARAMETERS_SP SP 1 /ATTAS_OUTPUT_PARAMETERS_SP NULL NULL NULL NULL 648 source 200 FCS_CONTROL_PANEL_STATUS_SP SP 1 /FCS_CONTROL_PANEL_STATUS_SP NULL NULL NULL NULL 96 source 200 NDU_CONTROL_PANEL_STATUS_SP SP 1 /NDU_CONTROL_PANEL_STATUS_SP NULL NULL NULL NULL 32 source 1000 END A3_Parameters BEGIN tcpipConnectionInfo #TcpipNmae Connect client/Server direction nodeId portId size ATTASComms 1 client both Ihtp 5003 520 END tcpipConnectionInfo



BEGIN NodesTable #nodeId address Ihtp 10.4.111.156 #IHTP on rig #4 END NodesTable BEGIN AttasDCPConfiguration # select which DCP has control [enter PORT or STARBOARD] SelectedDCP STARBOARD # map ATTAS modes to display options #SwitchPosition DisplayMode MapMode ShowAirports ShowNavAids ShowWayPoints ShowAlternateRoute 1 MAP ROSE TRUE TRUE TRUE TRUE 2 MAP ARC FALSE FALSE TRUE TRUE 3 TAXI_PLAN ROSE FALSE FALSE FALSE FALSE 4 TAXI_MAP ARC FALSE FALSE FALSE FALSE 5 PROFILE ROSE FALSE FALSE FALSE FALSE END AttasDCPConfiguration



A4.3 Slave MCDU

A trials facility exists to use the system with a ‘real’ MCDU and also a repeater MCDU using the IHTP. This latter unit is called a Slave MCDU as it can only be used to display the pages and not be used to control the system in any way. The file FmuMcduPart.bpt includes the configuration data for the Slave MCDU as well as the ‘MCDU over ethernet’ connection.

The default configuration enables the Slave MCDU interface. Port 50500 is used by the FMU to receive the IP address(es) of the IHTP(s) used to host a Slave MCDU. Up to 3 slave MCDUs can be driven in the current build.

When the FMU receives a Slave MCDU IP Address, it sets up a connection to transmit MCDU display data which is then output to each of the active Slave MCDUs following the transmission of data to the real MCDU.

Each IHTP needs to have the MCDU Control Tx port configured as an ‘On Demand’ IHTP ethernet port with the IP address of the FMU, and the IHTP MCDU ethernet interface enabled. See the IHTP User Guide for further details.

A4.4 Comms Configuration Files

A4.4.1 File cfgB_R1.sh / cfgC_R1.sh

These files, a template of which is reproduced below, defines the required IP addresses for the Comms Air applications and scenario file required for the particular installation (Defined as AAS_INPUT_FILE). The required configuration file is called from the CMU Script file.

putenv("AAS_R1_IP={CMU IP Address}"); putenv("AAS_R2_IP={Ground Router IP Address}"); putenv("SCRIPTS={pathname}/aas-scripts/scripts"); putenv("SCENARIOS= {pathname}/aas-scripts/scenarios"); putenv("AAS_INPUT_FILE= {pathname}/aas-scripts/scenarios/maafas_cfgB_R1.inp"); putenv("AAS_RECORD_FILE=/sd0/comms/aas/cfgB_R1.out"); putenv("RAPI_LOCAL_ADDRESS={CMU IP Address}:6570"); putenv("GACS_TCPIP_ADDRESS={CMU IP Address}:9023"); putenv("BCAST_SERVER_SNPA={CMU IP Address}:9390"); putenv("BCAST_CLIENT_SNPA={FMU IP Address}:9270"); putenv("BCAST_CLIENT2_SNPA={CMU IP Address}:9271");

A4.4.2 File AirAOCConfigurationData.txt

This file resides on the Avionics Rig hard drive and identifies the operational parameters for the GACS interface. By default, the AGPNAME parameter is set to GROUNDI1 for MA-AFAS. The ADDRESS parameter is set to the CMU IP address, port 9023 and refers to the GACS socket on the CMU based air router. The AIRCRAFT parameter is TBD. The TAILNUMBER parameter is TBD.

AGPNAME= GROUNDI1 ADDRESS= {CMU IP Address}:9023 AIRCRAFT= 47 41 43 TAILNUMBER= TN1

A4.4.3 File cms_cfg_data.txt



This file resides on the Avionics Rig hard drive and contains configuration data for the Context Management facility of the Comms. Most of the data is not user modifiable but the file contains IP socket data for CM and Broadcast and the logged data filenames.

The CM and BROADCAST REMOTE_ADDRESS items (ports 6570 and 9390) should be set to the CMU address, and the BROADCAST LOCAL_ADDRESS item (port 9270) should be set to the FMU address. The CM LOCAL_ADDRESS (port 9323) is set to the local_host address and thus does not need modification between installations.

# # SECTION : General Config # GENERAL_START VER,C1 ADM,83 65 73 RDF,00 ARS,40 00 01 LOC,00 01 SYS,00 00 41 41 31 33 NSEL,01 GENERAL_END # # SECTION : CM Specific # CM_START LOCAL_ADDRESS,127.0.0.1:9323 REMOTE_ADDRESS,{CMU IP Address}:6570 CONTEXT,1 ATSC_CLASS,C TSEL,2,55 55 LOG_FILE,/sd0/comms/cm/cm_log.txt CM_GROUND_START CONTEXT,1 FACILITY,41 42 43 44 45 46 47 48 VER,81 ADM,83 47 42 RDF,00 ARS,42 45 46 LOC,00 01 SYS,32 59 00 29 03 62 NSEL,01 TSEL,2,55 55 CM_GROUND_END CM_END # # SECTION : CPDLC Specific # CPDLC_START CONTEXT,1 TSEL,2,66 66 AIR_GROUND,GROUND LOG_FILE,/sd0/comms/cpdlc/cpdlc_log.txt DOWNLINK_TRT,300 DOWNLINK_ORT,600 DOWNLINK_TT,900 DOWNLINK_CT,1200 UPLINK_ORT,600 UPLINK_TT,900 CPDLC_END #



# SECTION : Broadcast Specific # BROADCAST_START LOCAL_ADDRESS,{FMU IP Address}:9270 REMOTE_ADDRESS,{CMU IP Address}:9390 MODE,ETHERNET LOG_FILE,/sd0/comms/brdcst/brdcst_log.txt BROADCAST_END

A4.4.4 File cms_script_cfg.txt

This file repeated below, identifies the location of the CMS configuration file described in the previous section and the IP address of the CMU. It is called by the script file FmuScript.spt. Lines 2-4 define the amount of trace data that is printed to the Tornado2 FMU shell. Zero means that no information is output, 1 (as shown below) allows minimal logging and BRDCST_TRACE = 0x00000021, CM_TRACE = 0x0000003B and CPDLC_TRACE = 0x007EFF89 provide full logging. Note: Low spec PCs used for Tornado may not be able to cope with the higher levels of data logging!

Only the last parameter, CPDLC_REMOTE_ADDRESS (port 6570), requires modification between installations.

putenv("CMS_CFG_FILENAME = /sd0/comms/cms_cfg_data.txt") putenv("BRDCST_TRACE = 0x00000001") putenv("CM_TRACE = 0x00000001") putenv("CPDLC_TRACE = 0x00000001") # Only required when running CPDLC Standalone (Without CM). putenv("CPDLC_LOCAL_ADDRESS = 127.0.0.1:9323") putenv("CPDLC_REMOTE_ADDRESS = {CMU IP Address}:6570")

A4.4.5 Ground Server Configuration

Whilst not strictly an Avionics rig item, the ground server, used in testing development systems, also needs configuration in line with the aircraft installation. The ground server application is capable of being run in a UNIX or Windows environment and uses script files similar to those defined above for the Air Router.

A full explanation of the Ground Router configuration has been included in the IHTP User Manual.



APPENDIX B SCRIPT TEMPLATES

This section gives an example of the scripts used to initialise the FMU and CMU processors.

Each of the two scripts follow the same format; the first section is a standard descriptive header giving details of the file, author and change history. Following this, the environment variables for the Comms and Blueprints are set-up. The system manager is then loaded and executed, followed by the loading of all of the operational software components. Finally, each of the software components is run.

The value of the {PATH} item in the example scripts will vary between the development environment and the aircraft environment. When in development, the files will be held on PCs/Fileservers where the required filenames will be in the form C:/UserSpecificId/BuildId/Dir/filename. On the aircraft, the executable files will be on the integral hard drive. Thus the filenames will be of the form /sd0/BuildId/Dir/filename. The executable files (*.out) will be stored in the locations given in Table 73.

Executable File FMU/CMU

Location Blueprint File Name

SystemManager.VxWorks Both /bin/aaa FmuOapPart.bpt

CmuOapPart.bpt

CommsManager.VxWorks Both /bin/aaa FmuCmPart.bpt

CmuCmPart.bpt

429InterfaceManager.out FMU /bin/fmu A429InterfaceManPart.bpt

429DataManager.out FMU /bin/fmu/Arinc429

/bin/fmu/ethernet

Fmu429ManPart.bpt

MCDUDriver.out FMU /bin/fmu/Arinc429

/bin/fmu/ethernet

FmuMcduPart.bpt

WarningAndMonitoring.out FMU /bin/fmu Warnings.bpt

display_manager.out FMU /bin/fmu DispManager.bpt

navigation_database.out FMU /bin/fmu NavDatabase.bpt

CommsManager.out FMU /bin/fmu CommsManager.bpt

surveillance_database.out FMU /bin/fmu SurvDataMan.bpt

aircraft_guidance.out FMU /bin/fmu AircraftGuid.bpt

trajectory_generator.out FMU /bin/fmu TrajGen.bpt

ControlPanel.out CMU /bin/cmu/serial

/bin/cmu/ethernet

CmuDcpPart.bpt

Rollerball.out CMU /bin/cmu CmuRollerPart.bpt

ATTASInterface.out CMU /bin/cmu Attas.bpt

ATTASGPSInterface.out CMU /bin/cmu GpsInterface.bpt

Air_AAS.out CMU /bin/cmu

ConflictProc.bpt

Table 73. MA-AFAS Software Components

Note that the order of running the components within a script is not critical except for the 429 interface manager which initialises the ARINC429 hardware in the rig. This component must be started before the ARINC versions of the MCDU and 429 data manager.

When the full software suite is run, the CMU should be started first to ensure that the Air Router (server) has started before the FMU comms component (client) requires service.

Not all components are required in all cases. For example, the ATTAS Interface (in the CMU) and the ARINC 429 Data Manager (FMU) are mutually exclusive depending on the host aircraft.

B1 FMU Script Template # # FILENAME : FmuScript.spt # # AUTHOR : Simon Evans # # FILE VERSION : 3 # # DESCRIPTION : FMU Script File # # CHANGE HISTORY : # # Revision 3 27-AUG-2002 Simon Evans # Build B release # # Revision 2 28-JUL-2002 Simon Evans # Build A release # # Created # Revision 1 25-Jun-2002 Simon Evans # # # ********************************************************************** # THROUGHOUT THIS FILE, REPLACE "C:/MA-AFAS/build_e1" with value of {ZIP_DIR} # ********************************************************************** scsiBusReset # remove previous run files @rm "/sd0/ag/HistoryFile.txt" @rm "/sd0/tg/InputTrajectoryConstraints.txt" # # setup Comms environment variables < C:/MA-AFAS/build_e1/blueprints/Comms-ConfigData/cms_script_cfg.txt # # graphics test application # required to initialise graphics card # should only be a temporary fix ld < C:/MA-AFAS/build_e1/bin/fmu/bitmap exbitmap taskDelay(3*sysClkRateGet()) # Blueprints putenv("A3_BP_PATH = C:/MA-AFAS/build_e1/blueprints")

# System Manager ld < C:/MA-AFAS/build_e1/bin/aaa/SystemManager.VxWorks taskSpawn("sysMan", 40, 0, 50000, vxmain, 1, 1) taskDelay(5*sysClkRateGet()) # AAA Comms Manager ld < C:/MA-AFAS/build_e1/bin/aaa/CommsManager.VxWorks # Arinc 429 Interface Manager partition - required for ARINC use only ld < C:/MA-AFAS/build_e1/bin/fmu/429InterfaceManager.out # 429 Data Manager, Ethernet or Arinc #ld < C:/MA-AFAS/build_e1/bin/fmu/ethernet/429DataManager.out #ld < C:/MA-AFAS/build_e1/bin/fmu/arinc/429DataManager.out # MCDU Driver, Ethernet or Arinc #ld < C:/MA-AFAS/build_e1/bin/fmu/ethernet/MCDUDriver.out ld < C:/MA-AFAS/build_e1/bin/fmu/arinc/MCDUDriver.out # Warnings & Monitoring (AWS and ACMS) #ld < C:/MA-AFAS/build_e1/bin/fmu/WarningAndMonitoring.out # Displays Manager ld < C:/MA-AFAS/build_e1/bin/fmu/display_manager.out # Navigation Database ld < C:/MA-AFAS/build_e1/bin/fmu/navigation_database.out # Communications Manager #ld < C:/MA-AFAS/build_e1/bin/fmu/comms_manager.out # Surveillance Database #ld < C:/MA-AFAS/build_e1/bin/fmu/surveillance_database.out # DUMMY Surveillance Database #ld < C:/MA-AFAS/build_e1/bin/fmu/Surveillance.out # Aircraft Guidance ld < C:/MA-AFAS/build_e1/bin/fmu/aircraft_guidance.out # Trajectory Generator ld < C:/MA-AFAS/build_e1/bin/fmu/trajectory_generator.out # spawn Navigation Database partition taskSpawn("navDatabase", 40, 0, 50000, NavigationDatabase, 1, 12) taskDelay(10*sysClkRateGet()) # spawn AAA CommsManager partition taskSpawn("Comms",40,0,50000,CommsManager,1,1) taskDelay(5*sysClkRateGet()); # spawn Arinc 429 Interface Manager partition taskSpawn("429IFManager",40,0,50000,Arinc429IntMan,1,5) taskDelay(10*sysClkRateGet()) # spawn 429 Data Manager partition #taskSpawn("429Manager",40,0,50000,Arinc429Man,1,3) #taskDelay(5*sysClkRateGet())



# spawn MCDU Driver partition taskSpawn("McduInterface",40,0,50000,McduInterface,1,4) taskDelay(5*sysClkRateGet()) # Warnings & Monitoring partition #taskSpawn("WarnMon",40,0,50000,WarningMonitoringInterface,1,6) #taskDelay(5*sysClkRateGet()) # spawn Displays Manager partition taskSpawn("dispMan", 40, 0, 50000, DisplayManager, 1, 11) taskDelay(10*sysClkRateGet()) # spawn Aircraft Guidance partition taskSpawn("aircraftGuid", 40, 0, 50000, AircraftGuidance, 1, 15) taskDelay(5*sysClkRateGet()) # spawn Communications Manager partition #taskSpawn("commsMan", 40, 0, 50000, CommunicationsManager, 1, 13) #taskDelay(10*sysClkRateGet()) # spawn Surveillance Database partition #taskSpawn("survDatabase", 40, 0, 50000, VxSDBMain, 1, 14) #taskDelay(15*sysClkRateGet()) # spawn DUMMY Surveillance Database partition #taskSpawn("survDatabase", 40, 0, 50000, SurvDataManager, 1, 24) #taskDelay(5*sysClkRateGet()) # spawn Trajectory Generator partition taskSpawn("trajGenAAA", 40, 0, 50000, TrajectoryGeneratorWrapper, 1, 16) #taskDelay(3*sysClkRateGet()) # END OF FMU SCRIPT FILE

B2 CMU Script Template # # FILENAME : CmuScript.spt # # AUTHOR : Simon Evans # # FILE VERSION : 3 # # DESCRIPTION : CMU Script File # # CHANGE HISTORY : # # Revision 4 26-SEP-2002 Simon Evans # add ATTAS related partitions # # Revision 3 28-JUL-2002 Simon Evans # Build B release # # Revision 2 28-JUL-2002 Simon Evans # Build A release # # Created # Revision 1 20-Jun-2002 Simon Evans #

# ***************************************************************** # THROUGHOUT THIS FILE, REPLACE "C:/MA-AFAS" with value of {ZIP_DIR} # ***************************************************************** # # setup Comms environment variables # AAS Server < C:/MA-AFAS/build_e1/blueprints/aas-scripts/cfgC_R1.sh # Blueprints putenv("A3_BP_PATH = C:/MA-AFAS/build_e1/blueprints") # System Manager ld < C:/MA-AFAS/build_e1/bin/aaa/SystemManager.VxWorks taskSpawn("sysMan", 40, 0, 50000, vxmain, 2, 1) taskDelay(5*sysClkRateGet()) # AAA Comms Manager ld < C:/MA-AFAS/build_e1/bin/aaa/CommsManager.VxWorks # DCP interface - don't use Serial version with ATTAS (uses same serial port) #ld < C:/MA-AFAS/build_e1/bin/cmu/ethernet/ControlPanel.out #ld < C:/MA-AFAS/build_e1/bin/cmu/serial/ControlPanel.out # Rollerball interface ld < C:/MA-AFAS/build_e1/bin/cmu/Rollerball.out # ATTAS Interface ld < C:/MA-AFAS/build_e1/bin/cmu/ATTASInterface_E1+.out # ATTAS GPS Position/Time Interface ld < C:/MA-AFAS/build_e1/bin/cmu/ATTASGPSInterface.out # Load AAS Server ld < C:/MA-AFAS/build_e1/bin/cmu/Air_AAS.out # spawn AAA CommsManager partition taskSpawn("Comms",40,0,30000,CommsManager,2,1) taskDelay(5*sysClkRateGet()) #spawn DCP interface #taskSpawn("DcpInterface",40,0,30000,DcpInterface,2,3) #taskDelay(3*sysClkRateGet()) # spawn AAS Server taskSpawn("AAS",40,0,500000,AirAAS) taskDelay(30*sysClkRateGet()) # spawn Rollerball partition taskSpawn("Rollerball",40,0,30000,Rollerball,2,4) taskDelay(3*sysClkRateGet()) # spawn ATTAS Interface taskSpawn("AttasIF",40,0,50000,AttasInterface,2,5) taskDelay(3*sysClkRateGet()) # spawn ATTAS GPS Time/Position Interface taskSpawn("AttasGPSIF",40,0,50000,GpsInterface,2,6) #taskDelay(3*sysClkRateGet())



# END OF CMU SCRIPT FILE

B3 Logged Data Extraction Script # # script file which will copy log files from the MA-AFAS FMS SCSI drive # to storage defined by {pathname} # # to run enter: # <CopyLoggedData.spt # at the Tornado shell window (on the FMU, i.e. ma-afas09) # # files are copied to the folder {pathname} # # copy aircraft guidance files # ============================ @cp "/sd0/ag/HistoryFile.txt","{pathname}/HistoryFile.txt" # # copy trajectory generator files # =============================== @cp "/sd0/ag/lateralroute.txt","{pathname}/lateralroute.txt" @cp "/sd0/ag/AircraftGuidanceConstants.txt", "{pathname}/AircraftGuidanceConstants.txt" @cp "/sd0/tg/TrajectoryGeneratorConstants.txt", "{pathname}/TrajectoryGeneratorConstants.txt" @cp "/sd0/tg/InputTrajectoryConstraints.txt", "{pathname}/InputTrajectoryConstraints.txt" @cp "/sd0/tg/InputFlightPhaseTable.txt", "{pathname}/InputFlightPhaseTable.txt" @cp "/sd0/tg/InputGeneratedRouteConst.txt", "{pathname}/InputGeneratedRouteConst.txt" @cp "/sd0/tg/GeneratedTrajectoryInfo.txt", "{pathname}/GeneratedTrajectoryInfo.txt"



APPENDIX C SCRATCHPAD MESSAGES

The following Tables show the messages that may be displayed in the Scratchpad area, an explanation of the message and, if relevant, a guide as to the required operator action to rectify the cause of the message.

Message Explanation Correction Action

!ALREADY LOGGED ON An attempt has been made to perform CM LOGON but the system is already logged on.

Acknowledge the message

!ARPT NOT IN DATABASE The identifier input as an origin or destination airport has not been found in the database.

Check the input data and correct.

!DISCONTINUITY EXISTS The trajectory generator has been instructed to generate a trajectory but the route input is not continuous

Ensure that the Destination/origin runway and/or SIDs and STARs are associated with the defined waypoints. See 4.2.6.

!FUEL TOO LOW Not enough fuel to perform trajectory

Ensure FUEL WEIGHT has been entered into the system via the LOAD page.

!GPS DATE Data has been entered for UTC date but the GPS system is active

Cancel data input

!GPS UTC Data has been entered for UTC time but the GPS system is active

Cancel data input

!IFTM MESSAGE SENT

!INCORRECT FORMAT The data entered is not in the required format

Correct the entry and re-enter

!INPUT OUT OF RANGE

!INVALID ENTRY The data entered is not valid for the field

Edit the entry and re-enter

!INVALID CONSTRAINT One or more of the parameters in the LEGS or VNAV pages is incorrect and a trajectory cannot be generated

Correct the value(s) and ensure that all required fields have been populated. Re-try trajectory generation (LOAD on VNAV page)

!INVALID ALT WIN

!NO AIRPORT ENTERED Airport data was expected but not entered. (FIS data request)

Acknowledge message and enter an airport ICAO code in the required position.

!NO AIRPORT SPECIFIED

!NO REPORT SELECTED




!NO SIDS FOUND There are no Standard Instrument Departure entries in the database for the specified departure airport.

Acknowledge message

!NO SIDS FOUND FOR RWY There are no Standard Instrument Departure entries in the database for the specified runway at the departure airport.

Acknowledge message

!NO SNAG CODE ENTERED

!NO STARS FOUND There are no Standard Arrival Route entries in the database for the specified arrivals airport.

Acknowledge message

!NO STARS FOUND FOR RWY There are no Standard Arrival Route entries in the database for the specified runway at the arrivals airport.

Acknowledge message

!NOT IN DATABASE The data in the scratchpad area does not have a match in the on-board database

Edit the data and re-enter

!NOT IN ROUTE

!OUT OF RANGE The data entered has been detected as being out of range. E.g. 25 hours, 67 minutes.

Edit the data and re-enter

!ROUTE APP DIFFERS

!ROUTE SID DIFFERS

!ROUTE STAR DIFFERS

!RWY NOT IN DATABASE

!SID NOT IN DATABASE

!SPACING TOO CLOSE

!STAR NOT IN DATABASE

!TG UNDEFINED ERROR An undefined error has been trapped in the Trajectory Generator

Check input constraints and re-generate a trajectory. This includes the phase table and other constants information.

!UNDEFINED MENU An inappropriate menu selection has been made. The menu item may not yet be available or a blank menu key presed

Acknowledge message and select another Programmable Key.

!WPT NOT IN TRAJECTORY A waypoint that is not in the active trajectory has been selected for use in an ASAS manoeuvre

Edit the entry and re-try

AOC MESSAGE RECEIVED! A message has been received from the AOC via the datalink

Acknowledge the message

CLEARED




DEP APT SET TO ---- System has detected that the aircraft is at the same position as an airport. Departure airport has been entered automatically.

Acknowledge message

FAILED TO LOG ON The attempt to log on to the CPDLC Facility has not been successful.

Try to log on again

FREE TEXT MESSAGE SENT

GUIDANCE ACTIVE The Aircraft Guidance software is receiving sufficient data to commence operation

Acknowledge message

LOG ON FULL The attempt to log on to the CPDLC Facility has not been successful as there are too many users

Try to log on at a later time

CM LOG ON SUCCESSFUL The attempt to log on to the CPDLC Facility has been successful.

Acknowledge message

LOG ON TIMEOUT The attempt to log on to the CPDLC Facility has not been successful.

Try to log on again

MALFUNCTION MESSAGE SENT

NAV DB INIT - FAILED Navigation Database Initialisation has failed

Check that the correct data is available on the hard drive and is formatted correctly. The readout on the Tornado shell window for the FMU can be used to identify a failure

NAV DB INIT - SUCCESS Navigation Database function has successfully initialised

Acknowledge Message

NEW TRAJ CREATED A new trajectory has been generated using the current ROUTE and LEGS data.

Acknowledge Message

NO APT MAP AVAILABLE !

NO TRAFFIC AVAILABLE !

NOT

PASS

PASS (XX) NM BEHIND TARGET\n

PASS ABOVE TARGET

PASS ABOVE TARGET (XX) NM \n

PASS BELOW TARGET

PASS BELOW TARGET (XX) NM \n

RECOVERED TRAJECTORY

REPORT REQUEST SENT The request for FIS data has been sent to the transponder

Acknowledge message




TARGET

TRAJ GEN INIT - FAILED

TRAJ GEN TIMED OUT

TRAJ INIT - SUCCESS The Trajectory Generator process has successfully initialised

Acknowledge Message

UNKNOWN MESSAGE RECEIVED Message acknowledgement is achieved by depressing the CLR keypad button. Cleared messages are either deleted (Information messages) or added to the acknowledged messages list (all others). The messages list may be reviewed using the Message Recall page available from the INIT/REF menu.



APPENDIX D OH, AND BY THE WAY

This section is intended to house any pointers to successful use of the MA-AFAS in its many environments.

D1 System Power Up

D1.1 SBAS and GBAS

When operating in the BAC1-11 configuration, ensure that the GBAS and/or SBAS systems have been powered up and have been given enough time to initialise their UTC Date outputs to NORMAL OPERATION with valid date before powering up the FMU.

Note that if this is not done, invalid date information could be used by the MFMS which would cause Comms message validity checks to fail. This does not affect the ATTAS as manual date entry via MCDU is always required in that environment.

D2 Initialisation

D2.1 Precision Approach Setup

The Precision Approach function uses airport specific data that is held in a configuration file, not from the Navigation Database. This information must be updated to the correct runway touchdown point whenever a GBAS or SBAS glideslope capture is to be performed. The values to be updated are:

DefaultSelectedRunwayHeading in degrees, e.g. 233.0

DefaultRunwayAltitude in metres, e.g. 124.0

DefaultRunwayPositionLongitude in degrees, e.g. -1.734525

DefaultRunwayPositionLatitude in degrees, e.g. 51.16196944

The values are held in the file AircraftGuidanceConstants.txt.

Precision Approach will only be performed at Boscombe Down on RWY23 or at Rome Ciampino RWYTBD.

D2.2 Configuration File NDBconfiguration.txt

The last lines of this file hold a list of filenames of the files that define the company routes. The list can comprise any number of filenames but the list MUST be in alphanumerical order otherwise the system may not recognise the filenames. This quirk of the system will not be corrected by software modification.

D3 ATTAS System Usage

D3.1 Date

When the ATTAS system is started, the current date must be entered using the INIT/REF:DATE/TIME menu item on the MCDU before the system initialises correctly.

D3.2 Heading



The only heading data available in the ATTAS configuration is Mag (not True). This is not the default and thus has to be changed using the INIT/REF:SET UP MCDU menu item.

D4 BAC1-11 Configuration Usage

D4.1 Time Data

When the system is used with the IHTP emulating the BAC1-11, only the SBAS emulation outputs the correct time. Thus the system should be set to use the SBAS and not the default GBAS data using the INIT/REF:SET UP:NAV DATA SOURCE:SBAS MCDU menu item.

d42 - users guide for the ma-afas avionics rig...me1 2xx england tel. 01634 844400 fax. 01634 816721...

Documents