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.
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 2013 myRIO Module sorted by Date.
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
|
Document last updated on 7/22/2013