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.
Each Issue appears as a row in the table and includes these fields:
Issue ID—Contains the number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
Legacy ID (optional)—Contains the legacy CAR ID, if an issue has a legacy ID from NI's legacy/deprecated bug reporting database. This ID appears on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).
Issue Title (in italics)—Describes the issue in one sentence or less.
Problem Description—Describes the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
Workaround—Provides possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
Reported Version—Contains the earliest version of NI Motion Assistant the issue was reported in. If you discover the issue appears in an earlier version of NI Motion Assistant than is reported in this field, you can report that to NI (contact information below) to have the field updated.
Resolved Version—Contains the version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
Date Added—Contains the date the issue was added to the document (not the reported date).
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
The following items are known issues in NI Motion Assistant 2013 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Graphical User Interface | ||||||
| 188126 Return | Cursor disappears when interacting with the position and velocity plots. Workaround: None.
| |||||
| 237934 Return | NI Motion Assistant can crash if you press buttons too quickly. Pressing any button or combination of buttons faster than about 5 clicks per second can cause NI Motion Assistant to crash. Workaround: None.
| |||||
| PVT | ||||||
| 201636 Return | NI Motion Assistant PVT interpolations cause increasing acceleration oscillations with increased profile length. In applications where velocity is not held constant, as NI Motion Assistant performs a contour move using a PVT file, over an extended contour the acceleration term begins to oscillate. The oscillation increases the longer the move profile is. Workaround: None.
| |||||
| Script Execution | ||||||
| 134221 Return | Running a script for multiple days may cause NI Motion Assistant to crash. Workaround: None.
| |||||
| 206181 Return | Returning the move to the origin in NI Motion Assistant can cause improper behavior. When using NI Motion Assistant to perform a series of blended straight-line moves to create a square, returning to the origin coordinate of (0,0) can cause an improper dip in velocity on the the last straight-line move. Workaround: If the final move returns to 1,1 rather than 0,0 the moves will blend properly. Alternatively, the square can be created moving in a counterclockwise direction.
| |||||
Document last updated on 8/2/2013