DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Validating DQMH module gives me an error 43 when checking for reentrance and error handling

Solved!
Go to solution

Hello Fancy Folk,

 

I'm relatively new to DQMH and ran into an issue when validating an "Analog In" module that I created.  When running the validation, I am seeing 2 issues: "Error 43 occurred while testing issue "Non-reentrant even VIs in module"" and "Error 43 occurred while testing issues "VIs in module with automatic error handling"".  When selecting these issues, no VIs pop up in the details sections of the validation results windows to "fix the issue".  Additionally, Error 43 seems to be related to opening/creating/replacing a file VI and is most common when the path for said VI doesnt exist.  I have validated several modules in my current project and the only one that I am seeing these 2 issues with is my Analog In module.  My LV Project file doesn't have any unexpected dependencies (only those in vi.lib) so I am not sure what files would cause this issue.  Below is an image of the validation results to show what the window looks like.  If wanted, I can post the module.

 

Matt_AM_0-1639409336782.png

 

 

Thanks,

Matt

If you want to find useful posts, you have to make useful posts. Please try to provide how you solve your posted problems for future users, a better forum helps the community out.
0 Kudos
Message 1 of 6
(2,003 Views)

Hey Matt, thank you for using DQMH, and for taking the time to report this issue.

 


@Matt_AM wrote:

Hello Fancy Folk,


Seeing as you addressed me specifically 😛 😛 I'll reply: Could you please share the module (feel free to email it to info@dqmh.org if you don't want to share it publicly) so we can try and reproduce your issue on our side?

 

Cheers,

Joerg




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 2 of 6
(1,992 Views)

Joerg, 

 

I have no issue posting it here since there is nothing proprietary with the code.  The main goal of the code was to be able to send a request to the module with a task (EHL -> MHL -> helper loop) then allow the the task (helper loop) to broadcast the data at a 10ms rate.  I tried using the same architecture to create user events to trigger my helper loop from my MHL and am pretty sure I followed the DQMH logic.  

 

I'm not sure what is all needed to post the module.  I just sent the folder containing the module and tester API to get compressed and am attaching the zip file.  If there is anything else I need to add, let me know. 

 

Thanks for responding and helping me with this issue,

Matt

 

Edit: I'm using DQMH 6.0.0.83 on LV 2015

If you want to find useful posts, you have to make useful posts. Please try to provide how you solve your posted problems for future users, a better forum helps the community out.
0 Kudos
Message 3 of 6
(1,988 Views)
Solution
Accepted by topic author Matt_AM

The problem is happening because of this missing VI in the module:

 

missingvi.png

 

If you remove that missing VI, the DQMH Validation tests will no longer return an error.

 

The validation tool should be handling this error better. I'll make sure the DQMH Consortium knows about this issue and addresses it in a future DQMH release.

Message 4 of 6
(1,963 Views)

Darren,

 

Well I'll be damned, I am missing that...  That must have been when I was trying to create an error handling VI like the MHL for my helper loop.  I went to try and find callers and subVIs for that control and nothing popped up.  When I went to load my Main.vi, there were no broken arrows, so I assumed that everything was on the up and up. 

 

I can validate my module now, thank you sir!

 

Matt

If you want to find useful posts, you have to make useful posts. Please try to provide how you solve your posted problems for future users, a better forum helps the community out.
0 Kudos
Message 5 of 6
(1,957 Views)

@Matt_AM wrote:

I was trying to create an error handling VI like the MHL for my helper loop


Just in case you're not aware: There's now a VI in the DQMH palette for exactly that purpose:

 

Bildschirmfoto 2021-12-13 um 23.36.49.png




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 6 of 6
(1,952 Views)