I have never used Waveform type. It does nothing for me. You are not forced to use that type - the EXPRESS VIs are for speed of CODING, not speed of execution.
In the manuals for the RT (real-time) module (a project I am currently working on), it says something to the effect that you should never use any EXPRESS vis on the real-time card - they have too much overhead. Still - I find it hard to believe that 16 signal generators would bog your computer down, unless you're running on an old Apple II. By what are you judging that your computer has slowed down? What do you mean? You should be (and as a newcomer perhaps you are not) aware that it is necessary to add timing delays to loops in some situations. I have seen newbie code where someone will have a while loop waiting on a button push. That's fine, except it might eat your CPU time. Putting an indicator on the [i] variable showed that it was polling the button over 10 million times per second!! The problem with that is that the CPU is busy polling the one button, and doing nothing else. Putting a wait of 100 mSec in the loop lets somebody else use the CPU (the task that does the wait goes to sleep for 100 mSec - the CPU is available for something else), while still being reasonably responsive (100 mSec is not noticable) to the user. Perhaps you have such a situation? In short, while I know that the waveform data type adds overhead, I would look somewhere else FIRST , for ways to solve your "slow down" problem. Tell me how you measure the speed.
