1 / 16

Technical proposals for the Generation and Distribution of Safe LHC Parameters

Technical proposals for the Generation and Distribution of Safe LHC Parameters. SLP message. Energy. SBF1. SBF2. BPF1. BPF2. all Safe LHC Parameters merged in one message. 3 parameters in 1 message:. Unique link => Reduce transmission cost.

azia
Download Presentation

Technical proposals for the Generation and Distribution of Safe LHC Parameters

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Technical proposals for theGeneration and Distribution ofSafe LHC Parameters AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  2. SLP message Energy SBF1 SBF2 BPF1 BPF2 all Safe LHC Parameters merged in one message 3 parameters in 1 message: • Unique link => Reduce transmission cost • Put Reliability effort on only 1 system instead of 3 16 + 1 + 1 + 1 + 1 = 20 bits AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  3. typical “Timing” message: 1st byte P 2nd byte P 3rd byte P 4th byte P Starting Seq. Ending Seq. Use Timing electronics to generate & receive messages • Reliable and improved transmission system • Fast speed is not required: 512Kbits and 1ms rate could be enough • Easy to re-use Generator and Receptor electronics (VHDL recovering) • Multi-bytes format: possible extension for additional parameters AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  4. a SLP Generatorina VME system installed in IR4* IR4* means SR4 or UA43 or UA47 or ? • VME is one the possible choice for an embedded card: • Easy to interface to Control infrastructure • Re-use VHDL code for VME-bus interface • SLP Generator will be installed in IR4* • Beam Currents already produced in this area • But Energyparameter should be transmitted from 6 to 4 • Features: • Receive Energy and Beam Currents data • Compute the SBFs and BPFs • Merge all Parameters and built the message • Broadcast SLP message • VME-bus interface for setting thresholds and monitoring purpose. AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  5. VME-Bus Thresholds settings and monitoring Simplified block diagram for the SLP* Generator * SLP stands for Safe LHC Parameters From SPS Rec. Energy Rec. Energy Computing unit SBFs Transmitter SLPmessages Rec. Ibeam1 BPFs Ibeam2 Rec. Other (?) Thresholds registers AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  6. VME-Bus SLP messages SLP messages Receiver Tr. Tr. SLP Error Reg. SBFs BPFs BPF1 Energy BPF2 SBF1 SBF2 Energy monitoring via Supervision SLP “User board”in a VME standard • Features: • Receives, decodes the SLP messages. • Gives local information via 3 different outputs. • Retransmits the SLP messages to the next User board. • VME-bus interface for monitoring purpose. (Need a free slot to be installed into an existing VME crate) AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  7. Link via Fiber Optic loop • Fail safe transmission support • A loop ensures that SLP clients receive the same information • Give possibility for adding new SLP clients: • Make a second transmitter output • Mix Ring (major clients) and Star distribution (see layout on next slide) • Check the transmitted messages at the end of the loop • If ERROR then activate a Beam Dump Request to BIC AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  8. RCV RCV RCV T T T to BLM input T T T Fiber optic or copper cable BLM crate in SR8 S S S B B B E E E Two Outputs for Ring and Star Distribution to IR1 from IR7 Fiber optic IR8 BIC crate in UA87 BIC crate in UA83 AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  9. If not equal  Beam Dump Request SLP messages Receiver Energy’ SBF’ BPF’ to BIC Comparator VME-Bus SLP Generator with verification of data From SPS Rec. Energy Rec. Energy Computing unit SBFs Tr. Rec. SLP messages Ibeam1 BPFs Ibeam2 Rec. Thresholds registers AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  10. BIC BIC BIC BIC UA47 1SLP generator UJ56 USC55 BIC + BIC UA43 28 SLP User boards BIC BIC BLM BLM Ext1 InK2 InK1 BLM Ext2 BLM BLM BLM BLM BLM BET BET BCT UJ33 UJ76 BIC BIC BIC BIC BIC BIC BIC BIC BIC BIC BIC BIC BIC BIC BIC BIC BIC UA83 UA27 LSS4 BIC BIC UA23 US15 BIC BIC BIC BIC LSS6 SR5 Proposed layoutfor theSLPdistribution SR6 SLP GEN SR4* BIC UA63 UA67 SR7 SR3 UA87 SR8 SR2 SR1 AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  11. Summary • New highly reliable system must be supplied • All parameters in one message • Use a.f.a.p. existing electronics and improved solutions • Message speed 512kb/s with 1 KHz rate • 2 types of modules: • Unique generator to built and broadcast the messages • R/T User Board to get local outputs • Use Optical Fibers to transmit all around LHC areas • Chain all (main) User boards in one loop • Check at the end of the loop and Generate Beam Dump request if Error • Process 100% made by Hw ( but Sw Monitoring via Supervision ) AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  12. Pending Questions • 2 bytes to define the Energy parameter: is it enough? • Safe LHC Parameters required for other systems? • Which (few!!) extra parameters should be added? • Need additional studies to achieve the required reliability: • Bring in a redundant “computing unit” to built parameters? • Transmit parameters across two loops? • Perform Cross check for received parameters with another source? • Append UTC time in the message? and so on… • Technical Questions: • How to catch BEM data installed in IR6? • How to acquire Intensity values from BCTs? • How to get SLP into Timing system? • How to give local parameters values? • Energy in serial? or in //? Digital or Analog value? • Flags with TTL level? • Which type of connectors? AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  13. Project Status After approval from MPWG and from LTC, we could start the study and the design… AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  14. Project Management (1/2) • What to do: • Gather 2 types of data: Energy + Beam Currents • Produce and transmit 3 Safe LHC Parameters in a single message • High level of Reliability is required • Who: • AB/CO is mandated to carry out the project ( through a close collaboration with AB/BDI and AB/BT) • HT section is proposed to manage the hardware part • IN section (as Applicant/Client) is proposed to coordinate and to assist • “SLP Team” = Ben + Bruno + Javier + Philippe • “SLP Team” report regularly to Marc and to Rüdiger • Report (when necessary) to MPWG and to AB/CO-TC • AP + FC sections for Sw application • Which: • 1 Generator module: Hw design by Philippe (+Ben +Javier +Bruno) • Several (~30) T/R User boards: design by Ben (+Philippe +Javier +Bruno) • Monitoring Software by FC and AP sections • Specification by Bruno (+Javier +Ben +Philippe) AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  15. Project Management (2/2) • When: • Phase 1: now → Dec.04 • Meetings with suppliers (BCT system and BEM system) • Meetings with clients (Kickers, BLM, Timing,…) • Hw designs set-up • Sw requirements set-up • Phase 2: Jan. → May05 • Produce Hw units: Generator module +User board • Complete Engineering Specification • Finalize requirements for Sw Monitoring • Phase 3: June→ Dec.05 • Lab Tests, Endurance Tests, Users tests • Reliability Studies • Upgrade Hw and Sw • Phase 4 : 2006 (?) • Fabrication in series for T/R cards • Installation in LHC + Hw Commissioning (after the BIC) • How much: • 250 KCHF: 100 KCHF for 2005 and 150 KCHF for 2006 • Dedicated Budget Code (Bruno & Javier in approval) • EVM (managed by Bruno and/or Javier) AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

  16. End AB/CO Technical Committee Meeting of 16 Oct.2004: SLP Project

More Related