Considerations for Converting Single LabVIEW VIs to LabVIEW NXG

You have the option of using the Code Conversion Utility or Convert a Stand-Alone VI when converting your LabVIEW VI for use in LabVIEW NXG.

When your VI is converted, the LabVIEW code is automatically replaced with the equivalent LabVIEW NXG code and other dependencies are replaced with placeholders. This happens when using either the Code Conversion Utility or Convert a Stand-Alone VI . However, Convert a Stand-Alone VI does not support VIs with dependencies or all VI types. For this reason, it is important to understand which conversion option will work best for your individual VI. Use the following table as a guide for choosing either the Code Conversion Utility or Convert a Stand-Alone VI .

Table 1. Conversion Support for LabVIEW VIs to LabVIEW NXG
LabVIEW VI Supported by Code Conversion Utility Supported by Convert a Stand-Alone VI
VIs with dependencies ■
VIs without subVIs or dependencies (such as classes or type definitions) ■ ■
VIs part of an .lvlib, class, or XControl ■
Polymorphic VIs ■
Global VIs ■
Malleable VIs (.vim) ■
Target-specific resources, such as FPGA resources (clocks, memory, etc.) ■
Run-time menu files ■
VIs with Call Library Function nodes ■
VIs with FPGA External IP nodes ■
VIs with Express VIs on the diagram ■
VIs with Malleable VIs on the diagram ■
VIs with Channels ■
VIs with Call By Reference nodes configured to statically reference subVIs by path ■
VIs with Target-specific resources, such as FPGA resources (clocks, memory, etc.) ■
Note This table is not a comprehensive list of all LabVIEW VIs supported by the Code Conversion Utility.