SAE AS 4114-1989 PRODUCTION TEST PLAN FOR THE TIME DIVISION COMMAND RESPONSE MULTIPLEX DATA BUS BUS CONTROLLERS《时分制指令 响应型多路传输数据总线控制器的生产试验计划》.pdf

《SAE AS 4114-1989 PRODUCTION TEST PLAN FOR THE TIME DIVISION COMMAND RESPONSE MULTIPLEX DATA BUS BUS CONTROLLERS《时分制指令 响应型多路传输数据总线控制器的生产试验计划》.pdf》由会员分享，可在线阅读，更多相关《SAE AS 4114-1989 PRODUCTION TEST PLAN FOR THE TIME DIVISION COMMAND RESPONSE MULTIPLEX DATA BUS BUS CONTROLLERS《时分制指令 响应型多路传输数据总线控制器的生产试验计划》.pdf（34页珍藏版）》请在麦多课文档分享上搜索。

1、AEROSPACESTANDARDAS4114Issued 1989-01PRODUCTION TEST PLAN FOR THE TIME DIVISION COMMAND/RESPONSE MULTIPLEX DATA BUS BUS CONTROLLERSTABLE OF CONTENTSPARAGRAPH TEST PAGE1. SCOPE 51.1 General 51.2 Application 52. APPLICABLE DOCUMENTS 52.1 Standards, Military 52.2 Other Documents 53. DEFINITIONS 63.1 Me

2、ssage 63.1.1 CMS - Command Message Segment 63.1.2 SMS - Status Message Segment 63.2 Bus Conditions 63.2.1 CS - Clear Status 63.2.2 NR - No Response 63.2.3 ISMS - Invalid Status Message Segment 63.2.4 VSMS - Valid Status Message Segment 63.3 Other Definitions 63.3.1 VW - Valid Word 63.3.2 UUT - Unit

3、Under Test 73.3.3 BC - Bus Controller 73.3.4 RT - Remote Terminal 73.3.5 MCX - Mode Code 73.3.6 DBACC - Dynamic Bus Control Acceptance Bit 74. GENERAL TEST REQUIREMENTS 74.1 General Monitoring Requirements 7Reaffirmed 2011-11RATIONALEThis document has been reaffirmed to comply with the SAE 5-year Re

4、view policy. SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement ar

5、ising therefrom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions.Copyright 2011 SAE International All rights reserved. No part

6、 of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 7

7、24-776-4970 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/AS4114Copyright SAE International Provided by IHS under license with SAE

8、Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-AS4114Page 2TABLE OF CONTENTS(Continued)PARAGRAPH TEST PAGE5. DETAILED REQUIREMENTS 85.1 Electrical Tests 85.1.1 Output Characteristics 85.1.1.1 Amplitude 85.1.1.2 Rise Time/Fall Time 85.1.1.3 Zero Crossing Stability

9、85.1.1.4 Distortion, Overshoot, and Ringing 85.1.1.5 Output Symmetry 95.1.1.6 Output Noise 95.1.1.7 Power On/Off Noise 95.1.2 Input Characteristics 95.1.2.1 Input Waveform Compatibility 105.1.2.1.1 Zero Crossing Distortion 105.1.2.1.2 Amplitude Variations 105.1.2.1.3 Rise and Fall Time 105.1.2.1.3.1

10、 Trapezoidal 105.1.2.1.3.2 Sinusoidal 105.1.2.2 Input Impedance 115.2 Protocol Tests 115.2.1 Required Bus Controller Operation 115.2.1.1 Command Vocabulary Verification 115.2.1.2 Identification of Correct Address Field in Response 115.2.1.2.1 Correct Address Field With Controller-Remote Terminal Mes

11、sage Transfers 115.2.1.2.2 Correct Address Field With RT-RT Message Transfers 125.2.1.3 Minimum Response Time 125.2.1.3.1 Minimum Response Time: BC-RT Transfers 125.2.1.3.2 Minimum Response Time: RT-RT Transfers 125.2.1.4 Minimum No-Response Time-Out 135.2.1.4.1 Minimum No-Response BC-RT Transfer 13

12、5.2.1.4.2 Minimum No-Response Time-Out: RT-RT Transfers 135.2.1.5 No-Response Time-Out 135.2.1.5.1 No-Response Time-Out: BC-RT Transfers 135.2.1.5.2 No-Response Time-Out: RT-RT Transfers 135.2.1.6 Error Injection: BC-RT/RT-BC 145.2.1.6.1 Parity 145.2.1.6.1.1 Status Word Validation for Transmit Comma

13、nds 145.2.1.6.1.2 Status Word Validation for Receive Commands 145.2.1.6.1.3 Data Word Validation 145.2.1.6.2 Word Length 155.2.1.6.2.1 Status Word Validation for Transmit Commands 155.2.1.6.2.2 Status Word Validation for Receive Commands 155.2.1.6.2.3 Data Word Validation 155.2.1.6.3 Bi-Phase Encodi

14、ng 165.2.1.6.3.1 Status Word Validation for Transmit Commands 165.2.1.6.3.2 Status Word Validation for Receive Commands 165.2.1.6.3.3 Data Word Validation 16Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IH

15、S-,-,-AS4114Page 3TABLE OF CONTENTS(Continued)PARAGRAPH TEST PAGE5.2.1.6.4 Sync Encoding 175.2.1.6.4.1 Status Word Sync Validation 175.2.1.6.4.2 Data Word Sync Validation 175.2.1.6.5 Response Message Length 175.2.1.6.5.1 Response to Receive Command 175.2.1.6.5.2 Response to Transmit Commands 185.2.1

16、.6.6 Discontiguous Data 185.2.1.7 Error Injection: RT to RT Transfers 185.2.1.7.1 Parity 195.2.1.7.1.1 Status Word Validation for Responses to RT to RT Transmit Commands 195.2.1.7.1.2 Status Word Validation for Responses toRT to RT Receive Commands 195.2.1.7.1.3 RT to RT Data Word Validation 195.2.1

17、.7.2 Word Length 195.2.1.7.2.1 Status Word Validation for Responses toRT to RT Transmit Commands 205.2.1.7.2.2 Status Word Validation for Responses toRT to RT Receive Commands 205.2.1.7.2.3 Data Word Validation 205.2.1.7.3 Bi-Phase Encoding 215.2.1.7.3.1 Status Word Validation for Responses toRT to

18、RT Transmit Command 215.2.1.7.3.2 Status Word Validation for Responses toRT to RT Receive Commands 215.2.1.7.3.3 Data Word Validation 215.2.1.7.4 Sync Encoding 225.2.1.7.4.1 Status Word Sync Validation for Response to RT to RT Transmit Commands 225.2.1.7.4.2 Status Word Sync Validation for Response

19、to RT to RT Receive Commands 225.2.1.7.4.3 Data Word Sync Validation 235.2.1.7.5 Response Message Length 235.2.1.7.5.1 Message Length Validation for RT to RT Transmit Commands 235.2.1.7.5.2 Message Length Validation for RT to RT Receive Commands 245.2.1.7.6 Discontiguous Data 245.2.2 Optional Operat

20、ion 245.2.2.1 Mode Commands 245.2.2.1.1 Dynamic Bus Control 245.2.2.1.2 Mode Commands Without Data Words 255.2.2.1.3 Transmit Mode Commands With Data Words 255.2.2.1.4 Receive Mode Commands With Data Words 255.2.2.2 Status Word 255.2.2.2.1 Status Bits, Receive Commands 255.2.2.2.2 Status Bits, Trans

21、mit Commands 255.2.2.2.3 Status Bits, RT to RT Commands, Transmitter Status 26Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-AS4114Page 4TABLE OF CONTENTS(Continued)PARAGRAPH TEST PAGE5.2.2.2.4 Stat

22、us Bits, RT to RT Commands, Receiver Status 265.2.2.2.5 Status Bits, Mode Command 265.2.2.3 Broadcast Command 265.2.2.3.1 Broadcast Receive Commands 265.2.2.3.2 Broadcast Receive Command With Response 265.2.2.3.3 Broadcast RT-RT Command 265.2.2.3.3.1 Broadcast RT-RT Command With No-Response 275.2.2.

23、3.3.2 Broadcast RT-RT Command With Response 275.2.2.3.3.3 Normal Broadcast RT-RT Command 275.2.2.3.4 Broadcast Mode Commands 275.2.2.3.5 Broadcast Mode Command With Response 275.2.2.4 Response On Alternate Bus 27LIST OF TABLESTABLE TITLE PAGE1 Mode Codes 28LIST OF FIGURESFIGURE TITLE PAGE1A General

24、Resistor Pad Configuration 291B General Bus Configuration 292 Waveform Measurements 303 Zero Crossing Interval Measurements 314 Output Noise Configuration 325 Gap Time Measurement 33LIST OF APPENDICESAPPENDIX TITLE PAGEA Test Plan Changes forMIL-STD-1553B, Notice 2 BCs 34Copyright SAE International

25、Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-AS4114Page 51. SCOPE:This test plan consists of two major sections for the production testing of bus controllers: Electrical tests and Protocol tests.1.1 General: This production

26、test plan defines the test requirements for determining that bus controllers meet the requirements of MIL-STD-1553B, “Digital Time Division Command/Response Multiplex Data Bus.“1.2 Application: This is a general test plan for any bus controller designed to meet the requirements of MIL- STD-1553B. Th

27、ese requirements shall apply to the bus controller under test, when invoked in a specification or statement of work.The primary intent of this test plan is to test those requirements of MIL-STD-1553 for bus controllers that have been implemented in hardware, software, or firmware. However, it is rec

28、ognized that some additional software may be required to meet this intent and that this software may be the operational software (or some portion thereof), special test software, or some combination of these.Tests specified may be performed in any order, combined with one another, or combined with o

29、ther tests of the subsystem in which the bus controller may be embedded.The bus controller which is under test must also have had its design validated per the “Validation Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Bus Controllers.“ This document deals only with bus c

30、ontroller functions which are explicitly described in MIL-STD-1553B. This document does not specify tests that check the integrity of data from the subsystem to the bus, nordoes it attempt to address the system test requirements.Special requirements such as those needed to meet armament bus requirem

31、ents when specified in theindividual equipment specification may, when within 1553B requirements, replace values or tolerances specified in this test plan for the purpose of generating a UUT production test procedure.2. APPLICABLE DOCUMENTS:2.1 Standards, Military: MIL-STD-1553B, 21 Sep 1978 “Aircra

32、ft Internal Time Division Command/Response Multiplex Data Bus,“ with Notice 2, 8 September 1986.2.2 Other Documents: SAE Aerospace Standard, AS 4113, “Validation Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Bus Controllers.“Copyright SAE International Provided by IHS u

33、nder license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-AS4114Page 63. DEFINITIONS:3.1 Message: A single message is the transmission of a command word, status word, and data words if they are specified. For the case of a remote terminal to remote termi

34、nal (RT to RT) transmission, the message shall include the two command words, the two status words, and data words. All messages are divided into two message segments: a command message segment and a status message segment.3.1.1 CMS - Command Message Segment: A command message segment consists of a

35、command word and associated data words, if any. In the case of RT to RT transfer, the command message segment includes both the receive command word and the transmit command word.3.1.2 SMS - Status Message Segment: A status message segment consists of a status word and associated data words, if any.

36、 In the case of RT to RT transfer, the status message segment includes the status word of the transmitting RT, its associated data words, and the status word of the receiving RT.3.2 Bus Conditions: The following are definitions of bus conditions that bus controllers are required to detect. A descrip

37、tion of the actual signal, state, or action taken within the bus controller, which is used during test procedures to indicate the detection of each of the following bus conditions, shall be attached to the test results. Bus controller states may or may not be distinguishable, that is, a single bus c

38、ontroller signal may indicate both NR and ISMS.3.2.1 CS - Clear Status: The status word may have the busy bit or service request bit set, or both. The status word shall have the correct terminal address, all other status code bits in the status word must be zero and the associated message segment mu

39、st have the proper word count.3.2.2 NR - No Response: A no response condition occurs if a bus controller determines that there has been no response to a command.3.2.3 ISMS - Invalid Status Message Segment: An ISMS condition occurs within a bus controller when it determines that an SMS is not a VSMS.

40、3.2.4 VSMS - Valid Status Message Segment: A VSMS condition occurs within a bus controller when it determines that an SMS contains only a CS, a valid status word, and valid data words, that the data words are contiguous to the status word and each other, and that the response time is as specified in

41、 MIL-STD-1553.3.3 Other Definitions:3.3.1 VW - Valid Word: A valid word conforms to the following minimum criteria:a. The word begins with a valid sync field.b. The bits are in a valid Manchester II code.c. The information field has 16-bits plus parity.d. The word parity is odd.Copyright SAE Interna

42、tional Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-AS4114Page 73.3.2 UUT - Unit Under Test: For the purposes of this test plan, UUT refers to the bus controller under test.3.3.3 BC - Bus Controller: As defined in the paragr

43、aph titled Bus Controller of MIL-STD-1553.3.3.4 RT - Remote Terminal: As defined in the paragraph titled Remote Terminal of MIL-STD-1553.3.3.5 MCX - Mode Code: For the purposes of this test plan, mode codes are tabulated in Table 1.3.3.6 DBACC - Dynamic Bus Control Acceptance Bit: The status word bi

44、t at bit time 18.4. GENERAL TEST REQUIREMENTS:The following paragraphs define the configurations, pass/fail criteria, and general procedures for production testing of bus controllers. Specifically, this document contains the test configurations and procedures for the electrical tests (5.1) and for t

45、he protocol tests (5.2) for MIL-STD-1553 bus controllers. Bus controllers which can be deployed in more than one configuration, depending upon the choice of stored program or hardware option, shall be tested using all specified configurations such that the test program exercises all of the bus contr

46、ollers capabilities. Before performing each test, the UUT shall be cleared of any pre-existing error conditions to insure that all test results from a given test are independent of previous test results. The bus controller under test is referred to as the UUT. Proper terminal responses are defined i

47、n each paragraph.4.1 General Monitoring Requirements: In addition to the specific tests that follow, certain parameters of the BC transmission must be continuously monitored throughout all tests. These parameters are:1. contiguous data2. proper Manchester encoding3. proper bit count4. odd parity5. p

48、roper word count6. proper intermessage gap times7. proper sync8. proper CMS transmissionThis general monitoring requirement shall include the verification that the CMS transmitted by the UUT is the CMS specified to be transmitted by the procedure. The UUT shall have failed the test if at any time du

49、ring the test any of these parameters fail to meet the requirements of MIL-STD-1553.Copyright SAE International Provided by IHS under license with SAENot for ResaleNo reproduction or networking permitted without license from IHS-,-,-AS4114Page 85. DETAILED REQUIREMENTS:5.1 Electrical Tests: Each test paragraph contains the requirements for both transformer and direct couple