03-10-2020 08:03 AM
I set this function and I have the same problem. I share my configuration if i did a mistake
03-11-2020 03:31 AM
You could also try using "Break on step failure". This way you can decide whether to go on with the execution or repeat the step.
Obviously, this is only practical for debugging - for operator use I would suggest to implement a "first-pass-exit"-loop over (few!) crucial steps to minimize operator interaction.
03-11-2020 07:23 AM - edited 03-11-2020 07:23 AM
Yes it's a good idea, I already had thought in that but I can't believe that test stand does not contemplate my situation. I think is a typical situation