1. Prepared by: Zorin Evgeny Today, everybody wants a dashboard. Like many newcomers to the technology scene, dashboards are sexy. Stephen Few, Information Dashboard Design.

2.  Objective  Building different dashboards for different clients: LHC operation, cryogenic, est..  WEB published dashboard.  Outcome  To use LabVIEW-RADE  To use the CERN web server

3.  Overview RADE data acquiring mechanism  Dashboard data publishing  Subscription, “get” function or read DB?  Web publishing data mechanism  Summary  Next Steps

4.  CMW wrapper High speed Depends only on RDA realization Very few error during operation Direct access, no intermediate server Can crash LabVIEW  JAPC Portability, based on http technology Central server DB access implemented Never crashes LabVIEW, but can stop responding  DIP Built on DIM Direct access Relies on DIP name server Can stop responding

5. LabVIEW Application RADE interface library FESA, DIP, JAPC, DB Equipment driver Equipment

6. Modbus S7 SQL OPC JAPC CMW LHC Logging JPEG

7. 1.Subscription: Fast access to the last published data, synchronized with data source, but limitation for opening subscriptions (~1000). Can overload the front-end. 2.Get: fast access to data, but not all devices support get function and this function can overload the device. 3.Read Data base with JAPC toolkit –slow access (depends on DB). Dashboard Data archive used at startup DBFile

8. Dumping screenshots or XML data ASCII file updating Technical network Public CERN network WEB, CERN server Third part visualization software HTML, JAVA script, WEB page DAQ DashboardASCII writer www.cern.ch/lhcdashboard http://te-dep-crg-oa.web.cern.ch/te-dep-crg- oa/Test%20V2/cryostatus.php www.cern.ch/lhcdashboard/cryo/cryoope.html

9. Client applications LHC Dashboard (public), CRYO-Dashboard (cryo-team + public) We support and improve Dashboards Web publishing Status  We use CMW, DIP and JAPC2LV technologies  We develop new types of dashboards including 3D graphs  We work on the stability of the application  Error detection/correction  Monitoring  Auto-restart in case of crash

10. Next phase – Make more interactive web application dashboard – Finish writing data in ASCII format for third party software – Use other technologies for data representation