...
| Key name | Source | Write freq. [Hz] | Data size [byte] | Throughput | FomatFormat | Notes |
|---|---|---|---|---|---|---|
DCTEL002_BUF | DEVIL723 | 2 | 32937 | ~128~64 | Cluster of: | LV cluster [flattened to str]
[DCTDyn (165 bytes)][4 bytes] [array of 4096 DBLs] |
DCTPS002_BUF | DEVIL723 | 2 | 32937 | ~128~64 | Cluster of: | LV cluster [flattened to str]
[DCTDyn (165 bytes)][4 bytes] [array of 4096 DBLs] |
DCTA*002_BUF | DEVIL724 (still running in test mode) | 4 | 32937 | ~256~128 | Cluster of: - DCTDyn - 4096 [DBL] | LV cluster [flattened to str]
[DCTDyn (165 bytes)][4 bytes] [array of 4096 DBLs] |
Total throughput
| Source | kbyte/s | Mbit/s |
|---|---|---|
| DEVIL723 | 128 kbyte/s (*) | ~0.125 Mbit/s (*) |
| DEVIL724 | 128 kbyte/s | ~0.125 Mbit/s |
| TOTAL | 256 kbyte/s | ~0.250 Mbit/s |
(*) NOTE: The DEVIL alternately acquires e-, e +, e-, e +, ... and does only one update at a time. As a consequence the throughput is not determined by the data volume of the 2 elements but by that of only one.
...
Immediately after the DCTDyn it follows an array af DBL of 4096 components. In LabVIEW the array serialization is made by a U32 containing the number of components of the array and then the array itselsf.
Meaningful offsets
The Be aware that the following offsets depends on the number of components of the "tau" array in the DCTDyn cluster. This number of components shouldn't change over time.
| Value | Offset [byte] | Data type |
|---|---|---|
| Acquisition pointer | 136 | U32 |
| First component of the data array | 169 | [DBL] |
...