DID FinderBack
Source
DI-MISC-80343

Multiplex Interface Control Document (MICD)

The Multiplex Interface Control Document (MICD) establishes the requirements for the transfer of data and details the electrical interfaces, hardware, and software for various equipments that employ one or more MIL-STD-1553B multiplex bus(es).

Approval DateApril 17, 1987
AMSC NumberA4099
Preparing Activity—
Project Number—
OPRA/AVSCOM
DTIC ApplicableNo
GIDEP ApplicableNo
Limitation—
Applicable Forms—
Approval Limitation—
Form VersionJUN 86
DID Formatdd_form_1664
963C CompliantNo
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Supersedes
—
Related
—

Description & Purpose

3.1 The Multiplex Interface Control Document (MICD) establishes the requirements for the transfer of data and details the electrical interfaces, hardware, and software for various equipments that employ one or more MIL-STD-1553B multiplex bus(es).

Application & Interrelationship

7.1 This DID contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

7.2 This DID is applicable to systems and subsystems which provide MIL-STD-1553B interfaces as the basic input and output communication interface.

Use & Relationship

—

Preparation Instructions

1Reference documents.The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
2General.The Multiplex Interface Control Document (MICD) identifies, defines, and controls electrical and physical interfaces related to the multiplexing of data and the transmission of multiplexed data over a MIL-STD-1553 data bus. Message structure and data word formats are to be standardized and controlled by the MICD.
3Title page.The title page sample format is illustrated in Figure 1.
4Message/data word formats.Message structure and data word format shall be as depicted on the standardized sheets detailed in Section 80 of MIL-HDBK-1553.
5MICD outline.The MICD shall be in the sample outline and paragraph numbering depicted in Figure 2. The MICD shall be on 8 1/2 x 11 inch sheets and shall incorporate the following content and format requirements:
5.1Introduction
5.1.1PurposeThis section establishes the requirements for the transfer of data over a MIL-STD-1553 data bus and identifies the systems or subsystems involved, in general terms (e.g., Ultra-High Frequency (UHF) radio and other on-board systems).
5.1.2ResponsibilityThis section identifies the Government agency that is the custodian of the MICD and that is the point-of-contact for comments, changes, or additional copies.
5.1.3ScopeThis section describes the boundaries or the extent of the interfaces included in the MICD.
5.1.4Functional Summary
5.1.4.1Unit Functional Summary.This section describes the unit for which this interface is being defined. This description includes the basic functions performed and the modes of operation. (For a System MICD, a Functional Summary for each unit shall be included.)
5.1.4.2Control Display Unit (CDU) Functional Summary.This section, if applicable, describes the control functions and display functions required in conjunction with the unit's operation. This section shall not define the implementation of these functions or whether the CDU is a stand-alone or integrated CDU. The CDU display page formats are not included. (For a System MICD, a Control Display Unit Functional Summary, for each unit which interfaces with the CDU, shall be included.)
5.1.5Notes
5.1.5.1Glossary.
5.1.5.2Definitions.
5.2Applicable DocumentsThis section provides a listing of publications, instructions, specifications, standards, and other documents applied to or used in the preparation of the MICD. This list includes the document number, title, and date. The documents shall be listed in the following order: If conflicts or incompatibilities exist between documents, then a brief description of the conflict or incompatibility shall be included along with the rationale for establishing the precedence of one document (or requirement) over another.
5.2.1Armed Forces Publications (Army, Navy, Air Force, etc.)
5.2.2Government Standards and Specifications (MIL-STD, etc.)
5.2.3Commercial Standards (ANSI, IEEE, SAE, etc.).
5.2.4Commercial Publications (any publications not generated by the above agencies.)
5.3Interface Requirements
5.3.1Physical Characteristics.This section defines any physical or electrical characteristics beyond the scope of MIL-STD-1553 ((e.g., Remote Terminal (RT) address selection method, or coupling method)).
5.3.2Protocol.This section defines any protocol requirements which are beyond the scope of MIL-STD-1553 (e.g., mode codes). This section also describes protocol features as message subaddress assignments, error processing and recovery functions, major and minor frame timing constraints (including duty cycle), and status and validity bit usage.
5.3.3Interface Diagrams.This section includes an overview of the interface in the form of the following block diagram: Note 1: Message Format as defined in Section 80 of MIL-HDBK-1553 Multiplex Applications Handbook.
5.3.4System Conventions.This section of the MICD describes any system conventions specific to the system (e.g., aircraft body coordinates).
5.4Message DescriptionsThis section subdivides into two subsections: Receive Messages and Transmit Messages. Within each subsection, messages are to be ordered by alphabetizing the message identification (sort on source and source subaddress within the message ID).
5.4.1Receive Messages.This section describes the set of messages received by the unit. (For a System MICD, messages received by each unit shall be included.) Each message shall be described as follows:
5.4.1.1The overview of the message shall be depictedThe overview of the message shall be depicted and the MIL-STD-1553 message structure provided (a tabular listing of all command, status, and any data words, including word name, word number, description, and the page number where the detailed description for that word can be found); a message description briefly characterizing the message and clarifying its use; transmission criteria (the rate at which the message is to be transmitted on the bus and any restrictions to that criteria); and the message functional or structural relationship (i.e., any cause/response interactions imposed on the system due to the message, such as a hardware/software action in response to a mode code).
5.4.1.2Following the message overview is a detailed descriptionFollowing the message overview is a detailed description of each word in the MIL-STD-1553 message using the format described in Section 80 of MIL-HDBK-1553 Multiplex Applications Handbook. (For a System MICD, detailed descriptions of data words need not be repeated for identical messages. The data words should be cross-referenced on identical messages).
5.4.2Transmit Messages.This section describes the set of messages transmitted by the unit. (For a System MICD, messages transmitted by each unit shall be included.) The format of this section is the same as the format in 10.5.4.1.

References

—

Figures

Figure Table 1: Functional Block Diagram

Figure Table 1. Functional Block Diagram

Figure 1: Multiple Interface Control Document Title Page Sample

Figure 1. Multiple Interface Control Document Title Page Sample

Figure 2: Multiplex Interface Control Document Outline Sample

Figure 2. Multiplex Interface Control Document Outline Sample

Schema v3.0Community-maintained · Verify against ASSIST
Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer