USER MANUAL
URM18PH392 Rev A. May 2020 Page 35 of 86
4. VIPER™ COMMAND INTERFACE
The purpose of this section is to describe VIPER™ configuration settings and other commands. These settings are
applied to the system via the VIPER™ command interface, which defines the commands, actions, and
configuration data used to interact with the tracker device.
VIPER™ commands can be applied to the device with the VIPER™ Command Manager or directly via the USB or
RS422 I/O channel with a user-developed custom application.
For application development, Polhemus offers an open-source Standard C++ SDK conforming to C++14 core
language features. Refer to online developer resources for details on the use of the VIPER™ command interface
directly or with these VIPER™ SDK libraries. Links to online developer resources are provided in the Release Notes
of the VIPER™ Host Software installation media.
4.1 COMMAND SUMMARY
VIPER™ commands fall into a variety of categories:
Command is applied per-SEU or per-Sensor.
Some commands are Executive in nature in that they perform executive actions on the running SEU.
Some are Get-only, reporting the current state of the system or version and/or serial numbers.
Configuration commands may pertain to persistent or not-persistent configuration settings.
The tables below list the main user commands and summarize their scope and function.
TABLE B. CONFIGURATION COMMANDS - PERSISTENT
TABLE C. CONFIGURATION COMMANDS -- NOT PERSISTENT (RUN-TIME ONLY)
To Next Page
Loading...