Dating of steps in Teststand in microseconds

[Piwi78180]

Hello,


I currently have Teststand tests that use functions from a Dll CVI Labwindows.

I would like to be able to scrutinize all the functioning of Teststand, to have the dating of all the steps of Teststand in sending and / or in reception, to trace each event of Teststand temporally to the nearest microseconds.

I need it for a precise timing comparison between tests under Teststand 2.0 and Teststand 2010.


Thank you in advance for your answers 🙂


Have a good day

[~jiggawax~]

There are so many factors that contribute to the speed of TestStand I don't think it is possible to do an exact comparison.  The biggest factor is tracing or any engine callbacks (specifically related to steps). 

Can you not use the TestStand Profiler?  I haven't played with it in a while so I'm not sure if it goes down to the microseconds.

[Piwi78180]

Thanks you for your answer.

I don't need an exact comparision, i just need to show that tests in teststand 2010 work well.

I used Teststand  execution profiler in Teststand 2017, i don't find it in Teststand 2010 or in Teststand 2.0 but it's exactly what i want, and it's in microseconds. Do you have any other solution for Teststand 2010 and 2.0 ?

[dug9000]

Using the expression function Seconds() with the default value for the parameter (or don't specify it to get the default), will give you a high resolution time measurement in most cases (somewhat machine dependent, but most modern machines should give you a high resolution timer). See the expression function help for more details.

[dug9000]

You can also use the API Engine.SecondsSinceStart() if you aren't doing this in an expression.

[Piwi78180]

I'm a begginner in Teststand, could you show me an exemple ?

[~jiggawax~]

Do you care about timing for each step or just the overall execution?  It will be trickier in earlier versions without the profiler. 

If I could understand a little bit more about what your goal is I might be able to point you to a better solution.  Do you just care about select steps? Are you only concerned about steps that are not in the process model?  Is it only steps that record results? Etc...

[Piwi78180]

I care about timing for each step. Because i need to caompare the same tests in the both versions of Teststand 2.0 and 2010.

I'm concerne about all the steps. I have fonctions that calls a dll library. I want to know all the timing to show that the same tests in teststand 2010 had the same timing or better than in teststand 2.0. It's for a secret projet i can't tell more...

[J.C._Andersen]

Hi.

You wrote in an earlier post that you just need to test if TestStand 2010 runs well with you test. So why is it not enough to compare the overall test time of the of executions done in TestStand 2.0 and TestStand 2010?

Since you are running in a Windows system making a comparison on millisecond level does much make sense. The timing for each step will be affected greatly by all kinds of running Windows services.

And on a side note: Why are you upgrading to TestStand 2010 when we now have a much better product in TestStand 2019?

[~jiggawax~]

This example shows how to track how long each step's code module takes to execute.  Not sure if this will work for you?  You just need to use the Pre and Post Step callbacks in your sequence file.