ystem Databases BLED Outline Topdown amp bottomup approach to configuring the control system BLED databases Lattice database and tools Parameters editor BLED and EPICS Current status and plans ID: 459897
Download Presentation The PPT/PDF document "ESS Control S" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
ESS
Control S
ystem Databases(BLED)Slide2
OutlineTop-down & bottom-up approach to configuring the control system
BLED databasesLattice database and toolsParameters editor BLED and EPICSCurrent status and plans2Slide3
The top-down/bottom-up approach
Top-down approach:Describe the system under control.Infer control system design.Implement control system (possibly automatically).Bottom-up:Interface devices.Integrate them.Problems:Top-down: hard to “nail it” in the first attempt, iterations are expensive.
Bottom-up: difficult to maintain coherence. Higher integration and maintenance cost.3Slide4
BLED
The abbreviation stands for all data relevant for the control system.Beam Line Element Databases.Should cover all database needs of the control system development, operations and maintenanceHowever, not at the cost at replicating data or rewriting tools!Facilitate top-down
and bottom-up approach to developmentThe databases:High-level parameters managementAccelerator latticeSystems engineeringEquipmentCablingControl system software4Slide5
BLED databases
5Slide6
BLED architecture
Different interoperable modules are expected.Various tools to interact with the database.Three-tier architecture is proposed to be used.6Slide7
High-level parameters
Designed/required performance parameters.Tied to subsystems.Workflow:Define a list of parameters.Propose a value.Approve the value.History tracking / audit.Used to manage the technical design process.
7Slide8
Lattice database and tools
TraceWin import/exportFile upload/download via web interfaceAdditional markers/annotations in TraceWin fileto define structuredescribe elements not needed by
TraceWin, but required (e.g., beam diagnostics)8Slide9
Lattice database:TraceWin file example
9
;NEW_STR Name COLD/WARM #_1st_Warm_elements #_1st_Cold_elements #_2nd_Warm_elements #_2nd_cold_elements Elements_per_slot(0=PeriodLength# /1=At each ;WRITE_SLOT_HERE /X=at each X elements ;NEW_STR ISRC WARM 0 0 0 0 1 ISRC-DRFT-1: DRIFT 280 100 ;: ;WRITE_SLOT_HERE ;: ;;: ;LEBT is IFMIF-LIKE ;NEW_STR LEBT WARM 0 0 0 0 1 LEBT-Z1: SPACE_CHARGE_COMP 0.9 ;: ;: ;Ion source exit
LEBT-DRFT-1: DRIFT 605 100 ;: ;: ;Set to physical length ;: ;: ;match_fam_grad 13 ;Marker LEBT-PBI_BCM-1
LEBT-PBO_Sol-1: SOLENOID 300 0.163558 30
LEBT-DRFT-2: DRIFT 665 100
;: ;: ;Set to physical length
;: ;: ;match_fam_grad 13
;Marker LEBT-PBO_Coll-1
;Marker LEBT-PBI_Slit-1
;Marker LEBT-PBI_FC-1Slide10
System breakdown
Systems engineering databaseLogical components (elements)and their hierarchyMachine broken down to the level of individual devicesSource of information:Lattice: all accelerator beamline
elementsPositions of other elements along the beamline (diagnostics equipment, etc.)CAD designs (e.g., for target)Object model is set-up…… but no tool developed/prototyped yetSimilar in scope to the DISCS’ Configuration module?10Slide11
Equipment
11
InstalledequipmentManufacturer, model, ...Serial numberLink to inventory management systemMultiple instances of same type of equipmentInterfaces between equipment“Ports”: e.g., cable connectorsLocation where equipment is installedSlide12
Cabling
Cables connects equipment’sportsOne cable connects two (ormore) portsTools existE.g., IRMIS’ cabling moduleCan they be integrated?Configuring cabling can betiresome
Can it be simplified/automated?12Slide13
EPICS configuration
Concept of a “module”:Corresponds to an EPICSapplication (database file templates,SNL programs, aSub routines, device support code, …)Module instantiation done by adding to EPICS’ st.cmd startup scriptModule definition provides
templatized “code snippets”We call template parameters “fields”Module development and “instantiation” must be cleanly decoupledDon’t replicate all records/fields in the database!Development cycles must be quick!13Slide14
Module development and integration
The developer:Develops “modules”E.g., device support, EPICS database templates, sequencer programs, …Defines parameters for configurationThe integrator
:Instantiates modules (“instances”)Provides parameter values for each instance14Slide15
The ideal worldAll requirements for each module are known.
Developers build the modules.The integrators bind them together.Integrators nail parameter values in the first attempt.15Slide16
The real world
Iterations are needed:Development:Module must provide an additional feature.Module has a bug.Integration:Parameter values not “nailed” in the first attempt.Short development cycle times are crucial!Even if database-centric, top-down approach is used.Times should be similar to using EPICS directly.
Otherwise:Missed deadlines and/or decreased scope.Skilled integrators and developers may take shortcuts.Top-down and bottom-up approaches out of sync.16Slide17
Prototype
Can quick development cycles be achieved via database?Validation of the “modularization” model.Video of example working session:Link (local file)Link (web, HTML5)Link (web, MP4)
17Slide18
An example:Beam Position Monitor
Timing receiver module.Generates triggers for data acquisition.Capable to provide accurate timestamps.Data acquisition module:Samples an analog input channel.Provides a waveform.Triggered
& time-stamped by timing receiver.Beam position monitor module:Logic for processing waveforms to produce beam positions.18Slide19
Timing receiver
19Slide20
Data acquisition
20Slide21
BPM processing
21Slide22
22Slide23
Example setup
23Slide24
EPICS module versioning
EPICS modules versioned according to standard software rules“Semantic versioning”: major.minor.bugfixSource version control tools (e.g., Mercurial)Packageable into RPM modules (via ITER CODAC mechanisms)Management of deployment with tools such as Spacewalk.It must
be possible to use multiple versions at the same timeE.g., to test an update on a single IOC before deploying site-wide24Slide25
BLED data versioning
Data versioning is mandatory.Strategy is not to remove any data.Each piece of data (row in a table) has validity time range assigned to it:E.g., update: set “valid to” of existing data to “now”, and add new datum with “valid from” to “now” and “valid to” to NULL.Additional support is needed:Snapshot of a working configuration (“tag”)Tuning of a tagged configuration (“branch”)
25Slide26
Plan
By end of June, determine which way to proceed. Options:Adapt ITER SDD.Proceed with custom development.Adapt and extend DISCS.Prototype custom solution and adapted SDD will be tested side-by-side by a team of EPICS integrators and developers.They will work most with the tools – their call.
26Slide27
Current status
Activities started in 2011.Lattice tools, parameters database, ...Low flame.Intensified in 12Q4.EPICS configuration generation (incl. Excel integration) – prototype.27Slide28
Roadmap
28Slide29
Thank you for your attention
29