US20050183570A1 - Self-contained airborne smart weapon umbilical control cable - Google Patents
Self-contained airborne smart weapon umbilical control cable Download PDFInfo
- Publication number
- US20050183570A1 US20050183570A1 US10/754,153 US75415304A US2005183570A1 US 20050183570 A1 US20050183570 A1 US 20050183570A1 US 75415304 A US75415304 A US 75415304A US 2005183570 A1 US2005183570 A1 US 2005183570A1
- Authority
- US
- United States
- Prior art keywords
- connector
- signals
- aircraft
- umbilical cable
- smart weapon
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F42—AMMUNITION; BLASTING
- F42C—AMMUNITION FUZES; ARMING OR SAFETY MEANS THEREFOR
- F42C15/00—Arming-means in fuzes; Safety means for preventing premature detonation of fuzes or charges
- F42C15/40—Arming-means in fuzes; Safety means for preventing premature detonation of fuzes or charges wherein the safety or arming action is effected electrically
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/001—Devices or systems for testing or checking
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F41—WEAPONS
- F41G—WEAPON SIGHTS; AIMING
- F41G7/00—Direction control systems for self-propelled missiles
- F41G7/007—Preparatory measures taken before the launching of the guided missiles
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F42—AMMUNITION; BLASTING
- F42C—AMMUNITION FUZES; ARMING OR SAFETY MEANS THEREFOR
- F42C17/00—Fuze-setting apparatus
- F42C17/04—Fuze-setting apparatus for electric fuzes
Definitions
- the present invention relates generally to aircraft and aircraft weaponry. More specifically, the present invention relates to an umbilical cable for connecting a smart weapon to an aircraft not otherwise equipped to handle the smart weapon.
- Smart weapons also referred to as precision guided munitions (PGMs) alter their trajectories in flight to seek, or home on, their targets. Unlike conventional ballistic munitions, their accuracy does not normally diminish as range increases. Generally speaking, smart weapons are divided into four categories, according to their method of homing: command guidance, active, semiactive, and passive. Munitions using command guidance are steered to the target by a remote system or operator that performs all target acquisition, tracking, and guidance functions. Active systems home on their targets using emissions transmitted by the munition itself. Semiactive smart weapons home on energy bounded off the target by an external transmitter, usually aboard the launch platform. Passive systems home on energy emitted by the target.
- PGMs precision guided munitions
- the Tomahawk missile does not actually home on the target but uses on-board radar to generate midcourse guidance corrections for its inertial navigation system.
- ALCM missiles fly to a precise set of coordinates using an inertial guidance system updated by Global Positioning System satellite transmissions.
- Newly produced tactical aircraft are designed to carry and deploy such smart weapons. This, for example, has led to a dramatic reduction in the collateral damage associated with conventional “dumb bombs”.
- the smart weapons typically are secured on a bomb rack which is mounted either in a bomb bay or to pylons under the wing of the aircraft.
- An electrical cable known as an “umbilical cable”, couples the aircraft to a respective smart weapon on the bomb rack.
- the umbilical cable typically runs from the bomb bay support structure or pylon to the smart weapon itself.
- the umbilical cable serves as an electrical connection for delivering power and exchanging data between the aircraft and the smart weapon.
- the smart weapons typically are designed to accept power, data and control information from the aircraft in order to carry out operations.
- the aircraft on the other hand, are designed to provide the appropriate power, data and control information to the umbilical cable via the pylon.
- JDAM Joint Direct Attack Munition
- an umbilical cable for delivering electrical signals between an aircraft and a smart weapon carried by the aircraft.
- the umbilical cable includes cabling comprising a plurality of conductive wires, a first connector provided on one end of the cabling and configured to connect to the aircraft, and a second connector provided on the other end of the cabling and configured to connect to the smart weapon.
- the umbilical cable further includes an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires.
- the interface circuit is configured to receive via the first connector a non-standard combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations.
- the interface circuit is configured to convert the non-standard combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector.
- a method of loading operation data into a smart weapon configured to be loaded on an aircraft.
- the method includes the step of providing an umbilical cable, the umbilical cable having cabling with a plurality of conductive wires, a first connector provided on one end of the cabling and configured to connect to the aircraft, and a second connector provided on the other end of the cabling and configured to connect to the smart weapon.
- the umbilical cable includes an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires.
- the interface circuit is configured to receive via the first connector a combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations, to convert the combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector.
- the method further includes the steps of temporarily connecting at least one of the first connector and the second connector to a ground loading device, and transmitting the operation data from the ground loading device to the umbilical cable and storing the operation data within the umbilical cable.
- FIG. 1 is an environmental view in partial cutaway illustrating a smart weapon umbilical cable in accordance with the present invention coupling a smart weapon to an aircraft;
- FIG. 2 is a schematic illustration of a smart weapon umbilical cable in accordance with an embodiment of the present invention
- FIG. 3 is an electrical schematic of a smart weapon umbilical cable in accordance with an embodiment the present invention.
- FIG. 4 illustrates a ground loading device communicating with the smart weapon via the umbilical cable in accordance with an embodiment of the present invention
- FIGS. 5, 6 and 7 represent different ways for providing communications between the aircraft and the smart weapon via the umbilical cable in accordance with respective embodiments of the present invention
- FIG. 8 illustrates an umbilical cable with a built-in display in accordance with another embodiment of the present invention.
- FIG. 9 illustrates still another embodiment of the umbilical cable of the present invention.
- the present invention relates to an umbilical cable for connecting a smart weapon to an aircraft that is not otherwise equipped to handle the smart weapon.
- a smart weapon 10 is shown mounted to the wing 12 of an aircraft.
- the wing 12 includes one or more pylons 14 secured to the underside of the wing 12 .
- Each pylon typically supports a bomb rack 16 used to secure various types of weapons.
- the weapon 10 is a smart weapon, i.e., one capable of altering its trajectory in flight to seek, or home on, its target.
- the smart weapon 10 is a JDAM or other MIL-STD-1760 type smart weapon.
- the smart weapon 10 could be any other type of smart weapon without departing from the scope of the invention.
- the aircraft is electrically coupled to the smart weapon 10 via an umbilical cable 18 .
- the umbilical cable 18 couples power, control and/or data signals between the aircraft and the smart weapon 10 which allow the smart weapon 10 to carry out its operations.
- the aircraft may provide power and target coordinate data to the smart weapon 10 .
- the smart weapon 10 may, in turn, provide status information, etc., to the aircraft.
- the aircraft according to the present invention is not equipped to communicate with the particular type of smart weapon 10 .
- the aircraft may not include the aforementioned MIL-STD-1553 databus or any other type standard databus intended for communicating with a particular smart weapon 10 .
- the aircraft may not have the necessary control systems to provide the MIL-STD-1760 control to the smart weapon 10 , for example.
- the umbilical cable 18 of the present invention allows such an aircraft to nevertheless control and utilize the smart weapon 10 .
- the umbilical cable 18 includes at one end of a piece of cabling 20 a first connector 22 configured to connect to the aircraft.
- the connector 22 mates to a connector 24 included in the pylon 14 .
- the umbilical cable 18 further includes a second connector 26 at the other end of the cabling 20 .
- the second connector 26 is designed to mate with the connector 28 included in the smart weapon 10 .
- the second connector 26 is designed to disconnect or release from the connector 28 upon the smart weapon 10 being released from the bomb rack 16 .
- the first and second connectors 22 and 26 may each include multiple sub-connectors as needed to properly connect to the aircraft/weapon.
- the aircraft in accordance with the present invention is not originally equipped to communicate with the smart weapon 10 via a standard smart weapon communications interface, the aircraft instead provides a non-standard combination of signals to the smart weapon 10 via the umbilical cable 18 .
- the umbilical cable 18 of the present invention makes it possible for the aircraft simply to provide a combination of conventional “dumb” weapon power and control signals (e.g., 28 volts power lines, Master Arm signal, Nose Arm signal, Tail Arm signal, etc.), yet still carry out smart weapon operations.
- Such conventional signals are typically available at the pylon 14 /bomb rack 16 interface.
- the connector 24 in the pylon 14 may be hardwired easily to include these signals and to provide the signals to the smart weapon 10 via the umbilical cable 18 .
- This non-standard combination of signals is not receivable directly by the smart weapon so as to enable the smart weapon to carry out operations.
- the umbilical cable 18 includes an interface circuit 30 coupled between the first connector 22 and the second connector 26 via the wires within the cabling 20 .
- the interface circuit 30 is configured to receive the non-standard combination of signals from the aircraft and to convert the non-standard combination of signals to a set of signals receivable by the smart weapon 10 to carry out operations.
- the interface circuit 30 is configured to provide the set of receivable signals to the smart weapon 10 .
- the umbilical cable 18 and interface circuit 30 may be designed to control or manipulate certain specific circuits in the aircraft by electrically toggling voltages or ground, depending on these specific functions and requirements.
- the types of aircraft which will benefit most from the present invention do not have standardized smart weapon interfaces.
- the umbilical cable 18 and the interface circuit 30 therein must be configured for the specific aircraft.
- the interface 30 is designed to utilize crew controlled circuits which are typically available, to provide for basic weapon required commands.
- discrete signals such as Nose Arm, Tail Arm, Station Select and Rocket Select can be sensed by the interface circuit 30 to control functions such as preprogrammed target selection or ballistic release override.
- the umbilical cable of the present invention may be used to allow a tactical aircraft to control many different types of weapons, which the aircraft would not otherwise be capable or equipped to control.
- An exemplary yet main weapon type intended for the application of this invention are those of the MIL-STD 1760 type. These weapons are designed to operate controlled by a standardized set of electrical power and signal circuits, including MIL-STD-1553 data bus commands.
- the interface circuit in the umbilical cable described by the invention is designed to provide the complete 1553 data bus control command sequences required by a particular weapon. This self contained 1553 capability is a feature of the invention.
- Inputs to this circuitry from the aircraft are either operating power inputs or “generic data inputs” such as navigation information which is interpreted and translated by the stand alone umbilical cable control circuitry.
- the umbilical cable circuitry can be designed to accept and react to specific existing aircraft signals normally present at weapon electrical interfaces, such as Master Arm, Nose Arming, Tail Arming, Normal Release, etc. These discrete voltage signals would be used to provide the pilot with direct control over specific aspects of the weapon control sequence process, from both the operational and safety aspects as required by prudent design guidelines.
- the umbilical cable 18 is shown in more detail.
- the umbilical cable 18 is typically on the order of about 11 ⁇ 2 to 2 feet long.
- the cabling 20 includes appropriate conductive wires for coupling signals between the aircraft/connector 22 and the smart weapon 10 /connector 26 , as will be appreciated.
- the interface circuit 30 is disposed approximately midway within the cabling 20 in what will typically be an expanded portion of the cabling. In an alternate embodiment, the interface 30 may be located elsewhere in the umbilical cable 18 as is discussed below in association with FIG. 9 , for example.
- the connectors 22 and 26 include backshells 32 and 34 , respectively, as are known in the art.
- FIG. 3 represents an exemplary embodiment of the umbilical cable 18 in accordance with the invention.
- the aircraft electronics (represented generally by block 40 ) are capable of providing conventional “dumb weapon” discrete control signals referred to as Normal Release, and Master Arm.
- the electronics 40 are capable of providing 28 volts DC.
- Each of these control signals and power signals is coupled to the umbilical cable 18 via the connector 22 coupled to the aircraft.
- a simple communication link such as a two wire databus may be present in the aircraft and provided to the umbilical cable 18 .
- the aircraft may be modified at relatively small expense to provide such simple type communication link.
- the particular combination of non-standard signals which the aircraft provides to the umbilical cable 18 will depend largely on the particular signals available in the aircraft and the particular level of control desired with the smart weapon 10 .
- the aircraft provides a supply voltage of 28 VDC and a supply voltage return to the umbilical cable 18 on lines 44 and 46 , respectively, via the connector 22 .
- the aircraft provides a Normal Release signal on line 48 and a Master Arm signal on line 50 .
- the Normal Release signal is a signal derived from the pilot's weapon release button, and is found even in aircraft not equipped to handle smart weapons.
- the Master Arm signal is a signal derived from the pilot's master arm button which signifies a request to arm the weapon. The Master Arm signal is also found even in aircraft not equipped to handle smart weapons.
- a structural ground is provided on line 52 of the umbilical cable 18 .
- the structural ground typically is acquired from the body of the aircraft via contact with the connector 22 .
- the aircraft may optionally provide some type of data communication link to the umbilical cable 18 such as a two-wire communication link 54 .
- a communication link 54 is not necessary, but can expand the operations of the smart weapon 10 .
- the interface circuit 30 shown in more detail in FIG. 3 , is designed to convert the non-standard combination of signals provided by the aircraft into a set of signals which may be used to operate the smart weapon 10 .
- the specific configuration of the interface circuit 30 will depend largely on the particular signals provided by the aircraft and the design of the smart weapon, as will be appreciated. However, those having ordinary skill in the art will appreciate based on the disclosure presented herein how to configure such an interface circuit 30 for a given aircraft and weapon 10 in accordance with the present invention. Thus, while a particular configuration of the interface circuit 30 is described herein, it will be appreciated that the present invention is not intended to be limited thereto.
- the interface circuit 30 receives the supply voltage on line 44 .
- the interface circuit 30 includes a reverse polarity diode 56 thru which the supply voltage is passed, and the interface circuit 30 provides the supply voltage to the smart weapon 10 via line 58 coupled to the connector 26 .
- the aircraft is capable of providing operating power to the smart weapon 10 .
- the interface circuit 30 may include an appropriate voltage converter as will be appreciated.
- the supply voltage return on line 46 passes thru the interface circuit 30 and is provided to the smart weapon 10 via line 60 coupled to the connector 26 .
- the connector 26 is designed to mate with a JDAM MIL-STD-1760 type connector on the smart weapon 10 .
- the MIL-STD-1760 weapon interface standard requires a primary and a secondary 28 VDC power circuit.
- the primary power circuit is essentially continuously providing constant, steady DC power for internal weapon circuitry.
- the secondary 28VDC power circuit is not constant, but must be closely controlled.
- the secondary power circuit is to be powered only if the weapon is properly prepared for release, and also only if release is imminent.
- the interface circuit 30 is designed to activate and deactivate the secondary power output circuit as required.
- the umbilical cable 18 provides a second supply voltage to the connector 26 via line 62 , an a second supply voltage return via line 64 .
- the second supply voltage on line 62 is provided via a logic circuit and communication control section 66 included in the interface circuit 30 .
- the logic circuit and communication control section 66 is designed to activate and deactivate the secondary power output on line 62 as required for proper weapon control.
- the interface circuit 30 may provide the second return line 64 simply by tapping off line 60 .
- the interface circuit 30 includes the logic circuit and communication control section 66 as shown in FIG. 3 .
- the interface circuit 30 includes a bus controller 68 coupled to the logic circuit and communication control section 66 .
- the logic circuit and communication control section 66 includes appropriate logic and circuitry for receiving and processing the non-standard combination of signals from the aircraft.
- the logic circuit and communication control section 66 is designed to convert the non-standard combination of signals from the aircraft into a format compatible with the particular bus controller 68 and interface (e.g., MIL-STD-1760) conventionally used by the smart weapon 10 .
- the logic circuit and communication control section 66 may be configured to provide any appropriate discrete signals directly to the smart weapon 10 .
- Such discretes include, for example, a Release Consent control signal as represented on line 70 .
- the Release Consent control signal according to the MIL-STD-1760 standard is analogous to the Master Arm signal on line 50 , and may be generated based thereon.
- the logic circuit and communication control section 66 compiles data and control information to the extent necessary from the non-standard combination of discretes (e.g., Normal Release) and the communication link 54 .
- the logic circuit and communication control section 66 provides the data in an appropriate format to the bus controller 68 so it may in turn be provided to the smart weapon 10 .
- the bus controller 68 is a MIL-STD-1553 databus conventionally used to communicate with the JDAM via the MIL-STD-1760 interface.
- the bus controller 68 is coupled to the interface via redundant databuses 72 and 74 standard in the MIL-STD-1760 interface.
- the logic circuit and communication control section 66 and the bus controller 68 have been described primarily in terms of communications from the aircraft to the smart weapon 10 . However, it will be appreciated that the control section 66 and bus controller 68 also can provide for bidirectional communications between the aircraft and the smart weapon 10 . For example, the smart weapon 10 can provide operation status, fault information, etc., via the bus controller 68 and the control section 66 .
- the interface circuit 30 also includes a memory 76 coupled to the logic circuit and communication control section 66 and/or the bus controller 68 .
- the memory 76 serves to store relevant data, such as target coordinates, necessary for the operation of the smart weapon.
- the memory 76 may serve as a working memory for the control section 66 and/or the bus controller 68 .
- the interface circuit 30 may include an optional display 78 for displaying relevant information.
- the display 78 may be used to display target coordinate data which is programmed into the smart weapon 10 as described more fully below.
- the logic circuit and communication control interface 66 and the bus controller 68 may be made of discrete components and/or an application specific integrated circuit (ASIC). As mentioned above, the particular design of the logic circuit and communication control interface 66 and the bus controller 68 will be appreciated by those having ordinary skill in the art in view of the particular signals available to the smart weapon 10 from the aircraft via the umbilical cable 18 and the desired degree of control. Therefore, detail as to the specifics of such circuitry has been omitted for sake of brevity.
- the logic circuit and communication control interface 66 and the bus controller 68 each may derive their necessary operating power from the supply voltage provided via lines 44 and 46 , as will be appreciated.
- the umbilical cable 18 as shown in FIG. 3 also includes interlock and interlock return lines 80 and 82 , respectively, coupled to the connector 26 .
- lines 80 and 82 are hardwired together within the cable 18 . Continuity between these two lines informs the smart weapon 10 that it is connected to the aircraft umbilical cable 18 .
- the logic circuit and communication control section 66 can be configured to sense a connection of the connector 22 to the aircraft and the connector 26 to the smart weapon 10 as a condition precedent to providing continuity between lines 80 and 82 .
- the umbilical cable 18 includes addressing lines 84 .
- the addressing lines may be hardwired within the cable 18 via jumpers or the like to define a fixed address for the smart weapon 10 .
- the addressing lines 84 may be coupled to bus controller 68 which in turn outputs the appropriate addressing.
- a basic manner for operating the smart weapon 10 provides for ground loading of target data (e.g., target coordinates).
- target data is loaded into the umbilical cable 18 by temporarily coupling the connector 26 at the weapon end of the umbilical cable 18 to a ground loading device 86 .
- the smart weapon 10 may be mounted to the aircraft at the time.
- the umbilical cable 18 need not be coupled to the smart weapon 10 .
- the target data is simply loaded into the umbilical cable 18 using the ground loading device 86 , and is stored in the memory 76 .
- the umbilical cable 18 remains connected at the opposite end to the aircraft via connector 22 . This minimizes the possibility of targeting errors.
- the ground loading device 86 loads targeting data into the umbilical cable 18 , the umbilical cable 18 is subsequently connected to the smart weapon 10 .
- the target data thus previously loaded in the umbilical cable 18 is then provided to the smart weapon 10 from the umbilical cable 18 during normal aircraft operation.
- the ground loading device 86 may be a computer, preferably of the hand-held variety.
- the ground loading device 86 is programmed to provide target data such as target coordinates to the umbilical cable 18 according to a predefined format.
- the ground loading device 86 preferably is coupled to the smart weapon end of the umbilical cable 18 .
- an alternate embodiment may utilize the aircraft end of the cable 18 to program the umbilical cable 18 via the communication link 54 .
- the ground loading device 86 includes an input/output port with a cable 88 designed to mate to the connector 26 .
- the ground loading device 86 provides the target data to the logic circuit and communication control section 66 via databuses 72 and 74 in accordance with the bus controller 68 protocol.
- the control section 66 stores the target data in the memory 76 . These commands are then provided to the smart weapon 10 via the databuses 72 and 74 during normal aircraft operation.
- the various discretes provided by the aircraft can serve as possible inputs for specific sequence initiation, target alternatives, etc.
- FIG. 4 allows for ground personnel to program target data for the smart weapon via the umbilical cable 18 .
- Such operation is advantageous as virtually no aircraft modifications are necessary.
- the discrete control signals necessary from the crew in flight are available already at the pylon or bomb bay as described above.
- virtually any aircraft can be made smart weapon capable at very little expense using the umbilical cable 18 of the present invention.
- a simple communication link e.g., non-MIL-STD-1553
- a simple communication link such as a two-wire bus for the aforementioned two-wire communication link 54 may be added to the aircraft at relatively minimal expense. This allows the pilot to target or retarget the smart weapon 10 while in flight.
- FIG. 5 illustrates an embodiment in which a two-wire bus (labeled as corresponding communication link 54 ) is run from the cockpit of the aircraft to the pylon connector 24 .
- the pilot may have a portable hand-held processor device 90 such as a commonly available personal digital assistant (PDA) from Palm (e.g., the Palm PilotTM), Casio, Dell, etc.
- PDA personal digital assistant
- the PDA device 90 includes an I/O port which is hardwired via an appropriate interface 92 to the communication link 54 . This allows the pilot to input relevant data such as target data (e.g., coordinate data) or the like.
- the PDA device 90 may be strapped to the knee of the pilot, and be configured to allow the pilot to input the data via a touchscreen 94 or the like.
- the umbilical cable 18 receives the data via the communication link 54 , and converts the data to a set of signals receivable by the smart weapon 10 . In this manner, full in-flight re-targeting capability is provided
- FIG. 6 illustrates a variation of the embodiment of FIG. 5 .
- the PDA device 90 is wirelessly linked to the communication link 54 . More specifically, the PDA device 90 may include a small infrared (IR), radio frequency (RF) or other type I/O port. Located preferably inside the cockpit is an appropriate interface 92 ′ for receiving and transmitting wireless communications between the interface circuit 30 in the umbilical cable 18 and the PDA device 90 .
- IR infrared
- RF radio frequency
- FIG. 7 generically represents the feature of the invention whereby any available data, discrete signals, etc. from the aircraft may serve as the source of the non-standard combination of signals provided to the umbilical cable 18 .
- any available data, discrete signals, etc. from the aircraft may serve as the source of the non-standard combination of signals provided to the umbilical cable 18 .
- navigation data, GPS data, altitude data, air speed data, etc. all may be provided to the smart weapon 10 as needed.
- the information may be hardwired to the connector 24 , or sent via a communication link 54 either automatically, if configured, or by manual entry by the pilot as described above in connection with FIGS. 5 and 6 .
- the umbilical cable 18 is designed, with knowledge of the particular information available from the aircraft and the particular smart weapon involved, the convert the information into a set of signals receivable by the smart weapon 10 in order to carry out operations.
- FIG. 8 illustrates another alternative embodiment of the present invention.
- the umbilical cable 18 includes the display 78 (see, FIG. 3 ) in the backshell 32 of the connector 22 .
- the display 78 is useful, for example, in providing verification of the target data stored in the memory. For example, when the umbilical cable 18 is loaded with target data in the manner described above in relation to FIG. 4 , the target data may be verified even after the umbilical cable 18 is disconnected from the ground loading device 86 and reconnected to the weapon. Additionally, or in the alternative, the display 78 may be used to display status information, fault information, or the like provided by the internal cable circuitry.
- the display 78 may be any type of display (e.g., numeric, alphanumeric, simple status indicator lights, etc.) without departing from the scope of the invention.
- the display 78 may be an liquid crystal display (LCD), light emitting diode (LED) display, or any other type of suitable display.
- LCD liquid crystal display
- LED light emitting diode
- the display 78 is shown as being located in the backshell 32 of the connector 22 , it could instead be located in the backshell 34 , or elsewhere along the umbilical cable 18 without departing from the scope of the invention as will be appreciated.
- FIG. 9 illustrates an embodiment in which the interface circuit 30 is located in the backshell 32 of the connector 22 .
- the interface circuit 30 may be included in the backshell 34 of the connector 26 .
- another embodiment may include the interface circuit 30 split and located in the back shells 32 and 34 of both connectors. Any of these embodiments may include a display 78 also.
Abstract
An umbilical cable for delivering electrical signals between an aircraft and a smart weapon carried by the aircraft. The umbilical cable includes cabling comprising a plurality of conductive wires, a first connector provided on one end of the cabling and configured to connect to the aircraft, and a second connector provided on the other end of the cabling and configured to connect to the smart weapon. The umbilical cable further includes an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires. The interface circuit is configured to receive via the first connector a non-standard combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations. Moreover, the interface circuit is configured to convert the non-standard combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector.
Description
- The present invention relates generally to aircraft and aircraft weaponry. More specifically, the present invention relates to an umbilical cable for connecting a smart weapon to an aircraft not otherwise equipped to handle the smart weapon.
- “Smart” weapons, also referred to as precision guided munitions (PGMs), alter their trajectories in flight to seek, or home on, their targets. Unlike conventional ballistic munitions, their accuracy does not normally diminish as range increases. Generally speaking, smart weapons are divided into four categories, according to their method of homing: command guidance, active, semiactive, and passive. Munitions using command guidance are steered to the target by a remote system or operator that performs all target acquisition, tracking, and guidance functions. Active systems home on their targets using emissions transmitted by the munition itself. Semiactive smart weapons home on energy bounded off the target by an external transmitter, usually aboard the launch platform. Passive systems home on energy emitted by the target.
- Some smart weapons do not fit cleanly in the above typology. For example, the Tomahawk missile does not actually home on the target but uses on-board radar to generate midcourse guidance corrections for its inertial navigation system. ALCM missiles fly to a precise set of coordinates using an inertial guidance system updated by Global Positioning System satellite transmissions.
- Newly produced tactical aircraft are designed to carry and deploy such smart weapons. This, for example, has led to a dramatic reduction in the collateral damage associated with conventional “dumb bombs”. The smart weapons typically are secured on a bomb rack which is mounted either in a bomb bay or to pylons under the wing of the aircraft. An electrical cable, known as an “umbilical cable”, couples the aircraft to a respective smart weapon on the bomb rack. The umbilical cable typically runs from the bomb bay support structure or pylon to the smart weapon itself.
- The umbilical cable serves as an electrical connection for delivering power and exchanging data between the aircraft and the smart weapon. The smart weapons typically are designed to accept power, data and control information from the aircraft in order to carry out operations. The aircraft, on the other hand, are designed to provide the appropriate power, data and control information to the umbilical cable via the pylon.
- For example, newly produced tactical aircraft are internally wired with the MIL-STD-1553 databus for coupling to the MIL-STD-1760 standard weapons interface. Smart weapons such as the Joint Direct Attack Munition (JDAM) are designed to communicate with the aircraft via such interface to obtain information from the aircraft such as coordinate data, etc., in order to carry out operations.
- Unfortunately, there is a significant number of older aircraft that are still in use today but are not properly equipped to handle smart weapons. For example, such aircraft may not include the MIL-STD-1553 databus and thus are unable to communicate with a smart weapon such as the JDAM. Replacing the older aircraft, which are otherwise perfectly functional, is extremely expensive considering the cost of modern military aircraft. However, even retrofitting an older aircraft to include the necessary wiring (e.g., databus) and sophisticated avionics to provide the necessary information to a smart weapon is very costly. Consequently, many older aircraft today remain unable to handle smart weapons and therefore their operators cannot make use of the advantages associated therewith.
- In view of the aforementioned shortcomings, there remains a strong need in the art for means to enable aircraft not equipped to handle smart weapons to nevertheless do so.
- According to one aspect of the invention, an umbilical cable is provided for delivering electrical signals between an aircraft and a smart weapon carried by the aircraft. The umbilical cable includes cabling comprising a plurality of conductive wires, a first connector provided on one end of the cabling and configured to connect to the aircraft, and a second connector provided on the other end of the cabling and configured to connect to the smart weapon. The umbilical cable further includes an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires. The interface circuit is configured to receive via the first connector a non-standard combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations. Moreover, the interface circuit is configured to convert the non-standard combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector.
- According to another aspect of the invention, provided is a method of loading operation data into a smart weapon configured to be loaded on an aircraft. The method includes the step of providing an umbilical cable, the umbilical cable having cabling with a plurality of conductive wires, a first connector provided on one end of the cabling and configured to connect to the aircraft, and a second connector provided on the other end of the cabling and configured to connect to the smart weapon. In addition, the umbilical cable includes an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires. The interface circuit is configured to receive via the first connector a combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations, to convert the combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector. The method further includes the steps of temporarily connecting at least one of the first connector and the second connector to a ground loading device, and transmitting the operation data from the ground loading device to the umbilical cable and storing the operation data within the umbilical cable.
- To the accomplishment of the foregoing and related ends, the invention, then, comprises the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative embodiments of the invention. These embodiments are indicative, however, of but a few of the various ways in which the principles of the invention may be employed. Other objects, advantages and novel features of the invention will become apparent from the following detailed description of the invention when considered in conjunction with the drawings.
-
FIG. 1 is an environmental view in partial cutaway illustrating a smart weapon umbilical cable in accordance with the present invention coupling a smart weapon to an aircraft; -
FIG. 2 is a schematic illustration of a smart weapon umbilical cable in accordance with an embodiment of the present invention; -
FIG. 3 is an electrical schematic of a smart weapon umbilical cable in accordance with an embodiment the present invention; -
FIG. 4 illustrates a ground loading device communicating with the smart weapon via the umbilical cable in accordance with an embodiment of the present invention; -
FIGS. 5, 6 and 7 represent different ways for providing communications between the aircraft and the smart weapon via the umbilical cable in accordance with respective embodiments of the present invention; -
FIG. 8 illustrates an umbilical cable with a built-in display in accordance with another embodiment of the present invention; and -
FIG. 9 illustrates still another embodiment of the umbilical cable of the present invention. - The present invention will now be described in detail with reference to the drawings, in which like reference numerals are used to refer to like elements throughout.
- The present invention relates to an umbilical cable for connecting a smart weapon to an aircraft that is not otherwise equipped to handle the smart weapon. Referring initially to
FIG. 1 , asmart weapon 10 is shown mounted to thewing 12 of an aircraft. As is typical, thewing 12 includes one ormore pylons 14 secured to the underside of thewing 12. Each pylon typically supports abomb rack 16 used to secure various types of weapons. - In accordance with the present invention, the
weapon 10 is a smart weapon, i.e., one capable of altering its trajectory in flight to seek, or home on, its target. In an exemplary embodiment described herein, thesmart weapon 10 is a JDAM or other MIL-STD-1760 type smart weapon. However, it will be appreciated that thesmart weapon 10 could be any other type of smart weapon without departing from the scope of the invention. - According to the invention, the aircraft is electrically coupled to the
smart weapon 10 via anumbilical cable 18. Theumbilical cable 18 couples power, control and/or data signals between the aircraft and thesmart weapon 10 which allow thesmart weapon 10 to carry out its operations. For example, the aircraft may provide power and target coordinate data to thesmart weapon 10. Thesmart weapon 10 may, in turn, provide status information, etc., to the aircraft. - Unlike current state of the art aircraft which are designed to communicate with the
smart weapon 10 in accordance with predefined standards, the aircraft according to the present invention is not equipped to communicate with the particular type ofsmart weapon 10. For example, the aircraft may not include the aforementioned MIL-STD-1553 databus or any other type standard databus intended for communicating with a particularsmart weapon 10. Moreover, the aircraft may not have the necessary control systems to provide the MIL-STD-1760 control to thesmart weapon 10, for example. - The
umbilical cable 18 of the present invention, on the other hand, allows such an aircraft to nevertheless control and utilize thesmart weapon 10. As will be described in more detail below, theumbilical cable 18 includes at one end of a piece of cabling 20 afirst connector 22 configured to connect to the aircraft. Typically, theconnector 22 mates to aconnector 24 included in thepylon 14. Theumbilical cable 18 further includes asecond connector 26 at the other end of thecabling 20. Thesecond connector 26 is designed to mate with theconnector 28 included in thesmart weapon 10. As is typical, thesecond connector 26 is designed to disconnect or release from theconnector 28 upon thesmart weapon 10 being released from thebomb rack 16. As will be appreciated, the first andsecond connectors 22 and 26 (and mated connectors) may each include multiple sub-connectors as needed to properly connect to the aircraft/weapon. - Since the aircraft in accordance with the present invention is not originally equipped to communicate with the
smart weapon 10 via a standard smart weapon communications interface, the aircraft instead provides a non-standard combination of signals to thesmart weapon 10 via theumbilical cable 18. More specifically, theumbilical cable 18 of the present invention makes it possible for the aircraft simply to provide a combination of conventional “dumb” weapon power and control signals (e.g., 28 volts power lines, Master Arm signal, Nose Arm signal, Tail Arm signal, etc.), yet still carry out smart weapon operations. Such conventional signals are typically available at thepylon 14/bomb rack 16 interface. Theconnector 24 in thepylon 14 may be hardwired easily to include these signals and to provide the signals to thesmart weapon 10 via theumbilical cable 18. This non-standard combination of signals is not receivable directly by the smart weapon so as to enable the smart weapon to carry out operations. - According to the present invention, however, the
umbilical cable 18 includes aninterface circuit 30 coupled between thefirst connector 22 and thesecond connector 26 via the wires within thecabling 20. Theinterface circuit 30 is configured to receive the non-standard combination of signals from the aircraft and to convert the non-standard combination of signals to a set of signals receivable by thesmart weapon 10 to carry out operations. Moreover, theinterface circuit 30 is configured to provide the set of receivable signals to thesmart weapon 10. Further, theumbilical cable 18 andinterface circuit 30 may be designed to control or manipulate certain specific circuits in the aircraft by electrically toggling voltages or ground, depending on these specific functions and requirements. - The types of aircraft which will benefit most from the present invention do not have standardized smart weapon interfaces. The
umbilical cable 18 and theinterface circuit 30 therein must be configured for the specific aircraft. Theinterface 30 is designed to utilize crew controlled circuits which are typically available, to provide for basic weapon required commands. Depending on the particular aircraft, discrete signals such as Nose Arm, Tail Arm, Station Select and Rocket Select can be sensed by theinterface circuit 30 to control functions such as preprogrammed target selection or ballistic release override. - As is described in more detail below, the umbilical cable of the present invention may be used to allow a tactical aircraft to control many different types of weapons, which the aircraft would not otherwise be capable or equipped to control. An exemplary yet main weapon type intended for the application of this invention are those of the MIL-
STD 1760 type. These weapons are designed to operate controlled by a standardized set of electrical power and signal circuits, including MIL-STD-1553 data bus commands. As such, the interface circuit in the umbilical cable described by the invention is designed to provide the complete 1553 data bus control command sequences required by a particular weapon. This self contained 1553 capability is a feature of the invention. Inputs to this circuitry from the aircraft are either operating power inputs or “generic data inputs” such as navigation information which is interpreted and translated by the stand alone umbilical cable control circuitry. Additionally, the umbilical cable circuitry can be designed to accept and react to specific existing aircraft signals normally present at weapon electrical interfaces, such as Master Arm, Nose Arming, Tail Arming, Normal Release, etc. These discrete voltage signals would be used to provide the pilot with direct control over specific aspects of the weapon control sequence process, from both the operational and safety aspects as required by prudent design guidelines. These circuit inputs would normally be inputted to the umbilical cable control circuitry, where the presence or absence of their voltage would be interpreted by the imbedded software and key the appropriate 1760 output to the weapon, whether that output be a discrete signal such as28VDC# 2 or a specific sequence of 1553 commands to the weapon's data bus input pins. - Referring briefly to
FIG. 2 , theumbilical cable 18 is shown in more detail. Theumbilical cable 18 is typically on the order of about 1½ to 2 feet long. Thecabling 20 includes appropriate conductive wires for coupling signals between the aircraft/connector 22 and thesmart weapon 10/connector 26, as will be appreciated. In the exemplary embodiment, theinterface circuit 30 is disposed approximately midway within thecabling 20 in what will typically be an expanded portion of the cabling. In an alternate embodiment, theinterface 30 may be located elsewhere in theumbilical cable 18 as is discussed below in association withFIG. 9 , for example. Theconnectors -
FIG. 3 represents an exemplary embodiment of theumbilical cable 18 in accordance with the invention. In this example, the aircraft electronics (represented generally by block 40) are capable of providing conventional “dumb weapon” discrete control signals referred to as Normal Release, and Master Arm. In addition, theelectronics 40 are capable of providing 28 volts DC. Each of these control signals and power signals is coupled to theumbilical cable 18 via theconnector 22 coupled to the aircraft. As an additional option, a simple communication link such as a two wire databus may be present in the aircraft and provided to theumbilical cable 18. Alternatively, the aircraft may be modified at relatively small expense to provide such simple type communication link. As will be appreciated, the particular combination of non-standard signals which the aircraft provides to theumbilical cable 18 will depend largely on the particular signals available in the aircraft and the particular level of control desired with thesmart weapon 10. - As is shown in
FIG. 3 , the aircraft provides a supply voltage of 28 VDC and a supply voltage return to theumbilical cable 18 onlines connector 22. In addition, the aircraft provides a Normal Release signal online 48 and a Master Arm signal online 50. The Normal Release signal is a signal derived from the pilot's weapon release button, and is found even in aircraft not equipped to handle smart weapons. The Master Arm signal is a signal derived from the pilot's master arm button which signifies a request to arm the weapon. The Master Arm signal is also found even in aircraft not equipped to handle smart weapons. - A structural ground is provided on
line 52 of theumbilical cable 18. The structural ground typically is acquired from the body of the aircraft via contact with theconnector 22. As mentioned above, the aircraft may optionally provide some type of data communication link to theumbilical cable 18 such as a two-wire communication link 54. For reasons explained below, such acommunication link 54 is not necessary, but can expand the operations of thesmart weapon 10. - The
interface circuit 30, shown in more detail inFIG. 3 , is designed to convert the non-standard combination of signals provided by the aircraft into a set of signals which may be used to operate thesmart weapon 10. The specific configuration of theinterface circuit 30 will depend largely on the particular signals provided by the aircraft and the design of the smart weapon, as will be appreciated. However, those having ordinary skill in the art will appreciate based on the disclosure presented herein how to configure such aninterface circuit 30 for a given aircraft andweapon 10 in accordance with the present invention. Thus, while a particular configuration of theinterface circuit 30 is described herein, it will be appreciated that the present invention is not intended to be limited thereto. - In the exemplary embodiment, the
interface circuit 30 receives the supply voltage online 44. Theinterface circuit 30 includes areverse polarity diode 56 thru which the supply voltage is passed, and theinterface circuit 30 provides the supply voltage to thesmart weapon 10 vialine 58 coupled to theconnector 26. In this manner, the aircraft is capable of providing operating power to thesmart weapon 10. Should thesmart weapon 10 operate on a voltage other than that available from the aircraft, theinterface circuit 30 may include an appropriate voltage converter as will be appreciated. - The supply voltage return on
line 46 passes thru theinterface circuit 30 and is provided to thesmart weapon 10 vialine 60 coupled to theconnector 26. In the case where thesmart weapon 10 is a JDAM as in the exemplary embodiment, theconnector 26 is designed to mate with a JDAM MIL-STD-1760 type connector on thesmart weapon 10. The MIL-STD-1760 weapon interface standard requires a primary and a secondary 28 VDC power circuit. The primary power circuit is essentially continuously providing constant, steady DC power for internal weapon circuitry. The secondary 28VDC power circuit is not constant, but must be closely controlled. The secondary power circuit is to be powered only if the weapon is properly prepared for release, and also only if release is imminent. In order to provide proper weapon control, theinterface circuit 30 is designed to activate and deactivate the secondary power output circuit as required. - Thus, in addition to
lines umbilical cable 18 provides a second supply voltage to theconnector 26 vialine 62, an a second supply voltage return vialine 64. The second supply voltage online 62 is provided via a logic circuit andcommunication control section 66 included in theinterface circuit 30. The logic circuit andcommunication control section 66 is designed to activate and deactivate the secondary power output online 62 as required for proper weapon control. Theinterface circuit 30 may provide thesecond return line 64 simply by tapping offline 60. - As mentioned above, the
interface circuit 30 includes the logic circuit andcommunication control section 66 as shown inFIG. 3 . In addition, theinterface circuit 30 includes abus controller 68 coupled to the logic circuit andcommunication control section 66. The logic circuit andcommunication control section 66 includes appropriate logic and circuitry for receiving and processing the non-standard combination of signals from the aircraft. Specifically, the logic circuit andcommunication control section 66 is designed to convert the non-standard combination of signals from the aircraft into a format compatible with theparticular bus controller 68 and interface (e.g., MIL-STD-1760) conventionally used by thesmart weapon 10. - The logic circuit and
communication control section 66 may be configured to provide any appropriate discrete signals directly to thesmart weapon 10. Such discretes include, for example, a Release Consent control signal as represented online 70. The Release Consent control signal according to the MIL-STD-1760 standard is analogous to the Master Arm signal online 50, and may be generated based thereon. - Regarding data communications, the logic circuit and
communication control section 66 compiles data and control information to the extent necessary from the non-standard combination of discretes (e.g., Normal Release) and thecommunication link 54. The logic circuit andcommunication control section 66 provides the data in an appropriate format to thebus controller 68 so it may in turn be provided to thesmart weapon 10. In the exemplary embodiment, thebus controller 68 is a MIL-STD-1553 databus conventionally used to communicate with the JDAM via the MIL-STD-1760 interface. Thebus controller 68 is coupled to the interface viaredundant databuses - The logic circuit and
communication control section 66 and thebus controller 68 have been described primarily in terms of communications from the aircraft to thesmart weapon 10. However, it will be appreciated that thecontrol section 66 andbus controller 68 also can provide for bidirectional communications between the aircraft and thesmart weapon 10. For example, thesmart weapon 10 can provide operation status, fault information, etc., via thebus controller 68 and thecontrol section 66. - The
interface circuit 30 also includes amemory 76 coupled to the logic circuit andcommunication control section 66 and/or thebus controller 68. Thememory 76 serves to store relevant data, such as target coordinates, necessary for the operation of the smart weapon. In addition, thememory 76 may serve as a working memory for thecontrol section 66 and/or thebus controller 68. - Furthermore, the
interface circuit 30 may include anoptional display 78 for displaying relevant information. For example, thedisplay 78 may be used to display target coordinate data which is programmed into thesmart weapon 10 as described more fully below. - The logic circuit and
communication control interface 66 and thebus controller 68 may be made of discrete components and/or an application specific integrated circuit (ASIC). As mentioned above, the particular design of the logic circuit andcommunication control interface 66 and thebus controller 68 will be appreciated by those having ordinary skill in the art in view of the particular signals available to thesmart weapon 10 from the aircraft via theumbilical cable 18 and the desired degree of control. Therefore, detail as to the specifics of such circuitry has been omitted for sake of brevity. The logic circuit andcommunication control interface 66 and thebus controller 68 each may derive their necessary operating power from the supply voltage provided vialines - The
umbilical cable 18 as shown inFIG. 3 also includes interlock and interlockreturn lines connector 26. In the exemplary embodiment, lines 80 and 82 are hardwired together within thecable 18. Continuity between these two lines informs thesmart weapon 10 that it is connected to the aircraftumbilical cable 18. Alternatively, the logic circuit andcommunication control section 66 can be configured to sense a connection of theconnector 22 to the aircraft and theconnector 26 to thesmart weapon 10 as a condition precedent to providing continuity betweenlines - Furthermore, the
umbilical cable 18 includes addressinglines 84. The addressing lines may be hardwired within thecable 18 via jumpers or the like to define a fixed address for thesmart weapon 10. Alternatively, in the case where dynamic addressing is utilized, the addressinglines 84 may be coupled tobus controller 68 which in turn outputs the appropriate addressing. - A basic manner for operating the
smart weapon 10 provides for ground loading of target data (e.g., target coordinates). Referring toFIG. 4 , target data is loaded into theumbilical cable 18 by temporarily coupling theconnector 26 at the weapon end of theumbilical cable 18 to aground loading device 86. Thesmart weapon 10 may be mounted to the aircraft at the time. Theumbilical cable 18 need not be coupled to thesmart weapon 10. The target data is simply loaded into theumbilical cable 18 using theground loading device 86, and is stored in thememory 76. Preferably theumbilical cable 18 remains connected at the opposite end to the aircraft viaconnector 22. This minimizes the possibility of targeting errors. Once theground loading device 86 loads targeting data into theumbilical cable 18, theumbilical cable 18 is subsequently connected to thesmart weapon 10. The target data thus previously loaded in theumbilical cable 18 is then provided to thesmart weapon 10 from theumbilical cable 18 during normal aircraft operation. - The
ground loading device 86 may be a computer, preferably of the hand-held variety. Theground loading device 86 is programmed to provide target data such as target coordinates to theumbilical cable 18 according to a predefined format. Theground loading device 86 preferably is coupled to the smart weapon end of theumbilical cable 18. However, an alternate embodiment may utilize the aircraft end of thecable 18 to program theumbilical cable 18 via thecommunication link 54. - Specifically, the
ground loading device 86 includes an input/output port with acable 88 designed to mate to theconnector 26. Theground loading device 86 provides the target data to the logic circuit andcommunication control section 66 viadatabuses bus controller 68 protocol. In the exemplary embodiment, thecontrol section 66 stores the target data in thememory 76. These commands are then provided to thesmart weapon 10 via thedatabuses - Accordingly, the embodiment of
FIG. 4 allows for ground personnel to program target data for the smart weapon via theumbilical cable 18. Such operation is advantageous as virtually no aircraft modifications are necessary. The discrete control signals necessary from the crew in flight are available already at the pylon or bomb bay as described above. Thus, virtually any aircraft can be made smart weapon capable at very little expense using theumbilical cable 18 of the present invention. - In the event it is desirable to provide in-flight pilot targeting control, a simple communication link (e.g., non-MIL-STD-1553) such as a two-wire bus for the aforementioned two-
wire communication link 54 may be added to the aircraft at relatively minimal expense. This allows the pilot to target or retarget thesmart weapon 10 while in flight. - For example,
FIG. 5 illustrates an embodiment in which a two-wire bus (labeled as corresponding communication link 54) is run from the cockpit of the aircraft to thepylon connector 24. The pilot may have a portable hand-heldprocessor device 90 such as a commonly available personal digital assistant (PDA) from Palm (e.g., the Palm Pilot™), Casio, Dell, etc. ThePDA device 90 includes an I/O port which is hardwired via anappropriate interface 92 to thecommunication link 54. This allows the pilot to input relevant data such as target data (e.g., coordinate data) or the like. ThePDA device 90 may be strapped to the knee of the pilot, and be configured to allow the pilot to input the data via atouchscreen 94 or the like. Theumbilical cable 18 receives the data via thecommunication link 54, and converts the data to a set of signals receivable by thesmart weapon 10. In this manner, full in-flight re-targeting capability is provided. -
FIG. 6 illustrates a variation of the embodiment ofFIG. 5 . In this embodiment, thePDA device 90 is wirelessly linked to thecommunication link 54. More specifically, thePDA device 90 may include a small infrared (IR), radio frequency (RF) or other type I/O port. Located preferably inside the cockpit is anappropriate interface 92′ for receiving and transmitting wireless communications between theinterface circuit 30 in theumbilical cable 18 and thePDA device 90. -
FIG. 7 generically represents the feature of the invention whereby any available data, discrete signals, etc. from the aircraft may serve as the source of the non-standard combination of signals provided to theumbilical cable 18. For example, navigation data, GPS data, altitude data, air speed data, etc. all may be provided to thesmart weapon 10 as needed. The information may be hardwired to theconnector 24, or sent via acommunication link 54 either automatically, if configured, or by manual entry by the pilot as described above in connection withFIGS. 5 and 6 . Theumbilical cable 18 is designed, with knowledge of the particular information available from the aircraft and the particular smart weapon involved, the convert the information into a set of signals receivable by thesmart weapon 10 in order to carry out operations. -
FIG. 8 illustrates another alternative embodiment of the present invention. In this embodiment, theumbilical cable 18 includes the display 78 (see,FIG. 3 ) in thebackshell 32 of theconnector 22. Thedisplay 78 is useful, for example, in providing verification of the target data stored in the memory. For example, when theumbilical cable 18 is loaded with target data in the manner described above in relation toFIG. 4 , the target data may be verified even after theumbilical cable 18 is disconnected from theground loading device 86 and reconnected to the weapon. Additionally, or in the alternative, thedisplay 78 may be used to display status information, fault information, or the like provided by the internal cable circuitry. - The
display 78 may be any type of display (e.g., numeric, alphanumeric, simple status indicator lights, etc.) without departing from the scope of the invention. Thedisplay 78 may be an liquid crystal display (LCD), light emitting diode (LED) display, or any other type of suitable display. Although thedisplay 78 is shown as being located in thebackshell 32 of theconnector 22, it could instead be located in thebackshell 34, or elsewhere along theumbilical cable 18 without departing from the scope of the invention as will be appreciated. - The
umbilical cable 18 is described above with theinterface circuit 30 being located approximately in the middle of the cable. It will be appreciated, however, that the interface circuit may be located elsewhere within thecable 18 without departing from the scope of the invention. For example,FIG. 9 illustrates an embodiment in which theinterface circuit 30 is located in thebackshell 32 of theconnector 22. In another embodiment, theinterface circuit 30 may be included in thebackshell 34 of theconnector 26. Further still, another embodiment may include theinterface circuit 30 split and located in theback shells display 78 also. - Although the invention has been shown and described with respect to certain preferred embodiments, it is obvious that equivalents and modifications will occur to others skilled in the art upon the reading and understanding of the specification. The present invention includes all such equivalents and modifications, and is limited only by the scope of the following claims.
Claims (27)
1. An umbilical cable for delivering electrical signals between an aircraft and a smart weapon carried by the aircraft, the umbilical cable comprising:
cabling comprising a plurality of conductive wires;
a first connector provided on one end of the cabling and configured to connect to the aircraft;
a second connector provided on the other end of the cabling and configured to connect to the smart weapon; and
an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires, the interface circuit being configured to receive via the first connector a non-standard combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations, to convert the non-standard combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector,
wherein the combination of signals which the interface circuit is configured to receive is not representative of a standardized smart weapon interface.
2. The umbilical cable of claim 1 , wherein the non-standard combination comprises discrete signals from the aircraft.
3. The umbilical cable of claim 1 , wherein the interface circuit comprises a memory for storing a sequence of control commands for operating the smart weapon, and a bus controller for providing the sequence of control commands to the smart weapon.
4. A system comprising the umbilical cable of claim 1 , and further comprising:
source operation circuitry for providing the non-standard combination of signals to the first connector.
5. The system of claim 4 , wherein the aircraft comprises an aircraft connector designed to mate with the first connector, and the source operation circuitry comprises at least one hardwired connection of a discrete control signal from elsewhere in the aircraft to the aircraft connector.
6. The system of claim 5 , wherein the discrete control signal comprises at least one of a release signal representing a desired release of the smart weapon, and a master arm signal representing a desire to arm the smart weapon.
7. The system of claim 5 , wherein the source operation circuitry further comprises a communication bus which is coupled to a corresponding bus included within the umbilical cable.
8. The system of claim 7 , wherein the communication bus is a two wire bus.
9. The system of claim 4 , wherein the source operation circuitry comprises a pilot-operated digital processor.
10. The system of claim 9 , wherein the pilot-operated digital processor is portable.
11. The system of claim 10 , wherein the pilot-operated digital processor is hardwired to an aircraft connector designed to mate with the first connector.
12. An umbilical cable for delivering electrical signals between an aircraft and a smart weapon carried by the aircraft, the umbilical cable comprising:
cabling comprising a plurality of conductive wires;
a first connector provided on one end of the cabling and configured to connect to the aircraft;
a second connector provided on the other end of the cabling and configured to connect to the smart weapon; and
an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires, the interface circuit being configured to receive via the first connector a non-standard combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations, to convert the non-standard combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector,
wherein the pilot-operated digital processor is portable and the pilot-operated digital processor is wirelessly linked to an aircraft connector designed to mate with the first connector.
13. An umbilical cable for delivering electrical signals between an aircraft and a smart weapon cared by the aircraft, the umbilical cable comprising:
cabling comprising a plurality of conductive wires;
a first connector provided on one end of the cabling and configured to connect to the aircraft;
a second connector provided on the other end of the cabling and configured to connect to the smart weapon;
an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires, the interface circuit being configured to receive via the first connector a non-standard combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations, to convert the non-standard combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector; and
a ground loading device separate from the aircraft and configured to connect to at least one of the first connector and the second connector to program operation data for the smart weapon into the umbilical cable.
14. The system of claim 13 , wherein the ground loading device programs target coordinate data into the umbilical cable.
15. The system of claim 13 , wherein the umbilical cable further includes a display for displaying at least a portion of the operation data programmed into the umbilical cable.
16. The system of claim 15 , wherein the display is included in a backshell of at least one of the first connector and the second connector.
17. A method of providing operation data to a smart weapon configured to be loaded on an aircraft, the method comprising the steps of:
providing an umbilical cable, the umbilical cable comprising:
cabling comprising a plurality of conductive wires;
a first connector provided on one end of the cabling and configured to connect to the aircraft;
a second connector provided on the other end of the cabling and configured to connect to the smart weapon; and
an interface circuit electrically coupled between the first connector and the second connector via the plurality of conductive wires, the interface circuit being configured to receive via the first connector a combination of signals comprising at least one of data signals, control signals and power signals not receivable directly by the smart weapon to carry out operations, to convert the combination of signals to a set of signals receivable by the smart weapon to carry out operations, and to provide the set of receivable signals to the smart weapon via the second connector;
temporarily connecting at least one of the first connector and the second connector to a ground loading device separate from the aircraft; and
transmitting the operation data from the ground loading device to the umbilical cable and storing the operation data within the umbilical cable.
18. The method of claim 17 , further comprising the steps of connecting the first connector to the aircraft, connecting the second connector to the smart weapon, and providing the operation data stored within the umbilical cable to the smart weapon during operation of the aircraft.
19. The method of claim 17 , wherein the method is carried out while the umbilical cable is connected at one end to the aircraft.
20. The method of claim 17 , wherein the ground loading device provides target coordinate data to the umbilical cable.
21. The method of claim 17 , wherein the umbilical cable further includes a display and displays at least a portion of the operation data stored in the umbilical cable.
22. The method of claim 21 , wherein the display is included in a backshell of at least one of the first connector and the second connector.
23. The method of claim 17 , wherein the umbilical cable supports bi-directional communication between the smart weapon and the ground loading device.
24. The method of claim 17 , wherein the operation data transmitted from the ground loading device to the umbilical cable and stored in the umbilical cable is transmitted from the ground loading device into the umbilical cable by coupling the ground loading device to an end of the umbilical cable not concurrently connected to the aircraft.
25. (canceled)
26. The system of claim 5 , wherein the source operation circuitry further comprises a communication bus which is coupled to a corresponding bus included within the umbilical cable, the corresponding bus not being part of a standardized smart weapon interface.
27. The system of claim 14 , wherein the umbilical cable includes a memory for storing the target coordinate data programmed into the umbilical cable by the ground loading device.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/754,153 US6941850B1 (en) | 2004-01-09 | 2004-01-09 | Self-contained airborne smart weapon umbilical control cable |
PCT/US2004/040659 WO2005124271A2 (en) | 2004-01-09 | 2004-12-03 | Self-contained airborne smart weapon umbilical control cable |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/754,153 US6941850B1 (en) | 2004-01-09 | 2004-01-09 | Self-contained airborne smart weapon umbilical control cable |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050183570A1 true US20050183570A1 (en) | 2005-08-25 |
US6941850B1 US6941850B1 (en) | 2005-09-13 |
Family
ID=34860709
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/754,153 Expired - Lifetime US6941850B1 (en) | 2004-01-09 | 2004-01-09 | Self-contained airborne smart weapon umbilical control cable |
Country Status (2)
Country | Link |
---|---|
US (1) | US6941850B1 (en) |
WO (1) | WO2005124271A2 (en) |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008121431A2 (en) * | 2007-01-31 | 2008-10-09 | Raytheon Company | Munitions control unit |
US20100070674A1 (en) * | 2008-09-15 | 2010-03-18 | Raytheon Company | Smart translator box for agm-65 aircraft "maverick" analog interface to mil-std-1760 store digital interface |
US7845263B1 (en) * | 2008-01-18 | 2010-12-07 | Frank Miller | Bomb release mechanism for radio-controlled airplane |
US20120150365A1 (en) * | 2010-12-13 | 2012-06-14 | Raytheon Company | Wireless Precision Avionics Kit |
US8314374B2 (en) | 2005-06-20 | 2012-11-20 | Aurora Flight Sciences Corporation | Remotely-guided vertical take-off system and method for delivering an ordnance to a target |
US20130218372A1 (en) * | 2012-02-22 | 2013-08-22 | Sikorsky Aircraft Corporation | Weapons Stores Processor Panel For Aircraft |
US8608111B2 (en) | 2010-04-01 | 2013-12-17 | Raytheon Company | Decoupling mechanism for a store |
US8967032B2 (en) | 2012-02-09 | 2015-03-03 | Raytheon Company | Smart-store emulation unit |
US20150370752A1 (en) * | 2013-09-23 | 2015-12-24 | Raytheon Company | Translation of universal armament interface (uai) to military standard (mil-std-1760) messaging interface |
US20160083089A1 (en) * | 2014-09-18 | 2016-03-24 | Raytheon Company | Aircraft store deployment system with improved safety of arming and releasing stores |
US9875200B2 (en) | 2013-09-23 | 2018-01-23 | Raytheon Company | Military standard (MIL-STD-1760) interface bridge |
US9897413B1 (en) * | 2016-07-22 | 2018-02-20 | Florida Turbine Technologies, Inc. | Process for launching a cruise missile from an aircraft |
US10422615B2 (en) | 2013-09-23 | 2019-09-24 | Raytheon Company | Interface bridge for initializing a weapon with mission planning data |
US20190299861A1 (en) * | 2018-03-27 | 2019-10-03 | GM Global Technology Operations LLC | Towing arrangement with integrated imaging connection device |
US20210067611A1 (en) * | 2019-08-29 | 2021-03-04 | Textron Systems Corporation | Interfacing modules of a munition to a standard munition network |
WO2024022748A1 (en) * | 2022-07-26 | 2024-02-01 | Diehl Defence Gmbh & Co. Kg | Effektor data connector for data connection of an effector to a firing platform |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7137599B1 (en) * | 2004-04-26 | 2006-11-21 | Raytheon Company | Launcher with dual mode electronics |
US8011180B2 (en) * | 2007-08-16 | 2011-09-06 | Ford Global Technologies, Llc | Particulate filter regeneration |
US7868276B2 (en) * | 2007-10-24 | 2011-01-11 | Lockheed Martin Corporation | Airborne vehicle emulation system and method |
US8224501B2 (en) * | 2008-09-30 | 2012-07-17 | General Electric Company | Store management system and method of operating the same |
DE102009040304B4 (en) * | 2009-09-05 | 2012-10-04 | Lfk-Lenkflugkörpersysteme Gmbh | Device for controlling functional tests and / or service procedures for aircraft-unmanned aerial vehicles |
US8186588B2 (en) * | 2009-10-15 | 2012-05-29 | Lockheed Martin Corporation | Shared drive launcher/weapon interface |
DE102010024541B4 (en) * | 2010-05-27 | 2013-11-07 | Mbda Deutschland Gmbh | Method for interrogating measurement and / or state data from a data memory of a sharp unmanned missile and device for carrying out the method |
US8287318B1 (en) | 2010-08-12 | 2012-10-16 | Williams-Pyro, Inc. | Electrical connector with spring for missile launch rail |
US8751069B2 (en) * | 2011-06-16 | 2014-06-10 | The Boeing Company | Dynamically reconfigurable electrical interface |
US8399817B1 (en) | 2011-08-12 | 2013-03-19 | The United States Of America As Represented By The Secretary Of The Navy | Micro designator dart |
DE102012000671B4 (en) * | 2012-01-17 | 2014-07-17 | Mbda Deutschland Gmbh | A missile launch tester and tester and method for testing and / or testing the health of a missile launcher |
DE102015006799B4 (en) * | 2015-05-27 | 2022-11-17 | Mbda Deutschland Gmbh | Test facility for a missile launcher |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5414347A (en) * | 1992-07-13 | 1995-05-09 | Hughes Aircraft Company | Method and apparatus for missile interface testing |
US5443227A (en) * | 1993-10-15 | 1995-08-22 | Hughes Aircraft Company | Switching control for multiple fiber-guided missile systems |
US5541839A (en) * | 1993-10-23 | 1996-07-30 | Bodenseewerk Geratetechnik Gmbh | Interface arrangement for data transfer between carrier aircraft and missile |
US5548510A (en) * | 1994-10-28 | 1996-08-20 | Mcdonnell Douglas Corporation | Method and apparatus for providing a universal electrical interface between an aircraft and an associated store |
US5942713A (en) * | 1998-02-06 | 1999-08-24 | Lockheed Martin Corp. | High missile packing density launching system |
US5992290A (en) * | 1997-04-09 | 1999-11-30 | Cubic Defense Systems, Inc. | Aircraft interface device and crossover cable kit |
US6122569A (en) * | 1998-11-13 | 2000-09-19 | Mcdonnell Douglas Corporation | Store interface apparatus |
US6615116B2 (en) * | 2001-08-09 | 2003-09-02 | The Boeing Company | Method and apparatus for communicating between an aircraft and an associated store |
US20040015273A1 (en) * | 2002-07-19 | 2004-01-22 | The Boeing Company | System, bypass apparatus and method of operating a store of a first predetermined type |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2132794B (en) * | 1982-12-18 | 1986-02-26 | British Aerospace | Missile guidance system |
GB2202061B (en) * | 1987-03-10 | 1991-04-24 | Boeing Co | Weapon interface system evaluator |
US5591031A (en) * | 1994-05-31 | 1997-01-07 | Hughes Electronics | Missile simulator apparatus |
US5721680A (en) * | 1995-06-07 | 1998-02-24 | Hughes Missile Systems Company | Missile test method for testing the operability of a missile from a launch site |
-
2004
- 2004-01-09 US US10/754,153 patent/US6941850B1/en not_active Expired - Lifetime
- 2004-12-03 WO PCT/US2004/040659 patent/WO2005124271A2/en active Application Filing
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5414347A (en) * | 1992-07-13 | 1995-05-09 | Hughes Aircraft Company | Method and apparatus for missile interface testing |
US5443227A (en) * | 1993-10-15 | 1995-08-22 | Hughes Aircraft Company | Switching control for multiple fiber-guided missile systems |
US5541839A (en) * | 1993-10-23 | 1996-07-30 | Bodenseewerk Geratetechnik Gmbh | Interface arrangement for data transfer between carrier aircraft and missile |
US5548510A (en) * | 1994-10-28 | 1996-08-20 | Mcdonnell Douglas Corporation | Method and apparatus for providing a universal electrical interface between an aircraft and an associated store |
US5992290A (en) * | 1997-04-09 | 1999-11-30 | Cubic Defense Systems, Inc. | Aircraft interface device and crossover cable kit |
US5942713A (en) * | 1998-02-06 | 1999-08-24 | Lockheed Martin Corp. | High missile packing density launching system |
US6122569A (en) * | 1998-11-13 | 2000-09-19 | Mcdonnell Douglas Corporation | Store interface apparatus |
US6615116B2 (en) * | 2001-08-09 | 2003-09-02 | The Boeing Company | Method and apparatus for communicating between an aircraft and an associated store |
US20040015273A1 (en) * | 2002-07-19 | 2004-01-22 | The Boeing Company | System, bypass apparatus and method of operating a store of a first predetermined type |
Cited By (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8314374B2 (en) | 2005-06-20 | 2012-11-20 | Aurora Flight Sciences Corporation | Remotely-guided vertical take-off system and method for delivering an ordnance to a target |
JP2010532852A (en) * | 2007-01-31 | 2010-10-14 | レイセオン カンパニー | Military supplies control device |
WO2008121431A3 (en) * | 2007-01-31 | 2008-11-27 | Raytheon Co | Munitions control unit |
WO2008121431A2 (en) * | 2007-01-31 | 2008-10-09 | Raytheon Company | Munitions control unit |
US20100217899A1 (en) * | 2007-01-31 | 2010-08-26 | Raytheon Company | Munitions control unit |
US7845263B1 (en) * | 2008-01-18 | 2010-12-07 | Frank Miller | Bomb release mechanism for radio-controlled airplane |
WO2010096090A2 (en) | 2008-09-15 | 2010-08-26 | Raytheon Company | Smart translator box for agm-65 aircraft "maverick" analog interface to mil-std-1760 store digital interface |
WO2010096090A3 (en) * | 2008-09-15 | 2010-12-02 | Raytheon Company | Smart translator box for agm-65 aircraft "maverick" analog interface to mil-std-1760 store digital interface |
US7802048B2 (en) | 2008-09-15 | 2010-09-21 | Raytheon Company | Smart translator box for AGM-65 aircraft “Maverick” analog interface to MIL-STD-1760 store digital interface |
US20100070674A1 (en) * | 2008-09-15 | 2010-03-18 | Raytheon Company | Smart translator box for agm-65 aircraft "maverick" analog interface to mil-std-1760 store digital interface |
US8608111B2 (en) | 2010-04-01 | 2013-12-17 | Raytheon Company | Decoupling mechanism for a store |
US20120150365A1 (en) * | 2010-12-13 | 2012-06-14 | Raytheon Company | Wireless Precision Avionics Kit |
US8967032B2 (en) | 2012-02-09 | 2015-03-03 | Raytheon Company | Smart-store emulation unit |
US9803958B2 (en) * | 2012-02-22 | 2017-10-31 | Sikorsky Aircraft Corporation | Weapons stores processor panel for aircraft |
US20130218372A1 (en) * | 2012-02-22 | 2013-08-22 | Sikorsky Aircraft Corporation | Weapons Stores Processor Panel For Aircraft |
US20150370752A1 (en) * | 2013-09-23 | 2015-12-24 | Raytheon Company | Translation of universal armament interface (uai) to military standard (mil-std-1760) messaging interface |
US10422615B2 (en) | 2013-09-23 | 2019-09-24 | Raytheon Company | Interface bridge for initializing a weapon with mission planning data |
US11002519B2 (en) | 2013-09-23 | 2021-05-11 | Raytheon Company | Interface bridge for initializing a weapon with mission planning data |
US9916277B2 (en) * | 2013-09-23 | 2018-03-13 | Raytheon Company | Translation of universal armament interface (UAI) to military standard (mil-std-1760) messaging interface |
US9875200B2 (en) | 2013-09-23 | 2018-01-23 | Raytheon Company | Military standard (MIL-STD-1760) interface bridge |
US20160083089A1 (en) * | 2014-09-18 | 2016-03-24 | Raytheon Company | Aircraft store deployment system with improved safety of arming and releasing stores |
WO2016064457A1 (en) * | 2014-09-18 | 2016-04-28 | Raytheon Company | Aircraft store deployment system with improved safety of arming and releasing stores |
US9783296B2 (en) * | 2014-09-18 | 2017-10-10 | Raytheon Company | Aircraft store deployment system with improved safety of arming and releasing stores |
US9897413B1 (en) * | 2016-07-22 | 2018-02-20 | Florida Turbine Technologies, Inc. | Process for launching a cruise missile from an aircraft |
US20190299861A1 (en) * | 2018-03-27 | 2019-10-03 | GM Global Technology Operations LLC | Towing arrangement with integrated imaging connection device |
CN110303835A (en) * | 2018-03-27 | 2019-10-08 | 通用汽车环球科技运作有限责任公司 | Traction arrangement with integration imaging connection equipment |
US10596967B2 (en) * | 2018-03-27 | 2020-03-24 | GM Global Technology Operations LLC | Towing arrangement with integrated imaging connection device |
US20210067611A1 (en) * | 2019-08-29 | 2021-03-04 | Textron Systems Corporation | Interfacing modules of a munition to a standard munition network |
US11641411B2 (en) * | 2019-08-29 | 2023-05-02 | Textron Systems Corporation | Interfacing modules of a munition to a standard munition network |
WO2024022748A1 (en) * | 2022-07-26 | 2024-02-01 | Diehl Defence Gmbh & Co. Kg | Effektor data connector for data connection of an effector to a firing platform |
DE102022002703A1 (en) | 2022-07-26 | 2024-02-01 | Diehl Defence Gmbh & Co. Kg | Effector data connector for data connection of an effector to a firing platform |
Also Published As
Publication number | Publication date |
---|---|
US6941850B1 (en) | 2005-09-13 |
WO2005124271A2 (en) | 2005-12-29 |
WO2005124271A3 (en) | 2006-02-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6941850B1 (en) | Self-contained airborne smart weapon umbilical control cable | |
US6615116B2 (en) | Method and apparatus for communicating between an aircraft and an associated store | |
US6349898B1 (en) | Method and apparatus providing an interface between an aircraft and a precision-guided missile | |
ES2331670T3 (en) | UNIVERSAL ELECTRICAL INTERFACE BETWEEN AN AIRCRAFT AND AN ASSOCIATED EXTERNAL LOAD THAT PROVIDES AN ORDER MENU ON A SCREEN. | |
US7802048B2 (en) | Smart translator box for AGM-65 aircraft “Maverick” analog interface to MIL-STD-1760 store digital interface | |
US6122569A (en) | Store interface apparatus | |
US20120150365A1 (en) | Wireless Precision Avionics Kit | |
US20100217899A1 (en) | Munitions control unit | |
US6763289B2 (en) | System, bypass apparatus and method of operating a store of a first predetermined type | |
AU2017378131B2 (en) | System and method for stores communications | |
US7353090B2 (en) | System, bus monitor assembly and method of monitoring at least one data bus of an aircraft | |
US5397079A (en) | Process for the autonomous positional control of guided missiles | |
EP2098451B1 (en) | Aerospace vehicle system | |
US8967032B2 (en) | Smart-store emulation unit | |
US8278611B2 (en) | Airborne guided shell | |
CN107870625B (en) | Unmanned helicopter airborne task manager | |
KR102424166B1 (en) | Weapon Control System for gunship-helicopter | |
CA2525996C (en) | Standoff land attack-expanded response device computer | |
GB2382865A (en) | A method for in-flight/real-time planning of a mission for a precision-guided missile | |
US20050223883A1 (en) | Standoff land attack-expanded response device computer | |
GB2403789A (en) | Autonomous smart store carrier | |
AU2005232254A1 (en) | Standoff land attack-expanded response device computer |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RAYTHEON COMPANY, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MCMAHON, ROY PATRICK;REEL/FRAME:014403/0023 Effective date: 20040108 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FPAY | Fee payment |
Year of fee payment: 12 |