AUTOMATIC GENERATION OF TELEMETRY FLIGHT SOFTWARE ACCOMPANYING SPECIFICATIONS, AND DECODE FILES

• US 20070032922A1
• Filed: 05/05/2006
• Published: 02/08/2007
• Est. Priority Date: 04/27/2004
• Status: Active Grant

• Current Assignee: Dennis Gvillo
• Original Assignee: Dennis Gvillo
• Inventors: GVILLO, DENNIS
• Granted Patent: US 8,132,155 B2
• Time in Patent Office: Days
• US Class Current: 701/3
• 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-31. -31. (canceled)

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

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

running said operational flight program in a canned mode;

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

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

33. The method of claim 32 further comprising a step of:

checking 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.

34. The method of claim 32 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.

35. The method of claim 32 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.

telemetry data stream format

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

reading a set of canned values; and

comparing a value actually written by an operational flight program to a simulated data stream with a value from said set of canned values expected to be written.

37. The method of claim 36 further comprising a step of:

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

38. The method of claim 36 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.

39. The method of claim 36 further comprising steps of:

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

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

40-42. -42. (canceled)