From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
LabVIEW
How do I use the same SubVIs in the different VIs? Those VIs have to run at the same time.
Hi WangX,
normally there's no problem to run the same vi in two different locations.
You only have to decide on concurrent operations:
- running subvi independently and really "at the same time" -> make them reentrant
- having them in more then one location, not running at the same time: use standard execution options
But:
Why do you want to initialize an instrument in 2 different places?
Why do you want to close an instrument in 2 different places?
Is it not sufficient to init & close the instrument in VI1 and let VI2 just monitor VI1?
normally there's no problem to run the same vi in two different locations.
You only have to decide on concurrent operations:
- running subvi independently and really "at the same time" -> make them reentrant
- having them in more then one location, not running at the same time: use standard execution options
But:
Why do you want to initialize an instrument in 2 different places?
Why do you want to close an instrument in 2 different places?
Is it not sufficient to init & close the instrument in VI1 and let VI2 just monitor VI1?
You should really show us some code.
What is done in these subVIs? What are the inputs? What are the outputs?
Hi, everyone
Thanks!
It seems that I didn't solve this problem, but now I maybe understand why it happened.
Thanks!
It seems that I didn't solve this problem, but now I maybe understand why it happened.
--------------------------------------------------------------------------------
GerdW said:
Why do you want to initialize an instrument in 2 different places?
Why do you want to close an instrument in 2 different places?
Why do you want to initialize an instrument in 2 different places?
Why do you want to close an instrument in 2 different places?
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Graziano said:
i guess the problem is that, running two times SubVI1 you initialize instrument two times (it is not desirable...), and, worst, running SubVi2 you close instrument twice!
i guess the problem is that, running two times SubVI1 you initialize instrument two times (it is not desirable...), and, worst, running SubVi2 you close instrument twice!
--------------------------------------------------------------------------------
That makes me think about the number of doing init & close. My project calls on that there must be a strict requirements about the number of calling those function in one process.
That is to say,when running them, if VI1 and VI2 are in different process but not in the same one, the program is going to run successfully. But now, VI1 and VI2 are threads which in the same process, so my project's strict requirements makes them run failue.I used SPY++ to analysis, and found those two threads are actually in one process.
That is to say,when running them, if VI1 and VI2 are in different process but not in the same one, the program is going to run successfully. But now, VI1 and VI2 are threads which in the same process, so my project's strict requirements makes them run failue.I used SPY++ to analysis, and found those two threads are actually in one process.
--------------------------------------------------------------------------------
Graziano said:
I suggest to put SubVI1 and SubVI2 outside VI1 and VI2, and you run them once, at the start and stop of your measurement.
I suggest to put SubVI1 and SubVI2 outside VI1 and VI2, and you run them once, at the start and stop of your measurement.
--------------------------------------------------------------------------------
I believe that is a good idea, I can deal the problem in this way. Thank you!
But if anybody has the idea which can deal with the problem between the threads, I will be so glad......
What does that called, Synchronized between threads.....maybe......
To altenbach
I am afraid showing the code doesn't work, because all the VI SubVIs and code is base on the japanese system.and all of them must call the functions form DLL which is protected by my company. I am sorry about that......
I am afraid showing the code doesn't work, because all the VI SubVIs and code is base on the japanese system.and all of them must call the functions form DLL which is protected by my company. I am sorry about that......
Thanks a lot!! Everyone.
I do not know whether Notification tech or Occurence tech can do the help.
It might be worth to try.
Hi WangX,
I think I see a little better your problem....
You have to make both VI1 and VI2 capable of initializing and closing instrument, as you say it.... so, in C programming language, I'd have used preprocessor directives, to do conditional compile: when VI1 and VI" are in the same program, you don't run initialize and close (say) in VI2, when tey're alone you do it. Only, you should translate it into LabVIEW code...
A raw way can be a global variable, that tells VI2 if the instrument has already been initialized, and if it has already closed...
...but, again, we should see the code, to understand better....... without it, my advices are poorer than usually.....
have a nice day!
graziano
I think I see a little better your problem....
You have to make both VI1 and VI2 capable of initializing and closing instrument, as you say it.... so, in C programming language, I'd have used preprocessor directives, to do conditional compile: when VI1 and VI" are in the same program, you don't run initialize and close (say) in VI2, when tey're alone you do it. Only, you should translate it into LabVIEW code...
A raw way can be a global variable, that tells VI2 if the instrument has already been initialized, and if it has already closed...
...but, again, we should see the code, to understand better....... without it, my advices are poorer than usually.....
have a nice day!
graziano
Hi, Graziano
Best regards
I have just get it done with two ways.
One of them is what you suggest me to do. That is using the global variable, that is a simple and fast way, but a little danger......
The other way is that I used LV8.0 to built those two VIs into EXEs. And then when the EXEs run, they are Of course in two different process but not threads.
But I believe there must be some better solutions.
using CIN is a little bit difficult and complex for whole project, so, the next I am going to try the Occurences. Or maybe setting a index for the called functions is the key......
Thanks for your help!!!
Best regards
