LabVIEW Real-Time Module for RTX Targets Troubleshooting

The following document contains configuration instructions for running the RTX target as a boot-mode process. The document also contains a list of some errors that you might receive when using the LabVIEW Real-Time Module for RTX Targets and solutions for each error.

Configuring the RT Target to Run as an RTX Boot-Mode Process

When LabVIEW RT for RTX is initially installed, the RT Engine is configured to start up automatically once the user has logged into Windows. LabVIEW RT for RTX can be started and stopped manually using the LabVIEW for RTX Manager in the system tray.

Additionally, it is also possible to configure the system so that LabVIEW RT for RTX runs as an RTX boot-mode process. The RT target running on the real-time subsystem executes once the Windows OS has loaded but before you log in, allowing the execution of start-up applications that don’t require the user to log into the system before they run.

Complete the following steps to configure the RT target as a boot process.

1) Configure the RTX subsystem to startup on boot. For RTX 5.5, go to the Programs>>Venturcom RTX>>RTX>>RTX Properties>>Settings tab and change the startup mode from Demand to Boot. For more detailed information on how to do this, refer to the Venturcom documentation.
2) Enter the following commands in the Windows command prompt:

cd c:\rtxroot\ni-rt\system

rtssrun /boot emblview.rtss

Note: replace the c:\rtxroot with the actual path of the RTX root folder.

The real-time subsystem prompt you that emblview.rtss was registered as a boot-time process.

3) Accept the changes and reboot the computer.

You can revert the changes by switching the startup mode from Boot to Demand and then accepting the changes.

Known Issues

The following list describes some errors that you might receive when using the LabVIEW Real-Time Module for RTX Targets.

Detecting and Configuring the NI PCI-7831 Plug-in Device—Refer to the Getting Started with the NI 7831R document.

RTX Starvation Timeout Errors—Reboot the host computer to restore proper functionality of the Windows environment.

-RTX Starvation Timeout with RT Startup Applications—Start-up applications without sleep cause Windows to freeze at boot. Start-up VIs that execute on the RTX subsystem must include sleep to avoid monopolizing CPU resources. If you do not include sleep in a start-up application the computer will freeze when you log into Windows and the RTX subsystem loads. You will have to boot into Windows Safe Mode and edit the ni-rt.ini file in the RTXROOT directory to stop the start-up application from loading
-Multiprocessor systems—Reboot the host computer and RTX subsystem. You can configure RTX to use a single dedicated processor allowing Windows to use the second processor.

Access Violation—Reboot the host computer and the RTX Subsystem.

Windows System Clock Not Keeping Correct Time—RTX subsystem tasks supercede Windows execution system task. Use a 3rd party time server application to keep the Windows clock updated.

Bad Windows performance and RTX applications running out of memory—The amount of memory that RTX uses for the non-paged pool is smaller than the total physical memory. You can increase the amount of memory that RTX uses for the non-paged pool. Refer to the Increasing the Size of Non-Paged Memory tech note on the Venturcom Website, www.vci.com for information about increasing the amount of non-paged pool memory.

Reducing Jitter in RTX Applications—Disable Windows cursor effects and virus scanners.

Default www Directory Set to ni-rt\startup\www—When the RT target on the real-time subsystem loads, it initializes the Web Server root path to ni-rt\startup\www when a startup application is running. Set the Web Server root path to c:\RTXROOT\ni-rt\system\www in the Web Server: Configuration page of the Tools>>RT Target: RTX (RTRTX::0)Options dialog box.

Windows Returns a Green Screen When Shutting Down Host Computer—Windows returns a green screen when shutting down a host computer after you install the Venturcom RTX Runtime 5.5 and an NI product that uses the niRTProxy service. This scenario usually happens on slower computers (<300 MHz P2) or computers with an NI RT Series plug-in device installed because they do not have enough time to properly shut down the niRTProxy service. You can increase the Windows kill service timeout from 20 seconds to 2 minutes to allow Windows enough time to properly shut down the niRTProxy service. Use the Windows regedit utility to modify the following registry key:

location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

key name: WaitToKillServiceTimeout
new key value: 120000

The LabVIEW Real-Time Module for RTX Targets is Incompatible with the Windows XP Service Pack 2—National Instruments does not recommend installing the Windows XP Service Pack 2 with the LabVIEW Real-Time Module for RTX Targets. The LabVIEW Real-Time Module for RTX Targets may not be fully compatible with the Windows XP Service Pack 2. Refer to the National Instruments Web site at ni.com/info and enter the info code winxpsp2 for information about NI products and Windows XP Service Pack 2 compatibility.

See Also:
Product Manual: Getting Started with the NI 7831R
Venturcom Technote: Increasing the Size of Non-Paged Memory

Reader Comments | Submit a comment »