1 / 9

Industrial Power Supplies

Industrial Power Supplies. Observations from the survey responses. Observations per commercial vendor. Engagement outline with commercial vendors. Observations from the Survey. Can you imagine replacing your XXX powering system with… Generally satisfied or too heavily invested to change.

dong
Download Presentation

Industrial Power Supplies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Industrial Power Supplies • Observations from the survey responses. • Observations per commercial vendor. • Engagement outline with commercial vendors.

  2. Observations from the Survey • Can you imagine replacing your XXX powering system with… • Generally satisfied or too heavily invested to change. • CAEN, Wiener and ISEG live on. • New commercial hardware/vendors to incorporate in fwJCOP? • Wiener(/ISEG) MPOD? • Bulk LV power supplies (PH/ESE talk), control interface? • Industrial power supply connectivity • CAN and Ethernet. • Slight prevailing trend migrating CAN -> Ethernet. CAN free future possible? • Environmental constraints • Rad/Mag tolerant CAEN/Wiener hardware acceptable. No step change in environments. • Really? Higher luminosity, higher energies? • New functional requirements • More power. • Linux support • Windows servers required? No complexity with distributed client/server with OPC-UA (compared to OPC-DA).

  3. Observations per commercial vendor • CAEN • Readout too slow. • New CAEN hardware models to support. • Mainframe firmware is too ‘black box’. • Force log off of mainframe sessions. • Intermittent board comms loss. • WIENER • Water leaks. • Insufficient granularity in monitor/control parameters. • Connectivity problems on restart. • Commands lost. • ISEG • Poor performance (readout? Stability?), improved now. • PEAK USB/CAN gateway only. SYSTEC support desirable (and Anagate?).

  4. OPC-UA servers: CAEN, WIENER, ISEG. End of LS2 Start of LS2 2015 Now 2014 2016 OPC UA Servers are ready for deployment Collaboration ATLAS-EN/ICE for the development of the QUASAR FW Start of collaboration with ISEG on OPC UA server using the FW. OPC DA Servers are decommissioned Start of collaboration with CAEN and Wiener on OPC UA servers using the FW. OPC UA Servers are commissioned QUASAR FW is ready Agreement with companies established

  5. End

  6. OPC for Commercial Power Supplies Major investment of the Experiments in commercial power supplies (>15MCHF) -> Prior importance to have proper integration into the DCS -> Currently OPC Data Access (DA) • However, DA is being phased out -> 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

  7. 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) • LGPLv3 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 to be negotiated (with EN-ICE, KT and vendor) to agree on goals and responsibilities of collaborations.

  8. QUASAR FW Architecture Delivered via the OPC-UA server generator framework. OPC-UA client OPC-UA client OPC-UA client Commercial toolkit OPC-UA server toolkit (C++) – Unified Automation Common namespace items and Namespace utilities Logging Security (X509 certificate handling) XML Configuration Server meta-information 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 Hardware Hardware Goal: To provide homogenous OPC-UA server implementations based on shared components.

  9. OPC UA Timeline End of LS2 Start of LS2 2015 Now 2014 2016 OPC UA Servers are ready for deployment Collaboration ATLAS-EN/ICE for the development of the QUASAR FW Start of collaboration with ISEG on OPC UA server using the FW. OPC DA Servers are decommissioned Start of collaboration with CAEN and Wiener on OPC UA servers using the FW. OPC UA Servers are commissioned QUASAR FW is ready Agreement with companies established

More Related