October 2022
This file contains installation instructions and compatibility information for NI-RIO 2022 Q4.
You can find more release information on ni.com.
Using the NI-RIO Driver and FPGA Interface LabVIEW API
Using the NI-RIO Driver and FPGA Interface C API
Using the NI-RIO Driver and FPGA Interface Python API
Using the NI-RIO Driver and FPGA Interface Python API
NI-RIO for Linux/x86 64-bit Architecture has been tested on the following distributions:
Visit NI Hardware and Operating System Compatibility to view driver, desktop operating system, and real-time operating system support for individual hardware devices.
To view information for your device:
Note: Some compatibility information may only be available in the archive attached to the NI Hardware and Operating System Compatibility page. For historic driver and OS support information, refer to the readme for the relevant driver version.
NI provides a repository add-on for all supported drivers that you can install using your Linux distribution's native package manager.
Currently the LabVIEW Interface supports R Series RIO devices on Linux Desktop. You must begin development on a computer that runs Windows. Use LabVIEW FPGA to develop and build an FPGA VI that runs on a RIO device. Next, copy the resulting bitfile and host VI from Windows to your Linux desktop. On your Linux Desktop, open the block diagram of the host VI, change the configuration of Open VI Reference to Bitfile, and select the corresponding bitfile. Run the host VI to deploy the bitfile and interact with the FPGA application.
When you open the examples for NI-RIO in LabVIEW, they might appear to be broken and search for missing files. This is expected until the configuration of Open VI Reference is changed to Bitfile.
To find the RIO devices present on your system that can be used in your application, use the command lsni -v.
You must begin development on a computer running Windows. Use LabVIEW FPGA to develop and build an FPGA VI that runs on a RIO device. Use the FPGA Interface C API Generator to create the C source files for your application. Visit ni.com/r/fpgainterfacecapi to get the latest version of the FPGA Interface C API Generator. Then 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, visit the NI Documentation Portal.
To find the RIO device you are using in your application, use the command lsni -v to list information on all NI devices in the system.
You must begin development on a computer running Windows. Use LabVIEW FPGA to develop 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 github.com/ni/nifpga-python to get started.
Complete the following steps to remotely access RIO devices on your Linux system from another system with NI-RIO installed:
[General] RpcServerPort=11296 DeviceAccess="-*;+10.0.29.54"
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 RIO devices on this system, the RIO server looks 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 denies 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 DeviceAccess as follows:
DeviceAccess="+*"
In order to create RIO aliases to local or remote RIO 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 aliases="resource" format. The following example specifies both a local and remote alias:
[Aliases] foo="RIO0" bar="rio://mycrio/RIO0"
Note: Aliases must contain only alphanumerics, '-', and '_'.
Next, change the following version lines to 0:
[General] MajorVersion=0 MinorVersion=0
This will trigger nirio.ini to be updated the next time it is used. After running lsni, you should see that the [Aliases] section is removed and instead there will be a new section for each new alias.
Some features discussed in the NI-RIO documentation are unavailable on Linux.
Copyright
© 2022 National Instruments Corporation. All rights reserved.
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.
Notices are located in the /usr/share/doc/NOTICES directory. EULAs are located in the /usr/share/ni/licenses directory.
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.
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.
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.
For patents covering the NI products/technology, refer to the NI Patent Notice at ni.com/patents.