02-24-2021 01:46 AM
Hi everyone I have questions. it is possible to switch from one labview VI to another, for example via a boolean at the end of a loop it goes to the next VI. Last question, can the data of a VI remain stored and go to the next one to save the string data (for example) of both in a single file (word / excel)?
02-24-2021 01:54 AM
Hi a.,
@a.garciaperez wrote:
it is possible to switch from one labview VI to another, for example via a boolean at the end of a loop it goes to the next VI.
Yes.
@a.garciaperez wrote:
can the data of a VI remain stored and go to the next one to save the string data (for example) of both in a single file (word / excel)?
Yes.
It seems you should take those "Training resources" as offered in the header of the LabVIEW board. Your both questions are about very basic LabVIEW topics (case structures, DATAFLOW)…
02-24-2021 02:03 AM
First of all thanks for the answer, if you can explain me in two words I would thank you infinitely. I'm not good at LabVIEW I've just started.
02-24-2021 04:33 AM - edited 02-24-2021 04:33 AM
02-25-2021 03:23 AM
GerdW's answer is just the most obvious one. Highly recommended.
The problem with the question is that could mean a lot of different things. For instance, you could have two VIs and when one is done, the other should start. It could also mean you have two VIs running in parallel, and you want to switch activity from one to the other. That's more like actors, and something completely different.
Each of the things it could mean, can be solved in numerus ways.
Also, you're asking solutions for problems that can\should probably be done in different ways, avoiding the problems completely. This makes it dangerous to give advice, because you might just blindly accept it as the truth.
If one VI stops (e.g. by pressing a Boolean that stops a loop) data flow (e.g. an error wire) makes the next thing(s) attached to it execute. So, that's an answer: "is it possible to switch from one LabVIEW VI to another, for example via a Boolean at the end of a loop it goes to the next VI."
Data can retain in VIs through feedback nodes, shift registers and\or control\indicator values. If you use this in a functional global, you'll get a buffer that you can fill in one VI and read in the other.
However, if you have two VIs that act as a user interface, you can also make them share data by wire. Each VI has the data (a cluster, a class, a reference or scalar value) coming in as a control, and when done, it outputs the data as an indicator. The 2nd VI is the same.
This is indeed very basic dataflow.
It seems you're (both) struggling to go from entry level to a slightly higher level. So, study. Do the courses, do more courses, ask questions, learn, get better...
02-26-2021 02:21 AM
02-26-2021 06:54 AM
Yes, all of these are possible. You are missing basic concepts of LabVIEW. There are 3 basic parts of a vi.
Each one is explained by the LabVIEW getting started training materials. We are not going to rewrite the content of those manuals here. But, we will point you to them.
After you have gone through some of those resources you may still have some questions. We'll be happy to explain the concepts you are unsure about. But, at least you will learn enough about LabVIEW to ask clearer questions.
02-26-2021 09:00 AM
@a.garciaperez wrote:
Hi, thank you for your response and encouragement. You are all right that it can be a basic concept of labview, so I was asking you that maybe you could explain these basics to me in a few lines. In response to the assumptions and misunderstandings about my question: the Vls are not in parallel. I would like that at the end of Vl, it closes and opens another one of my choice (obviously). as I said before since I know how to save data in word / excel, I was wondering if it is possible to save the data of more than one Vl in a word / excel.
You might look into the VI properties (in the VI Properties dialog) called "Show front panel when called" and "Close afterwards if originally closed". On the Window Appearance tab, press Customize.
That will literally open the FP when the VI executes, and closes it when done. A wire (or even a flat sequence structure) will make one VI execute after the other, so when one VI closes, the other opens. Put it in a loop, and you'll repeat this behavior.