2. LabVIEW Basic I with RADE introduction A. Raimondo (EN/ICE)

3. ADE Rapid Application Development Environment based on LabVIEW

4. Why was RADE developed?

5. Users applications domains: LabVIEW, MatLab, scripts, etc. Beam Operation JAVA SCADA PVSS Test & Development RADE

6. Test & Development applications characteristics  Punctually used applications (i.e. expert diagnostics)  Rapidly evolving applications (i.e. machine development)  Stand-alone systems (i.e. test facilities)  Short development time applications (i.e. specific analysis)

7.  Fast programming  Rapid learning curve  Drag and drop GUI development  Wide range of analysis libraries  Light/independent environment Test & Development applications requirements LabVIEW programming language  Integration with CERN infrastructures our effort

8. Other reasons for choosing LabVIEW  We have a deep experience (more then 10 years) EPICS and Tango have made a LabVIEW interface to their environments, mainly for the same reason (rapid application development)  Commonly used for control in other research labs:  Officially supported at CERN

9. What is RADE today?

10. 4. Development help  Trainings (cta)  RADE events (indico)  Documentation (edms)  Defined GUI  Application templates  Configuration files The building blocks 3. Support  Webpage (http://cern.ch/rade)  Mailing list (rade-users@cern.ch)  Direct user support 1. Installation  Clear LabVIEW version policy  NFS install for Linux  TS install (lvtsco)  Windows install (cmf)  Application server (lvdssco)  RADE servers (rade1 & rade2) 2. Control Integration  Maintained interface libraries - CMW- DIP - RBAC- PLC - SQL- JAPC - SDDS

11. LabVIEW library C/C++ shared lib C/C++ shared lib CMW RBAC Java Tomcat Server Tomcat Server JAPC Oracle RBAC LabVIEW Server ODBC SDDS PLC LabVIEW lib LabVIEW user application The RADE core technology

12. The User Palette

13. The framework Training Support Defined GUI Application templates Configuration files Documentation LabVIEW SQL SDDS JAPC libs DIP

14. Examples of RADE usage

15. RADE used for equipment tests RADE app 3rd party driver Middleware Front-End GUI Equipment Integration in the 3 layers control architecture

16. Optical Interface Board Tester (TE/MPE)

17. RADE used for specialist tools RADE app CMW wrapper JAPC FESA Java GUI Equipment example of accelerators architecture

18. SPS Power Converter View (TE/EPC)

19. RADE used for GUIs RADE app JAPC FESA Java GUI Equipment example of accelerators architecture LV2JAPC

20. Bunch Shape Measurement (BE/OP)

21. RADE used for offline applications SDDS RADE app SDDS lib JAPC FESA Java GUI Equipment example of accelerators architecture

22. Post Mortem Analysis (EN/ICE)

23. RADE activity

24. Evolution:  January 2008 (proposal, collection of libs)  May 2008 (GUI, templates and configuration)  August 2008 (training and documentation)  January 2009 (merge with LabVIEW CERNwide support) Development People involved:  2 FTE (temporary) for development  0.5 FTE (staff) for support Users:  80 registered RADE users (on 430 LabVIEW users)

25. Present domains of use Machine development Test facilities Expert tools

26. SCADA domain Operation domain Coming soon... in 2009  Interface to LASER alarms  libnodave wrapper for Siemens PLCs  UNICOS in LabVIEW

27. Questions? ADE