Problems with Thorlabs controller BSC103

[John.S]

I'll try this. Thanks.

[nyc_(is_out_of_here)]

I see now what they are doing.

Ignore my previous post.

You might want to read the earlier posts about serial numbers. There seems to be some confusion about which one is the one to use, but it was clarified by the person from Thorlabs.

[John.S]

OK. and yes, I read that post. The relevant serial numbers are those that appear in their 'APT User' software front panels and not those on the hardware. I'm also working with Thorlabs tech support. Again, thanks for looking into this. I'll post the solution if and when this is solved. 

[John.S]

I believe that I solved my problem. It was not a LabVIEW code problem but an incorrect choice of ActiveX control. When presented with a choice of ActiveX controllers to fill the ActiveX container, I chose the 'APTPZMotor' control. I should have looked further down in the alphabetical listing. The correct ActiveX control for the ThorLabs BPC203 APT Piezo Contoller is evidently called 'MGPiezo.' 

Thank you for your trouble nyc, it kept me on task & helped me think this through.

[nyc_(is_out_of_here)]

I am glad you got it working. 

[Jolyon]

I have had a similar problem to that discussed for the BSC103.  i.e. the APT Active X component wasn't recognising the serial number I was sending it using the property node.  

It turns out that you need to send the entire 8 digit serial number and then it works fine.  I had been sending it the last 6 digits due to a big red note in the user guide (page 46 of HA0143T rev9, Nov 18 2010).   See, that's what happens if you RTFM!!