LabVIEW Robotics 2010 Known Issues

Publish Date: Aug 10, 2011 | 0 Ratings | 0.00 out of 5 |  PDF

Overview

This document contains the LabVIEW Robotics 2010 known issues that were discovered before and since the release of LabVIEW Robotics 2010. 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.

Fields

Each known issue includes these fields:
  • Issue ID
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of LabVIEW the issue was reported in
  • 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)

Other Known Issues

The Known Issues for LabVIEW 2010 Platform can be found in the LabVIEW 2010 Platform Known Issues document.

Known Issues for other products in the Robotics Bundle

LabVIEW Development System

LabVIEW Toolkits PID and Fuzzy Logic Toolkit

LabVIEW Toolkits System Identification Toolkit

LabVIEW Real-Time Module

LabVIEW FPGA Module

LabVIEW MathScript RT Module

LabVIEW Control Design and Simulation Module

LabVIEW Statechart Module

NI Vision Development Module

LabVIEW 2010 NI SoftMotion

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. If you have feedback on this document, please contact NI on this NI Developer Zone post.

Windows 7

National Instruments is committed to maintaining compatibility with Microsoft Windows technology changes. However, NI has become aware of a number of issues of potential significance regarding Microsoft Windows 7. To learn how Windows 7 affects your use of NI products, visit ni.com/info and enter the Info Code windows7.

Known Issues by Date

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

187772 Performance of AD* VI slows over time
194486 Cogmation VIs may not work in Starter Kit if .NET is not installed.
195458 Skilligent Object Tracking Example VI may inaccurately reflect tracking state at startup
211258 Uninstalling LabVIEW Robotics removes some License Files
238691 Cannot deploy the Starter Kit Roaming executable as a start-up application
233753 The Hardware Setup Wizard installer upgrades incorrectly
236687 Serial Arm visualization VI's incorrectly treat prismatic joints as revolute joints.
247214 Starter Kit startup executable cannot be built when LabVIEW is in evaluation mode
277023 No Valid Path Exists output of A* doesn't indicate when no path is found
244642 If the velocity setpoint goes beyond +/- 32 rad/s, the direction of the motor will reverse
246660 Apply/Get Steering Velocity VIs does not allow selection of specific wheels
277086 Sick LMS 2XX Series example hangs if baud rate isn't 9600
282482 LabVIEW Robotics examples not linked from LabVIEW Help
241835 Starter Kit Roaming example uses the wrong wheel separation value
292411 Error -2318 on first run of 3D Mecanum Robot example
305272 Get Velocity from Wheels VI with a differential frame is numerically incorrect when used on RT targets



ID Known Issue
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
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
195458

Return
Skilligent Object Tracking Example VI may inaccurately reflect tracking state at startup
The Skilligent Object Tracking Example VI uses event based programming to monitor which sides of the dollar bill are currently being tracked. On the user interface, there is a checkbox for the front side, and one for the reverse, as well. When these values are changed, the event structure executes, and the subscription is modified, so that the VI is now tracking the specified models. The problem is that the VI doesn't check the state of the checkboxes until there is a change. So, if a user configures the checkboxes before running the VI, the subscription will not actually be modified until the state of one of the checkboxes is changed again.

Workaround: Run the VI before configuring any of the checkboxes.

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

Return
Cannot deploy the Starter Kit Roaming executable as a start-up application
When you try to deploy the Starter Kit Roaming executable as a start-up application, you get the message "The Real-Time application has not been built. You must build the application before deploying."

Workaround: Please see the following KB for instructions on how to resolve this issue.

Reported Version: 2010    Resolved Version: N/A    Added: 07/29/2010
233753

Return
The Hardware Setup Wizard installer upgrades incorrectly
The Hardware Setup Wizard may not run if NI LabVIEW 2009 Robotics or NI LabVIEW 2010 Robotics is uninstalled from a machine that had both versions on it.

Workaround: Perform a repair on the NI LabVIEW 2010 Robotics Hardware Wizard through Add/Remove Software.

Reported Version: 2010    Resolved Version: N/A    Added: 09/24/2010
236687

Return
Serial Arm visualization VI's incorrectly treat prismatic joints as revolute joints.
The Convert to GRobot VI mistakenly identifies a prismatic joint as a revolute joint

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 10/07/2010
247214

Return
Starter Kit startup executable cannot be built when LabVIEW is in evaluation mode
The "Starter Kit Roaming" startup exe cannot be built when LabVIEW is in evaluation mode, which is always the case with the Starter DVD. The only reason the build doesn't work is because the "Remove unused polymorphic VI instances" option is checked in the Additional Exclusions page.

Workaround: Open the "Starter Kit Roaming" build specification, then uncheck "Remove unused polymorphic VI instance" in the Additional Exclusions page.

Reported Version: 2009    Resolved Version: N/A    Added: 10/07/2010
277023

Return
No Valid Path Exists output of A* doesn't indicate when no path is found
NaN, infinity or a negative number is used as a cost value for a cell in the occupancy grid, the No Valid Path Exists output of A* doesn't indicate when no path is found.

Workaround: Do not use NaN, infinity or a negative number as a cost value for a cell in the occupancy grip.

Reported Version: 2009    Resolved Version: N/A    Added: 12/06/2010
244642

Return
If the velocity setpoint goes beyond +/- 32 rad/s, the direction of the motor will reverse
When writing velocity setpoint to the motors, the direction of the motor will reverse when you go beyond +/- 32 rad/second.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 06/20/2011
246660

Return
Apply/Get Steering Velocity VIs does not allow selection of specific wheels
Apply Velocity to Wheels VI and Get Velocity from Wheels VI always perform their calculations on all wheels in a steering frame. This prevents the VIs from being used for cases where some wheels are used for driving and others are used for encoder feedback.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 06/20/2011
277086

Return
Sick LMS 2XX Series example hangs if baud rate isn't 9600
If the baud rate of the LIDAR sensor is initially set to a value other than 9600, the example hangs if a reset command is sent to the sensor.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 06/20/2011
282482

Return
LabVIEW Robotics examples not linked from LabVIEW Help
When opening an example from LabVIEW Help, the Robotics examples give an error stating the example is not installed.

Workaround: Navigate to the examples through the Example Finder.

Reported Version: 2010    Resolved Version: N/A    Added: 06/20/2011
241835

Return
Starter Kit Roaming example uses the wrong wheel separation value
The Starter Kit Roaming example initializes a steering frame object with a wheel separation of 0.2m, but the actual wheel separation on the robot is more like 0.36m. Using the wrong width value causes the robot to turn at the wrong rate.

Workaround: Within the subVI Initialize Steering Control VI, modify the wheel separation input of the Create Differential Steering Frame VI to 0.36.

Reported Version: 2009    Resolved Version: N/A    Added: 07/25/2011
292411

Return
Error -2318 on first run of 3D Mecanum Robot example
The 3D Mecanum Robot example sometimes generates error -2318 the first time it is run after being opened. This error happens when the dimensions of parameter vectors don't match in the Control Design & Simulation functions.

Workaround: Give the motor setpoints control a default value that is not an empty array.

Reported Version: 2010    Resolved Version: N/A    Added: 07/25/2011
305272

Return
Get Velocity from Wheels VI with a differential frame is numerically incorrect when used on RT targets
There is a known issue with Solve Linear Equations VI where it produces incorrect results on RT targets with certain rank-deficient matrices. This is the sort of matrix is used along with the Solve Linear Equation VI in the Get Velocity from Wheels.vi and causes it to return incorrect results on RT targets.

Workaround: Please see KnowledgeBase 5O1B6EDP article.

Reported Version: 2010    Resolved Version: N/A    Added: 07/25/2011

Document last updated on 7/26/2011

Back to Top

Bookmark & Share

Ratings

Rate this document

Answered Your Question?
Yes No

Submit