This document contains the known issues with NI CompactRIO Device Drivers and NI R Series Multifunction RIO Device Drivers June 2019 that were discovered before and after the release of the May 2019 drivers. New issues appear at the top of this document. This list includes only severe or the most common issues, and does not include every issue known to NI.
The workarounds described in this document are not always tested by NI and are not guaranteed to resolve the issue. The brief description given does not necessarily describe the problem in full detail. If you would like more information on an issue, visit ni.com/contact and reference the issue ID. If you identify a workaround for an issue that is not listed in this document, please contact NI so that the workaround may be published.
ID | Known Issue | Affected LV Versions |
---|---|---|
205784 | Software installation fails on myRIO and ELVIS III with 2018 ELVIS III Toolkit | LabVIEW 2018 |
738261 | Non-recommended SD cards could fail to be recognized in cRIO-905x targets | LabVIEW 2019 |
738160 | RIO Mezzanine Card (RMC) added to LabVIEW project with shortened "RMC" name | LabVIEW 2019 |
Known Issues with NI CompactRIO Device Drivers June 2019
ID | Known Issues |
---|---|
Software installation fails on myRIO and ELVIS III with 2018 ELVIS III Toolkit When using the LabVIEW 2018 ELVIS III Toolkit and manually updating only the CompactRIO Device Drivers to 19.1 or higher, installing the CompactRIO Recommended Software Set can fail. Workarounds:
| |
Non-recommended SD cards could fail to be recognized in cRIO-905x targets In rare cases, it is possible that SD cards that are not NI recommended will fail to be recognized in cRIO-905x targets. Workaround:
| |
RIO Mezzanine Card (RMC) added to LabVIEW project with shortened "RMC" name. When adding a RIO Mezzanine Card (RMC) to an sbRIO in the LabVIEW project, it is given the name "RMC" without any information on the specific RMC type. As a result, it is difficult to distinguish which RMC card was added to the project. Workaround:
|