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
producer -consumer code with several variables (types)
Dear Messy (but I hope we are helping you become Neat),
I notice a huge structure in Controller v5 where you have about a dozen Floats that you convert into a string (a dozen times), then concatenate with commas between them.
Here's a suggestion:
- Build an array with "Build Array" to get a 1D array of your dozen floats.
- Do one more Build Array to create a 2D array.
- Wire this to an Array to Spreadsheet String. You need to specify a Format (I recommend <space>%f) and a delimiter (,). You now have a String.
- Write String to Text file.
Bob Schor
@Flo-w wrote:
Thx Blokk,
1) will do
2) well...
3)I am still unsure about what this is, and how it would help me.
4)yeup, that's something I forgot. I will add that stpo button straight away!
5) done
6) So yeah, I may not be the best programmer in the world. but it does hte job.
My real concern here is that this array will eventually eat all my RAM. Do you have any way to prevent that ??
Thank you,
Flo
Type definied clusters are very useful things. I give a little example here to show you how to use them. First of all, drop an empty cluster on any Front Panel. After this, right click on it, and select: "Make Type Def.". Right click on this cluster control again, and select: "Open Type def.". Now an extra window opens where you can work with your new type definied cluster, lets add 3 elements to it just for this example (right click inside the empty cluster and browse out the required element from your palette):
- an array of Waveforms type control,
- and 2 double values, lets call them "Serial1", "Serial2".
Lets also customize the icon of this type def cluster control: double click on the icon at the top right corner, and change it to some descriptive, maybe some text. When you are done with this, save this "ctrl" file into your LV project folder (it should be added automatically to your opened project, or you can do this manually too). This type def cluster should look like this now, see it below. You see that a little black triangle appeared at the topleft corner visible in te BD? That triangle means that this is not a simple control, but a typedef control!
Why is this very useful in a LabVIEW project? Easy to use it with the "Bundle by name" and "unbundle by name" functions. Even more important is the following: imagine, you use this typedef control at many places in your code. What about if one day you need to extend your code?? For example, if you need to add one more serial com to your measurement. If you do not use a typedef control, you have to search for EVERY instances in your code where you used that non-typdef cluster, and manually change ALL. But if you use a type def, you only need to right click on a SINGLE instance of such typdef control, open up the saved CTRL file ("Open type def."), and modify it as you need. After saving the modification, ALL of its instances in the block diagram will be updated at once! You see how much better this?
I attach a sample project zipped up, do not run the main VI, it is just for experimentation how you can add/remove elements from this typedef cluster (hint--> when you drop a typdef cluster into a VI, you can quickly change between control/indicator/constant types using right click):
My real concern here is that this array will eventually eat all my RAM. Do you have any way to prevent that ??
You should not build these arrays indefinitelly. You could use Charts instead of Graphs, Charts have "memory", by default they can show up to 1024 data points. So if you use Charts, you do not need those shift registers with the forever growing arrays...
