From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to close clone modules

Solved!
Go to solution

Hi

We have a DQMH module with 4 clones. Every time we call start module, clone modules get created and when we call stop module all the clones that are created are getting closed. However we see a clone module with 0 as ID getting open and never getting closed. We have to end task LabVIEW to come out of it. It happens very regularly. Sorry do not have an example code to share. We have tried sending -1 to stop module to close all modules but it does not work. Is there anything obvious we are missing? 

0 Kudos
Message 1 of 5
(3,364 Views)

You should only see a clone with ID 0 if you are running it as singleton (i.e. run the Start Module.vi with "Run as Singleton? (F)" set to true).




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® (The Future of Team-Based LabVIEW Development)


Message 2 of 5
(3,354 Views)
Solution
Accepted by Viswanathan.V

Hi Viswanathan,

 

There is another way you could end up with a module with ID 0 when not running as a singleton.

 

If you have your Main.vi open and you leave the front panel open when you start running your code, the Module 0 would appear to be running, but it is showing that the Main.vi is blocked for execution because instances of itself are running. 

 

If you start with all VIs closed and you run the API Tester for your cloneable module and do not run as a singleton, you should not see a Module 0 at all.

 

Regards,

Fab

For an opportunity to learn from experienced developers / entrepeneurs (Steve, Joerg, and Brian amongst them):
Check out DSH Pragmatic Software Development Workshop!

DQMH Lead Architect * DQMH Trusted Advisor * Certified LabVIEW Architect * Certified LabVIEW Embedded Developer * Certified Professional Instructor * LabVIEW Champion * Code Janitor

Have you been nice to future you?
Message 3 of 5
(3,317 Views)

Thanks for all responses. 

We are definitely not running it as Singleton. However keeping front panel open could be a possibility. Let me check if this is the case and revert back. 

0 Kudos
Message 4 of 5
(3,311 Views)

Fab,

You were right. This problem was reported only by the developer who owns the module and none of the the other DQMH modules were having this problem. In the last week we have been conscious to close modules before running them and we have not seen the issue so far. Thanks for your support. 

Message 5 of 5
(3,274 Views)