Non-intelligent acquisition devices are basically electronic converters attached to large-scale data registers. The problem is to operate these devices the way they need to be operated, when they need to be operated, to make sure that you capture all of your measurement data. It's a sort of service architecture, but backwards.
You don't want to deadlock your application waiting for data that aren't yet available, but you don't want delayed processing when data are ready. You don't want to read too soon and pick up buffer garbage, but you don't want to wait too long and lose unprocessed data. An intelligent solution takes care of these very real concerns so you do not have to think about them. The DAPcell server makes data available, and your application takes the data on its own terms.
In a stable DAPL architecture, a lot of things happen behind the scenes, with the DAPL system and the DAPcell services working in combination to deliver data in the amounts that you want and in the place that you want. There is no need for a device control protocol, because the data are recovered from hardware devices automatically by the DAPL system. There is no need to be concerned about transient delays because the DAPL system and DAPcell services will buffer the data intelligently. This works the same way for any mix of data types, any mix of Data Acquisition Processor models, any number of channels, and any number of boards, in combination or independently.