Changes for page Manual for the DOOCS camera server
Last modified by sndueste on 2024/03/13 14:17
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.snd ueste1 +XWiki.sendels - Content
-
... ... @@ -1,63 +1,34 @@ 1 1 (% class="twikiTocTitle" %)Contents: 2 2 3 -\\ 3 +* general Camera info 4 +* Camera server general info 5 +* scaling the image / spectra 6 +* Spectra (line outs) and Gaussian fits 7 +* working with ROIs 8 +* saving images 9 +* Installing new cameras 10 +* Renaming cameras 11 +* special topics 12 +** 13 +*** Background subtraction: 14 +*** Power Over Ethernet 15 +*** Triggering 16 +*** Restarting Servers 17 +* FAQs 18 +* Troubleshooting 19 +** Individual camera manuals 20 +* Cameras used in the FLASH photon diagnostic 4 4 5 - 6 - 7 -{{toc/}} 8 - 9 -== General Camera info == 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. 12 - 13 -The details of the available control parameters depends on the camera type. here is a typical view of 14 - 15 15 \\ 16 16 17 -the Standard view: the controls view: and the Expert view with all available control features 18 - 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 - 21 21 \\ 22 22 23 - \\26 +== general Camera info == 24 24 25 - ==Troubble shooting/Restartingthe camera server ==28 +there are several cameras that are watched if they have the correct rep rate and if not the server is restarted every 15 min. here is the list of these cameras [[https:~~/~~/ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=FlashCamerasToWatch~[~[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=FlashCamerasToWatch||shape="rect"]] 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:** 28 - 29 -* **There is no trigger connected to the camera → check with trying to run the camera untriggered ...** 30 -* **the server has problems -> restart the server.** 31 - 32 -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. 33 - 34 -1. Best to make a screenshot (in expert mode) to the logbook before restarting in case parameter settings are lost ... 35 -1. goto WDserver and press restart. The camera panel will go red and will come back after about 20 seconds ... 36 - 37 -[[image:attach:image2019-9-24_16-1-16.png||height="400"]] 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. 42 - 43 -\\ 44 - 45 -[[image:attach:image2019-9-24_16-3-48.png||height="400"]] 46 - 47 -\\ 48 - 49 -\\ 50 - 51 -== Monitoring system == 52 - 53 -we implemented a monitoring system for the important beamline cameras in FLASH1 and FLASH2. 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 !! 56 - 57 -The warning is also shown inn the according control panels for the cameras. 58 - 59 -[[image:attach:image2019-9-19_12-26-21.png||height="250"]] [[image:attach:image2019-9-19_12-34-54.png||height="250"]] 60 - 61 61 == Camera server general info == 62 62 63 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"]] ... ... @@ -68,46 +68,16 @@ 68 68 69 69 == scaling the image / spectra == 70 70 71 - [[image:attach:image2019-9-19_12-40-57.png||height="250"]][[image:attach:image2019-9-19_12-59-37.png||height="167"]]42 +\\ 72 72 73 -one can scale the image with a different scale as pixel. the center as well as the "pixel size" can be set. 74 - 75 75 == Spectra (line outs) and Gaussian fits == 76 76 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 - 79 79 \\ 80 80 81 -[[image:attach:image2019-9-19_15-3-23.png||height="400"]] 82 - 83 -"Spectrum" of the whole image. this can lead to a wrong fitting ... 84 - 85 -\\ 86 - 87 -\\ 88 - 89 -[[image:attach:image2019-9-19_15-5-29.png||height="400"]] 90 - 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 - 93 -\\ 94 - 95 -\\ 96 - 97 -[[image:attach:image2019-9-19_15-4-20.png||height="250"]] 98 - 99 -For some cameras we also have dedicated Beam profile viewers. 100 - 101 -\\ 102 - 103 -\\ 104 - 105 105 == working with ROIs == 106 106 107 107 To create more ROIs one has to do the following: 108 108 109 -[[image:attach:image2019-9-19_13-2-26.png||height="400"]] 110 - 111 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 cameraserver. ... ... @@ -141,7 +141,7 @@ 141 141 * Open the Jddd watchdog panel for the server ((% class="twikiNewLink" %)WatchdogOverview(%%).xml). goto camera server -> locations 142 142 * right upper part is a button Divice 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]]85 +[[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/Clipboardadd_camera.jpg||alt="Clipboardadd_camera.jpg" width="455" height="408"]] 145 145 146 146 * 147 147 ** use action: add ... ... @@ -149,9 +149,9 @@ 149 149 ** add name 150 150 ** press send 151 151 152 -the you see the new camera in the location table. do not forget to click "Cfg. restore" in the cameraexpert panel once everything looks o.k. with the camera ( otherwise the cameras may switch with their names ...)93 +the you see the new camera in the location table. do ot forget to click "Cfg. restore" in the camer expert pannel onece 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]]95 +[[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/screenshot.png||alt="screenshot.png" width="1490" height="950"]] 155 155 156 156 \\ 157 157 ... ... @@ -175,7 +175,7 @@ 175 175 ==== Background subtraction: ==== 176 176 177 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 cquisition before you can enable the background-substraction in jddd.119 +* For Basler ethernet camera's the offset needs to be zero in anycase, otherwise the server will crash. Also note, you have to make a reference image, that you have to stop/start the image aquisition before you can enable the background-substraction in jddd. 179 179 180 180 \\ 181 181 ... ... @@ -184,7 +184,7 @@ 184 184 ==== Triggering ==== 185 185 186 186 * 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 !! 187 -* [[BLCamTrigOverview>>doc:FLASH.Docu of the BL camera trigger system based on MTCA]] 128 +* [[BLCamTrigOverview>>doc:FLASHUSER.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]] 188 188 189 189 ==== Restarting Servers ==== 190 190 ... ... @@ -216,6 +216,8 @@ 216 216 1. //The cameraserver is unavailable - what to do? See Restarting Server 217 217 // 218 218 160 +\\ 161 + 219 219 == Troubleshooting == 220 220 221 221 === Individual camera manuals === ... ... @@ -222,21 +222,23 @@ 222 222 223 223 * [[SpectrometerPCOManual>>doc:FLASHUSER.jddd-linked help pages.FLASH1 Tunnel Spectrometer.Things to know about the FLASH1 Spectrometer PCO.WebHome]] 224 224 168 +\\ 169 + 225 225 == Cameras used in the FLASH photon diagnostic == 226 226 227 -* [[Basler ace GigE Users Manual>> attach:Basler_ace_GigE_Users_Manual.pdf]]172 +* [[Basler ace GigE Users Manual>>url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/Basler_ace_GigE_Users_Manual.pdf||shape="rect"]] 228 228 229 229 \\ 230 230 231 -* [[ attach:700013A_-_GE1350_User_Manual.pdf]]176 +* [[Prosilika User_Manual.pdf>>url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/700013A_-_GE1350_User_Manual.pdf||shape="rect"]] 232 232 233 233 \\ 234 234 235 -* [[Basler A311f user manual .pdf>> attach:Basler_A311f.pdf]]180 +* [[Basler A311f user manual .pdf>>url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/Basler_A311f.pdf||shape="rect"]] 236 236 237 237 \\ 238 238 239 -* [[PCO user manual.pdf>> attach:PCO.pdf]]184 +* [[PCO user manual.pdf>>url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/PCO.pdf||shape="rect"]] 240 240 241 241 \\ 242 242