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.
The following items are known issues in LabVIEW 2017 myRIO Toolkit sorted by Date.
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
| |||||
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
| |||||
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
| |||||
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.
| |||||
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
| |||||
586190 Return | Using the myRIO Custom FPGA Project Template and Setting a File Name Prefix Creates a Broken RT Main VI When creating a project using the myRIO Custom FPGA Project Template and setting a File Name Prefix, the RT Main VI is created in a broken state. The reason for this is that the Open FPGA VI Reference Function is configured to point to an FPGA VI without the prefix included in the FPGA VI filename. Workaround: Modify the Open FPGA VI Reference Function to point to the correct FPGA VI.
| |||||
588221 Return | When Adding an Existing myRIO Target to a LabVIEW Project, with the FPGA Module Installed, the Target Only Works with the Default FPGA Personality If an existing myRIO target is added to a LabVIEW Project with the FPGA Module installed then the target will only work with the Default FPGA Personality. The High Throughput VIs will load broken because the target will remain in the default personality. Workaround: Add a new, generic target or device to the project, and then connect to the device after it has been added.
| |||||
641163 Return | The myRIO Software Bundle Licensing Wizard Attempts to Activate the Report Generation Toolkit and Database Connectivity Toolkit After installing the myRIO Software Bundle Suite the Licensing Wizard lists the Report Generation Toolkit and Database Connectivity Toolkit as software that requires activation. The activation fails because the serial number for LabVIEW Student Edition is not associated with either toolkit. Workaround: If not using these toolkits then ignore the prompt. Optionally, you can enter a serial number that is valid for these toolkits and reactivate.
|
The following items are known issues in LabVIEW 2017 myRIO Toolkit sorted by Category.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
Functions, VIs, and Express VIs | ||||||
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
| |||||
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
| |||||
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.
| |||||
Installation and Activation | ||||||
641163 Return | The myRIO Software Bundle Licensing Wizard Attempts to Activate the Report Generation Toolkit and Database Connectivity Toolkit After installing the myRIO Software Bundle Suite the Licensing Wizard lists the Report Generation Toolkit and Database Connectivity Toolkit as software that requires activation. The activation fails because the serial number for LabVIEW Student Edition is not associated with either toolkit. Workaround: If not using these toolkits then ignore the prompt. Optionally, you can enter a serial number that is valid for these toolkits and reactivate.
| |||||
LabVIEW Project | ||||||
586190 Return | Using the myRIO Custom FPGA Project Template and Setting a File Name Prefix Creates a Broken RT Main VI When creating a project using the myRIO Custom FPGA Project Template and setting a File Name Prefix, the RT Main VI is created in a broken state. The reason for this is that the Open FPGA VI Reference Function is configured to point to an FPGA VI without the prefix included in the FPGA VI filename. Workaround: Modify the Open FPGA VI Reference Function to point to the correct FPGA VI.
| |||||
588221 Return | When Adding an Existing myRIO Target to a LabVIEW Project, with the FPGA Module Installed, the Target Only Works with the Default FPGA Personality If an existing myRIO target is added to a LabVIEW Project with the FPGA Module installed then the target will only work with the Default FPGA Personality. The High Throughput VIs will load broken because the target will remain in the default personality. Workaround: Add a new, generic target or device to the project, and then connect to the device after it has been added.
| |||||
Miscellaneous | ||||||
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
| |||||
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
|
Document last updated on 5/22/2017