Differences

This shows you the differences between two versions of the page.

--- kb:labview-frameworks:dqmh:starting-modules [2026/04/09 07:56] – [Starting Child Modules] joerg.hampel
+++ kb:labview-frameworks:dqmh:starting-modules [2026/07/13 16:15] (current) – [When to start] joerg.hampel
@@ Line 216: / Line 216: @@
   * Forking the registration reference wire so we can update the event registration of the EHL in the MHL
   * <color /#FFCCCC>Potential confusion about forked registration wire - not recommended by HSE</color>
+    * See the [[kb:bestpractices:codingconventions:architecture#event_registration|HSE Coding Conventions]]
 <WRAP center round box 100%>
@@ Line 260: / Line 261: @@
 The concept of placing the code for starting modules inside EHL/MHL and having a request or Queue message trigger the starting of child modules gives control and flexibility over when and from where modules are actually (re)started. It does beg the question, though, of where and when to actually send the request or message triggering the start.
-  * HSE modules with the need for automated sequential steps usually feature a [[code:dqmh:state-machine|State Machine]].
+<WRAP left round help 100%>
+See **[[kb:bestpractices:codingconventions:apptemplate#startup|Application Template Startup]]** for how to design module coordination in the HSE Application Template.
-  * Our [[code:dqmh:hse-application-template|HSE Application Template]] calls the "Configure" request automatically for any module it starts, which is another potential place for sending such a request (usually in combination with a state machine, though)
+</WRAP>
 ----