LabVIEW 2015 myRIO Toolkit Known Issues

Aperçu

This document contains known issues for the LabVIEW 2015 myRIO Toolkit. 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.

Contacting NI

You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID.

Known Issues by Date

The following items are known issues in LabVIEW 2015 myRIO Toolkit sorted by Date.

387950 I2C Shutdown VI Causes Bus to Show As Busy If There Are Multiple Masters
406935 Indicator Terminals in VIs on myRIO from Express VIs Look like Controls
510638 I/O Monitor Returns Error -63040 and Fails to Connect
520023 Encoder API Returns Error: -363005
530396 myRIO Connection Diagram's Terminal Names in I/O Monitor Is Inconsistent
530436 myRIO Timer IRQ Example Throws Error "XNode is not executable"
533568 Removing the FPGA Chassis from LabVIEW Project Does Not Update FPGA Personality



ID Known Issue
387950

Return
I2C Shutdown VI Causes Bus to Show As Busy If There Are Multiple Masters
The I2C Shutdown VI (used by the I2C Close) resets all the I2C registers to 0. However, if the user used the Keep Bus Busy? input of the Read and/or Write VIs of the I2C bus, the bus could still be in use and calling the Shutdown VI would leave the bus busy indefinitely.

Workaround: N/A

Reported Version: 1.0    Resolved Version: N/A    Added: 08/01/2015
406935

Return
Indicator Terminals in VIs on myRIO from Express VIs Look like Controls
Indicator terminals from Express VIs look like controls

Workaround: N/A

Reported Version: 1.0    Resolved Version: N/A    Added: 08/01/2015
510638

Return
I/O Monitor Returns Error -63040 and Fails to Connect
When connecting with I/O monitor to the myRIO over a wireless network, the following error is thrown: Error -63040 occurred at niLvFpga_Open_myRIO-1900.vi. The reason for this is that the I/O Monitor cannot connect to the target over a wireless network.

Workaround: Connect to target directly

Reported Version: 2015    Resolved Version: N/A    Added: 08/01/2015
520023

Return
Encoder API Returns Error: -363005
When using a PWM and encoder on the same port of the myRIO, the encoder returns "Error: -363005: An invalid transition occurred in the quadrature encoder. Ensure that you have connected the hardware correctly and the encoder is not turning too fast." This can be for one of two reasons:
1. The target encoder phase changes too fast where the frequency exceeds 20MHz.
2. There is noise on the signal which needs debouncing.

Workaround: Make sure the frequency of the encoder phase does not exceed 20MHz or add a debouncing function in front of the encoder input of the FPGA code.

Reported Version: 2014    Resolved Version: N/A    Added: 08/01/2015
530396

Return
myRIO Connection Diagram's Terminal Names in I/O Monitor Is Inconsistent
The terminal names in I2C, SPI and UART Connection Diagram pages follow the rule:"Connector" / "Terminal". For example "A / TX", "B / TX". The names in AIO, DIO and PWM pages are inconsistent and only show "Terminal".

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 08/01/2015
530436

Return
myRIO Timer IRQ Example Throws Error "XNode is not executable"
Opening the myRIO Timer IRQ example under a roboRIO throws error "XNode is not executable". The error is not descriptive. This error is thrown because of a broken subVI in the example.

Workaround: Examine Error List to determine which subVI is broken.

Reported Version: 2014    Resolved Version: 2016    Added: 08/01/2015
533568

Return
Removing the FPGA Chassis from LabVIEW Project Does Not Update FPGA Personality
In a project with an FPGA chassis, you can select n samples mode from the I/O mode selector of certain VIs. When you remove the FPGA chassis, this option is still available and the VI will run without error.

Workaround: Reload the project.

Reported Version: 2014    Resolved Version: N/A    Added: 08/01/2015

Document last updated on 8/11/2015

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).