Well, I admit that even after using LabVIEW for about 4 months, I still struggle with how to do most of the things I need. That’s why I came to the American forum (even though I'm in Brazil, just saying... it's good here, but you guys usually respond faster—probably because of experience).
Normally, a Control named A that has a single Dbl stored in it can be right-clicked and changed to an Indicator named A that stores a single Dbl. Similarly, A can also designated a 1D Array of Dbl, but though it is named the same as the "scalar" variable "A", it is different, and naming both a scalar (A) and a 1D Array (A) the same is a Bad Idea and eventually will lead you to a broken wire.
Hmm, I only made it like this because I was referencing this .vi in my application, and the indicator I use is a scalar, but I think I can change that.
When you say "Saving Multiple Array Values without Overwriting", where do you want to save them? If you save them in memory, the amount of data you can save is governed by the memory of your PC, say 8 GB. If you save them to disk, the limitation is much higher, often 1 TB or more.
Do you want to be able to look at all the values? Then "in memory" might be what you want. If they are "results/data" to be looked at later, then "on disk" is probably better.
As for saving the data, it’s simple. I plan to save it as an image of the .vi for demonstration purposes, and then I’ll store it in a folder with the test name.
You should never have a Control ("Salvar") in a Block Diagram without a label! Why hide it? It can only cause you trouble. [Oh -- are you trying to make an Event Structure, something that will "Fire" every time you push the "Save" button? Learn about Event Structures! Don't re-invent basic LabVIEW tools. Resist writing code for "Add", for example.
Apparently, the Event Structure was exactly what I needed in this case. But in my defense, I was just trying to do what made logical sense to me (dysfunctional? Of course it was, but I tried! ksadkas).
Do you understand what the For loop does? The first time, it builds a bunch of 1D Arrays of size 1, holding the values of the Front Panel controls. The second time, it overwrites the 1D Arrays of size 1 with (similar) Arrays of size 2. Note the original data are lost. The third time, the Arrays of size 2 are overwritten by Arrays of size 3.
I thought I knew what I was doing, but now I realize I didn’t, and yes, that was exactly my problem.
I bet that is not what you want. I'm guessing you want the first Array to have the first value(s). The next time through the (For) Loop, the output should be the previous Array with the new inputs appended at the end. What do you know about a Structure (most commonly used with While Loops) that have an Input that was formerly the Output of the previous run? A related question -- how do you restrict a While Loop to only running once?
Well, thank God I didn’t bet against you because you’re right! You pointed out some really good questions, so I’ll pass these on to someone really good because I still don’t know kskskas.
Okay, now I’ll give it a try. If I had to guess, I’d say it has something to do with using a shift register to save the previous value, and then I’d make the loop run only once by using a false condition. But again, that’s just a random guess.
