Print
PDFOverview
This document contains known issues for the LabVIEW 2012 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 2012 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
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 2012 Robotics Module 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.
|
|||||
| 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
|
|||||
| 361585 Return |
Configuration file for Rough Road environment is not correct. The collision height of the ground in Rough Road is higher than the actual ground. Workaround: Set the value of X,Y, and Z SGL to zero in the Rough Road.xml environment file.
|
|||||
| 362399 Return |
Loading some DAE model files can cause LabVIEW to crash DAE files saved by certain programs can cause LabVIEW to crash when loaded. If the material tag is missing in the DAE file this crash can be seen. Workaround: Include the material tag in the DAE file.
|
|||||
| 357648 Return |
Built Executable of Robotics Simulation VIs may prompt user to give location of LVODE.dll Built Executable of Robotics Simulation VIs may prompt user to give location of LVODE.dll even if it is located in the applications data folder. Workaround: Specify the location of the LVODE.dll each time the executable is run.
|
Document last updated on 7/27/2012
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).