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

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,6 @@
1 1  (% class="twikiTocTitle" %)Contents:
2 2  
3 +\\
3 3  
4 4  
5 5  
... ... @@ -11,16 +11,19 @@
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,19 +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 +\\
99 99  
100 100  * now all cameras have maximum ROIs. if you need less for some cameras read below:
101 101  * 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.
102 102  
121 +\\
103 103  
104 104  == saving images "locally" ==
105 105  
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.
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.
108 108  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.
109 109  
110 110  * aquire single images: just press "writing once"
... ... @@ -113,6 +113,7 @@
113 113  
114 114  note that youor login has to have the permissions to write in the specified field!
115 115  
135 +\\
116 116  
117 117  == Saving images in the DAQ ==
118 118  
... ... @@ -128,18 +128,17 @@
128 128  
129 129  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 )
130 130  
131 -[[image:attach:image2023-3-7_13-49-59.png||thumbnail="true" height="400" width="341"]]
151 +[[image:attach:image2023-3-7_13-49-59.png||thumbnail="true" height="250"]]
132 132  
133 133  Here a report where the image saving in the DAQ is investigated in more detail:
134 134  
135 -{{view-file att--filename="Report-K.Kharitonov-05.09.2017.pdf"}}{{/view-file}}
155 +{{view-file att--filename="Report-K.Kharitonov-05.09.2017.pdf" height="250"/}} and a more recent "studies"
136 136  
137 - and a more recent "studies"
138 -
139 139  {{view-file att--filename="statistic_2023_2.pdf" height="250"/}}
140 140  
141 141  {{view-file att--filename="Camera_bunchID_shift_V2023_3.pdf" height="250"/}}
142 142  
161 +\\
143 143  
144 144  == Installing new cameras ==
145 145  
... ... @@ -150,7 +150,7 @@
150 150  
151 151  [[image:attach:Clipboardadd_camera.jpg||height="400"]]
152 152  
153 -*
172 +*
154 154  ** use action: add
155 155  ** chose FCT code (812 in our case)
156 156  ** add name
... ... @@ -160,6 +160,7 @@
160 160  
161 161  [[image:attach:screenshot.png||height="400"]]
162 162  
182 +\\
163 163  
164 164  1. First you'll have to open the camera location overview from the watchdog panel
165 165  1*. Enable the camera you wanna edit. If the check mark can't be enabled, you can't talk to the camera.
... ... @@ -174,6 +174,7 @@
174 174  
175 175  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
176 176  
197 +\\
177 177  
178 178  == special topics ==
179 179  
... ... @@ -182,6 +182,7 @@
182 182  * 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)
183 183  * 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.
184 184  
206 +\\
185 185  
186 186  ==== Power Over Ethernet ====
187 187  
... ... @@ -199,8 +199,9 @@
199 199  ))).
200 200  * Calling (% class="WYSIWYG_TT" %)//doocs start camera_server// (%%)will include the
201 201  
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 -
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// (%%).
204 204  * 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.
205 205  * The (% class="WYSIWYG_TT" %)//reload_CAMERA_server s//(%%)cript will usually:
206 206  ** Stop capturing on all cameras (optional)
... ... @@ -209,6 +209,7 @@
209 209  ** Restore a default configuration (optional)
210 210  ** Start the camera_server
211 211  
235 +\\
212 212  
213 213  == FAQs ==
214 214  
... ... @@ -215,7 +215,8 @@
215 215  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..."
216 216  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.
217 217  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
218 -1. //The cameraserver is unavailable - what to do? See Restarting Server//
242 +1. //The cameraserver is unavailable - what to do? See Restarting Server
243 +//
219 219  
220 220  == Troubleshooting ==
221 221  
... ... @@ -227,14 +227,18 @@
227 227  
228 228  * [[Basler ace GigE Users Manual>>attach:Basler_ace_GigE_Users_Manual.pdf]]
229 229  
255 +\\
230 230  
231 231  * [[ Prosilika User_Manual.pdf>>attach:700013A_-_GE1350_User_Manual.pdf]]
232 232  
259 +\\
233 233  
234 234  * [[Basler A311f user manual .pdf>>attach:Basler_A311f.pdf]]
235 235  
263 +\\
236 236  
237 237  * [[PCO user manual.pdf>>attach:PCO.pdf]]
238 238  
267 +\\
239 239  
240 240  * Link to PCO status Sept 2015