Last modified by sndueste on 2024/03/13 14:17
From version 12.1
edited by sendels
on 2021/02/10 15:10
Change comment: There is no comment for this version
To version 7.1
edited by sndueste
on 2019/09/19 13:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sendels
1 +XWiki.sndueste
Content
... ... @@ -20,34 +20,6 @@
20 20  
21 21  \\
22 22  
23 -\\
24 -
25 -== Troubble shooting / Restarting the camera server ==
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 -\\
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 51  == Monitoring system ==
52 52  
53 53  we implemented a monitoring system for the important beamline cameras in FLASH1 and FLASH2.
... ... @@ -74,34 +74,10 @@
74 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 85  \\
86 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:
... ... @@ -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:attach:Clipboardadd_camera.jpg||height="400"]]
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]]
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:attach:screenshot.png||height="400"]]
102 +[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/screenshot.png~|~|alt="screenshot.png" width="1490" height="950"~]~]>>attach:screenshot.png]]
155 155  
156 156  \\
157 157  
... ... @@ -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:FLASHUSER.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]]
135 +* [[BLCamTrigOverview>>doc:FLASH.Docu of the BL camera trigger system based on MTCA]]
188 188  
189 189  ==== Restarting Servers ====
190 190