LabVIEW 2014 Real-Time Module Known Issues

Overview

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.

Known Issues by Category

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

Building and Distributing LabVIEW Applications
371282 A Real Time Executable with a Packed Project Library set to "Always Included" cannot be remotely debugged
465294 Startup Application will be broken if subVI name has Japanese characters
443346 LabVIEW Libraries localized in Korean cause RT targets to crash during deployment
File I/O
387418 Set Number of Records function erases all datalog contents on VxWorks targets
Functions, VIs, and Express VIs
298990 Clear Errors VI can affect determinism on RT targets
399608 RT FIFO writes produce high level of jitter on Linux-RT targets
475970 RT Wait function does not wait for the correct amount of time on Linux RT Controller
I/O Servers
481420 NI Linux Real-Time OS OPC UA Server will not start without a DNS Server on the Network
Miscellaneous
464351 Getting unexpected text or behavior when using non-ASCII passwords or non-ASCII SSIDs
Operating System Specific
543468 LabVIEW Run-Time hang on NI Linux Real-Time after system time set into past.
Performance
365498 Timed loops on Linux-RT are slow / don't meet timing on first iteration
399608 RT FIFO writes produce high level of jitter on Linux-RT targets
Web Server/Web Services
480085 Polymorphic VI in Real-Time web service will hang deployment



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.

Reported Version: 2012    Resolved Version: N/A    Added: 02/04/2013
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.

Reported Version: 2013    Resolved Version: N/A    Added: 07/31/2014
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.

Reported Version: 2013    Resolved Version: 2013 SP1 or 2015 and later    Added: 01/05/2016
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.

Reported Version: 2012    Resolved Version: N/A    Added: 02/04/2013
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.

Reported Version: 7.0    Resolved Version: N/A    Added: 10/28/2011
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.

Reported Version: 2013    Resolved Version: N/A    Added: 07/22/2013
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

Reported Version: 2013    Resolved Version: 2015    Added: 07/31/2014
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.

Reported Version: 2013 SP1    Resolved Version: 2015    Added: 07/31/2014
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.

Reported Version: 2014    Resolved Version: N/A    Added: 07/31/2014
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.

Reported Version: 2014    Resolved Version: N/A    Added: 10/15/2015
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.

Reported Version: 2012    Resolved Version: N/A    Added: 02/04/2013
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.

Reported Version: 2013    Resolved Version: N/A    Added: 07/22/2013
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.

Reported Version: 2013 SP1    Resolved Version: N/A    Added: 07/31/2014


Known Issues by Date

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

298990 Clear Errors VI can affect determinism on RT targets
365498 Timed loops on Linux-RT are slow / don't meet timing on first iteration
371282 A Real Time Executable with a Packed Project Library set to "Always Included" cannot be remotely debugged
387418 Set Number of Records function erases all datalog contents on VxWorks targets
399608 RT FIFO writes produce high level of jitter on Linux-RT targets
464351 Getting unexpected text or behavior when using non-ASCII passwords or non-ASCII SSIDs
465294 Startup Application will be broken if subVI name has Japanese characters
443346 LabVIEW Libraries localized in Korean cause RT targets to crash during deployment
475970 RT Wait function does not wait for the correct amount of time on Linux RT Controller
480085 Polymorphic VI in Real-Time web service will hang deployment
481420 NI Linux Real-Time OS OPC UA Server will not start without a DNS Server on the Network
543468 LabVIEW Run-Time hang on NI Linux Real-Time after system time set into past



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.

Reported Version: 7.0    Resolved Version: N/A    Added: 10/28/2011
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.

Reported Version: 2012    Resolved Version: N/A    Added: 02/04/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 02/04/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 02/04/2013
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.

Reported Version: 2013    Resolved Version: N/A    Added: 07/22/2013
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.

Reported Version: 2014    Resolved Version: N/A    Added: 07/31/2014
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.

Reported Version: 2013    Resolved Version: N/A    Added: 07/31/2014
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.

Reported Version: 2013    Resolved Version: 2013 SP1 or 2015 and later    Added: 01/05/2016
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

Reported Version: 2013    Resolved Version: 2015    Added: 07/31/2014
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.

Reported Version: 2013 SP1    Resolved Version: N/A    Added: 07/31/2014
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.

Reported Version: 2013 SP1    Resolved Version: 2015    Added: 07/31/2014
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.

Reported Version: 2014    Resolved Version: N/A    Added: 10/15/2015

Document last updated on 10/15/2015

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