Last modified by sndueste on 2025-09-08 15:36

From version 20.1
edited by sndueste
on 2020-03-19 09:38
Change comment: There is no comment for this version
To version 16.1
edited by sndueste
on 2020-01-17 13:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -189,8 +189,8 @@
189 189  
190 190  === Configuring the DAQ monitor ===
191 191  
192 -The DAQ monitor ( and the Offline monitor) can be configured using DAQdataGUI.
193 -Load a test run containing all relevant properties. Select all properties you want to monitor. Use {{code language="none"}}Tools -> Channels to DAQMonitor{{/code}} and choose your DAQ. This sends a list with the selected properties to the DAQ monitor of your system.
192 +The DAQ monitor ( and the Offline monitor) can be confgured using DAQdataGUI.
193 +Load a test run containing all relavant propoerties. Select all properties you want to monitor. Use {{code language="none"}}Tools -> Channels to DAQMonitor{{/code}} and choose your DAQ. This sends a list with the selected properties to the DAQ monitor of your system.
194 194  [[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/daq_monitor_config.png~|~|alt="daq_monitor_config.png" width="700" height="390"~]~]>>attach:daq_monitor_config.png]]
195 195  
196 196  \\
... ... @@ -325,12 +325,12 @@
325 325  ** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
326 326  
327 327  
328 -\\//**Here in more detail:**//
328 +\\*Here in more detail:*
329 329  
330 330  \\
331 331  
332 332  * 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.
333 -** **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"**
333 +** 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 (Aug 2018) 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"}}jFLASH{{/code}} command. Click on "Photons" -> Experimental Hall "Photons main panel"
334 334  ** The DAQ "expert" panel can be reached from the User DAQ control panel.
335 335  [[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_expert.jpg~|~|alt="DAQ_expert.jpg" width="400" height="350"~]~]>>attach:DAQ_expert.jpg]]
336 336  
... ... @@ -365,6 +365,7 @@
365 365  
366 366  *
367 367  ** 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)
368 +[[image:url:http://confluence.desy.de/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_US&version=2]]
368 368  ** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
369 369  ** finally you have to select your White list and start a run ...
370 370  
... ... @@ -380,7 +380,7 @@
380 380  
381 381  ----
382 382  
383 -== [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]] ==
384 +[[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]]
384 384  
385 385  === Re-read the data base ===
386 386  
... ... @@ -403,17 +403,3 @@
403 403  {{code language="none"}}"expert" -> "Run Control Commands" -> "Re-init SHM"{{/code}}
404 404  
405 405  Now close the RCGUI and start it again. Switch to the tab "subsystems", wait for the subsystems to be reloaded and load the whitelist you want to use.
406 -
407 -\\
408 -
409 -=== data base errors ===
410 -
411 -The red flags next to the  different stream indicators tell something about data base errors
412 -
413 -[[image:url:https://mail.desy.de/service/home/~~/?auth=co&loc=de&id=154203&part=2.2||width="788" height="140"]]
414 -
415 -upper flag:  There was a problem to read run catalogue
416 -
417 -lower flag: There was a problem to read dccp catalogue.
418 -
419 -In both cases there are counters of failures to read a catalogue. If this counter is not incrementing with every attempt to read a catalogue, then it's no problem. It can be monitored and reset in the panel that one gets by pressing on "green" area.