Focus on: 
Login

QPS reliability studies with CSL - progress meetings 2024

→ Europe/Zurich
  • Friday 22 March
    • 15:30 → 15:50
      QPS progress meeting - 1 20m
      Speaker: David Westermann (Universitaet Stuttgart (DE))
      • david's questions
        • there are two sets of tabs
        • each pdsu gets a separate voltage table
        • all three get the quench
        • worst
          • pa3 & pa1
          • always two layers
        • dqhsu
          • dipole magnets
        • uqds
          • few cards in nqps in lhc will run uqds
      • laure and adam
        • filtering of noise mainly
          • how does it go ok with threshold
          • experience from magnet test benches
            • power converters rather noisy
          • multiple magnets have more inductance/load and get less noise;
          • will only see from string the signal to noise ratio
            • 600 Hz spikes, apply non-linear filter
          • cannot realistically say noise
        • laure: for noise filtering block - do you have an idea of filter structure
          • yes, standard filter structure
          • shows example from uqds firmware documentation
          • spikes up to 1ms can be absorbed
      • csl wants to split argument in sub-parts
        • old argument - giving overview of whole MPS
        • QPS - different components and magnets
        • QPS again, but for inner triplet
        • fmea & fta comparison
      • fmea vs csl
        • hardware - do fmea & fta
        • maybe try fmecdma in socrates
        • level & side thoughts are interesting to capture
  • Thursday 25 April
    • 16:00 → 17:00
      QPS progress meeting - 2 1h

      Clarification of questions

      Speakers: David Westermann (Universitaet Stuttgart (DE)), Laure Millet
      • laure: developed argument - re-started from top-down - focus on inner triplet; defeaters added
      • review and check which are to focus on
      • david's questions
          1. How does the UQDS react upon loss of power (assuming all the UPS etc. fail)? Will it open the quench loop? Will it fire the CLIQs/QHDSs?
            1. will open quench loop --> fast power abort
            2. units powered in redundant way, in case of full power loss of both supplies, cannot fire heaters
            3. internal power on uqds level and pdsu level is there as well - meant for diagnositc purposes but could interlock
            4. generally same for pdsu
            5. possiblity of simultaneous power outage and quench
              1. controls electronics of heaters cannot trigger without power
              2. supply lines for cliqs (UR) and heaters (UJ) same as pdsu () & uqds ()
          2. Regarding the PDSUs for D1 and D2,
            1. is it clear yet how they will look like?
              1. pretty much like inner triplet
              2. take out cliq monitoring
              3. keep separate for D1 & D2
              4. trigger fan out via PDSU or UQDS
                1. if link quenches and we have to fire all Ds
                2. then need pdsu for trigger
            2. will D1/D2 each have one PDSU?
            3. will these perform the same functions (that are relevant to D1 & D2) as in the IT (removing the CLIQ which does not exist in D1 & D2 and removing the link to the BIS) or will they also perform other functions?
              1. will need PDSU
          3. Are the conditions for the PDSU in the inner triplet to open the quench loop identical to the ones for requesting a beam dump to the BIS? In other words, will it request a beam dump both in case of spurious HDS/CLIQ firing as well as upon any QDS detecting a quench?
          4. clarify with Daniel if D1 and D2 important for this
        2. uqds upon spurious firing would saturate, but only if the condition remains for n miliseconds; at top energy 3 milisecond, but can be ten miliseconds
        3. pdsu can always dump beam via bis - but better to have active low
        4. think through big disturbance
          1. trigger heaters within few ms
          2. ups should survive for that time
          3. fuses? are rather slow
          4. supercaps - wanted to cover 100ms gap in AC
          5. question whether you could trigger the hds from its own power circuit
  • Tuesday 11 June
  • Thursday 20 June
    • 10:30 → 11:30
      Discussion about the UQDS/PDSU schematics 1h
      • last UQDS version --> trigger separately
      • input stage
        • more resistors for voltage withstand
        • short in voltage tab --> inductive heating ..> burns short away
        • ground floating
          • inductive via PS
          • digital via coupler
        • voltage protection
          • FETs stop - current limiter
          • blind failure potential
        • from top comes gain control
        • test signal as soon as differental converter
        • differential for ADC
          • reduces signal to noise
        • high voltages
          • from magnet - shortly
          • ESD - test by not caring in lab about it
            • there were families of insulators who had problems
        • exchange
          • monitor via busy signal
          • state machine to check if busy is not ready
          • if too long not heard back --> safe signal
          • also check if noise is still present --> otherwise trip
        • flash memeory
          • calibration of channel
            • offset (not important)
            • gain error
          • but communicated to high level software
        • voltage reference - failure--> wrong data
        • in principle
          • separate power etc
          • poweer pins shared
          • steckverbinder geshared
      • midplane
        • lots of plugs
        • diagnostic not present
        • most connectors for input channels (16 x 5)
      • trigger
        • all options, maybe not all mounted
        • 4 current loops
          • optionally source
        • up to 8 hds/pdsu triggers
          • depletion mode FET
            • safe against short pulling down 15V line
          • because triggering needs to be active
        • contact problems?
          • contact line across first and last pin
          • because IT won't trigger often enough to see
        • sync
          • tell post mortem to synchronize
          • 10 uQDS
            • one detects, tells others
          • off topic - force A/B
            • boards swap sending
            • tell controller to stop toggling
            • for continous logging
        • fpga not directly driving, hence buffers (in middle)
        • vdp
          • fpga
            • no clock
              • communcation still there, but only static function
              • no protection
              • clk err has monitoring --> triggers FPA via FPGA
              • currenlty not foressen, but may be added
          • debug interface
            • either spi or uart
            • uART directly to fpga
            • spi via uC
              • spi also to uart
          • uC
            • connection to fpga only via handful of pins
            • all settings go to fpga
            • can write thresholds at any time
            • reads all registers periodically and writes out
              • track record is there
              • SPI for Laure?
              • SIS could do periodical check?
            • configuration management may need update
              • LSA has config
            • fpga has column parity over register map
              • if uC starts doing wild things
              • should notice parity
              • fpga has no clue what machine does
            • if uC fails safe, FPGA keeps going
          • memory
            • local configuration stored on flash
          • local PSU
            • shorts of cap - power supply goes down
            • should lead to FPA open
            • 1.7V instead of 3.3. --> fpga does whatever
            • all components can cause
            • ceramic capacitors
              • one known case at cern
      • ps
        • one big ac dc (5V)
          • several dc dc
          • 3.3 v
        • adc for voltage monitoring
          • for all rails jeweils fuer a und b
        • availability vs protection trade off
          • impossible to keep fpa loop closed when current gone
        • only protection
          • if monitoring gone, could enter intermediate stage, fpga ould do weird things
      • uQds as PDSU trigger when spurious triggering
        • rather on the slow side; could be adjusted to be fast enough but then we may do too many spruious triggers
  • Friday 12 July
  • Wednesday 17 July
    • 10:30 → 12:00
      Discussion about the UQDS/PDSU schematics 2 1h 30m
      • jens away 19/07 - 20/08, david away 20/08 - 30/08 (hand over all infos), me away 30/08 - 09/09 & 13/09 - 20/09 - 7. oct HL annual meeting "Reliability studies on PDSU and PDSU-BIS concentrator interface"
      • prepare PDSU estimates and questions & models until 20/08 - until 30/8 prasenation Draft
      • DSP decoupling capacitors
        • short --> would need to check what fpga does
        • fpa w/o core voltage - only via external baustein
        • if core voltage gone - no proper data out at start of fill
      • check will by per fill
        • fpga lives and is configured
        • not sure whether cable to quench heater is properly sone
        • such check should cover majority of blind failures on digital platform
        • can also ask tomasz
          • is supply voltage monitored?
          • could detect lots of faults
      • blind failures
        • active triggers
        • current loops not really
        • channels not really
          • almost all safe
      • send fmeca templates
      • v3 - fpga card ready -
        • pdpack v2 - is the same for pdsu - tomasz
        • channel in autumn (but no big changes) - very similar to pdsu cliq - very different for hds - jens
          • re-used for big CONS in LHC
          • but send current
        • trigger (very different pdsu) - jens
          • version exists
        • midplane
      • blind failures during yearly tests - no consistent record
Powered by Indico v3.3.6-pre