Archived: LabVIEW 2009 Real-Time Module Known Issues and Bug Fixes

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Panoramica



This document contains the known issues for the LabVIEW 2009 Real-Time Module. In addition, you can find a list of known issues from previous versions of the LabVIEW Real-Time Module in the LabVIEW Real-Time Module 8.6.1 Readme. Not every issue known to NI will appear on this list; it is intended only to show the severe and more common issues that can be encountered. 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)

    Known Issues by Category

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

    Building and Distributing LabVIEW Applications
    179676 NI-Switch IVI class reference in a type def cluster causes LabVIEW 2009 to hang when building an RT source distribution
    File I/O
    173990 FAT partition labels show up as files in Phar Lap
    Functions, VIs, and Express VIs
    165930 Get Fault List VI Allocates Memory Upon Fault
    Hypervisor
    158002 Unable to Put the RT Target on a Hypervisor System into Safe Mode from MAX
    162917 Windows Hangs During Shutdown On Certain Hypervisor Systems When Not Booted into Hypervisor Mode
    166467 On an NI Real-Time Hypervisor System, the Virtual Ethernet Connection Does Not Support TCP Offloading
    176762 Time Triggered Variables do not work on NI Real-Time Hypervisor Systems
    164513 Network errors sending large TCP packets between Hypervisor Windows and Phar Lap OSes with a shared network card
    173879 Multiple host network interfaces on same subnet as RT targets prevents MAX from discovering RT target
    147064 Converting Windows from ACPI mode to Standard PC mode can leave USB peripherals unresponsive
    151832 Serial port devices may need to update drivers
    LabVIEW Object Oriented Programming
    176901 Deploying a VI that uses only child classes may crash Real-Time target
    LabVIEW Project
    163516 Reconfiguring the Web Server Requires a Target Reboot
    Miscellaneous
    168343 RT Apply Target Network Settings VI Does Not Affect Secondary Network Cards
    170701 The PID Toolkit and the Real-Time Execution Trace Toolkit Are Not Localized
    Operating System Specific
    178443 Sending TCP or UDP packets at maximum throughput may hang single-core executing Phar Lap targets
    146085 Converting timestamp to numeric (of any representation) and back returns different timestamp on VxWorks target
    175183 RT Get Target Information VI does not work with multiple network interfaces on Vista
    Performance
    178443 Sending TCP or UDP packets at maximum throughput may hang single-core executing Phar Lap targets



    ID Known Issue
    Building and Distributing LabVIEW Applications
    179676

    Return
    NI-Switch IVI class reference in a type def cluster causes LabVIEW 2009 to hang when building an RT source distribution
    When building a source distribution in LV 2009, before the build is complete, LabVIEW 2009's build status window has a clickable Done button but the text still says "Processing Untitled 1.vi..." This window will stay in this state until you press done. After pressing Done LV 2009 is unresponsive.

    Workaround: Open original code in 8.6, right-click on all type defs and select "Disconnect from Type Def," save, open the project in LabVIEW 2009, and build the source distribution. --or-- You may not disconnect typedefs in source distribution.

    Reported Version: 2009    Resolved Version: IVI Compliance Package 4.2    Added: 08/05/2009
    File I/O
    173990

    Return
    FAT partition labels show up as files in Phar Lap
    FAT partition labels show up as files with a special attribute saying they are a volume ID in Phar Lap.

    Workaround: N/A

    Reported Version: 2009    Resolved Version: N/A    Added: 08/06/2009
    Functions, VIs, and Express VIs
    165930

    Return
    Get Fault List VI Allocates Memory Upon Fault
    The Get Fault List VI allocates memory when a fault occurs. Therefore, NI does not recommend using the Get Fault List VI inside a deterministic loop.

    Workaround: Use the Get Fault List VI in a non-deterministic loop.

    Reported Version: 2009    Resolved Version: 2010    Added: 08/07/2009
    Hypervisor
    158002

    Return
    Unable to Put the RT Target on a Hypervisor System into Safe Mode from MAX
    On NI Real-Time Hypervisor systems, you can not put the RT target into Safe Mode from NI Measurement & Automation Explorer (MAX).

    Workaround: Boot into RT Safe Mode through the bios of the controller.

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

    Return
    Windows Hangs During Shutdown On Certain Hypervisor Systems When Not Booted into Hypervisor Mode
    When an NI Real-Time Hypervisor system is booted into Windows-only mode, Windows hangs during the shut down process. This is due to the requirement that Windows use the Standard PC driver.

    Workaround: Give ample time for Windows to shut down and make sure the disk access LED on the front of the controller is no longer active, then physically power off or restart the controller.

    Reported Version: 2009    Resolved Version: 2010    Added: 06/30/2009
    166467

    Return
    On an NI Real-Time Hypervisor System, the Virtual Ethernet Connection Does Not Support TCP Offloading
    Enabling TCP offloading on the virtual Ethernet connection of an NI Real-Time Hypervisor system can cause connection instability and can substantially reduce performance.

    Workaround: Disable TCP offloading on the virtual Ethernet connection.

    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
    164513

    Return
    Network errors sending large TCP packets between Hypervisor Windows and Phar Lap OSes with a shared network card
    Network errors sending large TCP packets between Hypervisor Windows and Phar Lap OSes with a shared network card

    Workaround: Use two physical network cards

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/06/2009
    173879

    Return
    Multiple host network interfaces on same subnet as RT targets prevents MAX from discovering RT target
    If more than one host network interface is on the same subnet as an RT target, MAX may not be able to discover the RT target.

    Workaround: Isolate each network interface. Having two host NICs on the same subnet is not supported.

    Reported Version: 2009    Resolved Version: Not a bug    Added: 08/06/2009
    147064

    Return
    Converting Windows from ACPI mode to Standard PC mode can leave USB peripherals unresponsive
    RT Hypervisor systems are preconfigured to Windows Standard PC mode. However, if reinstallation is required, then a conversion from ACPI to Standard PC mode is necessary. It is possible that on reboot after the conversion, all USB peripherals will be unresponsive for a period of time.

    Workaround: If Remote desktop is enabled, logging in remotely will force the load of the USB drivers. Alternatively, you can simply wait for Windows to load USB drivers (could be up to 30 minutes). --or-- Reboot, possibly multiple times.

    Reported Version: 2009    Resolved Version: N/A    Added: 08/07/2009
    151832

    Return
    Serial port devices may need to update drivers
    Serial ports (as used for virtual console access to the RT OS) may need their serial drivers updated after switch to Windows Standard PC mode

    Workaround: Open Device manager, select the serial device, and righ-click>>update driver

    Reported Version: 2009    Resolved Version: 2010    Added: 08/07/2009
    LabVIEW Object Oriented Programming
    176901

    Return
    Deploying a VI that uses only child classes may crash Real-Time target
    If you deploy an application that uses a dynamic dispatch method VI without any parent class wires connected to it to RT, you may crash on run or call the wrong dynamic dispatch method

    Workaround: N/A

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/07/2009
    LabVIEW Project
    163516

    Return
    Reconfiguring the Web Server Requires a Target Reboot
    By default, LabVIEW requires you to restart the RT target to deploy new web server configuration settings on the target.

    Workaround: This behavior is required for VxWorks targets. However, you can disable the reboot requirement on ETS targets by adding the following token to the ni-rt.ini file on the target. [lvrt] WebServer.ReconfigureOnRT=true

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/07/2009
    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.

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

    Return
    The PID Toolkit and the Real-Time Execution Trace Toolkit Are Not Localized
    Although the LabVIEW Real-Time Module is localized for Japan, the PID Toolkit and the Real-Time Execution Trace Toolkit are not localized.

    Workaround: N/A

    Reported Version: 2009    Resolved Version: 2010    Added: 06/30/2009
    Operating System Specific
    178443

    Return
    Sending TCP or UDP packets at maximum throughput may hang single-core executing Phar Lap targets
    When sending TCP and UDP packets back and forth between a host system and a single-core RT system as fast as possible, while simultaneously trying to measure performance, the target may lock up.

    Workaround: Slow network transfer rate

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/05/2009
    146085

    Return

    Converting timestamp to numeric (of any representation) and back returns different timestamp on VxWorks target
    Converting timestamp to numeric (of any representation) using conversion VIs in Numeric palette, and back using To Time Stamp primitive returns different timestamp on VxWorks target

    Workaround: This is not a bug because precision is lost when converting the timestamp from 128-bit precision to a double of 64-bit precision.

     

    Reported Version: 2009    Resolved Version: Not a bug    Added: 08/06/2009
    175183

    Return
    RT Get Target Information VI does not work with multiple network interfaces on Vista
    On Windows Vista, the RT Get Target Information VI cannot detect an RT target that uses multiple network interfaces.

    Workaround: You can use NI Measurement & Automation Explorer to obtain information about RT targets interactively.

    Reported Version: 2009    Resolved Version: 2010    Added: 08/07/2009
    Performance
    178443

    Return
    Sending TCP or UDP packets at maximum throughput may hang single-core executing Phar Lap targets
    When sending TCP and UDP packets back and forth between a host system and a single-core RT system as fast as possible, while simultaneously trying to measure performance, the target may lock up.

    Workaround: Slow network transfer rate

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/05/2009

     

    Known Issues by Date

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

    158002 Unable to Put the RT Target on a Hypervisor System into Safe Mode from MAX
    162917 Windows Hangs During Shutdown On Certain Hypervisor Systems When Not Booted into Hypervisor Mode
    166467 On an NI Real-Time Hypervisor System, the Virtual Ethernet Connection Does Not Support TCP Offloading
    168343 RT Apply Target Network Settings VI Does Not Affect Secondary Network Cards
    170701 The PID Toolkit and the Real-Time Execution Trace Toolkit Are Not Localized
    176762 Time Triggered Variables do not work on NI Real-Time Hypervisor Systems
    178443 Sending TCP or UDP packets at maximum throughput may hang single-core executing Phar Lap targets
    179676 NI-Switch IVI class reference in a type def cluster causes LabVIEW 2009 to hang when building an RT source distribution
    146085 Converting timestamp to numeric (of any representation) and back returns different timestamp on VxWorks target
    164513 Network errors sending large TCP packets between Hypervisor Windows and Phar Lap OSes with a shared network card
    173879 Multiple host network interfaces on same subnet as RT targets prevents MAX from discovering RT target
    173990 FAT partition labels show up as files in Phar Lap
    147064 Converting Windows from ACPI mode to Standard PC mode can leave USB peripherals unresponsive
    151832 Serial port devices may need to update drivers
    163516 Reconfiguring the Web Server Requires a Target Reboot
    165930 Get Fault List VI Allocates Memory Upon Fault
    175183 RT Get Target Information VI does not work with multiple network interfaces on Vista
    176901 Deploying a VI that uses only child classes may crash Real-Time target



    ID Known Issue
    158002

    Return
    Unable to Put the RT Target on a Hypervisor System into Safe Mode from MAX
    On NI Real-Time Hypervisor systems, you can not put the RT target into Safe Mode from NI Measurement & Automation Explorer (MAX).

    Workaround: Boot into RT Safe Mode through the bios of the controller.

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

    Return
    Windows Hangs During Shutdown On Certain Hypervisor Systems When Not Booted into Hypervisor Mode
    When an NI Real-Time Hypervisor system is booted into Windows-only mode, Windows hangs during the shut down process. This is due to the requirement that Windows use the Standard PC driver.

    Workaround: Give ample time for Windows to shut down and make sure the disk access LED on the front of the controller is no longer active, then physically power off or restart the controller.

    Reported Version: 2009    Resolved Version: 2010    Added: 06/30/2009
    166467

    Return
    On an NI Real-Time Hypervisor System, the Virtual Ethernet Connection Does Not Support TCP Offloading
    Enabling TCP offloading on the virtual Ethernet connection of an NI Real-Time Hypervisor system can cause connection instability and can substantially reduce performance.

    Workaround: Disable TCP offloading on the virtual Ethernet connection.

    Reported Version: 2009    Resolved Version: N/A    Added: 06/30/2009
    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.

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

    Return
    The PID Toolkit and the Real-Time Execution Trace Toolkit Are Not Localized
    Although the LabVIEW Real-Time Module is localized for Japan, the PID Toolkit and the Real-Time Execution Trace Toolkit are not localized.

    Workaround: N/A

    Reported Version: 2009    Resolved Version: 2010    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
    178443

    Return
    Sending TCP or UDP packets at maximum throughput may hang single-core executing Phar Lap targets
    When sending TCP and UDP packets back and forth between a host system and a single-core RT system as fast as possible, while simultaneously trying to measure performance, the target may lock up.

    Workaround: Slow network transfer rate

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/05/2009
    179676

    Return
    NI-Switch IVI class reference in a type def cluster causes LabVIEW 2009 to hang when building an RT source distribution
    When building a source distribution in LV 2009, before the build is complete, LabVIEW 2009's build status window has a clickable Done button but the text still says "Processing Untitled 1.vi..." This window will stay in this state until you press done. After pressing Done LV 2009 is unresponsive.

    Workaround: Open original code in 8.6, right-click on all type defs and select "Disconnect from Type Def," save, open the project in LabVIEW 2009, and build the source distribution. --or-- You may not disconnect typedefs in source distribution.

    Reported Version: 2009    Resolved Version: IVI Compliance Package 4.2    Added: 08/05/2009
    146085

    Return
    Converting timestamp to numeric (of any representation) and back returns different timestamp on VxWorks target
    Converting timestamp to numeric (of any representation) using conversion VIs in Numeric palette, and back using To Time Stamp primitive returns different timestamp on VxWorks target

    Workaround: This is not a bug because precision is lost when converting the timestamp from 128-bit precision to a double of 64-bit precision.

    Reported Version: 2009    Resolved Version: Not a bug    Added: 08/06/2009
    164513

    Return
    Network errors sending large TCP packets between Hypervisor Windows and Phar Lap OSes with a shared network card
    Network errors sending large TCP packets between Hypervisor Windows and Phar Lap OSes with a shared network card

    Workaround: Use two physical network cards

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/06/2009
    173879

    Return
    Multiple host network interfaces on same subnet as RT targets prevents MAX from discovering RT target
    If more than one host network interface is on the same subnet as an RT target, MAX may not be able to discover the RT target.

    Workaround: Isolate each network interface. Having two host NICs on the same subnet is not supported.

    Reported Version: 2009    Resolved Version: Not a bug.    Added: 08/06/2009
    173990

    Return
    FAT partition labels show up as files in Phar Lap
    FAT partition labels show up as files with a special attribute saying they are a volume ID in Phar Lap.

    Workaround: N/A

    Reported Version: 2009    Resolved Version: N/A    Added: 08/06/2009
    147064

    Return
    Converting Windows from ACPI mode to Standard PC mode can leave USB peripherals unresponsive
    RT Hypervisor systems are preconfigured to Windows Standard PC mode. However, if reinstallation is required, then a conversion from ACPI to Standard PC mode is necessary. It is possible that on reboot after the conversion, all USB peripherals will be unresponsive for a period of time.

    Workaround: If Remote desktop is enabled, logging in remotely will force the load of the USB drivers. Alternatively, you can simply wait for Windows to load USB drivers (could be up to 30 minutes). --or-- Reboot, possibly multiple times.

    Reported Version: 2009    Resolved Version: N/A    Added: 08/07/2009
    151832

    Return
    Serial port devices may need to update drivers
    Serial ports (as used for virtual console access to the RT OS) may need their serial drivers updated after switch to Windows Standard PC mode

    Workaround: Open Device manager, select the serial device, and righ-click>>update driver

    Reported Version: 2009    Resolved Version: 2010    Added: 08/07/2009
    163516

    Return
    Reconfiguring the Web Server Requires a Target Reboot
    By default, LabVIEW requires you to restart the RT target to deploy new web server configuration settings on the target.

    Workaround: This behavior is required for VxWorks targets. However, you can disable the reboot requirement on ETS targets by adding the following token to the ni-rt.ini file on the target. [lvrt] WebServer.ReconfigureOnRT=true

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/07/2009
    165930

    Return
    Get Fault List VI Allocates Memory Upon Fault
    The Get Fault List VI allocates memory when a fault occurs. Therefore, NI does not recommend using the Get Fault List VI inside a deterministic loop.

    Workaround: Use the Get Fault List VI in a non-deterministic loop.

    Reported Version: 2009    Resolved Version: 2010    Added: 08/07/2009
    175183

    Return
    RT Get Target Information VI does not work with multiple network interfaces on Vista
    On Windows Vista, the RT Get Target Information VI cannot detect an RT target that uses multiple network interfaces.

    Workaround: You can use NI Measurement & Automation Explorer to obtain information about RT targets interactively.

    Reported Version: 2009    Resolved Version: 2010    Added: 08/07/2009
    176901

    Return
    Deploying a VI that uses only child classes may crash Real-Time target
    If you deploy an application that uses a dynamic dispatch method VI without any parent class wires connected to it to RT, you may crash on run or call the wrong dynamic dispatch method

    Workaround: N/A

    Reported Version: 2009    Resolved Version: 2009 SP1    Added: 08/07/2009

    Document last updated on 8/18/2009

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