石鑫华视觉
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的下载服务器对我国IP地址不是很友好，有些时候速度很慢或大的资源下载很容易出错，这样会造成安装过程各种类型报错而无法安装。建议在下载完成后，对下载资源做校验和验证（NI一般会提供MD5或SHA256等），与官方或视觉论坛提供的校验和对比，一致就可以安装，如果不一致，则需要重新下载。视觉论坛早期下载的资源，那时候NI没有这么多限制，基本上都是正常下载的资源；后期下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘，所以百度网盘的资源基本上是正确的。校验和工具下载地址：
文件Hash计算器FHash,文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算
http://pcmv.cn/thread-26524-1-1.html
NI-VISA3.0 Mac OS X 美国国家仪器虚拟仪器软件架构VISA3.0 苹果版下载
NI-VISA为使用GPIB、串行、PXI和其他类型仪器的用户提供支持。
NI-VISA是一个NI仪器驱动程序，是虚拟仪器软件架构(VISA) I/O标准的具体实现。虚拟仪器软件架构(VISA)这一标准用于配置和编程基于GPIB、VXI、PXI、串口(RS232/485)、以太网/LXI和/或USB接口的仪器系统以及故障分析。NI-VISA包括实用程序、底层控制功能和范例，可帮助您快速创建应用程序。
百度网盘下载：
NI-VISA3.0：
链接：请注册视觉论坛会员登陆后购买附件下载查看
提取码：请购买附件下载查看
NI官方下载地址（可能无效或无法下载完成）：
NI-VISA3.0：
请购买附件下载查看
NI-VISA3.0 Mac OS X 美国国家仪器虚拟仪器软件架构VISA3.0 苹果版下载
http://pcmv.cn/thread-22965-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
National Instruments NI-VISA(TM) Software for Mac OS X. Version 3.0.
Copyright(c) 1995, 2003 National Instruments Corporation. All rights reserved.
NATIONAL INSTRUMENTS HOLDS MULTIPLE COPYRIGHTS, TRADEMARKS, AND PATENTS
FOR THIS PRODUCT. BY DOWNLOADING AND/OR INSTALLING THIS PRODUCT, YOU
AGREE TO THE TERMS OF THE license.txt FILE THAT RESIDES IN THE SAME DIRECTORY
AS THIS readme.txt FILE ON THE CD AND/OR WEB SITE. FOR PATENTS COVERING
NATIONAL INSTRUMENTS PRODUCTS, REFER TO THE patents.txt FILE ON THE ROOT
DIRECTORY OF YOUR CD (IF APPLICABLE) AND/OR www.ni.com/patents.
CONTENTS OF THIS FILE
---------------------
Supported VISA Features
VISA Support for Multiple GPIB-VXI Controllers
Installed Files and Paths
NI-VISA 3.0 Improvements and Bug Fixes
Known Issues
SUPPORTED VISA FEATURES
-----------------------
We now support remote NI-VISA access. Any machine with the NI-VISA server
can export its resources to other NI-VISA clients. Only the client is
supported on Mac OS X and its settings are configured in VisaConfig. To use
a remote VISA resource, the name is a URL including the machine name or IP
address, followed by the traditional VISA resource name. Examples include:
"visa://machine.domain.com/GPIB0::5::INSTR"
"visa://1.2.3.4/ASRL2::INSTR"
Remote NI-VISA fully supports all functionality of all interface types,
including message based, register based, and all events.
NI-VISA 3.0 on Mac OS X adds TCP/IP functionality for both raw (SOCKET) and
VXI-11 (INSTR) protocols. This was added in NI-VISA 2.5 on Win32.
This driver also supports the National Instruments ENET-Serial products.
See the Serial section in chapter 9 of the NI-VISA User Manual for details.
Note that the NI-488 driver only supports the GPIB-ENET, so in turn,
NI-VISA also only supports the GPIB-ENET.
VISA SUPPORT FOR MULTIPLE GPIB-VXI CONTROLLERS
----------------------------------------------
NI-VISA supports multiple GPIB-VXI controllers in a single system. Because
the National Instruments GPIB-VXI controller ships with a primary address
of 1, NI-VISA automatically searches for any GPIB-VXI controllers at that
address.
If you have changed the primary address (for example, if you added a second
GPIB-VXI controller to your system, and set the address of the second
controller to 9), or if you have a GPIB-VXI controller from another vendor,
then you need to make changes to the visaconf.ini file which is located at
"/Library/Prefereneces/NIvisa/visaconf.ini".
If you are using a GPIB-VXI command module from another vendor, you also
need to obtain and install that vendor's VISA GPIB-VXI component.
INSTALLED FILES AND PATHS
-------------------------
There are three main locations where NI-VISA installs files.
The local "/Library/Frameworks" folder contains the VISA.framework folder.
This folder contains all needed headers, and supporting Passport libraries
that NI-VISA uses.
In the local "/Applications/National Instruments" folder, there is an
NIvisa folder. Included here are the user and programmer manuals, as well
as several groups of C examples using NI-VISA.
This NIvisa folder also includes a graphical utility named VisaConfig to
configure VISA options.
Finally, the "/Library/Preferences" folder contains an NIvisa folder with
INI files. These files are used for NI-VISA settings and status codes.
NI-VISA 3.0 IMPROVEMENTS AND BUG FIXES
--------------------------------------
When you open a VISA session to GPIB0::INTFC and immediately query the
attribute VI_ATTR_GPIB_SRQ_STATE, it previously returned the value
VI_STATE_UNASSERTED. It now returns VI_STATE_UNKNOWN because the SRQ line
cannot be monitored if the interface is not yet CIC. The correct state is
returned after calling viGpibSendIFC.
For a TCPIP INSTR resource, calling viTerminate did not work correctly.
For a TCPIP INSTR resource, calling viRead or viWrite with a large buffer
occasionally would return an error without transmitting the entire buffer.
For a TCPIP INSTR resource, opening and closing sessions to multiple host
addresses would cause NI-VISA to crash.
For a TCPIP INSTR resource, calling viLock with a timeout longer than the
I/O timeout for that session could cause NI-VISA to return VI_ERROR_TMO.
For a TCPIP SOCKET resource, viReadAsync was not implemented. Now it is.
For a Serial INSTR resource, viOpen will now open a port if the process
that had been using that port exited ungracefully (such as with Ctrl-C).
The previous behavior had been that viOpen would return VI_ERROR_RSRC_BUSY.
For a Serial INSTR resource, if you enabled RTS/CTS flow control and then
manually tried to set the state of the RTS line, some operating systems
would generate VI_ERROR_NSUP_ATTR while others would return VI_SUCCESS but
not actually modify the state of the line. Neither of these behaviours was
correct. Now NI-VISA will return VI_ERROR_INV_SETUP in this case on all
operating systems.
For a Serial INSTR resource, if a binding existed to a valid file/device
but that file/device was not really a serial port, then NI-VISA would
not close the handle. Repeated calls to viFindRsrc or viOpen would cause
the process to eventually run out of file handles. This has been fixed.
If you had a GPIB device at primary address 1 that generated a response to
*IDN? that was longer than 100 characters, viFindRsrc would occasionally
crash. This has been fixed.
viFindRsrc would crash on a complex expression with multiple "|" symbols.
This has been fixed.
viScanf %# modifier will now output the number of characters put into the
buffer excluding the terminating null character. This applies to the %#s,
%#t, %#T, and %#[] modifiers. NI-VISA treats the maximum array size
(specified on input) as the total buffer size including the terminating null
character.
Calling viFindRsrc repeatedly when logged in as root would eventually run
out of file descriptors. This has been fixed.
The attributes VI_ATTR_MANF_NAME and VI_ATTR_MODEL_NAME are now correctly
implemented for GPIB-VXI regardless of whether NI-VXI is installed.
The maximum simultaneous number of GPIB-VXI controllers supported by
NI-VISA has changed from 10 to 32.
For a Serial INSTR resource, the internal modem is now correctly detected.
For a Serial INSTR resource, during a viFindRsrc, when a previously found
serial port was detected again, the scan would not proceed to find any
new serial ports. This has been fixed.
For a Serial INSTR resource, a call to viOpen when the corresponding
serial port did not exist returned VI_ERROR_SYSTEM_ERROR. This return
value has been corrected to VI_ERROR_RSRC_NFOUND.
When calling viWaitOnEvent repeatedly with a timeout of 0 (immediate), some
interfaces and event types would still consume excessive CPU time. Now doing
this will yield the CPU regardless of the interface or event type.
For a GPIB resource, the operations viWriteAsync and viReadAsync did not
support true asynchronous operations. The data would still transmit and
receive, but NI-VISA did it synchronously. This has been fixed.
viFindRsrc would return VI_ERROR_INV_EXPR if the expression exceeded 255
characters. Now it will accept resource expressions of any length.
Calling viFindRsrc would always assert REN on each GPIB board after finding
devices. Now viFindRsrc will re-assert REN on each board only if there is
at least 1 open VISA INSTR session on that board.
For a TCPIP SOCKET resource, using viRead with termchar enabled was much
slower than reading the exact number of bytes. The performance of using
termchar with viRead is now much better than it was.
Calling viFindRsrc would return serial ports even if they were explicitly
disabled in the configuration file.
KNOWN ISSUES
------------
1. Callbacks for any event on a GPIB INTFC session might not work unless
you make a call to the VISA driver. For more information see the
Interrupt Callback Handler section in chapter 10 of the User Manual.