You can configure the Coprocessor through an INI file or option string.

INI File

Initializing the Coprocessor requires the following information. Use <Coprocessor Name> for Create Coprocessor configuration, where <Coprocessor Name> is the instrument name listed in NI MAX.

Table 37.
Section Key Use
<Coprocessor Name> coprocessor bitfile path Full path (including filename and extension) to the custom bitfile.
minimum latency (s) The time (in seconds) that a sample is delayed through the combined RTG+Coprocessor system.
coprocessor link timeout (s) The time (in seconds) to allow the Coprocessor and the RTG VST to establish an Aurora link over the MGT interface

If not extending the Coprocessor base class, calling Create Coprocessor VI from the RTG Coprocessor Link Interface class library adds the ability to read configuration values from the RTG INI file. Refer to RTG Configuration Sections and Keys for a list of sections and keys to use when incorporating a Coprocessor in your RTG system.

Option String

If not extending the Coprocessor base class, calling Create Coprocessor VI from the RTG Coprocessor Link Interface class library adds the ability to read configuration values from an option string. For each Coprocessor, create a section using the instrument name listed in NI MAX. Refer to RTG Configuration Sections and Keys for a list of option strings to use when incorporating a Coprocessor in your RTG system.

Note Be aware of the following Coprocessor option string behavior:
  • The option string overrides any incoming Coprocessor parameters, including what is in the INI file.
  • If a field is not present, that input parameter is modified.