Ethernet IP solution for ATLAS IBL and CMS Pixel

detectors CO2 cooling plants

26.06.2013

Lukasz Zwalinski PH/DT/DI

Presentation overview

• A bit of history

• Why Ethernet IP?

• Control system architecture example

• Real implementation example

• Implementation issues

• Summary

Overview

Lukasz Zwalinski GUAPI 26th June 2013

Lukasz Zwalinski GUAPI 26th June 2013

EN/ICE

EN/CV/DC

PH/DT/DI

PH/DT/POCO2

Setting CO2 cooling plants standards:• Control philosophy• Safety and interlocking philosophy• Software framework • Control and electrical hardware• PVSS data server location

PH-DT restructuration:• Cooling merged with Gas to common section

Experiment Project name PLC brand Project statusFunctional analyses

Groups involved

ATLAS

SR12kW

Schneider completed completedPH/DT/POEN/CV/DC

IBL2x3.3kW

Schneiderunder development

Sep.2013completed

PH/DT/PO & DIEN/CV/DC

CMS

TIFF 8kW

Schneiderunder development

Dec.2012under preparation PH/DT/DI & PO

Pixel phase115kW

Schneiderunder development

Dec.2013under preparation PH/DT/DI & PO

ATLAS & CMSCORA 2kW

Siemens completed completed PH/DT/PO

ATLAS & MPIMARCO

1kW Siemens

under developmentSeptember 2012

under preparation PH/DT/PO

ATLASCMS & LHCbAIDA & KEK

TRACI 100W

National Inst.

completed version1 and 2

x PH/DT/PO

History

Lukasz Zwalinski GUAPI 26th June 2013

• We have selected to work with Schneider PLCs• We knew that PROFIBUS is not perfect solution for Schneider• Schneider strongly advertised Ethernet IP (FDT/DTM workshops etc.)• EN-ICE recommended to study this technology• More and more equipment available with Ethernet IP

• Selected WAGO as I/O solution• FESTO as electro valves

Why Ethernet IP?

Ethernet IP advantages• Siemens and Schneider goes in the direction of implementation of the industrial Ethernet• Transparency: configure, control and diagnose all devices on the network • Efficiency: consolidate control onto a single network module• Simplicity: manage the entire network with Unity Pro• Ring topology• Hot Swapping• Etc..

But is it real??

IBL Control system architecture

CERN Technical Network

CERN GPN

OWS OWS OWS

EN/CV Terminal server

Detector Control System

DIP

Central Control Room

Critical data tunnel from PLC to DCS

IBL plant ALocal MODBUS TCP/IP

Pneumatic lines

FESTO

WAGO I/Os

Local Touch Screen

Premium CPU Premium CPU

IBL plant BLocal MODBUS TCP/IP

Pneumatic lines

FESTO

WAGO I/Os

Local Touch Screen

Vacuum PLC

M340M CPU

Lukasz Zwalinski GUAPI 26th June 2013

Privet network Privet network

IBL real implementation

Lukasz Zwalinski GUAPI 26th June 2013

Closer look on WAGO

Lukasz Zwalinski GUAPI 26th June 2013

CMS real implementation

Lukasz Zwalinski GUAPI 26th June 2013

• CERN TN – Ethernet IP was not validated to be implemented in CERN TN network directly, as the consequence we don’t have the direct access to all the devices in the network

• UNITY PRO - Each PC from which we want to access our application should have the same DTM library, so we need to import the definition files on all our PCs independently

• Addressing

Implementation issues

We have to remember that declared memory area for the Ethernet IP communication is not covering with UNICOS mapping

Lukasz Zwalinski GUAPI 26th June 2013

• Addressing - to establish no error communication the declared memory addressing for the coupler has to match exactly the real memory consumed by the coupler.

Implementation issues

Trick for WAGOCalculated memory area for inputs has to be always increased by 1 byte!! As it is reserved for coupler identification.

User has to carefully calculated required memory or can connect to the device and read how much it consumes. (Online parameters in Ethernet IP)

Lukasz Zwalinski GUAPI 26th June 2013

• Addressing – is not an issue when You use Schneider equipment like STB_NIC2212

• When additional Advantys software installed for configuration of the Schneider Ethernet IP device it connects automatically with UNITY and it has very nice graphical representation of the hardware configuration

Implementation issues

Lukasz Zwalinski GUAPI 26th June 2013

• Introduced new FE Encoding type for Ethernet IP (400)

• Instance template modification

• Based on current PROFIBUS implementation

• Small modifications according to the way of addressing

• Small modification for coupler I/O error

UNICOS CPC 6 extension for WAGO and FESTO

FEDeviceIOConfig  FEChannel

FE Encoding Type InterfaceParam1 InterfaceParam2 InterfaceParam3 InterfaceParam4 InterfaceParam5 InterfaceParam6 InterfaceParam7 InterfaceParam8 InterfaceParam9 InterfaceParam10

400 WAGO_1_IN 0 0 455400 WAGO_1_IN 2 0 455400 WAGO_1_IN 4 0 455400 WAGO_1_IN 6 0 455400 WAGO_1_IN 8 0 455400 WAGO_1_IN 10 0 455400 WAGO_1_IN 12 0 455

FEDeviceIOConfig  FEChannel

FE Encoding Type InterfaceParam1 InterfaceParam2 InterfaceParam3 InterfaceParam4 InterfaceParam5 InterfaceParam6 InterfaceParam7 InterfaceParam8 InterfaceParam9 InterfaceParam10

400 WAGO_1_IN 172 0 0 430400 WAGO_1_IN 172 1 0 430400 WAGO_1_IN 172 2 0 430400 WAGO_1_IN 172 3 0 430400 WAGO_1_IN 172 4 0 430400 WAGO_1_IN 172 5 0 430

Lukasz Zwalinski GUAPI 26th June 2013

Summary

Summary:

• Ethernet IP is very interesting technology but at CERN currently we can not

use all features because of the network infrastructure. It does not allow in

reality to access to the device form our PC like in example Siemens PDM.

We need to connect into privet network.

• Advantages:

• Ring topology – verified

• Hot swapping – not verified

• Consolidation – verified

• Easy cabling

Lukasz Zwalinski GUAPI 26th June 2013