Log MultiNumericLimit Custom step type

[logatto]

Hi, I developed a library containings some custom step types. I created the step type starting from the standarda Multiple Numeric Limit Test. In runtime the step get the sequence context and using the APIs of Teststand overwrite some parametres like:

Step.Result.Measurement[].Data
Step.Result.Measurement[].Limits.High
Step.Result.Measurement[].Limits.Low

.....

What I cannot change in runtime is the name of the measure, because it depends on line that I selected into the step type. I'd like changing the Step.Result.Measurement[XXX].Status with Step.Result.Measurement[YYY].Status in runtime.

I havo aslo another issue, but it is a little bit more complicate to explain. The step type has also an editor that the user can open in teststand sequence editor. In this editor the user can select what measure make. When the user ends configuration presses "save" on the step type editor the step should fill the pameters of the MultiNumeric limit test. Exactly the same when the user configure the test from the tab in the teststand sequence editor (attached). But I cannot do it.

Thanks a lot.

[Logan_081]

Hello Logatto,

I'm not sure what are you looking for. Are you meaning that you're not able to programmatically modify Custom Step Type's properties?

Second, I understood that you're not able to modify the step type from a shortcut menu in the sequence editor. But I'm pretty confuse about HOW your are not able to do that? Any command is missing? Warning dialog box pops up when you're attempting to select the feature? Are you able to attach any snap shot image in order to clarify which issue you're encountering?

Thank you in advance for your interest. I'm waiting for you to let me know something more. 

[logatto]

I will try to explain better. Let's focus just only on the first issue.

I developed a custom step type and it is like a multiple numeric limit test. This step has the cluster “Result” that contains the array of measures called “Measurement”. Each element of the array can have a name, I’d like to customize that name in runtime.

I attached a demo sequence that calls the VI that I use in my step types. This is just an example: two instances of the same vi that should have different measurement name.

I hope it can help.

Thanks a lot for your support.

[j_dodek]

Hi Logatto,

For setting the name you should try the Example in this link:

http://forums.ni.com/t5/NI-TestStand/Dynamic-Measurement-name/m-p/658646

Hope this helps

Juergen

[logatto]

Thanks the link has beeen very useful.

Let me ask you about 2nd issue.

The step type has also an user interface that the user can open in teststand sequence editor right-clikking on "edit". In this editor the user can select what measure make. When the user ends configuration presses "save" on the step type editor the step should fill the pameters of the MultiNumeric limit test. Exactly the same when the user configure the test from the tab in the teststand sequence editor (attached). But I cannot do it.

Basically I should configure a Multiple numeric limit test not from the TestStand editor but into a Labview VI. In this case I will not have the SequenceContext because TestStand is not running.

Thanks a lot.

[j_dodek · Accepted solution]

Hi Logatto

You wrote: ...In this case I will not have the SequenceContext because TestStand is not running.

You will have a SequnceContext. It is the the Current Context of your Sequence you are editing.

So just pass "ThisContext" to the vi in Edit-SubStep of your Step-Type.

Now you should be able to access the Step-Property and do your stuff.

For more TS-User perfomance please visit and rate this Idea : http://forums.ni.com/t5/NI-TestStand-Idea-Exchange/Ability-to-create-user-built-in-StepTypes/idi-p/1...

Regards

Juergen

[logatto]

Very good.

It didn't work because in runtime I used as reference "ThisContext" and in edit mode I used as reference"RunState.SequenceFile" (because the "IncChangeCount" property). I added the reference "ThisContext" also for the edit mode and it works!

Thanks a lot.