9th september 2001r. barillere - it-co1 industrial and custom front-end solutions for process...

9th September 2001R. BARILLERE - IT-CO 1

Industrial and Custom Industrial and Custom Front-End solutionsFront-End solutionsfor Process Controlsfor Process Controls


Schematic StructureSchematic Structure

rbarille:

This figure has to be updated

rbarille:

This figure has to be updated


FieldbusesFieldbuses

• OverviewOverview

• CERN recommendationCERN recommendation

• SupportSupport


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.


Fieldbuses withinthe industry


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?


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.


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?


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)


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)


Support

• CERN wide support• IT-CO first line support

– Advices / collaboration– Spare devices– Hands on


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).


Example withHMS AnyBus


PLCPLC

• OverviewOverview

• PurposePurpose

• SupportSupport


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

PLC Cycle PLC Cycle

Rea

d In

puts

Ope

rate

PLC

pro

gram

Wri

te O

utpu

tsR

ead

Inpu

tsO

pera

te P

LC p

rogr

am

Wri

te O

utpu

ts


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


Choosing a PLCChoosing 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


UNICOSUNICOS

• An application frameworkAn application framework– For process control oriented applicationFor process control oriented application– Schneider PLCs, PCVue32 -> PVSSSchneider PLCs, PCVue32 -> PVSS

• FunctionalitiesFunctionalities– Objects for I/O, Devices and process control;Objects for I/O, Devices and process control;– Control modelControl model– Alarms, Events and InterlocksAlarms, Events and Interlocks– Simulation of input/Overwritting of output.Simulation of input/Overwritting of output.


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


SLiCA custom solution

to Front End control• Overview• Purpose• Status


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


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


Controllers and Devices


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.


Covered Topics

9th september 2001r. barillere - it-co1 industrial and custom front-end solutions for process...

Documents

fieldbus manufacturers

fieldbus controllers0

end computers plc

custom developments

profibus dp

digital ios

remote ios

iosplc modules