Last modified by sndueste on 2024/03/13 14:17
From version 19.1
edited by sndueste
on 2023/04/24 13:32
Change comment: There is no comment for this version
To version 20.1
edited by sndueste
on 2024/03/13 14:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,5 @@
1 1  (% class="twikiTocTitle" %)Contents:
2 2  
3 -\\
4 4  
5 5  
6 6  
... ... @@ -12,19 +12,16 @@
12 12  
13 13  The details of the available control parameters depends on the camera type. here is a typical view of
14 14  
15 -\\
16 16  
17 17  the Standard view:                                                                                   the controls view:                                                                                                and the Expert view with all available control features
18 18  
19 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 20  
21 -\\
22 22  
23 -\\
24 24  
25 25  == Troubble shooting / Restarting the camera server ==
26 26  
27 -If there are problems occurring with the camera ( no image is shown, no update, camera server crashes ...) then it is** mainly 2 reasons:**
23 +If there are problems occurring with the camera ( no image is shown, no update, camera server crashes ...) then it is** mainly 2 reasons:**
28 28  
29 29  * **There is no trigger connected to the camera → check with trying to run the camera untriggered ...**
30 30  * **the server has problems -> restart the server.**
... ... @@ -36,17 +36,13 @@
36 36  
37 37  [[image:attach:image2019-9-24_16-1-16.png||height="400"]]
38 38  
39 -\\
40 40  
41 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 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.
42 42  
43 -\\
44 44  
45 45  [[image:attach:image2019-9-24_16-3-48.png||height="400"]]
46 46  
47 -\\
48 48  
49 -\\
50 50  
51 51  == Monitoring system ==
52 52  
... ... @@ -60,11 +60,10 @@
60 60  
61 61  == Camera server general info ==
62 62  
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"]]
55 +[[info from the DOOCS pages>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=Camera%20server||shape="rect"]]
64 64  
65 65  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
66 66  
67 -\\
68 68  
69 69  == scaling the image / spectra ==
70 70  
... ... @@ -76,31 +76,24 @@
76 76  
77 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 78  
79 -\\
80 80  
81 81  [[image:attach:image2019-9-19_15-3-23.png||height="400"]]
82 82  
83 83  "Spectrum" of the whole image. this can lead to a wrong fitting ...         
84 84  
85 -\\
86 86  
87 -\\
88 88  
89 89  [[image:attach:image2019-9-19_15-5-29.png||height="400"]]
90 90  
91 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 92  
93 -\\
94 94  
95 -\\
96 96  
97 97  [[image:attach:image2019-9-19_15-4-20.png||height="250"]]
98 98  
99 99  For some cameras we also have dedicated Beam profile viewers.
100 100  
101 -\\
102 102  
103 -\\
104 104  
105 105  == working with ROIs ==
106 106  
... ... @@ -108,22 +108,19 @@
108 108  
109 109  [[image:attach:image2019-9-19_13-2-26.png||height="400"]]
110 110  
111 -\\
112 112  
113 113  * 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.
114 114  * NOTE the file os owned by doocs adm. to edit it one can use (% class="twikiNewLink" %)WinSCP(%%) and log in as doocsadm.
115 115  
116 -\\
117 117  
118 118  * now all cameras have maximum ROIs. if you need less for some cameras read below:
119 119  * 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.
120 120  
121 -\\
122 122  
123 123  == saving images "locally" ==
124 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 +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
107 +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.
127 127  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.
128 128  
129 129  * aquire single images: just press "writing once"
... ... @@ -132,7 +132,6 @@
132 132  
133 133  note that youor login has to have the permissions to write in the specified field!
134 134  
135 -\\
136 136  
137 137  == Saving images in the DAQ ==
138 138  
... ... @@ -148,17 +148,18 @@
148 148  
149 149  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 )
150 150  
151 -[[image:attach:image2023-3-7_13-49-59.png||thumbnail="true" height="250"]]
131 +[[image:attach:image2023-3-7_13-49-59.png||thumbnail="true" height="400" width="341"]]
152 152  
153 153  Here a report where the image saving in the DAQ is investigated in more detail:
154 154  
155 -{{view-file att--filename="Report-K.Kharitonov-05.09.2017.pdf" height="250"/}} and a more recent "studies"
135 +{{view-file att--filename="Report-K.Kharitonov-05.09.2017.pdf"}}{{/view-file}}
156 156  
137 + and a more recent "studies"
138 +
157 157  {{view-file att--filename="statistic_2023_2.pdf" height="250"/}}
158 158  
159 159  {{view-file att--filename="Camera_bunchID_shift_V2023_3.pdf" height="250"/}}
160 160  
161 -\\
162 162  
163 163  == Installing new cameras ==
164 164  
... ... @@ -169,7 +169,7 @@
169 169  
170 170  [[image:attach:Clipboardadd_camera.jpg||height="400"]]
171 171  
172 -*
153 +*
173 173  ** use action: add
174 174  ** chose FCT code (812 in our case)
175 175  ** add name
... ... @@ -179,7 +179,6 @@
179 179  
180 180  [[image:attach:screenshot.png||height="400"]]
181 181  
182 -\\
183 183  
184 184  1. First you'll have to open the camera location overview from the watchdog panel
185 185  1*. Enable the camera you wanna edit. If the check mark can't be enabled, you can't talk to the camera.
... ... @@ -194,7 +194,6 @@
194 194  
195 195  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
196 196  
197 -\\
198 198  
199 199  == special topics ==
200 200  
... ... @@ -203,7 +203,6 @@
203 203  * 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)
204 204  * 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.
205 205  
206 -\\
207 207  
208 208  ==== Power Over Ethernet ====
209 209  
... ... @@ -221,9 +221,8 @@
221 221  ))).
222 222  * Calling (% class="WYSIWYG_TT" %)//doocs start camera_server// (%%)will include the
223 223  
224 -{{code language="none"}}
225 -PRE_START
226 -{{/code}}// //script, which is by default set to (% class="WYSIWYG_TT" %)///export/doocs/server/script/reload_CAMERA_Server// (%%).
202 +//{{code language="none"}}PRE_START{{/code}} //script, which is by default set to (% class="WYSIWYG_TT" %)///export/doocs/server/script/reload_CAMERA_Server// (%%).
203 +
227 227  * 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.
228 228  * The (% class="WYSIWYG_TT" %)//reload_CAMERA_server s//(%%)cript will usually:
229 229  ** Stop capturing on all cameras (optional)
... ... @@ -232,7 +232,6 @@
232 232  ** Restore a default configuration (optional)
233 233  ** Start the camera_server
234 234  
235 -\\
236 236  
237 237  == FAQs ==
238 238  
... ... @@ -239,8 +239,7 @@
239 239  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..."
240 240  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.
241 241  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
242 -1. //The cameraserver is unavailable - what to do? See Restarting Server
243 -//
218 +1. //The cameraserver is unavailable - what to do? See Restarting Server//
244 244  
245 245  == Troubleshooting ==
246 246  
... ... @@ -252,18 +252,14 @@
252 252  
253 253  * [[Basler ace GigE Users Manual>>attach:Basler_ace_GigE_Users_Manual.pdf]]
254 254  
255 -\\
256 256  
257 257  * [[ Prosilika User_Manual.pdf>>attach:700013A_-_GE1350_User_Manual.pdf]]
258 258  
259 -\\
260 260  
261 261  * [[Basler A311f user manual .pdf>>attach:Basler_A311f.pdf]]
262 262  
263 -\\
264 264  
265 265  * [[PCO user manual.pdf>>attach:PCO.pdf]]
266 266  
267 -\\
268 268  
269 269  * Link to PCO status Sept 2015