dpcamargo

QUOTE (kurty @ May 12 2009, 06:44 PM) Here`s the 8.5 version of the VI.

Hello everyone and thanks for all of your help. I`ve tried the method Mesmith suggested and it still wouldn`t allow the execution to proceed with the dll looping. I have no idea why LabVIEW works like this, I tought it would create another thread and run in parallel but it does not. The first method of Tim_S worked for me. I created a DLL VI that opens a reference to the looping vi, changes some controls values, and executes it. When building the DLL I put the DLL VI as Exported VIs and the looping VI as always included. Thanks again for everyone`s help. Dario Camargo

Hello everyone, I have a program wich makes dynamic calls to driver VIs that we put on the driver folder. What it does is list the folders of the folder, and create an array of paths, wich we feed to a for loop that opens a VI reference and runs them, one by one, with the Invoke Node Run VI. We have some drivers that run just once (no loop), and others that must run in parallel (looping), and it all works fine because we can set Wait Until Done to false when calling the looping drivers. My problem is that now we decided to create DLLs out of the drivers, and when using the function Call Library Function, there`s no way to call a looping dll and continue the execution of my main program as I did before when calling the VI`s. The CLF waits until the dll finishes executing and just after that the main program can continue executing. Creating a loop for each DLL call is not an option since our program has to be able to adapt itself for different numbers and types of drivers without us needing to code. One alternative I was thinking was calling a VI that would call the looping dll. That would work, but wouldn`t be pretty. Does anyone have any suggestion for my problem? Thank you very much, Dario Camargo