Callbacks ignored

[Nimgaard]

Hello

I have a problem with my callbacks being ignored.

What i have is a large sequence file (TestStand 2010) containing ~100 sequences after rewriting a very old TestStand application from a customer. The idea is to simplify it a lot, but the first goal is to get it to run somewhat decent and then start working on it. It is basically a large master sequence that uses the standard callbacks from the unmodified SequenceModel (ProcessSetup, PreUUTLoop, PreUUT, MainSequence, PostUUT, PostUUTLoop, ProcessCleanup) to handle order administration. The mastersequence then use productspecific sequencefiles to run tests (not implemented yet).

What happens is that it runs the ProcessSetup and the PreUUTLoop. It then ignores the overridden callbacks and carries on with the standard sequences in the processmodel.

I have created a simple Sequencefile that just overrides the same callbacks and that works fine. So the processmodel file should be OK.

My question is, does anyone have an idea what might cause this kind of behaviour? As the sequence file is rather large, I would like to know where to start looking.

Worth mentioning is that the large sequence file is derived from a heavily modified process model that was used in the old system (TestStand 2). Would there be any way to make the process model override the callbacks once again in such a setup and cause this behaviour?

Regards,

Per

[Norbert_B]

Per,

if the process model was altered, my guess would be that callbacks could have been renamed. I will talk about process model callbacks!

Make sure that the symbol for the subsequences in your client sequence files you want to use as callback overrides have a green color. If not, they are 'normal' subsequences and will not override any callback from the process model.

In addition, you might check this:

The process model defines the callbacks including the parameter set. Maybe, the adopted process model added parameters to those callbacks hence the overrides in the client sequence files also had those parameters added.

In a short test i have done, using callback overrides having a mismatch in the parameter set will create a runtime error. So this should not be an issue, but you can check for it as well.....

hope this helps,

Norbert

[Nimgaard]

 The callbacks themselves seem alright. They are green, and since im not using the modified process model anymore the names should be matched to the standard callbacks.

After a tip from the original developer(s) i managed to get it to run as expected. Im still not 100% sure what was going on with the callbacks but it seems like the old dynamic client sequence file loading somehow managed to put the callbacks out of play. Im leaning towards the file loading somehow overriding my running sequence file. However, im going to have to fix this functionality so im going to check the parameters to see if they are mismatched somehow.

Thanks for the input, it helps a lot to have a starting point when looking for errors in larger sequence structures.

// Per