Last modified by sndueste on 2024/03/13 14:17
From version 11.1
edited by sndueste
on 2019/10/29 11:21
Change comment: There is no comment for this version
To version 16.1
edited by sndueste
on 2023/03/02 14:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -38,7 +38,7 @@
38 38  
39 39  \\
40 40  
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.
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 43  \\
44 44  
... ... @@ -52,9 +52,9 @@
52 52  
53 53  we implemented a monitoring system for the important beamline cameras in FLASH1 and FLASH2.
54 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 !!
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 56  
57 -The warning is also shown inn the according control panels for the cameras.
57 +The warning is also shown in the according control panels for the cameras.
58 58  
59 59  [[image:attach:image2019-9-19_12-26-21.png||height="250"]] [[image:attach:image2019-9-19_12-34-54.png||height="250"]]
60 60  
... ... @@ -110,7 +110,7 @@
110 110  
111 111  \\
112 112  
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 cameraserver.
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 116  \\
... ... @@ -120,7 +120,7 @@
120 120  
121 121  \\
122 122  
123 -== saving images ==
123 +== saving images "locally" ==
124 124  
125 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 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.
... ... @@ -128,20 +128,38 @@
128 128  
129 129  * aquire single images: just press "writing once"
130 130  * aquire a defined number of images: put the number of images in the "count" field and press enter.
131 -* 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
131 +* 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
132 132  
133 133  note that youor login has to have the permissions to write in the specified field!
134 134  
135 135  \\
136 136  
137 +== Saving images in the DAQ ==
138 +
139 +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"
140 +
141 +[[image:attach:image2023-3-2_14-45-0.png||thumbnail="true" height="250"]]
142 +
143 +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.
144 +
145 +Depending on the binning, bit depth, image size the correct USR1 setting may be different. but typically 80 is a good number
146 +
147 +[[image:attach:image2023-3-2_14-48-51.png||height="250"]]
148 +
149 +Here a report where the image saving in the DAQ is investigated in more detail:
150 +
151 +{{view-file att--filename="Report-K.Kharitonov-05.09.2017.pdf" height="250"/}}
152 +
153 +\\
154 +
137 137  == Installing new cameras ==
138 138  
139 139  To install an additional camera to a DOOCS camera server perform the following steps:
140 140  
141 141  * Open the Jddd watchdog panel for the server ((% class="twikiNewLink" %)WatchdogOverview(%%).xml). goto camera server -> locations
142 -* right upper part is a button Divice control
160 +* right upper part is a button Device control
143 143  
144 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/Clipboardadd_camera.jpg~|~|alt="Clipboardadd_camera.jpg" width="455" height="408"~]~]>>attach:Clipboardadd_camera.jpg]]
162 +[[image:attach:Clipboardadd_camera.jpg||height="400"]]
145 145  
146 146  *
147 147  ** use action: add
... ... @@ -151,7 +151,7 @@
151 151  
152 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 ...)
153 153  
154 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/screenshot.png~|~|alt="screenshot.png" width="1490" height="950"~]~]>>attach:screenshot.png]]
172 +[[image:attach:screenshot.png||height="400"]]
155 155  
156 156  \\
157 157  
... ... @@ -174,8 +174,8 @@
174 174  
175 175  ==== Background subtraction: ====
176 176  
177 -* 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)
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.
195 +* 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)
196 +* 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.
179 179  
180 180  \\
181 181