Displaying Temperature Reading on Waveform Graphs in a DAQ Program

[Santana9937]

Hello,

I am having a small problem with LabVIEW but I haven't been able to figure out
how to solve this problem because I have very little LabVIEW Experience (3
days). Also, I am using LabVIEW version 6i.

I attached the program I need help with. The goal of this program is to read 40
temperatures from 40 different channels. I want to display these 40 temperatures
over time in 4 waveform graphs with each waveform graph displaying 10 plots.

I put the 4 waveform graphs on the front panel but I haven't connected them on
the Diagram of this program. My first question is where to connect the waveform
graphs in the diagram? In the first step of the program the temperatures from
the first multimeter are read from the first GPIB Address and the temperatures
are displayed in the Temperatures 1 column in the front panel. The next step
displays the temperatures the other multimeter is reading in the Temperatures 2
column. I think the remaining steps concentrate all the readings so that the
temperatures can be saved into a file. I am just not sure where the appropriate
place is to connect the graphs. I think it is in the steps where the
temperatures are read from the GPIB Addresses and put into the 2 columns
but I am not sure.

My next question is how do I make sure that each waveform graph actually
displays 10 different temperatures? I feel that just making connections wont
guarantee that 10 different temperatures are being displayed on each graph.

I have looked at all the example programs that LabVIEW has but I couldn't figure
out the solutions to these problems by looking at the example programs. Any help
would be very appreciated.


Rodolfo

[GerdW]

Hi santana,

here's your vi without sequences and globals, but with a possible solution:

The function I used is "decimate array" to split your 40 values to 4 charts. Also you should note:

- don't use "insert into array", when a simple "build array" will do too

- don't use globals as variables (think dataflow)

- don't use sequences when not needed (think dataflow)

- use path constants instead of string (they also allow browsing for path...)

- there's an EOL constant (combined CR/LF)

Message Edited by GerdW on 03-31-2009 12:18 AM