Including Limits, Measurements in Simple Operator Interface UI

[BAY]

Dear Experts,

I am in the process of modifying OPerator Interface such at that it must also display Low Limit,High Limits,Measured Value, Units. I am sure that it is possible only through expressions. I want this Limit columns value to be updated during runtime i.e., it must display the same value as we use to enter using Edit limits for Numeric test, Measured value should be the value in Step.Result.Numeric or Step.Result.NumericArrya.

I could just manage to create a parameters in each Sequence & Subsequence Parameters.Limits.Low, Parameters.Limits.High,,Parameters.Limits.Unit & just hard code the values in these. But for Parameters.Measurements i could get values in runtime using RunState.Sequence.Parameters.Measurement. I know this is not more efficient way. This might work only for Action, Numeric Limit.

For reference i have attached Simple OI Top Level.vi(where i have made some modifications) all other supporting files you can find in TestExec.llb. I hope i have explained my problem. If anyone find any confusions in understanding please let me know.

If someone tried this before please share your knowldege. Expecting your greatest support.

regards,
Bharat

[Adam B.]

Bharat,

You can include these values, but a couple things were tripping you up. The first is the fact that you want to use the step properties of each step, so instead of putting in Parameters.Measurement, you really just need to put in Step.Result.Numeric, etc. This however only gets you halfway there, as you will still get a message that this value does not exist for all steps. I've rewritten your attached VI to check to see if the step is a Numeric Limit step and if so, then get the High and Low Limits, the measurement, and the units. A sample of this for anyone who doesn't want to open the example is:
(TypeOf(RunState.Step) == "NumericLimitTest") ? Step.Limits.Low : ""
This line assures that the step is indeed going to have the value, and then retrieves the value, otherwise it does nothing. Hopefully, this modified example gets on the right track, but if you have any further questions, feel free to repost. Thanks and have a great day.

Adam B.
Applications Engineer
National Instruments

[BAY]

Dear Adam,

Thanks for your prompt reply. However, i could not open the vi you have attached since it is LV 7.1 & the version i am using is LV7.0. Also this can work only if step is Numeric Limit test.

But if i also have Multiple Numeric Limit test this might not work. Is their a way that a single expression must check whether the step is Numeric Limit or Multiple Numeric Limit & must take their corresponding limits. Please advise

Please reload your modifications in LV7.0. I want to see the VI to proceed further.

Thanks & Regards
Bharat

[Adam B.]

Bharat,

Attached you will find the OI saved for 7.0. Let me know if you have any problems loading it.

As far as using it for multiple numeric limit tests, you could certainly build that into the expression. The only reason that I didn't on the original example was that I felt that it would require that you have multiple columns for each of the items so that you could fully see them. You could always have something like:
(TypeOf(RunState.Step) == "NumericLimitTest") ? Step.Limits.Low : ((TypeOf(RunState.Step)) == "NI_MultipleNumericLimitTest") ? RunState.PreviousStep.Result.Measurement["Measurement 0"].Limits.Low : "")

Which would first check if it is a Numeric Limit Test and if so pass one sort of data, then check if it is a Multiple Numeric Limit Test and if so pass another set of data and finally, if none of the above, then pass nothing. Let me know if this generates more questions for you. Thanks and have a good one.

Adam B.
Applications Engineer
NI

[BAY]

Dear Adams,

Thanks for heading me in right direction. However i could not open your attached vi. I receied some error dialog while trying to open your attachment. i have attached the error dialgo for your reference. i suspect the problem could be the version of TS i am using. I am using LV7.0 & TS3.0.

I need your help again to load me the vi.

Thanks & Regards!
Bharat. A

[BAY]

Dear Adam,

Thanks for your support until now. But could you reload the files in LV7.0 & TS3.0. I cannot open your examples since it is in LV7.1 & TS3.1.

Eager to see your modified expression. Kindly upload it at your earliest convenience.

thanks & regards,
bharat

[Aaron B.]

Hello Bharat,

Adam is out of town right now. It looks like the error you are getting is occurring because you do not have the TestStand 3.0 UI controls installed for LabVIEW. You can check this by making sure that you have a TestStand subpalette in both your Control Palette and Function Palette. If you do not, you can go to "Start >> Settings >> Control Panel >> Add/Remove Program". Find the entry "National Instruments Software" and click "change". Find "TestStand 3.0" in the list of NI software installed on your computer. Click on "modify". This will launch the installer. Follow the steps and make sure to enable support for LabVIEW 7.0 (there is a step with a tree of features that you choose to install).

I took the liberty of saving the latest VI that was posted to my computer. I opened it with LabVIEW 7.0. This was verified by going to the "About" LabVIEW Dialog box that displays the version. I was running on the TestStand 3.0 engine. Besides the fact that you can only have one engine active on a computer at a time, I added a message popup to my TestStand 3.0 Front End Callback so that it would display when an instance of the engine is created. I did save the VI again and am not attaching it to this post. It should certainly work with LabVIEW 7.0 and TestStand 3.0 if everything is installed correctly.

Thank you for contacting National Instruments. Take care and good luck!


Regards,

Aaron B.
National Instruments