Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 35.3
edited by rangeadm
on 2025-02-21 11:48
Change comment: Update document after refactoring.
To version 35.4
edited by sndueste
on 2025-04-23 14:40
Change comment: Renamed back-links.

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rangeadm
1 +XWiki.sndueste
Content
... ... @@ -26,7 +26,7 @@
26 26  \\
27 27  
28 28  
29 -* By pressing the start and stop button, besides sending the commands to the DAQ the button prints the panel to the respective beamline / experiments logbook. Here you can later on keep track of the runs. Links to the Beamline logbooks can be found [[here>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.E-Logbooks.WebHome]].
29 +* By pressing the start and stop button, besides sending the commands to the DAQ the button prints the panel to the respective beamline / experiments logbook. Here you can later on keep track of the runs. Links to the Beamline logbooks can be found [[here>>doc:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.E-Logbooks.WebHome]].
30 30  * here a sample entry in the **logbook**. The run number, "run comment" and several other parameters are printed as (searchable) text in addition with the screenshot of the DAQ control to get all relevant data for this run in the logbook: [[image:attach:image2022-9-8_10-57-56.png||thumbnail="true" height="250"]]
31 31  * NOTE: After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
32 32  * NOTE: Each run has a unique run number. This number is needed to retrieve the data later on. So it is important to keep track which number is associated to what experimental parameters. Note that the run numbers are used by all FLASH DAQs (currently about 10). It might thus well be, that two consecutive runs from you do have run numbers which are spaced by more than one if another DAQ has been started in-between ...
... ... @@ -241,7 +241,7 @@
241 241  
242 242  === Setting the logbook to print in / putting the Whitelist name in jddd ===
243 243  
244 -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:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.E-Logbooks.WebHome]]
244 +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:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.E-Logbooks.WebHome]]
245 245  
246 246  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)
247 247  
... ... @@ -277,7 +277,6 @@
277 277  * Sometimes also a restart of the DAQ (see below) helps ... This however is more the case if the DAQ does not start at all or saves no data at all ...
278 278  * in several cases the reason is a configuration problem of the server. Then 2 servers are sending on the same "address". Then one property usually is saved without loss while the second one is only saved once in a while ( 1-5%). Here the server has to be fixed. As fast cure one can only exclude the less important subsystem and save the more important properly ...
279 279  
280 -
281 281  === Restarting the DAQ ===
282 282  
283 283  
... ... @@ -303,7 +303,7 @@
303 303  ==== **all to INITIALIZE** ====
304 304  
305 305  
306 -*
305 +* \\
307 307  ** First, one may try the "**all to INITIALIZE"** button. It starts a script window showing the progress of the initialization. The script sets all subcomponents to initialize. It is helpful if one subcomponent got stuck.
308 308  ** If there is no window coming up or closing right away there may be a problem with the rights. In this case you:
309 309  *** may try to login at the flashlxuser machines and try there again