I'm delighted that it works now.
Personally, I dislike the Adapt module.It can create as many problems as it fixes.
Remember to try all synchronization options before resorting the Signal Adaptation module.
When using software controls, such as the Switch or Slider, they allow you to both choose another Timebase (they default to Driver), or, you can create a timing input on them ("With Input"). This seems to work well when trying to work with averaged, separated, or relayed data where the original timing has been changed.
Another frequent error can be resolved by verifying that the AVERAGE module is configured the same way for each channel.
When using Signal Adapt, the faster channel should be connected to the Channel 0 of the module. That's the pacer, and other channels are interpolated up to the higher speed.
And finally, don't put Adapt modules in series. If the timing is really that problematic, then you may need to step back and review the application logic to figure out a different approach.
When I have to resort to using a Signal Adapt module, I usually turn on the View -> Animation-> FIFO Status (FIFO Filling Level) to monitor the data flow in the worksheet. Over the years, I've seen too many worksheets crawl to a stop because of very small timing changes.
In summary, I really dislike the Signal Adapt module. It's a last resort for me. I try to figure out the problem and work around it. I have some worksheets where the data gets stored in Global Variables using the Write Variable module, and read back using Read Variable, simply to fix a timing problem.
Measurement Computing (MCC) has free technical support. Visit
www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.
