Archived: abVIEW 2011 NI SoftMotion Module Bug Fixes

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.

Überblick

This document has been archived and is no longer updated by National Instruments.

The following items are the IDs and titles of a subset of issues fixed between the LabVIEW 2010 SP1 NI SoftMotion Module and the LabVIEW 2011 NI SoftMotion Module. If you have a CAR ID, you can search this list to validate that the issue has been fixed.

Bug Fixes

The following items are Bug Fixes in NI SoftMotion Module 2011.

ID Legacy ID Fixed Issue Issue Details
133066 - The Control Loop (Fixed Point PID) used in the Axis Interface FPGA VI can cause the motor to oscillate around the target position. Due to rounding errors in the Control Loop (Fixed Point PID) VI, it is possible to generate position commands that "backtrack" 1 encoder count or step (i.e. 100, 100, 99, 100, 99, 100, 100, 101, 100...).
170110 - Error -2132869095 occurs in large EtherCAT motion systems. Error -2132869095 occurs in large EtherCAT motion systems when transitioning from configuration mode to active mode. The transition completes successfully, but the error message box creates concern.
186332 - Executing a Function Block inside of a functional global variable does not work. You cannot use NI SoftMotion function blocks with functional global variables. Doing so will result in the VI not being deployed to the RT target.
225222 - On an AKD axis, Clear Faults must be called twice to clear the fault state in some cases. Attempting to clear a fault before the cause of the fault is resolved results in needing to call Clear Faults twice to clear the fault state after resolving the fault.
256062 - Changing the names of axes in a coordinate can lead to errors in the Interactive test panel. Changing the name of axes used in a coordinate can lead to unexpected behavior in the form of difficult to clear errors in the Interactive test panel. When you change the name of the axis, NI SoftMotion updates the coordinate containing it with the new axis name. However, immediately going to the Interactive test panel on the renamed axis does not deploy the coordinate, so the NI Scan Engine fails to transition to Active mode with error -77112 (NIMCDM_axisInCoordinateNotFoundError). Closing interactive and deploying the coordinate still returns this error in the Interactive test panel as the system is in Configuration mode and the old error has not been updated and cleared.
303800 - Executing a Function Block inside of a functional global variable does not work. You cannot use NI SoftMotion function blocks with functional global variables. Doing so will result in the VI not being deployed to the RT target.

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).