The LabVIEW 2017 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The following items are known issues in LabVIEW 2017 Real-Time Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 494699 Return | Message "Error while reading a file from the local disk. The file may be corrupt or not present" appears when attempting to format Real-Time controller from MAX This formatting failure can sometimes occur if the user file system on the Real-Time target is full. Workaround: Re-attempt a reformat after clearing space on the Real-Time controller's storage.
| |||||
| 514879 Return | Running a VI Using Invoke Node Fails When Embedded UI is Enabled When Embedded UI is enabled, using a LabVIEW Invoke Node to run a VI on NI Linux Real-Time results in an error about the Front Panel not being available. Using an Invoke Node to run a VI on NI Linux Real-Time works as expected if Embedded UI is disabled. Workaround: Instead of using an Invoke Node, use the Start Asynchronous Call with the connector pane of the target VI wired into the Open VI Ref.
| |||||
| 597335 Return | Changes to Constants Stored in Clusters in Real-Time VIs are not Propagated to Built Real-Time Application Changes to constants stored in clusters in Real-Time VIs are not propagated to built Real-Time application when "Separate compiled code from source file" is activated. Workaround: Reboot Real-Time target, or close all open VIs and clear compiled object cache.
| |||||
| 606689 Return | Screen resolution does not stick on TSM when using reset button to restart target. On a TSM when you change the resolution of the display, select apply, select close, and then use the reset button to restart the controller, the resolution does not stick. When the TSM restarts, the resolution reverts back to what it was before you changed it. Workaround: Instead of using reset button use the power button and power it off and then back on.
| |||||
| 606691 Return | Calibration procedure of Touch Screen Monitor in NI Linux Real-Time Does Not Adapt to Screen Resolution Running the calibration procedure in something other than the maximum resolution of the touch monitor will cause some of the calibration points to be outside of the visible screen area. Thus the calibration procedure can not be completed and will be aborted. Workaround: Calibrate with maximum screen resolution or, In an open terminal, type "xinput_calibrator --geometry WxH", where W is the screen width in pixels and H is the screen height in pixels.
| |||||
| 632907 Return | LabVIEW User Watchdog "Reset LabVIEW Runtime" Only Reboots Real-Time Application Twice on NI Linux Real-Time When using the "Reset LabVIEW Runtime" user watchdog feature on a NI Linux Real-Time controller, the Real-Time Application is only restarted twice, after which point the only way to restart the application is to reboot the target. Workaround: Contact NI Support.
| |||||
| 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.
|
The following items are known issues in LabVIEW 2017 Real-Time Module sorted by Category.
| 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
| |||||
| Functions, VIs, and Express VIs | ||||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 514879 Return | Running a VI Using Invoke Node Fails When Embedded UI is Enabled When Embedded UI is enabled, using a LabVIEW Invoke Node to run a VI on NI Linux Real-Time results in an error about the Front Panel not being available. Using an Invoke Node to run a VI on NI Linux Real-Time works as expected if Embedded UI is disabled. Workaround: Instead of using an Invoke Node, use the Start Asynchronous Call with the connector pane of the target VI wired into the Open VI Ref.
| |||||
| 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.
| |||||
| 597335 Return | Changes to Constants Stored in Clusters in Real-Time VIs are not Propagated to Built Real-Time Application Changes to constants stored in clusters in Real-Time VIs are not propagated to built Real-Time application when "Separate compiled code from source file" is activated. Workaround: Reboot Real-Time target, or close all open VIs and clear compiled object cache.
| |||||
| Miscellaneous | ||||||
| 606689 Return | Screen resolution does not stick on TSM when using reset button to restart target. On a TSM when you change the resolution of the display, select apply, select close, and then use the reset button to restart the controller, the resolution does not stick. When the TSM restarts, the resolution reverts back to what it was before you changed it. Workaround: Instead of using reset button use the power button and power it off and then back on.
| |||||
| 606691 Return | Calibration procedure of Touch Screen Monitor in NI Linux Real-Time Does Not Adapt to Screen Resolution Running the calibration procedure in something other than the maximum resolution of the touch monitor will cause some of the calibration points to be outside of the visible screen area. Thus the calibration procedure can not be completed and will be aborted. Workaround: Calibrate with maximum screen resolution or, In an open terminal, type "xinput_calibrator --geometry WxH", where W is the screen width in pixels and H is the screen height in pixels.
| |||||
| 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
| |||||
| 632907 Return | LabVIEW User Watchdog "Reset LabVIEW Runtime" Only Reboots Real-Time Application Twice on NI Linux Real-Time When using the "Reset LabVIEW Runtime" user watchdog feature on a NI Linux Real-Time controller, the Real-Time Application is only restarted twice, after which point the only way to restart the application is to reboot the target. Workaround: Contact NI Support.
| |||||
| 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.
| |||||
| 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
| |||||
| 494699 Return | Message "Error while reading a file from the local disk. The file may be corrupt or not present" appears when attempting to format Real-Time controller from MAX This formatting failure can sometimes occur if the user file system on the Real-Time target is full. Workaround: Re-attempt a reformat after clearing space on the Real-Time controller's storage.
| |||||
Document last updated on 5/19/2017