08-18-2010 05:33 AM
Hello,
I have a sequence in TS 3.5, where I call a dll. The dll is compiled in LV7.1.1.
If I run the sequence normally, the dll call works fine. The problem comes, when I call this sequence via Engine.NexExecution, from a VI. The dll call works once, but sometimes not. To figure out, where the dll function hangs, I have built in a popup message just right at the beginning of the function. If the failure happens, this popup window comes never, and the sequence editor stays on the step - until I abort the sequence. As I abort the sequence, comes the popup window. So the dll function will be executed after aborting the sequence.
Have I forgot something to set up by Engine.NexExecution invoke node in my sequence caller VI?
08-18-2010 05:43 AM
...and the relevant part of my sequence caller VI.
08-20-2010 08:47 AM
Hi mitulatbati,
what happens if you call the sequence with the default user interface e.g. the one for LabVIEW? Does the problem still occur?
What are your load and unload options for the dll call? Did you try releasing the sequence before you call it again?
A general question is why do you create a dll out of a vi, is there any reason for not using the LabVIEW adapter?
Kind regards
Carsten
08-30-2010 02:25 AM
Hello,
thanks for your reply.
It seems to be a useful idea to force TS to release the dll. The question is, how to do it? Where can I set up the load and unload options for a dll call?
To answer your general question, we build each step type to a dll, to assure reliability and frozen code for our plants. There is no more type conflict by the older sequences. If a step type has to be changed, we change it and build it into a new dll.
regards
Mitulatbati
08-30-2010 02:34 AM
Hi Carsten,
it has been too obvious to find 😄
many thanks for the idea!