LabVIEW NXG 5.0 Known Issues

Aperçu

This document contains the LabVIEW NXG 5.0 known issues that were discovered before and since the release of LabVIEW NXG 5.0. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Bug Number

Legacy ID

Description

Details

575800 514789

Autotuning PID Online.VI Example Reads Proportional Gain 'NaN' with the Relay Technique.

When running the Autotuning PID Online.vi example, with the Relay Technique the "Tuned PID gains" output of proportional gain (Kc) shows "NaN" when the program believes tuning is completed by flashing "tuning completed?".

Workaround:

Tune the individual terms first. Start by first tuning for P until the response is stable. Then continue to tune by switching to PI. Lastly, repeat the process for PID.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

May 21, 2017

53381 112702

Cannot read file that shows up as zero bytes.

Linux, Unix and Macs can have files that show up on disk as zero bytes but actually have data that can be read. If you use a Read Binary File primitive on these files you will return an empty string.

Workaround:

Read a large number of bytes and handle the end of file error that you will receive.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

May 21, 2017

59104 678830

Dictionaries are only found in specific language culture

Parent cultures will not find the dictionary even if the language matches the parent culture. As a result, localization will not happen.

Workaround:

Place the dictionary into a language-specific folder, e.g. de-DE, de-CH, de-LI, etc

Reported Version:

LabVIEW NXG 2.0

Resolved Version:

N/A

Added:

Feb 25, 2018

60727 599434

Dynamic dispatch controls are not supported inside structures

Workaround:

Remove the control from the structure and the error will clear.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

Feb 25, 2018

60729 620473

Element names inside Typedef Clusters or Rings may not show localized names

When looking at names of elements contained within a Typedef Cluster or Ring, the name may appear in English rather than the appropriate localized language.

Workaround:

Close out of NXG and re-open. Open from the project.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

Feb 25, 2018

61481 599881

Empty folders in project don't show up in the files pane when opening a project

When you open a project with empty folders, those don't show up in the files pane.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

Jan 22, 2018

53111 662414

Error & Warnings Panel continuously expands and collapses after repeated pinning and unpinning

Normally, The Error & Warnings panel pops up when the mouse is hovered over it. In some cases, the Errors and Warnings window may expand and collapsed continuously after pinning and unpinning the Errors and Warnings panel.

Workaround:

Click the tab.

Reported Version:

LabVIEW NXG 2.0

Resolved Version:

N/A

Added:

Jan 22, 2018

75162

Event Loop, In Place Element Structure, and Timed Loop do not create correctly when dragging from Right to Left (instead of Left to Right)

There are some structures that do not create correctly when dragging from right to left (instead of left to right). The structure will create and expand in the Y-axis correctly but will stay to the right of the point where the mouse clicked before dragging, and remain in the smallest width possible. I expect all of them to expand in the X-axis to follow the mouse drag when moving to the left.
The structures affected are Event Loop, In Place Element Structure, and Timed Loop.

Workaround:

Create the structures left to right, instead of right to left.

Reported Version:

LabVIEW NXG 2.0

Resolved Version:

N/A

Added:

May 17, 2020

93638 661948

Expand/Collapse glyph remains after deleting all contents of a class

When you delete all contents of a class, it still displays the Expand/Collapse glyph in the project, as if there were members to be shown or hidden.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW NXG 2.0

Resolved Version:

N/A

Added:

Jan 22, 2018

989174

GVI with C Node broken after project reload and force recompile.

Forcing a recompile of a GVI which includes a C Node will appear broken when you open your project again.

Workaround:

Delete LabVIEW NXG's Compiled Code Cache (".cache" folder)

Reported Version:

LabVIEW NXG 5.0 | Vision Development Module: 2020

Resolved Version:

N/A

Added:

May 17, 2020

127716 630075

IO constants cannot be resized when contained within a cluster connected to a G Type.

IO constants can be resized manually when contained within a cluster constant. However, IO constants cannot be resized once the containing cluster is connected to a G Type. The IO control in the G Type can be resized but this change is not reflected in any connected constants.

Workaround:

Disconnect the cluster from the G Type, resize the IO constant, and then reconnect to the G Type.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

May 21, 2017

982812

LabVIEW NXG crashes when using any of the Database Connectivity APIs

Crash using the "Database Connectivity" API on some computers. We have mostly noticed customers facing this issue on Lenovo X1 laptops. However, it could happen on other computers too.

Crash log:
ErrorId: 0x6AD7DF6F
Message: Unhandled Task Exception
Error message: attempt to write a readonly database attempt to write a readonly database
Exception: SQLiteException

The issue can also be reproduced by opening any of the Database examples. These examples can be found here in the NXG welcome page: Examples > Programming Basics > Connectivity > Database

Workaround:

Set the 'Default' value to empty for this key in Windows Registry: Computer\HKEY_CLASSES_ROOT\TypeLib\{51C0003F-0741-4D1A-A612-891EB6928B5B}\1.0\0\win64

Reported Version:

LabVIEW NXG 4.0 | LabVIEW NXG 5.0

Resolved Version:

N/A

Added:

Jul 30, 2020

576648 711967

LabVIEW NXG does not function correctly when license files are moved from default location.

LabVIEW NXG will not function when the license files for NXG have been removed from the C:\ProgramData\National Instruments\License Manager\Licenses folder.
The behavior will be that the splash screen will appear, then disappear and nothing happens.

Workaround:

Move the license files back into the correct location.

Reported Version:

LabVIEW NXG 2.1.1

Resolved Version:

N/A

Added:

May 17, 2020

61527 641719

Projects with large file hierarchy error out during conversion with unclear error message

Workaround:

Make shorter file paths initially so the added hierarchy doesn't extend beyond Windows file path limits

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

Feb 25, 2018

56269 643608

Right clicking on a tunnel of queue of numeric type shows the numeric palette

For most data types, the right click menu from the queue terminals shows the palette queue. Right clicking on a tunnel of numeric type shows the numeric palette.

Workaround:

Manually drop from the queue palette instead of right-clicking.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

Jan 22, 2018

52711 482816

Selection in Array of Clusters of Arrays constant loses focus.

Selecting an array inside a cluster inside another array loses focus when hovering over another element of the top array. This makes it difficult to edit the items in the inner-most array.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

May 21, 2017

53045 631907

Some keyboard shortcuts don't work with an AZERTY keyboard

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW NXG 2.0

Resolved Version:

N/A

Added:

Jan 22, 2018

61325 605135

Some strings remain in English rather than localized language when converted to LabVIEW NXG

When setting a localized dictionary and converting from LabVIEW to LabVIEW NXG, some strings may remain in English. Specifically, strings that are labels instead of captions will appear in English

Workaround:

Set a caption for controls prior to conversion or update text after conversion

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

Feb 25, 2018

575530 584767

Some UI elements in the environment may not display correctly using custom DPI settings.

Some UI elements may display incompletely if using a custom Windows DPI setting of 125%, or similar.

Workaround:

Use default DPI settings.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

May 21, 2017

357380 733974

SSH Connection to Linux RT target with non-blank root password fails

Attempting to connect to a Linux RT target via SSH when the root password is non-blank fails.

Workaround:

Modify /etc/ssh/sshd_config by changing “PermitEmptyPasswords yes” to “PermitEmptyPasswords no” and reboot the controller.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

May 16, 2019

53058 660805

Windows "line per notch" scroll wheel settings do not apply to NXG

The scroll wheel movement amount does correlate to the scroll size defined in the Windows mouse settings. For example there's no difference in the amount of block diagram scrolled whether the set to 1 line per notch or 10 lines per notch.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabVIEW NXG 2.0

Resolved Version:

N/A

Added:

Jan 22, 2018

88126 644397

Workbooks do not restore maximized after minimizing the environment window with a maximized workbook open.

A maximized workbook window will minimize when the environment window is minimized. Restoring the environment window will also restore the workbook window but not in the maximized view.

Workaround:

Maximize the workbook window manually after restoring the environment window.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

May 17, 2020

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

Bug Number

Legacy ID

Description

Details

52886 596295

Measurement Panel created for an array of task constants does not propagate name.

When a Measurement Panel is created from an empty task constant inside of an array, a new task will be generated for it and a name will be assigned. However, this name will not be automatically updated on the original task constant inside the array.

Workaround:

Manually rename the task constant.

Reported Version:

LabVIEW NXG 1.0

Resolved Version:

N/A

Added:

May 21, 2017

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).