Sequence steps not updated with custom step module function parameter changes

[MrPonny]

With TS 2.0.1 when I change a custom step's function parameter list (e.g., local reference to a station reference) these changes are not reflected in steps already used in a sequence. I know the answer is already in the knowledge base but I can't find it.

[Kevin L]

Hello,

When you make changes to a custom step type in TestStand 2.0.1 there are a couple ways to make sure the most recent version of that step type is loaded into TestStand. First, if you open a sequence file that contains a step type which is of a different version than the one currently loaded in one of the .ini files, a “Type Conflict in File” message box will appear. In this dialog box you will want to choose the “Use currently loaded type” option.

Another way is if you go the properties page of a custom step type in the type palette, you will see an option that says “Apply changes to all loaded steps of this type.” You will want to make sure this box is checked if you are making changes to any of the steps properties.

I hope that this information is helpful, and feel free to reply back to this thread if you have any follow up questions.

Regards,
Kevin L.
Applications Engineer
National Instruments

[MrPonny]

I tried this and it works most of the time, except when you change a parameter in the module call. For example, let's say my custom step calls func1(int Param1) where I assign StationGlobals.MyParam to be passed as Param1. I then use this step in a sequence. Later on I decide I want to pass StationGlobals.YourParam as Param1. When I make this change in the custom step and reload the sequence TS indicates a type conflict and I resolve it by choosing to use the updated custom step. However, the new parameter is not used in the sequence steps.
This is an acknowledged bug in TS 2.0.1. I dealt with this about 2-3 years ago and I know there is a work-around procedure, I just can't remember what it is. Maybe somebody can...
jcl

[RayFarmer]

Hi,

Instead of placing your code module in the Specify Module, use the Post Step substep. Set the Specify Module back to None.



Regards
Ray Farmer