teststand display bug

[Derren]

Hi All

I have created some Teststand custom step types that control NI Switch, Scope and other cards that run tests as part of a automated test sequence. The problem that I have is that sometimes when running down through a set of steps in a sequence, the teststand execution window, display the 'Passed' or 'Failed' status result before the execution has actually got to that point in the sequence.

All though the problem can be lived with, doesn't look good for the customer!!..

An ideas

Derren Price

Software Engineer

AmFax

[Scott_Richardson]

Derren -

All step statuses are displayed synchronously, so that step must complete before the status can be displayed. This holds true for the execution status as well. Can you explain better what you are seeing and why you think that the execution is displaying a status before it should?

[Derren]

Hi again.

Code is labview 8.5 Custom step types running under teststand 4.0.1.

Have included a jpeg screen grab of the problem occuring.

From the picture you can see that the execution has got to the third step

down, but it's displaying a result for one of the steps in the middle.

This strange result gets overwritten when the execution goes over

the step! 

Hope this helps to better explain the issue that I have

Derren Price

[Erik_Crank]

Thanks for the information. Probably the best way for us to diagnose the problem is to examine your custom step type and sequence. Could you attach your sequence file so we can examine it more closely?

Erik Crank

National Instruments

[Derren · Accepted solution]

Hi...

Finally stumbled upon the reason for the strange result being displayed before the execution got to

that point.

The reason for the strange going-ons is the custom-step types when created and modified, ended

up with 'Failed' string entry in the 'Step.Result.Status', so that when ever the custom step type was

placed into a sequence, it already appeared to have a result in it and then Teststand decided to

display the result for that step even though it hadn,t actually got there !?!.

So clear the 'Step.Result.Status' String and everything is as happy as a pig in you know what!!!!.

Derren Price

(Now hopefully with a happier customer)