Print
PDFOverview
This document contains the NI-RIO 3.2.1 known issues that were discovered before and since the release of NI-RIO 3.2.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). 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.2.1.
Further Information
|
ID |
Known Issue |
|
|
|
| 185187 |
Chassis settings don't automatically deploy when switching between scan mode and FPGA mode 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.
|
| 195192 |
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
|
| 193724 |
FPGA Discovery fails silently on sbRIO if FPGA is in a certain 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 Note1 -- If the sbRIO controller is not in one of the states mentioned above, auto-discovery succeeds. Workaround—(1) Manually add the FPGA target, or (2) resolve any of the conditions above that prevent auto-discovery
|
| 192012 |
cRIO crashes when configuring a 9235 module programmatically with Scan Engine API When the configuration node for the 9235 is called the CompactRIO will hang and loose connection Workaround—Upgrade to NI-RIO 3.3
|
| 187879 |
Discovery is slow (~15 sec.) if RIO local chassis has 8 modules This only happens if all modules are selected and added at once. Adding less modules works as expected and takes much less time Workaround—N/A Date Added—11/25/09 |
| 185715 |
Crash when running alternative FPGA application after waking from sleep on Windows Whenever Windows goes into sleep and resumes, running a new FPGA VI will cause a blue screen crash. If an FPGA VI was run before Windows sleep, it will continue to function normally after Windows resumes. Workaround—Upgrade to NI-RIO 3.3
|
| 195082 |
DAQmx 9.0.2 prevents NI-RIO 3.2.1 from installing the CompactRIO MAX provider This prevents Measurement and Automation Explorer (MAX) from recognizing cRIO targets Workaround—(1) Install NI-RIO before DAQmx 9.0.2 or (1a) If DAQmx 9.0.2 is already installed, the system needs to be cleared of all NI software before installing NI-RIO 3.2.1. Alternatively, (2) Install NI-RIO 3.3.0 (which can be installed on top of DAQmx 9.0.2 Date Added—11/25/09 |
| 171345 |
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. Date Added—11/25/09 |
| 177901 |
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
|
| 182431 |
cRIO-902x controllers do not support Ethernet polling The option is currently grayed out for these controllers Workaround—N/A
|
| 184171 |
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
|
| 196435 |
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 with programmatic configuration is swapped for another module, “Refresh Local Modules” followed by discovering children of the I/O Variable Container will return seemingly valid references with correct model and slot property information; however, "To More Specific Class" returns “Error 1070”, preventing the refnum from being used to configure modules. The class of the module refnum is only updated at open, and the implicitly opened refnum is not being closed. Workaround—(1) To prevent the issue, explicitly close all references (IO and module) by calling “Close Variable Connection” from the Shared Variables Palette, before calling "Refresh Local Modules" and discovering children of the I/O Variable Container. (2) If the VI is stopped and started again the references will be updated properly Date Added—11/25/09 |
| 132979 |
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 it will require extra processing that increases the CPU usage on the controller. Date Added—01/15/2009 |
| 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 |
|
|
|
| 185187 |
Chassis settings don't automatically deploy when switching between scan mode and FPGA mode 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.
|
| 116620 |
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
|
| 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 |
| 132979 |
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 it will require extra processing that increases the CPU usage on the controller. Workaround— Read zero elements to find elements remaining, instead of using a zero timeout Date Added—01/15/2009 |
| 131654 |
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. Date Added—01/15/2009 |
| 135570 |
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 Date Added—2/13/09 |
|
|
|
| 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 |
| -- |
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 |
| 40243 |
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 |
| 114569 |
NI-RIO 3.2.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.2.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 |
|
|
|
| 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—01/15/2008 |
| 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—01/15/2009 |
| 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 |
| 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—01/15/2009 |
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).