• CAN interface for low voltage supplies and front-end ELMBs (Embedded Local Monitor Boards)
• SYS TEC USB-CANmodul16 • Previous underuse of CAN ports • New architecture enables more efficient layout with fewer modules
• All compatibility problems were removed • Any combination of sub-applications was made possible • Proposed merging minimized I/O interface complexity
Old computers: DELL 1950/2950 New computers: M610 blades • Reduction to 3 servers • Additional server available for
load distribution (if necessary)
Software and databases had to be merged to enable this transition
1) ETH Zurich, Switzerland 2) University of Wisconsin-Madison, U.S.A.
O. Holme1, D. Di Calafiori1, G. Dissertori1, L. Djambazov1, W. Lustermann1, S. Zelepoukine1,2 On behalf of the CMS ECAL group
MOPPC035
Built with many industrial technologies: • Microsoft Windows • SIMATIC WinCC Open Architecture supervisory
control and data acquisition toolkit • Open Platform Communications (OPC) • Ethernet, CAN and RS-485 for data transfer • S7, Modbus, CANopen and vendor specific protocols
Uses the CERN Joint Controls Project (JCOP) Framework
• Investigation with CERN and CMS for CAN-Ethernet solution
Acknowledgements Swiss National Science Foundation, Switzerland
80 Bias voltage ELMBs 54 Low voltage supplies
54 Low voltage supplies 28 Low voltage supplies
2 Bias voltage ELMBs 22 Temperature and Humidity ELMBs
Previous layout
New layout
Grey ports are unused
Incompatibilities: - Internal object names - I/O interface numbering
Server 1
Monitoring & safety system
interfacing
Server 2
Wiener power supply
monitoring
Server 3
CAEN power supply
Monitoring
CAEN Hardware
Wiener Hardware
CA
EN
Eth
erne
t pr
otoc
ol
Wie
ner C
AN
pr
otoc
ol
Safety Systems
Humidity Monitoring
CA
Nop
en
Temperature & Bias Voltage
Monitoring
S7
Mod
bus-
TCP
Proposed merged architecture
• Frequent modifications to software and DBs required testing • Validation of new WinCC OA and JCOP Framework versions • Automatic test environment created using Python & Jenkins CI
• Databases for application images (ConfDB) and historical data (CondDB) • ConfDB merging simplifies deployment, maintenance and operations • CondDB merging was essential due to WinCC OA design
Yes
No
Test passes
• Sensitive test of validity • Problems identified quickly • Enables rapid issue resolution
ConfDB Application
instance
Unified schema
Individual sub-application schemas
Sub-app 1 +
Sub-app 2
Sub-app 1
Sub-app 2
Test fails
Reference image files
Application source files
Fuzzy comparison
Instance image files
Investigate & resolve
Are equal?
• Significant consolidation and merging achieved • Automatic testing ensured smooth re-integration • Working towards goal of all readout via Ethernet
