MHL case calling own Stop Module (wait for stop)

[shuttlefan]

Is it safe to call STOP MODULE within the module's own MHL?
What happens if you set WAIT FOR MOD TO STOP as True?

If it waits until the module has stopped, then what it is returning to?

If using this way to kill the module, does this cause any memory leaks/hanging code?

better practice to just directly go to EXIT?

[Darren · Accepted solution]

The best practice is to call the 'Exit' message from the MHL, which will call all the appropriate cleanup code. The 'Stop Module' VI is intended to be called externally from the module as a request to ask the module to stop.