Difference: RpcDataStructure (1 vs. 11)

Revision 11
01 Aug 2007 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Added:
>
>

TRBv1 structure

  Word: Contents: Description:
Revision 10
09 Feb 2007 - Main.MarekPalka
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Word: Contents: Description:
Line: 87 to 87
  4 trigger tag Trigger tag of subevent # subEvent
Changed:
<
<
5 0xTT TC NW NW Internal header, where TT is Trigger Tag, TC is the trigger code, and NW is number of words of the subEvent (including header and trailer (with optional 0xdeadface), 16 bits, MSB first.
>
>
5 0xTC TT NW NW Internal header, where TC is the trigger code, TT is Trigger Tag, and NW is number of words of the subEvent (including header and trailer (with optional 0xdeadface), 16 bits, MSB first.
 

6 0xVV XX NE NE Second header word: VV: Version number of data-format, XX: all bits reserved, except the lower most which defines if pairing mode was used, NE: Number of words in the data-extension
Revision 9
12 Jan 2006 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Word: Contents: Description:
Line: 53 to 53
  000000f0: 0x330d7021 0x240d7051 0x44f85d6e 0x340d7003 00000100: 0xdeadface
Added:
>
>

New data-format of the TRB

Experience shows that a fixed data-format never is sufficient for all possible future extensions and ideas. There will be different usages for the TRB with different requirement, so for example we have
  • a request of the LIP-group to put counter-data into the data-stream
  • a bit has to be introduced, which distinguishes between paired mode and edge-modes.
  • for calibration events we have to put the whole configuration bits of the TDC into the data-stream
  • future extensions

Therefore I suggest to extend the data format in the following way:

  • The header should consist of two 32 bit words
  • They should contain:
    • The overall length of the data sent in this event, 16 bit
    • The trigger tag and code
    • If the data contains paired or edge-data
    • A second length (16-bit), which tells the length of the "additional" data
    • a version number of the data structure. It uniquely describes the exact meaning of the "additional" data.

  • The "deadface" at the end of the event, should be optional and possible to be turned off and on by a register in the FPGA.

So it looks like this:

# RPC Header
 
 1        size                    Length of whole subevent 
 2        0x3001                  SubEvt Decoding as 32bit Data
 3        subdetecor-ID           Non-ambiguous ID. Set to 0x221
 4        trigger tag             Trigger tag of subevent
# subEvent

 5        0xTT TC NW NW           Internal header, where TT is Trigger Tag, TC is the trigger code, and NW is number of words of the subEvent (including header and trailer (with optional 0xdeadface), 16 bits, MSB first.

 6        0xVV XX NE NE           Second header word: VV: Version number of data-format, XX: all bits reserved, except the lower most which defines if pairing mode was used, NE: Number of words in the data-extension

 7        0x........              first word of extension data (for example 10 counter values)
 7+1      0x.....
...
...
 7+NE     0x330d701b              TDC data starts here. first word of event, NE word later
          0x........              next word 
          0x........              next word 
 N-1      0x........             (N-1)th word of event  
 N        0xdeadface              last word , optional

  -- RadekTrebacz - 22 Sep 2005
Revision 8
08 Nov 2005 - Main.RadekTrebacz
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Word: Contents: Description:
Line: 7 to 7
 

1 size Length of whole subevent 2 0x3001 SubEvt Decoding as 32bit Data
Changed:
<
<
3 subdetecor-ID Non-ambiguous ID. Set to 0x222
>
>
3 subdetecor-ID Non-ambiguous ID. Set to 0x221
  4 trigger tag Trigger tag of subevent # subEvent
Revision 7
07 Nov 2005 - Main.RadekTrebacz
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Word: Contents: Description:
Line: 21 to 21
  First word of the subEvent is started always as 0xbeefTTNW, and last word is 0xdeadface. 0xbeefTTNW is created by FPGA. 0xbeef and 0xdeadface are only markers, which is usefull to checking by Etrax that data transfer is ok. FPGA is counting how many words belong to each event and put this number as 0xNW. 0xTT is counter of events. Trigger tag of each next event is higher by 1. ....
Added:
>
>
Data word, which is begin from 0x2 is the header, from 0x3 is the trailer, from 0x6 is error, from 0x4 is the data.

We are using two type of measurement:
  1. Leading measurement - Single edge
  2. Leading measurement - Combined measurement of leading and trailing edge (pairing mode)
 

The datastructure of the long-words from the TDC are described in detail in the HPTDC-manual which is attached (page 24 to 26)
Revision 6
10 Oct 2005 - Main.RadekTrebacz
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Word: Contents: Description:
Line: 21 to 21
  First word of the subEvent is started always as 0xbeefTTNW, and last word is 0xdeadface. 0xbeefTTNW is created by FPGA. 0xbeef and 0xdeadface are only markers, which is usefull to checking by Etrax that data transfer is ok. FPGA is counting how many words belong to each event and put this number as 0xNW. 0xTT is counter of events. Trigger tag of each next event is higher by 1. ....
Added:
>
>
  The datastructure of the long-words from the TDC are described in detail in the HPTDC-manual which is attached (page 24 to 26)
Changed:
<
<
daq_sniff output id somethink like this:
>
>
daq_sniff output is something like this:
 
size: 0x00000134  decoding: 0x00030001  id:    0x00000222  seqNr:  0x000a2e6e  
date: 2005-09-22  time:     20:27:01    runNr: 0x42a1f5ee  expId:              
Revision 5
27 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Word: Contents: Description:
Line: 21 to 21
  First word of the subEvent is started always as 0xbeefTTNW, and last word is 0xdeadface. 0xbeefTTNW is created by FPGA. 0xbeef and 0xdeadface are only markers, which is usefull to checking by Etrax that data transfer is ok. FPGA is counting how many words belong to each event and put this number as 0xNW. 0xTT is counter of events. Trigger tag of each next event is higher by 1. ....
Changed:
<
<

Radek: You have to explain what this first word of event means! If it is pure TDC data, please add a link to the TDC manual (with page number!) or attach it to this wiki-page! It has to be clear for the reader, what is from the TRB and what is TDCdata. For the example you should explain how many events are in there and how many TDCs and so on. Don't be too brief, please!
>
>
The datastructure of the long-words from the TDC are described in detail in the HPTDC-manual which is attached (page 24 to 26)
 

daq_sniff output id somethink like this:
Line: 50 to 48
  00000100: 0xdeadface -- RadekTrebacz - 22 Sep 2005
Added:
>
>
 
Added:
>
>
META FILEATTACHMENT attr="" comment="The HPTDC Manual (version 2.2)" date="1127847924" name="CERN_hptdc2.2.pdf" path="CERN_hptdc2.2.pdf" size="1449473" user="MichaelTraxler" version="1.1"
Revision 4
26 Sep 2005 - Main.RadekTrebacz
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Word: Contents: Description:
Line: 19 to 19
  N 0xdeadface last word First word of the subEvent is started always as 0xbeefTTNW, and last word is 0xdeadface.
Changed:
<
<
>
>
0xbeefTTNW is created by FPGA. 0xbeef and 0xdeadface are only markers, which is usefull to checking by Etrax that data transfer is ok. FPGA is counting how many words belong to each event and put this number as 0xNW. 0xTT is counter of events. Trigger tag of each next event is higher by 1. ....
 

Radek: You have to explain what this first word of event means! If it is pure TDC data, please add a link to the TDC manual (with page number!) or attach it to this wiki-page! It has to be clear for the reader, what is from the TRB and what is TDCdata. For the example you should explain how many events are in there and how many TDCs and so on. Don't be too brief, please!
Revision 3
23 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Word: Contents: Description:
Line: 7 to 7
 

1 size Length of whole subevent 2 0x3001 SubEvt Decoding as 32bit Data
Changed:
<
<
3 MU ID Non-ambiguous ID. Set to 0x222
>
>
3 subdetecor-ID Non-ambiguous ID. Set to 0x222
  4 trigger tag Trigger tag of subevent # subEvent
Line: 20 to 20
  First word of the subEvent is started always as 0xbeefTTNW, and last word is 0xdeadface.
Added:
>
>

Radek: You have to explain what this first word of event means! If it is pure TDC data, please add a link to the TDC manual (with page number!) or attach it to this wiki-page! It has to be clear for the reader, what is from the TRB and what is TDCdata. For the example you should explain how many events are in there and how many TDCs and so on. Don't be too brief, please!
  daq_sniff output id somethink like this:
size: 0x00000134  decoding: 0x00030001  id:    0x00000222  seqNr:  0x000a2e6e  
Revision 2
23 Sep 2005 - Main.KrzysztofKorcyl
Line: 1 to 1
 
META TOPICPARENT name="TDCReadoutBoard"
Deleted:
<
<
  Word: Contents: Description:
Line: 12 to 11
  4 trigger tag Trigger tag of subevent # subEvent
Changed:
<
<
5 0xbeefTTNW Internal header, where TT is Trigger Tag and NW is number of words
>
>
5 0xbeefTTNW Internal header, where TT is Trigger Tag and NW is number of words of the subEvent (including header and trailer (0xdeadface)
  6 0x330d701b first word of event 0x........ next word 0x........ next word N-1 0x........ (N-5)th word of event N 0xdeadface last word
Changed:
<
<
First word of the subEvent is started always as 0xbeef, and last word is 0xdeadface.
>
>
First word of the subEvent is started always as 0xbeefTTNW, and last word is 0xdeadface.
 

daq_sniff output id somethink like this:
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)