From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Skipping a step through porpertyloader

Solved!
Go to solution

Hi all,

 

If I skip a step by importing an excel file with porperty loader, the sequence file is marked as modified.

It's not the case with other porperties.

Is it normal?

does it exist a solution to work around?

 

Thanks in advance for your help

 

0 Kudos
Message 1 of 3
(883 Views)
Solution
Accepted by topic author maxmont

Hi all, I answer to myself with a solution.

So, there is a bug in propertyloader. If TS.Mode pproperty is modified, the sequence file is marked as modified even during sequence execution.

To work around, in my propertyloader, I modify TS.mode property only if "IsUsingTool" is True. If "IsUsingTool" is false, I use SetRunModeEx function.

 

if (propertyLoaderContext.IsUsingTool == true)
{
   LoaderObject LoaderObjectMode = StepLoader.LoaderObjects["TS.Mode"];
   LoaderObjectMode.PropertyObject.SetValString("", 0, "Skip");
}
else
{
   propertyLoaderContext.TargetSequenceFile.GetSequenceByName(SequenceName).GetStepByName(StepName, StepGroups.StepGroup_Main).SetRunModeEx("Skip", propertyLoaderContext.SequenceContext.Execution);
}

0 Kudos
Message 2 of 3
(839 Views)

Hi all,

 

I have the same problem when a change a sequence call arguments value.

The property loader changes properties and the sequence file is marked as modified even if propertes are modified at runtime.

And in this case, there is no workaround.

Does this issue be known? It it already identifed and fixed?

 

Thanks in advance for your help

 

0 Kudos
Message 3 of 3
(821 Views)