Changes for page Manual for the DOOCS camera server

Last modified by sndueste on 2024/03/13 14:17

From 7.1 to 6.1 From 17.1 to 16.1

From version 16.1

edited by sndueste
on 2023/03/02 14:56

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

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -20,41 +20,13 @@
  \\
--\\
--
--== Troubble shooting / Restarting the camera server ==
--
--If there are problems occurring with the camera ( no image is shown, no update, camera server crashes ...) then it is** mainly 2 reasons:**
--
--* **There is no trigger connected to the camera → check with trying to run the camera untriggered ...**
--* **the server has problems -> restart the server.**
--
--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.
--
--1.  Best to make a screenshot (in expert mode) to the logbook before restarting in case parameter settings are lost ...
--1. goto WDserver and press restart. The camera panel will go red and will come back after about 20 seconds ...
--
--[[image:attach:image2019-9-24_16-1-16.png||height="400"]]
--
--\\
--
--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.
--
--\\
--
--[[image:attach:image2019-9-24_16-3-48.png||height="400"]]
--
--\\
--
--\\
--
  == Monitoring system ==
  we implemented a monitoring system for the important beamline cameras in FLASH1 and FLASH2.
--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 !!
++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 !!
--The warning is also shown in the according control panels for the cameras.
++The warning is also shown inn the according control panels for the cameras.
  [[image:attach:image2019-9-19_12-26-21.png||height="250"]]    [[image:attach:image2019-9-19_12-34-54.png||height="250"]]
@@ -74,34 +74,10 @@
  == Spectra (line outs) and Gaussian fits ==
--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 ...
--
  \\
--[[image:attach:image2019-9-19_15-3-23.png||height="400"]]
--
--"Spectrum" of the whole image. this can lead to a wrong fitting ...
--
  \\
--\\
--
--[[image:attach:image2019-9-19_15-5-29.png||height="400"]]
--
--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!
--
--\\
--
--\\
--
--[[image:attach:image2019-9-19_15-4-20.png||height="250"]]
--
--For some cameras we also have dedicated Beam profile viewers.
--
--\\
--
--\\
--
  == working with ROIs ==
  To create more ROIs one has to do the following:
@@ -110,7 +110,7 @@
  \\
--* 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.
++* 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.
  * NOTE the file os owned by doocs adm. to edit it one can use (% class="twikiNewLink" %)WinSCP(%%) and log in as doocsadm.
  \\
@@ -120,7 +120,7 @@
  \\
--== saving images "locally" ==
++== saving images ==
  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
  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,38 +128,20 @@
  * aquire single images: just press "writing once"
  * aquire a defined number of images: put the number of images in the "count" field and press enter.
--* 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
++* 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
  note that youor login has to have the permissions to write in the specified field!
  \\
--== Saving images in the DAQ ==
--
--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"
--
--[[image:attach:image2023-3-2_14-45-0.png||thumbnail="true" height="250"]]
--
--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.
--
--Depending on the binning, bit depth, image size the correct USR1 setting may be different. but typically 80 is a good number
--
--[[image:attach:image2023-3-2_14-48-51.png||height="250"]]
--
--Here a report where the image saving in the DAQ is investigated in more detail:
--
--{{view-file att--filename="Report-K.Kharitonov-05.09.2017.pdf" height="250"/}}
--
--\\
--
  == Installing new cameras ==
  To install an additional camera to a DOOCS camera server perform the following steps:
  * Open the Jddd watchdog panel for the server ((% class="twikiNewLink" %)WatchdogOverview(%%).xml). goto camera server -> locations
--* right upper part is a button Device control
++* right upper part is a button Divice control
--[[image:attach:Clipboardadd_camera.jpg||height="400"]]
++[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/Clipboardadd_camera.jpg~|~|alt="Clipboardadd_camera.jpg" width="455" height="408"~]~]>>attach:Clipboardadd_camera.jpg]]
  *
  ** use action: add
@@ -169,7 +169,7 @@
  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 ...)
--[[image:attach:screenshot.png||height="400"]]
++[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/CameraServerManual/screenshot.png~|~|alt="screenshot.png" width="1490" height="950"~]~]>>attach:screenshot.png]]
  \\
@@ -192,8 +192,8 @@
  ==== Background subtraction: ====
--* 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)
--* 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.
++* 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)
++* 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.
  \\
@@ -202,7 +202,7 @@
  ==== Triggering ====
  * 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 !!
--* [[BLCamTrigOverview>>doc:FLASHUSER.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]]
++* [[BLCamTrigOverview>>doc:FLASH.Docu of the BL camera trigger system based on MTCA]]
  ==== Restarting Servers ====

Changes for page Manual for the DOOCS camera server

Summary

Details

Applications

Navigation