Proper steps when shutting down TestStand

[pinguu]

Hi Trent,

Thanks for the reply, but I did check the return value of the function call and they all returned 0.

The issue that I found out was that when i restarted the program, the tasks were actually not initialized and started.

So, I suppose a TestStand program is supposed to be able to restart without unloading modules every time. If there's an issue then that means it did not or clean up properly?

[WireWeaver]

---

The issue that I found out was that when i restarted the program, the tasks were actually not initialized and started.

---

You should be able to use the same technique to check the return values from the initialize function and see why it's not initialized.

So, I suppose a TestStand program is supposed to be able to restart without unloading modules every time. If there's an issue then that means it did not or clean up properly?

---

It depends what you mean by "restart". If you mean closing and opening the application or sequence file, everything will be unloaded automatically. If you mean restarting an execution, it depends on a few things:

• Unload Option per step
• Unload option for the sequence file (Edit » Sequence File Properties)

 Everything you described in your first post is typical - besides the call to unload all modules.

• Open your hardware references in process setup callback
• Use them in the test sequence(s)
• Close them in process cleanup callback

There should be no need to unload all modules unless you need that memory for something else, or you need to edit and recompile the code modules.