Procedures running unexpectedly

[h_yong]

Hi, I was wondering if anyone has had procedures run on their own? I've put debug variables into my procedure steps, and there are several procedures that appear to run once on their own, usually soon after deploying/starting. I don't have a startup procedure selected. This is with VeriStand 2009. I have gone through all my alarms and disabled them (in case they get triggered unexpectedly), but some procedures still run once for some reason. Has anyone experienced the same? Thanks.

[StephenB]

I'm not sure what would cause this off the top of my head. Hopefully someone else can follow up with you and get more details, but I wanted to chime in with a quick thought.

If a procedure doesn't contain an exit subroutine or an end step, when it finishes all of it's steps... The next procedure in the procedure execution order list will begin executing. Perhaps something like that is happening?

[h_yong]

Hi, Thanks for the response, Stephen. I do have one procedure that does not have an end of exit subroutine. Can you please explain to me the difference between the two? Also, similarly, does "Reset alarm" also make it enabled even if the default is that it is disabled? Thanks.

[StephenB]

I'm not 100% sure, but I don't think reset alarm will cause the alarm to go to enabled. It will simply unset the "tripped" state.

There difference between end and exit subroutine is this:

• If procedure A calls procedure B and then procedure B calls END... both B and A stop.
• If procedure A calls procedure B and then procedure B calls exit subroutine... B stops but A resumes