Connect and control z921b with kdc101 without kinesis gui.

[Sms9175]

Greetings to all the Community Members,

I am a student and just started using labview with learning the basics for my experiment.

I have already tried and used the .net function to connect the kdc101 to control the z921b motor but it comes with the kinesis gui.

So is there any other way to do the same without the kinesis gui on the front panel?

I am grateful for all the help and answers. Thank You.

[jjohn1]

Yes it is possible, but takes some work.  However, if all you want to do is hide the front panel object display just move it outside the visible part of the front panel or hide it by creating a property node on the block diagram and setting its "Visible" property to false (then back to true before the VI ends).

[Sms9175]

Not just hide it in the front panel but like another method/way without using the .net function or involvement of the kinesis gui.

[Kyle97330]

You still have to use .NET but it is possible to do it without the front panel controls.

Do the following:

1. Put down a .NET constructor node

2. Choose the DLL "Thorlabs.MotionControl.Controls.dll"

3. Expand the "Thorlabs.MotionControl.Controls" section in the Objects browser window

4. Find the entry for KCubeDCServoControl

5. There should be only one entry in the "Constructors" field, "KCubeDCServoControl()".

6. Press OK

7. Add the remaining startup commands very similarly to how you would do it with the front panel control:

The reference for  "Device" is what you will use for almost everything.

[Sms9175]

I implemented the solution you mentioned but then it gives me error1172 System.Invalidoperation at the beginning of .net constructor node. 

[Sms9175]

Any help or knowledge regarding the error 1172 is appreciated. Thank You.

[Kyle97330]

95% of .NET errors are error "1172", so just that by itself is not enough.  Please copy-paste the entire error message you get.

Also, please post the VI containing the code you wrote making the error, saved back to 2019 edition or so, so we can double-check the code you wrote.

Also, it might be worth noting that at my work, the Thorlabs code we use is on the older side (with the idea that there's no need to fix what isn't broken) so it's possible new releases might have changed this functionality.