Skip to Content
Last modified by sndueste on 2025/04/23 17:34
From version 20.2
edited by rangeadm
on 2025/02/13 08:01
Change comment: Update document after refactoring.
To version 20.4
edited by sndueste
on 2025/04/23 14:28
Change comment: Renamed back-links.

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -FS-FLASH USER tmp.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).WebHome
1 +FS-FLASH USER tmp.Controls (DOOCS, jDDD,\.\.\.).WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rangeadm
1 +XWiki.sndueste
Content
... ... @@ -96,11 +96,9 @@
96 96  * 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.
97 97  * NOTE the file os owned by doocs adm. to edit it one can use (% class="twikiNewLink" %)WinSCP(%%) and log in as doocsadm.
98 98  
99 -
100 100  * now all cameras have maximum ROIs. if you need less for some cameras read below:
101 101  * Set the required number of ROIs for every camera in the property ROIS.NUM in the configuration file. The way how it's done is the following. On the camera server re-start xxx number of ROIS will be created for every camera. But after reading the configuration file the non-required ROIS will removed for every camera separately according to ROIS.NUM.
102 102  
103 -
104 104  == saving images "locally" ==
105 105  
106 106  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
... ... @@ -182,13 +182,12 @@
182 182  * 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)
183 183  * 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.
184 184  
185 -
186 186  ==== Power Over Ethernet ====
187 187  
188 188  ==== Triggering ====
189 189  
190 190  * 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 !!
191 -* [[BLCamTrigOverview>>doc:FLASHUSER.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]]
188 +* [[BLCamTrigOverview>>doc:FS-FLASH USER tmp.jddd-linked help pages.FLASH beamline camera docu.Docu of the BL camera trigger system based on MTCA.WebHome]]
192 192  
193 193  ==== Restarting Servers ====
194 194  
... ... @@ -209,7 +209,6 @@
209 209  ** Restore a default configuration (optional)
210 210  ** Start the camera_server
211 211  
212 -
213 213  == FAQs ==
214 214  
215 215  1. //How can I save some images?// you can save images of the camera locally on the computer you are running jddd by clicking the right mouse button and use "save as png..."
... ... @@ -227,14 +227,10 @@
227 227  
228 228  * [[Basler ace GigE Users Manual>>attach:Basler_ace_GigE_Users_Manual.pdf]]
229 229  
230 -
231 231  * [[ Prosilika User_Manual.pdf>>attach:700013A_-_GE1350_User_Manual.pdf]]
232 232  
233 -
234 234  * [[Basler A311f user manual .pdf>>attach:Basler_A311f.pdf]]
235 235  
236 -
237 237  * [[PCO user manual.pdf>>attach:PCO.pdf]]
238 238  
239 -
240 240  * Link to PCO status Sept 2015