This document contains the LabVIEW Real-Time Module 2014 known issues that were discovered before and since the release of LabVIEW 2014 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 2014 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The following items are known issues in LabVIEW 2014 Real-Time Module sorted by Category.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
Building and Distributing LabVIEW Applications | ||||||
371282 Return | A Real Time Executable with a Packed Project Library set to "Always Included" cannot be remotely debugged A Real Time Executable with a Packed Project Library set to "Always Included" cannot be remotely debugged. When connecting to the executable the "failed to connect to remote application" error message will be displayed. Workaround: Use other standard debugging methods.
| |||||
465294 Return | Startup Application will be broken if subVI name has Japanese characters When a Japanese-named subVI is included in the startup VI of a real time application, the startup application will not be able to run because after being deployed, it cannot locate the subVI. Workaround: One solution is in the startup application properties set the build name of the Japanese sub VI to an English name. Another workaround is to edit the subVI name to an English name.
| |||||
443346 Return | LabVIEW Libraries localized in Korean cause RT targets to crash during deployment If there is a LabVIEW Library, specifically an lvlib, included in the LabVIEW Real-Time code deployed to the target the target will crash during deployment. This is a known issue for the LabVIEW Real-Time Module versions 2013 and 2014 SP1. Workaround: Use a different LabVIEW version. The problem does not exist in 2012 SP1 and previous, 2013 SP1, 2014, or 2015 and later. Or, replace Korean localized LabVIEW libraries with an english equivalent library.
| |||||
File I/O | ||||||
387418 Return | Set Number of Records function erases all datalog contents on VxWorks targets Using the Datalog - Set Number of Records function on VxWorks targets wipes all logs contained in the file. Workaround: Use binary file, TDMS or another file format to store cluster data.
| |||||
Functions, VIs, and Express VIs | ||||||
298990 Return | Clear Errors VI can affect determinism on RT targets The Clear Errors VI is not reentrant and becomes a shared resource when it's called from multiple loops in an RT application. This can introduce higher levels of jitter in time critical code segments. Workaround: Create custom "Clear Error" VI.
| |||||
399608 Return | RT FIFO writes produce high level of jitter on Linux-RT targets On Linux-RT ZYNQ based targets, writes to an RT FIFO can introduce a high level of jitter compared to VxWorks and PharLap targets when the RT FIFO read occurs on a thread running in a different processor core. Workaround: Prioritize RT FIFO read and write operations so they take place in threads running on the same processor core.
| |||||
475970 Return | RT Wait function does not wait for the correct amount of time on Linux RT Controller RT Wait function does not wait for the correct amount of time on Linux RT Controller when using microsecond resolution if wait time is larger than 4.2 million microseconds. Workaround: Use millisecond resolution wait or wait in smaller increments than 4.2 million microseconds
| |||||
I/O Servers | ||||||
481420 Return | NI Linux Real-Time OS OPC UA Server will not start without a DNS Server on the Network When using an OPC UA Server on NI Linux Real-Time OS without a DNS Server, the following error is returned: Server.vi cannot start because Start.VI can not resolve IP Address from RT target. Workaround: Force the target name to be resolved as set IP Address by adding one line to /etc/hosts file on your NI Linux Real-Time device: " [IP Address] [target name of 9068]", which forces the target name to be resolved as the set IP Address.
| |||||
Miscellaneous | ||||||
464351 Return | Getting unexpected text or behavior when using non-ASCII passwords or non-ASCII SSIDs Using the NI Web-Based Monitoring and Configuration Utility, when trying to connect to an SSID that was created using non-ASCII characters, the network name is displayed incorrectly. In addition, when trying to connect with a password that used non-ASCII characters, there is an error that suggests it is the incorrect password. Workaround: Do not use non-ASCII characters when setting SSID names or passwords via the NI Web-Based Monitoring and Configuration Utility.
| |||||
Operating System Specific | ||||||
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.
| |||||
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.
| |||||
399608 Return | RT FIFO writes produce high level of jitter on Linux-RT targets On Linux-RT ZYNQ based targets, writes to an RT FIFO can introduce a high level of jitter compared to VxWorks and PharLap targets when the RT FIFO read occurs on a thread running in a different processor core. Workaround: Prioritize RT FIFO read and write operations so they take place in threads running on the same processor core.
| |||||
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.
|
The following items are known issues in LabVIEW 2014 Real-Time Module sorted by Date.
ID | Known Issue | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
298990 Return | Clear Errors VI can affect determinism on RT targets The Clear Errors VI is not reentrant and becomes a shared resource when it's called from multiple loops in an RT application. This can introduce higher levels of jitter in time critical code segments. Workaround: Create custom "Clear Error" VI.
| ||||||||||||||||||||||||||||||||||||||||
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.
| ||||||||||||||||||||||||||||||||||||||||
371282 Return | A Real Time Executable with a Packed Project Library set to "Always Included" cannot be remotely debugged A Real Time Executable with a Packed Project Library set to "Always Included" cannot be remotely debugged. When connecting to the executable the "failed to connect to remote application" error message will be displayed. Workaround: Use other standard debugging methods.
| ||||||||||||||||||||||||||||||||||||||||
387418 Return | Set Number of Records function erases all datalog contents on VxWorks targets Using the Datalog - Set Number of Records function on VxWorks targets wipes all logs contained in the file. Workaround: Use binary file, TDMS or another file format to store cluster data.
| ||||||||||||||||||||||||||||||||||||||||
399608 Return | RT FIFO writes produce high level of jitter on Linux-RT targets On Linux-RT ZYNQ based targets, writes to an RT FIFO can introduce a high level of jitter compared to VxWorks and PharLap targets when the RT FIFO read occurs on a thread running in a different processor core. Workaround: Prioritize RT FIFO read and write operations so they take place in threads running on the same processor core.
| ||||||||||||||||||||||||||||||||||||||||
464351 Return | Getting unexpected text or behavior when using non-ASCII passwords or non-ASCII SSIDs Using the NI Web-Based Monitoring and Configuration Utility, when trying to connect to an SSID that was created using non-ASCII characters, the network name is displayed incorrectly. In addition, when trying to connect with a password that used non-ASCII characters, there is an error that suggests it is the incorrect password. Workaround: Do not use non-ASCII characters when setting SSID names or passwords via the NI Web-Based Monitoring and Configuration Utility.
| ||||||||||||||||||||||||||||||||||||||||
465294 Return | Startup Application will be broken if subVI name has Japanese characters When a Japanese-named subVI is included in the startup VI of a real time application, the startup application will not be able to run because after being deployed, it cannot locate the subVI. Workaround: One solution is in the startup application properties set the build name of the Japanese sub VI to an English name. Another workaround is to edit the subVI name to an English name.
Document last updated on 10/15/2015 |