Archived: LabVIEW 2013 Robotics 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 Robotics 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.

Each Issue appears as a row in the table and includes these fields:
  • Issue ID
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of LabVIEW in which the issue was reported
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not reported date)

The LabVIEW 2013 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

Known Issues by Date

The following items are known issues in LabVIEW Robotics 2013 sorted by Date.

187287 Example Finder sometimes crashes when you click 'Find related examples' in the LabVIEW Help.
187772 Performance of AD* VI slows over time
192403 Some examples open with unsaved changes.
194428 No warning returned when you specify a remote filepath that doesn't end in .pgm in the Capture Image VI
194486 Cogmation VIs may not work in Starter Kit if .NET is not installed.
207367 Starter Kit will reboot constantly if LabVIEW 2009 is not installed and no DHCP server is available
211258 Uninstalling LabVIEW Robotics removes some License Files
356420 Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name
406186 Error -2147220308 in Hardware Setup Wizard when Connecting to Zynq Target
410068 Hardware Setup Wizard has Slow Target Discovery Time
414047 LabVIEW Crash if Project is Closed before Robotics Simulator is Stopped



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.

Reported Version: 2009    Resolved Version: N/A    Added: 12/08/2009
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:
  • Set the 'overhaul' Boolean input to TRUE periodically to discard old state data that might no longer be relevant and to increase epsilon again.
  • Use the 'epsilon' input to directly control the value of epsilon and balance the speed of the VI versus the quality of the path that the VI calculates.


Reported Version: 2009    Resolved Version: N/A    Added: 12/08/2009
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.

Reported Version: 2009    Resolved Version: N/A    Added: 12/08/2009
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.

Reported Version: 2009    Resolved Version: N/A    Added: 12/08/2009
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.

Reported Version: 2009    Resolved Version: N/A    Added: 12/08/2009
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.

Reported Version: 2009    Resolved Version: N/A    Added: 02/15/2010
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:
  1. On a Windows XP system, under the C:\Program Files\National Instruments\Shared\License Manager\License\Backup, copy everything under this directory and paste it one directory higher under the License directory.
  2. On a Windows Vista or 7 system, under the C:\ProgramData\National Instruments\License Manager\License\Backup, copy everything under this directory and paste it one directory higher under the License directory.


Reported Version: 2009    Resolved Version: N/A    Added: 07/29/2010
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

Reported Version: 2012    Resolved Version: N/A    Added: 07/13/2012
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.

Reported Version: 2013    Resolved Version: N/A    Added: 08/09/2013
410068

Return
Hardware Setup Wizard has Slow Target Discovery Time
It can take much longer to discover targets in the Hardware Setup Wizard.

Workaround: See KB (6B0A80QB): Long Target Search Time in Robotics Hardware Setup for 2013

Reported Version: 2013    Resolved Version: N/A    Added: 08/09/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/09/2013

Document last updated on 8/9/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).