Notes about MVD hardware address (year-3)


Versions of this document for earlier runs are different. The year-1 version of this document is different, Look here to the year-1 version. Look here to the year-2 version.

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 120 (in principle we are allowed to use numbers up to 2999) 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 each year as channels are added to the MVD
    2) related in a simple way 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.

    Look here or here to see the first version of the "pcf" file which is used by the DCMs to relate the DCM slot and input number to the packet number.

    Look at this pdf file or this powerpoint file for sketches of the locations of the packets and notes about current performance.

    inner barrel addressing:

    r phi z packet
    ID
    DCIM
    addr.
    DCIM
    out#
    MUX
    bit
    DCM
    slot,
    input#
    DCM
    cable
    notes
    0 0 0 2001 1 1 0 3,1 1 SW IM1, SN26
    0 0 1 2002 1 1 1 3,1 1 SW IM2, SN26
    0 0 2 2003 1 4 0 3,2 2 SW IM3, SN26
    0 0 3 2004 1 4 1 3,2 2 SW IM4, SN26
    0 0 4 2005 1 5 0 3,3 3 SW IM5, SN26
    0 0 5 2006 1 5 1 3,3 3 SW IM6, SN26
    0 0 6 2007 2 5 1 3,4 4 NW IM6, SN12
    0 0 7 2008 2 5 0 3,4 4 NW IM5, SN12
    0 0 8 2009 2 4 1 4,1 5 NW IM4, SN12
    0 0 9 2010 2 4 0 4,1 5 NW IM3, SN12
    0 0 10 2011 2 1 1 4,2 6 NW IM2, SN12
    0 0 11 2012 2 1 0 4,2 6 NW IM1, SN12
    0 1 0 2013 3 1 0 4,3 7 SW IT1, SN34
    0 1 1 2014 3 1 1 4,3 7 SW IT2, SN34
    0 1 2 2015 3 4 0 4,4 8 SW IT3, SN34
    0 1 3 2016 3 4 1 4,4 8 SW IT4, SN34
    0 1 4 2017 3 5 0 5,1 9 SW IT5, SN34
    0 1 5 2018 3 5 1 5,1 9 SW, IT6, SN34
    0 1 6 2019 4 5 1 5,2 10 NW IT6, SN17
    0 1 7 2020 4 5 0 5,2 10 NW IT5, SN17
    0 1 8 2021 4 4 1 5,3 11 NW IT4, SN17
    0 1 9 2022 4 4 0 5,3 11 NW IT3, SN17
    0 1 10 2023 4 1 1 5,4 12 NW IT2, SN17
    0 1 11 2024 4 1 0 5,4 12 NW IT1, SN17
    0 2 0 2025 5 1 0 6,1 13 SE IT1, SN6
    0 2 1 2026 5 1 1 6,1 13 SE IT2, SN6
    0 2 2 2027 5 4 0 6,2 14 SE IT3, SN6
    0 2 3 2028 5 4 1 6,2 14 SE IT4, SN6
    0 2 4 2029 5 5 0 6,3 15 SE IT5, SN6
    0 2 5 2030 5 5 1 6,3 15 SE IT6, SN6
    0 2 6 2031 6 5 1 6,4 16 NE IT6, SN 20
    0 2 7 2032 6 5 0 6,4 16 NE IT5, SN 20
    0 2 8 2033 6 4 1 7,1 17 NE IT4, SN 20
    0 2 9 2034 6 4 0 7,1 17 NE IT3, SN 20
    0 2 10 2035 6 1 1 7,2 18 NE IT2, SN 20
    0 2 11 2036 6 1 0 7,2 18 NE IT1, SN 20
    0 3 0 2037 7 1 0 7,3 19 SE IM1, SN32
    0 3 1 2038 7 1 1 7,3 19 SE IM2, SN32
    0 3 2 2039 7 4 0 7,4 20 SE IM3, SN32
    0 3 3 2040 7 4 1 7,4 20 SE IM4, SN32
    0 3 4 2041 7 5 0 8,1 21 SE IM5, SN32
    0 3 5 2042 7 5 1 8,1 21 SE IM6, SN32
    0 3 6 2043 8 5 1 8,2 22 NE IM6, SN16
    0 3 7 2044 8 5 0 8,2 22 NE IM5, SN16
    0 3 8 2045 8 4 1 8,3 23 NE IM4, SN16
    0 3 9 2046 8 4 0 8,3 23 NE IM3, SN16
    0 3 10 2047 8 1 1 8,4 24 NE IM2, SN16
    0 3 11 2048 8 1 0 8,4 24 NE IM1, SN16
    0 4 0 2049 9 1 0 9,1 25 SE IB1, SN28
    0 4 1 2050 9 1 1 9,1 25 SE IB2, SN28
    0 4 2 2051 9 4 0 9,2 26 SE IB3, SN28
    0 4 3 2052 9 4 1 9,2 26 SE IB4, SN28
    0 4 4 2053 9 5 0 9,3 27 SE IB5, SN28
    0 4 5 2054 9 5 1 9,3 27 SE IB6, SN28
    0 4 6 2055 10 5 1 9,4 28 NE IB6, SN4
    0 4 7 2056 10 5 0 9,4 28 NE IB5, SN4
    0 4 8 2057 10 4 1 10,1 29 NE IB4, SN4
    0 4 9 2058 10 4 0 10,1 29 NE IB3, SN4
    0 4 10 2059 10 1 1 10,2 30 NE IB2, SN4
    0 4 11 2060 10 1 0 10,2 30 NE IB1, SN4
    0 5 0 2061 11 1 0 10,3 31 SW IB1, SN27
    0 5 1 2062 11 1 1 10,3 31 SW IB2, SN27
    0 5 2 2063 11 4 0 10,4 32 SW IB3, SN27
    0 5 3 2064 11 4 1 10,4 32 SW IB4, SN27
    0 5 4 2065 11 5 0 14,1 33 SW IB5, SN27
    0 5 5 2066 11 5 1 14,1 33 SW IB6, SN27
    0 5 6 2067 12 5 1 14,2 34 NW IB6, SN3
    0 5 7 2068 12 5 0 14,2 34 NW IB5, SN3
    0 5 8 2069 12 4 1 14,3 35 NW IB4, SN3
    0 5 9 2070 12 4 0 14,3 35 NW IB3, SN3
    0 5 10 2071 12 1 1 14,4 61 NW IB2, SN3
    0 5 11 2072 12 1 0 14,4 61 NW IB1, SN3

    Outer barrel addressing:

    r phi z packet
    ID
    DCIM
    addr.
    DCIM
    out#
    MUX
    bit
    DCM
    slot,
    input#
    DCM
    cable
    notes
    1 4 0 2073 13 1 0 15,1 37 SE OB1, SN22
    1 4 1 2074 13 1 1 15,1 37 SE OB2, SN22
    1 4 2 2075 13 4 0 15,2 38 SE OB3, SN22
    1 4 3 2076 13 4 1 15,2 38 SE OB4, SN22
    1 4 4 2077 13 5 0 15,3 39 SE OB5, SN22
    1 4 5 2078 13 5 1 15,3 39 SE OB6, SN22
    1 4 6 2079 14 5 1 15,4 40 NE OB6, SN P2
    1 4 7 2080 14 5 0 15,4 40 NE OB5, SN P2
    1 4 8 2081 14 4 1 16,1 41 NE OB4, SN P2
    1 4 9 2082 14 4 0 16,1 41 NE OB3, SN P2
    1 4 10 2083 14 1 1 16,2 42 NE OB2, SN P2
    1 4 11 2084 14 1 0 16,2 42 NE OB1, SN P2
    1 5 0 2085 15 1 0 16,3 43 SW OB1, SN30
    1 5 1 2086 15 1 1 16,3 43 SW OB2, SN30
    1 5 2 2087 15 4 0 16,4 44 SW OB3, SN30
    1 5 3 2088 15 4 1 16,4 44 SW OB4, SN30
    1 5 4 2089 15 5 0 17,1 45 SW OB5, SN30
    1 5 5 2090 15 5 1 17,1 45 SW OB6, SN30
    1 5 6 2091 16 5 1 17,2 46 NW OB6, SN0
    1 5 7 2092 16 5 0 17,2 46 NW OB5, SN0
    1 5 8 2093 16 4 1 17,3 47 NW OB4, SN0
    1 5 9 2094 16 4 0 17,3 47 NW OB3, SN0
    1 5 10 2095 16 1 1 17,4 48 NW OB2, SN0
    1 5 11 2096 16 1 0 17,4 48 NW OB1, SN0

    Note added 3-Feb-2003: For the pads, I got confused about East and West when I originally defined this table. As a result, the packet numbers do not have a simple relationship with the phi and z location. However, it seemed to be too much trouble to change the packet numbers at this time. The only thing which differs between this table and the old (wrong) table is the column labeled "phi". If you really want to know the old (wrong) phi address, you can calculate it -- in every case (old wrong phi address) + (new correct phi address) = either 5 (for new or old address less than 6) or 17 (for new or old address 6 or greater). For example, NE pad 4, new address = 5, therefore old wrong address was 5-5 = 0. SW pad 1, new address = 8, old wrong address was 17-8 = 9.

    South endcap pads addressing:

    z phi packet
    ID
    DCIM
    addr.
    DCIM
    out#
    MUX
    bit
    DCM
    slot,
    input#
    DCM
    cable
    notes
    0 5 2097 17 4 1 18,2 50 SE pad4, SN33
    0 4 2098 17 5 0 18,1 49 SE pad5, SN33
    0 3 2099 17 5 1 18,1 49 SE pad6, SN33
    0 2 2100 18 5 1 18,4 52 SW pad6, SN25
    0 1 2101 18 5 0 18,4 52 SW pad5, SN25
    0 0 2102 18 4 1 19,1 53 SW pad4, SN25
    0 11 2103 18 4 0 19,1 53 SW pad3, SN25
    0 10 2104 18 1 1 19,2 54 SW pad2, SN25
    0 9 2105 18 1 0 19,2 54 SW pad1, SN25
    0 8 2106 17 1 0 18,3 51 SE pad1, SN33
    0 7 2107 17 1 1 18,3 51 SE pad2, SN33
    0 6 2108 17 4 0 18,2 50 SE pad3, SN33

    North endcap pads addressing:

    z phi packet
    ID
    DCIM
    addr.
    DCIM
    out#
    MUX
    bit
    DCM
    slot,
    input#
    DCM
    cable
    notes
    1 5 2109 19 4 1 19,4 56 NE pad4, SN19
    1 4 2110 19 5 0 19,3 55 NE pad5, SN19
    1 3 2111 19 5 1 19,3 55 NE pad6, SN19
    1 2 2112 20 5 1 20,2 58 NW pad6, SN21
    1 1 2113 20 5 0 20,2 58 NW pad5, SN21
    1 0 2114 20 4 1 20,3 59 NW pad4, SN21
    1 11 2115 20 4 0 20,3 59 NW pad3, SN21
    1 10 2116 20 1 1 20,4 60 NW pad2, SN21
    1 9 2117 20 1 0 20,4 60 NW pad1, SN21
    1 8 2118 19 1 0 20,1 57 NE pad1, SN19
    1 7 2119 19 1 1 20,1 57 NE pad2, SN19
    1 6 2120 19 4 0 19,4 56 NE pad3, SN19

    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.

    The DCM slots start with number 0 -- slot 0 contains the crate controller.

    Some totals:
    60 DCIM cables are used (Number 36 is bad)
    9 extra DCIM cables (numbers go up to 69, 61 used to replace cable 36)
    15 DCM modules
    20 DCIM modules
    120 packets ID's

    Comments and suggestions appreciated.


    updated 13-Mar-2003
    John Sullivan