Skip to Content
Last modified by sndueste on 2025/04/23 17:34
From version 8.1
edited by sndueste
on 2019/09/19 15:21
Change comment: There is no comment for this version
To version 12.1
edited by sendels
on 2021/02/10 15:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sndueste
1 +XWiki.sendels
Content
... ... @@ -20,6 +20,34 @@
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 +
23 23  == Monitoring system ==
24 24  
25 25  we implemented a monitoring system for the important beamline cameras in FLASH1 and FLASH2.
... ... @@ -113,7 +113,7 @@
113 113  * Open the Jddd watchdog panel for the server ((% class="twikiNewLink" %)WatchdogOverview(%%).xml). goto camera server -> locations
114 114  * right upper part is a button Divice control
115 115  
116 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/Clipboardadd_camera.jpg~|~|alt="Clipboardadd_camera.jpg" width="455" height="408"~]~]>>attach:Clipboardadd_camera.jpg]]
144 +[[image:attach:Clipboardadd_camera.jpg||height="400"]]
117 117  
118 118  *
119 119  ** use action: add
... ... @@ -123,7 +123,7 @@
123 123  
124 124  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 ...)
125 125  
126 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/screenshot.png~|~|alt="screenshot.png" width="1490" height="950"~]~]>>attach:screenshot.png]]
154 +[[image:attach:screenshot.png||height="400"]]
127 127  
128 128  \\
129 129  
... ... @@ -156,7 +156,7 @@
156 156  ==== Triggering ====
157 157  
158 158  * 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 !!
159 -* [[BLCamTrigOverview>>doc:FLASH.Docu of the BL camera trigger system based on MTCA]]
187 +* [[BLCamTrigOverview>>doc:FLASHUSER.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]]
160 160  
161 161  ==== Restarting Servers ====
162 162