When you create a new custom device that provides DUT- or socket-specific functionality for your Battery Test System implementation, you may need to create a custom device compiler plugin to incorporate a customized version of the device into the VeriStand system definition file for the system. For example, you might create a custom device that provides a map table that is specific to a particular DUT.

Custom devices in VeriStand add support for the custom hardware interfaces to the system definition file; compiler plugins incorporate these custom devices into the Battery Test System and enable users of the system to input parameters for the custom device with corresponding custom XML configuration files. Custom Device Compiler Plugins are implemented in two parts, a C# plugin that integrates into the Battery Test System backend and a LabVIEW plugin that modifies the VeriStand System Definition.