Archived: NI-RIO 3.5.0 Known Issues

242098

240922

239423

283266

240043

238827

237670

237624

236176

235891

235886

230492

215276 (226973)

200550

197769

196435

185187

171345

155238

132979

94604

4K1CDCMA

200550

198491

197769

196435

195192

193724

185187

184722

184171

177901

171345

132979

4K1CDCMA

ID

Known Issue

242098

sbRIO-963x/964x analog output may output incorrect values

On these devices, the built-in analog output channels may output a voltage very different from the commanded value, in some cases outputting a large voltage when commanded to output a small or zero voltage. Depending on how you are using the device, this issue could cause harm to persons or property. NI strongly recommends that all analog output users of the above-listed Single-Board RIO devices using NI-RIO 3.5.1 or later (and recompile any LabVIEW FPGA bitfiles)

Workaround:
To completely fix the issue, upgrade to NI-RIO 3.5.1 or later. If you have already installed NI-RIO 3.5.0, for convenience, NI-RIO 3.5.0 can by patched by running NI Update Service and following the prompts or manually downloading and applying the patch. NI Update Service is the recommended method if upgrading from NI-RIO 3.5.0

**Upgrading to NI-RIO 3.5.1 or later is strongly recommended**

Back to top

FlexRIO hardware resource conflicts with dynamic references

This is a critical issue for NI FlexRIO when using the dynamic reference wire in LabVIEW 2010. In affected applications, LabVIEW FPGA will incorrectly assign DMA resources to the peer-to-peer streams, which could result in potential hardware resource conflicts.

Applications that meet all the following criteria are affected:

• Implement peer-to-peer streaming on a LabVIEW FPGA target
• Use the dynamic FPGA reference wire in LabVIEW FPGA 2010
• Use NI-RIO 3.5.0

Workaround: 
To completely fix the issue, upgrade to NI-RIO 3.5.1 or later. If you have already installed NI-RIO 3.5.0, for convenience, NI-RIO 3.5.0 can by patched by running NI Update Service and following the prompts. This is the recommended method if upgrading from NI-RIO 3.5.0

**Upgrading to NI-RIO 3.5.1 or later is strongly recommended**

Back to top

Corrupt scan data when using CompactRIO in hybrid mode

This could result in several different incorrect types of readings. 

Workaround: 
Recompiling could fix the issue; however, it may not in all cases or fix the issue consistently between compiles of the same code.  To completely fix the issue, upgrade to NI-RIO 3.5.1 or later. If you have already installed NI-RIO 3.5.0, for convenience, NI-RIO 3.5.0 can by patched by running NI Update Service and following the prompts or manually downloading and applying the patch. NI Update Service is the recommended method if upgrading from NI-RIO 3.5.0

**Upgrading to NI-RIO 3.5.1 or later is strongly recommended**

Back to top

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

Scan Engine VIs (such as "Set Scan Engine Mode.vi") return an error when use in a built LabVIEW application on a machine which only has the LabVIEW runtime & NI-RIO driver installed (returns error -2132869114: A Module could not be loaded).  The same LabVIEW exe 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 & 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.

Back to top

Error -61499, timing violation, when compiling in hybrid mode

When compiling an FPGA VI that has modules under the chassis item (indicating scan mode) it’s possible to receive an erroneous timing violation.

Workaround:
There are several steps that could help resolve this issue. 

Back to top

Accessing 987x and 9402 with different FPGA diagram clock speeds returns compile error

Workaround:
None.  This has been corrected in NI-RIO 3.6 and later.

Back to top

FPGA Compiles containing User Defined Variables without modules fail timing

If code is compiled where a user defined variable is used without a module under the chassis item, the compile could fail to meet timing

Workaround:  
Go into the compile options and set the Design Strategy to be optimized for Timing Performance.

Back to top

Previous versions of NI-RIO will not install on CompactRIO 900x after installing NI-RIO 3.5.x

After installing NI-RIO 3.5 on a CompactRIO 900X, previous versions of NI-RIO will not install and result in a red exclamation point and Error -2147220296 with the message Microsoft Visual Studio 2008 Runtime Support 1.0 requires Base System 7.0.

Workaround:
Removing NI-RIO 3.5 from the controller will allow any NI-RIO version to be installed as normal. To remove NI-RIO 3.5, either reformat the controller or select Uninstall all software in the LabVIEW Real-Time Software Wizard.

Back to top

Possible timing errors when compiling a VI with a 9476/9477 IO node on a Spartan 3 target at 80 MHz

An IO node with 32 channels and error terminals enabled will not successfully compile on a Spartan 3 (sbRIO-96xx, cRIO-907x) when the top level clock is set to 80 MHz

Workaround:
Setting the Design Strategy to Timing performance in the build specification property for Xilinx Options will allow this to compile.  Alternatively, splitting the IO node into two 16-channel IO nodes will be successful.

Back to top

Getting INTERNAL_ERROR:Xst:cmain.c:3464:1.47.6.4 when compiling a 9205/9206 for a Spartan 3 target with an 80 MHz clock

This is a known issue with the Xilinx compiler that only occurs in rare situations.

Workaround:
Changing parts of the block diagram might fix the issue; alternatively, setting the Xilinx Options for Design Strategy to by optimized for Timing Performance should resolve the issue.  

Back to top

Timing violations with certain modules when compiling for a Spartan 3 target at 80 MHz

When using a 9205, 9206, 9263, 9264, or 9269 module with an 80 MHz clock on a Spartan 3 target (NI 96xx or NI 907x) it’s possible to get a timing failure when compiling.

Workaround:
In the Xilinx options, select the Design Strategy to be optimized for Timing Performance.  

Back to top

RIO IO Control does not display FPGA Targets for all targets in a LV Project

This only affects targets in a remote context. This is important for projects involving the NI 9148, which does not allow host VIs, as they are always on a different target.

Workaround:
Customers developing a host VI on a non-NI 9148 cRIO controller wanting to target a NI 9148 would have to manually type the NI 9148's IP address on the RIO IO control.

Alternatively, as of NI-RIO 3.6.0, all targets in the project will show in the RIO IO control.

Back to top

DMA Host side buffer failing to allocate memory with error -52000 or -50352

Using a 64-bit operating system (either Windows Vista or Windows 7) and configuring  DMA FIFO host side buffers fail to allocate enough memory and give error -52000 or -50352

Workaround:
Depending on how much memory is available to allocate, there are several things that can possibly resolve this issue.  

Back to top

200550

Setting date/time in a tight loop causes the controller to run at an incorrect frequency

If the date/time is being updated continuously in a loop with a period of less than 2 minutes, it can cause the controller to run slightly faster or slightly slower than it should

Workaround:
There is not ever a need to update the time this often.  To avoid the issue described above, do not set the date/time in a loop, or set it much less frequently

Back to top

197769

Using Windows Server 2003 R2 may require disabling Physical Address Extensions (PAE)

Support for Windows Server 2003 R2 may require disabling
physical address extensions (PAE). To learn how this might affect your use of Windows Server 2003 and what actions you might have to take, visit <a href="http://www.ni.com/info">ni.com/info</a> and enter the info code <i>PAESupport</i>

Workaround:
Disable PAE for Windows Server 2003 R2 as instructed in the knowledgebase referenced above.

Back to top

Configuring a module in scan mode that has been swapped for another without restarting causes error 1070

If a module being used in scan mode is swapped out and replaced, “Refresh Modules” command will pick up the difference; however, trying to programmatically configure the module results in “Error 1070”

The module is implicitly opening a reference that is not being refreshed

Workaround:
(1) To programmatically prevent the issue, explicitly close both references (IO and module) by calling “Close Variable Connection” from the Shared Variables Palette, before running Discover IO.vi  (2) If the VI is stopped and started again the references will be updated properly.

Back to top

Chassis settings don't automatically deploy

Changes to the chassis properties are not automatically deployed.  This is problematic when switching between Scan and FPGA Interface mode because it means the project can easily get out of sync with the target if the user does not manually deploy the chassis.

Workaround:
Manually deploy settings whenever changes are made to chassis properties.

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.

Back to top

Changing counter configuration via module refnum always resets counter

When changing properties such as terminal count and counter direction via the RSI module refnum the counter value always resets.

Workaround: 
None.

Back to top

Reading Empty Target to Host DMA FIFO with Timeout Set to Zero Gradually Starves CPU in built LabVIEW RT executables on cRIO targets

In built LabVIEW RT applications on cRIO, if a Target to Host DMA FIFO read executes with a timeout of zero and the FIFO is empty a processor leak occurs that increases the CPU usage on the controller.

Workaround:
Read zero elements to find elements remaining, instead of using a zero timeout

Back to top

Performance issues when using more than 16 FPGA sessions

The NI-RIO driver maintains a growable lookup table of sessions that has segments. If the first segment overflows, new segments are created. RIO sessions using those new segments will pay a performance penalty. The RIO driver sets a warning on any session that has this "problem".

Workaround:
Users should be careful to close unused sessions and look for sessions leaks.  If greater than 16 sessions are needed, please contact NI technical support.  www.ni.com/contact-us

Back to top

DMA is not supported from the host to the FPGA on cRIO-900x

DMA is not supported from the host to the FPGA target on the cRIO-9002/9004.

LabVIEW returns an error if you try to output DMA from the cRIO-9002/9004.

Workaround:
N/A

Back to top

ID

Known Issue

Setting date/time in a tight loop causes the controller to run at an incorrect frequency

If the date/time is being updated continuously in a loop with a period of less than 2 minutes, it can cause the controller to run slightly faster or slightly slower than it should

Workaround:
There is not ever a need to update the time this often.  To avoid the issue described above, do not set the date/time in a loop, or set it much less frequently

Back to top

NI 9213 return bad first value when the module is inserted and is already running

If an application is executing and the module is removed and readded, or a new module is added to the chassis while the code to read that module is already running, the first value returned is incorrect.

Workaround:
N/A

Back to top

Using Windows Server 2003 R2 may require disabling Physical Address Extensions (PAE)

Support for Windows Server 2003 R2 may require disabling
physical address extensions (PAE). To learn how this might affect your use of Windows Server 2003 and what actions you might have to take, visit <a href="http://www.ni.com/info">ni.com/info</a> and enter the info code <i>PAESupport</i>

Workaround:
Disable PAE for Windows Server 2003 R2 according to the knowledgebase referenced above.

Back to top

Configuring a module in scan mode that has been swapped for another without restarting causes error 1070

If a module being used in scan mode is swapped out and replaced, “Refresh Modules” command will pick up the difference; however, trying to programmatically configure the module results in “Error 1070”

The module is implicitly opening a reference that is not being refreshed

Workaround:
(1) To programmatically prevent the issue, explicitly close both references (IO and module) by calling “Close Variable Connection” from the Shared Variables Palette, before running Discover IO.vi  (2) If the VI is stopped and started again the references will be updated properly.

RIO Device Setup utility crashes after running a program with User-Defined variables on cRIO

Once a VI is run with user-defined variables, subsequently running the RIO Device Setup will cause the target to become unresponsive.

Workaround:
Before running RIO Device Setup, (1) download a blank FPGA VI  or (2) Reset the device.

FPGA Discovery fails silently on sbRIO if FPGA is in a bad state

Anytime the sbRIO is in the following states: safe mode, unconfigured IP address, or the NI-RIO driver is not installed on the controller, FPGA auto-discovery will fail silently.

Note1 -- If the sbRIO controller is in a good state, auto-discovery succeeds.
Note2 -- If there is some condition that prevents module discovery (not FPGA target discovery) from working during sbRIO auto-discovery, it is reported correctly.
Note3 -- cRIO autodiscovery reports errors properly at every stage

Workaround:
Manually add the FPGA target

Chassis settings don't automatically deploy

Changes to the chassis properties are not automatically deployed.  This is problematic when switching between Scan and FPGA Interface mode because it means the project can easily get out of sync with the target if the user does not manually deploy the chassis.

Workaround:
Manually deploy settings whenever changes are made to chassis properties.

Mount SD Card (9802) Doesn't return error on Pharlap

The NI 9802 is not supported on Pharlap targets (900x). 

If an attempt to mount the NI 9802 in LabVIEW Real-Time is made it will not work; however, no error is returned.  The drive letter returned is “/” which is the only indication this didn’t work.

Workaround:
N/A

cRIO-9074 set to Ethernet polling still uses interrupt based Ethernet

When Ethernet polling is enabled on this controller it still gets interrupts anyway, causing jitter

Workaround:
N/A

9401 output glitches high when set to output and sleep is asserted or FPGA VI is downloaded

The 9401 has a pull-up resistor causing this to happen.

Workaround:
Before going into sleep or downloading a new VI, set the outputs to inputs to prevent the glitch. 

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.

Reading Empty Target to Host DMA FIFO with Timeout Set to Zero Gradually Starves CPU in built LabVIEW RT executables on cRIO targets

In built LabVIEW RT applications on cRIO, if a Target to Host DMA FIFO read executes with a timeout of zero and the FIFO is empty a processor leak occurs that increases the CPU usage on the controller.

Workaround:
Read zero elements to find elements remaining, instead of using a zero timeout

DMA from the host to the FPGA target on the cRIO-9002/9004

DMA is not supported from the host to the FPGA target on the cRIO-9002/9004.

LabVIEW returns an error if you try to output DMA from the cRIO-9002/9004.

Workaround:
N/A

ID

Known Issue

NiRioScanInterface DMA Channel is listed when using Scan Interface along with LabVIEW FPGA Host Interface

When using Scan Inteface along with LabVIEW FPGA Host Interface, DMA FIFO method nodes display internal Scan Interface DMA Channels

Workaround:
N/A

DMA from the host to the FPGA target on the cRIO-9002/9004

DMA is not supported from the host to the FPGA target on the cRIO-9002/9004.

LabVIEW returns an error if you try to output DMA from the cRIO-9002/9004.

Workaround:
N/A

Reading Empty Target to Host DMA FIFO with Timeout Set to Zero Gradually Starves CPU in built LabVIEW RT executables on cRIO targets

In built LabVIEW RT applications on cRIO, if a Target to Host DMA FIFO read executes with a timeout of zero and the FIFO is empty a processor leak occurs that increases the CPU usage on the controller.

Workaround:
Read zero elements to find elements remaining, instead of using a zero timeout

Cannot Deploy Scan Interface Modules or IO Variables  with Non-ASCII Characters

When deploying Scan Interface Modules or IO Variables with Non-ASCII characters such as Chinese or Japanese Characters it will report that the Deployment Completed with Errors.

Workaround:
 Rename any Scan Interface Modules or IO Variables using Alpha Numeric  Characters.

Abort and Reset Methods do not execute on incoming error

If an error is passed to either the Abort or Reset Methods, they will not execute and the error will be passed through

Workaround:
Check, report, and clear errors manually in any error clusters wired to an Abort or Reset; otherwise, do not pass error clusters to these methods

DMA from the host to the FPGA target on the cRIO-9002/9004

DMA is not supported from the host to the FPGA target on the cRIO-9002/9004.

LabVIEW returns an error if you try to output DMA from the cRIO-9002/9004.

Workaround—N/A

VIs that use the calibration API should be modified to use the RIO Device I/O control

Applications from versions of LabVIEW older than 8.5.x that use 783XR Calibration - Open FPGA VI Reference.vi should be updated to use the RIO Device I/O control instead of the VISA I/O control.

Workaround—N/A

FPGA code generation into an existing host VI is very slow in FPGA Wizard

If you use the FPGA Wizard to generate code, open the host VI, then generate code into the same VI, the code generation goes very slowly.

Workaround—N/A

Large configuration files load slowly in FPGA Wizard

Opening a large FPGA Wizard configuration file can take several minutes.

Workaround—N/A

Maximum Timed I/O rate value is 70 kHz in FPGA Wizard generated code

The maximum rate you can set for the Single Point Timed I/O timing engine on the Single Point Timed configuration page is 70 kHz. The maximum rate achievable varies with different hardware devices.

Workaround—N/A

Selecting external clock requires external clock source with FPGA Wizard

If you select External for the Clock Type on the Single Point Timed or Buffered DMA Input configuration page and you do not have an external clock source connected, LabVIEW appears to hang when you run the generated host VI. Press the Global Stop button to stop the VI or add an external clock source to resume running the VI.

Workaround—N/A

NI-RIO 3.5.0 does not install support for the NI 987x serial modules for LabVIEW 8.5.x

For serial module support in LabVIEW 8.5 download and install the C-Series Serial Software  installer.  NI-RIO 3.5.0 will install support for the NI 987x serial modules for LabVIEW 8.6.x and later.

 Workaround—Install C-Series Serial Software from the installer linked above.

FPGA I/O Property Node returns wrong value for Module Model Code of NI 9217 module

The FPGA I/O Property Node returns the value 9217, which is the Product ID, not the Module Model Code, of the NI 9217. The Module Model Code is 0x712B.

Workaround—Look for 9217 in applications looking for the Product ID in LabVIEW 8.2.x

Read/Write Controls execute more slowly after upgrade to NI-RIO 2.4.1 or later

Read/Write Control now uses a Call Library Function Node to call the RIO driver. The Call Library Function Node executes additional code if debugging is enabled. To restore the performance to the original level, you must disable debugging in any VIs that contain Read/Write Controls.

 Workaround— You can disable debugging in a VI by going to File»VI Properties»Execution and unchecking Allow debugging. 

DMA from the host to the FPGA target on the cRIO-9002/9004

DMA is not supported from the host to the FPGA target on the cRIO-9002/9004.

LabVIEW returns an error if you try to output DMA from the cRIO-9002/9004.

Workaround—N/A

DMA in parallel While Loops

If you use DMA in parallel While Loops either on the cRIO-9002/9004 or while accessing the FPGA target across a network, one of the While Loops might hang while the other executes.

 Workaround—N/A