5.2.3 Status Register (base + 2)
The status register is read only and shares the same offset as the control register. It reports data FIFO flag, A/D interrupt and A/D conversion status. Table
Table
| Bit |
| Status |
| Explanation |
| |
|
|
|
| ||||
| 7 |
| Scanning status |
| 0/1 : busy / idle |
|
|
| 6 |
| A/D running status |
| 0/1 : no / yes |
|
|
| 5 |
| Data lost event |
| 0/1 : no / yes |
|
|
| 4 |
| End of scan event |
| 0/1 : no / yes |
|
|
| 3 |
| FIFO threshold event |
| 0/1 : no / yes |
|
|
| 2 |
| Data FIFO full |
| 0/1 : false / true |
|
|
| 1 |
| Data FIFO almost full |
| 0/1 : false / true |
|
|
| 0 |
| Data FIFO empty |
| 0/1 : false / true |
|
|
|
|
|
|
|
|
|
|
Bit 7 shows the scan status and is set to “0” when the DAQP card is scanning the input channels specified by the scan list and then “1” upon scan completion.
Bit 6 is the A/D running flag. A “1” here indicates indicates the DAQP card has been triggered and is acquiring data (busy), while a “0” means it is idle. If the
Bit 3, 4 and 5 are the event latches. When an event is detected, the corresponding bit will be set to “1” until the status register is read which then clears all event bits to “0”. Bit 5 is used for data lost events, bit 4 for
Each time the status register is read, the latched events (bits 3, 4 and 5) will be cleared. This structure is very efficient, yet it can cause events to be lost if the read action overwrites the event setting so that the corresponding event gets lost. This can be critical in a tight
48 |