Evaluation of Vi

[ceilingwalker]

This is what I originally started with and then abandoned it because I couldn't get it to write to the spreadsheet.

[Bob_Schor · Accepted solution]

---

@ceilingwalker wrote:

Thank you Sir for your input. Under what circumstances would one use a local variable? I remember in the training lesson it said something about preventing a race condition, and for feeding parallel loops, but I could be wrong about that.

Do NOT use Local Variables for "feeding parallel loops".  If you have a variable that you need to initialize (and can ensure that this code runs first), you could use a Local Variable for this.  My advice -- really, really make every effort to not use them anywhere, particularly while you are still learning LabVIEW.

"The five States "1 Volt" .. "5 Volts" seem to be the same, differing only in the constant wired to the AO function." That is correct, only the constant for each DAQ write changes. Originally I started this project using a sequencer. It was a lot more organized than the monster I created but for some reason it didn't seem correct. It also expanded my Vi, I was attempting to keep everything to where I could view the entire Vi without scrolling.

I guess you didn't read and "get" my long series of recommendations.  This distills several of the points I was trying to make ...

---

Bob Schor

[ceilingwalker]

I tried something like this as well, I just gave up on it too soon. Thanks much for this information.

[ceilingwalker]

I sat and figured out how to create sub-Vi's, that is HUGE! Thank you for the shove in that direction.

[PeterFoerster]

OK, I'm trying to be the grumpy one here, but:

How can you say you have been through Core 1-3 and not know how:

• to create subVIs?
• to avoid local variables (also local variables do not avoid race conditions, they can cause them)?
• how to cluster data and then use said cluster?

About the online course I can say that I work a lot with them, when teaching new employees and interns how to use NI tools. However Quantity is nothing if the concepts presented are not understood. Imho, Core 3 is fairly advanced and not at all needed for your case. 

Edits in blue

[ceilingwalker]

Unfortunately, I can sit through power point presentations, listen to lectures, and read every book on the topic but unless I am actually writing it, it doesn't sink in. I did the practical lessons but that was quite some time ago. It just didn't strike me as important. I had no experience at all with LV, never even opened a Vi in my life, prior to the online training. Now that I am working and using it, I am able to apply it to something. Difficult to explain.

[Verywiseguy]

I am the same kind of learner. I learn by doing, not by seeing or hearing.

Now that you have gotten your feat a bit wet in the LabVIEW pool, it might be worth revisting the practical lessons. With your new perspective you might notice that more of the lessons feel important and might even have an exact feature you've been looking for.

[ceilingwalker]

Good day Sir, I would like to know if the "Output Voltage" was a sub Vi you made or is is something that is available in LV? I have looked around for it but couldn't find it. Thank you.

[ceilingwalker]

Yes Sir, that is a great idea and I have been doing it. Now things make more sense. Thank you for the support.

[crossrulz]

---

@ceilingwalker wrote:

Good day Sir, I would like to know if the "Output Voltage" was a sub Vi you made or is is something that is available in LV? I have looked around for it but couldn't find it. Thank you.

---

That looks like a self-made subVI.  Or it may have come from a driver library for a specific instrument.  Definately does not look like a built-in LabVIEW function.