Home Support Documentation Bugs

Archived: LabVIEW NI SoftMotion Module 2011 SP1 f1 Bug Fixes

Updated Mar 10, 2020

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.

Overview



The following items are the IDs and titles of a subset of issues fixed between the LabVIEW 2011 SP1 NI SoftMotion Module and the LabVIEW NI SoftMotion Module 2011 SP1 f1. 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 LabVIEW NI SoftMotion Module 2011 f1.

IDLegacy IDFixed IssueIssue Details
316298-The NI 9502 shipping examples sometimes fail to move the motor.The Hall Angle Calculator VI does not always return the correct rotor position. This can cause the wrong motor coils to be energized, which can cause the motor to not rotate.
323429-The Spline Interpolation FPGA VI does not work with the Catmull-Rom spline type. 
338086-The PI Current Loop FPGA VI does not work correctly.The Voltage Output output of the PI Current Loop VI can become unstable and oscillate between positive and negative values. This occurs most often when either the proportional gain or integral gain contributions are too high.
338791-The Pulse Width Modulation FPGA VI does not consistently produce a 100% duty cycle.When the Alignment input of the Pulse Width Modulation VI is set to Center Aligned, the maximum possible duty cycle is less than 100%. The maximum possible duty cycle depends on the PWM frequency. A PWM frequency of 20 kHz allows for a maximum duty cycle of greater than 99.95%.
343677-Deleting then re-adding an AKD EtherCAT axis with the same name causes the target to crash on deploy. 
Back to top

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