Adding Support for LXI

The level of LXI compliance supported by the driver can be changed at any stage of development. Nimbus performs a number of roundtripping operations based upon the specific level of LXI compliance chosen. For example, changing the conformance from None to LXI Core 2016 and adding support for LXI Event Messaging adds several repeated capabilities to the driver as well as a host of methods, properties, and interfaces. Correspondingly, decreasing the level of compliance will cause Nimbus to remove code from the project.

Caution

When decreasing the level of LXI compliance, Nimbus removes implementation and test code from the project. It is important to ensure that no code of interest exists in the LXI-related implementation and test files before changing the driver to support a lower level of LXI compliance.

The table below shows the modifications Nimbus performs on your driver project based upon the level of LXI compliance selected.

LXI Support Selected	Project Modifications Performed
No Support	No modifications.
Class A	Adds a reference to the IviLxiSync type library. Creates the appropriate IviLxiSync interfaces and repeated capabilities. Adds repeated capability names for LAN triggers (LAN0...7). Adds repeated capability names for the LXI hardware trigger lines (LXI0...7).
Class B	Adds a reference to the IviLxiSync type library. Creates the appropriate IviLxiSync interfaces and repeated capabilities. Adds repeated capability names for LAN triggers (LAN0...7).
Class C	No modifications.

Tip

If the IviLxiSync interfaces contain a repeated capability that represents the same physical repeated capability as one already defined in the driver, then you may want to merge the repeated capabilities.