下载中心

Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://pcmv.cn/thread-490-1-1.html

视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://pcmv.cn/thread-26524-1-1.html

LabVIEW Real-Time Module 8.5.1 Win32Eng LV8.5.1实时模块RTM8.5.1

LabVIEW Real-Time模块可帮助您创建在嵌入式硬件设备上执行的可靠、独立的应用程序。
LabVIEW Real-Time模块是LabVIEW编程环境的一个附加软件，可用于创建和部署用于测试、监测和控制的实时分布式系统应用程序。您可以利用实时操作系统来确保独立系统的可靠性和精确定时。数百个事先编写好的LabVIEW库和硬件API还可以帮助您节省宝贵的开发时间以及实现确定性数据采集。
LabVIEW Real-Time模块为创建可靠独立的嵌入式系统提供了基于图形化编程方法的完整解决方案。 作为LabVIEW开发平台的附加模块，LabVIEW Real-Time模块有助开发和调试图形化应用程序，并将这些程序下载到嵌入式硬件设备（如：CompactRIO、Single-Board RIO、PXI、视觉系统，乃至第三方PC）上执行。

使用LabVIEW Real-Time模块的三大理由:
1. 将LabVIEW图形化编程扩展至独立的嵌入式系统
LabVIEW Real-Time包含了用于多线程和实时线程调度的内置结构，以帮助您高效地编写稳定、确定的代码。 您可对独立式系统进行图形化编程，使其更长时间地可靠运行。

2. 利用实时操作系统实现精确的定时和高可靠性
通用操作系统并不适用于需要严格定时的重要应用。 LabVIEW Real-Time可支持运行NI Linux Real-Time、VxWorks或Phar Lap ETS实时操作系统(RTOS)的NI嵌入式硬件。

3. 利用各类IP和实时硬件驱动
您可使用数百个预编写的LabVIEW函数库，比如PID控制和FFT，并用于独立式系统。 NI还提供了大量实时硬件驱动程序和LabVIEW API，适用于大多数NI I/O模块，以实现确定的数据采集。

百度网盘下载地址:
请注册登录视觉论坛会员，购买附件查看

LabVIEW Real-Time Module 8.5.1 Win32Eng LV8.5.1实时模块RTM8.5.1

http://pcmv.cn/thread-28896-1-1.html?fromuid=9

(出处: 机器视觉论坛)

LabVIEW Real-Time Module 8.5.1 Readme

Installation

Supported Platforms

New Features

• Reliance filesystem support—The reliance filesystem provides fast disk access and data preservation in the event of a power interruption. Refer to the Using Desktop PCs as RT Targets with the LabVIEW Real-Time Module document for information about installing the Reliance filesystem on an RT Desktop PC target.

• Formatting RT Desktop PCs from Safe Mode—With previous versions of the LabVIEW Real-Time Module, choosing the format option from Safe Mode formatted only the RT partition of the hard drive. When version 8.5.1 of the Real-Time Module is installed on the target, the Safe Mode format option formats the entire hard drive.

• New supported targets—The LabVIEW 8.5.1 Real-Time Module supports the following new targets: CompactFieldPoint 2200, CompactRIO 9072 and 9074, PXI 8104, and the NI 1722 and 1742 smart cameras.

• Support for nVidia ethernet drivers—The LabVIEW 8.5.1 Real-Time Module includes support for all nVidia ethernet chipsets, which you can use with RT Desktop PC targets.
  

Known Issues

All Target Platforms

• File I/O reads and writes of a drive formatted with the Reliance file system can slow down significantly when you include a large number of files in a single directory. Performance varies from system to system, but generally the slowdown appears when you include 1000 or more files in a directory. To avoid this issue, distribute files across multiple directories.

• If you format an RT target with an 8.5 format disk or Utility USB drive, you might not be able to downgrade the target to a previous version of the Real-Time Module. To downgrade a target from the LabVIEW 8.5 Real-Time Module to a previous version of the Real-Time Module, reformat the target with a format disk or utility USB drive created for a previous version of the Real-Time Module.

• Uninstalling RT software using an Uninstall Disk can leave the RT target in an unbootable state. If you encounter this issue, you can use a Safe Mode Disk to boot and reinstall RT software.

• When booting an RT Desktop PC target from a USB drive, certain BIOSes hang at the message "Waiting for USB to initialize..." To resolve this issue, remove the USB drive, wait a few seconds, and reinsert the USB drive.

• The Real-Time Module 8.5 introduced LogosXT, a new network protocol for shared variables, which can increase CPU usage in some cases. You can use an INI token to diable LogosXT and revert to the pre-8.5 Logos protocol. Refer to the National Instruments Web Site for more information about disabling LogosXT.

• If you modify and redeploy a VI, probes can stop receiving updates. After modifying a VI, you should close and recreate probes.

• If you format an RT target using a utility USB drive, you cannot subsequently format the target using a floppy drive.

• USB hard drives are not supported on RT targets. If you need to transfer files over USB, use a USB thumb drive.

• The disk footprint and the memory footprint of the Real-Time Module have increased by over 10% since version 8.2.1.

• When you create or add a VI under a specific target in the Project Explorer window, not all VIs and functions that appear on the palette are necessarily supported on that target.

• Indicators that are attached to local variables do not update properly through via remote front panel.

• Graphs and charts in subVIs do not display properly via remote front panel.

• The Strings[] property node does not supply a value until you make a remote front panel connection to the application.

• You cannot run LabVIEW Real-Time targets from secondary or removable hard drives.

• Queues allocated in RT VIs take up 150% of expected memory.

• Windows might fail to install or boot on a drive or partition formatted for LabVIEW RT. Before installing Windows on a drive or partition that has been configured or formatted for LabVIEW RT, delete the RT partition using a disk utility such as fdisk and recreate the partition for FAT32. While installing Windows, you can allow Windows to format the FAT32 partition.
  

ETS

• On RT PXI 8106 and 8196 targets, performing a TCP/IP write with a string larger than 64kB can consume CPU resources for several minutes.

• ETS targets can hang if a DHCP server forces an infinite lease time.

• Some USB thumb drives do not work on ETS targets. The following USB thumb drives are known to work properly on ETS targets: Memorex 1GB USB 2.0 TravelDrive, SanDisk Cruzer 128MB (non-U3), NexDisk USB 32MB (PSD-32N).

• ETS targets cannot use more than 2 GB of RAM.

• Desktop PCs that use processors without 64-bit writable RDTSC registers are not compatible with the NI RT Extensions for SMP. You can safely use an affected system as an RT target in single-core mode if you do not install the NI RT Extensions for SMP on the target. To use an RT Desktop PC as a multi-core RT target, the PC must use CPUs with 64-bit writable RDTSC registers.

• Desktop PCs that use AMD family 0Fh CPUs, distinguished by an integrated memory controller, typically ship with energy-saving features enabled in the BIOS. These energy-saving features can cause instability when the PC is used as an RT Desktop target with the NI RT Extensions for SMP installed. To use an affected PC as an RT Desktop PC target, you must either use the target in single-core mode or disable the energy-saving features in the BIOS. If the BIOS does not allow you to disable the energy saving features, you can safely use an affected system as an RT target in single-core mode by not installing or uninstalling the NI RT Extensions for SMP on the target.

• The maximum number of files you can open on an ETS RT target simultaneously is 256.

• If you receive an error while opening a TDMS file, closing the file can crash the RT target.
  

VxWorks

• Reading a shared variable that contains no data can cause slowdowns on VxWorks targets.

• VxWorks targets do not comply with the latest rules for Daylight Savings Time. As a result, VxWorks targets may report incorrect time from early March through early April and from late October through early November. The actual start and end dates of Daylight Savings Time differ from year to year, and not all regions participate in Daylight Savings Time. Refer to the official Daylight Savings Time regulations in your region for more information about the specific start and end dates of Daylight Savings Time each year.
  
  To prevent time fluctuations on the target, consider disabling Daylight Savings Time in the BIOS. If you need to compensate for Daylight Savings Time on the target, you can use the Set Date and Time VI to update the time at the beginning and end of Daylight Savings Time.

• The SMTP Email Send Message VI does not work on VxWorks targets.

• On VxWorks targets, using the Semaphore VIs and the Rendezvous VIs in the same application can cause errors and undefined behavior. You might also encounter errors if the application uses vi.libPlatform_goopsup.llbGOOP Object Repository.vi in addition to the Semaphore VIs or the Rendezvous VIs.

• RT Ping.vi does not return the IP or MAC address on cRIO 9012 targets.

• On cRIO 901x targets, DNS lookup has a long timeout on private networks with no DNS server. If the network has no DNS server, there is no need to perform a DNS lookup.
  

Upgrade and Compatibility Issues

Upgrading from 8.5 or Earlier

• The LabVIEW 8.5 Real-Time Module included a timing behavior change that affected the Wait (ms) function. Prior to version 8.5, the Wait (ms) function waited slightly less than the requested number of milliseconds, by up to one ms. In version 8.5, the Wait (ms) function waited slightly more than the requested number of milliseconds, by up to one ms. This timing change caused a problem (bug ID 4D5CTEKI), and the LabVIEW 8.5.1 Real-Time Module fixes the problem by reverting to the original timing behavior. If you updated your LabVIEW RT VIs to maintain consistent timing behavior in version 8.5, you will need to revert the VIs to maintain timing consistent timing behavior in version 8.5.1.
  
  Note—The magnitude of the timing behavior change was in the range of under 1 ms, so if you did not notice the altered timing behavior in version 8.5, you most likely will not notice any change in version 8.5.1. Refer to the Real-Time Module 8.5 readme file for information about how the timing behavior changed in version 8.5. Refer to bug ID 4D5CTEKI in the Bug Fixes section of this document for more information about the timing issue that arose in version 8.5 and is fixed in version 8.5.1.
  

Upgrading from 8.2.1 or Earlier

• Timed Loop error conditions that generated error −820 in the Real-Time Module 8.2.1 and earlier now generate error −818.

• In Windows Vista, you cannot use the RT Disk Utilities in NI Measurement & Automation Explorer to create bootable floppy disks. However, if you have Administrator status in Vista, you can create a Desktop PC Utility USB drive by selecting Tools»RT Disk Utilities»Create Desktop PC Utility USB Drive in MAX.

• The Real-Time FIFO VIs have been replaced with the Real-Time FIFO Functions. These functions perform faster and contain additional functionality. For compatibility with upgrading applications, the previous Real-Time FIFO VIs still load from an existing LabVIEW block diagram, but they are no longer available on the Real-Time palette.

• When you install the Network Variable Engine on an RT target, you also must install the Variable Client Support with the same version number. When you upgrade a target from LabVIEW 8.0.x to LabVIEW 8.2.x, you also must upgrade the Network Variable Engine and the Variable Client Support. For the LabVIEW Real-Time Module 8.2.x, you must install Variable Client Support 1.2 and Network Variable Engine 1.2 on the RT target using the LabVIEW Real-Time Software Wizard in Measurement & Automation Explorer.

• The Real-Time Module 8.0 returns error code –2222 to indicate that a shared variable with the Enable Real-Time FIFO option selected has no value. The Real-Time Module 8.2 and later no longer returns error code –2222 but instead returns error code –1950679034 (0x8BBB0006) to indicate the same problem. This error code is consistent with shared variables that have the Real-Time FIFO disabled.

• You must enable the W2 hardware jumper to upgrade the RT Engine of an NI PXI-8145RT controller from version 7.1.1 and earlier to version 8.0 or 8.2.x. Refer to the PXI-8140RT Series User Manual for information about the settings and options for the onboard jumpers and switches.

• In the Real-Time Module 8.0, executables you build with LabVIEW and the Real-Time Module have a .rtexe extension, which is changed from the .exe extension in earlier versions. Although the extension change was cosmetic, in the Real-Time Module 8.2.x you might notice different behavior associated with the extension change. In the Real-Time Module 8.0 and earlier, you can run an executable built with LabVIEW and the Real-Time Module on Windows, and then use FTP to transfer the executable to an RT target and run it when you boot the RT target. In the Real-Time Module 8.2.x, you cannot run an RT executable (.rtexe) on Windows.
  
  If you want to run an RT executable on Windows and on the RT target, you must create and build two build specifications (one for Windows and one for an RT executable) and drag the necessary VIs for the build specification to each target in the project.
  
  Executables for VxWorks targets do not run on Windows or on Phar Lap ETS targets.

• The NI PCI-7041 is no longer supported with the Real-Time Module 8.2.x and later.

• The following USB thumb drive is not supported for RT target booting or storage: SanDisk Cruzer with U3 smart technology.

• If you read paths from a file or convert paths from strings and if you use different delimiters for file paths, the paths do not match in comparison operations even though the paths are functionally equivalent but with different delimiters. Review all paths and verify that all use the correct delimiter. Do not use UNC paths.

• Running the Execution Trace Toolkit on a VI containing Timed Loops might show incorrect thread names of Timed Loop threads if the trace is longer than a few seconds.
  

Bug Fixes