Migrate SoftMotion Code to New SDI Plug-in

Updated Aug 23, 2018

Reported In


  • LabVIEW SoftMotion Module

Issue Details

My project controls a 3rd party motor drive over EtherCAT using SoftMotion’s SDI Plug-ins. I would like to change to a different brand of motor drive that also uses SDI Plug-ins. What do I need to change to convert my code?


Because you are using SDI Plug-ins to connect to your motor drive, the migration process is relatively simple. The only major change you will need to make is in the initialization section of your code, where you bind your SoftMotion Axes to your motor drive.
To migrate your code from one SDI Plug-in to another, you should do the following:
1) Verify that the new SDI Plug-in is compatible with what you need your system to do.
2) Install the new SDI Plug-in from the LabVIEW Tools Network.

3) Remove the old drive from your LabVIEW Project and add the new drive as an EtherCAT slave.

4) Re-bind the SoftMotion Axes to the new hardware by right clicking as shown below:

5) In the initialization section of your code, replace the old SDI Plug-in VI with the new one, as shown here:


6) Run and test your program on the new hardware.

Additional Information

For best results, you should limit each project to working with only one type of SDI Plug-in. Multiple types of drives that use different Plug-ins should not be used in the same project.

For more information about SDI Plug-ins, a list of currently-supported drives, and links to download each plug-in, see
the NI White Paper entitled Using EtherCAT Motion Drives with NI Real-Time Controllers. Each plug-in also contains documentation included in a readme file in the VI Package download.


Not Helpful