Notes about MVD hardware address


The format of MCM data packets is given here. The format of DCIM data packets is given here. From the DCIM, the packets go the the DCM, which adds further framing information as described here. The event builder home page also describes the frame format -- which appears to contain additional stuff wrapped around the DCM packet.

The information needed to associate a particular MCM/Si-detector with the packets is not conveniently organized. This information is as follows:

  • Each DCIM output packet contains the DCIM number, which is set via jumpers on the DCIM. This number is the 4th word of a DCIM packet (ModAdd).
  • Each DCIM output packet contains an odd/even bit (MUX bit in the tables) which says whether is is packet 0,2,4 (even) or 1,3,5 (odd) in the multiplexed output mode. This is bit 14 (bits are counted 0-15, with 15 the highest) of User Word 8.
  • The packet ID is a number of the format 2000+i (for the MVD) where i ranges from 1 to 999 and i=0 is reserved. As the documentation says: "The packet id in the PRDF data format (version 0) is a 32-bit value which is a unique identifier of where the data came from (eg. which drift chamber FEM card). The packet ids are specified in a configuration file (sample here for 1 DCM) and then added into the data stream by the DCMs.

    From the combination of these pieces of information and careful cabling, the DCIM output packet can be used to determine which MCM is came from.

    There was a request (maybe a rule?) that the packetID values be consecutive and start from 1. This makes it impossible for us to use a numbering system for packetIDs which is both
    1) The same in year-1 and later years
    2) related in a simple was to the r,phi,z position of the detector element.

    I propose to keep the same general organization (as in year-1) of the packetID numbers. The barrel data come first, then the pads. Within the barrel the z index runs fastest, then phi, then shell. Within the pads the phi index runs fastest and the z index is next.

    North end, inner barrel addressing:

    r phi z packet ID DCIM addr. DCIM out# MUX bit DCM slot, input# DCM cable # notes
    0 0 6 2001 1 5 1 6,1 1 NW IM6, SN7
    0 0 7 2002 1 5 0 6,1 1 NW IM5, SN7
    0 0 8 2003 1 4 1 6,2 2 NW IM4, SN7
    0 0 9 2004 1 4 0 6,2 2 not there, SN7
    0 0 10 -- 1 1 1 -- -- not there, SN7
    0 0 11 -- 1 1 0 -- -- not there, SN7
    0 1 6 2005 2 5 1 6,3 3 NW IT6, SN5
    0 1 7 2006 2 5 0 6,3 3 NW IT5, SN5
    0 1 8 2007 2 4 1 6,4 4 NW IT4, SN5
    0 1 9 2008 2 4 0 6,4 4 not there, SN5
    0 1 10 -- 2 1 1 -- -- not there, SN5
    0 1 11 -- 2 1 0 -- -- not there, SN5
    0 2 6 2009 3 5 1 7,1 5 NE IT6, SN P1
    0 2 7 2010 3 5 0 7,1 5 NE IT5, SN P1
    0 2 8 -- 3 4 1 -- -- not there, SN P1
    0 2 9 -- 3 4 0 -- -- not there, SN P1
    0 2 10 -- 3 1 1 -- -- not there, SN P1
    0 2 11 -- 3 1 0 -- -- not there, SN P1
    0 3 6 2011 4 5 1 7,2 6 NE IM6, SN9
    0 3 7 2012 4 5 0 7,2 6 NE IM5, SN9
    0 3 8 2013 4 4 1 7,3 7 NE IM4, SN9, bad chan?
    0 3 9 2014 4 4 0 7,3 7 not there, SN9, bad chan?
    0 3 10 -- 4 1 1 -- -- not there, SN9
    0 3 11 -- 4 1 0 -- -- not there, SN9
    0 4 6 2015 5 5 1 7,4 8 NE IB6, SN6
    0 4 7 2016 5 5 0 7,4 8 NE IB5, SN6
    0 4 8 2017 5 4 1 8,1 9 NE IB4, SN6
    0 4 9 2018 5 4 0 8,1 9 NE IB3, SN6
    0 4 10 -- 5 1 1 -- -- not there, SN6
    0 4 11 -- 5 1 0 -- -- not there, SN6
    0 5 6 2019 6 5 1 8,2 10 NW IB6, SN0
    0 5 7 2020 6 5 0 8,2 10 NW IB5, SN0
    0 5 8 2021 6 4 1 8,3 11 NW IB4, SN0
    0 5 9 2022 6 4 0 8,3 11 NW IB3, SN0
    0 5 10 2023 6 1 1 8,4 12 NW IB2, SN0
    0 5 11 2024 6 1 0 8,4 12 not there, SN0

    North end, outer barrel addressing:

    r phi z packet ID DCIM addr. DCIM out# MUX bit DCM slot, input# DCM cable # notes
    1 4 6 2025 7 5 1 9,1 13 NE OB6, SN10
    1 4 7 2026 7 5 0 9,1 13 NE OB5, SN10
    1 4 8 2027 7 4 1 9,2 14 NE OB4, SN10
    1 4 9 2028 7 4 0 9,2 14 NE OB3, SN10
    1 4 10 -- 7 1 1 -- -- not there, SN10
    1 4 11 -- 7 1 0 -- -- not there, SN10
    1 5 6 2029 8 5 1 9,3 15 NW OB6, SN4
    1 5 7 2030 8 5 0 9,3 15 NW OB5, SN4
    1 5 8 2031 8 4 1 9,4 16 NW OB4, SN4
    1 5 9 2032 8 4 0 9,4 16 NW OB3, SN4
    1 5 10 2033 8 1 1 10,1 17 NW OB2, SN4
    1 5 11 2034 8 1 0 10,1 17 not there, SN4

    North endcap pads addressing:

    z (end) phi (wedge) packet ID DCIM adde. DCIM out# MUX bit DCM slot, input# DCM cable # notes
    1 0 2035 9 4 1 10,3 19 NE pad4, SN P2
    1 1 2036 9 5 0 10,2 18 NE pad5, SN P2
    1 2 2037 9 5 1 10,2 18 NE pad6, SN P2
    1 3 2038 10 5 1 11,1 21 NW pad6, SN3
    1 4 2039 10 5 0 11,1 21 NW pad5, SN3
    1 5 2040 10 4 1 11,2 22 NW pad4, SN3
    1 6 2041 10 4 0 11,2 22 NW pad3, SN3
    1 7 2042 10 1 1 11,3 23 NW pad2, SN3
    1 8 2043 10 1 0 11,3 23 NW pad1, SN3
    1 9 2044 9 1 0 10,4 20 NE pad1, SN P2
    1 10 2045 9 1 1 10,4 20 NE pad2, SN P2
    1 11 2046 9 4 0 10,3 19 NE pad3, SN P2

    In the tables above, the DCM cable number is the number on the fiber-optic cable which goes from
    a) the DCIM output to the patch panel on the west side on the central magnet
    b) the patch panel in Bldg 1008 to the DCM
    The cable numbers are the same in the two places.

    Comments and suggestions appreciated.


    updated 12-Feb-2001
    John Sullivan