Hello. Sign In
Standards Store


2010 Edition, November 15, 2010

Complete Document


Includes all amendments and changes through Supplement 3, November 15, 2010

View Abstract
Product Details
Document History

Detail Summary

Active, Most Current

Price (USD)
Single User
In Stock
PDF + Print
In Stock
$604.80 You save 20%
Add to Cart

People Also Bought These:

IEC 60825-1
IEC 60721-3-3

Product Details:

  • Revision: 2010 Edition, November 15, 2010
  • Published Date: November 15, 2010
  • Status: Active, Most Current
  • Document Language: English
  • Published By: ARINC Industry Activities (ARINC)
  • Page Count: 204
  • ANSI Approved: No
  • DoD Adopted: No

Description / Abstract:

Purpose of This Document

This document contains the physical form and fit dimensions, the electrical interface definition, and a description of the functions, operations, and interfaces of the Communications Management Unit (CMU) Mark 2.

The CMU Mark 2 is used to provide management and access to the various datalink networks and services available to the aircraft. The CMU Mark 2 may also host various applications related to datalink, including both Company and Air Traffic Services. A brief white paper on the role of the CMU Mark 2 in Communications, Navigation, and Surveillance/Air Traffic Management (CNS/ATM) is provided in Appendix A.

The CMU Mark 2 is defined in terms of capability levels. There are two classes of capabilities, Levels 0 through 2 define communications service capabilities. Levels A through D defines application capabilities, see Section 4.1. The CNS/ATM definition is still in progress.

The CMU levels 0 and A definition has been completed. Future supplements will complete the definition of the other levels. The text for levels 1 through 2 and levels B through D is preliminary.

This document assumes that the architecture of the airborne CMU Mark 2, is as shown in the system block diagrams included as attachments. These architectures are consistent with guidelines provided by ARINC Report 660A: CNS/ATM Avionics, Functional Allocation and Recommended Architectures.