TReK .NET Framework  5.3.3
Telemetry/Command API
Telemetry .NET API

The TReK Telemetry .NET API contains the same functions that are in the TReK Telemetry API. Each function is wrapped with a .NET wrapper, which allows its use in a .NET environments.

All functions in the API are thread safe. An overview of the capabilities in the Telemetry .NET API are provided in the (trek::trek_user_api) section.

Functions to Retrieve Raw Data

Functions to Retrieve Converted Data

Functions to Retrieve Calibrated Data

General API Functions


Currently Unsupported Functions.
Some of the functions from the Release 3 .NET API are not planned to be supported at this time. If you use these functions and need to continue using them in the future, please contact the TReK help desk.

  • Create_Pseudo - No planned support in release 5.x
  • Remove_Pseudo – No planned support in release 5.x
  • Update_One_Binary_Pseudo - No planned support in release 5.x
  • Update_One_Integer_Pseudo - No planned support in release 5.x
  • Update_One_Unsigned_Integer_Pseudo - No planned support in release 5.x
  • Update_One_Double_Pseudo - No planned support in release 5.x
  • Update_One_String_Pseudo - No planned support in release 5.x
  • Update_Binary_Pseudo - No planned support in release 5.x
  • Update_Integer_Pseudo - No planned support in release 5.x
  • Update_Unsigned_Integer_Pseudo - No planned support in release 5.x
  • Update_Double_Pseudo - No planned support in release 5.x
  • Update_String_Pseudo - No planned support in release 5.x
  • Get_One_Newest_Binary_Pseudo - No planned support in release 5.x
  • Get_One_Newest_Integer_Pseudo - No planned support in release 5.x
  • Get_One_Newest_Unsigned_Integer_Pseudo - No planned support in release 5.x
  • Get_One_Newest_Double_Pseudo - No planned support in release 5.x
  • Get_One_Next_String_Pseudo - No planned support in release 5.x
  • Get_One_Next_Binary_Pseudo - No planned support in release 5.x
  • Get_One_Next_Integer_Pseudo - No planned support in release 5.x
  • Get_One_Next_Unsigned_Integer_Pseudo - No planned support in release 5.x
  • Get_One_Next_Double_Pseudo - No planned support in release 5.x
  • Get_One_Next_String_Pseudo - No planned support in release 5.x
  • Get_Overall_Status - No planned support in release 5.x
  • Get_Newest_Binary_Pseudo - No planned support in release 5.x
  • Get_Newest_Integer_Pseudo - No planned support in release 5.x
  • Get_Newest_Unsigned_Integer_Pseudo - No planned support in release 5.x
  • Get_Newest_Double_Pseudo - No planned support in release 5.x
  • Get_Next_String_Pseudo - No planned support in release 5.x
  • Get_Next_Binary_Pseudo - No planned support in release 5.x
  • Get_Next_Integer_Pseudo - No planned support in release 5.x
  • Get_Next_Unsigned_Integer_Pseudo - No planned support in release 5.x
  • Get_Next_Double_Pseudo - No planned support in release 5.x
  • Get_Next_String_Pseudo - No planned support in release 5.x


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

Telemetry .NET Next Data
This example uses the Get_Next_Converted_Double_Value function.
Source File:
Telemetry_Dotnet_Example/Program.cs


Additional Dependencies
The TReK Telemetry .NET API is also dependent on the following libraries. See the Libraries main help page for more information.

trek_telemetry_api
trek_user_api
trek_toolkit_common_api
trek_toolkit_data_api
trek_toolkit_utilities_api
xerces-c_3_1