Users Manual

ALL
EFFECTIVITY
© Honeywell International Inc. Do not copy without express permission of Honeywell.
Page 5-49
22 Apr 2019
23-15-49
SYSTEM DESCRIPTION, INSTALLATION, AND MAINTENANCE MANUAL
ASPIRE-400
(b) ARINC 429 MCDU 3 receive interface is enabled.
AND
(c) SSM of Label 272 is NOT set to either normal (NO) or functional test (FT) on
ARINC 429 “Data from MCDU 1” interface for at least 3 consecutive labels.
AND
(d) SSM of Label 272 is NOT set to either normal (NO) or functional test (FT) on
ARINC 429 “Data from MCDU 2” interface for at least 3 consecutive labels.
AND
(e) SSM of Label 272 is set to normal (NO) or functional test (FT) on ARINC 429
"Data from MCDU 3" interface for at least 3 consecutive labels.
(8) The ACD uses Label 272 received from ARINC 429 "Data from MCDU 3" interface.
(9) The ACD executes on the content of Label 272 on the selected ARINC 429 MCDU
interface only when the SSM is set to normal (NO) for at least 3 consecutive labels.
(10) Although Label 350o Maintenance Word #1 may be present with a period of 50 ms to 250
ms on receive MCDU interfaces there is no necessity to process it.
I. MCDU ARINC 739 Protocol
(1) Intercommunication between the SDU and MCDUs specified below is consistent with the
messaging protocol of ARINC 739 section 3.7. ARINC 739A does not add any changes
that impact the protocol to the SDU.
(2) If ORT indicates MCDU, the ARINC 739 protocol for pilot display and control information
transfer is supported using:
(a) The appropriate SDU 1 or SDU 2 SAL for received words;
(b) Transmitted words to any of the following MALs of 220o, 221o, 222o, and 230o.
NOTES:
1 MCDU protocol timing is not bus speed dependent.
2 This implementation does not fix a MAL to a physical MCDU interface.
(3) If the ORT indicates a MCDU controller type, upon receipt of a push button word with a
push button code of 6F, the ACD acknowledges the word with a period of less than 200
ms.
J. CMU Interfaces
(1) This section describes Intercommunication between the SDU and Communications
Management Units (CMUs) on ARINC 429 data busses.
(2) ARINC 741 P2 section 4.7 details the expected SATCOM behavior with ARINC 758
CMUs which support ACARS on Williamsburg V1. This protocol is also documented in
ARINC 429 Part 3 section 2.0.
(3) Additional/different requirements are expected to emerge as this interface is modified to
handle ATN as well as ACARS on Williamsburg V3. Williamsburg V3 is documented in
ARINC 429 P3 section 3.
(4) If the "Data from CMU 2" interface is enabled by ORT, the ACD selects the active CMU
from two CMUs in an Active/Standby configuration.
DRAFT
3rd rvw Draft as of:
29 January, 2020