NI-RIO 17.0旧版设备驱动Linux系统64位English完整版
Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html
NI-RIO 17.0旧版设备驱动Linux系统32位English完整版
NI-RIO（旧版）
NI-RIO用于为可重配置硬件设备提供支持。
NI-RIO是一个设备驱动，用于支持可重配置I/O (RIO)硬件的识别、编程和部署。它为CompactRIO模块、多功能可重配置I/O设备、PXI多功能可重配置I/O模块和FlexRIO仪器提供了支持。
17.0
文件大小: 16441344 字节 (15.68 MB)
修改日期: 2017-06-24 05:50
MD5: bb253ca19b2e6e38602b5e7071fcd249（官方正确）
SHA1: efd9e598db9e44492c8b424622ec303c6796e374
SHA256: e252c50040b24a11c726c2d9db1304bd009633244a61d83393960c25d67f81c6
CRC32: 83969ce4
NI-RIO for Linux/x86 64-bit, Version 17.0.0May 2017-------------------------------------------------------------------------------This file contains late-breaking news about NI-RIO and supersedes anyinformation found in other documentation included in the distribution. Refer toni.com/linux for the most recent information about Linux support from NationalInstruments.------------------------------------------------------------------------------------------------Table of Contents-----------------System RequirementsInstallationUninstallationUsing the NI-RIO Driver and FPGA Interface C APIUsing the NI-RIO Driver and FPGA Interface Python APIUsing the NI-RIO ServerUsing RIO AliasesRunning Linux on PXI ControllersDocumentation and HelpLinux LimitationsKnown IssuesNI-RIO Does Not Support 32-bit Linux DistributionsFAQsLegal Information-------------------System Requirements-------------------NI-RIO for Linux software for the Intel x64 64-bit architecture has been tested on the following distributions: openSUSE Leap 42.1 openSUSE Leap 42.2 Red Hat Enterprise Linux Desktop + Workstation 6.x Red Hat Enterprise Linux Desktop + Workstation 7.x Scientific Linux 6.x CentOS 7.xFor more information about Linux versions and distributions supported byNI, refer to ni.com/linux.In order to use NI-RIO on Linux, you need a Windows system to develop yourLabVIEW FPGA application. You must compile a bitfile, generate headers with theFPGA Interface C API Generator or FPGA Interface Python API, and then move the application to your Linux system. Refer to the "Using the NI-RIO Driver and FPGA Interface C API" and "Using the NI-RIO Driver and FPGA Interface Python API" sections for more information.---------------------------Installation---------------------------Note: To ensure that the installation completes successfully, you must uninstall any previous version of NI-RIO before you install the current version. For information about uninstalling an old version of NI-RIO, refer to the readme for that version.To install NI-RIO for Linux, run the INSTALL script from this directory asroot. The INSTALL script ensures that all requirements are met beforeinstalling the NI-RIO software. The script then uses RPM to install the contentof the NI-RIO 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 commonlymissing dependencies are GCC and kernel sources. For distributions managed withyum, 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." Thismessage can occur even if you have installed the correct kernel sources, if thesources require configuration. This problem may affect other distributions inaddition 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. 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 ensurethat all the drivers are updated.After installation, the NI-RIO drivers are loaded by default at boot time ifthere is a RIO device in the system.-----------------------------Uninstallation-----------------------------To uninstall the driver and its dependencies, run the UNINSTALL script.------------------------------------------------Using the NI-RIO Driver and FPGA Interface C API------------------------------------------------You must begin development on a computer running Windows. Use LabVIEW FPGA todevelop and build an FPGA VI that runs on a RIO device. Use the FPGAInterface C API Generator to create the C source files for your application.Visit ni.com/info and enter the Info Code fpgainterfacecapi to get the latestversion of the FPGA Interface C API Generator. Then copy the generated filesto the Linux machine to begin development of C/C++ code for your application.For information about using the FPGA Interface C API, visit ni.com/info andenter the Info Code fpgainterfacecapihelp.To find the RIO device you are using in your application, use the command"lsni -v" to list information on all NI devices in thesystem.-----------------------------------------------------Using the NI-RIO Driver and FPGA Interface Python API-----------------------------------------------------You must begin development on a computer running Windows. Use LabVIEW FPGA todevelop and build an FPGA VI that runs on a RIO device. Copy the compiled bitfile (.lvbitx) over to your Linux machine and follow the steps at https://github.com/ni/nifpga-python to get started.-----------------------Using the NI-RIO Server-----------------------Complete the following steps to remotely access RIO devices on your Linuxsystem from another system with NI-RIO 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 /var/local/natinst/nirio/etc/ 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: 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 ofqualifiers, IP addresses, DNS hostnames, and wildcard patterns. To determinewhether a remote system has access to RIO devices on this system, the RIOserver looks for an entry in the list that matches the remote system. The "+"qualifier allows access, and the "-" qualifier denies access. The RIO serveruses the last matching entry in the list to determine whether to allow or denyaccess. 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. Thefirst argument in the example above explicitly denies remote access from anyIP 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 DeviceAccess asfollows: DeviceAccess="+*"-----------------Using RIO Aliases-----------------In order to create RIO aliases to local or remote RIO devices, you must editthe nirio.ini file at /var/local/natinst/nirio/etc/. Add an section if one does not already exist. For each alias, there must be a separate line in the section that follows the <alias>="<resource>" format. Thefollowing example specifies both a local and remote alias: foo="RIO0" bar="rio://mycrio/RIO0"Note that aliases must contain only alphanumerics, '-', and '_'.Next, change the following version lines to 0: MajorVersion=0 MinorVersion=0This will trigger nirio.ini to be updated the next time it is used. Afterrunning "lsni", you should see that the section is removed andinstead there will be a new section for each new alias.--------------------------------Running Linux on PXI Controllers--------------------------------NI-RIO for Linux works with all PXI and PXI Express controllers and chassis.----------------------Documentation and Help----------------------Use a web browser to view the NI-RIO help at ni.com/manuals.-----------------Linux Limitations-----------------Some features discussed in the NI-RIO documentation and help are unavailable on Linux.- NI-RIO supports two application development environments:* Python 2.7 and Python 3.4+* C and C++ (gcc)NI-RIO does not support other ADEs, such as the LabVIEW Real-Time Module, LabWindows/CVI, Microsoft Visual C/C++, or Microsoft Visual Basic.- When using NI-RIO in a PXI system, several restrictions apply:* Control through MXI-4 is supported, but MXI-3 is not.* Certain embedded controllers may be recommended over others for use in Linux * There may be some restrictions related to routing triggers, events, and clocks over the PXI backplane on some PXI chassis models - External calibration functions are not supported.Refer to your hardware documentation for information about external calibration, and refer to ni.com/calibration.If your NI-RIO requires external calibration, either perform the calibration on a Windows system, or hire NI or an independent calibration laboratory to perform the calibration.------------Known Issues------------Visit ni.com/info and enter the Info Code jpcuj3 for a current list of all known issues in this release.----------------------------------------------------------------NI-RIO Does Not Support 32-bit Linux Distributions----------------------------------------------------------------NI-RIO dropped support for Intel 32-bit versions of Linux distributions on July 1, 2016. Versions of NI-RIO that ship after July 1, 2016 may install and execute on Intel 32-bit distributions, but official support is not provided.----FAQs----Q1: What action needs to be taken if I upgrade/change my kernel?A1: Some action is required to make the existing NI-RIO 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-RIO software for Linux from this directory. -----------------Legal Information---------------------COPYRIGHT:----(c) 2017 National Instruments. All rights reserved. Under the copyright laws, this publication may not be reproduced or transmittedin 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 RightsIf 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 NoticeContent 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 andits 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 namesmentioned herein are trademarks or trade names of their respective companies. ----PATENTS:----For patents covering the NI products/technology, refer to theappropriate location: Help» Patents in your software, the patents.txt file on your media, or the NI Patent Notice at ni.com/patents.
页:
[1]