DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot use "Simple Teststand API" with DQMH module ?

Solved!
Go to solution

Hi,

I would like to use the "SimpleTeststand API" downloaded on VIPM and combine it in a DQMH module in my DQMH application.

 

The simple example of the toolkit works well, and if I copy/paste this example in a new empty VI it works wells either.

 

But when I create a dqmh module and I try to integrate this example in it, it generates an error saying there are two instances of application manager...

I tried to copy/paste the example the example in the dqmh module (without modifying anything) and I have the same error.

Then I tried to delete all code of dqmh module to keep only the example and I still have the same error.

 

That let me think that DQMH module handle an application manager somewhere ?

How can I find this ?

 

Thank you for your help

 

Error description : 

Error -17500 occurred at Exception occured in TSUI.IApplicationMgr: There are two copies of ApplicationMgr control. in Teststand GUI.lvclass:Launch Application manager.vi->Teststand GUI.lvclass:Engine Init.vi->UI_Teststand.lvlib:Main.vi

This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input.

Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (-17500) or for its hexadecimal representation (0xFFFFBBA4).

0 Kudos
Message 1 of 8
(294 Views)

Is your DQMH module singleton or cloneable?  If cloneable, did you run it twice?

Or did you terminate your module pre-maturely and then run again and so you had two instances active?

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

0 Kudos
Message 2 of 8
(269 Views)

It is a cloneable module but I ran it only once. The error appears from the first call of the module when I start my project.

 

I have made a record that show : 

- I have imported the teststand UI example on my project

- I run the example from my project and it works well

- I copy/paste the example in my new dmqh module

- I run my new dqmh project and I have the error

 

Link : https://screenapp.io/app/#/shared/735JUmK9Hf

 

I tried to create a new dqmh project and a new dqmh module. And when I copy/paste the example like before, this time it worked.

Therefore, I have a problem with Teststand in my project. That is weird, because it supposed to be my first module implementing Teststand functions.

I don't know how to find where are located the two instances of manager according to LabVIEW ?

 

Thank you

0 Kudos
Message 3 of 8
(253 Views)

I have made another test in the record below : 

https://screenapp.io/app/#/shared/Otxodp5qC7

 

- Create a new VI next to my dqmh module.

- Copy/paste Teststand example in it and it works well

- Open my Main VI of dqmh module, delete all code, and copy/paste the Teststand example and still the same error

Whereas the code in it is the same and the location of the VI too.. It is a very weird behavior...

0 Kudos
Message 4 of 8
(247 Views)
Solution
Accepted by topic author LoisLbsUromems

Ok, I have managed to have my dqmh module running the simple Teststand API example.

 

I have created a new VI, copy/paste the teststand example in it. Then, I copy/paste the dqmh process in it.

I replace the dqmh main by this new VI (new main).

Then i proceed to merge the teststand example in the dqmh architecture in this new VI.

And it works, I still don't understand what was the issue.. maybe I have made a mistake previously handleling the exit of teststand but I still think there was something unusual..

 

I close this topic 🙂

0 Kudos
Message 5 of 8
(234 Views)

Great!  Glad you solved it!

Christopher Farmer

Certified LabVIEW Architect and LabVIEW Champion
DQMH Trusted Advisor
https://wiredinsoftware.com.au

0 Kudos
Message 6 of 8
(208 Views)
Solution
Accepted by topic author LoisLbsUromems

Ok, I have found where the problem came from.

 

This code cannot work if the Main VI execution is set on reentrant mode, when I changed to non-reentrant it works fine.

 

This is why the dqmh module main VI was not working whereas my new main VI was working.

 

Hope it will help.

0 Kudos
Message 7 of 8
(193 Views)

Since you are using Teststand and DQMH, I suggest you take a look at Neosoft Testandifier: 

https://www.vipm.io/package/neosoft_technologies_inc_lib_testandifier/

 

Its support forum is at: https://forums.ni.com/t5/Neosoft-Technologies/Support-Forum-Neosoft-DQMH-TestStandifier/td-p/4328567

 

Happy wiring,

Fab

 

cc: @CyGa 

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?
0 Kudos
Message 8 of 8
(135 Views)