-Waypoint position defined in the NAV data base is within the edit area and
-The waypoint is not a flight plan waypoint (including the reference fix(es) of the FIX INFO page) or the active waypoint and
-
If a terminal range is selected the waypoint must be classified as terminal or terminal/enroute and
-
If an enroute range is selected the waypoint must be classified as enroute or terminal/enroute.
(2)
Navaids (VOR.D) When the VOR.D pushbutton switch option is selected, all NAV data base VOR and/or DMEs and all stored navaids that meet the following criteria are transmitted as map background data. Navaid position defined is within the edit area and the navaid is one of the following types:
-VOR only
-DME only
-TACAN
-VORTAC
-Collocated VOR/DME
-
Non-Collocated VOR/DME
-
Non-Collocated VOR/TAC
-ILS/DME
-MLS/DME
The navaid is not selected to be output as a "tuned navaid".
(3)
Non Directional Beacons (NDB) When the NDB pushbutton switch option is selected, all NDBs in the NAV data base and all stored NDBs that lie within the defined edit area are transmitted as map background data.
(4)
Airports (ARPT) When the ARPT pushbutton switch option is selected, all airports in the NAV data base and all stored airports that meet the following criteria are transmitted as map background data.
-
The airport position defined in the NAV data base is within the edit area and
-
The airport is not the origin or destination airport.
(5)
Waypoint constraints (CSTR) When the waypoint CSTR pushbutton switch option is selected, all speed, altitude and time constraints for all flight plan waypoints excluding the FROM waypoint are transmitted as map background data. Note that navaids, airports, and non directional beacons may also be waypoints in the flight plan. Therefore, constraints will be displayed for these. If an altitude window constraint exists, both altitudes are displayed with the AT OR BELOW constraint displayed directly above the AT or ABOVE constraint. In addition, when the waypoint constraints pushbutton is selected and a CMS is defined in the F-PLN being displayed, the Constant Mach is transmitted as map background data for all the CMS waypoints. If a speed constraint and a Constant Mach apply to a same waypoint, the Constant Mach (Format.XX) is displayed under the speed constraint value. Grid MORA data are also displayed when the waypoint constraints option is selected. Grid MORA is only displayed on the enroute scales as dynamic data.
DATA LINK AND PRINTER FUNCTIONS - DESCRIPTION AND OPERATION
___________________________________________________________
1. General
_______
A. Aircraft Communication Addressing and Reporting System (ACARS) Through the ACARS, the Flight Management (FM) section is able to send information or requests to the ground and in turn receive information or requests from the ground, for information. The ACARS functions are divided into different categories:
-uplink messages: reception of data allowing flight plan, takeoff and wind data initializations, or requests for downlink reports sent by the ground station
-downlink messages: sending of flight reports or requests to the ground
station for data initialization. The ACARS function is enabled via two discretes. One is a discrete input received through a program pin (ACARS option installed). The other is the Datalink enable option within the Nav data base airline policy file (Ref. Para. 2-D : ACARS Programming Options). The ACARS function is available only if both of these discretes are in their 'enabled' state. If either discrete is 'disabled', then all of the ACARS functions are inhibited, dedicated ACARS prompts are not displayed and ACARS specific pages cannot be reached. The interface protocol with the ACARS Management Unit (MU) is based on ARINC 429, ARINC 619 and ARINC 702 Specifications.
B. Printer
Two kinds of ACARS information can be printed:
-FMGC-generated information: flight plan initialization, takeoff data, wind data and flight reports
-ACARS-generated information: flight plan initialization, takeoff data,
wind data. These reports are described in Para 2-B. The interface protocol with the printer is based on ARINC 740 Specification.
2. System Description
__________________
A. ACARS Functions
(1) General description
The different ACARS functions are:
-flight plan initialization data An uplink message answering a manual request, or automatically sent by the ground. The crew may send a request for flight plan data to the ground indicating the flight number and/or the company route. In response to this request, or automatically, the ground sends a flight plan and associated performance data to the aircraft. 中国航空网 www.aero.cn 航空翻译 www.aviation.cn 本文链接地址：A320飞机维护手册 AMM AUTO FLIGHT 自动飞行4(56)
