DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Module registrations / start up sequence

Solved!
Go to solution

@SC_boy wrote:

Jörg, I'm attempting to be more controlled when starting my child modules

[...]

I think it is working but wanted to ask here if there's something I'm overlooking with how the DQMH modules start and are synchronized.


It does look good to me. Just to reiterate:

 

  1. All clones of a Cloneable module share the same event references, so it's correct to register only once (not for each clone being started - although that would not break anything either, it's just not necessary)
  2. All the clones will start an instance of Main.vi and then wait for the sync. If starting takes a bit of time and you start many clones, you might run into synchronization problems (Error 403683: Module was unable to synchronize events). 
    1. Example: If starting a module (run Main.vi until the Initialise MHL case) takes 100 ms, and you start more than 50 clones, you will run into the 5000ms default timeout value of DQMH...



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 )


0 Kudos
Message 21 of 21
(19 Views)