Page History
...
Can check light levels going into the xpm by looking at EPICS variables like this:
| Code Block |
|---|
(ps-4.1.2) tmo-daq:scripts> pvget DAQ:NEH:XPM:0:SFPSTATUS
DAQ:NEH:XPM:0:SFPSTATUS 2021-01-13 14:36:15.450
LossOfSignal ModuleAbsent TxPower RxPower
0 0 6.5535 6.5535
1 0 0.5701 0.0001
0 0 0.5883 0.7572
0 0 0.5746 0.5679
0 0 0.8134 0.738
0 0 0.6844 0.88
0 0 0.5942 0.4925
0 0 0.5218 0.7779
1 0 0.608 0.0001
0 0 0.5419 0.3033
1 0 0.6652 0.0001
0 0 0.5177 0.8751
1 1 0 0
0 0 0.7723 0.201 |
XPM Timing Links Not Locking
If XPM links don't lock, here are some past causes:
- check that transceivers (especially QSFP, which can be difficult) are fully plugged in.
- for opal detectors:
- use devGui to toggle between LCLS1/LCLS2 timing
- hit TxPhyReset in the devGui (this should now be done in the opal drp executable)
- for timing system detectors: run "kcuSim -s -d /dev/datadev_0", this should also be done when one runs a drp process on the drp node (to initialize the timing registers)
- hit Tx/Rx reset on xpmpva gui (AMC tabs).
Opal
NOTE: when powering on the opal/feb-box (front-end-board) the LED on the FEB box will stay red until the DAQ has configured it, when it will turn green. Also, only after the DAQ configuration is done will the "@ID?" and "@BS?" uart strings sent to the camera here work. This is probably also fixable by loading a rogue yaml config file included in the cameralink-gateway git repo:
...
Overview
Content Tools