Work in progress on a set of LabVIEW programs to enable autonomous robots inspecting and cleaning internal chemical tanks.http://smarttooling.eu/ I could have made it look standard, but in this part of the dashboard sw. I explored a futuristic look of the sensor signals as motion pictures sometimes show future U.I.'s. Sometimes working on code can be fun for the developer as well. The psuedo-graphs are made up of bar-indicators with sections and have a separate boolean peak-indicator-array. As there is interrest I may show more U.I.'s as they are developed.
© © 2017 Copyright P. de Boevere b.v.
My best advise is to leave the vi for a year and do all sorts of other projects and learn and apply the basics of architecturing large LabVIEW vi's. Then look at your current work in progress, throw everything away and start from scratch.
At that data-rate with those kind of intervals, I would pre-process the data before storing to disk, as mentioned before. My approach is that I store the channel to individual binary files, not directly but via a buffer. In one file the data is stored, in the other the timestamps, so you basically have an X-Y save. Steps: - compare signal values; if data is changed? add to the buffer datastring and to the timestring. - If storage interval is reached, copy the buffers to the binary files - If a certain time-frame is reached, say 1 hour, I would store to new files and auto-archive the older data. In that way you get more but smaller files and only store relevant data, not values that do not change. Typical applications are low-noise signals only gradually changing or only at small time-intervals, or digital I/O values. On the decoding side, it takes additional effort.