Module was unable to synchronize events (Error 403683)

[maurizio.bollini]

Hi,

suddenly in my project using DQMH, I got from on a couple of modules the Error 403683, Module was unable to synchronize events.

The error chain is similar to the following:

Possible reason(s):

Data Base Module was unable to synchronize events.

Complete call chain:
Data Base.lvlib:Module Not Synced--error.vi:820001
Data Base.lvlib:Wait on Module Sync.vi:2300001
Data Base.lvlib:Start Module.vi
Test Data Base API.vi

I made the fixes suggested from the "Validate DQMH Module" scripting tool but this didn't fixed the issue.

Any clue?

I use:

DQMH version 4.1.0.42

LabVIEW 2016 32-bits

Cheers,

Maurizio.

[joerg.hampel]

Maurizio, maybe upgrading to 4.2.1 solves your problem (I'm at a customer so can't really look into it). See this post for more info.

[maurizio.bollini · Accepted solution]

Hi Joerg,

I fixed by passing all modules through the "Validate DQMH Module..." script and applying all suggested fixing actions.

I will upgrade the DQMH API to latest in the beta testing of my application (now I'm still in alpha). If you or other guys has good advice to upgrade now instead, I'll do now. Let me know. Usually I do work step by step with great caution.

Lesson learned today:

- always use Test Panels to check individual modules before use them in the "main" application. It saves time a lot.

- understand and use the scripting commands that appears in the DQMH updates.

Cheers!

Maurizio.

[FabiolaDelaCueva]

---

@maurizio.bollini wrote:

If you or other guys has good advice to upgrade now instead, I'll do now. Let me know. Usually I do work step by step with great caution.

---

Check the release notes for the newer versions to see if it makes sense for you to upgrade now or later:

https://delacor.com/dqmh-documentation/

---

@maurizio.bollini wrote:

Lesson learned today:

- always use Test Panels to check individual modules before use them in the "main" application. It saves time a lot.

---

🙂 As I always say, keep your DQMH API Testers up to date and use them often. If you don't see the need for them, you will eventually see the benefit and thank Delacor for forcing... I mean... encouraging to use them. Glad they worked this time.

---

@maurizio.bollini wrote:

Lesson learned today:

- understand and use the scripting commands that appears in the DQMH updates.

---

What scripting command confused you?

Thanks for your trust on DQMH,

Fab

[maurizio.bollini]

Hi Fab,

I updated from a beta version 4 to 4.1.  I hadn't noticed or even understood the utility of the Validation Tool script.

Again on test panels - I'm convinced they are important in the module development because they help to focus which other modules are required to run a module and related messages/broadcasts.

To maintain the Test Panels requires little additional time but it is very well spent.

Cheers,

Maurizio.

[FabiolaDelaCueva]

---

@maurizio.bollini wrote:

I updated from a beta version 4 to 4.1.  I hadn't noticed or even understood the utility of the Validation Tool script.

---

Thanks for the feedback. We understand that people are trusting DQMH, the validation tool is a way for us to give back and keep that trust. The validation tool ensures you have enough information as to what changed between versions but also have a quick way to fix some of those issues.

Do you think it would it would help to add the validation tool video link on the release notes? How do you think we can encourage people to run the validation tool? 

This is where the DQMH Validation tool video is at the moment:

https://delacor.com/documentation/dqmh-html/ValidatinganExistingDQMHModule.html

Thanks again for your trust in DQMH and for the feedback.

Regards,

Fab

[maurizio.bollini]

Thanks Fab.

For me, the optimal, would be: when I load a project with modules written with a previous version of DQMH, the validation tool shows up.

Regards,

Maurizio.

[FabiolaDelaCueva]

---

@maurizio.bollini wrote:

For me, the optimal, would be: when I load a project with modules written with a previous version of DQMH, the validation tool shows up.

---

That might be tricky, we will look into it. I am not saying we will do this, but what about launching the validation tool after upgrading DQMH?

[maurizio.bollini]

I think it could be a reasonable solution what you propose, Fab.

[XLEagle]

I encountered exactly the same problem and got exactly the same error messages (Error 403683). However, running "validate DQMH Module..." did not find any issue, "All validation tests passed."

Any suggestion what I should do next? BTW, the DQMH module was running ok previously.

Thanks.

XL