下载中心

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

NI-FBUS Monitor Software 16.0 Win32/64Eng NI现场总线监控软件16.0

NI-FBUS Monitor Software
NI-FBUS Monitor Software可帮助您使用现场总线接口设备调试、监测和分析现场总线(FBUS)数据通信。
NI-FBUS Monitor Software是一款应用软件，可用于检测通信并捕获FBUS设备之间传递的数据包。使用此软件，您可以使用现场总线接口设备来诊断H1网络通信并进行设备开发调试。您还可以解码来自FBUS的数据包，监测实时列表并执行数据包分析。该软件还提供可配置的多窗口显示。NI-FBUS Monitor软件具有可配置的多窗口显示功能，您可以过滤数据包并实时查看列表和总线统计信息。

Win32/64Eng
16.0
文件大小: 335249800 字节 (319.72 MB)
修改日期: 2016-10-11 14:35
MD5: d48154cd10187ae4adc4bad69edc44bd
SHA1: a23b71381e676913ce320c83f9d83a9e8f629a68
SHA256: 79f176f730c7ff0fde154022c714454ef3f250ac52749ba4811f24c4c478ba27
CRC32: e3dfddd3

百度网盘与NI官方下载地址：

NI-FBUS Monitor Software 16.0 Win32/64Eng NI现场总线监控软件16.0

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

(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)

NI-FBUS 16.0 Readme

Overview

• NI-FBUS Communications Manager (CM) 16.0

• NI-FBUS Configurator 16.0

• NI-FBUS Monitor 16.0
  

Supported Operating Systems

• Windows 10/8.11/7 SP12

• Windows Server 2012 R2 (64-bit)1

• Windows Server 2008 R2 SP1 (64-bit)2
  

Supported Hardware

• NI PCI-FBUS/2 (2-Port Fieldbus Interface for NI PCI)

• NI PCMCIA-FBUS Series 2 (1-Port FOUNDATION Fieldbus Interface for PCMCIA)

• NI PCMCIA-FBUS/2 Series 2 (2-Port FOUNDATION Fieldbus Interface for PCMCIA)

• NI USB-8486 without USB screw retention and mounting option (1-Port FOUNDATION Fieldbus Interface for USB)
  

Application Software Support

Microsoft Visual Studio Support

Installation Instructions

• Log in as an administrator or as a user with administrator privileges.

• Insert the NI-FBUS Software media. The installer launches automatically. If the installer does not launch automatically, navigate to the media and launch the autorun.exe file.

• Follow the installation wizard to install the NI-FBUS software.
  

NI-FBUS 16.0 Drops Support for Microsoft Windows 7 RTM, Windows Vista, Windows XP, and Windows Server 2003

Product Security and Critical Updates

New Features and Bug FixesConfigurator 16.0

• Added support for LabVIEW 2016
  

Configurator 15.0

• Added support for LabVIEW 2015

• Removed CompactRIO support
  

• Field Device VIs are not available under the Foundation Fieldbus palette.

• Field Device properties are not available.

• Real-time target support is not available.

• Remote operations on CompactRIO are not available.
  

• Added support for the Foundation Fieldbus Template feature

• Added the COLLECTION block type to the nifGetObjectAttributes() function

• Extended the default segment number from four to 12 to support more segments

• The following table contains the ID and title of the issues fixed in NI-FBUS Configurator 15.0. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Configurator.

  ID	Fixed Issue
  514081	Configurator method of a DD file displays the help instead of the label
  507037	SMAR linking device fails in the ITK test because the CM invokes wrong VFD reference numbers
  507034	ITK 6.1.1 crashes for test case i9001_03 on NI PCI-FBUS
  507032	A race condition occurs in NI USB-8486 firmware when reading and writing data
  498281	Add Tag Editor to support OPC operations

  
  

Configurator 14.0

• Added support for LabVIEW 2014

• Removed legacy VIs and utilities
  

• The legacy VIs are not available under the Legacy API (Windows Only) palette.

• Tag Editor is not available.

• Add Interface Wizard is not available.
  

• The following table contains the ID and title of the issues fixed in NI-FBUS Configurator 14.0. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Configurator.

  ID	Fixed Issue
  483217	Interface Configuration Utility does not count EDDL local parameter number correctly
  473688	Maximum size for Common Software Download is incorrect in ITK
  468492	The C# API WaitAlert2 does not work
  424901	The Configurator cannot display the & symbol properly
  422834	Communications Manager (CM) resets CURRENT_TIME in MIB to 1972/01/01 when you download linking schedules in Clear Device mode
  422071	Update the .NET framework from 2.0 to 4.0 for .Net library

  
  

Configurator 5.0

• Added support to use CompactRIO with NI USB-8486 as field devices:
  

• Creating, editing, and deleting the Analog Input (AI), Analog Output (AO), Discrete Input (DI), and Discrete Output (DO) function blocks programmatically

• Auto-recovery after configuration

• Added Link Active Scheduler support to NI USB-8486 in field device mode
  

• Added field device support to CompactRIO with NI USB-8486, including NI cRIO-901x/902x/9068/9076/908x

• Added support to NI cRIO-9068 for Linux RT

• Added support to Windows 8.1

• Added support for LabVIEW 2013 SP1

• The following table contains the ID and title of the issues fixed in NI-FBUS Configurator 5.0. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Configurator.

  ID	Fixed Issue
  415733	Configurator does not show DD-defined menu correctly
  382252	Domain download based on MIB is not supported
  382251	Variable list data type is not readable in C# library

  
  

Configurator 4.1.1

• Added support to the HSE ITK

• Added support for LabVIEW 2012

• The following table contains the ID and title of the issues fixed in NI-FBUS Configurator 4.1.1. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Configurator.

  ID	Fixed Issue
  346192	Adding a customized tab in the block view on Configurator causes the error of NIFCONF_ERR_APPLICATION_EXCEPTION
  335253	Communications Manager cannot find the latest version of DD5 file when the Rev01 DD file does not exist
  325020	The VB6 example application crashes when opening session
  320528	Interface Configuration Utility fails to import the DD/CFF file when the DEV_REV is greater than 9

  
  

Configurator 4.1

• Added support to NI USB-8486 with USB screw retention and mounting option on CompactRIO

• Provided a set of LabVIEW APIs to monitor data over the H1 bus and programmatically configure the H1 network (excluding schedule/trend/alarm downloading)

• The following table contains the ID and title of the issues fixed in NI-FBUS Configurator 4.1. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Configurator.

  ID	Fixed Issue
  302729	The Import DD feature fails if the local file path is longer than 100 characters
  247680	The function nifDownloadDomain() returns E_RESOURCE (-6) error when downloading Yokogawa FVX110 firmware
  247652	The Field Diagnostic Alarm test cases cannot run due to the E_BAD_ARGUMENT (-5) error in the function nifConnectAlert()

  
  

Configurator 4.0.1

• Added support to Windows 7

• Added support to the 64-bit operation systems for Windows 7/Vista/Server 2008 R2

• Improved the user interface of Communications Manager

• Enabled the interfaces automatically with default settings without the need to run Interface Configuration Utility

• The following table contains the ID and title of the issues fixed in NI-FBUS Configurator 4.0.1. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Configurator.

  ID	Fixed Issue
  219390	Configurator crashes on some EDDL devices
  217415	Configurator crashes in Live List window when CM is closed manually
  215340	The parameter values in offline device are still NULL if the imported online parameters are 0
  203244	Incorrect tab index for EDDL with empty menu item

  
  

Configurator 4.0

• Added support to NI USB-8486 H1 interface devices

• Added support to DDS 5.1.2

• Improved EDDL layout

• Added new DD/CFF files supporting the new devices

• Fixed some major inconvenience issues
  

Monitor 4.0.2

• The following table contains the ID and title of the issue fixed in NI-FBUS Monitor 4.0.2. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Monitor.

  ID	Fixed Issue
  332131	Monitor may lose packets when a large number of FF devices are connected with NI USB-8486

  
  

Monitor 4.0.1

• The following table contains the ID and title of the issue fixed in NI-FBUS Monitor 4.0.1. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Monitor.

  ID	Fixed Issue
  300080	Monitor may sometimes fail to launch

  
  

Monitor 4.0

• Added support to NI USB-8486 H1 interface devices

• Added support to Windows 7

• Added support to the 64-bit operation systems for Windows 7/Vista/Server 2008 R2

• Added support to the simulator board

• The following table contains the ID and title of the issues fixed in NI-FBUS Monitor 4.0. This table is not an exhaustive list of issues fixed in this version of NI-FBUS Monitor.

  ID	Fixed Issue
  101645	Supporting for partial load of the large files
  88190	Some packet numbers become negative
  87112	The first page is always printed when printing a specific page

  
  

Driver Version Naming Changes

Evaluation Mode

• Configuring multiple offline interfaces

• Configuring offline devices through DD/CFF files

• Configuring offline function block applications

• Saving offline configurations
  

• Running the simulator board based on an existing Monitor record file
  

Troubleshooting and Frequently Asked Questions

• How do I install the NI USB-8486, NI PCMCIA-FBUS, NI PCMCIA-FBUS Series 2, or NI PCI-FBUS/2 interface board?
  
  Install NI-FBUS and shut down the computer. Follow the instructions in NI-FBUS Installation Guide to install the Fieldbus hardware. Restart the computer and Windows recognizes the NI-FBUS interface card automatically. Use the Found New Hardware Wizard and install the driver for the new hardware.
  
  Run the Interface Configurator Utility, which shows the NI USB/PCI/PCMCIA interface after you install the driver.
  
  Open the NI-FBUS Communications Manager to use the newly-configured hardware.

• When do I need to activate the NI-FBUS Configurator 16.0 and Monitor 16.0?
  
  When launching NI-FBUS Configurator 16.0 or NI-FBUS Monitor 16.0, activate the product in the activation request dialog box that appears. You also can activate these products later using the NI License Manager, available by selecting Start»All Programs»National Instruments»NI License Manager.
  
  You must activate NI-FBUS Configurator before you can use the following features:
  
  You do not have to activate the NI-FBUS Configurator in the following situations:

• Install the drivers for the NI-FBUS interface devices

• Use Communications Manager APIs to build your own applications

• Evaluate the NI-FBUS Configurator in offline mode
  

• H1 interfaces (NI PCMCIA-FBUS, NI PCI-FBUS, and NI USB-8486) and HSE interfaces (Ethernet and HSE Linking Device)

• Ethernet and High-Speed-Ethernet (HSE) Linking Device in the Add Interface Wizard, Interface Configuration Utility, and Communications Manager
  

• How do I activate the NI-FBUS Configurator and NI-FBUS Monitor?
  
  You can acquire the activation code from NI through the Internet, telephone, or fax. Refer to the National Instruments License Manager Help, available by selecting Help»Contents in the NI License Manager, for more information about activating the NI software.
  
  Do not remove the Ethernet adapter from the computer after you activate NI-FBUS Configurator. Removing the Ethernet adapter might deactivate the NI-FBUS Configurator.

• How does NI-FBUS Communications Manager support Device Descriptions (DD)?
  
  NI-FBUS uses manufacturer-supplied device descriptions. To use a new Device Description (DD), you must specify a "Base Directory" for your device descriptions. This directory can be anywhere on your computer. All your DD files are in this directory. Complete the following steps to locate the base directory.
  After locating the directory, complete the following steps to import your manufacturer-supplied DD files into this directory.NI-FBUS uses identifying information in the actual device to locate the DD for this device. The identifying information includes four resource block parameters: "MANUFAC_ID", "DEV_TYPE", "DEV_REV", and "DD_REV". If the identifying information is incorrect, NI-FBUS is not able to locate the DD for the device. When NI-FBUS locates the DD, NI-FBUS matches the block types in the DD with the actual blocks in the device by using the Item ID of the block characteristics record. If this block information is incorrect, NI-FBUS is not able to locate the description of that particular block.

• Launch NI-FBUS the Interface Configuration Utility and click Import DD/CFF.

• Click Browse to locate the DD/CFF file or input the path.

• Click OK.

• The Interface Configuration Utility checks the DD/CFF files. If this utility does not detect any errors, the utility copies the .cff file, the .ffo file, and the associated .sym file to the correct location in the base directory. Otherwise, the utility returns an error message for you to identify the error.
  

• Launch the NI-FBUS Interface Configuration Utility and click Import DD/CFF.

• Click DD Info.

• Click Browse to locate the base directory path, or manually enter the path to this directory, such as C:Program FilesNational InstrumentsNI-FBUSDD.
  

• Troubleshooting — Setting Addresses
  
  If you cannot set the address of your device, you may need to change some of the "System Management Info" parameters in the Advanced settings of your interface port in the Interface Configuration Utility. The parameters in setting addresses are T1 and T3. These parameters represent delay time values that your interface card uses to compensate for the delays inherent in the device and in the set address protocol.
  
  T1 is a parameter that describes the expected response delay of the device at a given address. Normally, you do not need to increase the value of this parameter; however, if your interface card cannot detect responses of the device related with setting an address, increase this value of this parameter. The correct value for this parameter can depend on the number of devices on the link. For example, if you are using a bus monitor, you might see a WHO_HAS_PD_TAG request going to the device to start the Set Address sequence, and an IDENTIFY response coming back, but with the host never continuing with the next step in the protocol, the SET_ADDRESS packet. This probably mean that your T1 value is too small and should be increased.
  
  T3 is a parameter that describes the expected time for the device to respond at its new address. This parameter is highly dependent on the number of devices on the link and the number of addresses being polled. Refer to the next troubleshooting issue Setting the Number of Polled Addresses for more information about setting the number. If you are using a bus monitor, you may be able to see the host identify a device with the IDENTIFY packet at the new address before the device has sent its probe response (PR) packet to the host. This error indicates that the T3 value is too small. If this error occurs, increase your T3 value until the IDENTIFY packet to the new address occurs after the PR.
  
  All of the System Management Info timers are in units of 1/32 of a millisecond; for example, T3=32000 units means that T3=1 second.

• Troubleshooting — Setting the Number of Polled Addresses
  
  The Fieldbus Specification describes how a Link Active Scheduler device (LAS device) probes a list of addresses to allow devices to come online during normal operation. The LAS sends a Probe Node (PN on the bus monitor) packet to each address in its list of addresses during operation at a regular interval determined by the number of devices on the link and the value of the Link Maintenance Token Hold Time parameter. The Fieldbus Specification describes how to tell the LAS to avoid probing certain addresses in the range, which can speed up detection of new devices on the bus (or devices that are having their addresses changed). The two parameters involved in maintaining the list are called FirstUnpolledNode and NumOfUnpolledNodes, and they can be found in the NI-FBUS Interface Configuration utility advanced settings for a port, under the "DLME Master Info" section. The following diagram shows how the LAS determines the list:
  
      PPPPPPPPPPPPPPPPPPPXXXXXXXXXXXXXXXXXXXXXXXXXXXXPPPPPPPPPP
  
      |               |<--NumOfUnpolledNodes-->|        |
  
    0x10 (16)    FirstUnpolledNode                 0xf7 (247)
  
      P is the address that is probed for new devices
  
      X is the address that is not probed for new devices
  
  To summarize, FirstUnpolledNode tells the LAS the starting address of a section of addresses to skip, and NumOfUnpolledNodes tells the LAS the length of that region. So if FirstUnpolledNode was 0x25 and NumOfUnpolledNodes was 0xba, then none of the addresses from 0x25 to 0xdf would be probed. That means that if a device with an address of 0x25 was placed on this bus, the LAS would not probe it and it would never be able to send or receive packets on the bus.
  
  The main reason to have a NumOfUnpolledNodes with a nonzero value is this: The LAS probes every address in the list, and then starts over again at the beginning. Remember that a device cannot become active on the bus until its address is probed. If the LAS is probing all 255-16+1=240 possible addresses and each probe node request goes out every T millisecond, it might take 240T milliseconds for a device to come online. If, however, the LAS probed only the first 16 addresses and the last 16 addresses, it might take 32T milliseconds for the device to come online; this results in the new device being recognized almost 8 times faster. These parameters also affect the Set Address protocol, because recognizing a device at a new address is the same as recognizing a completely new device, because the new address must be probed for the device to come online. In this way, the NumOfUnpolledNodes parameter can affect the value of the Set Address protocol parameter "T3", which is described in the section above. Increasing the NumOfUnpolledNodes parameter might fix a SetAddress T3 problem because it takes the device less time to be recognized at the new address.
  

Known Issues

• For devices with a third-party stack, the NI-FBUS Configurator might take a long time to update device information such as Function Block list, MIB parameters, and so on. The reason is that when a device with a Softing stack has a higher address, like 0xE0 or 0xF6, the NI-FBUS Communications Manager is hard to obtain a valid VCR connection to the MIB of the devices. You can solve the problem by changing the address of the device to a lower one when the Configurator finishes updating the device.

• The following table contains the ID and title of known issues for NI-FBUS.

  Issue ID	Known Issue
  431096	Issue - NI-FBUS PCI/FBUS card does not appear in ICU after reinstalling the FBUS without restart. Description - When you use the NI PCI/FBUS card on Windows XP and reinstall or upgrade NI-FBUS, you plug out the Fieldbus hardware. After the installation, the card does not appear in ICU. This issue only occurs on Windows Vista or later. Workaround - Launch the Windows Device Manager, uninstall the card, click Scan for the changed hardware, and reinstall the software for the hardware.
  219594	Issue - When the system with multiple NI USB-8486s connected is recovered from hibernation on Windows Vista or later, only one USB-8486 is left in Configurator. Description - When the system with multiple NI USB-8486s connected is recovered from hibernation, the log in Communications Manager shows that all the interfaces are reinitialized automatically. When you use Take Online in Configurator, only one USB-8486 is left in the list. This issue only occurs on Windows Vista or later. Workaround - Restart Communications Manager and Configurator after the system is recovered from hibernation.
  171893	Issue - NI-FBUS does not support the dynamic image display feature in EDDL Description - The dynamic attribute of the image in EDDL is not supported. Configurator shows these images statically. Workaround - N/A
  89744	Issue - Communications Manager cannot initialize the HSE/H1 linking device if one of the link IDs is equal to or greater than 0xF0FF Description - If one of the link IDs on the HSE/H1 linking device is equal to or greater than 0xF0FF, Communications Manager can not start successfully. Error occurs when initializing the HSE/H1 linking device. Workaround - Use the default ID. Do not set the ID to the value which is equal to or greater than 0xF0FF.

  
  

Resources

Credits

Accessing the Help

Finding Examples

Automating the Installation of NI Products

• For more information about silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.

• For more information about silent installations of NI products in a suite, such as NI Developer Suite, refer to KB 4GGGDQH0, How Do I Automate the Installation of a Suited Installer?.

• To determine what version of NI Installers your product contains, refer to KB 4CJDR18M, How Can I Determine the Type and Version of My NI Installer?.
  

Using NI Software with Microsoft Windows 10

Using NI Software with Microsoft Windows 8.1

Legal Information

• Notices are located in the <National Instruments>_Legal Information and <National Instruments> directories.

• EULAs are located in the <National Instruments>SharedMDFLegallicense directory.

• Review <National Instruments>_Legal Information.txt for information on including legal information in installers built with NI products.