NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

How to use the Custom Multiple Numeric Limit Test found on this site?

Hi

I used the Custon Multiple Numeric Limit Test, that can be found on this web site, with TestStand2.0.1. The problem is, that I updated to TS3.0 and for some reason I cannot get that custom step to work. I simply don't remember how I did it the last time... I made a copy of the "normal" multiple numericl limit test. The problem is, that I can't get the "Edit Limits..." menu option to work. I'd like to use this custom step, because it enables the use of variables (locals) as low and high limits. So, if anyone has experience with this, please help. Or if anyone has a simple solution for the low/high limit from variables, please contribute.

Aleksi Sandqvist
0 Kudos
Message 1 of 9
(4,370 Views)
Hi,

The trouble is the Multiple Numeric Limit Test now has extra properties.

Open the NI Types palette and expand the tree view for Multiple Numeric Limit Test step type and copy the new properties, then open your palette and expand the tree view to your step type, paste the new properties into your step type. This will resolve your problems.

Alternatively,
Use the 'Combine with' your step type with the new NI Multiple Numeric Limit Test. You will have to delete the extra Edit and Post sub step from the newly created step type. And also mess about renaming step types. But both methods will resolve your problems.

Regards
Ray Farmer
Regards
Ray Farmer
0 Kudos
Message 2 of 9
(4,370 Views)
Hello Aleksi -

Do you remember the exact name of the example program you downloaded? There are several examples of working with Multiple Numeric Limit steps, but they are all involving additional features such as naming or limit loading. It sounds as though the example you found was related to how to configure the step which is a little different.

If you wish to use local variables as your limits, then certainly you could create a custom step type to handle this option however the code behind the Multiple Numeric Limit Test is particularly long and may give you some trouble as far as figuring out how to change the dialog. In general what you would be looking to do, either in a step Pre-Expression or inside your edit dialog would be:

(1) test to see how
many elements are in the:
Step.Result.Measurement[] array

(2) for every element, look inside to find your Limits container and set the value equal to some variable, for example:
Step.Result.Measurement[0].Limits.Low = Locals.Measurement_0_Low

There are likely several alternate solutions to this problem, I will keep an eye out to see if there is any archived example program that matches your description not currently live on our website.

--Regards

Elaine R.
National Instruments
http://www.ni.com/support
0 Kudos
Message 3 of 9
(4,370 Views)
Hi Elaine!

Your way is actually as good as the Custom Step I was looking for. Thanks! Here's what I'm going to do:

- Numeric limit test: Measure the Vcc. Store in local variable.
- Multiple Numeric Limit Test: In the pre-expression, count the +/-5% low and high limits according to the Vcc.

Do you know a way to do this; I want to show the user a front panel, that would be updated with test results. For example, If I had three steps in a test sequence: "Show front panel.vi for user", "measure 6 voltages, update them to the first step front panel", "measure 2 current, update the results to the user panel". How would I do this? I just want basicly a "running" list of things I'm testing. I DON'T want 10 popping front panels, just one with all the r
esults from different TestStand steps?

Thanks in advance,
Aleksi Sandqvist
0 Kudos
Message 4 of 9
(4,370 Views)
Hi Ray!

I actually tried the "NI resolution", which was to to alter the limits in the pre-expression. I want to adjust some voltages, that I'm going to measure, according to the Vcc. Worked fine. Here's what I'm going to do;

- Numeric limit test: Measure the Vcc
- Multiple Numeric Limit Test: In the pre-expression, adjust the low and high limits according to the Vcc.
- and so on...

but Ray, I didn't actually get the step we talked about in the last message, so here's my situation:

All type.inis are default. I don't have any custom steps from the old TestStand on my computer. (Why? That's what I'm thinking myself...) First I copied the NI_MultipleNumericLimitTest from NI_Types.ini to MyTypes.ini. The result was three items: NI_MultipleNumeri
cLimitTestm PostSubstep, EditSubstep. Then, I chose "paste" again and had an item called NI_MultipleNumericLimitTest_Copy. Now, this is the item (step /test) that I want to edit. Could you please go it through step-by-step from here...

Best regards,
Aleksi
0 Kudos
Message 5 of 9
(4,370 Views)
Aleksi,

You could use a LV notifier, each step could then send its results via the notifier to the Show front panel VI. There are examples in LaBVIEW example folder for using the notifier.

Regards
Ray Farmer
Regards
Ray Farmer
0 Kudos
Message 6 of 9
(4,370 Views)
Hi Ray

The notifier is a good idea, but here's the problem: The front panel would have to be some kind of a loop that loops until all result have been received. So, how do I make it work? Right now, the first step (show the panel) has to be "finished" before any actual measurement steps can be run?

And thanks for the speedy answer 🙂

-Aleksi
0 Kudos
Message 7 of 9
(4,370 Views)
BTW, Ray, I'm doing this with TestStand3.0 and LabView7. It would be easy to do this with only LV, but I have to use TestStand to manage the whole test sequence.

-Aleksi
0 Kudos
Message 8 of 9
(4,369 Views)
Aleksi,

No problem, either launch your front panel vi via VIServer setting to return without waiting
or
pop your step in a Sequence, then you can run the step as a SequenceCall as a New Execution. Then before you can finish your execution by Killing the New Execution.
Or better still use your notifier to close your Front Panel.
(Note: I thought in TS3.0 you could now call a Step in a New Execution without requiring it in SequenceCall. Mayby I am confusing myself with running a LabVIEW Adapter in the runtime engine.)

Hope this helps
Regards
Ray Farmer
Regards
Ray Farmer
0 Kudos
Message 9 of 9
(4,369 Views)