I contrloling an RTX equiped stage in a non-queue mode, but I think lab view is adding on a queue about 3 high

[Russell Pirlo]

The problem is that im using Image recognition to control the movement, and i am sending a command to move to a point based of the image, but before this is fed to the stage, another image recognition is performed and this is going to the stage as well, so everytime im overshooting about 3X the distance, because before the stage is moved. I am using a non-queue mode with this stage, which should discard any in action command, for the next, but i dont think this matters because i think labview is late to send them to the stage, and it finishes the moves before it gets them from labview. Besides for playing with delays (ive tried but, i really want a smooth program, and this isn't happening with delay adjustment) how might i keep this queue from building up in labview?

[s_a_s]

Russell,

I'm not sure I completely understand your question.  From what I can gather you are doing some image processing on some event and based upon the results of that processing you are sending a command to your motor to do some type of move.  The problem is that  your motion commands are not executing in the the manner you would like (ie timing problems).  Is ths a correct assessment of the problem?

A few other questions:

1. Are you using the National Instruments drivers for Vision and Motion?
2.What are the software versions you are using?
3. What type of image processing are you doing?
4. What type of move are you having your motor perform?
5. What specific VIs are you using to send the commands to the motor?
6. What is the "non-queue mode" you are referring to?
6. What are your timing constraints?

Thanks,