User Tools

Site Tools


s800_usb_daq_data_format

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
s800_usb_daq_data_format [2015/10/30 16:15]
pereira [VME Crate data format]
s800_usb_daq_data_format [2018/05/11 14:09] (current)
pereira [Tag 0x7167: Phillips 7164 ADC module for CRDC anodes (energies and TAC)]
Line 1: Line 1:
 ====== S800 USB DAQ data format ====== ====== S800 USB DAQ data format ======
  
-These pages contain information about the USB controller based data acquisition software of the S800. Two crates are read by the software (one CAMAC and one VME), but more could be easily added to the software. +These pages contain information about the USB controller based data acquisition software of the S800. Two crates are read by the software (one CAMAC and one VME), but more could be easily added to the software. The data format described here is irrelevant for the user. This is so because the USB data are "filtered" by the [[Event Filter|S800 Filter]] before being distributed to the user. 
- +
  
  
Line 44: Line 42:
  
 ==== Tag 0x2367: Trigger module ==== ==== Tag 0x2367: Trigger module ====
 +The [[Trigger|ULM trigger module]] provides a bit mask with information about the trigger sources, and a time-stamp value
  
 ^ 0x2367 ^ Trigger bits ^ TS 0-15 ^ TS 16-31 ^ TS 32-47 ^ TS 48-63 ^ 0xf367 | ^ 0x2367 ^ Trigger bits ^ TS 0-15 ^ TS 16-31 ^ TS 32-47 ^ TS 48-63 ^ 0xf367 |
Line 102: Line 101:
  
 ^ Channel ^ Assignment | ^ Channel ^ Assignment |
-| 0 | Available |+| 0 | Available (generally reserved for OBJ PIN)|
 | 1 | CRDC1 Anode | | 1 | CRDC1 Anode |
 | 2 | CRDC2 Anode | | 2 | CRDC2 Anode |
Line 110: Line 109:
 | 7 | XF TAC | | 7 | XF TAC |
 | 8 | Object TAC | | 8 | Object TAC |
-| 9-14 | Available |+| 9-13 | Available (generally reserved for Galotte) | 
 +14 | Available |
 | 15 | Hodoscope TAC | | 15 | Hodoscope TAC |
  
Line 210: Line 210:
  
 ==== Tag 0x0DDC: Mesytec MTDC-32 module ==== ==== Tag 0x0DDC: Mesytec MTDC-32 module ====
-This module has multi-hit capabilities and a better resolution than the Phillips TDC. The format of the data is determined by the module, and schematically shown below.+The [[Timing#MTDC|Mesytec TDC module (MTDC)]] has multi-hit capabilities and a better resolution than the Phillips TDC. The format of the data is determined by the module, and schematically shown below.
  
 ^ 0x0DDC ^ Header (0-15) ^ Header (16-31) ^ Data word (0-15) ^ Data word (16-31) ^ ... ^ Ender (0-15) ^ Ender (16-31) ^ 0xFDDC | ^ 0x0DDC ^ Header (0-15) ^ Header (16-31) ^ Data word (0-15) ^ Data word (16-31) ^ ... ^ Ender (0-15) ^ Ender (16-31) ^ 0xFDDC |
Line 223: Line 223:
 Channel 0 has three consecutive hits: The second hit (time: t0,1) is processes as long as it is separated from the preceding hit (time: t0,0) by more than 160 ns (the conversion time); the third hit is not processed because it "arrived" to the MTDC after the matching window was closed. Channels 7 and 11 have a single hit each within the matching window. The resulting data structure is illustrated in the figure below: Channel 0 has three consecutive hits: The second hit (time: t0,1) is processes as long as it is separated from the preceding hit (time: t0,0) by more than 160 ns (the conversion time); the third hit is not processed because it "arrived" to the MTDC after the matching window was closed. Channels 7 and 11 have a single hit each within the matching window. The resulting data structure is illustrated in the figure below:
  
-{{:wiki:MTDC_datastructure.jpg?900}}+{{:wiki:MTDC_datastructure.jpg?1200}}
  
  
s800_usb_daq_data_format.1446236106.txt.gz · Last modified: 2015/10/30 16:15 by pereira