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.
The LabVIEW 2013 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The following items are known issues in LabVIEW Robotics 2013 sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 187287 Return | Example Finder sometimes crashes when you click 'Find related examples' in the LabVIEW Help. An error sometimes occurs when you click the Find related examples button in LabVIEW Help topics. This causes the Example Finder to close and display the message "Error 1077 occurred at Property Node (arg 1) in 70-manage main listbox update.vi → Find Examples.vi". Workaround: Restart the Example Finder.
| |||||
| 187772 Return | Performance of AD* VI slows over time If significant changes occur to the map the AD* VI operates on and the VI is configured to mange the epsilon value automatically, the VI runs significantly slower over time. Workaround: Try one of the following:
| |||||
| 192403 Return | Some examples open with unsaved changes. When you close certain Robotics example files, LabVIEW prompts you to save changes to the VI even if you did not change the VI. Workaround: When the Save Changes dialog displays, click the Save button. Saving the VIs will not harm them.
| |||||
| 194428 Return | No warning returned when you specify a remote filepath that doesn't end in .pgm in the Capture Image VI When you use the Capture Image VI to capture an image and specify a filepath and filename at which to save the image, the filename must end with .pgm. However, if you do not use the correct .pgm extension, LabVIEW gives no warning. Workaround: Define filepaths that end with .pgm.
| |||||
| 194486 Return | Cogmation VIs may not work in Starter Kit if .NET is not installed. Some Cogmation VIs require the .NET 2.0 Framework to work currently. Workaround: Install the .NET 2.0 Framework.
| |||||
| 207367 Return | Starter Kit will reboot constantly if LabVIEW 2009 is not installed and no DHCP server is available If the Starter Kit is configured to obtain an IP address via DHCP and there is no DHCP server available then its behaviour is as follows: If LabVIEW 2009 is installed on the sbRIO: the network uses a private IP in 169.254.x.x range If LabVIEW 2009 is not installed on the sbRIO: the network fails to obtain an IP address and reboots Workaround: Setting the IP reset dip switch and rebooting will force the IP address to 0.0.0.0. Allow at least 15 seconds for the network to be initialized before switching the IP reset switch off. Then use the Hardware Setup Wizard or MAX as usual.
| |||||
| 211258 Return | Uninstalling LabVIEW Robotics removes some License Files The installer for the LabVIEW Robotics Bundle and Starter Kit hides all inactive licenses that exist on the system and replaces them with the LabVIEW Robotics bundle license. When LabVIEW Robotics is uninstalled, the bundle license file is removed and you will be unable to use any product which was licensed through a file which was hidden. Not all licenses will be hidden, the vast majority of times only includes the licenses installed by the LabVIEW Robotics product. Any NI Software previously installed on the system that has been and either activated or previously launched (even once for evaluation) will not be affected. Workaround:
| |||||
| 356420 Return | Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name Workaround: Move the manifest file to a new location
| |||||
| 406186 Return | Error -2147220308 in Hardware Setup Wizard when Connecting to Zynq Target Zynq targets require all web features to be installed to be recognized by the Hardware Setup Wizard. If a Zynq target has been reformatted these features will removed, and error -2147220308 will be thrown in the Hardware Setup Wizard Workaround: In NI MAX install all web features and then restart the target.
| |||||
| 410068 Return | Hardware Setup Wizard has Slow Target Discovery Time It can take much longer to discover targets in the Hardware Setup Wizard. Workaround: N/A
| |||||
| 414047 Return | LabVIEW Crash if Project is Closed before Robotics Simulator is Stopped If a VI is still running that uses the Robotics Simulator, and the LabVIEW Project is closed, LabVIEW will crash. Workaround: Avoid closing the project while running the simulation service.
|