OPC for Commercial Power Supplies etc Major investment

  • Slides: 5
Download presentation
OPC for Commercial Power Supplies (etc. ) Major investment of the Experiments in commercial

OPC for Commercial Power Supplies (etc. ) Major investment of the Experiments in commercial power supplies (~30 MCHF) -> Need proper integration into the DCS -> Currently OPC Data Access (DA) • However, DA is legacy -> Need to move to OPC Unified Architecture • Previous model whereby companies developed the servers very inefficient • Black-box, not real software expertise in company, issues impossible to reproduce in lab setups • Decision to develop the OPC servers at CERN in collaboration with the companies •

Collaboration Overview • Within CERN • EN-ICE and ATLAS identified a common interest in

Collaboration Overview • Within CERN • EN-ICE and ATLAS identified a common interest in OPC-UA middleware. • Created QUASAR, a framework which provides consistent implementations of OPC-UA servers. • Used to create numerous OPC-UA servers in EN-ICE and ATLAS. • KT involved to assist with open sourcing QUASAR (CERN I. P. export) • LGPLv 3 licensed. • Outwith CERN • Planned collaborations with CAEN, Wiener and ISEG. • CERN to implement ~80% of device logic, expert knowledge required from commercial partners for 20% optimisation. • Per-vendor collaboration agreements negotiated (with EN-ICE, KT and vendor) • agree on goals and responsibilities of collaborations.

QUASAR FW Architecture OPC-UA client OPC-UA server toolkit (C++) – Unified Automation Logging Security

QUASAR FW Architecture OPC-UA client OPC-UA server toolkit (C++) – Unified Automation Logging Security (X 509 certificate handling) XML Configuration Common namespace items and Namespace utilities Server metainformation Commercial/OS toolkit Common components made at CERN Hardware specific logic, Expected ~80/20 CERN/vendor split Device Logic (Custom code) Hardware access layer (device I/O) – provided by vendor 100% vendor Hardware Goal: To provide homogenous OPC-UA server implementations based on shared components.

How are the servers built? 1. Model (design -> XML) 2. Generate… • C++

How are the servers built? 1. Model (design -> XML) 2. Generate… • C++ stubs • Inherit quasar libs 3. Implement stubs OPC-UA client OPC-UA server Server business logic ISEG HAL (library) Configuration Logging

OPC UA Timeline 2014 2015 Collaboration ATLAS-EN/ICE for development of QUASAR Agreement with companies

OPC UA Timeline 2014 2015 Collaboration ATLAS-EN/ICE for development of QUASAR Agreement with companies established 2017 2016 ISEG: start collaboration on OPC UA server using the FW. QUASAR FW first version ready 2018 ATLAS: ISEG and CAEN OPC-UA servers deployed in production ATLAS: ISEG and CAEN OPC-UA servers validated using production hardware CAEN: Start collaboration on OPC UA server using the FW. Now Start of LS 2 All OPC UA Servers ready for deployment. Windows and linux. Wiener: Start collaboration on OPC-UA server using the FW End of LS 2 OPC DA Servers decommissioned All DA servers replaced with UA servers