Automatic generation of telemetry flight software accompanying specifications, and decode files

• US 8,132,155 B2
• Filed: 05/05/2006
• Issued: 03/06/2012
• Est. Priority Date: 04/27/2004
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Gvillo, Dennis W.
• Primary Examiner(s): DAS, CHAMELI
• Application Number:
  US11/381,934
• Publication Number:
  US 20070032922A1
• Time in Patent Office: 2,132 Days
• Field of Search: 717/124, 717/126, 717/136, 717/140, 717/139, 717/170, 714/25, 714/26, 714/38, 701/3, 701/14, 701/27, 701/29, 707/690, 707/695, 703/8
• US Class Current: 717/124
• CPC Class Codes: G06F 8/30 Creation or generation of source code

Abstract

A computer readable media, includes instructions capable of being interpreted for execution by a computer processor. The instructions provide information sufficient for: reading a master telemetry definition data file; producing a source code for implementing a data stream telemetry method, and generating documentation files for the source code. The source code includes a get component, a format component, and a blocks component. The get component includes source code for accessing flight software variable values according to the master telemetry definition data file. The format component includes source code for scaling the flight software variable values according to the master telemetry definition data file. The format component includes source code for formatting the values as telemetry stream parameters according to the master telemetry definition data file. The blocks component includes source code for placing telemetry parameters into a data stream according to the master telemetry definition data file.

Claims

1. A computerized method of testing and verifying telemetry flight software, comprising steps of:

providing a source code for implementing a data stream telemetry software, the source code including a format component wherein,

the format component includes source code for scaling flight software variable values; and

the format component includes source code for formatting the values as telemetry stream parameters;

providing a unique version identifier in an auto-generated telemetry flight software;

compiling the auto-generated telemetry flight software into an operational flight program for testing;

running said operational flight program in a canned mode on a computer;

writing a simulated telemetry data stream from said operational flight program to a data file;

decoding said data file into a tabular format showing a value of each telemetry parameter in the simulated telemetry data stream data file;

checking on the computer said telemetry parameter values in said simulated telemetry data stream data file against pre-determined canned values expected to be written into the simulated telemetry data stream by said operational flight program; and

verifying on the computer the unique version identifier.

2. The method of claim 1 further comprising steps of:

reading a canned values report;

checking said telemetry parameter values in said simulated telemetry data stream data file against canned values from said canned values report; and

producing a report of any discrepancies between said telemetry parameter values and said canned values.

3. The method of claim 1 further comprising steps of:

providing a unique version identifier of telemetry stream format for said simulated telemetry data stream;

comparing a version identifier actually written by said operational flight program to said simulated telemetry data stream with said unique version identifier of telemetry data stream format.

4. The method of claim 1 further comprising the step of generating a warning when said telemetry parameter value in said simulated telemetry data stream data file does not match the pre-determined canned value.

5. The method of claim 1 further comprising the step of correcting the telemetry flight software.

6. The method of claim 1 further comprising the step of ensuring that all of the canned data and each of the telemetry flight parameters processed by the operational flight program are checked.

7. The method of claim 6 wherein the step of ensuring comprises following a loop structure.

8. A computerized method for verifying correct operation of telemetry flight software, comprising steps of:

using a master telemetry definition data file to produce an operational flight program for telemetry;

providing a unique version identifier for a telemetry stream format for the simulated data stream;

reading, by a processor, a set of canned values expected to be written into a simulated telemetry data stream by the operational flight program;

executing the operational flight program using the set of canned values;

comparing, by the processor, a value actually written by the operational flight program to a simulated data stream with a value from said set of canned values expected to be written;

comparing a version identifier actually written by the operational flight program to the simulated data stream with the unique version identifier to verify the version identifier; and

ensuring that all of the canned data and each of the telemetry flight parameters processed by the operational flight program are compared.

9. The method of claim 8 further comprising a step of:

generating a warning message when said value actually written does not match said value expected to be written.

10. The method of claim 8 wherein said reading step comprises:

reading said set of canned values from a canned values report generated by a method that generates source code for said operational flight program.

11. The method of claim 8 wherein the step of comparing further comprises checking that the value actually written by an operational flight program matches the canned value from the simulated data stream.

12. The method of claim 11 further comprising correcting the telemetry flight software if the value actually written does not match the canned value from the simulated data stream.

13. The method of claim 8 further comprising the step of producing a report of any discrepancies between the value actually written by an operational flight program and the expected canned value.

14. The method of claim 8 wherein the step of ensuring comprises following a loop structure.