01-09-2025 06:28 AM
Hi All,
This is probably a trivial question (and I will continue to do so in coming few months, because I am using DQMH for a large scale applications that will involve 12 clones of a module and another 5 modules)
I have couple of helper loops in one of the modules. Is there any reason why helper loop errors are not wired to the final merge error block outside the while loop (as shown in figure below is left unwired)?
I understand the best way to propagate any helper loop error would be, by creating a private request to EHL, such that it is handled centrally. But I wonder if there is a possibility to fail the unregister for event function. That will go undetected because the error out is not wired.
Solved! Go to Solution.
01-09-2025 11:02 AM
There is no reasonable scenario where you need to worry about an error out from the Unregister For Events function.
01-14-2025 05:28 PM
If you wire the errors that come from your event structure or case structure to one of the DQMH Error Handler VIs, then you don't need to create a private request to report an error to the EHL.
The DQMH Error Handler - MHL is already present in the Message Handling Loop
The DQMH Error Handler - EHL is already present in the Event Handling Loop
The DQMH Error Handler - Helper Loop can be added to a helper loop to report the errors from that loop to the MHL or if you are using DQMH 7.0 or later, you can add a helper loop using the DQMH scripting tools and this DQMH Error handler VI will already be wired for you.
More details: https://documentation.dqmh.org/dqmh/7.0/AddHelperLooptoDQMHModule.html
Happy wiring!
Fab