10-21-2007 06:34 PM
10-22-2007 09:54 AM
Hey mike,
That sounds like quite a project you have going. In TestStand 4.0 the information about the step is stored in Step.Result.whatever. Check out the TestStand Reference Manual starting on page 4-6. It tells how all the information for each of the step types are stored. Very informative! The other section in the TestStand Reference Manual to check out is page 3-14. This contains the exact order of step execution. The pass/fail status doesn't get evaluated until the Status Expression executes. That's in action number 17. Your post step gets called in action number 15 so you won't know the status when your post step executes. You can however copy the same code from the status expression and put it as part of your post step to get that if you need it there.
I'm not sure I understand what you mean by this comment: "Additionally, I have Post UUT call back that I need modify for that VI I need the information that was in the "UUT Result" Cluster." VI's do not have a Post UUT callback. Only the process model has a Post UUT callback. Do you need to add a call to that VI in the Post UUT callback? If so then just add the callback to your client sequence and call the VI in there. You'll have to define what you mean by "UUT Result" Cluster. Is that a huge cluster that gets returned by your VI with information about passing and failing?
Hope this helps some,
01-27-2008 07:45 PM
@mikeg1 wrote:
I am coverting an Test Exective application to TestStand 4.0I have post step callbacks that I am looking to modify for use in test stand.I am looking for where the pass/fail result for the step, numerical value measured, and comparison mode.These could be found in Test executive in a cluster named "Test Result"Additionally, I have Post UUT call back that I need modify for that VI I need the information that was in the "UUT Result" Cluster.Thanks in advance for the assistance.
01-28-2008 01:00 AM
Hi,
http://digital.ni.com/public.nsf/allkb/F1118263F4599E9986256BE600602D97
This link may help, I understand you are using a very early version of the TestExecutive.
Regards
Ray Farmer