skip to content »

Experiences in validating mil std 1553 remote terminals

experiences in validating mil std 1553 remote terminals-82

Taken directly from the MIL-STD-1553 Multiplex Applications Handbook, Section II provides you with a complete copy of MIL-STD-1553 for your reference, and, a section-by-section interpretation of the rationale behind the various paragraphs in the standard.Plus, for your ongoing reference requirements, copies of Notices 1 and 2 to MIL-STD-1553B, as well as the Production Test Plan and Validation Test Plan are presented in Sections III through VI.

experiences in validating mil std 1553 remote terminals-65experiences in validating mil std 1553 remote terminals-32experiences in validating mil std 1553 remote terminals-83

Supporting documents such as the MIL-STD-1553 Multiplex Applications Handbook, the RT Validation and Production Test Plans, and DDC’s MIL-STD-1553 Designer’s Guide, have positively influenced the standard’s worldwide familiarity and acceptance.The interface to MIL-STD-1553 enables you to connect your MIL-STD-1553 network directly to the real-time application running on the d SPACE processor board.It supports the DS1006 and DS1007 Processor Boards, and is also multiprocessor-capable.As time and the popularity of the standard progressed, standardized components (sometimes available from multiple sources) started to become available.More important though, the experience in testing and integrating 1553 systems has led to the generation of a series of standardized test plans to support these requirements.The interface to MIL-STD-1553 connects a modular d SPACE real-time system to a MIL-STD-1553 network.

It is used in hardware-in-the-loop (HIL) simulation and rapid control prototyping (RCP) to test and develop control systems that use MIL-STD-1553.

The primary goal of the 1553B was to provide flexibility without creating new designs for each new user.

The basic difference between the 1553A and 1553B revisions is that in the latter, the options are defined rather than being left for the user to define as required.

The purpose of any form of testing is to determine the quality or functional capability of an item.

In the testing of 1553 devices, the purpose of the test procedure is to verify that the design does meet the 1553 specifications and that the options implemented have been done so correctly.

Focused on meeting the needs of hardware and software design engineers confronted with 1553/1760/1773 interface and/or test requirements, DDC is pleased to publish and provide you with this sixth edition of the Designer’s Guide for the MIL-STD-1553 community.