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

Overview



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

ID Fixed Issue Issue Details
319192 Certain axis properties cannot be read or written programmatically. The following axis properties can be set in the Axis Configuration page, but not programmatically from LabVIEW: Brake, Use Multiple Gain Sets, AR Filter Type, Digital Output Mapping, DAC Scaling Coeff, Analog Input Scaling units, Encoder Units, and Stepper Units. If you try to read or write these properties from LabVIEW, you will either get error -77037 (NIMCDM_invalidDataError) or -77004 (NIMCDM_invalidAttributeError).
352516 Rebinding an axis to a different hardware resource can cause parameters to be outside of the valid range. When you bind an axis to a different hardware type than what it was originally configured with, it can cause parameters to fall outside the valid range for the new hardware type.
364012 The Periodic Position Compare FPGA VI does not work correctly when the period input is 2.L When the compare period is 2 and the pulse width is 1, the period of the compare output will be 4 instead of 2. Compare periods greater than 2 work as expected.
377682 Reading faults on a remote target when no faults are present results in error -70238 (NIMC_noPropertyDataAvailable). This error is only returned when there are no faults and your motion resource is of the form nism://[Host Name]/[Axis Name], where [Host Name] is a remote target.
381344 The Pulse Width Modulation FPGA VI does not behave as expected while in a reset state. The PWM output of both the center aligned and left aligned versions is TRUE only if the duty cycle input is nonzero when the reset input goes TRUE. If the duty cycle is zero when reset input goes TRUE, the PWM output is FALSE.
382922 NI SoftMotion for SolidWorks only works with the most recent installed version of the NI SoftMotion Module. If you have multiple versions of the NI SoftMotion Module installed on the same computer and try to use NI SoftMotion for SolidWorks in one of the earlier versions, the simulation will not start. Everything will work normally in the most recent installed version.
382941 Certain limit switch configurations may cause your drive to enable when a bitfile is loaded to the FPGA. When using a User-Defined Variable Axis, if any of the limits or home switches are enabled, have a Stop Mode of Immediate, and have an Active State of On, the NI SoftMotion Engine transitions the state machine to Operation Enable when a bitfile is loaded to the FPGA. This may cause your drive to enable.
383688 The Position Capture FPGA VI cannot be used more than once in a top-level FPGA VI. This issue only applies to the Single » Digital Input polymorphic instance. One of the subVIs within this VI is set to non-reentrant execution and therefore can only be used once in a single-cycle timed loop.
402581 Moving off of a limit switch when using the EtherCAT AKD drive will cause the move to stop. When the limit switch deactivates, SoftMotion will stop any move in progress.
404298 The position feedback from the EtherCAT AKD drive can be incorrect after a data type rollover. When the data type rollover occurs, the position feedback will continually increase, even if the motor is not moving. The rollover will only happen if you are using an EtherCAT AKD and if you move the AKD in one direction for several thousand revolutions. This only affects the position feedback displayed to the user and does not affect the control loops.

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