Registering for multiple broadcast events when modules not running

[Jens_S]

Hello!
 
Right now, I'm working on my first project using the DQMH and ran into a problem I’m not sure how to solve.
 
Let’s say we have a singleton module called “Test Manager”, one called “Logger” and one cloneable called “Test Runner”. The Test Manager and Logger are started by the main application. The Test Manger is then starting up to 40+ Test Runner modules which are performing long term tests on different motion controllers. Each Test Runner is testing one device but all devices running different test scenarios.
 
The Logger should now register for the “Status Update” broadcast events of every Test Runner and that’s where I ran into some problems. I did a lot research in the forums and all the documentation and found quite a lot of threads with similar but still different problems.
 
The Logger is using the “Register for Broadcast Events.vi” of the Test Runner module to get the event refnums but if no Test Runner is actually executing when doing this, the broadcast events are not fired inside the EHL of the Logger.
 
I found this example https://forums.ni.com/t5/Delacor-Toolkits-Discussions/Registering-to-broadcast-events-from-many-modu... which is the way I do it right now (option 2). I’m not sure how to do this the right way. The Logger must start before the Test Runner so how do I get all the broadcast events from the Test Runner modules inside the Logger module?
 
Best regards

[joerg.hampel · Accepted solution]

The "Test Manager" could let the "Logger" know when it starts the "Test Runner(s)". The "Logger" can then (re)register for the broadcast events of the "Test Runner(s)".

Seeing as the cloneables share the same event references, the "Test Manager" can either just notice the "Logger" whenever a "Test Runner" is started, or you could put some logic there to only send the notification for the first clone that's instantiated.

[Ozfarmboy]

Agree with Joerg.  

If the Test Runners are dynamically being launched throughout the duration (and not all at the start), either the Test Manager needs to keep letting The Logger know of this. 

Or just have The Logger independently and periodically check for new registrations.

[Jens_S]

Thanks for the quick response!

Oh I’m surprised that it’s that easy :)…. but to let it get me straight.
 
When registering for the broadcast events and the module is not running, all I get is some kind of a null reference. I can then use the events in my EHL but they aren’t bound to something. When I start the module then these references point to the actual module and the reference is then shared between all the instances of the cloneable module. So, this is why it is enough to reregister for the events because all share the same reference?

Letting the Test Manager inform the Logger seems the most logical way to me so thanks for this!

[joerg.hampel]

Maybe you'll find the article on Helper Loops interesting, and also this specific post that talks about this stuff...

[Jens_S]

Thanks! Thing I got it 😉