The Telemetry Encoder Shell accepts telemetry data formatted as packets. It also accepts data for the Frame Secondary Header (FSH) and the Operational Control Field (OCF). (See the separate description for details of the Telemetry Features supported by the Telemetry Encoder Shell. For example, it describes the FSH and the OCF. See the TM Standards for a list of the specification documents.)
The Telemetry Encoder Shell delivers transfer frames, ready for coding and modulation.
Telemetry interfaces
There are telemetry interfaces in the API, shown by left-to-right arrows in the diagram. The Environment calls the Shell to:
The Shell calls the Environment to:
Management interfaces
There are management interfaces in the API, shown by downwards arrows in the diagram. The Environment calls the Shell to:
The Shell calls the Environment for storage allocation and for the optional logging of messages.
A telemetry system built with this package is likely to be very much cheaper than independent development of an equivalent capability.
Licensing and support may be negotiated according to requirements. All the Telemetry Features are included in the Telemetry Encoder Shell.
The Telemetry Encoder Shell code is written in ANSI/ISO 9899-1990 C and is highly modular and easy to maintain. The code makes no calls to the operating system run-time libraries and it is therefore easily portable to different computer architectures. The code has been compiled by a number of independent ANSI C compilers and the demonstration program produces identical results in each case.
Please contact us for further information on technical questions or licensing conditions for the Telemetry Encoder Shell package.
TM Standards
TM Features
TM Encoder Shell
TM Decoder Shell