Standard Limit Tests

Besides the LTT limit test you can - of course - still use all other TestStand standard limit tests.

LTT Limit Test Mixed

When using standard limit tests you can not easily access GUI configured limits (XML). Read here about how to do it.

In the picture above you see some examples of TestStand standard limit tests. Besides of the step name starting with an error number in square brackets, you are free to name your limit test step what you like. Yet, you are encouraged to name the step according to the pattern {signal name} @ {limit name} if applicable.

When using standard limit tests you still should supply at least an error number in [square brackets] at the beginning of the step name. Like with the error number you configure in GUI's F5 dialog, you need to make sure not to use duplicate error numbers.

Standard limit tests with error numbers will be shown in GUI's F6 dialog, where you can provide an error limit for them. Please be aware, that those TestStand only error numbers get added to the GUI but not removed if you remove them in TestStand. However, you can manually remove them in F6 dialog.

The limit test step with the yellow exclamation mark (!) in the picture above is still valid, however you will not be able to configure an error limit in GUI's F6 dialog, since it has no error number.

The limit test step with the red exclamation mark (!) in the picture above is invalid and will result in an error, which will stop the station. The reason is that this limit test step is using an error number [1001] which is already in use by a different limit test step.

If you run your LTT testplan in TestStand you will notice some "process result" steps inserted after each TestStand standard limit test. Those are automatically inserted by the LTT process model and are needed for the result processing. If they bother you, you can remove them via TestStand menu Configure > Remove Result Processing Steps.

TS Menu Remove ResProc

LTT Limit Test Mixed ProcRes