Modular mission payload control software

• US 6,873,886 B1
• Filed: 11/27/2002
• Issued: 03/29/2005
• Est. Priority Date: 11/27/2002
• Status: Active Grant

• Current Assignee: the united states of america as represented by the secretary of the navy
• Original Assignee: the united states of america as represented by the secretary of the navy
• Inventors: Milhouse, Keith D., Schmidt, Paul L., Mullen, Robert E.
• Primary Examiner(s): Zanelli, Michael J.
• Application Number:
  US10/307,534
• Time in Patent Office: 853 Days
• Field of Search: 701/2, 701/3, 701/33, 701/36, 244/189, 244/190, 709/203, 709/217, 709/219
• US Class Current: 701/2
• CPC Class Codes: B64G 1/24 Guiding or controlling apparatus, e.g. for attitude control

Abstract

The present application discloses an open system architecture and software system for plug and play modular mission payloads in aerial vehicles. The improved software moves the control function of mission payloads away from the ground station and into the aerial vehicle. The plug & play web-based payload interface software resides in a payload interface controller in the vehicle, and this is networked via a uniform resource locator (URL) address to a ground control station. Consequently, when new payloads are added to the system, integration issues and costs are minimized.

Claims

1. A software system for remote control of any of a variety of different payloads in a vehicle, comprising:

a software module resident on a dedicated payload interface controller in said vehicle and containing payload-specific data parameters;

a software application resident on said payload interface controller and including a standardized command set as required to control multiple different payloads, said software application incorporating the data parameters of the software module into said command set for issuing payload-specific commands to said payloads.

2. The software system according to claim 1, wherein said software module resident on said dedicated payload interface controller serves as a plug-in to said software application to allow the payload interface controller to interface with a payload.

3. The software system according to claim 1, further comprising an identify program that runs at boot-up to identify a payload connected to the payload interface controller and to populate a configuration file in accordance therewith.

4. The software system according to claim 3, wherein said software application boots to initialize the standardized command set, reads the configuration file created by the identify program, and then executes the appropriate payload-specific software module.

5. The software system according to claim 1, wherein said payload-specific software module is a web-enabled plug-in module.

6. The software system according to claim 5, wherein said payload-specific software module is a web-enabled plug-in module stored at a uniform resource locator (URL) address of said payload interface controller.

7. The software system according to claim 1, further comprising a Java client interface coupled to a server by the standardized command set through a TCP socket.

8. The software system according to claim 7, wherein the server interfaces with the payloads.