I'm dynamically launching a few clones, and I'd like to pass them some info using start.vi (this is fine, no questions there). But I'm not sure where to launch them. The MHL of my launcher carries the pre-launch info I want to pass them, while the EHL of my launcher needs to register for their broadcasts. Should I launch the clones in the MHL where I can give them their data, then message my EHL saying the clones have launched and to register for their broadcasts? Or launch them from the EHL so the registration can happen... but having the launch info held by the EHL feels terribly wrong. I don't want to send the info to the clones after launch using a request as it's info I'd like them to have on startup. This is my first DQMH project, but I always enjoyed using ephemeral actors with actor framework and it's an element I'd like to keep using, but am just trying to work out if I can.

After going through the process today, I can see how scripting it would be very beneficial for everyone, so thanks in advance! In case anyone else is interested in creating a "Private Request and Wait for Reply" event for synchronous communication within a module, I've detailed all of the steps below. Some of the steps are only cosmetic so the end result appears as if it was scripted. Let me know if I've missed anything. Create a standard Request and Wait For Reply event. Name this event according to what the EHL will do (Update Sub Module Broadcast Registration) since it will be processing the request. Remove the API Tester case that is created. Since we're converting this to a private event, this call can't be made from outside of the library. Move the new Request.vi from Public API\Requests to Requests\Private Requests Move the new Request Argument--cluster.ctl and Request (Reply Payload)--cluster.ctl from Public API\Arguments\Request to Requests\Private Requests\Priv Req Arguments Open Request Events--cluster.ctl and move the new User Event Refnum into the nested Private cluster. Open Obtain Request Events.vi and update the Bundle By Name to reflect the new private location. Open Destroy Obtain Request Events.vi and update the Bundle By Name to reflect the new private location. Open Request.vi and update the Bundle By Name to reflect the new private location. Remove everything in the EHL case except for the Wait Notifier event data node. Move the Reply Payload and Send Notification from the MHL to the EHL. Remove the case structure around the Send Notification since we will always wait. Wire the EHL Wait Notifier event data to Send Notification and the error output of the Send Notification to the EHL Error Handler. Delete the MHL case. Update the EHL comment to reflect the private call. (This module called the "Private.Request" private request.) Update the EHL comment colour to RGB(218,136,255) to match a scripted private event. Update the Request.vi icon to include the private key (search glyphs for "private") and align any text to the left. Thanks, Aaron

We've put some work into updating and tidying our HSE Coding Conventions for DQMH, and I've finally gotten around to starting a new page describing the process of starting DQMH modules (work in progress): https://dokuwiki.hampel-soft.com/kb/bestpractices/codingconventions/dqmh https://dokuwiki.hampel-soft.com/kb/labview-frameworks/dqmh/starting-modules Please feel free to give them a glance and let me know what's missing. I really appreciate any and all input. Thanks in advance!

DQMH Consortium Toolkits Discussions

Where to dynamically launch a module? EHL or MHL?

Solved!

@SemiTester wrote:

I feel I need to point out that HSE Wiki is such an excellent resource. This link especially cleared something up for me that I was considering but felt was a lot of effort. I'm very pleased private messages are scripted in DMQH now!

https://dokuwiki.hampel-soft.com/kb/labview-frameworks/dqmh/starting-modules#in_the_mhl_-_variant_2

Oh, I could listen to that all day! You know that flattery will get you everywhere, right? 😜

DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )

Message 21 of 21

(167 Views)

DQMH Consortium Toolkits Discussions

Where to dynamically launch a module? EHL or MHL?

Re: Where to dynamically launch a module? EHL or MHL?