multiple data points to boolean indiacator

[Islandman]

This is how you could implement file number increments, this way you don't have to worry about renaming files. It simply finds the files in your folder (List Folder), counts them (Array Size) then increments by 1 converts to text (adding to base & file name) then converts to path.

[aeastet]

My example in post 17 has the date time stamp in seconds add to the data. This should be an easy implementation. After we get this all straight then we can start talking about program structure. Look at my example and we can go from there.

[tanyasue327]

This is what doing that gives me....

Not only this but it messes up my waveform chart... So I wouldn't be able to wire it in like that anyway unless I want two separate arrays, one for data collection one for visualization.

It's my understanding that this is the way LabVIEW writes date and time...

I'd prefer not to have date and time in there, but more of time elapsed... Do you think I could do this with a tick count or the express vi elapsed time(which I don't really want to use)

[aeastet]

You will need to do something like this to have your chart show up correctly.

You need to add the second build array. to go to the data file.

[tanyasue327]

Figured it out

Thanks

[aeastet]

Is there more to your code? Do you want to move on to how to structure your code to make a reliable program? Do you want or need any more help? Did we get all of your problems fixed?

[tanyasue327]

Oh I'll always take help. Right now I'm just taking this one step at a time. Now that I know the data is going to log properly I'm trying to determine how to place headers on the columns of this file. As someone mentioned in one of my posts before I was using all express .vi's which was slowing down my process very much. I guess since I'm new to the program I'm still trying to figure things out.

That's all the code I have right now. I'm trying to make this as simple as possible because like I said eventually 150 data channels are going to be wired in from thermocouples, smoke meters, gas analyzers, etc... I need to make sure a base works before I just go on and test everything.

What do you mean by reliable? I know I will be in the control room during testing. If you have any resources on error handling that would be great. I feel as though just in case something happens I need some error handling in there.

Basically that's going to be the jist of it, very simple and eays to understand (obviously haha)

The problems that I had when I posted this thread are all solved though yes

[aeastet]

I do not have your Feild point VI so I am going to ask a few questions. What is the feild point VI doing? Are you going to have it output a single double value? Are you going to want to start and stop this program? Do you want to see real time reading and only log every second or so?

[tanyasue327]

Fieldpoint is just like a compact DAQ box pretty much. Basically it reads the channel (through those boxes you do not have) and outputs data just like a DAQ (I'm new to FP as well I'm used to a DAQ box). The FP outputs a temperature or value for each insturment, in this case temperature so they are measuring DBLs. The program does need to start and stop. I was trying to think of a way to implement a start button, but it's irreavent. Someone can just start it manually through LabVIEW and the STOP button is there and working when we need to stop the program.

The data needs to log every second (which it is doing now) and the real time reading, well eventually I'm going to need this .vi to be the master and I need to show two more screens. One will have digital displays and the other graphs. The contorl panel .vi allows the person in the control panel to view some results on the screen but all results will be logged.

[Islandman]

One thing that is unreliable about your VI is timing, you have overhead and possibly windows interrupting your program. So your 1000 ms counter may be off slightly. Here is an example of a more precise way of tracking time and extracting exact seconds. Not sure how this holds up structurally but this might help explain things better....or confuse you further;)  BTW "Increments are in seconds and you will get one count for every increment.