石鑫华视觉
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-VISA4.1Linux 美国国家仪器虚拟仪器软件架构VISA4.1Linux版下载
NI-VISA为使用GPIB、串行、PXI和其他类型仪器的用户提供支持。
NI-VISA是一个NI仪器驱动程序，是虚拟仪器软件架构(VISA) I/O标准的具体实现。虚拟仪器软件架构(VISA)这一标准用于配置和编程基于GPIB、VXI、PXI、串口(RS232/485)、以太网/LXI和/或USB接口的仪器系统以及故障分析。NI-VISA包括实用程序、底层控制功能和范例，可帮助您快速创建应用程序。
百度网盘下载：
NI-VISA4.1：
链接：请注册视觉论坛会员登陆后购买附件下载查看
提取码：请购买附件下载查看
NI官方下载地址（可能无效或无法下载完成）：
NI-VISA4.1：
请购买附件下载查看
NI-VISA4.1Linux 美国国家仪器虚拟仪器软件架构VISA4.1Linux版下载
http://pcmv.cn/thread-22990-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
National Instruments NI-VISA(TM) Software for Linux x86. Version 4.1.
Copyright(c) 1995, 2007 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
---------------------
System Requirements
Installation From the Internet
Installation FAQs
LabWindows(TM)/CVI Run-Time Engine
VISA Support for Multiple GPIB-VXI Controllers
VISA Probes for LabVIEW 7.x
USB Issues on Linux
NI-VISA 4.1 Improvements and Bug Fixes
NI-VISA 4.0 Improvements and Bug Fixes
NI-VISA 3.5 Improvements and Bug Fixes
NI-VISA 3.4 Improvements and Bug Fixes
NI-VISA 3.3 Improvements and Bug Fixes
NI-VISA 3.2 Improvements and Bug Fixes
NI-VISA 3.1 Improvements and Bug Fixes
NI-VISA 3.0 Improvements and Bug Fixes
Credits
Known Issues
SYSTEM REQUIREMENTS
-------------------
NI-VISA 4.1 for Linux software for the Intel x86 architecture requires
one of the following distributions:
Mandriva Linux 2006
Mandriva Linux 2007
SUSE Linux 10.1
SUSE Linux 10.2
Red Hat Enterprise Linux WS 3
Red Hat Enterprise Linux WS 4
You must use the provided INSTALL script to install NI-VISA 4.1. Manual
installation using rpm is not supported.
At the time of release, National Instruments supports NI-VISA 4.1 only
on the above listed distributions and versions. For information on
NI-VISA compatibility on other versions of these distributions,
including earlier versions of the distributions listed above, refer
to KB 3XAAMQV4 on ni.com, "What Linux distributions do National
Instruments' drivers and software support?".
After installation, you may need to reboot your machine before attempting
to use NI-VISA 4.1. The installer will prompt you to reboot if it is
required.
Refer to ni.com/linux for the most recent information about Linux
support at National Instruments.
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.
INSTALLATION FAQS
-----------------
Q1: What action needs to be taken if I upgrade/change my kernel?
A1: Some action is required to make the existing NI-VISA installation
work for the new kernel. After upgrading your kernel, run
updateNIDrivers utility as root. The utility is located in
/usr/local/bin. Be sure to have sources for your new kernel properly
installed on your system before running the utility. The utility
rebuilds the driver using the new kernel sources and copies it to
the appropriate location for the new kernel. For the changes
to take place, you will be asked to reboot your machine after the
utility completes.
Q2: During installation I get a message similar to the following one:
"Kernel source does not appear to be configured for the running kernel.
Configuration of kernel source is required to continue installation."
I do have kernel sources installed; is there anything else that needs to
be done?
A2: This problem has been seen on SUSE LINUX Professional 9.1 running the 2.6.5
kernel or newer versions of SUSE LINUX Professional. However, it is possible
that other distributions will require similar steps to resolve this problem.
On SUSE LINUX Professional complete the following steps:
1. Ensure you have installed kernel-source and kernel-syms packages
corresponding to the version of the currently running kernel. The version
of the currently running kernel can be determined by issuing the command
`uname -r`.
2. Change the directory to the /usr/src/linux-<version> directory, where
<version> corresponds to the currently running kernel version.
3. Run "make cloneconfig" as root to configure the sources for the
currently running kernel.
4. Run "make modules_prepare" as root to prepare the headers for
compilation.
5. THIS STEP IS STRICTLY OPTIONAL. Completing this step removes the
warning:
WARNING: Symbol version dump /usr/src/linux/Module.symvers is missing,
modules will have CONFIG_MODVERSIONS disabled.
Run "make modules" as root to compile all modules and generate
Module.symvers; this step may take 30 minutes or more to complete.
6. Run the INSTALL script for the NI-VISA software for Linux from this
directory.
LABWINDOWS/CVI RUN-TIME ENGINE
------------------------------
The INSTALL script 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.0.1 or later to be installed. When you
install this utility, the INSTALL script also installs the LabWindows/CVI
Run-Time Engine if it is not already present.
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 app's path is <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 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.
If you have a GPIB device at primary address 1 and that device does not
recognize "*IDN?", you should disable the GPIB-VXI auto-detect feature in
visaconf on the Settings tab.
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.
The NI-VISA installer will install the probes for LabVIEW 7.1. However,
if you are using LabVIEW 7.0, you can download and install them yourself.
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.
USB ISSUES ON LINUX
-------------------
NI-VISA relies on a Linux kernel feature for its USB support. This feature
is called "usbfs", and on older Linux kernels was referred to as "usbdevfs".
For NI-VISA to support USB devices, this feature must be present and
mounted (like a virtual filesystem). This is supported in most major Linux
distributions such as Red Hat, SUSE, and Mandrake. You may use the "mount"
command to display what filesystems are currently mounted to see if your
system currently supports this feature.
Also, the VISA user must have write accress to the file that represents
the USB device, which is typically somewhere in a subdirectory within
"/proc/bus/usb". If this is not the case, the USB device is not
accessible by VISA (it will not be found using viFindRsrc and viOpen will
fail). The default configuration on most systems is that the 'root' user
has write access; however, no other user has this access.
There are a number of options that you can take to provide a non-root
user access to a USB device.
1) Use the hotplug package. This package is installed by default on most
distributions including Red Hat, SUSE, and Mandrake. The hotplug package
allows the user to run scripts for a specific USB device based on
characteristics such as Vendor ID (VID) and Product ID (PID). If the
hotplug package exists, the NI-VISA Installer by default will install
scripts to give all users write access to all USB TMC devices and a
framework for USB RAW devices. To add write permissions for a specific
USB RAW device, simply run the included script:
"<VXIPNPPATH>/linux/NIvisa/USB/AddUsbRawPermissions.sh".
For more information on the hotplug package, please visit:
http://linux-hotplug.sourceforge.net
2) "usbfs" (formerly known as "usbdevfs") may be mounted with the option
"devmode=0666". This gives all users read and write access to all USB
devices.
3) The 'root' user may add write permissions to the file that represents
the USB device which is typically somehere in a subdirectory within
"/proc/bus/usb". Unfortunately, these permissions will be lost if the
device is unplugged and then plugged back in. Because of this, this
approach is not recommended.
NI-VISA 4.1 IMPROVEMENTS AND BUG FIXES
--------------------------------------
Added desktop menu shortcuts for KDE and Gnome. These will not work on
Red Hat Enterprise Linux WS 3 due to the older desktop menu technology
that it incorporates.
In visaconf, added options for 'Show all devices accessible to VISA' and
'Show peek/poke calls in NI Spy'.
In the NI-VISA Driver Wizard, it would not install the INF files for
users without root access and not display any errors. Now it warns that
root access is required to access the installation feature.
Added PXI and TCP/IP 'C' examples.
In visaconf, IP address entry was not validated. This is fixed.
For GPIB INSTR resources, VISA would set only the GPIB I/O time out and
not the GPIB serial poll time out. The serial poll time out is used
in 'viReadSTB'. This is fixed.
For GPIB INSTR resources, only one call to 'viWaitOnEvent' could be
outstanding at any given time. This is fixed.
The NI-VISA Driver Wizard now has an option for PXI Express devices that
provide a way to read the slot number using a sequence of register-level
accesses.
Calling 'viFindRsrc' with a non-empty, all-whitespace expression string
would cause VISA to crash. This is fixed.
Calling 'viFindRsrc' with an expression string that contained two sets of
double quotes would not work. This is fixed.
For USB INSTR resources, 'viReadSTB' could fail with a time out error on
some devices that are not completely compliant with the USB TMC
specification. This is fixed.
In LabVIEW, if the I/O Filtering option is set to URL format, local
resources were not included in the I/O control list. This is fixed.
NI-VISA 4.0 IMPROVEMENTS AND BUG FIXES
--------------------------------------
Added support for 64-bit data transfers in register-based operations, to
support the VISA 4.0 specification.
On some Linux desktop environments, visaconf and NIvisaic would not respond
to keyboard input while 'Num Lock' is on. This is fixed.
The I/O control in LabVIEW 8.0 would not always honor the parameters you
specified in the filtering dialog, depending on the order in which you made
changes. This is fixed.
viScanf would crash when reading indefinite-length block data. This is
fixed.
For ENET-Serial INSTR sessions, framing errors were occasionally not
detected. This is fixed.
Improved performance of NI Spy.
For TCP/IP SOCKET sessions, re-enabling the termination character between
read operations would incorrectly flush the internal buffer. This is fixed.
For TCP/IP SOCKET sessions, reading less than the entire amount of data that
the device sent would not work correctly for asynchronous read operations.
This is fixed.
The new PXI/PCI Express attributes are now implemented.
NI-VISA 3.5 IMPROVEMENTS AND BUG FIXES
--------------------------------------
For TCP/IP INSTR sessions, viWrite would fail if the transfer size was over
8KB. This is fixed.
Significantly optimized PCI interrupts and block moves.
Significantly optimized calls to viFindRsrc and viOpen for all interface
types.
In some cases, floating point formatted I/O would hang. This is fixed.
For Serial INSTR sessions, a call to viSetBuf, which did not modify the
buffer size, still returned VI_SUCCESS. viSetBuf now returns a warning
indicating the operation is not supported on the current platform.
NI-VISA 3.4 IMPROVEMENTS AND BUG FIXES
--------------------------------------
Added support for PXI system identification, trigger routing, and
reservation. PXI-1006 trigger routing is not supported.
Type "man nipxiconfig" for more information.
The VISA Driver Development Wizard is now supported on Linux. It is
located in /usr/local/vxipnp/linux/NIvisa. Previously, the wizard was
supported on Windows only.
For PXI INSTR sessions, non National Instruments PXI/PCI devices would not
be correctly detected and hence communication to them was not possible.
This is fixed.
Performing asynchronous I/O to a remote VISA resource would return an
incorrect transfer count and/or data. This is fixed.
For USB RAW sessions, communication with non-zero control endpoints is now
supported with the use of VI_ATTR_USB_CTRL_PIPE.
For USB RAW sessions, the default setting for VI_ATTR_USB_END_IN has been
changed from VI_USB_END_SHORT to VI_USB_END_SHORT_OR_COUNT.
For USB RAW sessions, viReadAsync would fail if the transfer size was over
8KB and not a multiple of the maximum packet size of the endpoint.
This is fixed.
For USB RAW sessions, changing the USB Alternate Setting on a USB
Interface number other than 0 would fail. This is fixed.
For TCP/IP SOCKET sessions, VI_ATTR_SUPPRESS_END_EN set to VI_TRUE did not
work in all cases. This is fixed. The default attribute setting for
VI_ATTR_SUPPRESS_END_EN on TCP/IP SOCKET sessions is now VI_TRUE.
For PXI INSTR sessions, when enabling for VI_EVENT_PXI_INTR using VI_QUEUE,
viDiscardEvents did not work properly. This is fixed.
For GPIB INSTR sessions, when using a GPIB-USB controller, if you unplug
and replug the GPIB-USB cable, you would have to exit and restart your
application to communicate with it again. This is fixed.
NI-VISA 3.3 IMPROVEMENTS AND BUG FIXES
--------------------------------------
The PXI/PCI INSTR Resource is now supported on Linux. PXI specific
functionality is not supported at this time. You must generate an INF file
for your PXI/PCI device with the VISA Driver Development Wizard on Windows
using NI-VISA 3.3 or higher. INF files generated with older versions of
NI-VISA are not supported on Linux. You can find installation instructions
in the generated file. This is a new feature.
For USB RAW sessions, now interrupt-out endpoints may be used for viWrite.
For USB RAW sessions, viReadAsync is now implemented.
Opening a VISA session to a resource and then exiting the application
without closing either the VISA session or the Resource Manager
could crash the application. This is fixed.
viFindRsrc could be very slow if the Serial Passport is enabled.
This is fixed.
viFindRsrc would crash when given long strings that use remote NI-VISA.
This is fixed.
Calling viMoveAsync on a remote VISA session would return an error.
This is fixed.
For Serial INSTR sessions, viClear previously would flush (discard) the I/O
buffers and then send a break. According to the VISA spec, VISA must flush
(discard) the I/O output buffer, send a break, and then flush (discard) the
I/O input buffer. This is fixed.
viScanf and variants did not support the "%u" identifier for arrays.
This is fixed.
viPrintf and variants did not support the "%zy" and "%Zy" identifiers for
floating point data. This is fixed.
viPrintf and variants previously generated "NaN", "+Inf", and "-Inf". It
now generates "NAN", "INF", and "NINF", respectively.
viScanf and variants did not correctly interpret the input values "NAN",
"INF", and "NINF". This is fixed.
The function viUsbControlIn would report an incorrect return count when it
read fewer bytes than requested. This is fixed.
NI-VISA 3.2 IMPROVEMENTS AND BUG FIXES
--------------------------------------
Added complete support for USB (both RAW and INSTR).
Added a new UNINSTALL script for Linux. This UNINSTALL script is installed
in the /usr/local/vxipnp/linux/NIvisa directory.
Calling viPrintf on a remote VISA session would return VI_ERROR_IO instead
of VI_ERROR_RSRC_LOCKED when the remote resource was locked. This is fixed.
The VISA Interactive Control utility (NIvisaic) now displays an error message
box when viFindRsrc returns an error.
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.
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.
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.
The GPIB INSTR and GPIB INTFC resources depend on the presence of an NI-488
driver installed on the system. For PCI-GPIB products on Linux, NI-VISA
requires NI-488.2 for Linux version 2.3 or higher. For GPIB ethernet
products on Linux, NI-VISA requires NI-488.2 for Linux version 2.2 or higher.
For USB resources, there are issues using interrupt-in endpoints. These
issues vary depending on the version of the Linux kernel and the USB
controller hardware that is on the system. On 2.4.x kernels, only one
packet may be requested at a time. Hence, if the value for the attribute
VI_ATTR_USB_MAX_INTR_SIZE exceeds the maximum packet size of the current
interrupt-in endpoint, interrupts will not be received. Also, depending
on the chipset of the USB controller hardware, it is possible for a
kernel panic (system crash) to occur while attempting an interrupt-in
transfer. These issues have been fixed in 2.6.x kernels. However, in some
2.6.x kernels, interrupt-in transfers will not work on EHCI (USB 2.0)
controllers with USB 2.0 devices.
In SUSE Linux 10.1, when using USB TMC (Test & Measurement Class)
Instruments, they may not be accessible by a user other than 'root' if the
class of the instrument is defined at the interface level. If this is the
case, access may be granted by using the "AddUsbRawPermissions.sh" script.
See the "USB ISSUES ON LINUX" section for details.