TReK ANSI-C  5.3.3
All ANSI-C APIs
Telemetry ANSI-C API

The Telemetry ANSI-C API provides a backward compatible thread-safe Telemetry API for user developed programs originally written for TReK Release 3.x. The API is provided to allow user applications that integrated TReK 3.x APIs an easy path to upgrade to the latest TReK release. It uses the Telemetry C++ API to provide its functions. A few functions from the Release 3.x API are not currently supported.
Information is provided about these functions further down this page.

Functions to Retrieve Raw Data

  • GetOneNewestRawValue() - Retrieves the newest unprocessed value for the specified parameter.
  • GetOneNextRawValue() - Retrieves the next unprocessed value for the specified parameter.
  • GetOneSamePacketRawValue() - Retrieves the unprocessed value for the specified parameter from the same packet as another parameter.
  • GetNewestRawValue() - Retrieves one or more newest unprocessed values for the specified parameter.
  • GetNextRawValue() - Retrieves one or more next unprocessed values for the specified parameter.
  • GetSamePacketRawValue() - Retrieves one or more unprocessed values for the specified parameter from the same packet as another parameter.

Functions to Retrieve Converted Data

Functions to Retrieve Calibrated Data

General API Functions

New Release 3 Compatible Functions


Removed Functions
These functions are not supported in this release of the Telemetry ANSI-C API. All of the APIs that have no planned support are related to the pseudo telemetry capability within TReK for Release 3.x. If you use unsupported functions and need the to continue using them in the future, please contact the TReK help desk.

  • CreatePseudo - No planned support in release 5.x
  • RemovePseudo – No planned support in release 5.x
  • UpdateOneBinaryPseudo - No planned support in release 5.x
  • UpdateOneIntegerPseudo - No planned support in release 5.x
  • UpdateOneUnsignedIntegerPseudo - No planned support in release 5.x
  • UpdateOneDoublePseudo - No planned support in release 5.x
  • UpdateOneStringPseudo - No planned support in release 5.x
  • UpdateBinaryPseudo - No planned support in release 5.x
  • UpdateIntegerPseudo - No planned support in release 5.x
  • UpdateUnsignedIntegerPseudo - No planned support in release 5.x
  • UpdateDoublePseudo - No planned support in release 5.x
  • UpdateStringPseudo - No planned support in release 5.x
  • GetOneNewestBinaryPseudo - No planned support in release 5.x
  • GetOneNewestIntegerPseudo - No planned support in release 5.x
  • GetOneNewestUnsignedIntegerPseudo - No planned support in release 5.x
  • GetOneNewestDoublePseudo - No planned support in release 5.x
  • GetOneNextStringPseudo - No planned support in release 5.x
  • GetOneNextBinaryPseudo - No planned support in release 5.x
  • GetOneNextIntegerPseudo - No planned support in release 5.x
  • GetOneNextUnsignedIntegerPseudo - No planned support in release 5.x
  • GetOneNextDoublePseudo - No planned support in release 5.x
  • GetOneNextStringPseudo - No planned support in release 5.x
  • GetOverallStatus - No planned support in release 5.x
  • GetNewestBinaryPseudo - No planned support in release 5.x
  • GetNewestIntegerPseudo - No planned support in release 5.x
  • GetNewestUnsignedIntegerPseudo - No planned support in release 5.x
  • GetNewestDoublePseudo - No planned support in release 5.x
  • GetNextStringPseudo - No planned support in release 5.x
  • GetNextBinaryPseudo - No planned support in release 5.x
  • GetNextIntegerPseudo - No planned support in release 5.x
  • GetNextUnsignedIntegerPseudo - No planned support in release 5.x
  • GetNextDoublePseudo - No planned support in release 5.x
  • GetNextStringPseudo - No planned support in release 5.x


Examples
The following examples are provided to show how to use Telemetry APIs:

Telemetry ANSI-C Newest Data
Uses the Telemetry ANSI-C to get the latest version of several parameter values. The technique used to retrieve data in this example is useful for applications such as displays.
Source File:
tlm_api_r3_newest/r3_newest_main.c

Telemetry ANSI-C Next Data
Uses the Telemetry ANSI-C to get ever data zone from a packet. This example also shows how you can set up your code to wait for new packets to arrive and then retrieve the data.
Source File:
tlm_api_r3_next/r3_next_main.c

Telemetry ANSI-C Same Packet Data
Uses the Telemetry ANSI-C API to get multiple parameters from the same packet. This example shows using a "newest" function as controlling the packet, but the same techniques can be used with a "next" function.
Source File:
tlm_api_r3_same_pkt/r3_same_pkt_main.c


Additional Dependencies
The TReK Telemetry ANSI-C API (trek_user_api) is also dependent on the following libraries. See the Libraries main help page for more information.

trek_telemetry_api
trek_toolkit_common_api
trek_toolkit_data_api
trek_toolkit_utilities_api
xerces-c_3_1