Don't know where to start

[steph33h]

I want to create a Labview program to control a pair of Zaber Technology motorized stage (T-LS model: http://www.zaber.com/products/product_group.php?group=T-LS). Zaber has a Labview demo that allows me to give specific commands to the stage, but it can't do what I need.

Here's what I need to do:

I want to use two stages in conjunction with each other to scan a specified dimension in two axes (so the stages need to communicate with eachother). I will mount a sample to the stages and have the sample move a specified range in one axis (call it the x-axis) and then shift up a small distance in the z-axis to start the x-axis scan again in the opposite direction. I need to be able to specify the dimensions (x-axis and z-axis range) and the time spent at each step in the scan. The whole process should be automatic so that I can input the dimensions and time spent on each point and then hit a go button and let the motorized stages go through the whole scan.

[Maca]

Your link is broke, it should point here: http://www.zaber.com/products/product_group.php?group=T-LS .

What have you done so far?

What have you been able to do?

What are you having trouble with?

What do you want us to do? (and don't say all of it)

Post the code you have completed with a better description of the problem you are having, and we will try to give you some pointers.

[Don Kirkby]

Hi, this is Don from Zaber Technologies.

Your timing is good, because I just spent the last few days writing a new set of labview demos for controlling our devices. The demo now lets you enter a list of commands, and it will execute each command and wait for a response before sending the next command.

As for adding a delay after each command, here are three options:

1. Leave the new demo as is. It waits for a response and then immediately sends the next command.
   
2. Add a delay after each command, but make it the same delay every time. To do that, add a sequence frame inside the inner loop of the demo with all the current code in the first step and a timer in the second step. Wire a constant to the timer.
   
3. Add a custom delay after each command. Do the same things as for the previous option, but also add a delay field to the request cluster. Then you'd have to unbundle the cluster inside the loop, rebundle the pieces that the MakeRequest subvi needs, and pass the delay to the timer in the second step of the sequence. Hopefully you don't need to go that far.
   

I'm still working on the new demo, so it's not published yet. I'll send you the work in progress, and I'll publish it here when it's done:

http://www.zaber.com/wiki/Software

I'll probably link to a separate Labview tutorial page from there. If anybody is looking for it in future and can't find it, just ask at our contact page:

http://www.zaber.com/contact/

[Don Kirkby]

Since my previous post, we've gone through the process of publishing a certified LabView Instrument Driver. You can download the driver in Labview from the Help menu: Find Instrument Drivers.... Search for the keyword Zaber, select the driver, and it will be installed automatically. You can also download it directly from the Instrument Driver Network:

http://sine.ni.com/apps/utf8/niid_web_disp...04400144F1EF859

You can find installation instructions and tutorials on our wiki:

http://www.zaber.com/wiki/Software/Labview_Driver

By the way, the certification process was really helpful, and didn't cost anything. I highly recommend getting certified for anyone publishing an instrument driver.

[Gabi1]

QUOTE (Don Kirkby @ May 5 2009, 07:50 PM)

By the way, the certification process was really helpful, and didn't cost anything. I highly recommend getting certified for anyone publishing an instrument driver.

Both as a developer and a big user of LV drivers from a lot of instruments, I cannot agree more!

those amateur engineers who thinks their instrument communication protocol is so unique it should be hidden under piles of password protected LV files that are buggy, badly written and lack features, should be shot on spot!

[Grampa_of_Oliva_n_Eden]

QUOTE (Gabi1 @ May 5 2009, 02:54 PM)

... I cannot agree more!

those amateur engineers who thinks ...., should be shot on spot!

Put the mouse down and slide away from the keyobard. We don't want anyone getting hurt! Have you ever tried to clean blood out of a keyboard?

Ben

[jcarmody]

QUOTE (neBulus @ May 5 2009, 03:39 PM)

Put the mouse down and slide away from the keyobard. We don't want anyone getting hurt! Have you ever tried to clean blood out of a keyboard?

Ben

The blood isn't the issue; bone fragments make it a bigger job than it would otherwise be (just rinsing in a mild H2O2 solution...)