OPEN ARCHITECTURE VEHICLE INFORMATION MODULE AND SYSTEM AND METHOD THEREOF

• US 20100211581A1
• Filed: 02/17/2009
• Published: 08/19/2010
• Est. Priority Date: 02/17/2009
• Status: Abandoned Application

• Current Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Original Assignee: Lockheed Martin Corporation (Martin Marietta Corporation)
• Inventors: Jesse, Patrick, Kane, Michael, KOTSKI, Jennifer, Cole, John J., Leas, Matthew, Coffman, Conrad
• Application Number:
  US12/372,350
• Publication Number:
  US 20100211581A1
• Time in Patent Office: Days
• US Class Current: 707/756
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C
• CPC Class Codes: G07C 5/085 using electronic data carriers

Abstract

A module, system, and method for presenting vehicle data to a client. A vehicle information module (VIM) is configured to interpret, store, and communicate to interested clients the status of a vehicle. Interested clients or end-users may include a GUI, a database, an Interrogative Diagnostics & Prognostics System and other future stakeholders, such as a fleet management system, a logistics system, a maintenance system, and a mobile personal digital assistant.

Claims

1. A method for presenting vehicle data of a wheeled tactical vehicle to a client using a vehicle information module of a vehicle management system, the vehicle information module being configurable through a series of eXtensible Markup Language (XML) files, the XML files defining device addresses, messages, and desired fields, and the method comprising:

receiving at the vehicle information module of the vehicle management system, vehicle messages including vehicle data;

selectively translating the received vehicle messages into individual data fields using the vehicle information module;

receiving a request from a client for vehicle data, the requested vehicle data including data representing a status of the wheeled tactical vehicle; and

sending to the client requested vehicle data based on said receiving the request, said sending being via a webservice interface,

wherein said selective translating being based on the desired fields specified in the XML files, and said selective translating being performed such that only vehicle messages necessary to populate the desired fields specified in the XML files are translated.

2. The method of claim 1,

wherein the vehicle information module is configurable such that modification of addresses, messages, or data fields in response to a change in the wheeled tactical vehicle'"'"'s physical configuration is performed through modification of the XML files, and

wherein the XML files of the vehicle information module are not recompiled in response to the change or modification.

3. The method of claim 1, wherein said receiving at the vehicle information module includes receiving vehicle data sent from a vehicle sensor.

4. The method of claim 1, wherein the vehicle messages include messages from separate sources including a first source and a second source, the first source being via a controller area network (CAN) bus and the second source being via Ethernet.

5. The method of claim 4, wherein messages from the Ethernet include vehicle prognostics data.

6. The method of claim 1, wherein the client is one of a graphical user interface, a database, an Interrogative Diagnostics and Prognostics system, a fleet management system, a logistics system, a maintenance system, and a mobile personal digital device.

7. A system for presenting specific vehicle data to a client upon request, the system comprising:

means for receiving a first vehicle message signal including vehicle status information, the first vehicle message signal being in a first data format;

means for receiving a second vehicle message signal including vehicle status information, the second vehicle message signal being in a second data format, the second data format being different from the first data format;

means for translating the first message in the first format to a third data format;

means for translating the second message in the second format to the third data format;

means for receiving a request for vehicle status information; and

means for transmitting only requested vehicle status information, the transmitted vehicle status information being transmitted in the third data format,

wherein the first data format is associated with a vehicle bus, and

wherein the second data format is associated with a prognostics-specific format.

8. The system of claim 7, wherein the vehicle bus is a CAN bus.

9. The system of claim 7,

wherein said means for translating the first message in the first format to the third data format selectively translates the first message based on a configuration of one or more eXtensible Markup Language (XML) files, the selective translating being done such that only first message data necessary to populate desired fields specified in the XML files are translated, and

wherein said means for translating the second message in the second format to the third data format selectively translates the second message based on the configuration of the one or more XML files, the selective translating being done such that only second message data necessary to populate desired fields specified in the XML files are translated.

10. The system of claim 7, wherein the request for vehicle status information is from one of a graphical user interface, a database, an Interrogative Diagnostics and Prognostics system, a fleet management system, a logistics system, a maintenance system, and a mobile personal display device.

11. A method for providing specific data to an end-user, the method comprising:

selectively interpreting received messages associated with a mechanical system, said selectively interpreting being based on a configuration of one or more eXtensible Markup Language (XML) files, the XML files being reconfigurable based on a physical change made to the mechanical system;

receiving a request from an end-user for specific data, the specific data being associated with a current status of the system; and

sending to the end-user only the requested data in response to the received request,

wherein the end-user is one of a graphical user interface, a database, an Interrogative Diagnostics and Prognostics system, a fleet management system, a logistics system, a maintenance system, and a mobile personal display device.

12. The method of claim 11, wherein the mechanical system is a wheeled vehicle, and the messages associated with the wheeled vehicle include CAN bus messages.

13. The method of claim 11, wherein the mechanical system is an aircraft.

14. The method of claim 11, wherein said sending only the requested data is performed periodically.

15. The method of claim 11, wherein said sending only the requested data is performed based on changing data.

16. The method of claim 11, wherein the mechanical system is a helicopter.

17. The method of claim 11, wherein the end-user is a fleet management system.

18. The method of claim 11, wherein the end-user is a maintenance system.

19. The method of claim 11, wherein the end-user is a mobile personal display device.

20. The method of claim 11,

wherein the one or more eXtensible Markup Language (XML) files respectively represent an electronic control unit (ECU) of the mechanical system, and

wherein the one or more XML files are configured to represent a current state of the mechanical system.