Slow Control System for Neutrino Experiment KATRIN

1
Slow Control System for Neutrino Experiment KATRIN
Wolfgang Eppler, Forschungszentrum
Karlsruhe Armen Beglarian, Forschungszentrum
Karlsruhe Volker Hartmann, Forschungszentrum
Karlsruhe Surik Chilingarian, Yerevan Physics
Institute Simon Kelly, Bristol University of the
West of England
2
Neutrino Experiment KATRIN

• tritium beta-decay
• - measures mass of electron neutrino to a
  precision of 0.35 eV
• scales up to previous experiments by an order of
  magnitude

3
Slow Control System Architecture
Extreme use of standards protocols, interfaces,
concepts
Data Access
Netscape Internet Explorer
Operator Control
WebClient
relational Oracle
DB
XML Query
HTTP
Convert
WebServer
XML Schema
Supervisor Control
STxx
LabView DSC
Convert
any database
XML OPC-HDR
FP-1








FP-2








FP-3








FP-4








FP-5








FP-6








Distributed Control
Magnet
Heating/ Cooling
Ultra-High Vacuum
High Voltage
Detector
CRYO- system
4
Experimental Impressions
LabView GUI
Testcylinder
Web GUI (TOSKA, not KATRIN)
5
Steps Towards a Highly Standardized System (1)
Web Server
Web Server
XSU
Oracle specific
relat2xml
XQuery on Clobs
XQuery
XSU
Oracle DB
Clobs
Tables
Oracle DB
In more detail
Admin
Measure
PL/SQL
PL/SQL
OCI Driver
administration data
measurement data
data2xml
OCI Driver
RT Control
RT Control
6
Steps Towards a Highly Standardized System (2)
Web Server
Web Server
Web Server
In more detail
Next step
XQuery
Oracle specific
relat2xml
XQuery on Clobs
XQuery
XSU
XQuery
XML DB
Oracle DB
XML DB
Admin
Measure
JDBC Driver
XQuery
XQuery
PL/SQL
OPC-XML Client
administration data
measurement data
OPC-XML
OPC-XML Server
OPC-XML
RT Control
RT Control
RT Control
7
OPC vs OPC-XML
OPC Drawbacks
- COM/DCOM not available on non-Microsoft
platforms - Consequently no integration into
enterprise applications without COM/DCOM
interface - Firewall problem as DCOM uses
dynamically allocated TCP/IP ports only
OPC-XML Drawbacks
- Data representation of OPC-XML as text -gt
more network traffic (lt35), more CPU ressources
- OPC History and OPC Alarms and Events not yet
available as XML - Restricted data subscription
with XML
8
OPC-XML/HDR (High Data Rate)

• Purpose
• Higher data rate by better binary data encoding
  und use of UDP
• Compatible with OPC XML DA
• Better security
• Stringent use of XML paradigm for users data
  presentation
• Support of multicasting
• Support of data subscription

• 2 alternatives
• SOAP message with attachment
• Still working draft in W3C
• No support by major XML libraries
• No multicasting
• HTTP message with MIME multipart type and XLink
• No multicasting, but separate connection as done
  in FTP protocol
• New user defined data type described by XML Schema

9
HTTP/MIME/XLink-Example
Content-Type multipart/related
boundaryxxxxxx --xxxxxx Content-Type
text/xml Content-IDOpcXmlHdrMessage lt?xml
version1.0?gt ...... ltValue xsitypeBinaryStre
am gt ltBinaryStream typeSomeType records5
recordsize64 xlinktypesimple
xlinkhrefcidBinaryData1/gt lt/Valuegt ltValue
xsitypeMulticastStreamgt ltMulticastStream
type SomeType recordsize64
xlinktypesimple xlinkhrefmcast224.0.0.1
/gt lt/Valuegt ltValue xsitypeXMLStreamgt ltXMLStrea
m xlinktypesimple xlinkhrefcidTypeDescripti
on1/gt lt/Valuegt ......
--xxxxxx Content-Type application/binary Content-
Transfer-Encoding Little-Endian Content-Length C
ontent-IDBinaryData1 ..... Binary Data
...... --xxxxxx Content-Type
text/xml Content-IDTypeDescription1 ... XSD
Schema ...
10
Implementation of OPC XML HDR
Servers
Internal Data Representation
Libraries
XML Parser XML Validation by XSD Schema
LibOpcXml
XML Data Representation
OPC Server
Access Rights Check XML Document Signature
Check XML Document Decryption
LibOpcSecure
Secure XML Data Representation
LibOpcHttp
MIME/XLink/HTTP Encapsulation
XLink / MIME / HTTP Message
Web Server
LibOpcTransport
Message Communication by IPv4 / IPv6
Transport Level
11
Which XML Parser?

• XML libraries used for Benchmarking
• LibXML2 GDome LibXSLT XML Security
• Apache Xerces for C Apache Xalan for C
• IBM XML4C IBM Lotus XSL
• Expat CenterPoint XML Sablotron Arabica
• RXP Parser
• Oracle XDK for C/C
• Oracle XDK for Java
• QT XML Module
• Sun XML Pack Summer Apache XML Security

• Performance measured in total
• and in following sub-tasks
• Non-Validating Parsing with Native, SAX,
• DOM Engines Benchmark
• Creating Serializing DOM tree Benchmark
• Schema Validation Benchmark
• XSL Transformation Benchmark
• XML Security (Signature, Encryption) Benchmark

-gt LibXML2 was chosen
(In spite of no XML Schema validation)
12
XQuery vs SQL
XQuery (1 Signal)
XQuery (4 Signals)
SQL (1-4 Signals)
XQuery
13
XQuery vs XSU
(XSU XML SQL Utility (Oracle)) Each signal with
own XML structure
XQuery (4 Signals)
XQuery (1 Signal)
XSU (8 Signals)
XSU (1-4 Signals)
14
XSU Improvements (1)
1. (big) improvement 1 timestamp for all signals
21 Signals
16 Signals
12 Signals
1-8 Signals
15
XSU Improvement (2)
2. (small) improvement Timestamps in separate
XML structure
16
XSU Improvement (3)
3. (big) improvement use of internal XSLT
17
Conclusion

• Still many problems with XML
• Especially problematic
• XML Query (-gt Oracle XSU)
• OPC XML (-gt OPC XML HDR, OCI, LOGOS)
• Significance of XML in future undoubtful
• More and more same techniques in
• Industrial automation
• Office applications
• Enterprise solutions
• Physical experiments
• because of same components
• database, internet, browser, documentation, GUI,
  graphics, ...
• and of same problems
• fast data access, good searching capabilities,
  flexible software, ...
• -gt Connection to Grid Computing