There are too many "moving parts" (some of which, as has been pointed out by others, could lead to loops not running as expected) for me to say with confidence that "doing it your way" (as opposed to "doing it my way") would work or not.
I can say the following with confidence:
- For transfers of data in the tens-of-kilohertz range (and possibly higher, but I have no direct experience with this), Channel Wires perform flawlessly.
- For proper synchrony of multiple asynchronous loops, using known fixed-size structures (like "Array of 1000 points" as opposed to "As many points as are available now") makes for much smoother, better-running code.
As an example, I have a program with 24 asynchronous Stations, each with an IP WebCam sending 640x400 RGB images at 30 fps over TCP/IP to a LabVIEW routine that uses lots of Channel Wires -- I just "did the math" and get a data rate of 30Mbytes/sec. At various times, one or more Station may need to save the images to an AVI. Oops, I thought I was using Channel Wires to save the Images to AVI, but (looking at my own code), I'm getting it directly from the Camera's Image Buffer. My main use for Channel Wires in this example is for Process Communication (something like a Message Channel), though I also use it to stream other (non-image) data to a Disk-Streamer VI.
Bob Schor
