US20100152919A1 - Vehicle management and mission management computer architecture and packaging - Google Patents
Vehicle management and mission management computer architecture and packaging Download PDFInfo
- Publication number
- US20100152919A1 US20100152919A1 US12/706,164 US70616410A US2010152919A1 US 20100152919 A1 US20100152919 A1 US 20100152919A1 US 70616410 A US70616410 A US 70616410A US 2010152919 A1 US2010152919 A1 US 2010152919A1
- Authority
- US
- United States
- Prior art keywords
- mission
- channels
- vehicle
- management
- channel
- 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.)
- Abandoned
Links
- 238000004806 packaging method and process Methods 0.000 title claims abstract description 35
- 230000008878 coupling Effects 0.000 claims description 11
- 238000010168 coupling process Methods 0.000 claims description 11
- 238000005859 coupling reaction Methods 0.000 claims description 11
- 238000000034 method Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 4
- 238000005259 measurement Methods 0.000 description 4
- RZVHIXYEVGDQDX-UHFFFAOYSA-N 9,10-anthraquinone Chemical compound C1=CC=C2C(=O)C3=CC=CC=C3C(=O)C2=C1 RZVHIXYEVGDQDX-UHFFFAOYSA-N 0.000 description 3
- 239000000446 fuel Substances 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000005251 gamma ray Effects 0.000 description 1
- 238000005507 spraying Methods 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course or altitude of land, water, air, or space vehicles, e.g. automatic pilot
- G05D1/0055—Control of position, course or altitude of land, water, air, or space vehicles, e.g. automatic pilot with safety arrangements
- G05D1/0077—Control of position, course or altitude of land, water, air, or space vehicles, e.g. automatic pilot with safety arrangements using redundant signals or controls
Abstract
A vehicle management and mission management computer architecture and packaging may include a first line replaceable unit and a second line replaceable unit. The first line replaceable unit may include a vehicle management system computer channel coupleable to a group including at least one mission related system and at least one vehicle system. The first line replaceable unit may also include a mission management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system. The second line replaceable unit may include another vehicle management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system. The second line replaceable unit may also include another mission management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system.
Description
- This application is a divisional of U.S. patent application Ser. No. 11/534,461 filed on Sep. 22, 2006, the disclosure of which is hereby incorporated by reference herein for all purposes.
- The present invention relates to computer architecture and packaging and more particularly to a vehicle management and mission management computer architecture and packaging for unmanned vehicles or the like.
- Vehicles, such as unmanned vehicles or the like, typically have systems related to the operation of the vehicle and systems related to the mission of the vehicle. Examples of vehicle related systems may include vehicle propulsion systems, fuel systems, electrical systems, hydraulic systems, flight termination systems and the like. Examples of mission related systems may include communications systems, intelligence, surveillance and reconnaissance (ISR) systems, weapons systems and the like. Each of these systems may be controlled by management system computers or the like. In some applications, particularly those that may require high altitude and long endurance, low weight and reliable vehicle management system (VMS) and mission management system (MMS) computing are needed to meet the long endurance and high mission reliability goals.
- In accordance with an embodiment of the present invention, a vehicle management and mission management computer architecture and packaging may include a first line replaceable unit and a second line replaceable unit. The first line replaceable unit may include a vehicle management system computer channel coupleable to a group including at least one mission related system and at least one vehicle system. The first line replaceable unit may also include a mission management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system. The second line replaceable unit may include another vehicle management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system, and the second line replaceable unit may also include another mission management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system.
- In accordance with another embodiment of the present invention, a vehicle management and mission management computer architecture and packaging may include a first line replaceable unit and a second line replaceable unit. A pair of vehicle management system computer channels may be included in each line replaceable unit, and a pair of mission management system computer channels may also be included in each line replaceable unit.
- In accordance with another embodiment of the present invention, a vehicle may include at least one vehicle system and at least one mission related system. The vehicle may also include a vehicle management and mission management computer architecture and packaging. The vehicle management and mission management computer architecture and packaging may include a first line replaceable unit and a second line replaceable unit. The first line replaceable unit may include a vehicle management system computer channel coupled to the at least one mission related system and the at least one vehicle system. The first line replaceable unit may also include a mission management system computer channel coupled to the at least one mission related system and the at least one vehicle system. The second line replaceable unit may include another vehicle management system computer channel coupled to the at least one mission related system and the at least one vehicle system. The second line replaceable unit may also include another mission management system computer channel coupled to the at least one mission related system and the at least one vehicle system.
- In accordance with another embodiment of the present invention, a method to provide vehicle management and mission management in a low weight and reliable architecture may include providing a first line replaceable unit and a second line replaceable unit. The method may also include providing at least one vehicle management system computer channel in each line replaceable unit; and at least one mission management system computer channel in each line replaceable unit.
- Other aspects and features of the present invention, as defined solely by the claims, will become apparent to those ordinarily skilled in the art upon review of the following non-limited detailed description of the invention in conjunction with the accompanying figures.
-
FIGS. 1A and 1B (collectivelyFIG. 1 ) are a block diagram of an example of a vehicle management system computer and mission management system computer architecture and packaging in accordance with an embodiment of the present invention. -
FIG. 2 is a block diagram of an example of a line replaceable unit (LRU) in accordance with an embodiment of the present invention. -
FIG. 3 is an illustration of an example of a vehicle including a vehicle management computer system and mission management computer system architecture and packaging in accordance with an embodiment of the present invention. - The following detailed description of embodiments refers to the accompanying drawings, which illustrate specific embodiments of the invention. Other embodiments having different structures and operations do not depart from the scope of the present invention.
-
FIGS. 1A and 1B (collectivelyFIG. 1 ) are a block diagram of an example of a vehicle management system computer (VMSC) and mission management system computer (MMSC) architecture andpackaging 100 in accordance with an embodiment of the present invention. The VMSC and MMSC architecture andpackaging 100 may include a first linereplaceable unit 102 a and a second linereplaceable unit 102 b. Each line replaceable unit 102 may include two VMSCs or VMSC channels 104 and two MMSCs or MMSC channels 106. In the embodiment illustrated inFIGS. 1A and 1B , the first linereplaceable unit 102 a may include VMSC Channel #1 104 a, VMSCchannel # 2 104 b, MMSC Channel #1 106 a (FIG. 1B ) and MMSC Channel #2 106 b (FIG. 1B ). The second linereplaceable unit 102 b may include VMSC Channel #3 104 c, VMSC Channel #4 104 d, MMSC Channel #3 106 c (FIG. 1B ) and MMSC Channel #4 106 d (FIG. 1B ). The linereplaceable units -
FIGS. 1A and 1B each illustrate examples of the same linereplaceable units FIG. 1A illustrates the VMSC channels 104 and an associatedVMSC bus architecture 108, andFIG. 1B illustrates the MMSC channels 106 and an associatedMMSC bus architecture 110. The MMSC channels 106 are illustrated in phantom or broken lines inFIG. 1A . Similarly, the VMSC channels 104 are illustrated in phantom or broken lines inFIG. 1B . - The vehicle management and mission management computer architecture and
packaging 100 may include a VMSC common bus 112 (FIG. 1A ) coupling together the VMSC channels 104 and the MMSC channels 106. The VMSCcommon bus 112 may be further adapted to couple the channels 104 and 106 to one or more missionrelated systems 114. Missionrelated systems 114 may includemission communications hardware 117 or equipment andmission payload 118 or other equipment or systems needed to perform a particular mission or purpose. Examples ofmission communications hardware 117 may include radios or other communications devices. Examples ofmission payload 118 may include intelligence, surveillance and reconnaissance (ISR) equipment or systems, weapons systems, or other systems to perform a predefined mission. - The vehicle management and mission management computer architecture and
packaging 100 may also include a MMSC common bus 116 (FIG. 1B ) to couple together the MMSC channels 106 and the VMSC channels 104. The VMSCcommon bus 112 and the MMSCcommon bus 116 may be a single common bus. The MMSCcommon bus 116 may be further adapted to couple the channels 104 and 106 to one ormore vehicle systems 120.Vehicle systems 120 may be those systems necessary to operate the vehicle to perform the predefined mission. Examples ofvehicle systems 120 may include propulsion systems, fuel systems, air data, electrical systems, flight termination systems and other systems needed for operation of the vehicle. - The VMSC bus architecture 108 (
FIG. 1A ) may also include a separate group ofVMSC buses 122. Eachseparate VMSC bus 122 may couple a respective one of the VMSC channels 104 to one ormore vehicle systems 120. - Similarly, the MMSC bus architecture 110 (
FIG. 1B ) may include a separate group ofMMSC buses 124. Eachseparate MMSC bus 124 may couple a respective one of the MMSC channels 106 to one or more mission relatedsystems 114. - The VMSC and MMSC architecture and
packaging 100 may also include achannel restart feature 126. A cross channeldata link architecture 128 may be provided to exchange data between channels and to support redundancy management voting and thechannel restart feature 126 or capability. A channel restart capability may be provided in the event that a VMSC channel 104 or a MMSC channel 106 becomes corrupted during operation. A possible cause of corruption may be a single event upset (SEU) where a gamma ray corrupts a memory component within a channel. To accomplish channel restart, the effected channel must reboot and its states must be reinitialized from correctly operating channels using the crosschannel data links 128. - In accordance with one embodiment of the present invention illustrated in
FIGS. 1A and 1B , the cross channeldata link architecture 128 may include a plurality of crosschannel data links 130, at least one between each VMSC channel 104 in the first and second LRUs 102 and another plurality of crosschannel data links 132, at least one between each MMSC channel 106 in the first and second LRUs 102. - The VMSC and MMSC architecture and
packaging 100 may also include a VMSC Ethernet 142 (FIG. 1A ) to couple the VMSC channels 104 and the MMSC channels 106 and may further couple the channels to one or more mission relatedsystems 114. - Similarly, the VMSC and MMSC architecture and
packaging 100 may include a MMSC Ethernet 144 (FIG. 1B ) to couple the VMSC channels 104 and MMSC channels 106 and may further couple the channels to at least onevehicle system 120. TheVMSC Ethernet 142 andMMSC Ethernet 144 may be a single system. - The VMSC channels 104 may also be coupled to one or
more actuators 146, flight control systems or similar apparatus associated with a vehicle where the VMSC/MMSC architecture andpackaging 100 may be deployed. The VMSC channels 104 may be coupled to the actuator or actuators by suitable links and/orconnectors 148. Theactuators 146 may be flight control actuators to control flight control surfaces, utility actuators, such as landing gear, doors or components. Thelinks 148 may be digital links or connections. - As will be described in more detail with reference to
FIG. 2 , each of the VMSC channels 104 may include a global positioning system (GPS) receiver. Accordingly, each of the VMSC channels 104 may be coupled to aGPS antenna 150 by asuitable connection 152. - The VMSC and MMSC architecture and
packaging 100 may further include abus 154 associated with each MMSC Channel 106 forMMS growth 156. Examples of theMMS growth 156 may include other mission related equipment or operations. -
FIG. 2 is a block diagram of an example of a line replaceable unit (LRU) 200 in accordance with an embodiment of the present invention. The LRU 200 may be used for each of the linereplaceable units FIGS. 1A and 1B . The LRU 200 may include a pair of vehicle management system computer (VMSC)channels channels - Each VMSC channel 202 may include a processor 206 or processor core to control overall operation of the VMSC channel 202 and the other components. The processor 206 may access a
memory 208 or storage device for storing programs or applications that may operate or run on the processor 206 for particular vehicle operations. Each VMSC channel 202 may also include a global positioning system (GPS)receiver 210 and an inertial measurement unit (IMU) 212. TheGPS receiver 210 may be used to determine a geographic location of the vehicle on which the LRU 200 is operating and to assist with guidance or navigation of the vehicle. TheIMU 212 may provide measurements of vehicle movement, such as vehicle rotation rates, linear accelerations and the like for flight controls and navigation algorithms. TheIMU 212 may be a Honeywell HG1700 as manufactured by Honeywell, Minneapolis, Minn., or a similar device. For airborne applications, each VMSC channel 202 may also include a radar altimeter to provide altitude measurements for control and guidance of the vehicle. - The VMSC channel 202 may also include a
power supply 216 to power the various components of the VMSC channel 202 that may require power.Data connections 218 between the different components of the VMSC channel are illustrated by a dashed or broken line inFIG. 2 andpower distribution lines 220 are illustrated by solid lines inFIG. 2 . The VMSC channel 202 may also include one or more bus connections orconnectors 222 to couple the VMSC channel 202 to various vehicle systems and mission related systems, such asvehicle systems 120 and mission relatedsystems 114, similar to that described with respect toFIGS. 1A and 1B . - Each MMSC channel 204 may include a
processor 224 or processor core and amemory 226 that may store programs or applications operable on theprocessor 224 as well as other data. Theprocessor 224 andmemory 226 may be the same as processor 206 andmemory 208 of the VMSC channels 202. A power supply 228 may also be included to provide power for operation of theprocessor 224 and any other components of the MMSC channel 204 that may require power. The MMSC channel 204 may also includebus connectors 230 or connections to couple the MMSC channel 204 to the various mission related systems and vehicle systems similar to the architectures described inFIGS. 1A and 1B . - The computing channels 202 and 204 may be electrically independent, particularly between LRUs to protect the system from potential faults that could take down or render inoperative all computing channels in a given LRU. However, all channels 202 and 204 within an LRU 200 may share a
common ground 232. -
FIG. 3 is an illustration of an example of avehicle 300 including a multiple redundant system 302 or vehicle management computer system and mission management computer system architecture and packaging in accordance with an embodiment of the present invention. Thevehicle 300 illustrated inFIG. 3 may be an aerospace vehicle, such as an unmanned aircraft or the like, but the present invention may also be applicable to water craft and terrestrial vehicles which may be manned or unmanned. The vehicle management and mission management computer architecture andpackaging 300 may provide quad redundant VMS and MMS computing using two line replaceable units (LRUs) 304 a and 304 b. The LRUs 304 may be similar to the LRU 200 described with reference toFIG. 2 and the VMS and MMS computer architecture and packaging 302 may be similar to that described with reference toFIGS. 1A and 1B . - The two
LRUs FIG. 2 . - The VMS 306 and MMS 308 computing channels may use common processor and memory hardware elements similar to
FIG. 2 . The primary difference between VMS and MMS hardware may be that the VMSC channels 306 may include unique sensors or components. As previously described with reference toFIG. 2 , the VMS 306 unique sensors or components may include an inertial measurement unit (quad) (212 inFIG. 2 ), global positioning system receiver (quad) (210 inFIG. 2 ), and radar altimeter (dual) (214 inFIG. 2 ). Similar to that described with respect toFIGS. 1A and 1B , the VMS channels 306 and the MMS channels 308 may include cross channel data links that exchange data between channels to support redundancy management voting and channel restart capability. - Desirable characteristics of the present invention include light weight and high reliability providing benefit to long endurance applications. Since long endurance is important to unmanned aircraft applications, the present invention has applicability to such technology.
- The flowcharts and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
- The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
- Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art appreciate that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown and that the invention has other applications in other environments. This application is intended to cover any adaptations or variations of the present invention. The following claims are in no way intended to limit the scope of the invention to the specific embodiments described herein.
Claims (22)
1-17. (canceled)
18. A vehicle management and mission management computer architecture and packaging, comprising:
a first line replaceable unit;
a second line replaceable unit;
a pair of vehicle management system computer channels in each line replaceable unit; and
a pair of mission management system computer channels in each line replaceable unit.
19. The vehicle management and mission management computer architecture and packaging of claim 1, further comprising:
a common bus coupling together each vehicle management system computer channel and each mission management system computer channel, and wherein the common bus is adapted to couple each of the channels to at least one mission related system; and
a separate bus to couple each of the vehicle management system computer channels to at least one vehicle system.
20. The vehicle management and mission management computer architecture and packaging of claim 18 , further comprising:
a common bus coupling together each vehicle management system computer channel and each mission management system computer channel, and wherein the common bus is adapted to couple each of the channels to at least one vehicle system; and
a separate bus to couple each of the mission management system computer channels to at least one mission related system.
21. The vehicle management and mission management computer architecture and packaging of claim 18 , further comprising a channel restart feature.
22. The vehicle management and mission management computer architecture and packaging of claim 18 , further comprising a cross channel data link architecture to exchange data between channels and to support redundancy management voting and channel restart capability.
23. The vehicle management and mission management computer architecture and packaging of claim 22 , wherein the cross channel data link architecture comprises:
a plurality of cross channel data links to couple each of the vehicle management system computing channels in the first and second line replaceable units; and
another plurality of cross channel data links to couple each of the mission management system computing channels in the first and line replaceable units.
24. The vehicle management and mission management computer architecture and packaging of claim 18 , further comprising fault protection to prevent all channels in a line replaceable unit from going down.
25-32. (canceled)
33. A method to provide vehicle management and mission management in a low weight and reliable architecture, comprising:
providing a first line replaceable unit;
providing a second line replaceable unit;
providing at least one vehicle management system computer channel in each line replaceable unit; and
providing at least one mission management system computer channel in each line replaceable unit.
34. The method of claim 33 , further comprising:
coupling together each vehicle management system computer channel and each mission management system computer channel with a common bus;
adapting the common bus to couple each of the channels to at least one mission related system; and
coupling each of the vehicle management system computer channels to at least one vehicle system by a separate bus.
35. The method of claim 33 , further comprising:
coupling together each mission management system computer channel and each vehicle management system computer channel with a common bus;
adapting the common bus to couple each of the channels to at least one vehicle system; and
coupling each of the mission management system computer channels to at least one mission related system by a separate bus.
36. The method of claim 33 , further comprising providing a channel restart feature.
37. The method of claim 33 , further comprising:
coupling a plurality of cross channel data links between each of the vehicle management system computer channels in the first and second line replaceable units; and
coupling another plurality of cross channel data links between each of the mission management system computer channels in the first and second line replaceable units.
38. The method of claim 33 , wherein each channel is electrically independent.
39. The method of claim 38 , further comprising separating a quad redundant vehicle management system computing architecture and a mission management system computing architecture into two channels each per line replaceable unit.
40. A vehicle management and mission management computer architecture and packaging, comprising:
a plurality of VMSC channels for communications with a plurality of vehicle systems, each vehicle system being related to operation of a vehicle;
a plurality of MMSC channels for communications with a plurality of mission systems, each mission system being related to a mission performable by the vehicle;
a VMSC common bus coupling together each of the plurality of VMSC channels and adapted to couple each of the plurality of VMSC channels to each mission system;
a separate VMSC bus to couple each VMSC channel to each vehicle system;
a MMSC common bus coupling together each of the plurality of MMSC channels and adapted to couple each of the plurality of MMSC channels to each vehicles system; and
a separate MMSC bus to couple each MMSC channel to each mission system.
41. The vehicle management and mission management computer architecture and packaging of claim 40 , further comprising a cross channel data link architecture to exchange data between channels and to support redundancy management voting and channel restart capability.
42. The vehicle management and mission management computer architecture and packaging of claim 41 , wherein the cross channel data link architecture comprises:
a plurality of cross channel data links to couple each of the VMSC channels; and
another plurality of cross channel data links to couple each of the MMSC channels.
43. The vehicle management and mission management computer architecture and packaging of claim 40 , further comprising a fault protection feature to prevent all VMSC channels and MMSC channels in a single line replaceable unit from becoming inoperative.
44. The vehicle management and mission management computer architecture and packaging of claim 43 , wherein the fault protection feature comprises a quad redundant VMSC architecture and MMSC architecture separated into two channels per line replaceable unit.
45. The vehicle management and mission management computer architecture and packaging of claim 40 , wherein vehicle comprises one of an aerospace vehicle, a watercraft, and a terrestrial vehicle.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/706,164 US20100152919A1 (en) | 2006-09-22 | 2010-02-16 | Vehicle management and mission management computer architecture and packaging |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/534,461 US7689594B2 (en) | 2006-09-22 | 2006-09-22 | Vehicle management and mission management computer architecture and packaging |
US12/706,164 US20100152919A1 (en) | 2006-09-22 | 2010-02-16 | Vehicle management and mission management computer architecture and packaging |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/534,461 Division US7689594B2 (en) | 2006-09-22 | 2006-09-22 | Vehicle management and mission management computer architecture and packaging |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100152919A1 true US20100152919A1 (en) | 2010-06-17 |
Family
ID=39226300
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/534,461 Active 2028-04-30 US7689594B2 (en) | 2006-09-22 | 2006-09-22 | Vehicle management and mission management computer architecture and packaging |
US12/706,164 Abandoned US20100152919A1 (en) | 2006-09-22 | 2010-02-16 | Vehicle management and mission management computer architecture and packaging |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/534,461 Active 2028-04-30 US7689594B2 (en) | 2006-09-22 | 2006-09-22 | Vehicle management and mission management computer architecture and packaging |
Country Status (1)
Country | Link |
---|---|
US (2) | US7689594B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110144828A1 (en) * | 2009-12-11 | 2011-06-16 | The Boeing Company | Unmanned Multi-Purpose Ground Vehicle with Different Levels of Control |
US11618585B2 (en) | 2019-10-10 | 2023-04-04 | Ge Aviation Systems Limited | Integrated system for improved vehicle maintenance and safety |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7831369B2 (en) * | 2005-11-16 | 2010-11-09 | Gm Global Technology Operations, Inc. | Method and apparatus for vehicle and engine operation |
US20080205416A1 (en) * | 2007-02-23 | 2008-08-28 | Honeywell International, Inc. | Flight control computers with ethernet based cross channel data links |
US8370002B2 (en) * | 2009-04-03 | 2013-02-05 | The Boeing Company | Multi-mission remote aerial refueling operator system |
US8601150B1 (en) | 2010-10-01 | 2013-12-03 | The Boeing Company | Cross-channel data link |
US9489195B2 (en) | 2013-07-16 | 2016-11-08 | Raytheon Company | Method and apparatus for configuring control software for radar systems having different hardware architectures and related software products |
US9557406B2 (en) * | 2013-07-16 | 2017-01-31 | Raytheon Command And Control Solutions Llc | Method, system, and software for supporting multiple radar mission types |
US9550583B2 (en) * | 2015-03-03 | 2017-01-24 | Honeywell International Inc. | Aircraft LRU data collection and reliability prediction |
CN105576428A (en) * | 2015-12-10 | 2016-05-11 | 中国航空工业集团公司西安航空计算技术研究所 | Multilayer rigid-flex PCB overlapping structure simultaneously achieving functions of base plate and 1394B bus port |
US10355853B1 (en) * | 2016-08-25 | 2019-07-16 | The United States Of America As Represented By The Secretary Of The Navy | Multilayered obstructed brokered (MOB) embedded cyber security architecture |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3909632A (en) * | 1972-08-21 | 1975-09-30 | Gen Signal Corp | Fail-safe logic circuitry for vehicle transportation control |
US4739469A (en) * | 1984-04-19 | 1988-04-19 | Nissan Motor Company, Limited | Fail-safe circuit for a control system |
US6208923B1 (en) * | 1998-08-01 | 2001-03-27 | Robert Bosch Gmbh | Fault-tolerant electromechanical steer-by-wire steering actuator |
US6636009B2 (en) * | 2000-12-22 | 2003-10-21 | Renk Aktiengesellschaft | Fault-tolerant electromechanical actuating device |
US6640167B1 (en) * | 2003-02-25 | 2003-10-28 | Visteon Global Technologies, Inc. | Method of detecting and managing sensor fault for safety-critical road-wheel position in vehicle steer-by-wire systems |
US6885922B2 (en) * | 2003-06-24 | 2005-04-26 | Visteon Global Technologies, Inc. | System and method of robust fault detection for a vehicle steer-by-wire system |
US6958709B2 (en) * | 2002-08-08 | 2005-10-25 | General Electric Company | Method, system, and storage medium for integrating vehicle management, transportation and communications functions |
US6985803B2 (en) * | 2001-05-30 | 2006-01-10 | General Electric Company | System and method for monitoring the condition of a vehicle |
US7092803B2 (en) * | 2000-08-18 | 2006-08-15 | Idsc Holdings, Llc | Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components |
US7100733B2 (en) * | 2002-07-22 | 2006-09-05 | Visteon Global Technologies, Inc. | Method to initialize steering wheel in a steer-by-wire system |
US7130728B2 (en) * | 2003-03-27 | 2006-10-31 | Toyoda Koki Kabushiki Kaisha | Vehicle steering apparatus and method for controlling the same |
US7222008B2 (en) * | 2002-12-02 | 2007-05-22 | Jtekt Corporation | Vehicle steering control apparatus |
US7317974B2 (en) * | 2003-12-12 | 2008-01-08 | Microsoft Corporation | Remote vehicle system management |
US7447574B1 (en) * | 2004-04-26 | 2008-11-04 | Hti Ip, Llc | In-vehicle wiring harness with multiple adaptors for an on-board diagnostic connector |
US7477968B1 (en) * | 2001-03-14 | 2009-01-13 | Hti, Ip Llc. | Internet-based vehicle-diagnostic system |
-
2006
- 2006-09-22 US US11/534,461 patent/US7689594B2/en active Active
-
2010
- 2010-02-16 US US12/706,164 patent/US20100152919A1/en not_active Abandoned
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3909632A (en) * | 1972-08-21 | 1975-09-30 | Gen Signal Corp | Fail-safe logic circuitry for vehicle transportation control |
US4739469A (en) * | 1984-04-19 | 1988-04-19 | Nissan Motor Company, Limited | Fail-safe circuit for a control system |
US6208923B1 (en) * | 1998-08-01 | 2001-03-27 | Robert Bosch Gmbh | Fault-tolerant electromechanical steer-by-wire steering actuator |
US7092803B2 (en) * | 2000-08-18 | 2006-08-15 | Idsc Holdings, Llc | Remote monitoring, configuring, programming and diagnostic system and method for vehicles and vehicle components |
US6636009B2 (en) * | 2000-12-22 | 2003-10-21 | Renk Aktiengesellschaft | Fault-tolerant electromechanical actuating device |
US7477968B1 (en) * | 2001-03-14 | 2009-01-13 | Hti, Ip Llc. | Internet-based vehicle-diagnostic system |
US6985803B2 (en) * | 2001-05-30 | 2006-01-10 | General Electric Company | System and method for monitoring the condition of a vehicle |
US7100733B2 (en) * | 2002-07-22 | 2006-09-05 | Visteon Global Technologies, Inc. | Method to initialize steering wheel in a steer-by-wire system |
US6958709B2 (en) * | 2002-08-08 | 2005-10-25 | General Electric Company | Method, system, and storage medium for integrating vehicle management, transportation and communications functions |
US7222008B2 (en) * | 2002-12-02 | 2007-05-22 | Jtekt Corporation | Vehicle steering control apparatus |
US6640167B1 (en) * | 2003-02-25 | 2003-10-28 | Visteon Global Technologies, Inc. | Method of detecting and managing sensor fault for safety-critical road-wheel position in vehicle steer-by-wire systems |
US7130728B2 (en) * | 2003-03-27 | 2006-10-31 | Toyoda Koki Kabushiki Kaisha | Vehicle steering apparatus and method for controlling the same |
US6885922B2 (en) * | 2003-06-24 | 2005-04-26 | Visteon Global Technologies, Inc. | System and method of robust fault detection for a vehicle steer-by-wire system |
US7317974B2 (en) * | 2003-12-12 | 2008-01-08 | Microsoft Corporation | Remote vehicle system management |
US7447574B1 (en) * | 2004-04-26 | 2008-11-04 | Hti Ip, Llc | In-vehicle wiring harness with multiple adaptors for an on-board diagnostic connector |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110144828A1 (en) * | 2009-12-11 | 2011-06-16 | The Boeing Company | Unmanned Multi-Purpose Ground Vehicle with Different Levels of Control |
US9163909B2 (en) * | 2009-12-11 | 2015-10-20 | The Boeing Company | Unmanned multi-purpose ground vehicle with different levels of control |
US11618585B2 (en) | 2019-10-10 | 2023-04-04 | Ge Aviation Systems Limited | Integrated system for improved vehicle maintenance and safety |
Also Published As
Publication number | Publication date |
---|---|
US20080077616A1 (en) | 2008-03-27 |
US7689594B2 (en) | 2010-03-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7689594B2 (en) | Vehicle management and mission management computer architecture and packaging | |
EP3514644B1 (en) | Autopilot control system for unmanned air vehicles | |
US11094146B1 (en) | Intelligent electrical system for vehicle | |
Petritoli et al. | Reliability assessment of UAV systems | |
US9313276B2 (en) | Method for transmitting aircraft flight data | |
BR102016021336A2 (en) | apparatus and method for reporting status information to an aircraft | |
US20190228666A1 (en) | System and Method for Reconfiguring a System-On-Module for an Unmanned Vehicle | |
US10663964B2 (en) | Unified and redundant flight and mission control for an unmanned aerial vehicle | |
US10511515B1 (en) | Protocol buffer avionics system | |
CN115390432B (en) | Redundancy unmanned aerial vehicle flight control system and flight control method | |
Nonami | Present state and future prospect of autonomous control technology for industrial drones | |
Hanaway | Space shuttle avionics system | |
Zhao et al. | Reliability analysis of the reconfigurable integrated modular avionics using the continuous-time Markov chains | |
US11409282B2 (en) | Control system for movable body, control method for movable body, and non-transitory storage medium | |
WO2023080955A1 (en) | Modular architecture avionics | |
US10182065B1 (en) | Distributed vetronics intrustion detection system and device | |
US11874673B2 (en) | Integrated travel control and attitude heading reference system | |
CN114637322B (en) | High-orbit satellite anti-collision method and system | |
Succa et al. | IXV avionics architecture: Design, qualification and mission results | |
Song et al. | Study on Practical Use of Air Vehicle Test Equipment (AVTE) for UAV Operation Support | |
CN117833993A (en) | Unmanned aerial vehicle information communication method and control equipment | |
CN115535270A (en) | Aircraft onboard control system, aircraft control system and aircraft | |
Chandler et al. | A low-cost control system for a high-altitude uav | |
Kasai et al. | Technology of H-II transfer vehicle rendezvous system | |
Mueller et al. | Unifled GN&C System for the Space Rapid Transit Launch Vehicle |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |