Table Of Contents

Resolving Behavioral Changes in Converted LabVIEW NXG Code

Last Modified: September 28, 2017

Resolve behavioral changes in your converted code to replicate the original source code in this software.

Before you can resolve behavioral changes in the new source code, you must convert code from a supported version of LabVIEW for use with LabVIEW NXG. Refer to Converting Your Code for help converting code for use with LabVIEW NXG.

  1. If the new project did not launch automatically after the Code Conversion Utility finished converting your source code, launch the newly generated projects using LabVIEW NXG to begin reviewing the converted code.
  2. In the Conversion Report tab, review the messages and determine if you need to resolve any messages by updating the original source code.

    Conversion messages that list SourceFile in the Category column usually correspond to issues that can be resolved only in the original source code.

  3. If you make any changes to the original LabVIEW source files, convert the original source files again. Because the Code Conversion Utility generates a unique copy of the converted code each time it runs, the code generated when you rerun conversion will not include any changes you made to code from a previous conversion. This means you should always resolve issues by updating the original source files before modifying the converted code.
  4. After resolving the issues in the original LabVIEW source code and rerunning conversion, identify messages that affect the core functionality of your code and begin resolving changes in your converted code by evaluating the severity and category of the messages.

    You can click the message in the Description column of the Conversion Report tab to open the associated location in the editor.

    The following tables describe the possible severity levels and category tags of conversion messages.
    Severity Level Description
    ManualFix The Code Conversion Utility did not convert the associated item to a runnable state. You must update the associated item to restore dataflow in the converted code. This is the highest severity level for a message.
    ReviewRequired The associated item changed in some way, and the runtime behavior of the item may differ from the original source code. The change may or may not affect the behavior of the code, so you should review this change in the editor to determine whether you need to update the associated item.
    Info The Code Conversion Utility changed the associated item in a way that does not affect the behavior of the code. You do not need to take any action for info messages.
    Category Tag Description
    Error The Code Conversion Utility encountered an unexpected error. Contact NI Support for conversion messages with the category tag Error.
    NotConverted The Code Conversion Utility could not access a missing file, file in vi.lib, password protected file, or unlicensed file.
    SourceFile Address the associated message in the original source code.
    Placeholder The Code Conversion Utility replaced a section of the original source code with a placeholder node. The Code Conversion Utility uses placeholder nodes to preserve dataflow for unsupported features or missing subVI references.
    Panel Something changed on the panel. Most converted code contains many minor changes to the panel, especially for VIs that include complex panels.
  5. If a core feature of your code is not supported in this application, wrap the code in a subVI in the original source code, and call the subVI into this application using a VI Interop node. Instead of using many VI Interop nodes to replace individual missing nodes, attempt to modularize calls to the previous LabVIEW product into as few VI Interop nodes as possible. Each time you call code outside of this application, the efficiency of your code decreases.

Recently Viewed Topics