Archived: LabVIEW SoftMotion Module 2014 f1 Bug Fixes
Updated Mar 17, 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.
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.
The following items are Bug Fixes in LabVIEW SoftMotion Module 2014 f1.
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.
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.
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.
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.