1 / 33

Software Interlock System for < PS>

Software Interlock System for < PS>. Jakub Wozniak BE-CO - DA 02/02/2012. Agenda. What is SIS (with examples)? General overview of the architecture Basic configuration & s cripting features GUI & Diagnostics PS presence and plans for this year Questions. Software Interlock System?.

corine
Download Presentation

Software Interlock System for < PS>

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. Software Interlock Systemfor <PS> Jakub Wozniak BE-CO-DA02/02/2012

  2. Agenda • What is SIS (with examples)? • General overview of the architecture • Basic configuration & scripting features • GUI & Diagnostics • PS presence and plans for this year • Questions

  3. Software Interlock System? • Helps protecting our machines • Takes part in overall Machine Protection • Surveys the state of key equipment / other systems • Acts on a beam (timings, BIS, etc) if abnormal situation is discovered • Protects against repetitive faulty conditions in the following cycles (limits radiation, etc) • Remembers complex logic that humans tend to forget

  4. What SIS is NOT! • Not a hard RT system • Not an immediate hardware protection • Not a nanosecond reaction time • Not there for human safety • Not aSafety Integrity Level 4 (SIL-4) • So as any software it might fail… • …although it was rarely the case!

  5. Key Features • (Relatively) easy to configure (in XML) • Reliable core with a versatile extension system • Flexibility to cover various needs • Comes with generic tools and based on a common JAPC-MON framework (FDF, Logging, Concentrators, InCA) • Experience from various installations (SPS, LHC, Linac2)

  6. SIS Examples Start-cycle 400 ms 200 ms SIS evaluation 100 ms BCT • SPS-SIS (2300 subscriptions, ~5000 checks) • Covers transfer lines, ring, North Area, CNGS • SPS Economy -> over300,000 CHF saved everyyear on energy • CESAR-SIS • Automatic eLogBook entries for beam availibility • LHC-SIS (2500 subs, 5500 checks) • All major systems checked (BI, BIC, Coll, Magnets, QPS, RF...) • LHC-BIGSISTER • Announcesvariousconditions & warnings • LINAC2-WATCHDOG-SIS • Stateoriented, destinationbasedsurvey, knob-controllable Switch to economy via timing event

  7. sis-core (cs-ccr-pssis2) sis-core (cs-ccr-pssis1) Front-end A Front-end A Front-end A Front-end A General Architecture Overview sis-gui sis-gui sis-gui sis-gui DB backup primary XML Controls middleware

  8. Tail-clipper Timing event Timing Logbook Java Alarms Logs Data buffer japc-monitoring japc Flow of Control Export Action sis-core Boolean expression over channels: Permit =(A or B) and (D or (not C)) Data Processing External Systems Processing Data Acquisition Acquisition Subscription channels Controls middleware Middleware Front-end A Front-end B Front-end C Front-end D Any Fesa Device + Any Japc DataSource

  9. Alarm Ignore (Mask) Permit Tree Evaluation Good or bad pulse for a given USER Permit channel G AND Logical channels All BCTs are ok E F OR AND Elementary channels A B B C C D DEST(LBS,LBE,PSB) BCT06 - BCT60 Simple: Status != OFF Compex: anycalculationwith Java orGroovy

  10. Configuration • In 3 XML files (or more if complex) • Parameters.xml – devices to monitor • Permits.xml – definition of the logic trees • Spring-Beans.xml– additional classes as beans • You don’t have to tediously write them… • Velocity generates them • simple text processing with macros • If more processing logic is required…

  11. Java Extension Points • ValueConverters - one-to-one conversions • ValueBuilders – many-to-one conversions • ValueConditions – custom tree node logic • Exporters – custom export logic • Modules – additional non-SIS logic • SISController – API for core control • …more – many classes can be exchanged • Spring Framework - glues it all together

  12. Linac2 Watchdog Config • Permits.xml • Parameters.xml • Spring-Beans.xml • A bit of Java • SIS checks if the beam has passed all the elements (BCTs) correctly and sends a good or a bad pulse. • Counter == 0 -> beam is cut.

  13. Permit Channel

  14. Logical (Software Interlock) Channel

  15. Individual (Software Interlock) Channel

  16. Parameters.xml

  17. Spring-Beans.xml

  18. BctCheckValueBuilder

  19. Velocity Generation

  20. Groovy Scripts • Groovy == Java • No need to learn a new syntax • But if you do - it’s even simpler! • Declaration of simple conditions in XML • No need for additional Java classes • No speed penalty – all compiled into Java at startup.

  21. Complex Value Condition

  22. Custom ValueCondition

  23. Let’s Groovy!

  24. SIS GUI

  25. Japc Monitoring GUI

  26. Dynamic Log4J Config

  27. Diagnostics

  28. Diagnostics

  29. Operational Error Cases • Data OK but the test failed. • E.g. a power converter that should be ON is OFF. • No value for a given cycle stamp (PPM evaluations) • Values arrive too late with respect to the evaluations • Value too old (non-PPM evaluations) • The data is not within the predefined time window. • No value at all. • No data for comparison arrived. • Exception from CMW or frontends • The subscription received an exception, instead of valid data.

  30. (Timid) Injector Presence • Linac 2 Watchdog smoothly running last year

  31. PS-SIS in 2012 • Dirac monitoring (Q1 – best before startup) • AQN / CCV comparison of BHZ01S8…QFO02S8 • Executed on destination = EAST_T8 • Counter for bad pulses (knob-controlled) • Actions on EASTB tail clipper • InCA – Isolde (slow) comparators (Q1/Q2) • BTY.CPMAXP-GPS (average intensity comparison) • BTY.CPDIPPOW-GPS (quadruple/dipole min/max) • Executed on destinations = ISOGPS or ISOHRS • Actions on BIX.TCL-SIS to stop the beam

  32. PS-SIS Ideas? • Radiation monitors? • RF Cavities – beam stop, auto reset? • Ideas for further automation?

  33. Questions?

More Related