1. Ethernet IP solution for ATLAS IBL and CMS Pixel detectors CO 2 cooling plants 26.06.2013 Lukasz Zwalinski PH/DT/DI

2. Presentation overview A bit of history Why Ethernet IP? Control system architecture example Real implementation example Implementation issues Summary Overview Lukasz Zwalinski GUAPI 26 th June 2013

3. Setting CO 2 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 History

4. Lukasz Zwalinski GUAPI 26 th 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??

5. IBL Control system architecture OWS EN/CV Terminal server Detector Control System DIP Central Control Room Critical data tunnel from PLC to DCS Vacuum PLC M340M CPU Lukasz Zwalinski GUAPI 26 th June 2013 Privet network

6. IBL real implementation Lukasz Zwalinski GUAPI 26 th June 2013

7. Closer look on WAGO Lukasz Zwalinski GUAPI 26 th June 2013

8. CMS real implementation Lukasz Zwalinski GUAPI 26 th June 2013

9. 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 26 th June 2013

10. 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 WAGO Calculated 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 26 th June 2013

11. 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 26 th June 2013

12. 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 TypeInterfaceParam1InterfaceParam2InterfaceParam3InterfaceParam4InterfaceParam5InterfaceParam6InterfaceParam7InterfaceParam8InterfaceParam9InterfaceParam10 400WAGO_1_IN00455 400WAGO_1_IN20455 400WAGO_1_IN40455 400WAGO_1_IN60455 400WAGO_1_IN80455 400WAGO_1_IN100455 400WAGO_1_IN120455 FEDeviceIOConfig FEChannel FE Encoding TypeInterfaceParam1InterfaceParam2InterfaceParam3InterfaceParam4InterfaceParam5InterfaceParam6InterfaceParam7InterfaceParam8InterfaceParam9InterfaceParam10 400WAGO_1_IN17200430 400WAGO_1_IN17210430 400WAGO_1_IN17220430 400WAGO_1_IN17230430 400WAGO_1_IN17240430 400WAGO_1_IN17250430 Lukasz Zwalinski GUAPI 26 th June 2013

13. 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 26 th June 2013