M505.6PD Wait for Axes to stop: Accuracy and poll time question

[riraheta]

I have written a program in Labview to contorl an M505.6 PD linear stage.  After moving the stage, I notice that for a very small amount of time, the stage seems to be "settling" into the target position.  This settling occurs even after I have received a "true" value to the query  "stopped?". 

Increasing the Polling Cycle Time lowers the amount of "settling" that occurs after receiving a value of "true".

My question is, is there any place I can find more information about this settling that occurs or perhaps someone has encountered this before and has concluded the minimum polling cycle time required to prevent settling given some sort of parameter.

Please let me know if there is any more information I can give that would help.

[Lemongrab]

Hello riraheta,

It would be helpful if you could provide a link to product page for the motor on the manufacturer’s website. It would also be helpful if you could find and post the datasheet and/or user manual here for everybody’s reference.

You say you have observed this settling behavior, which sounds like a physical phenomenon. It is probably best for you to also contact the motor manufacturer. They will be more familiar with the internal design of the motor and its expected performance behavior, so they might be able to explain this settling behavior.

Otherwise what functions are you using? Are you using functions provided by the motors manufacturer? Some companies provide LabVIEW function libraries with VIs they have written specifically for their hardware. Or are you using the NI-Motion driver?

[riraheta]

http://www.physikinstrumente.com/product-detail-page/m-505-702000.html  I am using the m505.6pd

http://www.physikinstrumente.com/index.php?id=543&eID=dam_frontend_push&docID=4697  This is the manual for the stage I am using. 

I am using the labview drivers that came with the program.  The controller I am using is the Mercury c-863

The functions are called MVR.vi and waitforaxestostop.vi

[Lemongrab]

Hello riraheta,

While somebody here may have an answer for your question, I strongly recommend contacting the motor’s manufacturer for answers. They will be the most familiar with this product since they designed the motor and wrote the software. I wish I could provide more help but I am unfamiliar with this 3^rd party product.