A Low Voltage Command-Arm System for Distributed Fuzing

Size: px

Start display at page:

Download "A Low Voltage Command-Arm System for Distributed Fuzing"

Shona Palmer
5 years ago
Views:

A Low Command- System for Distributed Fuzing

NDIA Fuze Conference July 7-9, 05 Baltimore,

1 A Low Command- System for Distributed Fuzing DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. NDIA Fuze Conference July 7-9, 05 Baltimore, MD Presented by: Mark Etheridge U.S. y Aviation and Missile Research, Development, and Engineering Center

Naval Air Warfare Center Adedayo Oyelowo, Naval Surface Warfare

2 Acknowledgements This project is sponsored by the Joint Fuze Technology Panel (JFTP) FATG II (Tailorable Effects) Paul Anderson, Naval Air Warfare Center Adedayo Oyelowo, Naval Surface Warfare Center DISTRIBUTION A. Approved for public release; distribution is unlimited.

3 Project Overview How complex is complex enough?? The 6. JFTP sponsored project was successful in defining some minimal hardware & messaging guidelines. FESWG approval in February, 04. JOTP document has been started. A 6.3 program was accepted by the JFTP to pursue form, fit, and function designs targeting the following programs: Low-Cost Tactical Extended Range Missile (LC-TERM; y). Joint Multi-Effects Warhead System (JMEWS) program (Navy-China Lake). Reliability DPICM Replacement (Navy-Indian Head) JMEWS LC-TERM HRDR 3 DISTRIBUTION A. Approved for public release; distribution is unlimited.

4 Project Overview All designs will be based on the 6. Navy Architecture. Most compliant with the safety standards and feedback regarding low voltage signals. JFTP recommendation to pursue a single design. Goal is Initial Safety Certification or supportability statement from the Service Safety Review Authorities ing Control Unit Logic Logic Weapon uc Trigger Sw HV Data Sw Sequencer 4 DISTRIBUTION A. Approved for public release; distribution is unlimited.

5 Project Overview Some unique aspects of the targeted applications LC-TERM: will include warhead fuzing and rocket motor ignition. HRDR: minimum 56 sub-munitions to arm; available sub-munition volume is very limited. JMEWS: arming environment signals airspeed thru pitot tube and turbogenerator sense signal Block diagrams for all applications have been developed. In beginning stages of detailed designs. 5 DISTRIBUTION A. Approved for public release; distribution is unlimited.

6 How complex is complex enough?? Proposed FESWG guidelines 6 DISTRIBUTION A. Approved for public release; distribution is unlimited.

7 DISCLAIMER!! The following slides are proposed guidelines. They have not been reviewed in detail by any fuze-related Safety Community organization (such as the FESWG) 7 DISTRIBUTION A. Approved for public release; distribution is unlimited.

8 ing Control Unit (i.e. the Master S&A) The ACU shall directly sense, process, and validate the physical arming environments and transmit the subsequent arming signals to the remote firing modules (RFMs). Weapon ing Control Unit Logic Control Environment Environment erometer Simulator Logic ESAF ESAF Built In Test (BIT) Input Input Verification Logic Sequence Verification Logic First Motion ion Safe Separation Distance Calculation Comm To Remote set +5vdc AP Opto Opto TO REMOTE FIRESET Data Validated Intent CLK Analog Profile Clock Delay UQS Generation Comparator Windowing & Sampling Clock Reset Driver Driver Data Clock Validated Intent Analog Profile Comparator Windowing & Sampling UQS Out UQS Line Validated Target Intent Sequence & Reference s Firing Sequence Generation 8 DISTRIBUTION A. Approved for public release; distribution is unlimited.

9 The ACU shall maintain an active link with all RFMs that are in use after the fuze system is properly armed. ing Control Unit Logic Logic Weapon uc Trigger Sw HV Data Status Sw Sequencer 9 DISTRIBUTION A. Approved for public release; distribution is unlimited.

10 The ACU shall source all power for the RFMs including. All power slated for the RFM should be partitioned from other power such as electronics power ing Control Unit Logic Logic Weapon Data uc Trigger Sw Sw HV Sequencer Option ing Control Unit Logic Logic +3.3vdc +.5vdc Option Weapon ` Data uc Trigger Sw HV Sequencer 0 DISTRIBUTION A. Approved for public release; distribution is unlimited.

11 The ACU shall source all power for the RFMs including. All power slated for the RFM should be partitioned from other power such as electronics power ACU RFM- RFM- Option Option ACU RFM- RFM- DISTRIBUTION A. Approved for public release; distribution is unlimited.

12 The ACU may contain one or more static safety feature(s) for the control of to the RFM ing Control Unit ACU Logic Logic +3.3vdc +.5vdc Option (Viable) Weapon Data ACU Logic ing Control Unit SS SS Logic +3.3vdc +.5vdc Option (Maybe) Weapon Data DISTRIBUTION A. Approved for public release; distribution is unlimited.

13 There shall be no inadvertent release of any arming signals by the ACU during and after exposure to power transfers, transitions, and/or transients. There shall be no inadvertent release of any arming signals by the ACU during and after exposure to all credible electromagnetic environments that the applicable weapon system will be exposed to. 3 DISTRIBUTION A. Approved for public release; distribution is unlimited.

14 Remote Firing Module The RFM may be powered utilizing when practicable. Control ing Control Unit Logic Logic Weapon uc Trigger Sw HV Data Sw Sequencer ing Control Unit Logic Logic +3.3vdc +.5vdc Control ing Control Unit Logic Logic +3.3vdc +.5vdc Weapon ` Data uc Trigger Sw HV Sequencer Weapon ` Data uc Trigger Sw HV Sequencer 4 DISTRIBUTION A. Approved for public release; distribution is unlimited.

15 The RFM shall contain at least one static safety feature for interrupting energy to the high voltage transformer. Control Weapon ing Control Unit Logic Data uc Logic Trigger Sw Sw HV Sequencer Weapon ACU Logic ing Control Unit Logic Data +3.3vdc +.5vdc Trigger Sw HV Sequencer ESAF Remote set ESAF Remote set Control Logic +5vdc RFS Logic Control Logic +5vdc RFS Logic Environment Environment erometer Simulator ESAF Built In Test (BIT) Input Input Verification Logic Sequence Verification Logic First Motion ion Safe Separation Distance Calculation Comm To Remote set AP Opto Opto Reset set BIT Input Verification Logic Sequence Verification Logic Clock Driver Logic Delay r Logic Signal Processing SS3 Dyn 3 Environment Environment erometer Simulator ESAF Built In Test (BIT) Input Input Verification Logic Sequence Verification Logic First Motion ion Safe Separation Distance Calculation Comm To Remote set AP Opto Opto Reset set BIT Input Verification Logic Sequence Verification Logic Clock Driver Logic Delay r Logic Signal Processing Dyn Reset Drvr Reset Drvr Driver Data Driver Driver Data Driver Driver Clock Driver HV Level Control Driver Clock Driver HV Level Control 5 DISTRIBUTION A. Approved for public release; distribution is unlimited.

16 for the RFM should be applied as late in the launch sequence or operational deployment as practical. Why?? Additional measure to mitigate the possibility of inadvertent release of low voltage arming signals signal generation for driving the high voltage transformer shall be performed at the RFM. Sequence monitoring shall be performed at the RFM at a minimum. Data uc Logic Trigger Sw HV Sequencer Sw Preference towards discrete Device PWR Clock UQS UQS # / Firing Discrimination UQS # / Firing Discrimination UQS Discrimination UQS_FS UQS_FS seq_fs Sequence Monitor fire_valid fire_valid Failsafe ARM Dyn ARM 6 DISTRIBUTION A. Approved for public release; distribution is unlimited.

17 There shall be no inadvertent activation of any safety features located on the RFM during and after exposure to power transfers, transitions, and/or transients. There shall be no inadvertent activation of any safety features located on the RFM during and after exposure to all credible electromagnetic environments that the applicable weapon system will be exposed to. 7 DISTRIBUTION A. Approved for public release; distribution is unlimited.

18 ing Signals/Commands There shall be a minimum of two arming signals transmitted to the RFM for proper arming of the fuze system. Each command message shall be unambiguous, to the extent possible, from any and all other command messages. Ex: Navy Design utilizes frequency (actually frequency shift) and serial message (minimum 7 bits flipped between! and Safe cmds) If practical, no more than one of the arming signals may be utilized for additional functions within the fuzing system. Ex: Navy Design utilizing the upper frequency of the frequency shift for the signal 8 DISTRIBUTION A. Approved for public release; distribution is unlimited.

19 The generation and transmission of the arming signals shall be implemented with independent logic devices that are physically and functionally partitioned from each other. Where practical, at least one arming signal shall be generated utilizing discrete components. The generation of the arming signals shall be implemented with dissimilar logic devices. The degree of dissimilarity shall be sufficient to ensure that any credible common cause susceptibility will not result in an inadvertent arming signal transmission in other logic devices. The requirements outlined above shall also apply to the processing of the received arming signal at the RFM and subsequent activation of any safety features contained within. 9 DISTRIBUTION A. Approved for public release; distribution is unlimited.

20 Weapon ing Control Unit Logic Validated Intent CLK Analog Profile Clock Delay UQS Generation Comparator Windowing & Sampling Clock Validated Intent Analog Profile Comparator Windowing & Sampling UQS Out UQS Line Discrete Complex Data Dissimilar & Partitioned Validated Target Intent Sequence & Reference s Firing Sequence Generation Logic Device PWR Clock UQS Discrimination UQS_FS UQS_FS seq_fs Failsafe HV UQS # / Firing Discrimination ARM uc Trigger Sw Sequencer UQS Sequence Monitor Dyn Data Sw Dissimilar & Partitioned UQS # / Firing Discrimination fire_valid fire_valid ARM 0 DISTRIBUTION A. Approved for public release; distribution is unlimited.

21 Commands The length of a command message shall be 0 bits at the minimum. This does not include any start, stop, or message reliability bits.. The preferred method for utilizing serial communications is to generate the command word based on events that occur throughout an arming environment. Transmission of the command word will only occur upon verification that the specific arming environment has been achieved.. Question becomes what is the maximum number of bits per event in order to build the message. DISTRIBUTION A. Approved for public release; distribution is unlimited.

22 Where generation of the serial command is not practicable, pre-defined serial commands may be utilized. The commands must be further distinguished by a minimum of two additional features in order to mitigate the possibility of inadvertent release. Features could include multiple (more than two) messages, sequencing, sending each message at a different frequency Susceptibility to improper serial data shall be characterized through sending a minimum of 00,000 randomly generated serial messages to the RFM and monitoring the status of all safety features. If the arming commands contain start, stop, and/or message reliability bits, those bits should be held in a static position within the randomly generated message. DISTRIBUTION A. Approved for public release; distribution is unlimited.

23 QUESTIONS? Mark Etheridge AMRDEC Fuze Office 3 DISTRIBUTION A. Approved for public release; distribution is unlimited.

A Low Voltage Command-Arm System for Distributed Fuzing

A Low Voltage Command-Arm System for Distributed Fuzing DISTRIBUTION STATEMENT A. Approved for Public Release. Distribution is Unlimited NDIA Fuze Conference May 15-17, 2018 San Diego, CA Presented by: