A Beam Image Server For TTF2. L.Catani PCaPAC 2002

Transcription

1 A Beam Image Server For TTF2 L.Catani PCaPAC 2002

2 A Beam Image Server For TTF2 (why we keep on using LabVIEW) L.Catani PCaPAC 2002

3 About

4 About evolution of the Optical Diagnostic Control System (ODCS) from TTF to TTF2

5 About evolution of the Optical Diagnostic Control System (ODCS) from TTF to TTF2 software porting to different platforms

6 About evolution of the Optical Diagnostic Control System (ODCS) from TTF to TTF2 software porting to different platforms integration of new functionalities as the development software (LabVIEW ) provides new features

7 TTF Layout with OTR Stations

8 OTR TTF TV Camera + lenses + filters all of them with remote control

9 Background

10 Background previous experience with LabVIEW in a Control System we used it as GUI and to develop high-level applications

11 Background previous experience with LabVIEW in a Control System we used it as GUI and to develop high-level applications it has a powerful Image Analysis Library and Frame Grabbers drivers (available only for the Mac, that time)

12 Background previous experience with LabVIEW in a Control System we used it as GUI and to develop high-level applications it has a powerful Image Analysis Library and Frame Grabbers drivers (available only for the Mac, that time) some analysis software already developed

13 ODCS v (see PCaPAC99)

14 ODCS v (see PCaPAC99)

15 ODCS v (see PCaPAC99) What was needed:

16 ODCS v (see PCaPAC99) What was needed: VME boards

17 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis

18 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis Communications with DOOCS

19 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis Communications with DOOCS Limitation:

20 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis Communications with DOOCS Limitation: networking tools

21 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis Communications with DOOCS Limitation: networking tools (anyway, images are heavy!)

22 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis Communications with DOOCS Limitation: networking tools Solution: (anyway, images are heavy!)

23 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis Communications with DOOCS Limitation: networking tools Solution: (anyway, images are heavy!) Server and Operator Console on a Macs

24 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis Communications with DOOCS Limitation: networking tools Solution: (anyway, images are heavy!) Server and Operator Console on a Macs VME shared memory for communication

25 ODCS v (see PCaPAC99) What was needed: VME boards Image Acquisition & Analysis Communications with DOOCS Limitation: networking tools Solution: (anyway, images are heavy!) Server and Operator Console on a Macs VME shared memory for communication Low-level C-library for LabVIEW (labview doesn t provide pointer variables)

26 Example of Measurement applications

27 ODCS Client Desktop

28 ODCS Client Desktop

29 ODCS v (see PCaPAC200)

30 ODCS v (see PCaPAC200)

31 Reasons: ODCS v (see PCaPAC200)

32 ODCS v (see PCaPAC200) Reasons: Computers upgrade -> no fiber-optic link to VME available

33 ODCS v (see PCaPAC200) Reasons: Computers upgrade -> no fiber-optic link to VME available Better integration in TTF Control System & remote operation

34 ODCS v (see PCaPAC200) Reasons: Computers upgrade -> no fiber-optic link to VME available Better integration in TTF Control System & remote operation Desing:

35 ODCS v (see PCaPAC200) Reasons: Computers upgrade -> no fiber-optic link to VME available Better integration in TTF Control System & remote operation Desing: Unix Server and Client + Mac Client + Mac Image Server

36 ODCS v (see PCaPAC200) Reasons: Computers upgrade -> no fiber-optic link to VME available Better integration in TTF Control System & remote operation Desing: Unix Server and Client + Mac Client + Mac Image Server LabVIEW code and C-library ported to Unix (easy!)

37 ODCS v (see PCaPAC200) Reasons: Computers upgrade -> no fiber-optic link to VME available Better integration in TTF Control System & remote operation Desing: Unix Server and Client + Mac Client + Mac Image Server LabVIEW code and C-library ported to Unix (easy!) Limitation:

38 ODCS v (see PCaPAC200) Reasons: Computers upgrade -> no fiber-optic link to VME available Better integration in TTF Control System & remote operation Desing: Unix Server and Client + Mac Client + Mac Image Server LabVIEW code and C-library ported to Unix (easy!) Limitation: no Image Analysis Lib on Unix (basic functions developed in C)

39 ODCS v.2

40 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW):

41 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras

42 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported

43 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)

44 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)! but only available on Windows platform J no problem: we ll port server on Windows

45 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)! but only available on Windows platform J no problem: we ll port server on Windows Low-res images and on-line beam RMS/FWH calculation

46 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)! but only available on Windows platform J no problem: we ll port server on Windows Low-res images and on-line beam RMS/FWH calculation Remote TV Monitor for remote operations

47 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)! but only available on Windows platform J no problem: we ll port server on Windows Low-res images and on-line beam RMS/FWH calculation Remote TV Monitor for remote operations Image Web Server J LabVIEW provide built-in HTTP server

48 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)! but only available on Windows platform J no problem: we ll port server on Windows Low-res images and on-line beam RMS/FWH calculation Remote TV Monitor for remote operations Image Web Server J LabVIEW provide built-in HTTP server no more VME (DOOCS will take care of it)

49 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)! but only available on Windows platform J no problem: we ll port server on Windows Low-res images and on-line beam RMS/FWH calculation Remote TV Monitor for remote operations Image Web Server J LabVIEW provide built-in HTTP server no more VME (DOOCS will take care of it) read from DOOCS information about OTR stations

50 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)! but only available on Windows platform J no problem: we ll port server on Windows Low-res images and on-line beam RMS/FWH calculation Remote TV Monitor for remote operations Image Web Server J LabVIEW provide built-in HTTP server no more VME (DOOCS will take care of it) read from DOOCS information about OTR stations new client-server configuration to provide more efficient remote operation

51 ODCS- Beam Image Server for TTF2 What s new (and why we stick on LabVIEW): IEEE1394 cameras driver library for IEEE1394 -> provided LabVIEW J many IEEE1394 cameras are supported improved Image Analysis Library (IMAQ)! but only available on Windows platform J no problem: we ll port server on Windows Low-res images and on-line beam RMS/FWH calculation Remote TV Monitor for remote operations Image Web Server J LabVIEW provide built-in HTTP server no more VME (DOOCS will take care of it) read from DOOCS information about OTR stations new client-server configuration to provide more efficient remote operation VI Server and Data Socket from LabVIEW J

52 ODCS - Beam Image Server control VI on ODCS Server by means of "VI Server" communication Control digital cameras sending commands to ODCS Server Read images, OTR Stations infos, profiles and RMS/FWHM from server IEEE1394 (Firewire) HTTPServer Control digital cameras Read images from digital cameras Generate on-line profiles and RMS/FWHM Measurements (emittance, energy, etc.) Read OTR Stations infos from DOOCS (target IN/OUT, camera ON/OFF, etc.) Provide Hi-Res Beam Infos for DOOCS applications or measurements Provide Low-Res Beam Infos for Web interface DOOCS VI interface from Global using Data Socket File Server DOOCS VI interface Information on Accelerator Status and Beam Parameters Images for other DOOCS Applications Control Optic Elements (screens, quads, etc.)

53 ODCS - Beam Image Server control VI on ODCS Server by means of "VI Server" communication Control digital cameras sending commands to ODCS Server Read images, OTR Stations infos, profiles and RMS/FWHM from server IEEE1394 (Firewire) HTTPServer Control digital cameras Read images from digital cameras Generate on-line profiles and RMS/FWHM Measurements (emittance, energy, etc.) Read OTR Stations infos from DOOCS (target IN/OUT, camera ON/OFF, etc.) Provide Hi-Res Beam Infos for DOOCS applications or measurements Provide Low-Res Beam Infos for Web interface DOOCS VI interface from Global using Data Socket File Server DOOCS VI interface Information on Accelerator Status and Beam Parameters Images for other DOOCS Applications Control Optic Elements (screens, quads, etc.)

54 ODCS - Beam Image Server control VI on ODCS Server by means of "VI Server" communication Control digital cameras sending commands to ODCS Server Read images, OTR Stations infos, profiles and RMS/FWHM from server IEEE1394 (Firewire) HTTPServer Control digital cameras Read images from digital cameras Generate on-line profiles and RMS/FWHM Measurements (emittance, energy, etc.) Read OTR Stations infos from DOOCS (target IN/OUT, camera ON/OFF, etc.) Provide Hi-Res Beam Infos for DOOCS applications or measurements Provide Low-Res Beam Infos for Web interface DOOCS VI interface from Global using Data Socket File Server DOOCS VI interface Information on Accelerator Status and Beam Parameters Images for other DOOCS Applications Control Optic Elements (screens, quads, etc.)

55 ODCS - Beam Image Server control VI on ODCS Server by means of "VI Server" communication Control digital cameras sending commands to ODCS Server Read images, OTR Stations infos, profiles and RMS/FWHM from server IEEE1394 (Firewire) HTTPServer Control digital cameras Read images from digital cameras Generate on-line profiles and RMS/FWHM Measurements (emittance, energy, etc.) Read OTR Stations infos from DOOCS (target IN/OUT, camera ON/OFF, etc.) Provide Hi-Res Beam Infos for DOOCS applications or measurements Provide Low-Res Beam Infos for Web interface DOOCS VI interface from Global using Data Socket IEEE1394 Library for IMAQ File Server DOOCS VI interface Information on Accelerator Status and Beam Parameters Images for other DOOCS Applications Control Optic Elements (screens, quads, etc.)

56 ODCS - Beam Image Server control VI on ODCS Server by means of "VI Server" communication Control digital cameras sending commands to ODCS Server Read images, OTR Stations infos, profiles and RMS/FWHM from server IEEE1394 (Firewire) HTTPServer Control digital cameras Read images from digital cameras Generate on-line profiles and RMS/FWHM Measurements (emittance, energy, etc.) Read OTR Stations infos from DOOCS (target IN/OUT, camera ON/OFF, etc.) Provide Hi-Res Beam Infos for DOOCS applications or measurements Provide Low-Res Beam Infos for Web interface DOOCS VI interface from Global using Data Socket File Server DOOCS VI interface Information on Accelerator Status and Beam Parameters Images for other DOOCS Applications Control Optic Elements (screens, quads, etc.)

57 ODCS - Beam Image Server control VI on ODCS Server by means of "VI Server" communication Control digital cameras sending commands to ODCS Server Read images, OTR Stations infos, profiles and RMS/FWHM from server IEEE1394 (Firewire) HTTPServer Control digital cameras Read images from digital cameras Generate on-line profiles and RMS/FWHM Measurements (emittance, energy, etc.) Read OTR Stations infos from DOOCS (target IN/OUT, camera ON/OFF, etc.) Provide Hi-Res Beam Infos for DOOCS applications or measurements Provide Low-Res Beam Infos for Web interface DOOCS VI interface from Global using Data Socket File Server DOOCS VI interface Information on Accelerator Status and Beam Parameters Images for other DOOCS Applications Control Optic Elements (screens, quads, etc.)

58 ODCS - Beam Image Server control VI on ODCS Server by means of "VI Server" communication Control digital cameras sending commands to ODCS Server Read images, OTR Stations infos, profiles and RMS/FWHM from server IEEE1394 (Firewire) HTTPServer Control digital cameras Read images from digital cameras Generate on-line profiles and RMS/FWHM Measurements (emittance, energy, etc.) Read OTR Stations infos from DOOCS (target IN/OUT, camera ON/OFF, etc.) Provide Hi-Res Beam Infos for DOOCS applications or measurements Provide Low-Res Beam Infos for Web interface DOOCS VI interface from Global using Data Socket File Server DOOCS VI interface Information on Accelerator Status and Beam Parameters Images for other DOOCS Applications Control Optic Elements (screens, quads, etc.)

59 ODCS - Beam Image Server control VI on ODCS Server by means of "VI Server" communication Control digital cameras sending commands to ODCS Server Read images, OTR Stations infos, profiles and RMS/FWHM from server IEEE1394 (Firewire) HTTPServer Control digital cameras Read images from digital cameras Generate on-line profiles and RMS/FWHM Measurements (emittance, energy, etc.) Read OTR Stations infos from DOOCS (target IN/OUT, camera ON/OFF, etc.) Provide Hi-Res Beam Infos for DOOCS applications or measurements Provide Low-Res Beam Infos for Web interface DOOCS VI interface from Global using Data Socket File Server DOOCS VI interface Information on Accelerator Status and Beam Parameters Images for other DOOCS Applications Control Optic Elements (screens, quads, etc.)

60 VI-Server Communication

61 VI-Server Communication

62 VI-Server Communication

63 Data Socket Communication

64 Data Socket Communication

65 Time needed for a loop of the Beam Image server: 1. Data Socket off, display update on 2. Data Socket off, display update off 3. Data Socket on, display update on 4. Data Socket on, display update off Timing Diagram

66 Communication with DOOCS

67 HTTP Interface LabVIEW Panel for the Consoles

68 HTTP Interface WebBrowser interface for remote operations and web publishing LabVIEW Panel for the Consoles

69 HTTP Interface WebBrowser interface for remote operations and web publishing LabVIEW Panel for the Consoles

70 HTTP Interface WebBrowser interface for remote operations and web publishing LabVIEW Panel for the Consoles

71 Conclusions

72 Conclusions we took advantage of portability of applications developed with powerful PC software

73 Conclusions we took advantage of portability of applications developed with powerful PC software our application has been traveling from one platform to another without loss of performances

74 Conclusions we took advantage of portability of applications developed with powerful PC software our application has been traveling from one platform to another without loss of performances evolution of PC software and development systems allows to EASELY add network capabilities to our applications

75 Conclusions we took advantage of portability of applications developed with powerful PC software our application has been traveling from one platform to another without loss of performances evolution of PC software and development systems allows to EASELY add network capabilities to our applications several protocols and communication solutions can be implemented at the same time with limited programming efforts