Archived: NI-RIO 3.0.1 Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Aperçu

This document has been archived and is no longer updated by National Instruments.

This document contains the NI-RIO 3.0.1 known issues that were discovered before and since the release of NI-RIO 3.0.1. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered. Each Issue appears as a row in the table and includes an issue title, a brief description of the problem, any workarounds that might help resolve the issue, and the date the issue was added to the document (not the reported date) and the NI-RIO release it was fixed in.

The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI and referencing the ID number given in the document. You can contact us through any of the normal support channels including phone, email, or the discussion forums. See www.ni.com/ask to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.

Known Issues

The following items are known issues in NI-RIO 3.0.1.

Known Issues with NI-RIO 3.0.1 and LabVIEW 8.6.x

116620

 Allocating DMA Memory on cRIO Controllers with 128 MB DRAM Can Cause the Controller to Crash when using NI-RIO 3.0.0

116834

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

113879

Projects containing cRIO modules take longer to load

117925

RIO IO Control Browse Window Does not Return Remote Device

117018

Cannot Deploy Scan Interface Modules with the character "/"

117222

Cannot Deploy Scan Interface Modules with the name "System"

     

123516

Boolean Values Returned by NI 9426 modules are inverted when used with the Scan Interface

     

Known Issues with NI-RIO 3.0.1 and LabVIEW 8.5.x

4K1CDCMA

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

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

114569

NI-RIO 3.1 does not install support for the NI 987x serial modules forLabVIEW 8.5.x

Known Issues with NI-RIO 3.0.1 and LabVIEW 8.2.x

4G3AED20

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

4DAEDMLX

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

4K1CDCMA

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

3VKDOURY

DMA in parallel While Loops

 

ID

Known Issue

Known Issues with NI-RIO 3.0.1 and LabVIEW 8.6.x

116620

Allocating DMA Memory on cRIO Controllers with 128 MB DRAM Can Cause the Controller to Crash when using NI-RIO 3.0.0

Allocating DMA Memory above 64 MBs on cRIO-9014, cRIO-9074, and sbRIO-96x2 Controllers can cause a crash or hang when using NI-RIO 2.30 or later.

Workaround—Refer to Knowledge Base 4767OILX.

 

This issue is fixed with NI-RIO 3.0.1


Date Added—11/21/2008
Return to top

 102834

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


Date Added—11/21/2008
Return to top

 113879

Projects containing cRIO modules take longer to load

cRIO Projects with many cRIO modules will take longer to load in LabVIEW 8.6 than in LabVIEW 8.5.1 or earlier.


Workaround—N/A


Date Added—11/21/2008
Return to top

117925

RIO IO Control Browse Window Does not Return Remote Device

The RIO IO Control Browse Window Does not Return Remote Device when the RIO Device Setup is launched from the Project. 


Workaround—Launch the RIO Device Setup from the Start Menu.


Date Added—11/21/2008
Return to top

 117018

Cannot Deploy Scan Interface Modules with the character "/"

Deploying Scan Interface Modules with the character "/" puts the Scan Interface software into an unrecoverable state.


Workaround—Rename any modules with the character “/”


Date Added—11/21/2008
Return to top

 117222

Cannont Deploy Scan Interface Modules with the name "System"

Deploying Scan Interface Modules named "System" puts the Scan Interface software into an unrecoverable state


Workaround—Rename any modules with the name “System”


Date Added—11/21/2008
Return to top

117222

Cannont Deploy Scan Interface Modules with the name "System"

Deploying Scan Interface Modules named "System" puts the Scan Interface software into an unrecoverable state


Workaround—Rename any modules with the name “System”


Date Added—11/21/2008
Return to top

123516

Boolean Values Returned by NI 9426 modules are inverted when used with the Scan Interface

When used with the Scan Interface, NI 9426 modules will return inverted boolean logic.


Workaround—Invert values returned by NI 9426 modules when used with the Scan Interface


Date Added—12/3/2008
Return to top

Known Issues with NI-RIO 3.0.1 and LabVIEW 8.5.x

4K1CDCMA

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

Date Added—11/21/2008
Return to top

 --

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

Date Added—11/21/2008
Return to top

 114569

NI-RIO 3.0.1 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.0.1 will install support for the NI 987x serial modules for LabVIEW 8.6.x.

 

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


Date Added—01/15/2009
Return to top

   

Known Issues with NI-RIO 3.0.1 and LabVIEW 8.2.x

 4G3AED20

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
Date Added—11/21/2008
Return to top

 4DAEDMLX

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. 

Date Added—11/21/2008
Return to top

 4K1CDCMA

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

Date Added—11/21/2008
Return to top

 3VKDOURY

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


Date Added—11/21/2008
Return to top

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).