LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Communicating with Thorlabs BSC201

Solved!
Go to solution

Hello,

 

I am trying to use LabView 2011 to communicate with a Thorlabs BSC201 stage (disclaimer: I am new to Labview). I am following the guide on: https://www.thorlabs.com/Software/Motion%20Control/Kinesis/Kinesis-labview.pdf

 

The only thing I'd like to do is get the current position of the stage, which is outlined on p. 18 in the manual. However they are using a different control box, and the functions are different for my model. When I right click on the Device property / Create / Method I would expect to see a method called GetPosition or similar, but I can't find it in the list of methods (see attached png file). According to the Thorlabs Kinesis API manual this method should be available for the BSC201.

 

Is there any way I could search for methods that would for some reason to be visible on this list?

I have attached the VI in case it is useful.

 

Thanks!

 

Download All
0 Kudos
Message 1 of 6
(4,928 Views)

Do you need to install driver software?

 

 

.

0 Kudos
Message 2 of 6
(4,906 Views)

You should have a method available called GetPosition or GetXPosition or something simliar to that. Page 18-20 of the manual you attached shows the method they recommend.  The motor I used is different but there are only a couple driver options to choose from.  Also, feel free to call Thor Labs.  They were very helpful, and free.

 

I have attached the setup I used a while back.  Hope it helps

0 Kudos
Message 3 of 6
(4,899 Views)
Solution
Accepted by topic author JohnNearby

I've used one of these before.  The trick is that the device is of the same family as the BSC202 and BSC203, which are multi-channel devices and therefore require an extra step before they get to the actual device reference.

 

BSC simple.PNG

VI attached in 2011.  Note that you'll need to change the serial number there to match your own. Also, depending on which motor you have attached the constant reference to "GenericAdvancedMotorCLI" might need to be a different class.

 

Vimes, you're using the old ActiveX code there, not the newer Kinesis code.  That's why it's different.

Message 4 of 6
(4,889 Views)

Thanks a lot, that fixed it!

0 Kudos
Message 5 of 6
(4,868 Views)

@Kyle

 

Thank you very much for your code, this works very well when I run it alone, however, every time when I integrated it into my other part LabVIEW program, I will have the following error.

 

FYI, I dragged the node from your code to mine, and they loaded from the same Kinesis Controls in the same folder location.

 

Thank you very much,

 

Pacino

0 Kudos
Message 6 of 6
(3,309 Views)