08-09-2013 08:51 AM
I am looking for efficient ideas on an event dump. Right now I have a basic datalogger. it takes data at 100Hz and discards all but the last datapoint for a specified time frame. eg: one sample every two seconds, not two hundred. I am looking to record discontinuity events without sacrificing the basic datalog function.
I am thinking that I want the channels of interest to be stored in a running buffer at the full 100Hz. maybe a lossy queue or an running array of specified length? Another concern is how to add this data after the basic datalog colums but not have the datalog dequeue wait on data from the possible event? Would there be a diffference between putting the event structure around enqueue element in the process loop and placing it around the dequeue element in the datalog loop? I am relatively new to labview so if I get it working, it will probably not be a "best practice" answer. I am going to start playing with the code, but high speed, low drag answers are really appreciated.
08-09-2013 08:55 AM
sorry to double post. I received an error.
08-09-2013 07:01 PM
update. I am not at my computer so I cant provide an updated version right now. I added a lossy Q in the producer loop. I flush the Q in the logging loop on bottom on demand. it works! it results in array. I would like to use merge signal with the regular datalog stream. the only solution I have right now is to rotate array, index array, and rotate array? then merge signal? my stop button results in an error,too, but that is another matter for another day.
08-12-2013 06:56 PM
Hello,
Which location of the case structure worked for you? Also, how are you using the merge signals function at the end? These details might point me in the right direction as far as offering the best practice.
Thanks
08-12-2013 08:15 PM
08-13-2013 09:20 PM
I believe you are on the right track when by rotating the array. I can't think of another way to index it by channel.
08-19-2013 07:10 AM
I accidentally double posted. I figured it out and it is running. check other post with same name for solution, if interested.