S800 Documentation

User Tools

Site Tools

Trace:
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/28 18:31]
pereira [Tag 0x0DDC: Mesytec MTDC-32 module] 		s800_usb_daq_data_format [2015/10/30 12:15]
pereira [Tag 0x7186: Phillips 7186 TDC module for time-of-flights]
Line 107: Line 107:
 ^ 0x7186 ^ hit pattern ^ ADC data... ^ 0xf186 | ^ 0x7186 ^ hit pattern ^ ADC data... ^ 0xf186 |
  
-The TDC data contains all channels for which the hit pattern bit is set. The channel number is encoded in bits 12-15, while the data is in bits 0-11. The table below shows the channel assignments. +The TDC data contains all channels for which the hit pattern bit is set. The channel number is encoded in bits 12-15, while the data is in bits 0-11. The channel assignments can be found [[Timing#Phillips TDC|here]]
- +
-^ Channel ^ Assignment | +
-| 0 | E1_up | +
-| 1 | E1_down | +
-| 2-7 | Available | +
-| 8 | S800 source | +
-| 9 | External 1 source | +
-| 10 | External 2 source | +
-| 11 | Secondary source | +
-| 12 | RF TOF | +
-| 13 | Object TOF | +
-| 14 | XF TOF | +
-| 15 | Available | +
  
 ==== Tag 0x4448: LeCroy4448 coincidence register module for hodoscope hit pattern ==== ==== Tag 0x4448: LeCroy4448 coincidence register module for hodoscope hit pattern ====
Line 216: Line 202:
 ^ 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 |
  
-The number of data words depend on the number of channels receiving signals, and the number of "hits" received on each channel. The figures below illustrates how the data are coded; in the example, the MTDC window has a +The number of data words depend on the number of channels receiving signals, and the number of "hits" received on each channel. The figure below illustrates how the data are coded; in the example, the MTDC window has a 
 -1017-ns delay (with respect to the trigger trig0) and 641-ns width.  -1017-ns delay (with respect to the trigger trig0) and 641-ns width. 
  
  
-{{:wiki:MTDC_structure_diagram.jpg?300}}+{{:wiki:MTDC_structure_diagram.jpg?550}}
  
  
 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?300}}+{{:wiki:MTDC_datastructure.jpg?900}}
  
  
s800_usb_daq_data_format.txt · Last modified: 2018/05/11 14:09 by pereira

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki