Last modified by sndueste on 2024/03/13 14:17
From version 7.1
edited by sndueste
on 2019/09/19 13:23
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
Tags
... ... @@ -1,0 +1,1 @@
1 +favourite
Content
... ... @@ -1,6 +1,5 @@
1 1  (% class="twikiTocTitle" %)Contents:
2 2  
3 -\\
4 4  
5 5  
6 6  
... ... @@ -8,35 +8,55 @@
8 8  
9 9  == General Camera info ==
10 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.
10 +**several [[different camera types>>url:https://confluence.desy.de/display/MCS/DOOCS+Camera+Server||shape="rect"]] can be easily integrated into DOOCS. **
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  
20 +
21 +== Troubble shooting / Restarting the camera server ==
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:**
24 +
25 +* **There is no trigger connected to the camera → check with trying to run the camera untriggered ...**
26 +* **the server has problems -> restart the server.**
27 +
28 +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.
29 +
30 +1. Best to make a screenshot (in expert mode) to the logbook before restarting in case parameter settings are lost ...
31 +1. goto WDserver and press restart. The camera panel will go red and will come back after about 20 seconds ...
32 +
33 +[[image:attach:image2019-9-24_16-1-16.png||height="400"]]
34 +
35 +
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 +
38 +
39 +[[image:attach:image2019-9-24_16-3-48.png||height="400"]]
40 +
41 +
42 +
23 23  == Monitoring system ==
24 24  
25 25  we implemented a monitoring system for the important beamline cameras in FLASH1 and FLASH2.
26 26  
27 -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 !!
47 +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 !!
28 28  
29 -The warning is also shown inn the according control panels for the cameras.
49 +The warning is also shown in the according control panels for the cameras.
30 30  
31 31  [[image:attach:image2019-9-19_12-26-21.png||height="250"]] [[image:attach:image2019-9-19_12-34-54.png||height="250"]]
32 32  
33 33  == Camera server general info ==
34 34  
35 -[[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"]]
36 36  
37 37  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
38 38  
39 -\\
40 40  
41 41  == scaling the image / spectra ==
42 42  
... ... @@ -46,10 +46,27 @@
46 46  
47 47  == Spectra (line outs) and Gaussian fits ==
48 48  
49 -\\
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 ...
50 50  
51 -\\
52 52  
71 +[[image:attach:image2019-9-19_15-3-23.png||height="400"]]
72 +
73 +"Spectrum" of the whole image. this can lead to a wrong fitting ...         
74 +
75 +
76 +
77 +[[image:attach:image2019-9-19_15-5-29.png||height="400"]]
78 +
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 +
81 +
82 +
83 +[[image:attach:image2019-9-19_15-4-20.png||height="250"]]
84 +
85 +For some cameras we also have dedicated Beam profile viewers.
86 +
87 +
88 +
53 53  == working with ROIs ==
54 54  
55 55  To create more ROIs one has to do the following:
... ... @@ -56,42 +56,65 @@
56 56  
57 57  [[image:attach:image2019-9-19_13-2-26.png||height="400"]]
58 58  
59 -\\
60 60  
61 -* 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 cameraserver.
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.
62 62  * NOTE the file os owned by doocs adm. to edit it one can use (% class="twikiNewLink" %)WinSCP(%%) and log in as doocsadm.
63 63  
64 -\\
65 65  
66 66  * now all cameras have maximum ROIs. if you need less for some cameras read below:
67 67  * 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.
68 68  
69 -\\
70 70  
71 -== saving images ==
104 +== saving images "locally" ==
72 72  
73 -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
74 -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.
75 75  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.
76 76  
77 77  * aquire single images: just press "writing once"
78 78  * aquire a defined number of images: put the number of images in the "count" field and press enter.
79 -* aquire many images. pressing the countinously writing button starts the writing and stops when you press the stop button or the harddisk is 95% full
112 +* aquire many images. pressing the continuously writing button starts the writing and stops when you press the stop button or the hard drive is 95% full
80 80  
81 81  note that youor login has to have the permissions to write in the specified field!
82 82  
83 -\\
84 84  
117 +== Saving images in the DAQ ==
118 +
119 +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"
120 +
121 +[[image:attach:image2023-3-2_14-45-0.png||thumbnail="true" height="250"]]
122 +
123 +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.
124 +
125 +Depending on the binning, bit depth, image size the correct USR1 setting may be different. but typically 40-80 is a good number
126 +
127 +[[image:attach:image2023-3-2_14-48-51.png||height="250"]]
128 +
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 +
131 +[[image:attach:image2023-3-7_13-49-59.png||thumbnail="true" height="400" width="341"]]
132 +
133 +Here a report where the image saving in the DAQ is investigated in more detail:
134 +
135 +{{view-file att--filename="Report-K.Kharitonov-05.09.2017.pdf"}}{{/view-file}}
136 +
137 + and a more recent "studies"
138 +
139 +{{view-file att--filename="statistic_2023_2.pdf" height="250"/}}
140 +
141 +{{view-file att--filename="Camera_bunchID_shift_V2023_3.pdf" height="250"/}}
142 +
143 +
85 85  == Installing new cameras ==
86 86  
87 87  To install an additional camera to a DOOCS camera server perform the following steps:
88 88  
89 89  * Open the Jddd watchdog panel for the server ((% class="twikiNewLink" %)WatchdogOverview(%%).xml). goto camera server -> locations
90 -* right upper part is a button Divice control
149 +* right upper part is a button Device control
91 91  
92 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/Clipboardadd_camera.jpg~|~|alt="Clipboardadd_camera.jpg" width="455" height="408"~]~]>>attach:Clipboardadd_camera.jpg]]
151 +[[image:attach:Clipboardadd_camera.jpg||height="400"]]
93 93  
94 -*
153 +*
95 95  ** use action: add
96 96  ** chose FCT code (812 in our case)
97 97  ** add name
... ... @@ -99,9 +99,8 @@
99 99  
100 100  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 ...)
101 101  
102 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/screenshot.png~|~|alt="screenshot.png" width="1490" height="950"~]~]>>attach:screenshot.png]]
161 +[[image:attach:screenshot.png||height="400"]]
103 103  
104 -\\
105 105  
106 106  1. First you'll have to open the camera location overview from the watchdog panel
107 107  1*. Enable the camera you wanna edit. If the check mark can't be enabled, you can't talk to the camera.
... ... @@ -116,16 +116,14 @@
116 116  
117 117  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
118 118  
119 -\\
120 120  
121 121  == special topics ==
122 122  
123 123  ==== Background subtraction: ====
124 124  
125 -* 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)
126 -* 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.
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 +* 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.
127 127  
128 -\\
129 129  
130 130  ==== Power Over Ethernet ====
131 131  
... ... @@ -132,7 +132,7 @@
132 132  ==== Triggering ====
133 133  
134 134  * 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 !!
135 -* [[BLCamTrigOverview>>doc:FLASH.Docu of the BL camera trigger system based on MTCA]]
191 +* [[BLCamTrigOverview>>doc:FLASHUSER.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]]
136 136  
137 137  ==== Restarting Servers ====
138 138  
... ... @@ -143,9 +143,8 @@
143 143  ))).
144 144  * Calling (% class="WYSIWYG_TT" %)//doocs start camera_server// (%%)will include the
145 145  
146 -{{code language="none"}}
147 -PRE_START
148 -{{/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 +
149 149  * 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.
150 150  * The (% class="WYSIWYG_TT" %)//reload_CAMERA_server s//(%%)cript will usually:
151 151  ** Stop capturing on all cameras (optional)
... ... @@ -154,7 +154,6 @@
154 154  ** Restore a default configuration (optional)
155 155  ** Start the camera_server
156 156  
157 -\\
158 158  
159 159  == FAQs ==
160 160  
... ... @@ -161,8 +161,7 @@
161 161  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..."
162 162  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.
163 163  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
164 -1. //The cameraserver is unavailable - what to do? See Restarting Server
165 -//
218 +1. //The cameraserver is unavailable - what to do? See Restarting Server//
166 166  
167 167  == Troubleshooting ==
168 168  
... ... @@ -174,18 +174,14 @@
174 174  
175 175  * [[Basler ace GigE Users Manual>>attach:Basler_ace_GigE_Users_Manual.pdf]]
176 176  
177 -\\
178 178  
179 179  * [[ Prosilika User_Manual.pdf>>attach:700013A_-_GE1350_User_Manual.pdf]]
180 180  
181 -\\
182 182  
183 183  * [[Basler A311f user manual .pdf>>attach:Basler_A311f.pdf]]
184 184  
185 -\\
186 186  
187 187  * [[PCO user manual.pdf>>attach:PCO.pdf]]
188 188  
189 -\\
190 190  
191 191  * Link to PCO status Sept 2015
700013A_-_GE1350_User_Manual.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +374.4 KB
Content
Basler_A311f.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
Basler_ace_GigE_Users_Manual.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +3.6 MB
Content
Camera_bunchID_shift_V2023_3.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +179.6 KB
Content
Clipboardadd_camera.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +29.8 KB
Content
PCO.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +557.0 KB
Content
Report-K.Kharitonov-05.09.2017.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +627.2 KB
Content
image2019-9-19_12-26-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +35.3 KB
Content
image2019-9-19_12-28-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +53.4 KB
Content
image2019-9-19_12-29-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +131.2 KB
Content
image2019-9-19_12-29-44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +56.9 KB
Content
image2019-9-19_12-34-54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +21.6 KB
Content
image2019-9-19_12-38-46.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +128.6 KB
Content
image2019-9-19_12-40-57.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +338.8 KB
Content
image2019-9-19_12-59-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +5.6 KB
Content
image2019-9-19_13-2-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +51.2 KB
Content
image2019-9-19_15-3-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +322.3 KB
Content
image2019-9-19_15-4-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +154.9 KB
Content
image2019-9-19_15-5-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +404.2 KB
Content
image2019-9-24_16-1-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +526.6 KB
Content
image2019-9-24_16-3-48.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +732.0 KB
Content
image2023-3-2_14-45-0.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
image2023-3-2_14-48-51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +27.9 KB
Content
image2023-3-7_13-49-59.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +61.1 KB
Content
screenshot.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +440.6 KB
Content
statistic_2023_2.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +168.9 KB
Content