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
Next revision Both sides next revision
s800_usb_daq_data_format [2015/10/30 16:15]
pereira [VME Crate data format]
s800_usb_daq_data_format [2015/11/01 08:12]
pereira [Tag 0x0DDC: Mesytec MTDC-32 module]
Line 44: Line 44:
  
 ==== 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 223: Line 224:
 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?1100}}
  
  
s800_usb_daq_data_format.txt ยท Last modified: 2018/05/11 14:09 by pereira