This document contains the known issues with NI CompactRIO Device Drivers February 2016 and NI R Series Multifunction RIO Device Drivers February 2016 that were discovered before and after the release of NI CompactRIO Device Drivers August 2015 and NI R Series Multifunction RIO Device Drivers August 2015. New issues appear at the top of this document. Not every issue known to NI will appear on this list. The list is intended to show only the severe or most 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, and any workarounds that might help resolve the issue.
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/contact 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.
ID | Known Issue | Affected LV Versions |
---|---|---|
559661 | The Signal Quality Property Node is not supported for the cRIO-9032 and cRIO-9037 targets | 2015 SP1 |
Known Issues with NI CompactRIO Device Drivers February 2016 and NI R Series Multifunction RIO Device Drivers February 2016
ID | Known Issues |
---|---|
559661 |
The Signal Quality Property Node is not supported for the cRIO-9032 and cRIO-9037 targets. The Signal Quality Property Node for determining the signal strength of a connected access point is not currently supported. Workaround: |