Archived: LabVIEW 2013 myRIO Module Known Issues

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.

Panoramica



This document contains known issues for the LabVIEW 2013 myRIO Module. 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 2013 myRIO Module sorted by Date.

378032 myRIO Controller may not be discoverable on machine with many items in the domain search list
406307 myRIO cannot be discovered over USB on Windows XP and Windows Server 2003
406934 Reset VI might output error -63195 if FPGA VI is not initialized
406943 SPI Express VI may cause jitter in real time applications
407080 Activation of myRIO suite may fail if myRIO controller is plugged in during activation
409244 Installing the myRIO software suite to a Unicode path causes the installer to crash
411446 System Configuration Restart VI will return a timeout error if IP Address of myRIO changes during reboot
412285 Certain USB devices plugged into myRIO will not show up in MAX because Linux already has a driver for them
412315 Formatting a myRIO Controller in a virtual machine causes it to be undiscoverable
412530 When bridged to a network the IP Address reported by the myRIO USB Monitor may be incorrect
413077 Cannot reconnect to myRIO if USB is unplugged while running
413415 Asynchronous serial VIs may timeout when WIFI disconnects
413847 myRIO USB Monitor will not always display after being unplugged and plugged back in on Windows Vista



ID Known Issue
378032

Return
myRIO Controller may not be discoverable on machine with many items in the domain search list
On machines with many items in the domain search list as well as multiple network adapters the myRIO controller may not be discoverable.

Workaround: Reduce the number of items in the domain search list. Information on configuring the domain search list is available here:http://support.microsoft.com/kb/275553

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
406307

Return
myRIO cannot be discovered over USB on Windows XP and Windows Server 2003
National Instruments uses a 3rd party USBLAN driver to create a virtual ethernet connection over USB to communicate with the NI myRIO. This driver is not installed by default on Windows XP and Windows Sever 2003.

Workaround: The driver files are installed on your Host PC and you can install it manually by following this procedure: 1. On your Windows XP or Windows Server 2003 PC, launch Device Manager 2. Find your NI myRIO [NI-myRIO-19xx-] under Other devices 3. Right click the device and select "Update Driver" 4. Select Install from a specific location 5. Enter path "C:\Program Files\National Instruments\CompactRIO\Staging\USBLAN\XP" Windows might warn you regarding lack of Windows Logo testing. Click continue. Windows should successfully install the driver and the NI myRIO US Monitor should pop up.

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
406934

Return
Reset VI might output error -63195 if FPGA VI is not initialized
Using the Reset VI may output error -63195 if FPGA VI is not initialized. This is most common when using only UART Express VI's which do not open the FPGA reference.

Workaround: Set up your application to ignore the -63195 error thrown by the Reset VI if your application only uses the UART Express VIs

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
406943

Return
SPI Express VI may cause jitter in real time applications
Using the SPI Express VI may cause jitter in real time applications. Slower SPI clocks will cause worse jitter.

Workaround: Don't use the SPI Express VI in time critical loops.

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
407080

Return
Activation of myRIO suite may fail if myRIO controller is plugged in during activation
The myRIO controller creates a virtual NIC when it is plugged into a computer. This virtual NIC can change the computer ID used for activation causing licensing errors after rebooting the computer.

Workaround: Unplug the myRIO Controller from the computer and run NI License manager to activate software

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
409244

Return
Installing the myRIO software suite to a Unicode path causes the installer to crash
Installing the myRIO software suite to a Unicode path causes the installer to crash

Workaround: Choose a path without Unicode characters

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
411446

Return
System Configuration Restart VI will return a timeout error if IP Address of myRIO changes during reboot
System Configuration Restart VI will return a timeout error if IP Address of myRIO changes during reboot

Workaround: Ignore the timeout error

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
412285

Return
Certain USB devices plugged into myRIO will not show up in MAX because Linux already has a driver for them
USB devices like the Hokuyo USB LIDAR when connected to an RT-Linux target, cannot be detected in MAX because Linux already has the cdc-acm class driver for it.

Workaround: Use Linux console commands to unload the driver already on the controller

Reported Version: 13.0.0    Resolved Version: 5.4    Added: 08/04/2013
412315

Return
Formatting a myRIO Controller in a virtual machine causes it to be undiscoverable
When formatting a myRIO from a virtual machine it is possible that the controller will not be discoverable in MAX after the controller reboots.

Workaround: In the virtual machine settings, disconnect and reconnect the myRIO.

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
412530

Return
When bridged to a network the IP Address reported by the myRIO USB Monitor may be incorrect
When bridged to a network the IP Address reported by the myRIO USB Monitor may be incorrect.

Workaround: Use the target name to connect to the target instead of the IP Address

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
413077

Return
Cannot reconnect to myRIO if USB is unplugged while running
If the USB for the myRIO is unplugged while running a VI with a front panel open it is possible to get the controller into a state where LabVIEW cannot reconnect to the controller and receives an Äccess Denied" error.

Workaround: Reboot the controller

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
413415

Return
Asynchronous serial VIs may timeout when WIFI disconnects
Asynchronous serial VIs may timeout when WIFI disconnects

Workaround: Use synchronous serial VIs instead of asynchronous or increase the timeout of the asynchronous serial VIs

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013
413847

Return
myRIO USB Monitor will not always display after being unplugged and plugged back in on Windows Vista
myRIO USB Monitor will not always display after being unplugged and plugged back in on Windows Vista or Windows Server 2008.

Workaround: N/A

Reported Version: 13.0.0    Resolved Version: N/A    Added: 08/04/2013

Document last updated on 7/22/2013

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