LabVIEW 2018 SoftMotion Module Bug Fixes

Overview

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

IDFixed IssueIssue Details
621339SoftMotion Set Plugin Mode VI does not have detailed help availableThe Set Plugin Mode VI offers no detailed or context help to explain which actions take place when called.
643434SoftMotion Drive Interface (SDI) Axis position cannot be reset following a home moveAfter a homing sequence on an SDI Axis, the EtherCAT drive will report a position of 0. SoftMotion will display an axis position error of the last known position. This position error cannot be reset with the Reset Position method.
667021SoftMotion Set Plugin Mode VI does not transition to Configuration mode if an error is passed to the error inputThe error handling inside the SoftMotion Set Plugin Mode VI does not correctly discard input errors and will fail to transition to Configuration mode if an error is passed to it.
685409Using more than 16 SDI Axes may fail to transition to Active modeFor most SDI Plug-ins, using more than 16 SDI Axes on one controller will fail to transition to Active mode.
667023Manually changing an SDI Axis operating mode may cause a position jumpSDI Axes can operate in four move modes (homing, velocity, torque, position). While operating in homing, velocity, and torque modes, the position setpoint is not updated in SoftMotion's trajectory generator. When switched back to position mode manually the position error is calculated as the last known position and the current feedback position and causes the axis to rapidly change position.
612846SoftMotion Express VIs cannot be used with more than one coordinate resourceWhen using the SoftMotion Express VI API to command moves with Coordinate Spaces, do not wire two different Coordinate Spaces to the resource input of one Express VI.
639822LabVIEW RT can crash when property nodes of different resources are called in parallelWhen repeatedly calling property nodes in parallel for different SoftMotion resources, LabVIEW RT can crash. The chance of this happening is low and is mitigated by calling SoftMotion property nodes in series.
645028UDV Axes fail to link when containing subset of another axis nameWhen using the UDV Axis type, the axis names must be unique identifiers without repeating a subset of the name. For instance, Axis 1 is contained in Axis 10, and Axis 10 will not behave correctly if used in the same project.
640148Duplicate examples for the 9501 module in LabVIEW Example FinderThe Example Finder contains duplicate lists of examples for the 9501 stepper drive module. This is cosmetic, as one half of the examples will open, and the other half will fail to open.
657386SoftMotion Read or Write Digital Line does not range check for out of range index valuesUsing a negative line index for the SoftMotion Read or Write Digital Line Express VI or method will cause LabVIEW RT to crash.
657377Ethernet Stepper Read Digital Line on SMD-761x drives gives bad dataThe SMD-761x Ethernet Stepper drives provide additional digital inputs compared to the ISM-741x Ethernet Integrated Stepper Motors. Digital lines X4-X8 do not provide correct data.
654932NI 9503 example code will result in SoftMotion fault 8780 if run for an extended period of timeThe FPGA code contained in the NI 9503 example projects has the maximum jitter value set too low and will eventually fault if left running for an extended period of time.
667024After a Find Reference Move, a SoftMotion Axis will not correctly enable gearing when commandedFollowing a Find Reference Move on an axis, SoftMotion will not transition the operating mode of the axis back to position mode. This prevents the Gear In method from executing.
667009Read Analog Data does not throw an error when used with an Ethernet Stepper axisEthernet Stepper Drives do not support the Read Analog Data method. Read Analog Data will return a value of 0 instead of an error if used with an Ethernet Stepper axis.
676856SoftMotion returns Error -77124 when commanding an axis move following a coordinate contour moveWhen executing a series of moves (a coordinate straight line move and a coordinate contour move, followed by an axis straight line move), SoftMotion will return Error -77124.
679833LabVIEW RT will crash if two SoftMotion closed-loop stepper axes both encounter an unrecoverable stallThe SoftMotion stepper drive interface axis type can be configured for closed-loop behavior. If the position error during a move exceeds the threshold for an unrecoverable stall on two axes at the same time, LabVIEW RT will crash.
680471SoftMotion Gain Tuning Panel does not correctly set the Acceleration Jerk and Deceleration parameters of a straight line moveThe SoftMotion Gain Tuning Panel allows straight line move parameters to be set directly, but the Acceleration Jerk and Deceleration parameters will be reversed.

 

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