Execution order of Multiple Numeric Limit Test?

[KimMortensen]

Norbert

Haven’t tried it in other versions of TS than 2010

'works as intended' was when I was changing it to Numeric Limit Test instead of Multiple numeric Limit Test and got the correct reply

a) I was hoping that it wasn't necessary to make a new steptype. I already have plenty as it is

b) That is the obvious solution, bus it is not possible in MAX to write an equation

c) Hope that it has sent come to that

[dug9000]

Kim,

I recommend you do what Jiggwax suggested and do one of the following:

Either:

1) Split things up into two steps, the first step should just be an action step that gets your array of measurements from your code module storing them in a local variable and then in its post-expression, does the scaling you desire. Then the second step should be a None Adapter specified Multinumeric limit step. In that step change the data source setting on the data source tab to refer to your local variable rather than Step.NumericArray.

Or:

1) in the adapter configuration dialog, unhide the sequence adapter, then use that with the mulitnumeric limit step type, passing your array of measurements (i.e. Step.NumericArray) as a parameter to the sequence, then inside of the sequence use an action step to get the data into the parameter and either its post-expression, statement step, or other steps to do your scaling.

Hope this helps,

-Doug

[Norbert_B]

I am sorry that 'works as intended' was an expression easily misunderstood.... i just spoke out of the view of a TestStand developer used to the mechanisms of TestStand. I understand that the behavior is not that what you want to have. But purely from TestStand view, it would be a serious problem if it work like you suggest.....

Regarding two of your answers, i don't really understand them:

b) "but it is not possible in MAX to write an equation": MAX is the abbrevation for Measurement and Automation Explorer. You cannot interface to MAX directly using MAX such way, that you receive measurement values. So i assume that you used MAX to configure a measurement and use e.g. LV to read those values. Scaling has to be done in the code module of course (so in this example LV).

c) "Hope that it has sent to come to that" What do you mean with this sentence?

thanks

Norbert

[KimMortensen]

Normally I would prefer to do the scaling of my tasks in MAX but it doesn't support that formula I am using for this purpose.

I will try what Jiggwax an others are suggesting

Norbert

I misunderstood what you were saying

[Al.B]

Hi,

If there are not too many limits in the step (since this method requires that each limit's data source is specified manually), another possible solution would be to simply change the Data source in the limits tab to the desired calculation:

Also, Ray, what changes would you propose to the Order of Actions table?  Because the numeric limit step uses a post-step substep to evaluate results (as opposed to evaluation in the status expression in "regular" steps), the resulting behavior is indeed different, but the order of execution within the step is the same. Am I missing something?