PDFKnown Issues by Date
The following items are known issues in LabVIEW Robotics 2010 sorted by Date.
| 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:
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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:
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
Document last updated on 7/26/2011
