石鑫华视觉
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.1 Linux 美国国家仪器虚拟仪器软件架构VISA3.1 Linux版下载
NI-VISA为使用GPIB、串行、PXI和其他类型仪器的用户提供支持。
NI-VISA是一个NI仪器驱动程序，是虚拟仪器软件架构(VISA) I/O标准的具体实现。虚拟仪器软件架构(VISA)这一标准用于配置和编程基于GPIB、VXI、PXI、串口(RS232/485)、以太网/LXI和/或USB接口的仪器系统以及故障分析。NI-VISA包括实用程序、底层控制功能和范例，可帮助您快速创建应用程序。
百度网盘下载：
NI-VISA3.1：
链接：请注册视觉论坛会员登陆后购买附件下载查看
提取码：请购买附件下载查看
NI官方下载地址（可能无效或无法下载完成）：
NI-VISA3.1：
请购买附件下载查看
NI-VISA3.1 Linux 美国国家仪器虚拟仪器软件架构VISA3.1 Linux版下载
http://pcmv.cn/thread-22968-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
National Instruments NI-VISA(TM) Software for Linux x86. Version 3.1.
Copyright(c) 1995, 2004 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
---------------------
Installation From the Internet
LabWindows(TM)/CVI Run-Time Engine
Support for new VISA Features
VISA Support for Multiple GPIB-VXI Controllers
Using viPeekXX/viPokeXX Macros
VISA Probes for LabVIEW 7.x
NI-VISA 2.5 Improvements and Bug Fixes
NI-VISA 2.6 Improvements and Bug Fixes
NI-VISA 3.0 Improvements and Bug Fixes
NI-VISA 3.1 Improvements and Bug Fixes
Credits
Known Issues
INSTALLATION FROM THE INTERNET
------------------------------
You should be logged in as 'root' to perform this installation.
1) Download the installation script file "INSTALL" and the compressed tar
file "NICVISA_.TZ" from the ftp site into a temporary directory.
2) Type ./INSTALL to execute the install script, and follow the instructions
as prompted.
3) Add the following environment variables to your shell setup file as shown
in the following example for csh. The following commands assume that
you installed NI-VISA into /usr/local/vxipnp:
setenv VXIPNPPATH /usr/local/vxipnp
setenv LD_LIBRARY_PATH /usr/local/vxipnp/linux/bin
Note: If your setup file already contains the LD_LIBRARY_PATH environment
variable, you need to append /usr/local/vxipnp/linux/bin to the end of
the statement. The required commands may vary from those shown in the
previous section if you are not using csh.
LABWINDOWS/CVI RUN-TIME ENGINE
------------------------------
The Setup program now automatically installs the LabWindows/CVI Run-Time
Engine when necessary. The NI-VISA interactive utility, VISAIC, requires the
LabWindows/CVI Run-Time Engine 5.01 or later to be installed. When you
install this utility, Setup also installs the LabWindows/CVI Run-Time Engine
if it is not already present.
SUPPORT FOR NEW VISA FEATURES
-----------------------------
The NI-VISA Help (in HTML format) describes the new features of NI-VISA 3.1,
but they are briefly listed here for your convenience. The help is installed
in "<VXIPNPPATH>/linux/NIvisa/Manuals".
Starting with NI-VISA 2.6, we now support remote NI-VISA access. Any machine
with the NI-VISA server can export its resources to other NI-VISA clients.
Client and server settings are configured in visaconf. 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.
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.
The best way to explore the new features is to use the VISA Interactive
Control to open sessions to the new resource types and look at the available
operations, events, and attributes. VISAIC also has a new feature to help
you find specific resources. Type a search expression and press <Tab>, or
click the drop-down arrow and select "Create Query" to let VISAIC assist you
in fine-tuning your expression.
The NI-VISA User Manual has been updated to include a new section on formatted
I/O, including many common instrument driver examples. There is also a new
chapter with information about each supported hardware interface type. These
topics are covered in chapters 5 and 9, respectively.
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 use the VISA configuration utility so NI-VISA can
find it. This application is located at <VXIPNPPATH>/linux/NIvisa/visaconf.
While in the Resource Editor, click the 'Add' button to add a new resource.
Specify a valid resource name for the new controller, such as
GPIB-VXI2::0::INSTR. You will then be prompted for the GPIB board number and
the GPIB-VXI's primary and secondary addresses. For most users, the only
number that will change (from the default selections) is the primary address
(for the above example, you would change it to 9). Click 'OK' to add this
new resource, and then select the File|Save menu option to save this
information to the NI-VISA database.
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.
USING viPeekXX/viPokeXX MACROS
------------------------------
Users who want to use the viPeekXX/viPokeXX macros for platforms on which the
macros are available must define a macro called NIVISA_PEEKPOKE before
including "visa.h". Please note that the macros are currently available
only on the following platforms:
- Win32 (All C compilers)
- Solaris (LabWindows/CVI only)
If you have used these macros with a version of NI-VISA prior to 2.0, your
application will continue to run, but the peek/poke performance will decrease.
You should relink with the libraries supplied with this installation to regain
the prior peek/poke performance.
VISA PROBES FOR LABVIEW 7.x
---------------------------
The VISA probes for LabVIEW 7.x greatly extend the amount of relevant
information displayed when using LabVIEW probes on VISA refnums. They are used
automatically by LabVIEW in place of the generic probe when they are
installed.
To install them, download them from "ftp.ni.com/support/visa/labview/probes/"
and copy them into "<LABVIEW_DIR>/vi.lib/_probes/default/VISA/" where
<LABVIEW_DIR> is the installation directory of LabVIEW.
NI-VISA 2.5 IMPROVEMENTS AND BUG FIXES
--------------------------------------
GPIB and Serial performance have been improved over Version 2.01.
If you are using the GPIB-ENET controller, the previous version of NI-VISA
would take a minute or more to time out if a GPIB-ENET controller were not
connected or powered on. The timeout is now much shorter.
This version of NI-VISA incorporates general bug fixes and improvements for
GPIB-VXI. The NI-VISA code instrument will now load properly in configurations
where it previously failed.
If a GPIB-VXI chassis is reset while an application has VISA loaded, the
GPIB-VXI would previously become accessible only as GPIB but not GPIB-VXI.
This release of NI-VISA will now properly re-detect the GPIB-VXI.
Fixed bug with the GPIB-VXI and hardware triggers.
This version of NI-VISA incorporates general bug fixes and improvements for
formatted I/O, especially with very large buffers and with the following
modifiers: "%b", ",", "#", "!ob", "!ol", and "%[".
The documentation for viPrintf and viFlush better describes when formatted
I/O buffers are sent. The documentation for viScanf better describes the ","
and "#" modifiers.
Fixed bug with the Serial End Last Bit mode for reads and writes.
NI-VISA 2.6 IMPROVEMENTS AND BUG FIXES
--------------------------------------
Fixed bug with enabling the exception event on GPIB-VXI.
viScanf %f modifier will now properly scan numbers bigger than 2^31-1.
viGpibPassControl now returns an error if the primary and/or secondary address
is invalid.
In VXI, mapping a trigger line already mapped produced VI_ERROR_LINE_IN_USE
(0xBFFF0042), instead of VI_SUCCESS_TRIG_MAPPED (0x3FFF007E). This now
returns the expected status code.
In VXI and GPIB-VXI, using viMoveInXX and viMoveOutXX with a negative
value for the length parameter would occasionally cause the system to reboot.
This now returns the error code VI_ERROR_INV_LENGTH (0xBFFF0083) instead.
viReadToFile now writes the correct data to the file.
For TCP/IP SOCKET and INSTR resources, the openTimeout specified in viOpen
is now used as the network timeout during the connection sequence. The
default openTimeout, if not specified, is 2 seconds (2000 milliseconds).
For TCP/IP INSTR resources, trying to do a viRead or viReadAsync on a buffer
with a size larger than a few kilobytes, would either return an error or
occasionally crash. This has been fixed.
viFindRsrc would previously reject certain valid expressions and accept
certain invalid expressions, usually involving spaces. This has been fixed.
The NI-VISA driver would not initialize properly on libc version 5.4.44.
This has been fixed.
If an application called fork, the NI-VISA driver didn't initialize
properly in the child process. Exiting either the child or parent process
caused the other's VISA calls to stop working.
In Serial, we now support baud rates higher than 38400. Specifically,
the values 57600, 115200, 230400, and 460800 are now valid as long as the
system driver allows them.
In Serial, if data arrives at the same time as viTerminate is called or a
timeout occurs, the data now gets read. If this satisfies the read request,
then the read operation returns a successful status.
Enabling VI_EVENT_SERVICE_REQ for VI_HNDLR with a GPIB-ENET controller
would cause an application to hang if an SRQ event arrived while I/O was
in progress. This has been fixed.
Multiple VISA processes using GPIB could not perform I/O simultaneously
even if the I/O was to different controller cards. This has been fixed.
Multiple I/O requests to the same GPIB controller will still be handled
sequentially due to the nature of GPIB.
Calling viOpen with access mode 1 (exclusive lock) did not work as expected
on GPIB interface sessions. This has been fixed.
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, NI-VISA now supports the baud rates 50, 75,
134, 200, 1800, and 576000. This list is now identical to the OS list.
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.
Once viScanf returned VI_ERROR_TMO, it would no longer work properly on
that session.
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.
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.
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.
NI-VISA 3.1 IMPROVEMENTS AND BUG FIXES
--------------------------------------
Reading data from a Serial port was slow. The performance has improved.
Using the Serial Break VI from LabVIEW did not work with remote NI-VISA.
This has been fixed.
For a Serial INSTR resource, if a parity or framing error occurred, NI-VISA
would not return the correct error condition. This has been fixed.
The hostname "localhost" or the IP address "127.0.0.1" did not work properly
with remote NI-VISA. Only the DHCP name or network IP address would work.
This has been fixed.
Calling viEnableEvent on a remote VISA session would leak memory in the
server. This has been fixed.
The remote NI-VISA server did not properly validate a hostname with an
underscore. This has been fixed.
Calling viOpen on a remote NI-VISA resource did not honor the openTimeout
parameter. This has been fixed.
Calling viClose on an ethernet resource would leak a socket handle. This
has been fixed.
The global attributes on a GPIB INTFC resource were not properly shared
across sessions. This has been fixed.
Using the system call "fork" on a process with VISA loaded would sometimes
cause the forked process to hang. This has been fixed.
CREDITS
-------
This product includes components that use the socket++ library. The library
is Copyright(C) 1992-1995 Greg Lavender (University of Texas) and
Gnanasekaran Swaminathan (University of Virginia). All rights reserved.
KNOWN ISSUES
------------
If your application crashes or terminates abnormally, NI-VISA cannot always
clean up properly. In order to run another VISA application, you should
first run the application <VXIPNPPATH>/linux/NIvisa/viclean. This deletes
any remaining shared memory segments and system semaphores.
If you upgrade from NI-VISA 2.5 using the Red Hat Package Manager directly,
the uninstall script for the old NI-VISA will remove the symbolic links for
libvisa.so, libcvi.so, NIvisaic, and visaconf from /usr/lib and /usr/bin.
To get around this problem, either use the new INSTALL script or uninstall
the previous 'nivisa' and 'nicvirte' packages before installing those
included in this distribution.
If you are experiencing problems using the TCPIP SOCKET, TCPIP INSTR, remote
NI-VISA server, or client in Red Hat Linux version 7.3, you might have
encountered known issues with TCPIP in kernel version 2.4.18-3. Please
upgrade to kernel version 2.4.18-5 or later. The .rpm file for this update
may be found at:
ftp://speakeasy.rpmfind.net/linux/redhat/updates/7.3/en/os
The GPIB INSTR and GPIB INTFC resources depend on the presence of an NI-488
driver installed on the system. For PCI-GPIB and AT-GPIB/TNT products on
Linux, currently only a Beta version of NI-488 is available. For GPIB
ethernet products on Linux, NI-VISA requires NI-488.2 for Linux version 2.2
or higher.