DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

DQMH problem with syn

Hello All,

 

I have a problem with my application based on DQMH modules. I added a new module (app. works without it) and this module causes problems.

I can't synchronize events.

 

Error 403683 occurred at DUT_MBSP.lvlib:Module Not Synced--error.vi:820001

Possible reason(s):

DUT_MBSP Module was unable to synchronize events.


Complete call chain:
DUT_MBSP.lvlib:Module Not Synced--error.vi:820001
DUT_MBSP.lvlib:Wait on Event Sync.vi:3480002
DUT_MBSP.lvlib:Synchronize Module Events.vi
UserInterface.lvlib:Main.vi

 

I think the problem could be with the order of initialization of all modules?

Could any one have some hints how to deal with it?

I check all my modules with DQMH validation tool - all OK

 

UI module inits all modules.

 

LVuser89_0-1722859374545.png

 

MBSP module init code below.

 

LVuser89_1-1722859428242.png

Thanks for your support.

0 Kudos
Message 1 of 4
(531 Views)

In the second diagram, try wiring the 'Wait for Event Sync' boolean from the Start Module VI over to the Synchronize Module Events VI (as opposed to having those False constants wired).

0 Kudos
Message 2 of 4
(521 Views)

Hello Darren,

 

Thanks for response. I detected that the error comes form Sync Caller Events VI on Initialization of MBSP module.

 

DUT_MBSP.lvlib:Module Not Synced--error.vi:820001<ERR>
DUT_MBSP Module was unable to synchronize events.

 

I still don't know where is the issue.

0 Kudos
Message 3 of 4
(497 Views)

If I understand correctly, the second screenshot shows the block diagram of the DUT_MBSP module, which starts both the UI module and the IO AI module.

 

First of all, to underline what Darren said, if you don't wire the "Wait for Event Sync?" terminals between Start Module.vi and Sync Module Events.vi, you'll run into problems.

 

Seeing as the UI module seems to do lots of things when starting, it might just be that it takes too long and the DUT_MBSP module therefore times out. The time it takes for a module to start up (i.e. arrive at the "Initialize" MHL case and execute the Sync Caller Events.vi) is limited to the module timeout, usually 5 seconds. If you place too much code outside the main error structure, those 5 seconds might not be enough. You can read more about that in this post

 

I recommend looking into a different place for starting your modules (like, in the EHL or MHL).




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 4 of 4
(490 Views)