
bigl00z3
Members-
Content Count
9 -
Joined
-
Last visited
Never
Community Reputation
0About bigl00z3
-
Rank
LAVA groupie
-
Sorry for not replying earlier I ran out off time yesterday. No I don't know yet how to do the analysis in LabVIEW. I know and I can see that it's possible to do most of the data analysis in it. But I think that in my situation it's not the best solution.As my system is running on a machine that is constantly modified by people wanting to study different parameters, it's easier for everybody to have the raw data on their personal computer. I know that Excel is far from being the best solution to treat large data, but at least it's on everybody's computer and it's working for the length of
-
Thank you for all your inputs. LV Punk You were right, the Notifier was exactly what I was looking for. It's now stopping at the right time. I definitely have to look closely to your comment about passing queue refnums into the loops. That may be useful. Karl Rony TDMS sounds interesting I should look at it when I have a bit more time
-
I'm using a floating average VI based on this VI. It's calculating the average for 3 of my 8 signals on the last "x" (generally 50) points. On my system I have a pump generating high oscillations of pressure. -For some measurements, I want all the data (without the average) on short period of time (max 30 seconds) so I can analyse all the oscillations. <-- this I can already do and it's working perfectly fine. -For some longer mesurements (45 minutes or more), I only need my average pressure and to save post processing time & server space I only want 1 value per second. I'm usi
-
Here is what I'm trying to do: Data Acquisition vi: -Read data at high speed (500-800 Hz), calculate an average value. -Write to a file the average values at 1 Hz frequency. -Display calculated values on the user interface. First I had everything in the same while loop which was slowing down the vi. So after asking on the forum I was told to use the Producer/Consumer template. Now my vi is working perfectly fine for short measurements at high speed (writing to file at 500-800Hz). Depending on the test we want to run on our machine, I will only need one value per second. So I decided to
-
Thanks a lot, You were right, that fixed our problem. We can now start aquiring our data.... bigl00z3
-
I'm trying to create a simple data aquisition VI with 8 imputs. I've used the Producer/Consumer Design Pattern (Data) template. In my producer loop I'm writing the signals to a file. In the consumer loop I'm trying to display the values of the differents signals on my interface. I'm trying to access one of the element of a Variant data set from the queue. The Variant Data set has the folllowing structure: <Dynamic Data {[8] (<Waveform(DBL) {...}>, <Waveform(DBL) {...}>, <Waveform(DBL) {...}>, <Waveform(DBL) {...}>, <Waveform(DBL) {...}>, <Wavefo
-
Thanks erverybody for all your imputs. And very sorry about the large pictures... I will definitely try with the "producer/consumer" way.. bigl00z3
-
I'm totally new to LabView (and a bit lost...). I'm trying to create a simple data acquisition VI. I have 8 signals which I want to write to a file. I need a fairly high rate, I have to capture in between 800 and 1000Hz. I started from a basic VI that was developed for us and now I have to try to make it work for us. My problems are that I would like to display the calculated values on my interface: -In my first test (image below) I was placing the display inside the main while loop. The problem with this is that it's trying to refresh the values on the interface way to often (which is n