Archived: LabVIEW 2011 and 2011 SP1 Real-Time Module Known Issues

Publish Date: Aug 08, 2018 | 0 Ratings | 0.00 out of 5 | Print

Overview

This document has been archived and is no longer updated by National Instruments.

This document contains the LabVIEW 2011 and 2011 SP1 Real-Time Module known issues that were discovered before and since the release of the LabVIEW 2011 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 2011 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

Each Issue appears as a row in the table and includes these fields:
  • Issue ID - the number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
  • Legacy ID (optional) - If an issue has a legacy ID from NI's legacy/deprecated bug reporting database, you will see it appear on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).
  • Issue Title: in italics - it describes the issue in one sentence or less
  • Problem Description - a few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
  • Workaround - possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
  • Reported Version - the earliest version of LabVIEW the issue was reported in. If you discover the issue appears in an earlier version of LabVIEW than is reported in this field, you can report that to NI (contact information below) to have the field updated.
  • Resolved Version - version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
  • Date Added - the date the issue was added to the document (not the reported date)

Table of Contents

 

Documents Organization

The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by issue category.  

Known Issues by Category

The known issues in this document are organized by the category of issue. Please refer to Developer Zone Article "LabVIEW Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.

Known Issues by Date

For those who wish to locate the newly reported issues, we have also published another version of the known issues table sorted only by date the issue was added to the document.

Known Issues by Category

The following items are known issues in LabVIEW Real-Time 2011 SP1 sorted by Category.

Compatibility
309133 USB hub with more than 8 ports does not work with LabVIEW Real-Time 2011
306355 Real-Time Target Errors Dialog Fails to Launch from MAX 5.0
Controls and Indicators
323607 On an RT OS, Numeric Control With "Visible" Property Node Stops Updating
DataSocket
196504 FieldPoint Data Channels Swapped when Reading Data using Datasockets in a For Loop
Functions, VIs, and Express VIs
168343 RT Apply Target Network Settings VI Does Not Affect Secondary Network Cards
177926 Scan from string.vi and Format Date/Time String.vi give incorrect results if run on a cFP-22x0
298990 Clear Errors VI is Not Reentrant
305567 File/Directory Info function reports two extra files when called on for an external hard drive
336011 Unable to deploy a Real-Time VI including a FXP to EXT conversion on VxWorks
Hypervisor
176762 Time Triggered Variables do not work on NI Real-Time Hypervisor Systems
LabVIEW Object Oriented Programming
305921 Redeploying Dynamic Dispatch Vis in Child Classes Cause Failure to Redeploy
Miscellaneous
168343 RT Apply Target Network Settings VI Does Not Affect Secondary Network Cards
216548 Scan Engine Flags do not Display in Execution Trace Toolkit Traces from Phar Lap Targets
115784 Timed-Structure CPU Usage not Reported as Time-Critical Priority by RTSM and CPU Measurement VIs on VxWorks
312813 Real-Time Target Becomes Inaccessible in MAX When Multiple NICs are Enabled
Operating System Specific
275880 UDP Broadcast behaves differently on Phar Lap and VxWorks Real-Time Targets
Performance
303821 Enabling the console-out switch on cRIO-908x causes jitter when writing to the console
Shared Variables
292012 Real-Time Applications containing typedef Shared Variables fail to run.



ID Known Issue
Compatibility
309133

Return
USB hub with more than 8 ports does not work with LabVIEW Real-Time 2011
USB hubs that have more than 8 ports or that report more than 8 ports are not supported with LabVIEW Real-Time 2011.

Workaround: Use a USB hub with 8 or fewer ports.

Reported Version: 2011    Resolved Version: 2011 SP1    Added: 08/02/2011
306355

Return
Real-Time Target Errors Dialog Fails to Launch from MAX 5.0
With Measurement & Automation Explorer (MAX) 5.0, if "View Error Log" is selected on a remote target, it will fail to launch if the LabVIEW 2010 Run-Time Engine is not installed.

Workaround: Install the LabVIEW 2010 Run-time Engine

Reported Version: 2011    Resolved Version: 2011 SP1    Added: 10/28/2011
Controls and Indicators
323607

Return
On an RT OS, Numeric Control With "Visible" Property Node Stops Updating
If a VI contains a Numeric Indicator and this Indicator has a property node of the type Boolean Visible; once the Indicator is made invisible (i.e. Property node = F), then is made visible once again the value on the indicator no longer updates. Note: the system is still passing through the correct value, it is simply not being updated onto the front panel.

Workaround: Put the numeric indicator on a Tab Control, then make the property of the tab control invisible/visible rather than the numeric indicator itself.

Reported Version: 2011    Resolved Version: N/A    Added: 04/11/2012
DataSocket
196504

Return
FieldPoint Data Channels Swapped when Reading Data using Datasockets in a For Loop
When calling a single Datasocket Read function multiple times in a For Loop the FieldPoint channel data could randomly swap between the channel.

Workaround: 1. Use a sequential read with multiple Datasocket functions. 2. Explicitly open the Datasocket connections and then use a Datasocket Read in the for loop. 3. Use a different API to access the IO point (SV, FieldPoint, etc)

Reported Version: 2009    Resolved Version: N/A    Added: 03/05/2012
Functions, VIs, and Express VIs
168343

Return
RT Apply Target Network Settings VI Does Not Affect Secondary Network Cards
You cannot use the RT Apply Target Network Settings VI to apply network settings for a secondary network card.

Workaround: Use NI Measurement & Automation Explorer to configure secondary network cards or use the System Configuration API.

Reported Version: 2009    Resolved Version: N/A    Added: 06/30/2009
177926

Return
Scan from string.vi and Format Date/Time String.vi give incorrect results if run on a cFP-22x0
Scan from string.vi (to scan for timestamp) and Format Date/Time String.vi give incorrect results if run on a cFP-22x0. The results obtained with a cFP-2200 or cFP-2220 are incorrect and differ from the ones obtained with cFP-2100 or cFP-2120.

Workaround: Use manual string manipulation instead of the built-in function.

Reported Version: 8.5    Resolved Version: 2012    Added: 08/02/2011
298990

Return
Clear Errors VI is Not Reentrant
If the Clear Errors VI is used in parallel loops on LabVIEW Real-Time, you introduce a shared resource. This will affect the code's determinisms

Workaround: Create custom "Clear Error" VI.

Reported Version: 7.0    Resolved Version: N/A    Added: 10/28/2011
305567

Return
File/Directory Info function reports two extra files when called on for an external hard drive
Calling the File/Directory Info function and pointing it at a folder on an external hard drive connected to a CompactRIO returns two more files than exist in that folder. For example, if the function points to a empty folder on the CompactRIO hard drive, it will return zero; if it's pointed to an empty folder on an external drive, it will return 2.

Workaround: Subtract 2 from the file count returned from the File/Directory Info function when reporting on a folder on an external hard drive.

Reported Version: 2010    Resolved Version: N/A    Added: 10/28/2011
336011

Return
Unable to deploy a Real-Time VI including a FXP to EXT conversion on VxWorks
When performing a conversion between a FXP (fixed point) and EXT (extended float point) data types in a Real-Time VI, the VI cannot be deployed to the Real-Time target.

Workaround: Use an intermediate conversion to type DBL.

Reported Version: 2011    Resolved Version: 2012    Added: 03/05/2012
Hypervisor
176762

Return
Time Triggered Variables do not work on NI Real-Time Hypervisor Systems
You cannot use Time-Triggered Shared Variables on an NI Real-Time Hypervisor system.

Workaround: If you need deterministic Ethernet in an NI Real-Time Hypervisor system, you can use the virtual Ethernet device to communicate between Windows and the RT target or you can use NI EtherCAT to communicate with add-on I/O.

Reported Version: 2009    Resolved Version: N/A    Added: 06/30/2009
LabVIEW Object Oriented Programming
305921

Return
Redeploying Dynamic Dispatch Vis in Child Classes Cause Failure to Redeploy
Editing and redeploying dynamic dispatch Vis in child classes can cause the VI to fail during deployment.

Workaround: Close and redeploy the top level VI.

Reported Version: 2011    Resolved Version: 2012    Added: 11/11/2011
Miscellaneous
168343

Return
RT Apply Target Network Settings VI Does Not Affect Secondary Network Cards
You cannot use the RT Apply Target Network Settings VI to apply network settings for a secondary network card.

Workaround: Use NI Measurement & Automation Explorer to configure secondary network cards or use the System Configuration API.

Reported Version: 2009    Resolved Version: N/A    Added: 06/30/2009
216548

Return
Scan Engine Flags do not Display in Execution Trace Toolkit Traces from Phar Lap Targets
NI Scan Engine flags Scan Period, Mode Chance, Fault Added, and Fault Cleared do not display in Execution Trace Toolkit traces. This only occurs on Phar Lap ETS targets.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2012    Added: 08/03/2010
115784

Return
Timed-Structure CPU Usage not Reported as Time-Critical Priority by RTSM and CPU Measurement VIs on VxWorks
On VxWorks targets, the Real-Time System Manager (RTSM) and CPU Measurement VIs incorrectly report CPU usage by Timed Structures as normal priority. The NI Real-Time Execution Trace Toolkit correctly reports the priority as Timed-Structure priority.

Workaround: Use the NI Real-Time Execution Trace Toolkit to monitor thread priorities.

Reported Version: 8.6    Resolved Version: N/A    Added: 08/02/2011
312813

Return
Real-Time Target Becomes Inaccessible in MAX When Multiple NICs are Enabled
If a Real-Time system has additional NICs installed and enabled, the Real-Time system can become inacccessible in Measurement & Automation Explorer. The disconnection occurs if some NICs are not connected to a network.

Workaround: Downgrade NI System Configuration 1.1.3 or earlier.

Reported Version: 2011    Resolved Version: 2012    Added: 03/05/2012
Operating System Specific
275880

Return
UDP Broadcast behaves differently on Phar Lap and VxWorks Real-Time Targets
UPD Broadcast may behave differently for Real-Time targets running different operating systems. VxWorks targets cannot read back a message it has broadcast, while this is possible on Phar Lap targets.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 10/28/2011
Performance
303821

Return
Enabling the console-out switch on cRIO-908x causes jitter when writing to the console
If a low priority thread is writing to the console, it can cause jitter in the order of several "ms" in the higher priority code.

Workaround: Disable console logging to improve jitter.

Reported Version: 2010    Resolved Version: 2012    Added: 08/02/2011
Shared Variables
292012

Return
Real-Time Applications containing typedef Shared Variables fail to run.
If you are building an RTEXE that contains Shared Variables whose data type is based upon a type definition and the build specification is configured to disconnect type definitions the RTEXE will not run.

Workaround: 1.) Manually disconnect the variable from the typedef before building the application 2.) Change the build spec so it doesn't disconnect type definitions

Reported Version: 2011 32-bit    Resolved Version: 2012    Added: 10/11/2011

Document last updated on 3/2/2012

Known Issues by Date

The following items are known issues in LabVIEW Real-Time 2011 SP1 sorted by Date.

168343 RT Apply Target Network Settings VI Does Not Affect Secondary Network Cards
176762 Time Triggered Variables do not work on NI Real-Time Hypervisor Systems
216548 Scan Engine Flags do not Display in Execution Trace Toolkit Traces from Phar Lap Targets
115784 Timed-Structure CPU Usage not Reported as Time-Critical Priority by RTSM and CPU Measurement VIs on VxWorks
177926 Scan from string.vi and Format Date/Time String.vi give incorrect results if run on a cFP-22x0
303821 Enabling the console-out switch on cRIO-908x causes jitter when writing to the console
309133 USB hub with more than 8 ports does not work with LabVIEW Real-Time 2011
292012 Real-Time Applications containing typedef Shared Variables fail to run.
275880 UDP Broadcast behaves differently on Phar Lap and VxWorks Real-Time Targets
298990 Clear Errors VI is Not Reentrant
305567 File/Directory Info function reports two extra files when called on for an external hard drive
306355 Real-Time Target Errors Dialog Fails to Launch from MAX 5.0
305921 Redeploying Dynamic Dispatch Vis in Child Classes Cause Failure to Redeploy
196504 FieldPoint Data Channels Swapped when Reading Data using Datasockets in a For Loop
312813 Real-Time Target Becomes Inaccessible in MAX When Multiple NICs are Enabled
336011 Unable to deploy a Real-Time VI including a FXP to EXT conversion on VxWorks
323607 On an RT OS, Numeric Control With "Visible" Property Node Stops Updating



ID Known Issue
168343

Return
RT Apply Target Network Settings VI Does Not Affect Secondary Network Cards
You cannot use the RT Apply Target Network Settings VI to apply network settings for a secondary network card.

Workaround: Use NI Measurement & Automation Explorer to configure secondary network cards or use the System Configuration API.

Reported Version: 2009    Resolved Version: N/A    Added: 06/30/2009
176762

Return
Time Triggered Variables do not work on NI Real-Time Hypervisor Systems
You cannot use Time-Triggered Shared Variables on an NI Real-Time Hypervisor system.

Workaround: If you need deterministic Ethernet in an NI Real-Time Hypervisor system, you can use the virtual Ethernet device to communicate between Windows and the RT target or you can use NI EtherCAT to communicate with add-on I/O.

Reported Version: 2009    Resolved Version: N/A    Added: 06/30/2009
216548

Return
Scan Engine Flags do not Display in Execution Trace Toolkit Traces from Phar Lap Targets
NI Scan Engine flags Scan Period, Mode Chance, Fault Added, and Fault Cleared do not display in Execution Trace Toolkit traces. This only occurs on Phar Lap ETS targets.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2012    Added: 08/03/2010
115784

Return
Timed-Structure CPU Usage not Reported as Time-Critical Priority by RTSM and CPU Measurement VIs on VxWorks
On VxWorks targets, the Real-Time System Manager (RTSM) and CPU Measurement VIs incorrectly report CPU usage by Timed Structures as normal priority. The NI Real-Time Execution Trace Toolkit correctly reports the priority as Timed-Structure priority.

Workaround: Use the NI Real-Time Execution Trace Toolkit to monitor thread priorities.

Reported Version: 8.6    Resolved Version: N/A    Added: 08/02/2011
177926

Return
Scan from string.vi and Format Date/Time String.vi give incorrect results if run on a cFP-22x0
Scan from string.vi (to scan for timestamp) and Format Date/Time String.vi give incorrect results if run on a cFP-22x0. The results obtained with a cFP-2200 or cFP-2220 are incorrect and differ from the ones obtained with cFP-2100 or cFP-2120.

Workaround: Use manual string manipulation instead of the built-in function.

Reported Version: 8.5    Resolved Version: 2012    Added: 08/02/2011
303821

Return
Enabling the console-out switch on cRIO-908x causes jitter when writing to the console
If a low priority thread is writing to the console, it can cause jitter in the order of several "ms" in the higher priority code.

Workaround: Disable console logging to improve jitter.

Reported Version: 2010    Resolved Version: 2012    Added: 08/02/2011
309133

Return
USB hub with more than 8 ports does not work with LabVIEW Real-Time 2011
USB hubs that have more than 8 ports or that report more than 8 ports are not supported with LabVIEW Real-Time 2011.

Workaround: Use a USB hub with 8 or fewer ports.

Reported Version: 2011    Resolved Version: 2011 SP1    Added: 08/02/2011
292012

Return
Real-Time Applications containing typedef Shared Variables fail to run.
If you are building an RTEXE that contains Shared Variables whose data type is based upon a type definition and the build specification is configured to disconnect type definitions the RTEXE will not run.

Workaround: 1.) Manually disconnect the variable from the typedef before building the application 2.) Change the build spec so it doesn't disconnect type definitions

Reported Version: 2011 32-bit    Resolved Version: 2012    Added: 10/11/2011
275880

Return
UDP Broadcast behaves differently on Phar Lap and VxWorks Real-Time Targets
UPD Broadcast may behave differently for Real-Time targets running different operating systems. VxWorks targets cannot read back a message it has broadcast, while this is possible on Phar Lap targets.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 10/28/2011
298990

Return
Clear Errors VI is Not Reentrant
If the Clear Errors VI is used in parallel loops on LabVIEW Real-Time, you introduce a shared resource. This will affect the code's determinisms

Workaround: Create custom "Clear Error" VI.

Reported Version: 7.0    Resolved Version: N/A    Added: 10/28/2011
305567

Return
File/Directory Info function reports two extra files when called on for an external hard drive
Calling the File/Directory Info function and pointing it at a folder on an external hard drive connected to a CompactRIO returns two more files than exist in that folder. For example, if the function points to a empty folder on the CompactRIO hard drive, it will return zero; if it's pointed to an empty folder on an external drive, it will return 2.

Workaround: Subtract 2 from the file count returned from the File/Directory Info function when reporting on a folder on an external hard drive.

Reported Version: 2010    Resolved Version: N/A    Added: 10/28/2011
306355

Return
Real-Time Target Errors Dialog Fails to Launch from MAX 5.0
With Measurement & Automation Explorer (MAX) 5.0, if "View Error Log" is selected on a remote target, it will fail to launch if the LabVIEW 2010 Run-Time Engine is not installed.

Workaround: Install the LabVIEW 2010 Run-time Engine

Reported Version: 2011    Resolved Version: 2011 SP1    Added: 10/28/2011
305921

Return
Redeploying Dynamic Dispatch Vis in Child Classes Cause Failure to Redeploy
Editing and redeploying dynamic dispatch Vis in child classes can cause the VI to fail during deployment.

Workaround: Close and redeploy the top level VI.

Reported Version: 2011    Resolved Version: 2012    Added: 11/11/2011
196504

Return
FieldPoint Data Channels Swapped when Reading Data using Datasockets in a For Loop
When calling a single Datasocket Read function multiple times in a For Loop the FieldPoint channel data could randomly swap between the channel.

Workaround: 1. Use a sequential read with multiple Datasocket functions. 2. Explicitly open the Datasocket connections and then use a Datasocket Read in the for loop. 3. Use a different API to access the IO point (SV, FieldPoint, etc)

Reported Version: 2009    Resolved Version: N/A    Added: 03/05/2012
312813

Return
Real-Time Target Becomes Inaccessible in MAX When Multiple NICs are Enabled
If a Real-Time system has additional NICs installed and enabled, the Real-Time system can become inacccessible in Measurement & Automation Explorer. The disconnection occurs if some NICs are not connected to a network.

Workaround: Downgrade NI System Configuration 1.1.3 or earlier.

Reported Version: 2011    Resolved Version: 2012    Added: 03/05/2012
336011

Return
Unable to deploy a Real-Time VI including a FXP to EXT conversion on VxWorks
When performing a conversion between a FXP (fixed point) and EXT (extended float point) data types in a Real-Time VI, the VI cannot be deployed to the Real-Time target.

Workaround: Use an intermediate conversion to type DBL.

Reported Version: 2011    Resolved Version: 2012    Added: 03/05/2012
323607

Return
On an RT OS, Numeric Control With "Visible" Property Node Stops Updating
If a VI contains a Numeric Indicator and this Indicator has a property node of the type Boolean Visible; once the Indicator is made invisible (i.e. Property node = F), then is made visible once again the value on the indicator no longer updates. Note: the system is still passing through the correct value, it is simply not being updated onto the front panel.

Workaround: Put the numeric indicator on a Tab Control, then make the property of the tab control invisible/visible rather than the numeric indicator itself.

Reported Version: 2011    Resolved Version: N/A    Added: 04/11/2012

Document last updated on 3/2/2012

Contacting NI

Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit