From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

concurrent execution of LabVIEW exported functions

Solved!
Go to solution

Hi

 

I am exporting two VIs into a DLL. The resulting functions are expect to run concurrently in separate threads.  Then I load the dll in my app. As soon as  a function is executed in a primary thread the other function in the secondary thread is killed (I assume is killed because the panel disappears immediately). 

 

Is there a work around to allow concurrent execution of these functions? 

 

Thanks

0 Kudos
Message 1 of 3
(1,890 Views)
Solution
Accepted by topic author kretinga

How about putting them in separate DLLs?  Is there an expectation that within a DLL, components can be assigned "separate threads"?  How does the DLL know?  [I'm asking out of ignorance -- I can imagine that LabVIEW, if it is scheduling its code, can keep the threads separate, but don't know if/how it can maintain control once it packages it up for Windows to handle inside a single DLL ...].

 

Bob Schor

0 Kudos
Message 2 of 3
(1,879 Views)

OK, I guess I will have o change my design slightly. 

Thank you 

0 Kudos
Message 3 of 3
(1,805 Views)