Last modified by sndueste on 2024/03/13 14:17
From version 4.1
edited by sendels
on 2019/06/24 12:14
Change comment: There is no comment for this version
To version 12.1
edited by sendels
on 2021/02/10 15:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,34 +1,63 @@
1 1  (% class="twikiTocTitle" %)Contents:
2 2  
3 -* general Camera info
4 -* Camera server general info
5 -* scaling the image / spectra
6 -* Spectra (line outs) and Gaussian fits
7 -* working with ROIs
8 -* saving images
9 -* Installing new cameras
10 -* Renaming cameras
11 -* special topics
12 -**
13 -*** Background subtraction:
14 -*** Power Over Ethernet
15 -*** Triggering
16 -*** Restarting Servers
17 -* FAQs
18 -* Troubleshooting
19 -** Individual camera manuals
20 -* Cameras used in the FLASH photon diagnostic
3 +\\
21 21  
5 +
6 +
7 +{{toc/}}
8 +
9 +== General Camera info ==
10 +
11 +several [[different camera types>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=Camera%20server||shape="rect"]] can be easily integrated into DOOCS.
12 +
13 +The details of the available control parameters depends on the camera type. here is a typical view of
14 +
22 22  \\
23 23  
17 +the Standard view:                                                                                   the controls view:                                                                                                and the Expert view with all available control features
18 +
19 +[[image:attach:image2019-9-19_12-28-30.png||height="400"]][[image:attach:image2019-9-19_12-29-14.png||height="400"]][[image:attach:image2019-9-19_12-29-44.png||height="400"]]
20 +
24 24  \\
25 25  
26 -== general Camera info ==
23 +\\
27 27  
28 -there are several cameras that are watched if they have the correct rep rate and if not the server is restarted every 15 min. here is the list of these cameras [[https:~~/~~/ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=FlashCamerasToWatch~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=FlashCamerasToWatch||shape="rect"]]
25 +== Troubble shooting / Restarting the camera server ==
29 29  
27 +If there are problems occurring with the camera ( no image is shown, no update, camera server crashes ...) then it is** mainly 2 reasons:**
28 +
29 +* **There is no trigger connected to the camera → check with trying to run the camera untriggered ...**
30 +* **the server has problems -> restart the server.**
31 +
32 +Even if it seems unrelated ( camera saved only 0 in the DAQ, reprate can not be changed... ) it turned out that restarting the camera server is helpful.
33 +
34 +1. Best to make a screenshot (in expert mode) to the logbook before restarting in case parameter settings are lost ...
35 +1. goto WDserver and press restart. The camera panel will go red and will come back after about 20 seconds ...
36 +
37 +[[image:attach:image2019-9-24_16-1-16.png||height="400"]]
38 +
30 30  \\
31 31  
41 +If the restart (several times ...) does not help there is an option to make a "deeper restart". This option uses a restart script which includes powercycling of the camera ( for ethernet cameras)and reloading a standard configuration.  One has to be logged in at a linux computer in order to run the script.
42 +
43 +\\
44 +
45 +[[image:attach:image2019-9-24_16-3-48.png||height="400"]]
46 +
47 +\\
48 +
49 +\\
50 +
51 +== Monitoring system ==
52 +
53 +we implemented a monitoring system for the important beamline cameras in FLASH1 and FLASH2.
54 +
55 +the camera check overview shows a red indicator if the camera is off OR the actual values are different from the saved reference values. Clicking on the red symbol in the camera check one can get to the overview of the parameters. Here a red dot indicates which parameter is different from the reference setting. e.g. if ROI settings have been changed also the reference settings have to be changed accordingly if they are now the new reference !!
56 +
57 +The warning is also shown inn the according control panels for the cameras.
58 +
59 +[[image:attach:image2019-9-19_12-26-21.png||height="250"]] [[image:attach:image2019-9-19_12-34-54.png||height="250"]]
60 +
32 32  == Camera server general info ==
33 33  
34 34  [[info from the DOOCS pages~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=Camera%20server||shape="rect"]]
... ... @@ -39,17 +39,45 @@
39 39  
40 40  == scaling the image / spectra ==
41 41  
42 -\\
71 +[[image:attach:image2019-9-19_12-40-57.png||height="250"]][[image:attach:image2019-9-19_12-59-37.png||height="167"]]
43 43  
73 +one can scale the image with a different scale as pixel.  the center as well as the "pixel size" can be set.
74 +
44 44  == Spectra (line outs) and Gaussian fits ==
45 45  
77 +The camera server can fit the vertical and horizontal averaged data  with a Gaussian fit and provides the corresponding parameters ( height, centroid and width) which have a history and can be used as for optimizing a signal ...
78 +
46 46  \\
47 47  
81 +[[image:attach:image2019-9-19_15-3-23.png||height="400"]]
82 +
83 +"Spectrum" of the whole image. this can lead to a wrong fitting ...         
84 +
85 +\\
86 +
87 +\\
88 +
89 +[[image:attach:image2019-9-19_15-5-29.png||height="400"]]
90 +
91 +For a useful fit it is better to look at the "spectrum" of a ROI which can be set to the desired region. Note that the ROI has to be filled (Width = 0) to be correctly averaged!
92 +
93 +\\
94 +
95 +\\
96 +
97 +[[image:attach:image2019-9-19_15-4-20.png||height="250"]]
98 +
99 +For some cameras we also have dedicated Beam profile viewers.
100 +
101 +\\
102 +
103 +\\
104 +
48 48  == working with ROIs ==
49 49  
50 50  To create more ROIs one has to do the following:
51 51  
52 -\\
109 +[[image:attach:image2019-9-19_13-2-26.png||height="400"]]
53 53  
54 54  \\
55 55  
... ... @@ -84,7 +84,7 @@
84 84  * Open the Jddd watchdog panel for the server ((% class="twikiNewLink" %)WatchdogOverview(%%).xml). goto camera server -> locations
85 85  * right upper part is a button Divice control
86 86  
87 -[[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/Clipboardadd_camera.jpg||alt="Clipboardadd_camera.jpg" width="455" height="408"]]
144 +[[image:attach:Clipboardadd_camera.jpg||height="400"]]
88 88  
89 89  *
90 90  ** use action: add
... ... @@ -92,9 +92,9 @@
92 92  ** add name
93 93  ** press send
94 94  
95 -the you see the new camera in the location table. do ot forget to click "Cfg. restore" in the camer expert pannel onece everything looks o.k. with the camera ( otherwise the cameras may switch with their names ...)
152 +the you see the new camera in the location table. do not forget to click "Cfg. restore" in the camera expert panel once everything looks o.k. with the camera ( otherwise the cameras may switch with their names ...)
96 96  
97 -[[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/screenshot.png||alt="screenshot.png" width="1490" height="950"]]
154 +[[image:attach:screenshot.png||height="400"]]
98 98  
99 99  \\
100 100  
... ... @@ -118,7 +118,7 @@
118 118  ==== Background subtraction: ====
119 119  
120 120  * it is important that the values for negative offset are 0. otherwise the substraction does not work (experimental finding by Stefan ...) . For the Basler A311 cameras the mode has to be 5 . for mode 7 the Background substraction does not work... (no resources left)
121 -* For Basler ethernet camera's the offset needs to be zero in anycase, otherwise the server will crash. Also note, you have to make a reference image, that you have to stop/start the image aquisition before you can enable the background-substraction in jddd.
178 +* For Basler ethernet camera's the offset needs to be zero in any case, otherwise the server will crash. Also note, you have to make a reference image, that you have to stop/start the image acquisition before you can enable the background-substraction in jddd.
122 122  
123 123  \\
124 124