Changing the test limits & passing waveform in Labview OI problems

[EricLu]

Hi all:

I have some problem with using labivew OI....

 Question 1: Is it possible to change the test step limits within Labview simple OI ??I only know to give "thiscontext (sequence reference)" as input to vi and use set property function to modify these parameter if the vi is part of teststand step.

Because I need to allow user to modify the limits by their test criteria, and the action will not be one of the step of the sequence.

How could I do that? Question 2: How to pass the waveform data to labview simple OI?I save the data to Teststand local variable "waveformData"(Type: LabviewAnalogWaveform which is a cointainer type)and pass the seq reference by PostUIMessageEX.I'm sure that the TS local variable has data within it, just in the labview OI, the variant to cluster function seems not work for me.....Don't really know my code is correct or not  Anyone have the idea how to solve the problem or how to pass the waveform data?? Thanks in advance.

Regards,

 

Eric

 Attach pic: the part of code of getting waveform from teststand (variant to cluster).  

[~jiggawax~]

Hey Eric,

Question1-  There is no nice way to say this but it is considered bad practice to customize your OI to a specific sequence.  It should be that your OI should be able to handle almost any sequence thrown at it.  It would be better for you to add the limit changing to a callback or part of the sequence.  Is there a reason you cannot make it part of the sequence?  It could be in the Setup or one of the PreUUT callbacks. 

Now that I've put a disclaimer on this you can do it in the OI.  However you will still need a step in your sequence that passes the sequence context using the PostUIMessageEx.  Then whatever the user has set as the limits in your OI you can still use the set property function to modify the limits because you'll have the sequence context. 

Question2-  I have attached one way you can do this.  Don't know if it's the best way but it works for me.

Let me know if you have any questions.

Regards,

[EricLu]

Hi, jigg:

I'm doing that because of the end user don't have their "final" limitaion values for the test yet.

Because the DUT is still under "RD" process, the limitation may change some other day but not every test.

Also it's pretty annoying if the msg box pops up every time the sequence executes.

So i'm thinking to allow user to select they will modify the value or not b4 the sequence execution.

And for question 2, the solution you gave me are also works fine for me.

Just i can not understand why the container type doesn't work if both Teststand and Labview have this type "Cluster".

Because it's bad once I have to send lots of data type at once...

Really thanks for your reply and the information you gave me 🙂

Best Regards,

Eric 

Message Edited by EricLu on 10-28-2008 08:23 PM