ARINC 739A:1996

ARINC 739A:1996 Multi-purpose Control And Display Unit Consists of the original ARINC 739 definition with enhancements to allow it to be logged on to up to two systems at one time. Alternate form factors are included to allow the MCDU to be introduced int

More details

Download

PDF AVAILABLE FORMATS IMMEDIATE DOWNLOAD
$129.36 tax incl.

$294.00 tax incl.

(price reduced by 56 %)

1000 items in stock

Table of Contents

1.0INTRODUCTIONANDDESCRIPTION
1.1PurposeofThisDocument
1.2Functions
1.3SystemDescription
1.4Interchangeability
1.4.1General
1.4.2InterchangeabilityDesiredforthe
ARINC739AMCDU
1.4.3"GenerationInterchangeability"Consideration
1.5RegulatoryApproval
1.6RelationshiptoARINC739
2.0INTERCHANGEABILITYSTANDARDS
2.1Introduction
2.2FormFactor
2.3EnvironmentalConditions
2.4Interwiring
2.5ThermalInterfaceandDesign
2.6PowerCircuitry
2.6.1PrimaryPowerInput
2.6.2PowerControlCircuitry
2.6.3TheCommonGround
2.6.4TheACCommonCold
2.7Weights
2.8GroundingandBonding
3.0MCDUDESCRIPTION
3.1General
3.2Display
3.3Keyboard
3.3.1BasicFunctionKeys
3.3.2SpecificFunctionKeys
3.3.3Alpha-NumericKeys
3.3.4PanelIlluminationandAnnunciatorLights
3.4MCDUOperationandDisplay
3.4.1TypicalMCDUInitiation
3.4.2MCDUMenu
3.4.3SubsystemSpecificMenu
3.4.4Non-MenuOperation
3.4.5ScratchpadandDataFieldEntry
3.4.6ClearingDataFields
3.4.7Exiting
3.4.8ProposedPhilosophytoMenuStepping
3.5MCDUOutputs
3.6MCDUInputs
3.7SystemCommunication
3.7.1SubsystemandMCDUIdentification
3.7.2MenuGeneration
3.7.2.1InitialMenu
3.7.2.1.1AddressingandResponses
3.7.2.1.2ProtocolTimingandResponses
3.7.2.2MenuChanges
3.7.2.3AlternateMenuDisplay
3.7.3DataCommunication
3.7.3.1SubsystemInitiatedMessages
3.7.3.1.1SubsystemsNotCurrentlyActive
3.7.3.1.2ActiveSubsystems
3.7.3.2MCDUCommunicationwithInactiveSubsystem
andDataRequest
3.7.3.3MessageTransfer
3.7.3.4Control(CNTRL)Word
3.7.3.5DataWord
3.7.3.6Background/VectorWords
3.7.3.7DiscreteWord
3.7.3.8ButtonPushWord
3.8Built-InTestEquipment(BITE)
3.8.1BITEConsiderations
3.8.2BITEDisplay
3.8.3Self-Test
3.9ElectronicFlightInstrumentSystemInterface
3.9.1MCDUOutputstoEFI
3.9.2MCDUInputsfromEFI
3.9.3MCDUMapInputsfromFMC
3.9.4FlightPlansandGuidance
3.9.5MapDisplayEditArea
3.9.6BackgroundDataPrioritizing
3.9.7DataTypeWordFormats
3.9.8FlightPlanRetention
4.0NAVIGATIONANDDISPLAYCONTROL
4.1Introduction
4.2FunctionalRequirements
4.2.1SystemSelectionandControl
4.2.2NavigationRadioTuning
4.2.2.1ModeSelection
4.2.2.2GeneralOperation
4.2.2.3NavigationTuningPageFunctions
4.2.2.3.1TuningInhibit
4.2.2.4InterfaceRequirements
4.2.3StandbyNavigation
4.2.3.1ModeSelection
4.2.3.2Operation
4.2.3.2.1General
4.2.3.2.2NavigationandGuidance
4.2.3.2.3CDUPageAccess
4.2.3.2.4NavigationComputations
4.2.3.2.5MapDisplay
4.2.3.3InterfaceRequirement
4.2.4AlternateEFISControl
4.2.4.1General
4.2.4.2PageAccess
4.2.4.3Interface
4.2.5AlternateEICASControl
4.2.5.1General
4.2.5.2PageAccess
4.2.5.3Interface
4.2.6SystemCommunication
4.2.6.1Inter-system
4.3HardwareRequirements
4.3.1General
4.3.2InterwiringDefinition
4.4StandbyNavigationLateralGuidance
ATTACHMENTS
1StandardInterwiring
2AddressLabels
3DigitalWordFormats
4CharacterCodeAssignments
(DerivedfromISONo.5)
5EnvironmentalTestCategories
6TypicalSystemConfiguration
7TypicalFrontPanelLayout
8Glossary
9OptionalMCDUFunctions
10MCDUDisplayConsiderations

Abstract

Consists of the original ARINC 739 definition with enhancements to allow it to be logged on to up to two systems at one time. Alternate form factors are included to allow the MCDU to be introduced into a wide variety of airframes candidate for CNS/ATM upgrade.

Contact us