upgrade_of_fw_status
This is an old revision of the document!
Table of Contents
Status of the new firmware
— DAQ user 2018/06/18 07:26
Data Transfer
Each new window is tagged with an event packet
| CAFEDADE (4 bytes) | GTC (3 bytes) | 0 | ABCID (5 bytes) | DADECAFE (4 bytes) |
Each channel is read separately if there is data
| Header (2 bytes words) | |||||
|---|---|---|---|---|---|
| CAFE | BABE | GTC | GTC | Channel | Lines |
| and then per line | |||||
| channel (1 byte) | Coarse (4 bytes) | fine (1 byte) | |||
| Trailer (2 bytes word) | |||||
| BABE | CAFE |
Remaining bugs : From time to time (<1/min),an empty event header is sent with same GTC number , good ABCID and no channels, the event synchr is recovered on next event header. Since the DAQ is synchronised on GTC, no inefficiencies is seen. It might come from MDCC firmware
Data Structure
The data forwarded to the Event builder are grouped per event. It has similar structure to the previous one.
upgrade_of_fw_status.1529387178.txt.gz · Last modified: 2021/07/10 23:20 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
