Difference: TrbNetIPUChannel (1 vs. 4)

Revision 4
28 May 2009 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetUsersGuide"

IPU Data Channel

Line: 48 to 48
 

  • Length must be valid during the first dataready signal, error pattern must be valid while readout_finished is high
Changed:
<
<
-- JanMichel - 02 Jan 2009
>
>
  • Readout of an Event containing three data words on an IPU channel endpoint:
    Readout of an Event containing three data words on an IPU channel endpoint
 
Added:
>
>
META FILEATTACHMENT attr="" comment="Readout of an Event containing three data words on an IPU channel endpoint" date="1243516638" name="ipu_timing_diagram.png" path="ipu_timing_diagram.png" size="20775" user="JanMichel" version="1.1"
Revision 3
14 Jan 2009 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetUsersGuide"

IPU Data Channel

Line: 13 to 13
 
31 - 16 16 bit counter
3 - 0 Type
Added:
>
>
Word 15-12 11-8 7-4 3-0
F0 reserved (CRC)
F1 add. information random code
F2 trigger number
F3 0 seq. no. type
  The type and additional information are not yet defined and set to 0.
Revision 2
05 Jan 2009 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="TrbNetUsersGuide"

IPU Data Channel

Line: 39 to 39
 

  • The read signal will be low for one clock cycle after each dataready due to the conversion from 32 to 16 bit word size.
Changed:
<
<
  • Length and Error pattern must be valid during the whole readout process
>
>
  • Length must be valid during the first dataready signal, error pattern must be valid while readout_finished is high
 

-- JanMichel - 02 Jan 2009
 
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)