Expose monitorables for the front-end power monitoring tools
Description
This MR aims to export additional monitorables in order to be able to measure the power consumption of a given OptoHybrid in known conditions.
The low-voltage and high-voltage values and status are retrieved from the DCS DIM interface and exported in the DAQ monitoring JSON files. They are also displayed in the web interface. The front-end status (OptoHybrid FPGA programming state & VFAT running mode) is read out from the DAQ and exported in the DAQ monitoring JSON file as well. This information is not made available through the web interface.
All required values from #248 (closed) are now monitored:
- GBT ->
GBT.LINK:OHxx.GBTy.READY
- Ready
- Not ready
- Note that it is different from the GBT locking on the signal transmitted from the back-end, status which cannot be retrieved.
- OptoHybrid FPGA ->
FE.STATUS:PROGRAMMED_FPGA
+FE.STATUS:PROGRAMMED_FPGA_VALID
- Programmed
- Not programmed
- Unknown
- VFAT run mode ->
FE.STATUS:OHxx.VFAT_RUN_MODE
+FE.STATUS:OHxx.VFAT_RUN_MODE_VALID
- In run mode
- Out of run mode
- Unknown
- Low-voltage ->
DCS.IMPORT:OHxx.LV_IMON
+DCS.IMPORT:OHxx.LV_VCON
- Monitored current
- Monitored voltage at the PS connector
Related Issue
Fix #248 (closed).
How Has This Been Tested?
- Front-end status are properly readout on the GE1/1 integration setup in b904
- Low-voltage and high-voltage monitorables are properly imported from the DCS in a local instance of the monitoring suite at p5
Screenshots
Types of changes
-
Bug fix (non-breaking change which fixes an issue) -
New feature (non-breaking change which adds functionality) -
Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
-
My code follows the code style of this project. -
My change requires a change to the documentation. -
I have updated the documentation accordingly. -
I have read the CONTRIBUTING document. -
I have added tests to cover my changes. -
All new and existing tests passed.
Edited by Laurent Petre