TestStand 2016 : Step Setting : An error has occurred. Save your work and restart the sequence editor.

[~jiggawax~]

Close the sequence file.

Delete the one out of the type palette.

Maybe restart TestStand?

Ensure it is still not in type palette.

Open Sequenc file.

Copy to type palette (optional)

[Vincent90]

The custum DataType cannot be deleted because is linked with stepType which return the error.

But i cannot find where is the link.

See error message attached.

Vincent

[Scott_Richardson]

Vincent -

• The issue why the step panel displays an error is that the panel is expecting that the following numeric property exist <StepType>.Limits.Nominal. The panel needs to be tolerant of the pre-2016 version of the step type.
• This is a bug that has been now reported under ID 614061.
• Until this is fixed, you can add the above property to your step type which will prevent the error described. We have not reviewed if there are any other incorrect assumptions for other properties added to the step type in 2016 that would not exist in your step type. You could consider adding all the properties added in 2016 to your step type(s).

Thanks for reporting.

[Vincent90]

Scott,

How to add "the above property" ?

In the step description expression ?

(step.result.status == "" ? ResStr("NI_STEPTYPES", "NUMERIC_LIMIT_DESCRIPTION_NAME") : ("Obtained: x = " + Str(Step.result.numeric) + 
(Step.Result.Units == "" ? "" : " " + Step.Result.Units)))  + " ; Expected: " + (Step.compexpr == "" ? (SearchAndReplace(SearchAndReplace(ResStr("NI_SUBSTEPS",Step.Comp + "_EX"),
"%hi",(Step.limits.highexpr == "" ? Str(Step.limits.high) : Step.limits.highexpr)),"%low",(Step.Limits.lowexpr == "" ? Str(Step.limits.low) : Step.limits.lowexpr))) : 
(ResStr("NI_SUBSTEPS", "COMP_TYPE_EXPR_DESC"))) + (Step.Result.Units == "" ? "" : " " + Step.Result.Units)

[Vincent90]

The problem is that Step.Limits.Nominal doesn't exist in TestStand API...

[RaymondFarmer]

This is only available if you use EQT (== +/-) comparison type.

Ray Farmer

[Scott_Richardson]

Vincent -

You should work with the developer that owns the step type if it is not you. To consider upgrading your step to include the EQT capability, you will need to add and update the properties of the SETIM_Report_CheckNumericValue step type to match what NI added or updated to the NumericLimitTest step type. The below is not an exhaustive review of the differences but this will give you an idea of what differences exist. I will look into us possibly creating a KB on this issue.

If you look in the Sequence Editor type panel view for the NumericLimitTest step type you see the following new properties:

You would have to add these properties to your step type. The specific one causing the panel error that you reported is Step.Limit.Nominal. Even with this there could be other issues, we will have to investigate further.

You would have to change your step type Step Description Expression to match the updated one in NumericLimitStep so that the step displays EQT comparison when selected by the user.

You would need to update the Status Expression in the step type to match so that new steps have the correct expression. In addition, you would have to also update all instances of the step already in any sequence file that uses the type because the status expression is a property of the step that the step type cannot control or change. You cannot use Find/Replace in Files because the status expression in steps is flagged as not editable. Updating steps will require you to either load all files that use the step type and change the step type expression and use the "Apply Changes in this Dialog Box to all Loaded Steps of this Type" option to update all instances of the step, or we will need to help you with creating a tool to programatically update status expressions in steps of that type.

Lastly, any changes to a step type would require you to update the version of your step type.

I will have to get back to you on options for a tool to help customers with this type of update to their step types.

[Vincent90]

Hello Scott,

Thanks a lot for those informations.

Do you have an estimation when the tool gonna be ready ? Will it come with SP1 versions ?

Vincent

[Vincent90]

Is it possible to keep using LabVIEW 2016 but with TestStand 2015 which will not get the issue ?

[Scott_Richardson]

Vincent -

Yes using LabVIEW 2016 with TestStand 2014 (SP1) will not have this issue.