SequenceFileLoad causing System Level Exception

[Jon_M]

Hi,

You'll probably want to take a look at the DisplayingProgressAndStatus example for how to update the progress bar. It uses UIMessages to update the progress bar and status text.

[RayFarmer]

Hi,

It should work unless off course you have disabled it in your Sequence Files some where. Do you call Execution.EnableCallback (CallbackType_ModelPostStep, False) or the obsolete version Execution.ModelPostStepCallbackEnabled by any chance.

I have added a PostStep Callback in the TestStand Example and that runs the callback ok

Regards

Ray Farmer

[RayFarmer]

Hi caviars,

I have just tried the example using TS3.5 and added a PostStep Callback and although when queried it reports that the PostStep Callback is enabled. It doesn't actually get executed. I wonder if this is a bug. Are you using TS3.5 or TS4.0?

Regards

Ray Farmer

[caviars]

Hi Ray,

I am using TestStand 3.5. I'm not sure whether this is a bug or not since I don't have TS 4.0. Is it run OK when you run it with TS4.0? If it is a bug, is there any workaround for it? Should I report this bug to NI? If so how can I do that?

I'm not sure if there any other way to update the OI progress bar using the Process Model. FYI I cannot make any changes to the client sequence file (written by customer). So any modification must come from the Process Model

I cannot use TestStand 4.0 or downgrade to 3.0 since the client sequence file is written in TestStand 3.5. The client sequence already caused me some problem (see the begining of this thread).   

[Jon_M]

Ray and caviars,

I tried to replicate the lack of the ProcessModelPostStep firing in 3.5 and wasn't able to do it. Here is what I tried:

1. Open DisplayingProgressAndStatus example.
2. Open SequentialModel.seq
3. Go to Edit -> Sequence File Callbacks...
4. Add ProcessModelPostStep to the list of callbacks
5. Put Message Box step in ProcessModelPostStep callback to indicate that I am in the callback
6. Run example and message popup occurs after Call Long Test step

Was there a different method that you used to determine that the callback was not firing?

[caviars]

Hi Jon,

The problem only occured if you load the sequence file dynamically. You are doing the right thing but you have to try it using the "DynamicClientSequenceFile". example instead of the "DisplayingProgressAndStatus"

What you need to do is to add the ProcessModelPostStep callback (+ message popup) into the process model "DynamicClientModel.seq" included inside the example folder. Then run the "Load me first.seq" sequence. Initially you will see the message pop up from the ProcessModelPostStep since you still executing the "Load me first" sequence. After that when you select which sequence you want to run (either A or B) you will find that the message pop up from the ProcessModelPostStep will no longer executed. This will happen regardless which sequence you select (both A or B)

The sequence A or B is loaded using the Execution.SetClient() property. I use this method to load my client sequence file and I exeperience the same problem. I'm attaching a modified DynamicClientModel.seq for you to try out

Thanks

[RayFarmer]

Jon,

Caviars, is right, you have to look at the example "DynamicClientSequenceFile" not "DisplayingProgressAndStatus". I haven't looked at this example but it probably doesn't use the same mechanism as the other one.

Regards

Ray Farmer

[Jon_M]

Ray and caviars,

Using that modified example I did verify the behavior. When Ray mentioned 'example' I assumed it was the one I had mentioned earlier but we all know what happens when you assume.

This looks like a bug in 3.5 and I'll be filing a Corrective Action Request for it. As for workarounds, you might try overriding the StationCallbacks and do some filtering to determine if you are in the ProcessModel or not, though there will be obvious overhead involved with that. Was there a particular reason why you were unable to make modifications to the client sequence file? Was versioning the only problem that you had with their sequence file?

[caviars]

Due to some other problem with the client Sequence File the developers decided that they will change the whole sequence file structure to a new one. They believe there some are issues when they using DLLs compiled using Visual Studio 6 and Visual Studio 2003 together. I will update the tread if there any new news. 

Thank you for all the help and responses.