VI broken Labview/Kinesis - M30XY - Set Velocity Step/M30XYConnectSetVelocityStep.vi

[Micro-Sandworms]

Hi,

The vi requires the dll Thorlabs.MotinoControl.Controls.dll
I installed the kinesis software, and I tried to provide as new path the corresponding dll that I get upon installing the software. That did not solve the problem. It seems that the dll that comes with the latest installation of the software is no longer compatible.
I get the following warning that might help to identify the kinesis software that was working with it:

C:\Users....\Downloads\M30XYConnectSetVelocityStep.vi (M30XYConnectSetVelocityStep.vi)
- The .NET assembly expected to be at "C:\Users\fmovagharnemati\OneDrive - THORLABS Inc\Desktop\github\M30XY\Thorlabs.MotionControl.Controls.dll" was loaded from "C:\Program Files\Thorlabs\Kinesis\Thorlabs.MotionControl.Controls.dll".
- Expected Assembly "Thorlabs.MotionControl.Controls, Version=1.14.50.23230, Culture=neutral, PublicKeyToken=c7ec6d6d6e2435e7", but found "Thorlabs.MotionControl.Controls, Version=1.14.56.25920, Culture=neutral, PublicKeyToken=null."

Thanks you in advance for looking into this

[movagharnematiThorlabs]

Hello Luis.
Thank you for your interest in our line of motion products and associated LabVIEW examples.
The issue you are experiencing has to do with improper project setup.
You must ensure you are accessing the VI functionality through a project that properly maintains DLL dependencies.
When VIs are run outside a properly configured project, they attempt to use hardcoded DLL paths from when they were originally created.
Try the following steps which on my side allowed me to use the same VI in a new project with version 1.14.56.25920 DLLs without needing to update the VI itself.

Setup a directory for the new project on Windows Explorer.
Create a New Blank Project using the LabVIEW Explorer.
Save the New Project to the directory aforementioned.
From your Kinesis installation folder, use the 'Thorlabs.MotionControl.Kinesis.DLLutility' executable, mark the target directory as the project directory, and ensure the dropdown for 'Required Project Type' is set to 'LabVIEW (with UI)'.
In the project explorer save all for the project.
Place the VI into the project directory.
In the project explorer save all for the project once again.
Drag the VI from the directory to the project explorer to add it to the project, and save once again.

At this point you can check the dependencies of the VI through the project explorer, and see the required DLLs are the ones saved to the project directory, which should be of whatever Kinesis version you have installed instead of the versions used when the VI was created.