12-12-2016 04:13 AM
Hi,
we have in some systems the problem that sequences sometimes take a lot longer than usual (like 200ms instead of 100). It happens sporadically in various places and one thing these places seem to have in common is that there are usually conditional steps (if, while) involved.
I remember that we once had problems with a wrong COM initialization of a driver which manifested themselves always at conditional steps (in that case with a system level error).
Is anything known that a conditional step may sometimes take much longer than usual, e.g. due to COM problems?
Is there a way to diagnose such problems (like through Debug-Messages)?
Regards
Peter
12-14-2016 07:47 AM
There many ways to speed up the excution of teststand check on the station options
if you disable tracing your test will speed up a lot. Play with the options
12-15-2016 03:19 AM
Thank you for the hint. We never activate Tracing as this is way too slow (and no-one looks at the running sequences anyway).
Regards
Peter