Top Level Actor Stop Message not stopping first level nested Actors

[BillMe]

I have a top level Actor, "Application Controller", that launches via "Launch Nested Actor" ~seven nested actors (more to come). The "Launch Nested Actor" builds an array of nested actor enqueuers to be used later by the default Stop Core. So Application Controller shouldn't have to override Stop Core and send Stop Messages to each first level nested actor......but all the first level nested actors will not stop if the default Stop Core is used. However, for any nested actors launching their own nested actor(s), the default Stop Core works to stop them.

For example, in the Task hierarchy diagram below, all the tasks in orange will stop through the default Stop Core message from their callers (TLM Controller and UUT Power). Those in cyan will not.

Am I missing something? (Yes, Bill, apparently a brain)

[dsavir]

Sorry for the obvious question, but in the top level actor, when using launch nested actor, did you wire the "auto stop" input? It should be either empty or true.

I haven't seen the behavior you describe, in my case even if I do something stupid in my nested actor (like forgetting to enable "show front panel when called ) the default stop core of the top level actor stops the actors beautifully.

[BillMe]

All the "Launch Nested Actor" calls I use do not have the "Auto Stop" wired (defaulted to TRUE).

[BillMe]

Ok, user error.....I'm not carrying through the "Caller Actor Out" from each "Launch Nested Actor" to the next, so I'm losing the nested actor object references as they're "saved". Argggggghhhh...

[dsavir]

Happens to all of us sometimes

[AristosQueue (NI)]

BillMe wrote:

Ok, user error.....

*phew* Moment of panic. 🙂