TReK ANSI-C
5.3.3
All ANSI-C APIs
|
The Command ANSI-C API provides a backward compatible thread-safe Command 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 Command C++ API to provide its functions. For new code consider using the Command C++ API as it provides more features than the Command ANSI-C API. A few functions from the Release 3.x API are not currently supported. Information is provided about these functions further down this page.
Sending Commands
There are six functions provided to send commands. The availability of any of the functions is dependent on the destination. All of the functions will fail safely if not available for a destination.
Updating Commands
Any command that is added from the GUI can be updated through the Command ANSI-C API.
Destination Specifics
For a POIC destination you can obtain status and configuration information through the Command ANSI-C API.
Currently Unsupported Functions.
These functions all required the Remote Services application available in Release 3. Current security requirements make a new application more difficult to support and these are not planned for future development. If you use these functions and need to continue using them in the future, please contact the TReK help desk.
Examples
The following examples are provided to show how to use Command APIs:
Command ANSI-C API Example
Uses the Release 3 Compatible API to check on user status, update, and uplink a command.
Source File:
cmd_api_r3/cmd_api_r3_main.c
Additional Dependencies
The TReK Command ANSI-C API (trek_cmd_user_api) is also dependent on the following libraries. See the Libraries main help page for more information.
trek_command_api
trek_toolkit_common_api
trek_toolkit_data_api
trek_toolkit_utilities_api
xerces-c_3_1