From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Clone Manager question

Hello,

I'm currently trying to implement a clone manager for my application and I was wondering how best to notify the clone manager module when a clone is initialized or stopped. I'm asking because when the clones are launched in the clone manager module from a config file using a For loop, these events are not registered and therefore broadcast events like module did init and module did stop will not be available in the EHL.  I'm able to launch the clones and store the names and IDs in a map registry but I'm not sure about how best to implement the notification.  I will appreciate any suggestions. See screenshots below.

Thanks in advance..  

 

DQMH MAP1.PNGDQMH MAP2.PNG

0 Kudos
Message 1 of 6
(650 Views)

Easiest thing would be to fire up a dummy clone and register for its events. So your EHL is good to go. Then in your code where you launch clones, use the dummy as the "first" one, taking into account that it has already launched when you populate your UI with all the other clone info as their 'Module did Init' events start firing.

0 Kudos
Message 2 of 6
(645 Views)

I'm asking because when the clones are launched in the clone manager module from a config file using a For loop, these events are not registered and therefore broadcast events like module did init and module did stop will not be available in the EHL.  

I would advise against what you've said above. You definitely want all of the clones registered.  

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

0 Kudos
Message 3 of 6
(636 Views)

Hello Darren,

Thanks for your reply. I decided to use a "start modules" request from the top level application and perform all the launching and registration in the Device Manager EHL and then passed the mapped info to the MHL to populate the UI. I found it easier this way.  Again, thanks for the suggestion.

0 Kudos
Message 4 of 6
(583 Views)

Hello Chris,

Your point is duly noted. Thanks

0 Kudos
Message 5 of 6
(576 Views)

@SolPS wrote:

I decided to use a "start modules" request from the top level application and perform all the launching and registration in the Device Manager EHL and then passed the mapped info to the MHL to populate the UI.


This sounds like a great solution as well.

0 Kudos
Message 6 of 6
(568 Views)