Last modified by sndueste on 2024/03/13 14:17
From version 9.1
edited by sndueste
on 2019/09/24 16:04
Change comment: There is no comment for this version
To version 8.1
edited by sndueste
on 2019/09/19 15:21
Change comment: There is no comment for this version

Summary

Details

Page properties
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.