DAP Architecture Features
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
|
|
|
|||||||||||||||
|
| | | ||||||||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
||||||||||||||||
 |
 |
 |
|
||||||||||||||
 |
 |
 |
 |
Point to elements to learn more about them. |
|
||||||||||||
 |
 |
|
|||||||||||||||
 |
|
||||||||||||||||
 |
 |
 |
|
||||||||||||||
 |
 |
 |
 |
 |
|
||||||||||||
 |
 |
 |
|
||||||||||||||
 |
|
||||||||||||||||
 |
 |
|
|||||||||||||||
 |
|
||||||||||||||||
 |
 |
 |
 |
|
|||||||||||||
 |
 |
|
|||||||||||||||
 |
 |
 |
 |
 |
 |
|
|||||||||||
 |
 |
|
|||||||||||||||
Modularization
Like spaghetti software, "spaghetti hardware" leaves too much to untangle for sophisticated designs. The DAP solution to hardware complexity, like the solution to software complexity, is modularization. Things closely related are packaged together. Things less directly related act through a well-defined interface.
The DAP architecture takes the concepts of modularization and interface far beyond what you will find in ordinary data acquisition products.
Timing and Synchronization
Detailed Information |
|---|
|
|
|
|
In addition to its onboard precision time reference, the DAP architecture allows external control of triggering, clocking, or both. Triggering determines when action starts and stops. Clocking determines when individual samples are captured or delivered. You can use one, or the other, or both in combination depending on the needs of your application.
There are some subtle differences, but the broad architectural features of triggering and clocking are very similar both for input sampling and for output updating. Triggering can act one time in a "one shot" mode, or suspend and resume repeatedly in a "gated" mode. Timing of individual samples or updates can use the internal clock, an external timing signal, or the unique "channel list clocking" scheme with a mix of both.
 |
Simplified processing and device control |  |
Consistent real-time response |  |
Smart buffering and data management |
