ma cs workshop 3-2-06adriaan rijllart1 labview integration into the lhc control system the...
TRANSCRIPT
CS workshop 3-2-06
Adriaan Rijllart 1
MA
LabVIEW integration into the LHC control
system
The LHC LabVIEW
CS workshop 3-2-06
Adriaan Rijllart 2
MA
Presentation overview
Why LabVIEW in the LHC control? What is it used for? How? Can we do better? Can we use CS?
CS workshop 3-2-06
Adriaan Rijllart 3
MA
Why LabVIEW? Post Mortem analysis of transient events is much easier with LV than with Java.
Equipment experts are using LV to debug and commission their systems
PXI with LV-RT will be used for fast digitisers (8 GS/s), HW and drivers not available in VME.
On-line beam diagnostics needs fast software development tool to enable expert operators to quickly understand instabilities, resonances, beam losses, …
CS workshop 3-2-06
Adriaan Rijllart 4
MALabVIEW in the LHC control system
Javaapplication
CMW
CMWFESA
LabVIEWapplication
LabVIEWRealTime
DataSocketserver
LabVIEWapplication
Central partEquipment diagnostics
On-line beam diagnostics
lib
Data server
LabVIEWapplication
Post Mortemanalysis
CS workshop 3-2-06
Adriaan Rijllart 5
MAPost Mortem data analysis stages
Individual system tests (QPS, PIC, PC)
Hardware Commissioning (powering) Sector tests (octant) LHC commissioning with beam LHC operation with beam
CS workshop 3-2-06
Adriaan Rijllart 6
MAQuench Protection System check-out
•Synchronised analog and digital graphs for visual inspection.
•Analysis of time constants•Transition sequence and delay times of digital signals.
CS workshop 3-2-06
Adriaan Rijllart 7
MA
LabVIEW equipment diagnosis
CMW wrapper developed at CERN
Equipment experts can connect to their equipment bypassing the middle tier
FESA is Front-End Software.
LHC Devices
FESA
LabVIEW
User application(virtual instrument)
FESA palette
FESA objects
CMW Wrapper
Client PC
TCP/IP
Wrapper DLL
CMW client
Orbacus OBECORBA client
FESA FEC
IP network
CMW server
Orbacus OBECORBA server
CS workshop 3-2-06
Adriaan Rijllart 8
MA
LabVIEW - CMW wrapper Get and Set functions are implemented.
Every Get command has 5 different modes:
0 – synchronous
1 – first request is synchronous and all next is asynchronous
2 – asynchronous
3 – subscribe property
4 – unsubscribe property
5 – last value from cache.
CS workshop 3-2-06
Adriaan Rijllart 9
MA
Data exchange Java-LabVIEW
The problem: OASIS - observation of analog signals system,
difficult to modify. Need for fast programmable signal analysis application
(FFT, filters, convolution, correlation,…).
Our solution: Connect via NI library to send data to the DataSocket
server. Then connect from any LabVIEW application to the
DataSocket server to receive the data. Minimum investment: only a Java data interface.
CS workshop 3-2-06
Adriaan Rijllart 10
MA
LabVIEW signal analyser
NI DataSocket Server
Java <-> LabVIEW data exchangethe OASIS example
Publish
Subscribe
OASISJava data interface
Existing
NI provided
AB/OP devel.
AP+MA devel.
Legend
NI.jar
CS workshop 3-2-06
Adriaan Rijllart 11
MAIntegration of LV-RT and PXI LV-RT on PXI can publish data.
Using LV8: network variables.
LV control room application merges OASIS and LV-RT data.
LabVIEWapplication
DataSocketserver
CS workshop 3-2-06
Adriaan Rijllart 12
MA
Questions Can we profit from CS? If yes, how? Should we try DIM? Try LV8?