NI-RIO 13.0.0 Known Issues

TEDS is not supported on cRIO-9068

Any code that uses TEDS on the cRIO-9068 will fail to deploy giving an error on an NI-RIO driver VI.

Workaround:

Unfortunately there is no work-around. You can use a different cRIO target if you need to use TEDS.

Back to top

Hybrid compilations with the cRIO-9076 and the NI 9802 can fail for timing violations

When compiling a hybrid bit file with the cRIO-9076, the NI 9802, and two other modules in Scan Mode, the compile fails for "timing violations that are not of type PERIOD".

Workaround:

Use the modules in FPGA mode, or use a different cRIO, such as the cRIO-9074.

Back to top

Scan Engine errors when resetting the FPGA immediately after calling FPGA Open Reference

Real-Time VIs that reset the FPGA immediately after calling an FPGA Open Reference method may return Scan Engine fault errors. 

Workaround:

Add sufficient wait after the FPGA Open Reference before calling the Reset method. See linked Knowledgebase article for details.

Back to top

Scan Interface Example returns error indicating that LabVIEW needs more memory to compile the VI

In the example "Using Scan Interface with FPGA Interface.lvproj", the "Getting Started" Real-Time VI will report an error indicating that LabVIEW needs more memory to compile the VI. This error may occur in other examples.

Workaround:

The FPGA "Reset" and FPGA "Run" methods needs to be regenerated. Delete and replace them in the Host VI.

Back to top

Error -52023 when connecting to USB R-series

When connecting to a USB R-series card, if you insert or remove other USB devices, some USB controllers can cause persistent error -52023 when communicating with the USB R-series. 

Workaround:

See the above linked Knowledgebase for more details.

Back to top

Timing violations with USB-7855R and USB-7856R

Compiling FPGA bitfiles for the USB-7855R and USB-7856R using the default 40 MHz top-level clock and a large amount of I/O channels leads to an increased number of compilation failure due to timing violations.

Workaround:

Several options exist to work around this issue. You can recompile which usually yields a successful result, change the top-level clock to 80 MHz or greater, or reduce the amount I/O your FPGA program is using. If using one of these workarounds still doesn't produce a successful compile, please contact ni.com/support.

Back to top

FPGA compile fails when using an XNET Module and the Synthesis Optimization Goal is set to Area

If using a cRIO-911x backplane, an XNET module in Scan Mode and another C-series module in FPGA mode, if you set the Synthesis Optimization goal to "Area" in the FPGA Compilation options, your compile will fail for "timing violations that are not of type PERIOD".

Workaround:

Set your Synthesis Optimization Goal to "Speed".

Back to top

Operating System Crash When Scanning Internal Memory of NI-RIO processes

Using a program (such as a debugger) that scans process memory of an application that interfaces with a FlexRIO, MXI-Express RIO, or R Series device can cause an operating system crash. 

Workaround:

Do not access internal memory within a process that is using NI-RIO devices.

Back to top

NI 9802 Mount and Unmount Methods cannot be called remotely from Windows

Normally, these commands would be run from the RT controller host (or remotely on the RT host through VI Server). For the EthernetRIO targets, NI 9146/9148 this is not an option.  This means that the NI 9802 RT API cannot be used with these targets.

Workaround:

None.

Back to top

Possible timing errors when compiling a VI with an NI 9215 IO node

Compiling an FPGA VI with 9215 IO nodes will potentially fail timing constraints.

Workaround:

The failure should only occur intermittently and recompiling the FPGA VI usually executes successfully. This issue has been resolved in NI-RIO 12.1.0 and later with LabVIEW 2012 SP1 and later.

Back to top

Adding a new NI-RIO device may cause MAX to temporarily display incorrect information.

While viewing NI-RIO devices in Measurement & Automation Explorer (MAX), adding a new NI-RIO device and naming it RIO0 can temporarily cause the wrong device information to display.

Workaround:

After installing and renaming the last device, refresh the device information in MAX. You may be required to refresh the Devices and Interfaces list up to three times for all information to be correctly displayed. This issue has been resolved in NI-RIO 13.0.0 and later with LabVIEW 2013 and later.

Back to top

Reduced network throughput on 902x and 9074 controllers when connecting to forced-speed network partners

The default link speed for 902x and 9074 CompactRIO controllers is autonegotiated. When connecting to partner network targets without autonegotiated link speeds, packets are dropped and network throughput over TCP drops as a result.

Workaround:

In NI-RIO 3.4 and later, set the network partner device to use autonegotiation. In NI-RIO 3.5.1 and later, you can also set the Preferred Link Speed for your CompactRIO controller to the same link speed as your network partner device. This issue has been resolved in NI-RIO 13.0.0 and later with LabVIEW 2013 and later.

Back to top

Mounting/Unmounting a NI 9802 in Real-Time interrupts Scan Engine

When you take scan mode measurements and then mount and unmount the SD card, on the subsequent reads the scan mode I/O variable throws error -65536 until the FPGA VI is run.

Workaround:

Instead of the blank FPGA VI required to normally make this work, use an empty while loop inside the FPGA VI and leave this VI running while running the RT VI. This issue has been resolved in NI-RIO 13.0.0 and later with LabVIEW 2013 and later.

Back to top

IO Variables lose custom settings when C Series module is copied and pasted in the LabVIEW project

When copying and pasting a C Series module containing IO Variables with custom settings, the custom settings are lost and revert to default values.

Workaround:

Instead of using copy-paste, drag or control-drag the module to move or copy the module. This issue has been resolved in NI-RIO 13.0.0 and later with LabVIEW 2013 and later.

Back to top

Calling the Mount method for a NI 9802 module on the wrong slot number will sometimes result in a crash on VxWorks targets

When running the Mount method for a NI 9802 from the Real-Time host, entering the wrong slot number can result in a crash on VxWorks targets.

Workaround:

Ensure a NI 9802 module is in the correct slot before running the Mount method. This issue has been resolved in NI-RIO 12.0.0 and later with LabVIEW 2012 and later.

Back to top

Setting Range property on 9219 with other properties in the same property node returns error -65720

Using a property node that includes 'Range' and any other property specific to the same channel of a 9219 will return Error -65720: This property is not valid for this module, or is not valid for the current configuration of this module. This error will be returned even though the configuration is valid.

Workaround:

When writing the Range property, write to it in a property node separate from other properties. This issue has been resolved in NI-RIO 12.0.0 and later with LabVIEW 2012 and later.

Back to top

Deploying an NI 9870 or 9871 when the module isn't physically present corrupts the CompactRIO RT controller

If a project is configured to contain an NI 9870 or 9871 module but the module isn't physically in the chassis, deploying the chassis will result in software corruption on VxWorks controllers. This and subsequent deployments will result in the following error: LabVIEW: (Hex 0x80DF0019) The deployment connection has timed out. To determine which operating system your controller is running, refer to Real-Time Controllers and Real-Time Operating System Compatibility

Workaround:

None. This issue has been resolved in NI-RIO 12.0.0 and later with LabVIEW 2012 and later.

Back to top

NI 9075/9076 do not support RIO Scan Interface or Hybrid modes

The new NI 9075/9076 integrated chassis and controller CompactRIO devices did not initially ship with RIO Scan Interface (RSI) capability.

However, the "Chassis Properties" dialog box used to select FPGA or RSI mode alludes to the fact that the controller may be used in Hybrid Mode.

Workaround:

None. This issue has been resolved in NI-RIO 4.0.0 and later with LabVIEW 2011 and later.

Back to top

Scan Engine VIs fail on a machine with only LabVIEW runtime and NI-RIO

Scan Engine VIs (such as "Set Scan Engine Mode.vi") return an error when used in a built LabVIEW application on a machine which only has the LabVIEW runtime and NI-RIO driver installed (returns error -2132869114: A Module could not be loaded).  The same LabVIEW executable works fine on a machine which also has the LabVIEW development environment installed.

Workaround:

The Scan Engine VIs need the DLLs located in:

C:\Program Files\National Instruments\Shared\DeploymentFramework

Copy this directory onto the machine with only LV runtime and NI-RIO (in the same location), and the scan engine VIs will function properly. This DeploymentFramework folder is installed with the LabVIEW development environment, but not with LabVIEW runtime or NI-RIO driver. This issue has been resolved in NI-RIO 4.0.0 and later with LabVIEW 2011 and later.

Back to top