-- Main.AntonJusko - 28 May 2009 Our knowledge about TRD inputs: |*agreed_name*| *CTPin* | *L0SWITCHin* | *DIMchannel* | *Signature* | |trdpim02 | 14/0 | 11 | - | - | |TRDL0 | 15/0 | 12 | 1 | 83 | |trdpim01 | - | 24 | - | - | |trdpim03 | - | - | - | - | |trdpim05 | - | - | - | - | |trdpim07 | - | - | - | - | |1HTS1 | 9/1 | - | 1 | (81) | |TRDL2 | 10/1 | - | 2 | (82) | With Stefan K. we agreed on 2 TIN proxy servers for TRD: *TRD_GTU* and *TRD_PT*. They will use DIM channel numbering from 1 (2 different servers). Signatures 80..89 are allocated for TRD_PT, 90-99 for TRD_GTU. TRD_GTU is using DIM_DNS_NODE alitrddimdns. We tested 1HTS1 and TRDL2 inputs with toggling signal and signatures 81 and 82 - signal is fine. Phase measurements are here [[%ATTACHURL%/trd_gtu_1hts1.ps][1HTS1]] [[%ATTACHURL%/trd_gtu_trdl2.ps][TRDL2]]. Positive edge to be used with these inputs.<br> In random mode, we got the rate ~2hz. Todo: * TRD_GTU: * TINproxy code is ready, the command names to be changed to STATUS_OPTIONCODE and SET_OPTIONCODE * signature allocation should be done (81 82 are values used for today's test, but signatures from 90 to be used...) * TRD_PT: * TINproxy code should be prepared * signatures and DIM channels allocation for L0 inputs (if there is more than TRDL0/83/1 defined today). * CTP: we will keep in mind, that TIN proxies can run in different DIM domains
Attachments
Attachments
Topic attachments
I
Attachment
History
Action
Size
Date
Who
Comment
ps
trd_gtu_1hts1.ps
r1
manage
29.0 K
28 May 2009 - 15:07
UnknownUser
ps
trd_gtu_trdl2.ps
r1
manage
29.0 K
28 May 2009 - 15:08
UnknownUser
This topic: ALICE
>
WebHome
>
DetectorCommunications
>
TrdInputs
Topic revision: r1 - 28 May 2009 - _47DC_61ch_47DC_61cern_47OU_61Organic_32Units_47OU_61Users_47CN_61juskoa_47CN_61403783_47CN_61Anton_32Jusko
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback