Parameters specified by step do not match the settings of the sequence

I just upgraded from Teststand 4.1.1 to 4.2 and have encountered this

problem during the review of the existing sequence files.

When I open a file of sequence, select any stage of type sequence call, which calls another sous-séquence

in a different sequence file, I learned that the parameters used do not correspond to those required.

To be more precise, in the settings area of the stage, a red exclamation symbol appears at the side of the

subsequence called step, and the ToolTip is displayed when the mouse pointer is

hovered over the exclamation point States:

"Parameters specified by the step do not match the settings of the sequence."

The ToolTip goes on to explain how to solve this problem by clicking on the exclamation symbol.

I find also that by deselecting the "Prototype using sequence" tab in step Settings\Module

solves the problem.

When the sequence is executed, no problems occur with execution, the test performs correctly.

Is it possible to clear this error for each sequence call not in one operation?

Thank you

Gary.

My apologies to attach a file of sequence buggy. I forgot to pass a parameter to the LoadPrototype method to preserve existing settings. I have attached a corrected version of the sequence file. I changed to update SequenceCall not only because of potential problems, reloading the DLL prototypes.

I would try to explain why you see cela TestStand 4.2. The additional results feature, we added to TestStand 4.1 needs to know what parameters are entered, output and input/output (i.e. what settings is pass by reference). Before TestStand 4.1, step of calling sequence does not store this information but rather dynamically got it and it appears in the column how go. Now that we store the past by reference with the step option, you can have an inconsistency between the option stored in step and the current setting of the sequence called. This inconsistency affects only additional results and not execution. TestStand 4.1, the sequence editor to not warn you on these inconsistencies. We have added the TestStand 4.2 warning so that you will have the correct information for additional results.

When TestStand 4.1 or 4.2 load a file of sequence from a pre-version 4.1 version, TestStand sets cervical optionally reference true for all parameters in the call sequence steps. This is why you see the warning for any sequence calling step created TestStand 3.5 If no parameters are not passing by reference. You can also see the problem if you change the option collar called a reference parameter in the sequence.

Tags: NI Software

Similar Questions

Maybe you are looking for