LabVIEW 2016 Real-Time Module Known Issues

Aperçu

This document contains known issues for the LabVIEW 2016 Real-Time Module. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

The LabVIEW 2016 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

Known Issues by Date

The following items are known issues in LabVIEW 2016 Real-Time Module sorted by Date.

505831 Reformat and "Set Image" fail on Linux-RT immediately after uninstalling all software
515259 RT Print Debug String does not Print to the Web Interface Framework (WIF) Console Display on Pharlap targets.
518056 Downloading a Modified File from the Remote File Browser always Downloads the Original File even after Modifying the Contents
519187 Targets with PharLap Operating System Throws Error on Boot: Reliance v2.10 Build 1053: Assertion failure in module rlimode.c line 1138 (DCL = 351).
523232 Error -2233 Thrown when Deploying Start-up Executable Containing Get CPU Loads VI and Embedded UI Enabled
526153 Error 1 thrown from Front Panel Property Node when Remote Front Panel's SubVI is Called as Popup Dialog on NI Linux Real-Time Target
489045 LabVIEW crashes when manually assigning a value to the Processor assignment that is larger than the number of available cores for a Timed Sequence.
540869 Behavior of App.Kind Property Node in Linux x64 RT targets Embedded UI Returns Invalid Property
541200 Cursor Reference returned by the Cursor Move event not valid on LinuxRT x64 target with the Embedded UI enabled.
543061 Error 56 Thrown When Using "Disconnect from Slave" Invoke Method
553905 Mass Compile Fails when using VIs from the RT Utilities Palette
567919 Creating an User Named 'lvuser' on NI Linux Real-Time Overrides Native 'lvuser' Account
580414 RT LEDs VI Returns Incorrect Error Code on Invalid Input
593319 Writing TDMS files to an RT controller using the DAQmx Read VI can result in a memory corruption
667456 NI Linux Real-Time Impacted by CVE-2017-1000251 (blueborne)



ID Known Issue
505831

Return
Reformat and "Set Image" fail on Linux-RT immediately after uninstalling all software
If you attempt to reformat or set an image on a Linux-RT target immediately after uninstalling software with the "Uninstall All" option, the reformat or set image may fail.

Workaround: Before attempting to reformat or set an image, reboot the target.

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 11/18/2014
515259

Return
RT Print Debug String does not Print to the Web Interface Framework (WIF) Console Display on Pharlap targets.
With the RT Print Debug String.vi you can choose to write to monitor or to serial. In both cases this doesn't show up on the console page of the PharLap targets.

Workaround: Use a new line (\n) at the end of the Debug String.

Reported Version: 2014    Resolved Version: N/A    Added: 07/24/2015
518056

Return
Downloading a Modified File from the Remote File Browser always Downloads the Original File even after Modifying the Contents
Using Remote File Browser, the same file downloads no matter how many times the file contents are modified or overwritten.

Workaround: Clear browser history when a change is made, or call FTP Open/Close on the file that was changed.

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 07/24/2015
519187

Return
Targets with PharLap Operating System Throws Error on Boot: Reliance v2.10 Build 1053: Assertion failure in module rlimode.c line 1138 (DCL = 351).
An assertion failure on boot with the PharLap operating system can occur. The following error occurs on the console out: Reliance v2.10 Build 1053: Assertion failure in module rlimode.c line 1138 (DCL = 351). The green alpha-numeric code at the top right hand corner reads: SF01480. Once this error occurs, you cannot detect the device in MAX and are unable to reformat the driver. Rebooting or booting into safe mode does not have an effect.

Workaround: Contact NI Support

Reported Version: 2012    Resolved Version: N/A    Added: 07/24/2015
523232

Return
Error -2233 Thrown when Deploying Start-up Executable Containing Get CPU Loads VI and Embedded UI Enabled
With the Embedded UI enabled, deploying a start-up executable with the RT Get CPU Loads VI, the function returns with Error -2233: LabVIEW: Unable to retrieve CPU load information. Verify that CPU load monitoring is enabled on the target. Disabling the Embedded UI does not yield the same behavior.

Workaround: Disable Embedded UI.

Reported Version: 2014    Resolved Version: N/A    Added: 07/24/2015
526153

Return
Error 1 thrown from Front Panel Property Node when Remote Front Panel's SubVI is Called as Popup Dialog on NI Linux Real-Time Target
When using Remote Front Panel on NI Linux Real-Time targets, calling a SubVI as popup dialog has the front panel control property node(s) throw Error 1 until the HTML page is reloaded in the browser.

Workaround: N/A

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 07/24/2015
489045

Return
LabVIEW crashes when manually assigning a value to the Processor assignment that is larger than the number of available cores for a Timed Sequence.
LabVIEW crashes when manually assigning a value to the Processor assignment that is larger than the number of available cores for a Timed Sequence.

Workaround: Make sure to manually assign a value that is equal to or lower than the number of available cores. To do this, you can: a) Use CPU Information Function to find the number of available cores; b) Check if the assigned processor exists; c) Specify the processor you want to handle execution by wiring the verified number to the Processor Input instead of setting manually the desired core.

Reported Version: 2013    Resolved Version: N/A    Added: 03/08/2016
540869

Return
Behavior of App.Kind Property Node in Linux x64 RT targets Embedded UI Returns Invalid Property
Querying the App.Kind property returns Run-time System regardless of whether it is in development or executable state

Workaround: N/A

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 03/08/2016
541200

Return
Cursor Reference returned by the Cursor Move event not valid on LinuxRT x64 target with the Embedded UI enabled.
When obtaining the cursor reference returned by the cursor move event, the output is not valid on NI Linux Real-Time x64 targets with the Embedded UI enabled

Workaround: Obtain the reference from a graph control property node

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 03/08/2016
543061

Return
Error 56 Thrown When Using "Disconnect from Slave" Invoke Method
Using the "Disconnect from Slave" invoke method will almost immediately generate error 56; however the method functions correctly and disconnects the NI Real-Time system from the host machine.

Workaround: Ignore error

Reported Version: 2015    Resolved Version: N/A    Added: 03/08/2016
553905

Return
Mass Compile Fails when using VIs from the RT Utilities Palette
If a VI running on an RT target uses a subVI from the RT Utilities palette, the VI cannot be mass compiled without errors as long as the project or VI are open during the compile.

Workaround: Close the project and VI and run the mass compile again. It should run successfully.

Reported Version: 2015    Resolved Version: N/A    Added: 03/08/2016
567919

Return
Creating an User Named 'lvuser' on NI Linux Real-Time Overrides Native 'lvuser' Account
When using the Web-based Configuration & Monitoring tool to create or edit user accounts on a Linux RT target, the WIF allows creation of an account named "lvuser" or any of the other native Linux RT user accounts. Creating an account of the same name overrides the privileges of the native account. The default privileges for a new account are the same as the "Everyone" group, but not the "Admin" group. Unless admin permissions are added to this new account, issues can crop up using this account.

Workaround: Avoid adding an 'lvuser' account or make sure this new account has admin privileges.

Reported Version: 2015    Resolved Version: N/A    Added: 03/08/2016
580414

Return
RT LEDs VI Returns Incorrect Error Code on Invalid Input
When selecting invalid parameter for a cRIO controller for the RT LED VI the error code and origin is incorrect. It should be error code one and the source should point to the RT LED.vi

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 03/29/2016
593319

Return

Writing TDMS files to an RT controller using the DAQmx Read VI can result in a memory corruption

Writing data to disk on a real-time controller using the DAQmx Read VI can result in a memory corruption if the TDMS file name has an odd number of characters. The file on disc is unaffected, but the data in the application can be corrupted.


Workaround: Use an even number of characters in the name of the TDMS file. This issue was addressed in the Phar Lap ETS Real-Time Operating System 2016 Q4 Patch.

Reported Version: 2015 SP1    Resolved Version: N/A    Added: 08/01/2016
667456

Return

NI Linux Real-Time Impacted by CVE-2017-1000251 (blueborne)

Use of some Bluetooth USB adapters with stock kernel support in 2016 or 2017 NI Linux Real-Time can result in exposure to a stack overflow vulnerability in the processing of L2CAP configuration responses resulting in Remote code execution in kernel space.


Workaround: Do not use Bluetooth USB adapters on NI Linux Real-Time 2016 or 2017 systems.

Reported Version: 2016    Resolved Version: N/A    Added: 09/20/2017


Known Issues by Category

The following items are known issues in LabVIEW 2016 Real-Time Module sorted by Category.

Documentation
580414 RT LEDs VI Returns Incorrect Error Code on Invalid Input
Functions, VIs, and Express VIs
515259 RT Print Debug String does not Print to the Web Interface Framework (WIF) Console Display on Pharlap targets.
523232 Error -2233 Thrown when Deploying Start-up Executable Containing Get CPU Loads VI and Embedded UI Enabled
526153 Error 1 thrown from Front Panel Property Node when Remote Front Panel's SubVI is Called as Popup Dialog on NI Linux Real-Time Target
489045 LabVIEW crashes when manually assigning a value to the Processor assignment that is larger than the number of available cores for a Timed Sequence.
540869 Behavior of App.Kind Property Node in Linux x64 RT targets Embedded UI Returns Invalid Property
541200 Cursor Reference returned by the Cursor Move event not valid on LinuxRT x64 target with the Embedded UI enabled.
567919 Creating an User Named 'lvuser' on NI Linux Real-Time Overrides Native 'lvuser' Account
593319 Writing TDMS files to an RT controller using the DAQmx Read VI can result in a memory corruption
LabVIEW Project
553905 Mass Compile Fails when using VIs from the RT Utilities Palette
Miscellaneous
505831 Reformat and "Set Image" fail on Linux-RT immediately after uninstalling all software
518056 Downloading a Modified File from the Remote File Browser always Downloads the Original File even after Modifying the Contents
Operating System Specific
519187 Targets with PharLap Operating System Throws Error on Boot: Reliance v2.10 Build 1053: Assertion failure in module rlimode.c line 1138 (DCL = 351).
667456 NI Linux Real-Time Impacted by CVE-2017-1000251 (blueborne)
Remote Target
543061 Error 56 Thrown When Using "Disconnect from Slave" Invoke Method



ID Known Issue
Documentation
580414

Return
RT LEDs VI Returns Incorrect Error Code on Invalid Input
When selecting invalid parameter for a cRIO controller for the RT LED VI the error code and origin is incorrect. It should be error code one and the source should point to the RT LED.vi

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 03/29/2016
Functions, VIs, and Express VIs
515259

Return
RT Print Debug String does not Print to the Web Interface Framework (WIF) Console Display on Pharlap targets.
With the RT Print Debug String.vi you can choose to write to monitor or to serial. In both cases this doesn't show up on the console page of the PharLap targets.

Workaround: Use a new line (\n) at the end of the Debug String.

Reported Version: 2014    Resolved Version: N/A    Added: 07/24/2015
523232

Return
Error -2233 Thrown when Deploying Start-up Executable Containing Get CPU Loads VI and Embedded UI Enabled
With the Embedded UI enabled, deploying a start-up executable with the RT Get CPU Loads VI, the function returns with Error -2233: LabVIEW: Unable to retrieve CPU load information. Verify that CPU load monitoring is enabled on the target. Disabling the Embedded UI does not yield the same behavior.

Workaround: Disable Embedded UI.

Reported Version: 2014    Resolved Version: N/A    Added: 07/24/2015
526153

Return
Error 1 thrown from Front Panel Property Node when Remote Front Panel's SubVI is Called as Popup Dialog on NI Linux Real-Time Target
When using Remote Front Panel on NI Linux Real-Time targets, calling a SubVI as popup dialog has the front panel control property node(s) throw Error 1 until the HTML page is reloaded in the browser.

Workaround: N/A

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 07/24/2015
489045

Return
LabVIEW crashes when manually assigning a value to the Processor assignment that is larger than the number of available cores for a Timed Sequence.
LabVIEW crashes when manually assigning a value to the Processor assignment that is larger than the number of available cores for a Timed Sequence.

Workaround: Make sure to manually assign a value that is equal to or lower than the number of available cores. To do this, you can: a) Use CPU Information Function to find the number of available cores; b) Check if the assigned processor exists; c) Specify the processor you want to handle execution by wiring the verified number to the Processor Input instead of setting manually the desired core.

Reported Version: 2013    Resolved Version: N/A    Added: 03/08/2016
540869

Return
Behavior of App.Kind Property Node in Linux x64 RT targets Embedded UI Returns Invalid Property
Querying the App.Kind property returns Run-time System regardless of whether it is in development or executable state

Workaround: N/A

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 03/08/2016
541200

Return
Cursor Reference returned by the Cursor Move event not valid on LinuxRT x64 target with the Embedded UI enabled.
When obtaining the cursor reference returned by the cursor move event, the output is not valid on NI Linux Real-Time x64 targets with the Embedded UI enabled

Workaround: Obtain the reference from a graph control property node

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 03/08/2016
567919

Return
Creating an User Named 'lvuser' on NI Linux Real-Time Overrides Native 'lvuser' Account
When using the Web-based Configuration & Monitoring tool to create or edit user accounts on a Linux RT target, the WIF allows creation of an account named "lvuser" or any of the other native Linux RT user accounts. Creating an account of the same name overrides the privileges of the native account. The default privileges for a new account are the same as the "Everyone" group, but not the "Admin" group. Unless admin permissions are added to this new account, issues can crop up using this account.

Workaround: Avoid adding an 'lvuser' account or make sure this new account has admin privileges.

Reported Version: 2015    Resolved Version: N/A    Added: 03/08/2016
593319

Return

Writing TDMS files to an RT controller using the DAQmx Read VI can result in a memory corruption

Writing data to disk on a real-time controller using the DAQmx Read VI can result in a memory corruption if the TDMS file name has an odd number of characters. The file on disc is unaffected, but the data in the application can be corrupted.


Workaround: Use an even number of characters in the name of the TDMS file. This issue was addressed in the Phar Lap ETS Real-Time Operating System 2016 Q4 Patch.

Reported Version: 2015 SP1    Resolved Version: N/A    Added: 08/01/2016
LabVIEW Project
553905

Return
Mass Compile Fails when using VIs from the RT Utilities Palette
If a VI running on an RT target uses a subVI from the RT Utilities palette, the VI cannot be mass compiled without errors as long as the project or VI are open during the compile.

Workaround: Close the project and VI and run the mass compile again. It should run successfully.

Reported Version: 2015    Resolved Version: N/A    Added: 03/08/2016
Miscellaneous
505831

Return
Reformat and "Set Image" fail on Linux-RT immediately after uninstalling all software
If you attempt to reformat or set an image on a Linux-RT target immediately after uninstalling software with the "Uninstall All" option, the reformat or set image may fail.

Workaround: Before attempting to reformat or set an image, reboot the target.

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 11/18/2014
518056

Return
Downloading a Modified File from the Remote File Browser always Downloads the Original File even after Modifying the Contents
Using Remote File Browser, the same file downloads no matter how many times the file contents are modified or overwritten.

Workaround: Clear browser history when a change is made, or call FTP Open/Close on the file that was changed.

Reported Version: 2014 SP1    Resolved Version: N/A    Added: 07/24/2015
Operating System Specific
519187

Return
Targets with PharLap Operating System Throws Error on Boot: Reliance v2.10 Build 1053: Assertion failure in module rlimode.c line 1138 (DCL = 351).
An assertion failure on boot with the PharLap operating system can occur. The following error occurs on the console out: Reliance v2.10 Build 1053: Assertion failure in module rlimode.c line 1138 (DCL = 351). The green alpha-numeric code at the top right hand corner reads: SF01480. Once this error occurs, you cannot detect the device in MAX and are unable to reformat the driver. Rebooting or booting into safe mode does not have an effect.

Workaround: Contact NI Support

Reported Version: 2012    Resolved Version: N/A    Added: 07/24/2015
667456

Return
NI Linux Real-Time Impacted by CVE-2017-1000251 (blueborne)
Use of some Bluetooth USB adapters with stock kernel support in 2016 or 2017 NI Linux Real-Time can result in exposure to a stack overflow vulnerability in the processing of L2CAP configuration responses resulting in Remote code execution in kernel space.

Workaround: Do not use Bluetooth USB adapters on NI Linux Real-Time 2016 or 2017 systems.

Reported Version: 2016    Resolved Version: N/A    Added: 09/20/2017
Remote Target
543061

Return
Error 56 Thrown When Using "Disconnect from Slave" Invoke Method
Using the "Disconnect from Slave" invoke method will almost immediately generate error 56; however the method functions correctly and disconnects the NI Real-Time system from the host machine.

Workaround: Ignore error

Reported Version: 2015    Resolved Version: N/A    Added: 03/08/2016

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).