250 likes | 378 Views
Industrial and Custom Front-End solutions for Process Controls. Schematic Structure. rbarille: This figure has to be updated. Fieldbuses. Overview CERN recommendation Support. Overview. What is a fieldbus? A low level data transmission mechanism. It is not a LAN. Purpose
E N D
Industrial and Custom Front-End solutionsfor Process Controls R. BARILLERE - IT-CO
Schematic Structure rbarille: This figure has to be updated R. BARILLERE - IT-CO
Fieldbuses • Overview • CERN recommendation • Support R. BARILLERE - IT-CO
Overview What is a fieldbus? A low level data transmission mechanism. It is not a LAN. Purpose Access to distributed I/Os or devices. Reducing the number of cables. R. BARILLERE - IT-CO
Fieldbuses withinthe industry R. BARILLERE - IT-CO
Choosing a fieldbus A large number of available fieldbuses More than 120 Some are based on open standards Specific purposes and characteristics Tools: devices, chip sets, analysis tools CERN recommendation Three fieldbuses: CAN, Profibus, WorldFip In house support What about Ethernet? R. BARILLERE - IT-CO
The CERN recommendation CAN: Custom developments Profibus: Stronger industrial support WorldFip: Real-time features Ethernet: Not yet recommended but: Front end computers (PLC,PC,…) integration. Remote I/Os when Ethernet infrastructure available. R. BARILLERE - IT-CO
Domains of applications Industry like control systems Gas, liquid cooling, cooling and ventilation, racks, etc... Experiment magnets Sub-detector controls Temperatures (e.g. through ELMBs) Others? R. BARILLERE - IT-CO
Connecting Equipment Fieldbus-ready devices Mass Flow Controllers, PID, Pressure transmitters,... Via fieldbus controllers 0-10 V, 0-24 V, 4-20 mA, TTL, RSxxx... Via additional cards To be integrated in the equipment Chip sets When the needs are very specific (e.g. ELMB) R. BARILLERE - IT-CO
Integrating Fieldbuses within Experiment Controls Possible levels In the front end computers or in the SCADA computers Hardware PLC: manufacturer modules, dedicated to its fieldbus PC: Fieldbus manufacturers or third parties cards VME: Cards or modules Software Drivers or libraries Higher level applications (e.g. DDE or OPC servers) R. BARILLERE - IT-CO
Support CERN wide support IT-CO first line support Advices / collaboration Spare devices Hands on R. BARILLERE - IT-CO
Example withWAGO modules - analog and digital I/Os and serial lines (RS232, RS485). - supports PROFIBUS (DP, FMS), CanOpen, Interbus S. - standard electrical interfaces (4-20 mA, 0-10V). R. BARILLERE - IT-CO
Example withHMS AnyBus R. BARILLERE - IT-CO
PLC Overview Purpose Support R. BARILLERE - IT-CO
What is a PLC • A compact front end computer • Proprietary OS • Standardized programming languages • Cyclic execution • Connected to fieldbus • Industrial I/O modules • Well integrated into SCADA R. BARILLERE - IT-CO
Purpose • For local control • Close loop, interlock, safety. • Independent of SCADA • Reliability,performances. • Domain of application • Gas control • Cooling and ventilation • Temperature control (thermal screens) • DSS R. BARILLERE - IT-CO
Choosing a PLC CERN recommended PLCs Siemens and Schneider (UNICOS) “Full” PLCs Wide range of CPUs Large connectivity CERN wide support uPLC Wago and Beckhoff Not as powerful but cheaper IT-CO first line support Advices / collaboration Spare devices Hands On R. BARILLERE - IT-CO
UNICOS • An application framework • For process control oriented application • Schneider PLCs, PCVue32 -> PVSS • Functionalities • Objects for I/O, Devices and process control; • Control model • Alarms, Events and Interlocks • Simulation of input/Overwritting of output. R. BARILLERE - IT-CO
Integration of PLCs • Communication • COTS OPC servers • Field bus • TCP-IP based • SCADA drivers • E.g. UNICOS in PVSS • Configuration • Proprietary dev. environments • Automatically extracted configuration files R. BARILLERE - IT-CO
SLiCA custom solutionto Front End control • Overview • Purpose • Status R. BARILLERE - IT-CO
SLiC overview • C++ front end control application framework for • Devices access • Process control • Set of ready to use classes. • Guideline to add user specific ones. • VME/Linux; PC/Linux; PC/NT R. BARILLERE - IT-CO
Why SLiC? • When no COTS solution is usable • Unsupported devices or electrical interfaces: • Custom devices • HEP specific devices (CAEN PS) • TTL signals • Large number of I/Os. • Advantage of a framework: • Common kernel; • Re-usable user extentions R. BARILLERE - IT-CO
Controllers and Devices R. BARILLERE - IT-CO
SLiC status • Released • Devices: CAEN PS, Can, Wiener • Integrated with PVSS: DIM/XML • Used by COMPASS and HARP • Next releases • New devices • New communication mechanisms • Complete user documentation. R. BARILLERE - IT-CO
Covered Topics R. BARILLERE - IT-CO