The Custom Device XML file enables you to define parts of the custom device in System Explorer, specify which VIs to call, and select the dependencies to deploy to an RT target.

When VeriStand launches, it uses the Custom Device XML file in the <Common Data>\Custom Devices directory to determine how to load, configure, display, and run custom devices. This XML file provides basic information about a custom device, including the type of custom device, paths to its VIs and dependencies, and pages, glyphs, buttons, and menu items associated with the custom device.

Every custom device must have a Custom Device XML file in the directory. A properly formatted XML file correctly implements the tags defined by the Custom Device XSD file located in the same directory. The XML file must have its custom device type defined in its title before the device name. The following are examples of properly named XML files:
  • Custom Device <Device Name>.xml
  • SLSC Module <Device Name>.xml
  • Timing and Sync <Device Name>.xml
Note You must restart VeriStand to recognize new or changed Custom Device XML files. After you restart, VeriStand will report errors in the XML.
The <Common Data>\Custom Devices directory also includes Custom Device XML files for the custom devices that install with VeriStand. You can use these XML files for reference when structuring your XML.
Caution Do not directly edit the contents of the included Custom Device XML files. Edits to the file can break the custom devices.