1、 METRIC MIL-HDBK-1760A 10 March 2004 Superseding: MIL-HDBK-1760 15 February 2000 DEPARTMENT OF DEFENSE HANDBOOK AIRCRAFT/STORE ELECTRICAL INTERCONNECTION SYSTEM This handbook is for guidance only. Do not cite this document as a requirement. AMSC: N/A AREA SESS DISTRIBUTION STATEMENT A. Approved for
2、public release; distribution is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-1760A ii FOREWORD 1. This handbook was developed by a team including members from the three U.S. military services, the UK MOD, the SAE AS-1B committe
3、e, and contractors. It includes information previously published in document ASD-TR-87-5028 with certain elements of ASD-TR-91-5009. Some of this information was also published in DEF-STAN-00-69 (Part II), which is written around MIL-STD-1760B. This revision of this handbook is written around MIL-ST
4、D-1760D and assumes that the reader is also reading 1760D. 2. This handbook provides information on the implementation of a standardized electrical interconnection system, as defined by MIL-STD-1760, into both current and future aircraft and stores. It provides guidance on design considerations and
5、options for including the standard interface capability at the aircrafts store stations and for providing a common electrical interface on carriage stores and mission stores. As a handbook, it cannot be invoked as a requirement in a contract. 3. Trends in weapon system designs (aircraft and stores)
6、caused concern over the general proliferation of aircraft-to-store electrical interfacing requirements and the resulting high cost to achieve interoperability between aircraft and stores. The intent of MIL-STD-1760 is to reduce the aircraft/store electrical integration problem by specifying a standa
7、rd electrical interface between aircraft and stores. The standard electrical interface is based on recognized trends in store management systems which use serial digital data transmission for control, monitor and release of stores. In general, the handbook provides the following: a. An overview of M
8、IL-STD-1760 requirements, exclusions and future growth provisions. b. Detail design considerations applicable to the Aircraft Station Interface (ASI), Mission Store Interface (MSI), Carriage Store Interface (CSI) and the Carriage Store Station Interface (CSSI), with application guidelines. c. Aircra
9、ft/Store Physical Design Considerations. d. A commentary on the purpose of each requirement in MIL-STD-1760. e. A summary of changes between the various revisions of MIL-STD-1760. 4. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving t
10、his document should be addressed to: ASC/ENOI, 2530 Loop Road West, Wright-Patterson AFB, OH 45433-7101, or e-mailed to: James.Byrdwpafb.af.mil. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-1760A iiiCONTENTS (Abbreviated - limited to 2 di
11、git paragraph numbers) PARAGRAPH PAGE 1. SCOPE1 1.1 Purpose.1 1.2 Background. 1 1.3 Limitations. 2 2. APPLICABLE DOCUMENTS 3 2.1 General. 3 2.2 Government documents3 2.3 Other Government documents, drawings, and publications. 4 2.4 Non-Government standards and other publications5 2.5 MIL-STD-1760.5
12、3. DEFINITION OF TERMS AND ACRONYMS 6 3.1 Definition and use of terms. 6 3.2 Acronyms and Abbreviations. .9 4. GENERAL .16 4.1 Scope of the standard. 16 4.2 MIL-STD-1760 interface definitions.19 4.3 MIL-STD-1760 interface elements. .20 4.4 MIL-STD-1760 classes23 4.5 Summary of requirements.23 4.6 Pu
13、rpose, goals and projected benefits of MIL-STD-1760. 29 4.7 The MIL-STD-1760 application process33 5. SYSTEM DESIGN.36 5.1 General. 36 5.2 Aircraft design considerations.36 5.3 Store design considerations47 5.4 System safety features51 5.5 Interface design/documentation process. .73 5.6 Future trend
14、s and considerations77 6. DIGITAL DATA BUS INTERFACE79 6.1 Overview of data bus application to AEIS. 79 6.2 Data communications and system control. .84 6.3 Network reconfiguration. .86 6.4 Data bus interface EMI considerations. 88 6.5 Architectural considerations94 6.6 Data bus topology issues. .99
15、6.7 Mission store issues107 7. DISCRETES113 7.1 Release consent. 113 7.2 Interlock interface127 7.3 Address interface. .135 8. HIGH BANDWIDTH INTERFACES.149 8.1 General. 149 8.2 Detailed discussion on HB requirements. .154 Provided by IHSNot for ResaleNo reproduction or networking permitted without
16、license from IHS-,-,-MIL-HDBK-1760A iv PARAGRAPH PAGE 8.3 Cable selection for HB interfaces175 8.4 HB Type A signal path linear distortion. 175 8.5 HB Type A signal path system-level performance budget. .188 8.6 Video signal path system-level performance. .199 8.7 Requirements for GPS RF Signals. 20
17、4 9. LOW BANDWIDTH (LB)210 9.1 LB characteristics210 9.2 Aircraft design requirements. 211 9.3 Mission store low bandwidth interface. .214 9.4 Grounding requirements. 216 9.5 Differential signal transmission. 216 9.6 Electromagnetic considerations. .217 9.7 Analog network BIT.220 9.8 Insertion gain.
18、221 9.9 Equalization requirements.221 9.10 Noise. 221 10. POWER AND STRUCTURE GROUND INTERFACES 223 10.1 Power source rating. .223 10.2 Power return circuits interference issues. .224 10.3 Phase sequence. 226 10.4 Shielding. 228 10.5 Aircraft power control and power characteristics at the ASI228 10.
19、6 Carriage store power control and distribution. 237 10.7 Mission Store power control and power characteristics at the MSI.240 10.8 Store power return interfaces246 10.9 Operational power interfaces. .246 10.10 Circuit protection. 247 10.11 Structure ground. 252 10.12 270 VDC254 11. RESERVED FUNCTIO
20、N 270 VDC 260 12. RESERVED FUNCTION FIBER OPTICS 261 12.1 Characteristics of fiber optics261 12.2 Strategy for implementation of fiber optics261 12.3 Proposed interface. .261 13. ELECTROMAGNETIC COMPATIBILITY 263 13.1 Reason for lack of EMC requirements. .263 13.2 EMC requirements that were in Revis
21、ion B.263 14. CONNECTORS, WIRING AND UMBILICALS 268 14.1 Aircraft station interface connectors271 14.2 Mission store interface. .283 14.3 Carriage store interface (CSI). 290 14.4 Carriage store station interface (CSSI). 290 14.5 Umbilicals and buffers.290 14.6 Low bandwidth cable characteristics.300
22、 14.7 LB connectors. 300 14.8 Use of existing audio wiring in LB installation. 301 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-1760A vPARAGRAPH PAGE 15. COMMENTARY ON THE REQUIREMENTS OF MIL-STD-1760D.302 15.1 Scope. .302 15.2 Applicable
23、 documents. 302 15.3 Definitions. 303 15.4 General requirements. 305 15.5 Detailed requirements. 311 15.6 NOTES359 16. CARRIAGE STORES362 17. LOGICAL DEFINITION .363 17.1 Scope. .363 17.2 Applicable documents. 364 17.3 Definitions. 364 17.4 Requirements364 17.5 Table B-XXXI.548 18. COMPATIBILITY BET
24、WEEN VERSIONS OF MIL-STD-1760 550 19. CHANGES BETWEEN MIL-STD-1760 AND MIL-STD-1760A551 19.1 MIL-STD-1760 First Issue. 551 19.2 MIL-STD-1760 Notice 1. .551 19.3 MIL-STD-1760 Notice 2. .551 19.4 MIL-STD-1760A. .551 20. CHANGES BETWEEN MIL-STD-1760A AND MIL-STD-1760B .552 20.1 MIL-STD-1760A Notice 1.
25、.552 20.2 MIL-STD-1760A Notice 2. .552 20.3 MIL-STD-1760A Notice 3. .552 20.4 MIL-STD-1760B. .552 21. CHANGES BETWEEN MIL-STD-1760B AND MIL-STD-1760C NOTICE 1557 21.1 Changes between MIL-STD-1760B and MIL-STD-1760B Notice 1. .557 21.2 Changes between MIL-STD-1760B Notice 1 and MIL-STD-1760B Notice 2
26、557 21.3 Changes between MIL-STD-1760B Notice 2 and MIL-STD-1760B Notice 3557 21.4 Changes between MIL-STD-1760B Notice 3 and MIL-STD-1760C557 21.5 Changes between MIL-STD-1760C and MIL-STD-1760C Notice 1559 22. CHANGES BETWEEN MIL-STD-1760C NOTICE 1 AND MIL-STD-1760D .561 23. CROSS REFERENCE OF SEC
27、TIONS BETWEEN REVISION B, REVISIONS C-D, AND HANDBOOK563 24. NOTES566 24.1 Intended use. 566 24.2 International standardization agreements. 566 24.3 Keyword listing. .566 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-1760A vi TABLES PAGE T
28、able I. Example of aircraft, stores and store missions. 30 Table II. Interface classes39 Table III. MIL-STD-1760 safety features54 Table IV. Application comparison. .79 Table V. Reference (0% K-rating) T signal response. .181 Table VI. Variation of T signal response envelope with different K-ratings
29、182 Table VII. Calculation of K-rating for 2T signal response envelope.182 Table VIII. Conversion of AEIS return loss requirements. .188 Table IX. Type A signal path addition laws. .190 Table X. K-rating budget contribution of each aircraft signal path interface. .191 Table XI. Overall K-rating aris
30、ing from return loss. 191 Table XII. Overall performance budget for T signal response. 193 Table XIII. Overall performance budget for 2T signal response. .193 Table XIV. Overall performance budget for 2T bar signal response194 Table XV. Overall performance budget for insertion gain error. 195 Table
31、XVI. Overall performance budget for representative pulse delay and error.196 Table XVII. Overall performance budget for gain misequalization.197 Table XVIII. Overall performance budget for incidental phase modulation198 Table XIX. Overall performance budget for signal noise. 198 Table XX. Video sour
32、ce signal requirements.201 Table XXI. Video sink interface requirements202 Table XXII. Distribution budget. .203 Table XXIII. Minimum continuous current rating at each ASI. .223 Table XXIV. Continuous power available at the MSI. 242 Table XXV. MIL-STD-1760 hardware, primary signal set. .273 Table XX
33、VI. Primary signal set connector requirements (ASI). .276 Table XXVII. Auxiliary signal set connector requirements. 276 Table XXVIII. MIL-STD-1760 hardware, auxiliary signal set278 Table XXIX. MIL-STD-1760 hardware, primary signal set. 284 Table XXX. Primary signal set connector requirements (MSI).2
34、86 Table XXXI. Auxiliary signal set connector requirements (MSI).286 Table XXXII. MIL-STD-1760 hardware, MSI auxiliary signal set287 Table XXXIII. MIL-STD-1760 hardware, primary umbilical. .292 Table XXXIV. Primary signal set connector requirements (umbilical)293 Table XXXV. Auxiliary signal set umb
35、ilical contact requirements. .294 Table XXXVI. MIL-STD-1760 hardware, MSI auxiliary signal set (auxiliary umbilical).294 Table XXXVII. Example MDT data types. 371 Table XXXVIII. TC Message Format376 Table XXXIX. Instruction Word. .377 Table XL. Allowable instruction type field bit states.378 Table X
36、LI. Subaddress select word requirements. 380 Table XLII. Dual Binary Number Word Format. .382 Table XLIII. File number word requirements383 Table XLIV. Record number word requirements385 Table XLV. Block number word requirements. 387 Table XLVI. Checksum word requirements. 390 Table XLVII. Transfer
37、Monitor (TM) message format.391 Table XLVIII. Transfer mode status word. .393 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-1760A viiTABLES PAGE Table XLIX. Allowable mode status field bit states. .394 Table L. Subaddress select word requi
38、rements.395 Table LI. Current file number word requirements. .397 Table LII. Current record number word requirements399 Table LIII. Current block number word requirements.401 Table LIV. Transfer Data (TD) message format.403 Table LV. TC format to initiate download mode.407 Table LVI. TM message form
39、at to indicate not ready for download mode.408 Table LVII. TM message format to indicate in download mode. 409 Table LVIII. TC format to erase all files410 Table LIX. TM message format to indicate erasure in progress. .411 Table LX. TM message format to indicate erasure complete. .412 Table LXI. Exa
40、mple of TC format to erase designated file. .413 Table LXII. Example of TM message format to indicate erasure in progress for designated file erase414 Table LXIII. Example of TM message format to indicate erasure complete for designated file erase415 Table LXIV. TM message format to indicate invalid
41、 erase designated file command416 Table LXV. Example of TC format to erase designated record. 417 Table LXVI. Example of TM message format to indicate erasure in progress for designated record.418 Table LXVII. Example of TM message format to indicate erasure complete designated record erase419 Table
42、 LXVIII. TM message format to indicate invalid erase designated record command. .420 Table LXIX. Example of TC format to start new file/record423 Table LXX. Example of TM message format to indicate not ready for file transfer424 Table LXXI. Example of TM message format to indicate ready to receive f
43、ile transfer425 Table LXXII. Example of TC format to start new file/record with echo mode selected. .427 Table LXXIII. Example of TM message format to indicate ready to receive file transfer with echo mode selected. 429 Table LXXIV. Example of TC format to command file checksum with an embedded chec
44、ksum.431 Table LXXV. Example of TC format to command file checksum. 432 Table LXXVI. Example of TM message format to indicate file checksum in progress.433 Table LXXVII. Example of TM message format to indicate file checksum complete and passed.434 Table LXXVIII. Example of TM message format to indi
45、cate file checksum complete and failed.435 Table LXXIX. Example of TC format to command record checksum with an embedded checksum.436 Table LXXX. Example of TC format to command record checksum437 Table LXXXI. Example of TM message format to indicate record checksum in progress. 438 Table LXXXII. Ex
46、ample of TM message format to indicate record checksum complete and passed. 439 Table LXXXIII. Example of TM message format to indicate record checksum complete and failed. .440 Table LXXXIV. Example of TM message format to indicate retransmission request.442 Table LXXXV. Example of TM message forma
47、t to indicate retransmission complete. 443 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-1760A viii TABLES PAGE Table LXXXVI. Example of TC format to command MDT exit. 444 Table LXXXVII. Example of TM message format to indicate the store i
48、s exiting MDT. .445 Table LXXXVIII. Example of TM message format to indicate the store has exited MDT.446 Table LXXXIX. TC format to initiate upload mode. 448 Table XC. TM message format to indicate not ready for upload mode449 Table XCI. TM message format to indicate in upload mode. .450 Table XCII
49、. Example of TC format to start new file/record for upload452 Table XCIII. Example of TM message format to indicate not ready for upload file transfer.453 Table XCIV. Example of TM message format to indicate ready to transmit file transfer454 Table XCV. Example of TC format for an upload file checksum test. 456 Table XCVI. Example of TM message format to indicate upload file checksum in progress.457 Table XCVII. Example of TM message fo
