How does the parameter LoadModelPluginAddons in the ModelOptions callback work?

[J.C._Andersen]

I ask this question because I am running a scenario in TestStand 2012 where I want to run one sequence file using the execution entry point "Test UUTs" which then starts another sequence file using the execution entry point "Single Pass". The first sequence file uses the Parallel model and the second uses the Batch model.

For the first sequence file I want to run a model plugin add-on but I do not want to run or even load it for the second sequence file. So in the second sequence i made an override of the model callback sequence ModelOptions and create a step which just sets the parameter LoadModelPluginAddons = False. But it does not seem to work like I expected since the model add-on sequence file is still loaded and executed for the second sequence.

Can anyone tell me what happens?

Best regards Jens Christian Andersen

[James_Grey · Accepted solution]

There is also a ModelPluginConfigurationToLoad parameter, which defaults to "".   "" is a wildcard that means load the 'active configuration' from each configuration file. Alternatively, you can specify a configuration name explicilty, such as "<Default for Inline Processing>". 

You don't edit the automatically created Addons.cfg, file, it contains only one configuration and it is named "<Addons>. Thus is will only be loaded if your configuration name is "" or "<Addons>". The LoadAddonOns parameters is a way to force the addon configuration to be loaded even if you specify some other configuration name.

So, it is not exactly for what you are trying to do, but if you can specify a specific configuration name, it will serve your purpose.

[J.C._Andersen]

Hi James.

Thank you for your reply. Now it all makes more sense and I can solve my problem 🙂 The next thing I need to do is to remember to distribute the Cfg\ModelPlugins folder to the test stations.

Thank you again and have a nice weekend