The Configuration Utility enables you to easily edit configuration files.

The Section Tree

The Sections column shows the structure of the selected file as a tree.
  • Configuration is the root node. Selecting this shows the general settings sections combined in the editor.
  • Each instrument (VST) and coprocessor appears as their own nodes beneath Configuration.
  • An attenuator (AATT) appears as a child node under the instrument it is associated with.
  • If you add an attenuator that is not yet assigned to an instrument, it appears under an Unassociated group until you associate it.
Select any node to edit its fields in the right-hand pane.

The Editor Pane

The Editor shows the fields (keys) for the selected section in a consistent order. The control used for each field depends on the kind of value it holds.
Table 39. Configuration File Keys and Controls
Field Type Control Type Allowed Values
Free text Text box General text values.
Whole number Text box Must be a non-negative whole number; some fields enforce a maximum.
Number Text box Accepts decimal values.
True/False Drop-down Choose True or False.
Choice list Drop-down Choose from the allowed values.
PXI trigger Drop-down Choose a trigger line (or leave blank for none).
IP address Text box Must be a valid IPv4 address or localhost.
File path Text box with ... button. Click ... to browse for a file.
Where a field has units, the unit is shown in parentheses next to the field name. Changes you make take effect immediately and mark the file as having unsaved changes.

The File Description

At the top of the Editor pane is an editable Description box. This corresponds to the comment block at the top of the file and is a good place to record notes about what the configuration is for. Edits here also mark the file as changed.

Validation Indicators

Each field shows a small colored dot that reflects its current state. Hover over the dot to see a tooltip explaining the status.
Table 40. Field Status Indicators
Color Meaning
Green The value is valid.
Yellow The field is acceptable but there is something to flag.

For example, some checks are skipped because a metadata field is empty.
Red The value is invalid and must be corrected.

For example, a number is out of range or there is a duplicate trigger assignment.
The utility also performs some cross-checks across sections, such as flagging incompatible model combinations or warning when two instruments use the same PXI trigger output.