Hub Module Hardware Monitoring Notes --------------------------------------- Initial Rev. 26-Feb-2019 Current Rev. 28-Feb-2019 This note covers only the Hardware Level items in the Hub Modules that the Detector Control System might want to monitor. The Physics Performance items that need to be monitored are not included in this document. For now this note starts out with a section that describes all of the hardware items that we could in principle monitor on the Hub Module and then list the items that we probably should monitor. In this note I assume that all hardware monitoring is done via the IPMC initiating I2C Bus Read cycles, i.e. only items visible on the I2C Bus are candidates for this DCS monitoring. Full List of Hardware Items We Could Monitor: ----------------------------------------------- Monitor Data from the Hub FPGA SysMon: -------------------------------------- FPGA Si Temperature (this is our fundamental indication of the Hub Module's temperature) FPGA Core power supply voltage (VINT) (Hub supply DCDC1 FPGA_CORE) FPGA Auxiliary supply voltage (VAUX) (Hub supply DCDC6 BULK_1V8) Note that the other voltage monitors available in the FPGA SysMon (e.g. VBRAM) are just copies of the above and do not need to be repeated in the Hub monitoring. Monitor Data from the DCDC Converter on the Hub: ------------------------------------------------ The Hub Module uses 7 GE (Lineage Power) DCDC Converters that can be Monitored from the Sensor I2C Bus. These 7 Hub power supplies are: DCDC1 FPGA_CORE DCDC2 MGT_AVCC DCDC3 MGT_AVTT DCDC5 SWCH_1V2 DCDC6 BULK_1V8 DCDC7 FAN_1V8 DCDC8 BULK_3V3 The details of the I2C read cycles to access the raw binary monitoring data from these converters and the arithmetic that is required to convert this data into engineering units can be found in: https://web.pa.msu.edu/hep/atlas/l1calo/hub/hardware/components/power/ ge_mega__d_lynx_40_amp_pmbus_MDT040A0X.pdf ge_micro_d_lynx_20_amp_pmbus_UDT020A0X.pdf ge_pico__d_lynx_12_amp_pmbus_PDT012A0X.pdf and in the documentation for the common controller chip that is used in all three of these DCDC converters ti_pmbus_buck_controller_tps40400.pdf There are many many registers that we could read and monitor in these 7 DCDC converters. Reading some of this information requires doing I2C write cycles to clear (or reset) certain status bits in some registers. Because the operation of these converters (e.g. their output voltage) is controlled by information that is stored in these I2C Bus visible registers I don't think that we ever want the IPMC monitoring system doing any write cycles. In general I don't think that we want the IPMC poking around on the I2C Bus any more than is necessary to carry out a minimum rational DCS monitoring system. In the "what should we monitor" section below I have listed the registers in these DCDC converters that I believe we should ask the IPMC monitor system to read. Monitor Data from the Power Entry Module on the Hub: ----------------------------------------------------- Data from the Hub's Power Entry Module is read on the IPMC's Management I2C Bus (not on its Sensor I2C Bus). The power entry module used on the Hub is a SynQor model IQ65033QMA10. The data-sheet for this component is available in the same web directory that is noted above. See pages 12 and 13 of that data-sheet. I2C Bus Visible Registers in the Power Entry Module: - Status Bits (0x1e) - Hold Up Capacitor Voltage (0x1f) - Negative 48V Output Current (0x21) - Negative 48V A Bus Voltage (0x22) - Negative 48V B Bus Voltage (0x23) - Average Unit Temperature (0x28) The bits in the Status Register are: - State of the A and B Enable Signals - State of the Alarm Signal - States of the Holdup and Hat-swap switch - State of the Negative 48V Under-Volt Alarm Monitor Data from I2C Visible Registers that We Could Implement in the Hub FPGA: ---------------------------------------- We do have status information is the Hub's FPGA that might be of interest to the DCS system. This is hardware level information that indicates whether or not the Hub Module is operating normally. The following items, that exist as signals within the Hub's FPGA, could be made visible in an I2C read only register. - Locked Status of the 2 PLLs on the Hub Module - Status of the Power Control signals between the Hub and ROD, e.g. is the ROD telling the Hub that it is all powered up and ready to run. - Status of the All Power Good signal on the Hub Module. Power Supplies that We Can NOT Monitor via I2C: ------------------------------------------------- The following 4 power supplies on the Hub Module can not be monitored from the I2C Bus and thus as far as I know can not be monitored by the DCS system: DCDC4 MGT_AVAUX a 1.800 V linear supply SysMon_Ref a 1.250 V linear supply DCDC9 Bulk_2V5 a 2.505 V linear supply In addition note that the ISO_12V supply (12.000 V) can only be indirectly monitored from the I2C Bus by reading the input voltage to the DCDC Converters that are feed by it. Monitor Data that We Should Readout: -------------------------------------- My preference is to keep our DCS Monitor Data as simple and straight forward as possible consistent with allowing us to understand the state of the Hub Modules. I would not ask the DCS system to take any action in the Hub Module to clear alarm flags from registers and things like that (actions that require I2C Bus write cycles). Note that because we are not clearing all alarm flags after power up, we will have some alarm flags set in various status registers on our GE (Lineage Power) DCDC Converters. These alarm flags are set during startup, e.g. during ramp up the output voltage is under its low alarm threshold. The cost (aka danger) of allowing the IPMC to clear these flags sounds too high to me. Monitor Data from the Hub FPGA SysMon: -------------------------------------- From the Hub FPGA SysMon I would readout only the FPGA's Si Temperature. For now I would set a 65 deg C alarm on this temperature. Monitor Data from the DCDC Converter on the Hub: ------------------------------------------------ The registers to readout from the 7 GE (Lineage Power) DCDC Converters are: - Temperature (0x7d) bit #7 over temperature fault bit #6 over temperature warning The DCDC Converters report their temperature only by indicating whether or not it is above pre-programmed warning and fault levels. - Read V_In (0x88) Read only on 2 of the 7 converters - Read V_Out (0x8b) - Read I_Out (0x8c) Initial alarm limits that we could use on this monitoring information are the following. Voltage Alarms are shown as a lower limit and an upper limit. The Current Alarms are an upper limit. DCDC1 FPGA_CORE V_In nominal is 12.000 V Alarms at 90% and 110% V_Out nominal is 0.950 V Alarms at 97% and 103% I_Out Alarm at 30 Amps Temp. Alarm if either fault or warning bit is set DCDC2 MGT_AVCC V_Out nominal is 1.000 V Alarms at 97% and 103% I_Out Alarm at 15 Amps Temp. Alarm if either fault or warning bit is set DCDC3 MGT_AVTT V_Out nominal is 1.200 V Alarms at 97% and 103% I_Out Alarm at 15 Amps Temp. Alarm if either fault or warning bit is set DCDC5 SWCH_1V2 V_Out nominal is 1.200 V Alarms at 95% and 105% I_Out Alarm at 5 Amps Temp. Alarm if either fault or warning bit is set DCDC6 BULK_1V8 V_Out nominal is 1.800 V Alarms at 95% and 105% I_Out Alarm at 5 Amps Temp. Alarm if either fault or warning bit is set DCDC7 FAN_1V8 V_In nominal is 12.000 V Alarms at 90% and 110% V_Out nominal is 1.800 V Alarms at 95% and 105% I_Out Alarm at 15 Amps Temp. Alarm if either fault or warning bit is set DCDC8 BULK_3V3 V_Out nominal is 3.300 V Alarms at 95% and 105% I_Out Alarm at 5 Amps Temp. Alarm if either fault or warning bit is set Monitor Data from the Power Entry Module on the Hub: ----------------------------------------------------- For now I would not readout any DCS monitor data from the Hub's Power Entry Module. Monitor Data from I2C Visible Registers that We Could Implement in the Hub FPGA: ---------------------------------------- For now I would not implement or readout any DCS monitor data from I2C Bus registers in the Hub's FPGA.