How to setup a labview-vi to create a numeric result using error-output

[OnlyOne]

Hello,

i inserted some instrument teststeps from a downloaded library like initialize.vi, reset.vi, close.vi.

Currently they are running as Action.

What do i have to do that they also execute in NumericLimitTest so that i get a result?

Something like a Post-Expression: Step.Result.Numeric = Step.Result.Code

Is this all?

Thanks

[Beutlich]

When you placed the Action step, you should have placed a 'Numeric Limit Test' step. This would give the options you want.

[OnlyOne]

Yes, i already did this.

My question is more like: What do i write into Step.Result.Numeric? Is it a good idea to use Step.Result.Code or are there better variables?

[Beutlich]

The "Step.Result.Numeric" is meant to be the result of some test that will undergo the Limit comparisons. Store any measurement or variable that is a result of the test you are running.

"Result.Error.Code" is part of the error status of the step. I'll wire the error cluster from LabVIEW to the Result.Error, and then the 'Code' field refers to the error generated.

You can read NI's verbage about them here.

[Beutlich]

Here are some pictures. I made a random VI, but you would have your own:

Then I configure the step to run the code, and stick My Result into the Step.Result.Numeric.

That's really it. I leave the Data Source as Default. I've seen some people stick logic in here, but I like defaults so I stick any conversion logic into LabVIEW if I can.

[OnlyOne]

The VI does not  have a result that can be checked as in your example.
As posted in the first message it is about the initialize.vi, reset.vi, close.vi.

I need to change he type of teststep from action to Numeric limit test and for this i need a variable that can be used for the result.

Using a PostExpression with Step.Result.Numeric = Step.Result.Error:Code is also no possible as if an error occurs the Teststand stops testplan and does not execute the PostExpression...

[Beutlich]

If you have a variable that you want to use that already has a value before executing the step, then I recommend you put that variable as the DataSource:

This effectively ignores the Step.Result.Numeric, and uses your variable instead for the limit comparison and reporting.

If you want to use the error code from the VI, and you don't want the step to fail, I can think of two methods to do this:

1) don't put the error into the Step Error.

When you select a VI, TestStand automatically connects the error wire out to the Step.Error, but you can change this. Change the values in the Module tab of the VI like this:

This means the error information will not be treated as an error for logging purposes, only used in a Numeric Comparison.

2) Using a PostExpression with Step.Result.Numeric = Step.Result.Error.Code and disabling the error reporting on the step.

Just like you are thinking, you can set the Numeric to be equal to the Error code in the post step. Then you can prevent the step from throwing an error in TestStand by disabling that feature for that step:

With this enabled, the step will ignore the value in Step.Result.Error, so you can put whatever you want in that field.