09-10-2010 05:38 AM
Hi,
I have a series of large sequence files (i'm talking of 10's of thousands of steps within sub sequences etc). I believe I have an issue with some of the low level hardware driver steps taking longer to execute than they should, causing test times to take hours longer than expected. However, narrowing down and determining which steps are the bottle neck is causing me problems.
I would like to find a way to default enable result collection for every step within a sequence and also add the ResultList[x].TS.TotalTime numeric to the report for each step.
Can anybody point me in the right direction?
Thanks,
Steve
09-13-2010 08:13 AM - edited 09-13-2010 08:18 AM
Hi Steve,
Thank you for using the NI forums!!
It is possible to time how long it takes to execute VI's in a sequence. This can be seen : Forum : Can you time how long it takes to execute a certain number of VI's in teststand?)
Also easiest other way of narrowing down where the error is, is to half the lines of sequence steps, check each half, and then narrow down the culprit side, repeating to find exactly where the issue is.
Also another article : KB How Can I Find the Execution Time of a Step or a Group of Steps in TestStand?
Kind regards,
09-16-2010 03:35 AM
Hi Steve,
I was just wondering how you were getting on debugging the issue!
Kind regards,