Automatic update sequence files

[mitulatbati]

Hi all,

we have a simple step type, which will be usen in some hundreds of small sequence files.

We have changed the step type, as we added some variables, and in the Specify Module dialog we have defined the variabla-table new.

Now we want to update all the sequence files automatic. In the "Tools menu -> Update sequence files" there is a possibility, but it adds only the new variables to each instance of the step type, and doesn´t update the table, which we changed in the Specify Module tabe in the step type editor. If we open the updated file again, and go to Specify Module on an instance of the step type, we get the message "The prototype of the VI changed. The parameter information wil be updated to reflect the new prototype." 

But the changes, what we have done in the Step Type editor, are not done to the instance.

The question is: how to update the step types?

regards

MB

[Johann.Wagner]

Best way ist search for StepTypes Parameter in whole sequence (file(s)) and then set it explicit e.g. with Statement (see Screenshot)

RunState.Sequence.Main["Action"].TS.SData.ViCall.Parms

e.g. RunState.Sequence.Main["Action"].TS.SData.ViCall.Parms["Sequence Context"].ArgVal="Locals.Test123"

[Manooch_H]

Hi MB,

The problem here is that you create the custom step type and specified your code module as a Default Module. Default Modules are called at the first creation of the step but are not updated from changes to the definition of the step type. A better option would have been to call your code module as a Post-Step Sub-Step. Sub-Steps are unique to their specific step type and are updated with each change to the definition of the step type. For a more in depth explanation see the second post by AllenP to the following thread:

http://forums.ni.com/ni/board/message?board.id=330&requireLogin=False&thread.id=6610 

You could either create a tool using the TestStand API to find each instance of the step type, then specify the new code module for each instance, and finally update the parameters in the Variables Table. However, in the future, if you want this behavior I would suggest creating a custom step type with the None Adapter specified as its only adapter, the Specify Module option disabled, and your specific code module called in the first Post-Step Sub-Step of the custom step type.