12-27-2019 01:55 AM
Hi All
I am customizing TestStand semiconductor module OI and would like to show indext time on it.
During my development, I have two questions:
1. How do I get the index time?
I searched TestStand and TSM help. It seems TSM API doesn't offer get index time method.
TSM APIs provide "GetAverageSockerTime()", "GetAverageCycleTIme()", "GetWindowAverageCycleTime()", and "GetWindowAverageSocketTime()" methods but not "GetAverageIndexTime()".
Shall I subtract GetWindowAverageSocketTime() from GetWindowAverageCycleTime?
2. What is the index time I get from 1?
Based on the help page http://zone.ni.com/reference/en-XX/help/373892H-01/tssemiconductor/execution/
I assume the GetWindowAverageCycleTime() - GetWindowAverageSocketTime() returns me "handler index time". In some situation, let me assume I have a very fast handler with a very short index time, while my test plan is long and it takes TestStand long time to generate test reports for each Batch , i.e handler index time > tester index time; in this case, what do I get from "GetWindowAverageCycleTime() - GetWindowAverageSocketTime()".
Thank you
Vincent
Solved! Go to Solution.
12-27-2019 09:34 AM
You are correct that subtracting the Cycle Time from the Socket Time will give you the Handler Index Time, and I think that is probably the best way to do it with the current API.
As for your second question, I believe that since the handler/prober driver is waiting for the Controller Execution to call StartOfTest, it will not be able to notify a start of test until the full Tester Index Time has completed. Because of that, you'll still end up with the Handler Index Time.
Cheers,
Ryan Curtis
Product Support Engineer
Automated Test Software R&D