Table Of Contents

Resolving Behavioral Changes in Converted LabVIEW NXG Code

Last Modified: August 7, 2018

Modify the parts of your converted code in LabVIEW NXG where behavior differs between LabVIEW and LabVIEW NXG, to replicate the behavior of your original LabVIEW source code.

  1. Launch the new project.
  2. Resolve in your original source code any messages in the Conversion Report tab that list SourceFile in the Category column, then convert the original source files again.
    spd-note-note
    Note  

    The Code Conversion Utility generates a unique copy of the converted code each time it runs. You should always update the original source files to resolve issues before modifying the converted code.

  3. Identify messages that affect the core functionality of your code and begin resolving changes in your converted code.
    spd-note-note
    Note  

    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, a file in vi.lib, a password protected file, or an 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.
  4. 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 the converted application, the efficiency of your code decreases.

Recently Viewed Topics