Archived: LabVIEW 2012 SP1 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.


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

IDFixed IssueIssue Details
329767The Reported Velocity is incorrect for certain axis types.If you are using an NI 951x axis, an AKD EtherCAT axis, or an unbound axis, the reported velocity does not correctly use the Steps Per Unit setting in the Axis Configuration menu.
330144The Solve Profile method can fail on moves that have an acceleration greater than the deceleration.The Solve Profile method may fail on a move with a much faster acceleration than deceleration. On a real-time target, NI SoftMotion returns error -77108 (NIMCDM_parametersDefineImpossibleMove). On Windows, LabVIEW may crash.
335246A Velocity-Time contour move must have a velocity change between move segments.When doing a Velocity-Time contour move with the Solve Profile method, you will get error -77108 (NIMCDM_parametersDefineImpossibleMove) if you have two consecutive move segments with the same velocity.
349494After a system reboot or system re-initialization, the position error limit is not properly scaled using user units.After rebooting, the position error limit uses the default scaling, and does not take into account any user-specified unit scaling.
356868User-defined variable axes cannot easily switch between single and periodic position compare.User-defined variable (UDV) axes should be able to use the Periodic Position Compare FPGA VI to perform both periodic and single compare operations by using a period of 0 to enable a single compare. However, a period of 0 is not currently supported by the NI SoftMotion Module.
357667Relative to capture moves do not work on user-defined variable (UDV) axes.When performing a relative to capture move with a UDV axis, the move always occurs as if the capture was at position 0.
369535The Position Compare FPGA VI does not work properly when using the Digital Output polymorphic instance.When you enable position compare, the compare output resets.
370414Inverting the Drive Command Output on the NI 9514 or NI 9516 can cause the Drive Command signal to continuously output +10V or -10VWhen you have the "Invert" button checked on the "Drive Command" page of the Axis Configuration dialog and the Drive Command output of the NI 9514 or NI 9516 goes to either +10V or -10V, it is possible that the Drive Command will stay stuck at one of these values. This will cause your motor to spin out of control.
371917The Current Limit Algorithm FPGA VI only clamps positive currents and can clamp the current at the wrong value 
376990The Spline Engine and Step Generator FPGA VIs in the Motion » NI SoftMotion » Advanced palette don't work when dropped from the palette.You can drop these VIs on your block diagram and compile a bitfile, but they do not give you the correct outputs.
378476NI SoftMotion for SolidWorks does not work if only LabVIEW and the NI SoftMotion Module 2012 are installed.When only LabVIEW and the NI SoftMotion Module 2012 are installed, you will see errors about missing deployment plugins when trying to deploy a SolidWorks project item.
380860Using multiple NI 951x modules in Scan Interface mode can sometimes cause fault 8130: NI 951x Heartbeat Communication Fault.This fault most often occurs when deploying new settings to the module, but can also occur when switching from Configuration mode to Active mode.

Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  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).