Table Of Contents

ExpressVINotSupported

Last Modified: October 4, 2017

The Code Conversion Utility replaced an Express VI because this version of LabVIEW NXG does not support all Express VIs.

The Express VI replacement depends on the Express VI:
  • The Code Conversion Utility converts Express VIs you create with placeholder nodes.
  • The Code Conversion Utility converts NI-created Express VIs in the following ways:
Replacement Rationale
Plugin node Occurs when the Express VI in LabVIEW is equivalent in execution and edit behavior to the Express VI in LabVIEW NXG. You can edit the plugin node settings in the configuration pane.
SubVI Occurs based on all of the following factors:
  • The Code Conversion Utility can convert the Express VI's diagram to LabVIEW NXG.
  • The Express VI does not contain protected IPs.
  • The Express VI contains functionality that is difficult to re-create by hand.
The Express VI converts to a subVI, which has the same execution behavior as the original Express VI. You may or may not receive conversion messages during conversion.
spd-note-note
Note  

The edit behavior of the Express VI changes during conversion. You can no longer change your Express VI settings in the configuration wizard.

Placeholder node Occurs when LabVIEW NXG does not support the Express VI.

What to Do

See the Addressing Placeholders to Correct Converted Code topic for more information on how to fix placeholders.

Alternate Workarounds

If the previous suggestions don't restore the functionality of the affected code and the code isn't essential to the core functionality of your application, you can remove the portion of code. If the code is part of the core functionality of the application, you can use the VI Interop node to call your existing code, provided that the new code organization meets the architectural goals of your application. If neither solution meets the requirements of your application, do not migrate to LabVIEW NXG at this time.


Recently Viewed Topics