This document contains the LabVIEW Real-Time Module 2015 and 2015 SP1 known issues that were discovered before and since the release of LabVIEW 2015 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 2015 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The following items are known issues in LabVIEW Real-Time 2015 and 2015 SP1 sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 365498 Return | Timed loops on Linux-RT are slow / don't meet timing on first iteration On Linux-RT the thread in which a timed structure resides must be moved to a particular control group of threads and moving threads between cgroups is inherently non-deterministic. This thread move executes during the first iteration of the timed loop because it's not possible to move a thread that doesn't yet exist (i.e. before the timed loop executes). Workaround: Run timed structures with warmup iterations and monitor execution time. When execution time meets the desired specification, then run desired code.
| |||||
| 480085 Return | Polymorphic VI in Real-Time web service will hang deployment If there is a polymorphic VI in a web service on a real-time target, the deployment will hang and say that it's trying to reconnect. The system gives no indication as to why this is occurring and will not error out. Workaround: Do not use polymorphic VIs in a Real-Time web service.
| |||||
| 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.
| |||||
| 535980 Return | Value Change Event >> Old Value Property does not Return a Valid Value When Using an Event Structure on x64 Real-Time Targets When running a VI that has an indicator for an Old Value event, the indicator reads an invalid value. Workaround: N/A
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 522374 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. After a system restart the cRIO will no longer boot into the user interface and an error will be continuously displayed on the screen. Workaround: New workaround: 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. Calibrate with maximum screen resolution
| |||||
| 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.
| |||||
| 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
| |||||
| 543468 Return | LabVIEW Run-Time hang on NI Linux Real-Time after system time set into past Setting the current time in the past by n seconds on certain NI Real-Time controllers causes LabVIEW code to hang for n seconds. Workaround: Restart the target immediately after the new time is set. Refer to KnowldgeBase 72DETC1O: LabVIEW Run-Time Hang On NI Linux Real-Time After Set System Time Into Past for more information.
| |||||
| 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: Use CPU Information Function to find the number of available cores. Check if the assigned processor exists. Specify the processor you want to handle execution by wiring the verified number to the Processor Input instead of setting manually the desired core.
| |||||
| 531415 Return | The RT LED.vi behavior is incorrect for the cRIO-9063, cRIO-9064, cRIO-9065, cRIO-9066, cRIO-9067, and sbRIO-9651. The documented behavior of the RT LED for these chassis are not consistent with published documentation. The RT LEDs.vi used to interface with the user RT LED on the controller front panel and will report the status of the LED. If the secondary led (2) is set the VI will report a value of TRUE. The chassis above do not contain a secondary user LED. In addition, the blink (3) value does not enable the blinking behavior of the LED. Workaround: N/A
| |||||
| 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.
| |||||
| 571133 Return | LAN Port 1 on PXIe-8135 Becomes Inactive on Boot-up with No Ethernet Cable Plugged In If LAN Port 1 is not used on the PXIe-8135, on boot-up the port will become inactive and be unable to communicate with BIOS 1.2.0f0 Workaround: N/A
|
The following items are known issues in LabVIEW Real-Time 2015 and 2015 SP1 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Controls and Indicators | ||||||
| 535980 Return | Value Change Event >> Old Value Property does not Return a Valid Value When Using an Event Structure on x64 Real-Time Targets When running a VI that has an indicator for an Old Value event, the indicator reads an invalid value. Workaround: N/A
| |||||
| Documentation | ||||||
| 531415 Return | The RT LED.vi behavior is incorrect for the cRIO-9063, cRIO-9064, cRIO-9065, cRIO-9066, cRIO-9067, and sbRIO-9651. The documented behavior of the RT LED for these chassis are not consistent with published documentation. The RT LEDs.vi used to interface with the user RT LED on the controller front panel and will report the status of the LED. If the secondary led (2) is set the VI will report a value of TRUE. The chassis above do not contain a secondary user LED. In addition, the blink (3) value does not enable the blinking behavior of the LED. Workaround: N/A
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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: Use CPU Information Function to find the number of available cores. Check if the assigned processor exists. Specify the processor you want to handle execution by wiring the verified number to the Processor Input instead of setting manually the desired core.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 522374 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. After a system restart the cRIO will no longer boot into the user interface and an error will be continuously displayed on the screen. Workaround: New workaround: 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. Calibrate with maximum screen resolution
| |||||
| 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
| |||||
| 543468 Return | LabVIEW Run-Time hang on NI Linux Real-Time after system time set into past Setting the current time in the past by n seconds on certain NI Real-Time controllers causes LabVIEW code to hang for n seconds. Workaround: Restart the target immediately after the new time is set. Refer to KnowldgeBase 72DETC1O: LabVIEW Run-Time Hang On NI Linux Real-Time After Set System Time Into Past for more information.
| |||||
| Performance | ||||||
| 365498 Return | Timed loops on Linux-RT are slow / don't meet timing on first iteration On Linux-RT the thread in which a timed structure resides must be moved to a particular control group of threads and moving threads between cgroups is inherently non-deterministic. This thread move executes during the first iteration of the timed loop because it's not possible to move a thread that doesn't yet exist (i.e. before the timed loop executes). Workaround: Run timed structures with warmup iterations and monitor execution time. When execution time meets the desired specification, then run desired code.
| |||||
| 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
| |||||
| 571133 Return | LAN Port 1 on PXIe-8135 Becomes Inactive on Boot-up with No Ethernet Cable Plugged In If LAN Port 1 is not used on the PXIe-8135, on boot-up the port will become inactive and be unable to communicate with BIOS 1.2.0f0 Workaround: N/A
| |||||
| Web Server/Web Services | ||||||
| 480085 Return | Polymorphic VI in Real-Time web service will hang deployment If there is a polymorphic VI in a web service on a real-time target, the deployment will hang and say that it's trying to reconnect. The system gives no indication as to why this is occurring and will not error out. Workaround: Do not use polymorphic VIs in a Real-Time web service.
| |||||
Document last updated on 3/22/2016