石鑫华视觉
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 FlexRIO 17.0 Driver Linux32/64Eng NI-FlexRIO设备驱动程序17.0
FlexRIO
FlexRIO驱动程序为使用NI FlexRIO设备的客户提供支持。
FlexRIO驱动是用于支持FlexRIO设备的NI仪器驱动。该驱动为基于集成I/O和模块化I/O的FlexRIO设备提供硬件支持，包括用于FlexRIO的PXI FPGA模块以及FlexRIO的各种适配器模块。对于基于集成I/O的FlexRIO设备，FlexRIO驱动还提供用于数据流传输的API以及NI-TClk同步支持。
Linux32/64Eng
17.0.0
文件大小: 54034432 字节 (51.53 MB)
修改日期: 2017-06-22 22:50
MD5: 8bc4cdc8771b18107280eaa1df8d936f（官方正确）
SHA1: 0c07f305f97eecb1b6ce59f40c80040f5871af17
SHA256: 93df0e252adc638a89f4e6bcd736aaef65a9d97da555bce1831e6f3cc365dd11
CRC32: 903d19e3
百度网盘与NI官方下载地址：
NI FlexRIO 17.0 Driver Linux32/64Eng NI-FlexRIO设备驱动程序17.0
http://pcmv.cn/thread-26097-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
FlexRIO for Linux, Version 17.0.0
-------------------------------------------------------------------------------
This file contains late-breaking news about FlexRIO and supersedes any
information found in other documentation included in the distribution. Refer to
ni.com/linux for the most recent information about Linux support from National
Instruments.
-------------------------------------------------------------------------------
-----------------
Table of Contents
-----------------
- FlexRIO for Linux
- Differences from the Windows Driver
- System Requirements
- Dropped Support for 32-bit Linux Distributions
- Installing FlexRIO for Linux
- Using the FlexRIO Driver and FPGA Interface C API
- Using the NI-RIO Server
- Using RIO Aliases
- Uninstalling FlexRIO for Linux
- Running Linux on PXI Controllers
- Documentation and Help
- Bug Fixes
- FAQ
- Legal Information
----------------------
FlexRIO for Linux
----------------------
FlexRIO for Linux contains the FlexRIO drivers, the FlexRIO shared library,
the FPGA Interface C API runtime library, and all supporting
runtime libraries and services necessary to interact with a FlexRIO device
from a system running Linux.
-----------------------------------
Differences from the Windows Driver
-----------------------------------
The following FlexRIO driver features supported for Windows are not
supported for Linux:
* Development of LabVIEW FPGA VIs and bitfiles (*.lvbitx)
* Development of LabVIEW FPGA Interface host VIs
You must compile a bitfile using LabVIEW FPGA on a Windows machine. Refer to
the "Using the FlexRIO Driver and FPGA Interface C API" section for more
information.
-------------------
System Requirements
-------------------
FlexRIO for Linux requires one of the following distributions:
* Red Hat Enterprise Linux 6.x x86_64
* Red Hat Enterprise Linux 7.x x86_64
* Scientific Linux 6.x x86_64
* openSUSE Leap 42.1 x86_64
* openSUSE Leap 42.2 x86_64
* CentOS 7 x86_64
FlexRIO 17.0 no longer officially supports x86 systems, and it is important to
note that on x86 systems with memory or memory-mapped devices beyond the first
4 GB of physical address space, FlexRIO will fail to load altogether. This
limitation does not apply to x86_64 systems. To ensure the successful operation
of National Instruments FlexRIO products on x86 systems, you must use a kernel
configuration that recognizes only up to 4 GB of physical memory. Refer to the
documentation of your Linux distribution to determine how to configure the
distribution installer to select an appropriate kernel. Alternatively, you can
dynamically restrict the addressable range of the kernel to a specific limit by
passing "mem=<size>" to the kernel at boot time. For example, to restrict the
kernel to 3 GB of addressable physical space, specify "mem=3072M".
For more information about Linux versions and distributions supported by
NI, refer to ni.com/linux.
In order to use FlexRIO on Linux, you need a Windows system to develop your
LabVIEW FPGA application. You must compile a bitfile, generate headers with the
FPGA Interface C API Generator, and then move the application to your Linux
system. Refer to the "Using the FlexRIO Driver and FPGA Interface C API"
section for more information about developing LabVIEW FPGA applications
with Windows systems.
---------------------------------------------------------------------
Dropped Support for 32-bit Linux distributions
---------------------------------------------------------------------
FlexRIO for Linux has dropped support for Intel 32-bit
versions of Linux distributions as of July 1, 2016. Versions of
FlexRIO for Linux that ship after July 1, 2016 may install and execute on
Intel 32-bit distributions, but official support is not provided.
-------------------------------
Installing FlexRIO for Linux
-------------------------------
Note: To ensure that the installation completes successfully, you must
uninstall any previous version of FlexRIO before you install the
current version. For information about uninstalling an old version of
FlexRIO, refer to the readme for that version.
To install FlexRIO for Linux, run the INSTALL script from this directory as
root. The INSTALL script ensures that all requirements are met before
installing the FlexRIO software. The script then uses RPM to install the
content of the FlexRIO packages in /usr/local/natinst/. The script also
creates links in /usr/local/lib/ to libraries in /usr/local/natinst/.
Missing dependencies will cause the installer to fail. The most commonly
missing dependencies are GCC and kernel sources. For distributions managed with
yum, the following command can install those dependencies:
yum install gcc kernel-devel-$(uname -r)
For other distributions, refer to the documentation for your distribution.
During installation on openSUSE, you may see the following error message:
"Kernel source does not appear to be configured for the running kernel.
Configuration of kernel source is required to continue installation." This
message can occur even if you have installed the correct kernel sources, if the
sources require configuration. This problem may affect other distributions in
addition to openSUSE.
Complete the following steps to configure your kernel sources on openSUSE:
1. Install the kernel-source package corresponding to the version of the kernel
you are using. For versions of openSUSE earlier than 11.3, you also need to
install the corresponding kernel-syms package. You can determine which
version of the kernel is running with the command "uname -r".
2. Change the directory to /usr/src/linux-<version>, where <version> is the
version number of the kernel.
3. Run "zcat /boot/symvers-<version>.gz > Module.symvers" as root to prepare
modversion support.
4. Run "make cloneconfig" as root to configure the sources for the kernel.
5. Run "make modules_prepare" as root to prepare the headers for compilation.
After installing all missing dependencies, run the INSTALL script again.
Once the INSTALL script completes successfully, reboot the system to ensure
that all the drivers are updated.
After installation, the FlexRIO drivers are loaded by default at boot time
if there is a FlexRIO device in the system.
------------------------------------------------
Using the FlexRIO Driver and FPGA Interface C API
------------------------------------------------
You must begin development on a computer running Windows.
1. Use LabVIEW FPGA to develop and build an FPGA VI that runs on a
FlexRIO device.
2. Use the FPGA Interface C API Generator to create the C source files
for your application.
Go to ni.com/info and enter the Info Code fpgainterfacecapi to get the
latest version of the FPGA Interface C API Generator.
3. Copy the generated files to the Linux machine to begin development of
C/C++ code for your application.
For information about using the FPGA Interface C API, go to ni.com/info and
enter the Info Code fpgainterfacecapihelp.
To find the FlexRIO device you are using in your application, use the command
"lsni -v" to list information on all National Instruments devices in the
system.
If your application requires triggering, you can reserve triggers statically
with the NI PXI Config utility, or dynamically with NI-VISA. For information
about using these PXI systems in Linux, go to ni.com/info and enter
the Info Code linuxconfigpxi. For information about PXI triggering, go to
ni.com/info and enter the Info Code pxitrigger. This version of FlexRIO for
Linux supports triggering only on x86 versions of Linux.
-----------------------
Using the NI-RIO Server
-----------------------
Complete the following steps to remotely access FlexRIO devices on your Linux
system from another system with FlexRIO installed:
1. Select a port for the NI-RIO server to use. The default port is 11296.
2. Configure the system firewall to allow TCP connections through the
selected port.
3. Edit the nirio.ini file at /etc/natinst/nirio/ to specify both the selected
port and the users allowed to access the device. The following example
specifies the default port, 11296, and allows only users at the IP address
10.0.29.54 to have access to the device:
[General]
RpcServerPort=11296
DeviceAccess="-*;+10.0.29.54"
4. Execute NiRioRpcServer at /usr/local/natinst/nirio/bin/.
Note that the DeviceAccess variable is defined by a semicolon-delimited list
of qualifiers, IP addresses, DNS hostnames, and wildcard patterns.
To determine whether a remote system has access to FlexRIO devices on this
system, the RIO server searches for an entry in the list that matches the
remote system. The "+" qualifier allows access, and the "-" qualifier
denies access. The RIO server uses the last matching entry in the list to
determine whether to allow or deny access. If no entry matches the
remote system, the RIO server denies access.
For example, if the list is empty, all remote systems are denied access.
The first argument in the example above explicitly restricts remote access
from any IP address. The second argument allows access from the
IP address 10.0.29.54.
To allow access from multiple IP addresses, define DeviceAccess as follows:
DeviceAccess="+10.0.29.54;+10.0.35.42"
To allow access from any IP address on the network, define Device Access as
follows:
DeviceAccess="+*"
-----------------
Using RIO Aliases
-----------------
To create RIO aliases to local or remote FlexRIO devices, you must edit
the nirio.ini file at /var/local/natinst/nirio/etc/. Add an [Aliases] section
if one does not already exist. For each alias, there must be a separate line
in the [Aliases] section that follows the <alias>="<resource>" format.
The following example specifies both a local and remote alias:
[Aliases]
foo="RIO0"
bar="rio://mycrio/RIO0"
Note that aliases must contain only alphanumerics, '-', and '_'.
Next, change the following version lines to 0:
[General]
MajorVersion=0
MinorVersion=0
This triggers nirio.ini to be updated the next time it is used.
After running "lsni", note that the [Aliases] section has been replaced
by a new section for each new alias.
-----------------------------
Uninstalling FlexRIO for Linux
-----------------------------
To uninstall the driver and its dependencies, run the UNINSTALL script.
--------------------------------
Running Linux on PXI Controllers
--------------------------------
FlexRIO for Linux works with all PXI and PXI Express controllers and chassis.
However, to use PXI Express features, you must install the PXI Platform
Services driver 2.6 (not included with this installer), use an x86 version of
Linux, and use a PXI Express controller and chassis.
PXI Express features:
* NI-P2P streaming
* Slot and chassis identification
* Trigger bus number identification (for trigger reservation)
Supported PXI Express Embedded controllers:
* PXIe-8101
* PXIe-8108
Supported PXI Express chassis:
* PXIe-1062Q
* PXIe-1065
* PXIe-1075
* PXIe-1082
To install the PXI Platform Services driver, go to ni.com/info and enter the
Info Code linuxpxidriver. For installation and configuration notes specific to
each controller, go to ni.com/info and enter the Info Code linuxpxiembedded.
----------------------
Documentation and Help
----------------------
Use a web browser to view the FlexRIO help and hardware documentation
at ni.com/manuals.
---------
Bug Fixes
---------
Added support for downloading to the FPGA on Linux desktop for
PXIe-797xR FPGA modules. This feature addresses the download error
previously seen in KB 6QGFHPSL.
---
FAQ
---
Q1: I am not using one of the distributions listed as supported above. Will
FlexRIO still work?
A1: The distributions above have been tested and verfied by National
Instruments. Other distributions may work, but you should test extensively
before deploying a system using such a configuration. For information about
which Linux distributions National Instruments supports, go to ni.com/info
and enter the Info Code nilinuxdistro.
Q2: My application used to work, but I updated my kernel and now I'm getting
"libnipalu.so failed to initialize
Perhaps you need to run updateNIDrivers
Aborted"
Will my application work?
A2: The FlexRIO and supporting drivers must be built with the kernel sources
for the kernel that is in use. As root, run "updateNIDrivers" and restart
to fix the issue.
Q3: I am using a PXI controller and I have installed PXI Platform Services on my
x86 version of Linux, but when I run "lsni -v" I don't see any PXI-specific
information. What is wrong?
A3: You must reboot after installing PXI Platform Services to see PXI-specific
information.
Q4: Does FlexRIO support native x86_64 applications?
A4: As of NI-RIO 12.0.0, native x86_64 applications are supported.
Q5: When I run "lsni" I get the error "version 'GLIBCXX_3.4.9' not found."
A5: For information about this issue, go to ni.com/info and enter the Info Code
GLIBCXXerror.
-
-----------------
Legal Information
-----------------
----
Licensing
----
The license agreement for National Instruments software is contained in the
LICENSE.txt file in the root directory of the FlexRIO installer. You can
find third-party license agreements and legal notices in
/usr/local/natinst/nirio/doc/thirdpartylicenses.txt.
----
COPYRIGHT:
----
(c) 2016 National Instruments.
All rights reserved.
Under the copyright laws, this publication may not be reproduced or transmitted
in any form, electronic or mechanical, including photocopying, recording,
storing in an information retrieval system, or translating, in whole or in
part, without the prior written consent of National Instruments Corporation.
NI respects the intellectual property of others, and we ask
our users to do the same. NI software is protected by copyright and other
intellectual property laws. Where NI software may be used to reproduce
software or other materials belonging to others, you may use NI software
only to reproduce materials that you may reproduce in accordance with the
terms of any applicable license or other legal restriction.
For end-user license agreements (EULAs) and copyright notices, conditions, and
disclaimers, including information regarding certain third-party components
used in LabVIEW, refer to the Copyright topic of the LabVIEW Help.
U.S. Government Restricted Rights
If you are an agency, department, or other entity of the United States
Government ("Government"), the use, duplication, reproduction, release,
modification, disclosure or transfer of the technical data included in this
manual is governed by the Restricted Rights provisions under Federal
Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal
Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for
military agencies.
IVI Foundation Copyright Notice
Content from the IVI specifications reproduced with permission from the IVI
Foundation.
The IVI Foundation and its member companies make no warranty of any kind with
regard to this material, including, but not limited to, the implied warranties
of merchantability and fitness for a particular purpose. The IVI Foundation and
its member companies shall not be liable for errors contained herein or for
incidental or consequential damages in connection with the furnishing,
performance, or use of this material.
----
TRADEMARKS:
----
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for
information on NI trademarks. Other product and company names
mentioned herein are trademarks or trade names of their respective companies.
----
PATENTS:
----
For patents covering the NI products/technology, refer to the
appropriate location: Help patents in your software, the patents.txt file on
your media, or the NI Patent Notice at ni.com/patents.