Controlling Aerotech's AVL125 w/ Labview - Error 1172

[ChetM]

I'm working with a Aerotech stage (Model # AVL125) and have a problem with my labview program. The purpose of the program is for the stage to oscillate for a certain period of time and return a graph which maps the velocity time and amplitude of the oscillations. Using the labview samples provided in Aerotech's Soloist program files (primarily Oscillate.vi and PlotScopeData.vi), I was able to piece together what I believed to be a program that could carry out this function. Everytime I input values for the oscillations, I hit run and watch the stage move for a split second, but shortly after I get a 1172 error in labview. I have attached the error message and my program. I'm not sure how .NET works and program primarily in C++ and Java. If someone could clarify what exactly the issue is or what I can do to fix it, that would be much appreciated. I'm new to the forums so if this question or something similar has been asked, redirection is also helpful.

Thank you 

[LaThoS]

Hi ChetM,

Unfortunately I can't find the problem as the code calls many Aerotech SubVIs that aren't attached.

If you could post these that would be helpful (at least Disable.vi, and possibly Oscillate.vi - as I think this will help solve the problem of the stage stopping moving so early).

Thanks,

Laurence

[ChetM]

Thanks for the response. The error is occuring at the Disable.vi. Here are the block diagrams for Oscillate, Disable, and Disconnect.

 

[ChetM]

Here are the actual VI's

[LaThoS]

Hi ChetM,

Unfortunately the 1172 error means that there is a problem calling the .NET assembly that the Aerotech drivers use. As I am not familiar with these assemblies I do not know what would cause the conflict that is occurring.

Do the Oscillate and Plot Scope Data examples work on their own? I have a feeling that the Plot Scope VI might not be waiting for the oscillations to finish before continuing on to the Disable and Disconnect VIs, and as the Oscillate works in a background thread, this causes it to terminate early. The error may be caused by the fact there is still an operation (Oscillate) being performed when you try to disable the platform. A possible solution, if this is the case, may be some sort of loop structure around the acquisition VIs that stops after the oscillations have finished.