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.
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:
The following items are known issues in LabVIEW 2009 Real-Time Module sorted by Category.
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 146085 Return |
Converting timestamp to numeric (of any representation) and back returns different timestamp on VxWorks target
| |||||
| 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.
| |||||
| 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
| |||||
The following items are known issues in LabVIEW 2009 Real-Time Module sorted by Date.
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
|
Document last updated on 8/18/2009