Archived: LabVIEW SoftMotion Module 2014 f1 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.

Aperçu



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

ID Fixed Issue Issue Details
  Scaling velocity with NI ISM or SMD devices results in unexpected behavior. The units for commanded velocity  incorrectly specified rev/second. This has been corrected to be configured as steps/second.
485347 The Calculate Anti-Res Coefficients example VI has a broken run arrow. An example VI that shipped with LabVIEW 2014 SoftMotion Module was not functional. The example now functions as expected.
485535 Using unbound axes causes LabVIEW to hang. Using an unbound axis would cause LabVIEW to hang when SoftMotion tried to locate a required resource. The instability has been resolved and unbound axes should function as expected.
420789 Deployment error when deploying Create Motion Reference VI to an RT target. LabVIEW would present a deployment error when deploying all instances of a polymorphic VI without a valid SoftMotion license, even if the particular instance did not require a license. License enforcement has been corrected to apply only to instances which require a license.

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