Configuring typical devices in the telemetry community requires the creation of complex,
device-specific configuration files. While the grammar of the configuration files is vendor
neutral, the device specific details are vendor specific. Thus, a naïve approach to building these
files is to construct a file, test it against a device, and then iterate. The specification sheets (and
other documents) for the device can serve as a guide, but the details of flight test configuration
possibilities are immense and, in this community, typically not fully documented. This paper
describes a process of creating a set of general rules describing characteristics of a configuration
file and using those rules to discover the configuration constraints of telemetry devices
automatically. The discovered constraints posed by a particular vendor’s device can then be
quickly formed into a correct-by-construction constraint-based grammar for use in other systems.
| Identifer | oai:union.ndltd.org:arizona.edu/oai:arizona.openrepository.com:10150/624240 |
| Date | 11 1900 |
| Creators | Whittington, Austin J., Youngs, Alexander G., Harwell, John R., Moodie, Myron L. |
| Contributors | Southwest Research Institute |
| Publisher | International Foundation for Telemetering |
| Source Sets | University of Arizona |
| Language | en_US |
| Detected Language | English |
| Type | text, Proceedings |
| Rights | Copyright © held by the author; distribution rights International Foundation for Telemetering |
| Relation | http://www.telemetry.org/ |
Page generated in 0.0056 seconds