LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Creating a datalogging FIFO buffer of TDMS files

 

I'm looking to create a LabVIEW and cDAQ or cRIO based system for machine condition monitoring, and I would like some advice on how to best database my file storage. I will be using a cDAQ/cRIO chassis with a Windows Embedded touch panel PC to monitor about 24 channels of analog input at a 10kHz/ch sampling rate. The PC will only be used to stream live waveforms, show trend plots, and output alarm signals. What I would like to do is continuously data log all channels into some form of a first-in-first-out buffer of data files (preferably TDMS) that keeps maybe the last 24 hours of data. Obviously due to memory constraints this can't be done in software, and will have to be a buffer of data files saved to a hard drive. In the event of an alarm trigger from LabVIEW I would then like to save the current buffer of data files to a new location so they do not get overwritten and can be post-processed later to determine what led up to an alarm trigger. Ideally a new FIFO buffer of data files would start running again after an alarm trigger as well.

 

My question is what is the best way to create a FIFO buffer of data files to a windows computer that keeps the last 24 hours of data? I could probably do this manually with command prompts and batch files run through LabVIEW, but this seems cumbersome and there are probably better ways. From everything I've looked at none of the built-in File I/O VI's in LabVIEW support something like this. I'm open to other file formats or databasing than TDMS, but it has worked well for all my past projects and is fairly simple.

 

Thanks,

 

Grant

0 Kudos
Message 1 of 3
(3,452 Views)

see this

0 Kudos
Message 2 of 3
(3,432 Views)
0 Kudos
Message 3 of 3
(3,428 Views)