You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

Fibers were tested in fixed locations on the RTM. To ensure that things are working as expected from this table, they should be placed in the same locations on the RTM according to the 2021 mapping.

Fiber / RTM combinationStatus
AOK
BOK
COK
DOK
EOK
FOK
G?
HPossible issue

QA of Flange Board ↔ FE0Bs

FEBFlange Board (HW)Flange ChannelI At Boot (AnaN, AnaP, Digi)I Mod ONI Mod ON + ConfigCtrl Ch
(dpm / ch)
(1 is top cob)
Fiber (ctrl / Data)

jTag OK

Feb AddressData TakingComment
L0-1t220.242 - 1.212 - 1.250

0.292 - 2.317 - 1.392

0.292 - 2.833 - 1.3220 / 3D / HY0OK
L2-3t300.256 - 1.248 - 1.2390.317 - 2.319 - 1.3140.313 - 3.112 - 1.3130 / 8D / HY2OK
L5t000.236 - 1.216 - 1.2870.272 - 2.101 - 1.3340.271 - 2.715 - 1.3341 / 5A / EY6OK
L6t010.249 - 1.222 - 1.3620.313 - 2.743 - 1.4340.308 - 3.539 - 1.4341 / 4A / EY8OK
L4b ( In EPICS is L4t)210.248 - 1.241 - 1.248

0 / 4C / GY5
Hybrid 1 and Hybrid 3 give check transaction errors at the power up. Those correspond to Ly6 hybrids in the test setup..Probably broken feb? Also noticed two HV pins missing.
L4t ( In EPICS is L4b)100.252 1.153 1.3740.307 - 2.8755 - 1.4480.304 - 3.564 - 1.4491 / 8B / FY4OK
L5b110.246 - 1.169 - 1.2430.306 - 2.242 - 1.3460.302 - 3.063 - 1.3211 / 7B / FY7

L6b120.248-1.199-1.2780.307 - 2.705 -1.3450.304 - 3.525 - 1.3481 / 6B / FY9

L0-1b200.241 - 1.284 - 1.3130.293 - 2.235 - 1.3940.293 - 2.931 - 1.3940 / 5C / GY1

L2-3b310.248 - 1.122 - 1.1950.308 - 2.324 - 1.2670.305 - 3.153 - 1.2670 / 7D / HY3NOTimeouts on DPM


Current Issues with Back-end.

List of issues we observed during local data taking relative to the Back - End.
NOTICE!!! The dpm numbers in the daq map after 7 are off by one. Example: DataDpm[13] in the DAQ Map is hostname dpm14.


1)

RCEData pathIssue
Dpm[6] 0Feb3 (L2-3b) connected. Observed timeout waiting for data. Observed TriggersOut lagging wrt TriggerIn during local data taking (96 vs 891 expected). Doesn't lose sync.
Dpm[6]1Feb3 (L2-3b) connected. SampleExtractor shows triggers out lagging wrt Trigger In. Doesn't lose sync.


Attempts to diagnose the error:

  • Swap fiber H with F (changes channels in the RTM). 
  • Reset COBs to change DaqMap. Now Feb3 is on dpm13 and dpm14. Observed timeout waiting for data.
  • We moved the hybrids to top FEBs. (L01-t and L23-t). Reset COBs. We observed the same issue on L23-t => possibly related to the hybrids or flange board.
  • Moved Layer0 modules on L23-t FEB. That FEB is on flange 3. Copied updated config with module swap to rce-test-eel-swap.yml. Same errors. We suspect the flange board but we see no errors on the dpm data links. So that's odd.
  • Moved Layer0 modules on Ly01-t FEB. Worked fine. Also tested hybrid L23 on L23-t Feb: all OK
  • Tested L23 on FEB L23b and saw timeout on data dpms.
  • Changed flange-board from 3 to 2. Saw timeout on data dpms. Suspect FEB
  • Changed data fiber from F to E. Saw timeout errors on data dpms. Observed increasing RxFrame and RxCell Error counts during data taking on dpm[9] data link 1.


Test outcome: we think that FEB 23B (SN 14) has some issue we need to discuss with Ben.

Situation at the end of the run: Link errors on dpm[9] Pgp link 1. No other apparent issue observed.




  • No labels