I've been writing LabVIEW for about 4 years now, but mostly programatic user-driven programs where operations could process data sequentially. Recently I've been writing a lot of code that I want to run in parallel, such as a DAQ andmultiple Signal Processing loops. I currently have a few questions and observations I hope the community can give me insight to.
Code Layout:
Traditionally, I could always make my block diagram code fit reasonably on the screen. My favorite structure was a while loop that encompassed a case structure, which had cases for various purposes such as user input or data processing. The while loop would iterate until program state, and the case was selected by an enumerated constant in two shift registers, which essentially gave me the ability to give the program a current and next instruction.
With the code I'm writing now, I want everything to run in parallel, and what I've ended up with is quite a few while loops. I've got a loop for DAQ, a loop for signal processing methods (I've got quite a few I want to all run in parallel on the same signal and analyze their results independently,) and a few loops to just handle buffering, etc. My problem with this is that I seem to end up with code that's all over the place, somewhat messy, and rarely fits onto one screen sized portion of the block diagram. Does anyone have any suggestions as to what I could do? Am I coding incorrectly? What I would love is a structure visually similar to a case structure, but which would allow code to be run in parallel.
Signal Buffers:
I currently have a DAQ loop running that captures a signal at 300Points/Sec, and the result of this is a DDT. In order to make this data available to my other processing loops, I create an individual queue for each loop with the DDT type, and simply enqueue the incoming DDT with each iteration of my main DAQ loop. In the processing loops, I simply dequeue the element and use a collector to create a longer buffer. Why do I do this? I need the signal to be available for independent manipulation by each processing loop. I cannot use local variables to "preview" a global buffer because all of my DAQ loops run at different speeds due to demands on processing power. Is there a better way to do this?
Thank you for your time, it's really appreciated!
Regards,
Kenneth Miller
