Skip to Content
Last modified by sndueste on 2025/04/23 17:34
From version 20.7
edited by sndueste
on 2025/04/23 17:34
Change comment: Update document after refactoring.
To version 15.1
edited by sndueste
on 2021/06/21 10:02
Change comment: Reverted from v. 13

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -FLASHUSER.Controls.WebHome
Tags
... ... @@ -1,1 +1,0 @@
1 -favourite
Content
... ... @@ -1,5 +1,6 @@
1 1  (% class="twikiTocTitle" %)Contents:
2 2  
3 +\\
3 3  
4 4  
5 5  
... ... @@ -7,20 +7,23 @@
7 7  
8 8  == General Camera info ==
9 9  
10 -**several [[different camera types>>url:https://confluence.desy.de/display/MCS/DOOCS+Camera+Server||shape="rect"]] can be easily integrated into DOOCS. **
11 +several [[different camera types>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=Camera%20server||shape="rect"]] can be easily integrated into DOOCS.
11 11  
12 12  The details of the available control parameters depends on the camera type. here is a typical view of
13 13  
15 +\\
14 14  
15 15  the Standard view:                                                                                   the controls view:                                                                                                and the Expert view with all available control features
16 16  
17 17  [[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"]]
18 18  
21 +\\
19 19  
23 +\\
20 20  
21 21  == Troubble shooting / Restarting the camera server ==
22 22  
23 -If there are problems occurring with the camera ( no image is shown, no update, camera server crashes ...) then it is** mainly 2 reasons:**
27 +If there are problems occurring with the camera ( no image is shown, no update, camera server crashes ...) then it is** mainly 2 reasons:**
24 24  
25 25  * **There is no trigger connected to the camera → check with trying to run the camera untriggered ...**
26 26  * **the server has problems -> restart the server.**
... ... @@ -32,13 +32,17 @@
32 32  
33 33  [[image:attach:image2019-9-24_16-1-16.png||height="400"]]
34 34  
39 +\\
35 35  
36 36  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 power cycling 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.
37 37  
43 +\\
38 38  
39 39  [[image:attach:image2019-9-24_16-3-48.png||height="400"]]
40 40  
47 +\\
41 41  
49 +\\
42 42  
43 43  == Monitoring system ==
44 44  
... ... @@ -52,10 +52,11 @@
52 52  
53 53  == Camera server general info ==
54 54  
55 -[[info from the DOOCS pages>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=Camera%20server||shape="rect"]]
63 +[[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"]]
56 56  
57 57  For the (% class="twikiNewLink" %)CeYAG(%%) camera in the FL1 tunnel Gerhard implemented a feature that during a restart a camera_server.conf.default file is copied as conf file to always have the same settings. if one wants to change something permanently one has to edit the default file. e.g. cp /export/doocs/server/camera_server/camera_server.conf.default /export/doocs/server/camera_server/camera_server.conf
58 58  
67 +\\
59 59  
60 60  == scaling the image / spectra ==
61 61  
... ... @@ -67,24 +67,31 @@
67 67  
68 68  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 ...
69 69  
79 +\\
70 70  
71 71  [[image:attach:image2019-9-19_15-3-23.png||height="400"]]
72 72  
73 73  "Spectrum" of the whole image. this can lead to a wrong fitting ...         
74 74  
85 +\\
75 75  
87 +\\
76 76  
77 77  [[image:attach:image2019-9-19_15-5-29.png||height="400"]]
78 78  
79 79  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!
80 80  
93 +\\
81 81  
95 +\\
82 82  
83 83  [[image:attach:image2019-9-19_15-4-20.png||height="250"]]
84 84  
85 85  For some cameras we also have dedicated Beam profile viewers.
86 86  
101 +\\
87 87  
103 +\\
88 88  
89 89  == working with ROIs ==
90 90  
... ... @@ -92,17 +92,22 @@
92 92  
93 93  [[image:attach:image2019-9-19_13-2-26.png||height="400"]]
94 94  
111 +\\
95 95  
96 96  * Define in ENVIRONMENT file the environment variable "(% class="WYSIWYG_TT" %)export FLASH_CAM_ROI_NUM_ENV=xxx(%%)" . With xxx the maximum number of ROIS one needs in a camera controlled by the camera server. (The ENVIRONMENT file is under e.g. export/doocs/hasvuvblfw2/server/camera_server). after editing the ENVIRONMENT file one has to restart the camera server.
97 97  * NOTE the file os owned by doocs adm. to edit it one can use (% class="twikiNewLink" %)WinSCP(%%) and log in as doocsadm.
98 98  
116 +\\
117 +
99 99  * now all cameras have maximum ROIs. if you need less for some cameras read below:
100 100  * Set the required number of ROIs for every camera in the property ROIS.NUM in the configuration file. The way how it's done is the following. On the camera server re-start xxx number of ROIS will be created for every camera. But after reading the configuration file the non-required ROIS will removed for every camera separately according to ROIS.NUM.
101 101  
102 -== saving images "locally" ==
121 +\\
103 103  
104 -The tool writes images of either bmp or an image depemdent format to the specified folder. The folder is on the computer on which the camera server is running (!) and the path starts from the camera server path (!)options
105 -The typical location of the camera server is /export/doocs/server/camera_server/. . if you put "./" in the field Camera Directory. the images in the camera_server directory. It is better to have a separate directory as subfolder like "CameraImages". on some computers this is already installed.
123 +== saving images ==
124 +
125 +The tool writes images of either bmp or an image depemdent format to the specified folder. The folder is on the computer on which the camera server is running (!) and the path starts from the camera server path (!)options
126 +The typical location of the camera server is /export/doocs/server/camera_server/. . if you put "./" in the field Camera Directory. the images in the camera_server directory. It is better to have a separate directory as subfolder like "CameraImages". on some computers this is already installed.
106 106  Another aproach is to write the files to a home directory. One may put e.g. "/home/vuvfuser/CameraImages/" in the Camera Directory to save on the home directory.
107 107  
108 108  * aquire single images: just press "writing once"
... ... @@ -111,34 +111,8 @@
111 111  
112 112  note that youor login has to have the permissions to write in the specified field!
113 113  
135 +\\
114 114  
115 -== Saving images in the DAQ ==
116 -
117 -To save the cameras in the DAQ the server has to have a sender and they have to be "registered" in the DAQ. if this is one one can activate the saving by activating "images"
118 -
119 -[[image:attach:image2023-3-2_14-45-0.png||thumbnail="true" height="250"]]
120 -
121 -if the timing of the sender is not configured correctly it often occurs that the images are saved by one bunch ID "too late"  (-1 has to be substracted by the bunch ID of the camera). one can finetune the sending by optimizing the USR1 time.
122 -
123 -Depending on the binning, bit depth, image size the correct USR1 setting may be different. but typically 40-80 is a good number
124 -
125 -[[image:attach:image2023-3-2_14-48-51.png||height="250"]]
126 -
127 -one can check the mismatch easily by comparing the GMD and the integrated counts on the camera. here an example for USR1 time = 0. (for USR1 >= 20 the correlation is present without bunch ID shift )
128 -
129 -[[image:attach:image2023-3-7_13-49-59.png||thumbnail="true" height="400" width="341"]]
130 -
131 -Here a report where the image saving in the DAQ is investigated in more detail:
132 -
133 -{{view-file att--filename="Report-K.Kharitonov-05.09.2017.pdf"}}{{/view-file}}
134 -
135 - and a more recent "studies"
136 -
137 -{{view-file att--filename="statistic_2023_2.pdf" height="250"/}}
138 -
139 -{{view-file att--filename="Camera_bunchID_shift_V2023_3.pdf" height="250"/}}
140 -
141 -
142 142  == Installing new cameras ==
143 143  
144 144  To install an additional camera to a DOOCS camera server perform the following steps:
... ... @@ -148,7 +148,7 @@
148 148  
149 149  [[image:attach:Clipboardadd_camera.jpg||height="400"]]
150 150  
151 -*
146 +*
152 152  ** use action: add
153 153  ** chose FCT code (812 in our case)
154 154  ** add name
... ... @@ -158,6 +158,7 @@
158 158  
159 159  [[image:attach:screenshot.png||height="400"]]
160 160  
156 +\\
161 161  
162 162  1. First you'll have to open the camera location overview from the watchdog panel
163 163  1*. Enable the camera you wanna edit. If the check mark can't be enabled, you can't talk to the camera.
... ... @@ -172,6 +172,7 @@
172 172  
173 173  While the camera is running one can go to the WD -> locations -> properties ... and then change the NAME to the desired one (NO SPACE CARACTERS IN THE NAME !!!) and press enter ... thats it
174 174  
171 +\\
175 175  
176 176  == special topics ==
177 177  
... ... @@ -180,12 +180,14 @@
180 180  * it is important that the values for negative offset are 0. otherwise the subtraction does not work (experimental finding by Stefan ...) . For the Basler A311 cameras the mode has to be 5 . for mode 7 the Background subtraction does not work... (no resources left)
181 181  * 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-subtraction in jddd.
182 182  
180 +\\
181 +
183 183  ==== Power Over Ethernet ====
184 184  
185 185  ==== Triggering ====
186 186  
187 187  * it is important for the ace cameras that the trigger is 7 µs long. when it was accidentally switched to 0.7 µs the a311 were still triggering while the ace were NOT !!
188 -* [[BLCamTrigOverview>>doc:FS-FLASH USER tmp.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]]
187 +* [[BLCamTrigOverview>>doc:FLASHUSER.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]]
189 189  
190 190  ==== Restarting Servers ====
191 191  
... ... @@ -196,8 +196,9 @@
196 196  ))).
197 197  * Calling (% class="WYSIWYG_TT" %)//doocs start camera_server// (%%)will include the
198 198  
199 -//{{code language="none"}}PRE_START{{/code}} //script, which is by default set to (% class="WYSIWYG_TT" %)///export/doocs/server/script/reload_CAMERA_Server// (%%).
200 -
198 +{{code language="none"}}
199 +PRE_START
200 +{{/code}}// //script, which is by default set to (% class="WYSIWYG_TT" %)///export/doocs/server/script/reload_CAMERA_Server// (%%).
201 201  * You can also use the (% class="WYSIWYG_TT" %)//!restart!//(%%)button from watchdog server overview. This will execute (% class="WYSIWYG_TT" %)///export/doocs/server/script/reload_CAMERA_server //(%%)directly.
202 202  * The (% class="WYSIWYG_TT" %)//reload_CAMERA_server s//(%%)cript will usually:
203 203  ** Stop capturing on all cameras (optional)
... ... @@ -206,27 +206,38 @@
206 206  ** Restore a default configuration (optional)
207 207  ** Start the camera_server
208 208  
209 +\\
210 +
209 209  == FAQs ==
210 210  
211 211  1. //How can I save some images?// you can save images of the camera locally on the computer you are running jddd by clicking the right mouse button and use "save as png..."
212 212  1. //How can I save many images?// goto camera "control" -> "Write images" - a new window opens. With this you can save images (set best to BMP) with timestamp to the computer on which the camera server is running !! (hasftunnelcam1). here the directory in which it safes is : hasftunnelcam1: /export/doocs/server/camera_server/images (if you have the standard setting "./images/" in the directory field). you can get the images with e.g. (% class="twikiNewLink" %)WinSCP(%%). See also help in the "write images" window for more info.
213 213  1. //No images are shown / no update - what to do?// Check if the camera is on (right upper part: Images. the checkbox should be green). If not activate the check box. if this is on but the frames are not counting the trigger might be off. you can check this going to
214 -1. //The cameraserver is unavailable - what to do? See Restarting Server//
216 +1. //The cameraserver is unavailable - what to do? See Restarting Server
217 +//
215 215  
216 216  == Troubleshooting ==
217 217  
218 218  === Individual camera manuals ===
219 219  
220 -* [[SpectrometerPCOManual>>doc:FS-FLASH USER tmp.jddd-linked help pages.FLASH1 Tunnel Spectrometer.Things to know about the FLASH1 Spectrometer PCO.WebHome]]
223 +* [[SpectrometerPCOManual>>doc:FLASHUSER.jddd-linked help pages.FLASH1 Tunnel Spectrometer.Things to know about the FLASH1 Spectrometer PCO.WebHome]]
221 221  
222 222  == Cameras used in the FLASH photon diagnostic ==
223 223  
224 224  * [[Basler ace GigE Users Manual>>attach:Basler_ace_GigE_Users_Manual.pdf]]
225 225  
229 +\\
230 +
226 226  * [[ Prosilika User_Manual.pdf>>attach:700013A_-_GE1350_User_Manual.pdf]]
227 227  
233 +\\
234 +
228 228  * [[Basler A311f user manual .pdf>>attach:Basler_A311f.pdf]]
229 229  
237 +\\
238 +
230 230  * [[PCO user manual.pdf>>attach:PCO.pdf]]
231 231  
241 +\\
242 +
232 232  * Link to PCO status Sept 2015
700013A_-_GE1350_User_Manual.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -374.4 KB
Content
Basler_A311f.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content
Basler_ace_GigE_Users_Manual.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -3.6 MB
Content
Camera_bunchID_shift_V2023_3.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -179.6 KB
Content
Clipboardadd_camera.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -29.8 KB
Content
PCO.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -557.0 KB
Content
Report-K.Kharitonov-05.09.2017.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -627.2 KB
Content
image2019-9-19_12-26-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -35.3 KB
Content
image2019-9-19_12-28-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -53.4 KB
Content
image2019-9-19_12-29-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -131.2 KB
Content
image2019-9-19_12-29-44.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -56.9 KB
Content
image2019-9-19_12-34-54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -21.6 KB
Content
image2019-9-19_12-38-46.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -128.6 KB
Content
image2019-9-19_12-40-57.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -338.8 KB
Content
image2019-9-19_12-59-37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -5.6 KB
Content
image2019-9-19_13-2-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -51.2 KB
Content
image2019-9-19_15-3-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -322.3 KB
Content
image2019-9-19_15-4-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -154.9 KB
Content
image2019-9-19_15-5-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -404.2 KB
Content
image2019-9-24_16-1-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -526.6 KB
Content
image2019-9-24_16-3-48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -732.0 KB
Content
image2023-3-2_14-45-0.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image2023-3-2_14-48-51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image2023-3-7_13-49-59.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -61.1 KB
Content
screenshot.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -440.6 KB
Content
statistic_2023_2.pdf
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.rangeadm
Size
... ... @@ -1,1 +1,0 @@
1 -168.9 KB
Content