After running my program some more times, it appears that the streaming is NOT happening during the beginning of the requested collection time. When I refresh Explorer after a few seconds, the file size is still small. It then grows more rapidly than it would in real time with each refresh. I tried setting the collection time to 60 seconds to see what's going on. It takes about 8 seconds for the task VIs to indicate that they've read a block of data. Each task then indicates high-speed bursts of Events Received updates. The bursts get shorter and begin to slow down as the acquisition progresses. I was able to collect 60 seconds of data, but the behavior of the program was completely different than with the 'good slot' test, which starts immediately and updates the Events Received counters at regular intervals. It seems like setting up the tasks is taking much longer in some slots, and the system is trying to catch up.
Has anyone asked the developers if the slot number has any effect on how DaqMX initializes, performs threadings, etc.? I've been asking this question for weeks now, but haven't gotten an answer. As I've repeatedly stated, the ONLY DIFFERENCE in the test program is the change in the Physical Channel assignment.
