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

Compare with Current View Page History

« Previous Version 7 Next »

To-Do List

  • fix TxLinkReset workaround
  • fix xpmmini-to-lcls2timing workaround
  • fix link-lock failure on timing system KCUs
  • manufacture new boards
  • check/fix loopback fiber problem in production in room 208 
  • work on high-speed-digitizer timing robustness
  • check wave8 timing robustness

Summary Of Testing

These are the results of the tests that have been conducted in the FEE alcove to determine if the XPM glitch can be reproduced.
Every test is run from a starting behavior where the DAQ can allocate, configure, run, and disable.
Whenever the DAQ does not follow the starting behavior remedies are applied to recover it.

XPM firmware 3.5.4
Opal_config.py still has xpm mini – timing2 hack

In 2023/10/26:

actionissue founderror statremedy

stop pyxpm 10 and 11
fru-deactivate and activate xpm 11
restart pyxpm 10 and 11
start DAQ

no issue has been detected0/10---

stop pyxpm 10 and 11
fru-deactivate and activate xpm 10 
restart pyxpm 10 and 11
start DAQ

at first xpmpva DAQ:NEH:XPM:11 does not come up
Then Opal shutsdown		3/20

stop pyxpm 10 and 11
fru deactivate activate 10 
fru deactivate activate 11 (in order)
devGui switch xpm mini/timing2
if needed restart opal from terminal

Observation Of Front-Panel XPM Link Glitch With Version 3.5.4

Perhaps fixed by Matt in later firmware version?

XPM11 glitches between 4pm and after 6pm and also around 10:10 am the next day

Testing Details

In 2023/10/24 :

actionresultremedyresult
Remove XPM10 fiber timing in the back
while DAQ running

*** XpmDetector: timing link ID is ffffffff = 4294967295^M
Timing 1 shutsdown

TxlinkReset of cmp015 in XPM11DAQ recovers
Repeat XPM10 fiber timing removal removal

DAQ cannot disable

---DAQ recovers by itself at restart
Repeat XPM10 fiber timing removal removal

---

---no issue
Repeat XPM10 fiber timing removal removal

DAQ cannot disable

---DAQ recovers by itself at restart
Remove XPM10 fiber timing in the back
while DAQ stopped

---

---DAQ starts with no issue
Repeat XPM10 fiber timing removal removal while DAQ stopped

---

---DAQ starts with no issue
Remove transceiver from XPM10 in the back (DAQ stopped)

---

---DAQ starts with no issue
Remove transceiver from XPM10 in the back (DAQ started)

---

---DAQ starts with no issue

timing 1 shutsdown by itself

TXlinkReset on XPM10 for XPM11DAQ recovers
Remove fiber on XPM10 to XPM11

---

---DAQ starts with no issue
Remove transceiver on XPM10 to XPM11

---

---DAQ starts with no issue
Remove fiber on XPM11 AMC0 port 0

---

---DAQ starts with no issue
Remove transceiver on XPM11 AMC 0 port0

---

---DAQ starts with no issue

opal disappears from the list f detectors

restart DAQDAQ starts with no issue
power cycle xpm10 via switch only AMC0

XPM 11 looses timing node
Opal not in the list of detectors

Restart pyxpm 10 and 11
Power cycle xpm 11 with handles
fru-deactivate xpm11 (3 times)
fru-deactivate xpm10

restart pyxpm 11


DAQ restarts but opal shutsdown

opal still shutdown

devGui xpmmini timing v2
TxLinkReset
Opal still not back BadDetector Paddr
Xpmpva died xpm11

no avail


Stop pyxpm 10 and 11
fru-deactivate 10 and 11
strat pyxpm 10 and 11

DAQ starts with no issue

Conclusion:
It appears that yanking the timing fiber can cause disturbances in the system, but they are not repeatable 100% of the time.
XPMs Power spikes can set the DAQ in a behavior similar to the XPM glitch, but only if pyxpms are running. To be repeated.


  • No labels