Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 23.1
edited by cpassow
on 2021-02-10 12:43
Change comment: There is no comment for this version
To version 25.1
edited by sndueste
on 2021-02-10 15:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cpassow
1 +XWiki.sndueste
Content
... ... @@ -20,11 +20,12 @@
20 20  
21 21  === DAQ control panel ===
22 22  
23 -To get to the User DAQ control one has to go to {{code language="none"}}Experiment control{{/code}} -> {{code language="none"}}User DAQ tab{{/code}} -> {{code language="none"}}FLxUSERy DAQ CTRL{{/code}}
24 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/jddd_DAQ-control-manual-how_to_get.png~|~|alt="jddd_DAQ-control-manual-how_to_get.png" width="500" height="360"~]~]>>attach:jddd_DAQ-control-manual-how_to_get.png]]
23 +To get to the User DAQ control one has to go to {{code language="none"}}Experiment control{{/code}} -> {{code language="none"}}User DAQ tab{{/code}} -> {{code language="none"}}FLxUSERy DAQ CTRL{{/code}}
24 +
25 +[[image:attach:jddd_DAQ-control-manual-how_to_get.png||height="400"]]
25 25  \\The following window opens. Here the User DAQ can be started and stopped as well as the incoming data can be visualized, information about data rates and saved properties is presented as well as the panel is automatically printed in to the logbook:
26 26  
27 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/jddd_DAQ-control-manual2.png~|~|alt="jddd_DAQ-control-manual2.png" width="960" height="720"~]~]>>attach:jddd_DAQ-control-manual2.png]]
28 +[[image:attach:jddd_DAQ-control-manual2.png||height="400"]]
28 28  \\\\
29 29  
30 30  \\
... ... @@ -74,7 +74,8 @@
74 74  
75 75  To ultimately check if the correct data is saved one can use the DAQ data GUI to look at the saved raw. files.
76 76  
77 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQgui1.jpg~|~|alt="DAQgui1.jpg" width="500" height="350"~]~]>>attach:DAQgui1.jpg]][[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQgui2.jpg~|~|alt="DAQgui2.jpg" width="500" height="350"~]~]>>attach:DAQgui2.jpg]][[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/daqgui3.png~|~|alt="daqgui3.png" width="500" height="350"~]~]>>attach:daqgui3.png]]
78 +[[image:attach:daqgui3.png||height="250"]][[image:attach:DAQgui2.jpg||height="250"]][[image:attach:DAQgui1.jpg||height="250"]]
79 +
78 78  \\
79 79  
80 80  The DAQ Data GUI is a general tool to select and visualise data that was saved in the DAQ . It has in addition simple analysis options like histogram, mean, min or max values as function of time etc. Also correlations between different parameters can be analyzed in the tool. More details can be found [[How to Use the FLASH DAQ Data GUI?~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=FLASHDAQdataGUI||shape="rect"]] and [[ here (DAQdataGUI link collection) >>doc:FLASH.How to get the data out of the DAQ]]
... ... @@ -131,9 +131,9 @@
131 131  
132 132  === Configuring the DAQ ===
133 133  
136 +[[image:attach:RCGUI_2.jpg||height="400"]]
137 +\\
134 134  
135 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RCGUI_2.jpg~|~|alt="RCGUI_2.jpg" width="400" height="500"~]~]>>attach:RCGUI_2.jpg]]
136 -
137 137  Using the jddd DAQ control panel one can start and stop runs but in order to configure the DAQ which data to save one has to use a a separate *DAQ run control * java application. Since it needs write access to DOOCS internal file systems, which can not be made available elsewhere one has to start the system on our DOOCS control computers [[flashlxuser1.desy.de>>url:http://flashlxuser1.desy.de||shape="rect"]]{{code language="none"}}{{/code}} or [[flashlxuser2.desy.de>>url:http://flashlxuser2.desy.de||shape="rect"]]{{code language="none"}}{{/code}}.
138 138  Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via X-Win32 from windows or via ssh from Linux machines.
139 139  Once logged in to {{code language="none"}}flashlxuser1{{/code}} or {{code language="none"}}flashlxuser2{{/code}} the DAQ run control can be started. Depending on the DAQ you want to use the commands are:
... ... @@ -177,10 +177,8 @@
177 177  
178 178  Which DAQ to use is decided by the FLASH DAQ team according to the beamtime schedule.
179 179  
180 -\\
182 +[[image:attach:RCGUI_properties.jpg||height="400"]]
181 181  
182 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RCGUI_properties.jpg~|~|alt="RCGUI_properties.jpg" width="503" height="311"~]~]>>attach:RCGUI_properties.jpg]]
183 -
184 184  \\
185 185  
186 186  Using the {{code language="none"}}Add{{/code}} and {{code language="none"}}Rem(ove){{/code}} buttons one can move the desired "subsystems" in the included side - meaning that they are saved. The "subsystems" contain typically several DOOCS parameters. E.g. {{code language="none"}}EXPERIMENT_MHZ_ADC_BL1{{/code}} contains all relevant DOOCS properties of the 4 MHZ ADC channels available at BL1. To get a detailled information about the saved parameters one can have a look to the "Show Properties in Subsystems" button . In addition, a list of all possible subsystems and their description can be found [[here>>doc:FLASHUSER.Configuring the user DAQs]].
... ... @@ -212,9 +212,8 @@
212 212  
213 213  === Load/Save the configuration ===
214 214  
215 +[[image:attach:whitelist.jpg||height="400"]]
215 215  
216 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/whitelist.jpg~|~|alt="whitelist.jpg" width="532" height="370"~]~]>>attach:whitelist.jpg]]
217 -
218 218  Once a list of subsystems is defined and tested this parameter combination should then be saved in a so-called //white list//. By loading this white list one can then easily configure the DAQ after changes / restarts ... to the initially defined settings to save the correct data.
219 219  The whitelist can be saved/loaded with the Run Control GUI by: {{code language="none"}}File -> Group White List -> Save/Load{{/code}}. Note, while the top left rectangle's background of time and date is yellow, don't try any further controls of the GUI, you might confuse the program. It is busy reading the configuration from the run control database. The background changes back to grey when it has finished.
220 220  \\The filename convention for the White Lists are arranged in the way:
... ... @@ -261,16 +261,13 @@
261 261  The jddd DAQ Control should be set up that it prints by default the relevant run information in the logbook associated to your beamline [[Logbooks>>doc:FLASH.Electronic Logbooks]]
262 262  
263 263  Define logbook / and whitelist for display in the jddd DAQ control (jddd otherwise does not "know" which White list was used ... this has to be put in by hand ...up to now)
264 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/setting_parameters.jpg~|~|alt="setting_parameters.jpg" width="500" height="300"~]~]>>attach:setting_parameters.jpg]]
265 265  
266 -\\
264 +[[image:attach:setting_parameters.jpg||height="400"]]
267 267  
268 268  \\
269 269  
270 270  \\
271 271  
272 -\\
273 -
274 274  == In case something goes wrong: Troubleshooting ==
275 275  
276 276  \\
... ... @@ -293,9 +293,11 @@
293 293  
294 294  === Data seems not properly saved ===
295 295  
292 +[[image:attach:RC_logfile.jpg||height="250"]]
296 296  
297 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RC_logfile.jpg~|~|alt="RC_logfile.jpg" width="518" height="300"~]~]>>attach:RC_logfile.jpg]]When checking the saved run with the (% class="twikiNewLink" %)DAQdataGUI(%%) it may happen that the property shows up in the data tree but no events are saved. Then (most likely) something is wrong with the sending of the data.
298 298  
295 + When checking the saved run with the (% class="twikiNewLink" %)DAQdataGUI(%%) it may happen that the property shows up in the data tree but no events are saved. Then (most likely) something is wrong with the sending of the data.
296 +
299 299  * A very helpful tool is the {{code language="none"}}RC logfile{{/code}}. in the RCGUI on the lower right side there is a button to start an editor with the log file. besides lots of standard entries there is usually also a hint on where to find the problem ...
300 300  * check if the device is working properly. Is it connected? Can you see data in jddd / DOOCS ? . If not you have to fix the DOOCS part ... DAQ can only save what is properly implemented in DOOCS.
301 301  * If camera images are not properly saved ( e.g. only "0"s in the image matrix or the DAQ sender can not be switched to "on") a **restart of the camera server** usually helps.
... ... @@ -329,24 +329,23 @@
329 329  * if the DAQ gets stuck in the starting or stopping procedure one can try to initialize the DAQ or in the worst case restart it.
330 330  ** **to be able to restart the DAQ one has to run jddd on the {{code language="none"}}flashlxuser1{{/code}} or {{code language="none"}}flashlxuser2{{/code}} (up to now ( 2020) the restat on our consoles (cons0...12) is NOT possible yet [[image:url:http://hasfweb.desy.de/pub/TWiki/SmiliesPlugin/frown.gif||alt="frown"]]) : log in at one of these machines with your beamline account (e.g. bl1user or fl24user). Start jddd with the {{code language="none"}}flash{{/code}} command. Click on "Photons" -> Experimental Hall "Photons main panel"**
331 331  ** The DAQ "expert" panel can be reached from the User DAQ control panel.
332 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_expert.jpg~|~|alt="DAQ_expert.jpg" width="400" height="350"~]~]>>attach:DAQ_expert.jpg]]
333 333  
331 + [[image:attach:DAQ_expert.jpg||height="400"]]
334 334  \\
335 335  
336 -\\
337 -
338 338  *
339 339  ** Then you see the following "DAQ expert panel":
340 340  ** first one may try the "all to INITIALIZE" button. it starts a script window and asks for the passwd (the beamline accounts (blxuser) should have the according rights. vuvfuser has it for sure. The script sets all subcomponents to initialize. It is helpful if one subcomponent got stuck.
341 341  
338 + [[image:attach:UserDAQ_status.jpg||height="400"]]
339 +\\
342 342  
343 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/UserDAQ_status.jpg~|~|alt="UserDAQ_status.jpg" width="500" height="400"~]~]>>attach:UserDAQ_status.jpg]]
344 -
345 345  \\
346 346  
347 347  * If this does not help you have to "re-start DAQ". This completely restarts all processes and takes a while. A script window appears and shows what steps are actually done. At the end is sais: "Cleanup finished".
348 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_restart_msg.jpg~|~|alt="DAQ_restart_msg.jpg" width="400" height="350"~]~]>>attach:DAQ_restart_msg.jpg]]
349 349  
345 + [[image:attach:DAQ_restart_msg.jpg||height="400"]]
346 +
350 350  \\
351 351  
352 352  * For the "re-start DAQ" the DAQ should come up in the same state as before. Meaning that the subsystems (ADCs, cameras ..) are still loaded and displayed. If this is not the case you can try to load your white list and start a new run. If the data is saved correctly you are done.
... ... @@ -356,10 +356,12 @@
356 356  * **IF the DAQ still does not work properly** the final option is the: "re-start DAQ (no RCSHM)". This button does the same as the "re-start DAQ" but the Run Controller shared memory is **not** re-stored. It means that after the DAQ is back no run configuration is selected.
357 357  ** in the jddd control the list of subsystems sais "empty"
358 358  ** in the RCGUI in the lower part it sais "RUN mode is not set"
359 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/restart_RCM_no_runmode.jpg~|~|alt="restart_RCM_no_runmode.jpg" width="400" height="400"~]~]>>attach:restart_RCM_no_runmode.jpg]]
360 360  
357 + [[image:attach:restart_RCM_no_runmode.jpg||height="400"]]
361 361  \\
362 362  
360 +\\
361 +
363 363  *
364 364  ** one has to go to the "Run Modes" tab and select the run mode {{code language="none"}}FLASH1_EXP{{/code}} by clicking on it and choose the desired file size (stored settings)
365 365  ** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
... ... @@ -415,8 +415,10 @@
415 415  
416 416  The red flags next to the  different stream indicators tell something about data base errors
417 417  
418 -[[image:url:https://mail.desy.de/service/home/~~/?auth=co&loc=de&id=154203&part=2.2||width="788" height="140"]]
417 +\\
419 419  
419 +[[image:attach:2021-02-10 15_23_20-How to save data in the User DAQ - FS-FLASH USER - DESY Confluence.png||width="600"]]
420 +
420 420  upper flag:  There was a problem to read run catalogue
421 421  
422 422  lower flag: There was a problem to read dccp catalogue.