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.
The following items are known issues in NI-RIO 3.2.0.
Important: This is a special known issues document. The following list is not comprehensive. It only covers six issues. The following six issues are severe enough that NI immediately released NI-RIO 3.2.1 to fix these issues.
It is strongly advised that any customer using NI-RIO 3.2.0 should upgrade immediately to NI-RIO 3.2.1 or later!
It is advisable to upgrade to NI-RIO 3.2.1 for all customers, if known issues are needed for NI-RIO 3.2.0 beyond those listed here, refer to known issues for NI-RIO 3.2.1, which is the same driver but with the following issues fixed.
ID | Known Issue |
| |
CQE 4ZCFM1CP | SST Solid-state drive failures Some cRIO controllers have an issue that can cause the internal solid-state storage drive to stop responding after several million write cycles. If the internal solid-state storage drive stops responding, the controller is unusable and must be repaired. The following controllers are affected by this issue and should be updated to extend the life of the solid-state storage drive:
Workaround: Upgrade to NI-RIO 3.2.1 Immediately! Date Added—11/24/09 |
174963 | RIO Scan Interface on ECAT 1.0 causing lost data Scan Engine data is not being completely transferred back. If you were to write 1,2,3,4,5 to a user-defined variable (on ECAT only) the data returned would be 1,1,3,4,4, etc. Results are random. Date Added—11/24/09 |
178392 | RIO Scan Interface improperly casting FXP data causes incorrect conversion to integer FXP data is fine throughout LabVIEW. Whenever FXP data, only from RIO Scan Engine user-defined variable, is converted, the result is incorrect Workaround—Set the user-defined default to 64-bit configuration, then convert Date Added—11/24/09 |
178008 | NI 9219 improperly sign extends causing bad data in raw (uncalibrated), unipolar (resistance, RTD, Quarter Bridge) modes The 24-bit module readings are improperly being extended to the 32-bits by the driver anytime a reading is greater than half of the range. The upper 8-bits are assigned 1's, causing a random, large value.
Date Added—11/24/09 |
178492 | NI 9215 FPGA code hangs occasionally without error or indication Workaround— Upgrade to NI-RIO 3.2.1 Date Added—11/24/09 |
176794 | Recommended Software Sets fail upgrades/downgrades with error code 1430 Workaround---Uninstall/install (instead of upgrade/install); Use custom install option to upgrade; Upgrade to NI-RIO 3.2.1 Date Added—11/24/09 |
| |
CQE 4ZCFM1CP | SST Solid-state drive failures Some cRIO controllers have an issue that can cause the internal solid-state storage drive to stop responding after several million write cycles. If the internal solid-state storage drive stops responding, the controller is unusable and must be repaired. The following controllers are affected by this issue and should be updated to extend the life of the solid-state storage drive:
Workaround: Upgrade to NI-RIO 3.2.1 Immediately! Date Added—11/24/09 |
178008 | NI 9219 improperly sign extends causing bad data in raw (uncalibrated), unipolar (resistance, RTD, Quarter Bridge) modes The 24-bit module readings are improperly being extended to the 32-bits by the driver anytime a reading is greater than half of the range. The upper 8-bits are assigned 1's, causing a random, large value.
Date Added—11/24/09 |
178492 | NI 9215 FPGA code hangs occasionally without error or indication Workaround— Upgrade to NI-RIO 3.2.1 Date Added—11/24/09 |
176794 | Recommended Software Sets fail upgrades/downgrades with error code 1430 Workaround---Uninstall/install (instead of upgrade/install); Use custom install option to upgrade; Upgrade to NI-RIO 3.2.1 Date Added—11/24/09 |
| |
CQE 4ZCFM1CP | SST Solid-state drive failures Some cRIO controllers have an issue that can cause the internal solid-state storage drive to stop responding after several million write cycles. If the internal solid-state storage drive stops responding, the controller is unusable and must be repaired. The following controllers are affected by this issue and should be updated to extend the life of the solid-state storage drive:
Workaround: Upgrade to NI-RIO 3.2.1 Immediately! Date Added—11/24/09 |
176794 | Recommended Software Sets fail upgrades/downgrades with error code 1430 Workaround---Uninstall/install (instead of upgrade/install); Use custom install option to upgrade; Upgrade to NI-RIO 3.2.1 Date Added—11/24/09 |
| |
CQE 4ZCFM1CP | SST Solid-state drive failures Some cRIO controllers have an issue that can cause the internal solid-state storage drive to stop responding after several million write cycles. If the internal solid-state storage drive stops responding, the controller is unusable and must be repaired. The following controllers are affected by this issue and should be updated to extend the life of the solid-state storage drive:
Workaround: Upgrade to NI-RIO 3.2.1 Immediately! Date Added—11/24/09 |
176794 | Recommended Software Sets fail upgrades/downgrades with error code 1430 Workaround---Uninstall/install (instead of upgrade/install); Use custom install option to upgrade; Upgrade to NI-RIO 3.2.1 Date Added—11/24/09 |