Unable to read data in ResultList through SequenceFilePostStep callback

[ShanBhar]

Hello,

I am working on an application where I need to access the ResultList variable from Test stand into Labview and create my own customized report. I require data like StepName, Numeric value, Status, Loop index, NumPassed and NumFailed, etc. I have looping in each step and basically need to read the ResultList array after each step (results of all the loops in a step).

I have implemented the SequenceFilePostStep callback in the teststand and UI message event in Labview to read the results. But, I am unsuccessful in reading any of the data, I get an error saying unknown variable.

The expression to read the step name;   

RunState.Root.Locals.ResultList[0].TS.StepName

This is the SequenceFilePostStep callback;

The error I get.

Callback VI to read the UI message

However, when I give the same expression as a step (Message Popup) in the sequence, I do not get the error. It pop ups the step name perfectly.

What am I missing? why is the expression failing in the callback and not in the Message Popup step?

Any suggestion would be of great help. 

Thanks

[Teds]

Hello.  My guess is when you run 'SequenceFilePostStep'  at that point the result has not yet been posted in the ResultList hence the expression 'RunState.Root.Locals.ResultList[0].TS.StepName' is not yet valid.

En

I used the SequenceFilePostResultListEntry callback and the above expression worked.

~Teds

[Oli_Wachno]

Good point! The ResultList entry only exists after the  SequenceFilePostResultListEntry.

Yet I have to admit that I wasn‘t able to find a comprehensive list / description of the when the according callbacks occur in respect to each other…

[ShanBhar]

Hi Teds,

Thanks for the reply.

I used the ResultObject to get the final result list. Although I wanted to display the result after every execution of a step but I guess I am ok with the final result which is available in the result list after the end of sequence execution. I am using this to generate the final report. 

Thanks again for your idea.