Page History
...
then fru-restart from psdev xpm 10 and xpm 11 in sequence, not together.
first light presents a problem with XPMPVA and GROUPCA
xpmpva XPM11 does not work
fru-restart bring it back alive
But OPAL does not respond to roll call
TXLINKRESET XPM11 in XPM10 brings OPAL back to live
| action | issue found | stat | remedy |
|---|---|---|---|
| remove fiber in RTM and restart DAQ | TXLINKRESET timing1 (on rollcall) TXLINKRESET timing1,2,3 (on alloc) | 2/10 | TxLinkReset solved rollcall TxLinkReset and RxLinkReset on xpm10,11 timing1,2,3,4 and opal |
| just restart the DAQ | Opal RxId issue RxLinkReset on timing4 (on rollcall) rxid issue on connect opal | 3/10 | TxLinkReset |
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.
Upgrading XPM firmware seems to have mitigated all the issues (to 3.6.0 from 3.5.4). The bucket issue becomes more prominent, probably because other issues are not happening. This issue appears when power cycling the xpm11.
...
Overview
Content Tools