MIL-STD-1553A ‘SUPERSEDING MIL-sTD-1553 (USAF) 30 aucust 1973 MILITARY STANDARD AIRCRAFT INTERNAL TIME DIVISION COMMAND/RESPONSE MULTIPLEX DATA BUS FSC MISCMIL-STD-1553A 30 April 1975 DEPARTMENT OF THE AIR FORCE Washington D. C, 20330 MIL-STD~1553A (USAF) Aircraft Internal Time Division Conmand/Response Multiplex Data Bus 1. , Inis Mil dury standard has been approved for use by all Departments and Agencies of the Department of Defense. 2. Recommended corrections, additions, or deletions should be addressed fo Aeronautical Systems Division, ATTN: ENYESS, Wright-Patterson Ale Force Base, Ohio 45433, itCONTENTS Paragraph lL SCOPE AND PURPOSE al Scope 22 Purpose 2. APPLICABLE DOCUMENTS . DEFINITIONS 1 Remote Terminal 2 Bit 3 Bit Rate 4 Pulse Code Modulation (PCM) Ss ‘Time Division Muli‘plexing (TDM) 6 Command/Response Mode 7 Half Duplex 8 Asynchronous Operation 9 Dynamic Bus Allocation 10 Word i Message 12 Data Bus 13 Controller a REQUIREMENTS Data Bus Operation al Information Transfer Modes Characteristics Data Form Bit Priority ‘Transmission Method al Modulation 2, Data Code 3. Transmission Rate of Word Size 25 Word formats Se Command Word 5.1.1 Syne 1ad MIL~STD-1553A 30 April 1975 Page BUUUEUUUE EE Ee &ey + MIL-STD-1553A, * 30 April 1975 Paragraph BEovEbLELE BRERRERE EE BOO bEELELLE RERRER BREE EEE EEA wu wu PREP RE CONTENTS (cont'd ) Address Transmit/Receive Subaddress/Mode Word Count Parity Optional Mode Control Data Word Syne Data Parity Status word Syne RT Address Message Error Status Codes ‘Terminal Flag Parity Message Formats Controller To RT Transfers RT To Controller Transfers RT to RT Transfers Transmission Line Cable Characteristics Impedance Cable Attenuation Cable Length Cable Termination Cable Coupling Wiring and Cabling for EMC RI/Bus Interface Circuits Circuit Configuration Fault Isolation RT Output Characteristics output Levels Output Waveform Output Noise iv Page OO DamanamannMIL~STD-1553A 30 April 1975 CONTENTS (cont'd) Paragraph Page RT Input Characteristics 16 Input Waveform Compatibility 14 Conmon Mode Rejections rvs Input Impedance 16 Data Validation 16 Terminal Operation 16 1 Response Tine 16 2 Terminal Fail-Safe Operation 16 3 Noise Environment Operation 7 3.1 Test Environment 7 BLL Electric Field v [Link].2 Magnetic Field vy [Link] Bir Error Rate 7 [Link] Incomplete Message Rate 7 [Link] Test Conditions 18 44 Terminal To Subsystem Interface 18 4.41 Serial Digital Interface 18 4.4L Serial Digital Input 18 4eb.1.2 Serial Digital output 23 [Link] Signal Characteristics 23 4.4.2 Discrete Signals 25 45 Bus Controller 25 APPENDIX 10. General 7 10.1 Redundancy 27 10.2 Bus Controller 27 10.3 Multiplex Selection Criteria 29 10.4 High Reliability Requirements 29 10.5 Stubbing 29 10.6 Status Code Usage 30 10.6.1 Vectored Service Request 30 10.6.2 Error Code Supplement 3u 10.6.3 Assigned Codes 30MIL-STD-1553A 30 April 1975 Pp wevausunn eS 13 14 10.1 10.2 ‘FIGURES Typical Multiplex Data Bus Architecture Data Encoding, Word Formats - Command and Status Syne Data Bus Interface Output Waveform Serial Digital Interface Serial Digital Input Interface Serial Digital Input Interface Timing Diagram for External Initiation of Transfer Serial Digital Input Interface Timing Diagram for Terminal Initiation of Transfer Serial Digital Output Interface Serial Digital Output Interface Timing Diagram Illustrations of Possible Redundancy Illustrations of Possible Redundancy TABLE Signal Definitions for Serial Digital Interfaces vi 204 MIL-STD-1553A, 30 April 1975, 1. SCOPE AND PURPOSE 1,1 Scope. This standard defines requirements for digital, conmand/ Fesponse, time division multiplexing (Data Bus) techniques on aircraft. It “encompasses the data bus line and its interface electronics as illustrated on figure 1, and also defines the concept of operation and information flow on the multiplex data bus and the electrical and functional formats to be employed. 1.2 Purpose. The purpose of this document is to establish uniform Tequirements for multiplex data system techniques which will be utilized in systems integration of aircraft subsystems and to promote standard digital interfaces for associated subsystems. The system designer retains the flexibility to assemble a custom miltiplex systen from the functionally Standard parts and to program the standard electronic functions in order to provide a control mechanism, traffic patterns, redundancy, and a viable degradation concept. 2. APPLICABLE DOCUMENTS 2.1 The following documents, of the issue in effect on date of invitation for bid or request for proposal, form a part of the standard to the extent specified herein. SPECIFICATION Military MIL-E-6051 “Electromagnetic Compatibility Requirements, Systens ‘STANDARDS Military MIL-STD-461 Electromagnetic Interference Characteristics, Requirenents for Equipment MIL-STD-462 Electromagnetic Intereference Characteristics, Measurement of (copies of specifications, standards, drawings, and publications required by suppliers in connection with specific procurement functions should be obtained from the-procuring activity or as directed by the contracting officer.) FSC MISC1975 MIL-~STD-1553A, 30 April Sangoeatuoay sng eaeg xeLdiaiMy Leopdey “1 sunByy (S)H31SAsanS NTT ALL Tavayo a | wast, | [HBR es +r sng ! ' t ' 1 1 { { ' sav) i7 ltr Agwaundza 4-p-j---- ak TWNOILIOMIL-STD-1553A 30 April 1975 3. DEFINITIONS 3.1 Remote terminal. The remote terminal is the electronics necessary to interface the bus with the subsystem and the subsystem with the bus. This electronics may exist as a separate LRU (line replaceable unit), or be contained within the users’ subsystem. A redundant bus controller, when not functioning as a controller, may operate as a remote terminal. 3.2 Bit. Contractionof binary digit: may be either zero or one. In information theory a binary digit is equal to one binary decision or the designation of one of two possible values or states of anything used to store or convey information. 3.3 Bit rate. The number of bits transmitted per second. 3.4 Pulse code modulation (PCM). The form of modulation in which the nodulation signal is sampled, quantized, and coded so that each elenent of information consists of different types or numbers of pulses and spaces. 3,5 Time division multiplexing (TDM). The transmission of information from Several signal channels through one communication system with different channel samples staggered in time to form a composite pulse train. 3.6 Command/response mode. The operation of a bus system in which the remote terminal will respond only when commanded by the bus controller. 3.7 Half duplex. Operation of a data: transfer system in either direction over a single line, but not in both directions on that line simultaneously. 3.8 Asynchronous operation. For the purpose of this standard, asynchronous bus operation impli an independent clock source at each remote terminal which is utilized for the transmission of messages. The received message shall be decoded using clock information derived from the received signal. 3.9 Dynamic bus allocation. The operation of a bus system in which designated remote terminals are offered control of the data bus. 3.10 Word. In this docunent associ Ia'S sequence of 16 bits plus eyne and parity. There are three types of weds: command, status and datMIL-STD-1553A 30 April 1975 3.11 Message. A message is a transmission of. vords on the data bus cable. A message transfer is complete when the command word,data word(s)yand the Status vord have been transmitted. There are three types of messages: contro!ter to terminal, terminal to controller and terminal to terminal. 3,12, Eata bus. Whenever a data bus or bus is referred to in this document it shall imply a single twisted shielded pair cable. 3,13 Controller. The controller shall be or controlled by a processor, and that se1 scanning and monitoring bus traffic. a unit that is either programmable, rves the function of comnanding, 4. REQUIREMENTS 4.1 Data bus operation. The multiplex data bus in its most elemental configuration shall operate as shown on figure 1. The data bus shall function asynchronously in a conmand/response mode, and transmission shall occur in a half-duplex manner. Sole control of information transmission on the bus shall reside with the bus controller, which shall initiate all transmissions. The information flow on the data bus shall be comprised of messages hich are, in turn, formed by three types of words (command, data, and status) as defined in [Link]. All elenents of the data bus, including the transmission line, remote terminal and controller, shall conform to the electromagnetic interference requirements specified in MIL-STD-461 and the electromagnetic compatibility requirements of MIL-E-6051. 4.1.1 Information transfer modes. The data bus may employ three modes of jnformation transfer: (1) bus controller to renote terminal (RT) transfer, (2) RT to controller transfer, and (3) RT to RT transfer. These modes shail operate as described in [Link] and subparagraphs. 4.2 Characteristics 4.2.1 Data form. Digital data may be transmitted in any desired form, Provided thet the chosen form shall be compatible with the message and word formats defined in this standard. Any unused bit positions in a word shall be transmitted as logic zeros. 4.2.2 Bit priority. The most significant bit shall be transmitted first with the less significant bits following in descending order of value. The fumber of bits required to define a quantity shall be consistent with the Yesolution or accuracy required. In the event double precision quantities (information accuracy or resolution requiring more than 16 bits) are transmitted, the more significant half shall be transmitted first, followed by the less significant half.MIL~STD-1553A 30 April 1975 Buypooug eyeg “2 aunBpy “oO 7 3SVHd-18 - 0) I B3LS3HONWH : -H) a 0 0 t t - way zon =) - 0 on LILI LE 1 "a = 3NIL 418 3N0MIL-STD-1553, 30 April 1975 4.2.3 Transmission method. [Link] Modulation. The signal shall be transferred over the data bus in serial digital pulse code modulation form. [Link] Data code. The data code shall be Manchester bi~phase level. A logic one shall be transmitted as a bipolar coded signal 1/0 (i.e., @ positive pulse followed by a negative pulse). A logic zero shali be bipolar coded signal 0/1 (1.e., a negative pulse followed by a positive pulse). A transition through zero occurs at the, midpoint of each bit time (see figure 2). [Link] Transmission rate. The transmission rate on the bus shall be 1.0 megabit per second with a long term stability of 40.01 percent (i.e., 4100 Hz). The short term stability (i.e., stability over a 1.0 second Gnterval) shall be at least 0.001 percent (i.e., +10 Hz). [Link] Word size. The word size shall be 16 bits plus the sync vaveforn and the parity bit for a total of 20 bit times as shown in figure 3. [Link] Word formats. The word formats’ shall be as shown on figure 3 for the command, data, and status words. 4,[Link] Command word. A command word shall be comprised of a sync waveform, address, transmit/receive bit, subaddress/mode, data word count, and a parity bit (see figure 3), except as modified by [Link].1.7. 4,[Link].1- Syne. The command syne waveform shall be an invalid Manchester waveform as shown on figure 4. The width shall be three bit times, with the waveform being positive for the first one and one-half bit times, and then negative for the following one and one-half bit times. If the next bit following the sync is a logic zero, then the last half of the sync waveform will have an apparent width of two clock periods due to the Manchester encoding. [Link].1.2 Address. The next five bits following the sync shall be the RT address. This permits a maximum of 32 RTs to be attached to any one data bus. All 1's shall indicate a decimal address of 31, and all 0's shall indicate a decimal address of 32. The most significant bit of the address shall be transmitted first. [Link].1.3 Transmit/receive. The next bit following the address shall be the transmit/receive bit, which shall indicate the action required of the RT. A logic zero shall indicate the RT is to receive, and a logic one shall indicate the RT is to transmit.MIL~STD-1553A 30 April 1975 42:3-5-1.4 Subaddress/mode. The next five bits following the transmit/ receive bit shall be utilized for either a RT subaddress or mode control, as is dictated by the individual terminal requirements. The subaddrese/ mode value of 00000 is reserved for special purposes, as specified in 4.2.3,5.1.7, and shall not be utilized for any other function. [Link].1.5 Word count. The next five bits following the subaddress/mode control shall be the quantity of data words to be either seat out or rescived by the RI. A maximum of 32 data words nay be transmitted or received te asp one message block. All 1's shall indicate a decimal count of 31, and all 0's shall indicate a decimal count of 32. 4:[Link].6 Parity. The last bit in the word shall be used for parity over the preceding sixteen bits. Odd parity shall be utilized. [Link].1.7 Optional mode control. For Rts exercising this option, a subaddress/mode code of 00000 shall imply that the contents of the word count field are to be decoded as a five bit mode command. When used with this option, the word count field mode code of 00000 shall be reserved for dynamic bus allocation. 4:[Link] Data word. A data word shall be comprised of a sync waveform, data bits, and a-parity bit (see figure 3). [Link].2.1 Syne. The data sync waveform shall be an invalid Manchester waveform as shown on figure 5. The width shall be three bit times, with the waveform being negative for the first one and one-half bit times, and then positive for the following one and one-half bit times. Note that if the bits preceding and following the sync are logic ones, then the apparent width of the sync waveform will be increased to four bit times. 4-[Link].2 Data. The sixteen bits following the syne shall be utilized for data transmission as specified in 4.2.2. 4:2-3-5-2.3 Parity. The last bit shall be utilized for parity as specified in [Link],1.6. 4,2.3:5.3 Status word. A status word shall be comprised of a sync waveform, RT address, message error bit, status codes, terminal flag bit, and a Parity bit (see figure 3). [Link].3.1 Syne. The sync waveform shall be as specified in [Link].1.1.MIL-STD-1553A 30 April 1975 Syeuog pox “€ SANG} é fan spo smeas | 34 | ssospey rewyauay uks ufc 6 PON smaeas 4 weg outs 7 5 a pi0M veg 4 |__20me9 pson evra | sow/stasppeans [ast] sseuppy ieupsiay | outs ft s s t s pon puruoy o2| 61 a| [o st} mt} er] at} u for} 6 {ele [s]>]e eft tsoup, 348MIL-STD-1553A 30 April 1975 Syeuoy aGessoy “9 aunbyy Ue%b Ub pazspzads se deg 4 sojuest 2] Gal---- 2) Ee Tes seysun EES feo stete| | [anme? | sirea] 4, ihe a Ree] Ba] BO] pam] woe feu ]----[Bee [ea [oS] [me] atts sojuest Poy i PsON, PsoHK purwwoy eujwsay o, wins | [ed feo | et | Batty | tsisiu'on . ‘ w 10MIL-STD-1553A 30 April 1975 + VOLTS r--5 poy i ! | ! 0 ti 1 ‘ 1 + voUTS J WORD sytic — + bir Figure 4. Coumand and Status Syne + VOLTS 0 + VOLTS Figure 5. Data SyneMIL-STD-1553A, 30 April 1975 4.2.4 Transmission line. The data bus shall utilize, as the transmission medium, a twisted, shielded, wire pair. 4.2.61 Gable. The cable used shall be a tvo conductor, twisted, shielded, Jacketed cable. The wire-to-wire distributed capacitance shall not exceed 30.0 picofarads per foot. The cable shall be formed with not less than one twist per inch; and the cable shield shall provide a minimum of 80 peréent coverage. [Link] Characteristic impedance. The characteristic impedance shall be 70 ohms, plus or minus 10 percent, at a sinusoidal frequency of 1.0 Miz. [Link] Cable attentuation. At the frequency of [Link]; the cable power loss shall be I db/100 ft or less. [Link] Cable length. The cable length of any main bus may be up to 300 feet. [Link] Cable termination. The cable shall be coupled to the RT as shown on figure 7, A long stub is defined as any stub greater than one foot in length. The use of long stubs is discouraged and the length of any stub shall not exceed 20 feet. The two ends of the cable shall be terminated with @ resistance equal to the cable characteristic impedance. [Link] Cable coupling. All connections to the data bus shall utilize a small shielded coupler box. This box shall be of sufficient size to permit the installation of the transformer and isolation resistors specified in 4.2.5. The connector plug shall be compatible with Auphenol Type 31-235 or Trompeter Type TEI-14949-E137 receptacles. The connector receptacle shall be compatible with Amphenol type 31-224 or Trompeter Type TEI-14949-PL36 plugs. The polarity convention shall be that the female connection in the plug is Positive, and the male connection in the receptacle is positive. This connector, with the indicated polarities, shall be used for all bus interfaces. [Link] Wiring and cabling for EMC. For purposes of electromagnetic compatibility (EMC), the wiring and cabling provisions of MIL-E-6051 shall apply. 4.2.5 RO/bus interface circuits. [Link] Circuit configuration. The input/output circuits shall consist of a transmitter-receiver, DC isolation/coupling transformer, and isolation resistors as configured on figure 7. 12MIL~STD-1553A 30 Apri 1975 4.2,[Link] RT address. The next five bits following the syne shall. contain the address of the terminal which is transmitting the status word as defined in [Link].1.2. 4.2.3,5.3.3 Message error. The first bit after the address shall be utilized to indicate that the preceding message failed to pass the RT's validity tests. This error condition shall include parity errors. A logic one shall indicate the presence of a message error, and a logic zero its absence. A wiessage error shall be indicated when the preceding message to a RT bas failed either the word or message validity criteria for the RT. The criteria shall include those specified in [Link].4. [Link].3.4 Status codes. The next nine bits following the message error bit may be utilized in any fashion desired by the RT designer, except that al} zeros shal indicate a normally functioning terminal. [Link].3.5 Terminal flag. The next to least significant bit in the Status word is reserved for a terminal flag bit. This bit shall be set to one to indicate the need for the bus controller to examine the built in test data available from the terminal. 4.2.3,5.3.6 Parity. The last bit shall be utilized for parity as specified in [Link].1.6. [Link] Message formats. The messages transmitted on the data bus shall be in accordance with the formats in figure 6. The maximum and minimim response times shall be as stated in 4.3.1. [Link].1 Controller to RT transfers. The controller shall issue a receive command followed by the specified number of data words. The RT shall, after message validation, transmit a status word back to the controller. The command and data words shall be transmitted in a continuous fashion with no interword gaps. [Link].2 RZ_to controller transfers. The controller shall issue a transmit command to the RT. The RT shall, after command verification, transmit a status word back to the controller, followed by the specified number of data words. The status and data words shall be transmitted in a continuous fashion with no interword gaps. [Link].3 | RT_to RT transfers. The controller shall issue a receive comand to RT A, followed by a transmit command to RT B. RIB shall then transmit the data as specified in [Link].1. aLMIL-STD-15534 30 April 1975 nich cacpeauit isolation. An isolation resistor shall be placed in series wanna ash connection £0 the data bus cable. This resistor shall haart Value of 0.75 2, ohms plus or minus 5 percent where 2, is the cable cheracteristic “impedance. The impedance placed acros? the date tes cable shall be no less than 1.5 Z, ohms for any failure of the coupling transformer, cable stub, or RT trfnsmitter/receiver. [Link] RT output characteristics. 6:2;5;3-1 Qutput levels. The RT signal output circuitry shall be capable Sf driving the cable specified in [Link] and not less than 33 othec Rts, of Specified herein, each attached to the cable by means of a cable sean Shemaxinum iength specified in [Link]. The output cirqiitry shell maintain She specified operation with the exception of a 25 percent aainny reduction Paulette bus signal amplitude in the event that one of the Rte hee fault that causes it to reflect the fault impedance specifing ae [Link] Fo ene go ony et Peak signal output voltage shall be between plus os minus 20 and 10.0 volts, 1ine-to-line, when measured at the date bus cutie connection (point A on figure 7), 4.2,5.3.2 Output waveform. figure 7 shall have zero cros: 25 nanoseconds from those shown voltage as shown in figure 8. [Link] Qutput noise. Any noise transmitted to the data bus when the RT is Receiving or has power removed, shall not exceed a value of 10.0 pillinslen Peak-to-peak, line-to-line, as measured at the point specified in [Link].1, [Link] RT input characteristics. The RT shall be capable of signals specified herein, and Taanall respond to an input signal whose positive or negative peak amplitude, jine-to-line, is within the range of 10.0 to 0.5 volts. “The voltages are measured at point C in figure 7. 2;2,5:4.2, Common mode rejections. Any signals from de to 2.0 wile, Yikh eplitudes equal to or less than plus or minus 10.0 volts peak, iine-to-ground, applied to point A as shown in figure 7 shall ave degrade the performance of the RT. 14MIL-STD-1553A 30 April 1975 GMs ONOT HLIM Ly soezuaquy sng veg °y aunbyy 8313938 /83. LLINSNVEL Tose +~ 2 > GALS LYOHS HLIM 1y UBAT3ORU/YILLIWSHYEL I" leggea 71 ! t 1 ! ] | 2 > ! 1 r-E a> bq t ! xog ' I 1 I — watanoo I ' ! 1 ' 1 1 ' v I ud 341M 1 Ny ' ng Vivo t Nh { NEI boi ill -! 13ce) MIL-STD-1553A 30 April 1975 the bn’ j2 lupus impedance. The magnitude of the RT input impedance, when Spe Rt is NOE transmitting, or has power removed, shall be a nininen gf 2000 ohms within the frequency range of 100 Kz to 1.0 Mie. This Ampendance is that measured line-to-line at point C on figure 7. 4,2-5-4.4 Data validation. Logic shall be provided in each RT to Signela, guvroperly coded signals, data dropouts, or excessively noisy signals. Each word shall conform to the following minima validating criteria: a. The word begins with a valid sync field b. The bits are in a valid Manchester IT code c. The information field has 16 bits plus parity d. The word parity is odd. an, avelid word syne occurs, the receiving RT shall reset and walt fer a nee valid message sync. An invalid word count shall be construed ac a message transmission error. 4.3, ‘Terminal operation. The remote terminal shall operate in response receleaans Feceived from the bus controller. The RT shall be capsble of 4-3:1 Response time. The RT shall respond to a valid transmit data command Serene the time period 2.0 to 5.0 microseconds after receipt of the lace ane of the command word. The RT shall respond to a valid reserve dave soot bat eens the time period 2.0 to 5.0 microseconds after receipt of the last bit of the last data word. i222, Terminal fail-safe operation. The RT shall contain the self-test girevitry necessary to detect an erroneous transmission of daca on to cre Gata bus. This circuitry shall include a transmission tine-oue which ‘Gue Preclude a signal transmission period of greater than 660 micrcesconds (one status, and thirty-two data words). When the self-cese circuitry detects any such erroneous transmission, it shall. automatically shut down the transmitter portion of the RT. 16MIL-STD-1553A 30 April 1975 wioganen nding *g sanBy4 338M Oot | fe 7-7 ---l- marten fem sion = 305 SLIOA 0 roaty---------4+------- aH m6 site 15of MIL-STD-1553A 30 April 1975 [Link] Test conditions. For purposes of the noise tests, the following conditions shall be observed. All data words shall be changed to random bit patterns prior to each transmission/reception set as defined in [Link]. The test shall be conducted with the bus controller and the renote terminal both connected by 20 foot stubs to the main data bus cable, with a minimum distance of 100 feet between the stubs. The remote terminal transmitter shall provide an output as specified in [Link]. The bus controller transmitter Shall have its output adjusted so as to provide the minimum signal amplitude specified in [Link].1 at the remote terminal. 4.4 Terminal to subsystem interface. For those applications where a terminal ia not contained within a subsystem, and the terminal exists as a distinct LRU, the terminal shall provide the necessary electronics to interface to the subsystem. The terminal shall have provisions for the standard serial digital and discrete interfaces as defined in the following paragraphs. ‘All other signals shall require special purpose interface provisions Within the terminal, this electronics being designed for the peculiar interface requirement. 4.4.1 Serial digital interface. The standard serial digital interface shall be configured as shown in figure 9. All lines are unidirectional, with the data line's direction to be determined by its usage, i.e., to transmit or to receive data. The interface shall operate as defined in Gcéc1-1 for an input interface and as defined in [Link] for am output daterface. ‘The functions of each of the signals is as define? in table I. e .6.1.1 Serial digital input. A serial digital input interface is a of six signals between an external device and the remote terminal. This interface is shown in figure 10. The function of each of the six signals is defined in table I. The performance of a data input sequence can be {nitiated by either of two actions. The external device can pulse the FLAG Line if the LOCKOUT line is low, and thereby initiate a data input sequence. The timing diagram for this action is shown in figure 11. The bus controller can directly conmand the remote terminal to begin a data input sequence. The timing diagram for this action is shown in figure 12. In either case, the nitiation of the data input sequence causes the LOCKOUT line to be set, and the completion of the data input sequence shall cause the remote terminal to notify the bus controller of the datainput, and of any parity errors. ‘The remote terminal shall be required to clear the LOCKOUT before any new externally initiated data input sequences can occur. 18MIL~STD-1553A 30 April 1975 4.3.3 Noise environment operation. The remote terminal shall function Properly under the test conditions specified in [Link], and encountering the electromagnetic environment specified in 4.3.31. The remote terminal shall exhibit a maximum bit error rate of 10-12, “where the bit erroe rate is as defined in [Link]. The remote terminal shall also exhibit « maximum incomplete message rate of 10-6, where the incomplete message rate is ce defined in [Link]. [Link]. Test environment. The test environment for the renote terminal and data bus cable radiated susceptibility shall be as follows. 4.3,3,1,1 Electric field. The electric field test shall employ MIL-StD;462 Rethod RSO3, with the limit specified in MIL-STD-461 test limit RSO3. {ie clectric field shall be 100 percent modulated by a waveform as specified in 4.2.3. wpledit-2 Magnetic field. The magnetic field (spike test) shall eaploy WL STD-462 method RSO2, with the limit specified in MIL-STD-46l test limit Rso2. [Link] Bit error rate. For the purposes of paragraph 4.3.3, the bit error Fate is defined as follows: The bus controller transnits 32 data words te a Fenote terminal as specified in 4.1, and the remote terminal responds with the atus (Word indicating no message errors. The bus controller then coumands the Teaote terminal to transmit the same 32 data words hich it previously Received, as is specifed in 4.1. Upon receipt of a valid response from tne Tonore terminal, the controller than compares each data word which it sent Batch, this is to be considered a bit error. The total number of data bite transmitted during a specific time period are counted. The bit error rate ig then defined as the number of bit. errors, divided by the total number of bits transmitted. $p3;3-3 incomplete message rate. For the purposes of paragraph 4.3.3, the incomplete message rate is defined as follows: A message is the set of Command, data, and status words as defined in [Link]. An incomplete ceasatg <8 defined as one during which the remote terminal does not properly pipPond fo & comand by the bus controller, or one in which the message error Pet ig set in the renote terminal status word. The total number of incomplete ne eages ate counted during a specific time period, as are the total number Cf messages. | The incomplete message rate is given by the number of ‘complete ‘Tessages divided by the total number of messages. The message error bit in the first status word following a non-response by a renote terminal shall Rot be included in the incomplete message count. The message formats shall be as defined in [Link]. 7MIL-STD-1553A, 30 April 1975 TABLE I Stsaal Definitions for ¢.-tal Digital Interfaces sovp REQUEST. This 4s a signal from the renote terminal to the external gevice which, when set to logic 1 by the ccsoce terminal, notifies the Set co toeevice, that 2 data transfer is about to take Place, and when a dary LBtC ® by the renote terminal, notifies the external device that @ data transfer is complete. the rongemimal which, vhen set to logic 1 by the axtenos device, notifies ght Fenote terminal that the external device hee Fecognized the REQUEST, and jo recdy for the data transfer, and when sec Co logic @ by the external device, notifies the renote terminal that che external device has recognized the lowering of the REQUEST and the end ef the data transfer. - JeveSLOORs, This is a signal from the renote terminal to the external eerasty watch when active is al Miz square wace mene number of cycles Ne ressee eeuber Of bits to be shifted. The CLock te im started until rege emgte terminal has seen the ACKNOWLEDGE Line voves® "OE the end of the tast CLOCK eyele the renote terminal shall loves the REQUEST Line. This is a signal to or from the remote terminal upon which data is transmitted. On the positive edge of che CLOCK signal the next DATA bit shall be placed on the DATA linc. 32 LOOKOUT. This is a signal from the remote terminal to the external device vhich, when set to logic 1 by the ressce terminal, notifies the teasgrad device that it shall refuse all external requests for data transfer, and when set to logic @ by the remsce terminal, notifies the 6. ERROR... This is a signal from the external device to the remote sepminal which the external device clears at the ine ACKNOWLEDGE is raised, and which the external device sets at any time that a parity error is detected while receiving data. Thaeii@s This is a signal from the external device to the remote terminal, which is a pul; en 1 and 10 microseconds, that notifies the The ssceerminat that there has been an external request sor DATA input sequence. ThE QceurFence of this pulse shall initiate « DATA input sequence, and after the Sequence is completed the bus controller shale be informed that the catmee scoccurred and whether or not there were any Parity errors. This signal Signal couceg Wize, the LOCKOUT line is high, and the ocewrens of this Signal causes the LOCKOUT line to be set high, 20MIL-STD-1553A 30 April 1975 c REQUEST REMOTE ‘SUBSYSTEM TERMINAL ACKNOWLEDGE FIGURE 9: Serial Digital Interface 19© MIL-STD-1553A, 30 April 1975 FLAG. Lockout REQUEST ‘ACKNOWLEDGE > Lock DATA 22 wore: (1) (2) (3) @ Figure 12. MN equals 17 times the number of words” ty and ty are less than 200 nanseconds tz is less than 500 nanoseconds ty 18 design dependent Serial Digital Input Interface Timing Diagram for Terminal Initiation of TransferMIL~STD-1553A 30 April 1975 smote ACKNOWLEDGE SUBSYSTEN TERMINAL LH Figure 10, Serial Digital Input Interface be t ey P— LockouT _————_—= —[—= Sa REQUEST TT ey ACKNOWLEDGE —- cee ‘FLeLAL PL ALP, wm THe Figure 11, Serial Digital Input Interface Timing Otagram for External Initiation of Transfer NOTE: (1) HM equals 17 tines the number of words (2) ty is less than 10 and greater than 1 microsecond (3) tay ty and ty are less than 200 nanoseconds (4) ty is less than 500 nanoseconds (5) tg ts design dependent 3 # 21 eeMIL-STD-1553A, 30 April 1975 24 REQUEST ‘ACKNOWLEDGE chock DATA ERROR REQUEST REMOTE SUBSYSTEM TERTNAL ACKNORLEDGE Figure 13. Serial Digital Output Interface Se, TL —ALELB, .ALL ear IZA ZZ, RR NOTE: (1) N equals 17 tines the number of words (2) ERROR line is based on parity check by subsystem (3) ty and ty are less than 200 nanoseconds (4) tz is less than 500 nanoseconds At ke Figure 14. Serial Digital Output Interface Timing OiagrtmMIL~STD-15534 30 April 1975 sot de?,Sttigh digital output. A serial digital output interface is a eis nee usnals between an external device and the remote tevainal’ Hus interface is show in figure 13. The functions of each of these five signals is defined in table I. The timing diagram for the dues output Bee geeg eine these five signals is shown in figure 14. The performance seeosats QutPUE sequence can be initiated by either of evo bus conteniter actions. The bus controller can send a new data block to the ence ferminal, and the receipt of this data block shall initiate « dete output to rbeein a pig, bus controller can also directly command the remote tereival Roe Sein a data output sequence using the data block that the remote recmeal has available. In either case, once a data output sequence ie initiated, the deta erseetiace shall alvays transfer the complete set of data, anf umen (fe data transfer is complete the renote terminal shall examine the ERROR tive’ 4;4-1-3 Signal characteristics. The characteristics of serial digital signals shall be in accordance with the following: a. Data code Non-return-to zero (NRZ) b. Type Differential and balanced c. Data word + 16 bits followed by one bit of odd parity 4. Data rate One megabit plus or minus 10 percent e- Rise and fall time As specified in [Link].2 £. Output voltage 0.5 t0 0.5 volts 2.4 to 5.5 volts 8+ Common mode output The common mode output voltage (measured from each voltage line to the signal common) of the output circuit shall be no greater than plus or minus 0.5 volt peak he Short and Over- The output circuit shall not be damaged when voltage protection subjected to shorts to ground or a voltage of plus or minus 20 volts 1. Message size A fixed number of words for each request with a maximum of 32 words 4. Bit priority As specified in 4.2.2. 2326 MIL-STD-15534 30 April 1975MIL-STD-1553A 30 April 1975, 4.4.2 Discrete signals. The discrete interface shall be double-ended, and shall employ the following logic levels: Zero: -0.5 to 0.5 volts One: 2.4 to 5.5 volts ghe_input circuits shall present a minimum impedance of 10K ohm sesso ltage faults to an input of up to plus or minus 20 volte shall not damage the input. The output circuits shall be capable of Providing a penauen output current of 100 milliamperes. Short circuits on eicher inputs OF outputs shall not damage the circuits. speacemme computer, The controller shall be programmable eal chart reguitemenaet Software (or firmware) control. Individual application Tuyegments shall determine the choice as to which forn of sontecling is used. Custodian: Preparing activity: Air Force - 11 Air Force = 11 Navy ~ AS Army ~ Project Nr MISC-0941 25MIL-STD-1553A, 30 April 1975 Bus CONTROLLER NOTE: RT - Remote Terminal BUS Ko. 1 -| BUS NO, 2 REMOTE TERMINAL ar ar — saan] [astm ] BUS bus CONTROLLER }-—| CONTROLLER [ RT RT RT | ‘SUBSYSTEM ‘SUBSYSTEM | sme JULUSTRATIONS OF POSSIBLE REDUNDAKCY 28we MIL-STD-1553A, 30 April 1975, APPENDIX 10. General. The following paragraphs in this appendix are presented in order to discuss certain aspects of the standard in a general sense. They are intended to provide a user of the standard more insight into the aspects discussed. 10.1 Redundancy. It is intended that this standard be used to support rather than to supplant the system design process. For this reason, the standard is deliberately vague concerning the use of redundancy in implementing a miltiplex data bus system. The system designer should utilize this standard as the needs of a particular application dictate. The use of redundancy, the degree to which it is implemented, and the form which it takes must be determined on an individual application basis. Figures 10.1 and 10.2 illustrate some possible approaches to dual redundancy, These illustrations are not intended to be inclusive, but rather representative. It should be noted that analogous approaches exist for the triple and quad redundant cases. 10.2 Bus controlJer. The bus controller is a key part of the data bus system. The functions of the controller, in addition to the issuance of commands, must include the constant monitoring of the data bus and the traffic on the bus. It is envisioned that most of theroutine minute details of bus monitoring (e.g., parity checking, terminal non-response time-out, etc.) will be embodied in hardware, while the algorithms for bus control and decision making will reside in software. It is also envisioned that, in general, the bus controller will be a general purpose airborne computer with a special input/output (1/0) unit to interface with the data bus. In the case of a large aircraft, such as a bomber, the multiplex bus control problem may be of sufficient complexity to warrant the employment of a dedicated bus controller. While in a smaller, fighter-type aircraft, the control function will probably be incorporated into a computer which is also utilized for the navigation and weapon delivery functions. It is important to remember that the controller will be the focal point for modification and growth within the multiplex system, and thus the software must be written in such a manner as to permit modification with relative ease. 27MIL-STD-15534, 30 April 1975 Zine {0 Provide’ isolation from the fault. These networks are also used Gor Stubs that are of such length that the nisusteh won reflection degrades bus operation. Of the possible networks, transtome. coupling gives the jeast loss. For a 300 foot transmission line operating at 1 megabit, che total loss for the system-with 30 stubs was beeweee 15 and 25 4B. For Saree Rgtworks such as direct, loss, and loaded, the ese varied from 32 to 45 dB. If the length of the stub doce soe approach one-quarter dieegength oF is less than 50 en, it does not seen to case significant distortion. It may be well to note that stubbing is not a preferred method SE rus configuation, but that it is necessary or convenient in the physical javout oF installation of the transmission line, “a exact limit to stubbing Gepends upon the number of stubs, length, type of modulation, and the degree of filtering used. 20,6, Status code usage. The nine bits in the remote terminal status word sesccated for Status Codes may be utilized in any snomee the terminal designer wishes. Such usage may include the following possibilities: auror}, Mectored service request. These nine software interpretable Bits may be used to encode a subaddress and word cowne referencing a specific concer iate Words which the terminal wishes to have collector by the bus controller. All zeros in the field could signify so requests. 10.6.3 Assigned codes. The individual bit positions may be assigned specific fe indicaces eerscance. Thus, if one bit 1s set, then « power supply failure fs indicated, or if another bit is set, then a Manchesves encoding error has > occurred. 30 SUS. GOVERMENT PANTING OFMCE:1976— senze64ra0 JMIL-STD-1553A. 30 April 1975 10.3 Multiplex selection criteria. The selection of candidate signals for multiplexing is a function ‘of the particular application involved, and criteria will in general vary from system to system. Obviously those signals which have bandwidths of 400 Hz or less are prime candidates for inclusion on the bus. It is also obvious that video, audio, and high speed parallel digital signals should be excluded. The area of questionable application is usally between 400 Hz and 3kHz bandwidth. The transfer of these signals on the data bus will depend heavily upon the loading of the bus in a particular application. The decision must be based on projected future bus needs as well as the current loading. Another class of signals which in general are not suitable for multiplexing are those which can be typified by a low rate (over a mission) but possessing a high priority or urgency. Examples of such signals might be a nuclear event detector output or a missile launch alarm from a warning receiver. Such signals are usually better left hardwired, but they may be accommodated by the multiplex system if a direct connection to the bus controller's interrupt hardware is used to trigger a software action in response to the signal. 10.4 High reliability requirements. The use of simple parity for error detection within the multiplex bus system was dictated by a compromise between the need for reliable data transmission, system overhead, and remote terminal simplicity. Theoretical and empirical evidence indicates that an undetected bit error rate of 10-!2 can be expected from a practical multiplex system built to this standard. If a particular signal requires a bit error rate which is better than that provided by the parity checking, then it is incumbent upon the system designer to provide the reliability within the constraints of the standard or to not include this signal within the multiplex bus system. A possible approach in this case,would be to have the signal source and sink provide appropriate error detection and correction encoding/ decoding and employ extra data words to transfer the information. Another approach would be to partition the message, transmit a portion at a time, and chen verify (by interrogation) the proper transfer of each segnent. 10.5 Stubbing. Stubbing is a method wherein a separate line is connected between the primary data bus line and a remote terminal. The direct connection of a stub line causes a mismatch which appears on the waveforms. This mismatch can be reduced by filtering at the receiver and by using Biphase modulation. Stubs are often employed not only as a convenience in bus layout but as a means of coupling a unit to the line in such a manner that a fault on the stub or terminal will not greatly affect the transmission line operation. In this case, a network is employed somewhere in the stub 29