08-27-2021 10:27 AM
I have a few questions:
1. What VIs are to be included in the PPL, Do I include my entire Module Library in the PPL or do I just Include the Required Public API request?
2. Do I used exclude Dependent Packed Libraries in PPL Build Specification or Exe Build Specification?
I created a new project.
Added a Library to the project
Added my module library to the newly added Library
Created a PPL from the Newly created Library
Create an Exe of my Module -- Main
Add Request VI from PPL to my Test Stand
Ran the Exe and the Test Sequence
Still receiving the same error.
Can someone guide me as to how to create PPL DQMH properly?
What am I missing here?
Regards,
Linus
08-28-2021 02:37 AM
Hi Claude,
What have you done to extend the functionality of the obtain broadcast.vi and obtain request.vi and which case?
Sorry but the image you have attached and that is in the article is not very clear.
Can you please help me with the details?
-Linus Koli
08-28-2021 04:42 AM
1. When creating a Packed Library, you add the module library (*.lvlib) as the top level file. So for DQMH, you add the lvlib file for your DQMH module as the top-level library to your PPL
2. Can't be certain, but I think you want to exclude dependent libraries
As for your listed procedure, I'm only building a PPL - not building or using an EXE at all. If you are trying to use both, I think you are essentially using two separate instances of the same module.
08-28-2021 09:30 AM
Hi Linus,
Re-reading the thread, I've got an additional question for you :
within TS, how do set the action step calling the DQMH requests ? Do you specify a project +VI in there ? Or do you only specify a VI ?
Can you send a screen copy of a request step call here ? (original sequence not involving any PPL).
If you specified a project to choose a request from it in the action step, the project creates its own memory space. And therefore cannot share anything with the GUI launching the test sequence. Let's see if no 'project' memory domain is involved here.
08-28-2021 10:08 AM
Irrelevant of whether I add the project or not I get the same error.
Check the attached Image.
Note: The Attached Image is for a simple Test code which I was just testing to check if my concept works.
-Linus
08-28-2021 10:10 AM
Hi Nightshade,
I need a compiled GUI to be deployed at the Client Site. I cannot give them just the Source Code.
How do you suggest I do that?
-Regards
Linus
08-28-2021 10:13 AM
But here you're launching it from the TestStand Sequence Editor, not your exe launching your modules right ?!
08-28-2021 10:19 AM
For now yes,
My main application has a Test Stand Sequence Module, which is basically a Test Stand API, it will load the Sequence File just like Test Stand Sequence Editor.
Are you suggesting that if I run it through my GUI exe application and load the sequence file via my Test Stand Sequencer Module which gets loaded in a sub-panel of my main application, without loading the project in the actions it will run?
08-28-2021 10:41 AM
My guess is yes !
Since it is your exe which is launching the DQMH Module...
Otherwise you have to launch the module from your test sequence (like it is done in the DQMH TS examples).
08-28-2021 10:54 AM
As a quick check I used the Simple Test Stand UI example and added my DQMH module Library to it.
Simply for Testing purpose I added my Launcher Module to run parallelly outside the while loop of the Test Stand Simple UI example and used SubVI node setup to run it.
Then opened the Sequence file in the Test Stand UI and tried to run it.
This is what I got (Please check the attached image.)
Not the best way to do things. But I would like to know your thoughts on this.