SequenceFilePostStepFailure

[RayFarmer]

Hi,

You dont appear to actually pass any arguments (Step and Result) to the Sequence MainSequence in ErrorHandler.seq.

Also, you need to rename MainSequence in ErrorHandler.seq. Rename it to say ErrorHandler.

Then you need to Specify some arguments for the Parameters Step and Result in your sequence call in the Sequence SequenceFilePostStepFailure in Displaytest3.seq.


Regards
Ray Farmer

[Tumbler]

In the sequencecall to ErrorHandler.seq in the Parameters tab you mean? Step and Result Container are by reference

The ErrorHandler SequenceCall in specify Modul File Path or Refernce: StationGlobals.Config.GlobalPfad + "\\" + StationGlobals.Config.ProduktPfad + "\ErrorHandler.seq"
Sequence: "MainSequence"
Multithreading : None
Parameters: None


I don't know exactly what you mean thats wy i wrote both

[Tumbler]

So i had rename the MainSequence of ErrorHandler.seq in ErrorHandler

But i don'T know which kind of arguments i should specify.


It would be more simply for me if you write in such a way as if you it someone would explain ever with TestStand did not work. Which I work only for about 3 weeks thereby. I am thus absolute beginner.

regards Tumbler

[Tumbler]

Now you have their rest from me. I am offline till tomorrow.

I hope you will help me tomorrow to. I will learn all about to work with TestStand and LabView

Thank you very much for your help today.

Thank and have a nice day.

Tumbler

[RayFarmer]

Hi,

You haven't specified the arguments to the sequencecall ErrorHandler

see args.jpg

Open the Edit Sequence Call Dialog, you will find the Parameter part is empty,

see unspecified.jpg

Because you are specifying the path of the SequenceFile by expression, Press the Load Prototype.. button another dialog will be displayed, use the browse button to find the ErrorHandler.seq file. When you return back from the file dialog, select the sequence, I am using you original example so there is only MainSequence available, but you have changed the name now so use that name. Close that dialog.

see prototype.jpg

In the Edit Sequence Call dialog, now specify the arguments, F(x) button to get the write properties.

see specified.jpg

Close the Edit Sequence Call dialog.
Now you shoud be ok.

Regards
Ray Farmer

Message Edited by Ray Farmer on 06-09-2005 05:58 PM

[Tumbler]

Hi,

Thank you i will try it tomorrow. But I'm sure that works.

Thank you very very much. Very Nice.

Can you help me by the second problem i wrote on the first page? But i think it'S better we waiting for tomorrow.

Nice evening see you

[RayFarmer]

Hi,

That should clear your second problem.

Regards
Ray Farmer

[Tumbler]

Good Morning Ray Farmer,

It works very very nice. Thank you very much.
Is this wright the only problem was that i don't specify the two container in the CallSequence ErrorHandler.
And don't creat the step and result container and the Locals StepDetails.


But the second problem i wrote is not clear. I want to insert a fith button in the MessagePopup that is no problem.
But i don't know what i have to do that an ActiveX/com or what ever checked if an variable in Action step in Displaytest3.seq exist named Error.
If the variable don't exist it would be creat. Then i can wrote in the variable some text. And this text schould be visible if the error in the same Action step appears again.

Do you know what i mean.

I would be very nice if you help me by my second problem if you explain it to me every step i should do. Because i will learn the work with TestStand.

Best Reguards

Tumbler

[RayFarmer]

Hi,

Are, the extra function, I get back to you later on today.

The button action is going to be very similar to the other buttons. The extra bit is setting the Error property with the required text. There is some examples in the TestStand examples folders that may help you, in the mean time.

Regards
Ray Farmer

[RayFarmer]

Hi,

Sorry for the delayed response.

Attached is a small example.

The response from the MessagePop in the form of Step.Result.ButtonHit returns a number correspond to the Button pressed, I just turn it into a String to append to my error string to be inserted into my local variable.

The creating of the Locals.Error is done in the second step of my example using API call PropertyObject.SetValString. The option parameter is set to 1. This means, if Locals.Error doesn't exist, then create it. There I don't need to do any checks to see if it exists. To find the result of the first step eg the Step.Result.ButtonHit, I am using the expression 'RunState.PreviousStep.Result.ButtonHit'. Obviously this only works if it the provious step. If its not you will have to use the expression 'RunState.Sequence.Main["Prompt For Error"].Result.ButtonHit'. You would change Main["Prompt For Error"] to something similar to match your sequence structure.

The last step just displays the result.

Hope is is clear.

Regards
Ray Farmer