| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
sweeper_daq_tools [2017/07/06 18:20]
pereira [CCUSB and/or VMUSB claimed by existing programs] |
sweeper_daq_tools [2017/07/07 13:01] (current)
pereira [Level-3 Trigger GUI] |
| |
| ==== Level-3 Trigger GUI ==== | ==== Level-3 Trigger GUI ==== |
| The Level-3 trigger GUI gets started by clicking the button ''Launch Level3 Trigger GUI''. It can be used to select the trigger mode: (1) Sweeper standalone [Sweeper data are processed when there is a Sweeper trigger, typically coming from the Thin left-up PMT (''thin_LU'') of the FP scintillator]; (2) Sweeper singles (Sweeper, MoNA and LISA data are processed whenever there is a Sweeper trigger); and (3) Coincidence Sweeper (Sweeper, MoNA and LISA data are processed whenever there is a coincidence between the Sweeper and MoNA/LISA triggers). | The Level-3 trigger GUI gets started by clicking the button ''Launch Level3 Trigger GUI''. It can be used to select the trigger mode: (1) **Sweeper standalone** [Sweeper data are processed when there is a Sweeper trigger, typically coming from the Thin left-up PMT (''thin_LU'') of the FP scintillator]; (2) **Sweeper singles** (Sweeper, MoNA and LISA data are processed whenever there is a Sweeper trigger); and (3) **Coincidence Sweeper** (Sweeper, MoNA and LISA data are processed whenever there is a coincidence between the Sweeper and MoNA/LISA triggers). |
| |
| {{:wiki:l3gui-start.png|L3 GUI}} | {{:wiki:l3gui-start.png|L3 GUI}} |
| In order to set this module you must: | In order to set this module you must: |
| |
| * Select one of the three possible trigger configurations. | * Select one of the three possible trigger configurations. IMPORTANT NOTE: When running the Sweeper DAQ in standalone mode always select **Sweeper standalone**. When running in Slave mode with MoNA/LISA, you can use either **Sweeper singles** or **Coincidence Sweeper** |
| * Go to the tab ''FPGA Configure''. If the VME crate was power cycled you will need to load the firmware by clicking ''Load'' | * Go to the tab ''FPGA Configure''. If the VME crate was power cycled you will need to load the firmware by clicking ''Load'' |
| * In the tab ''FPGA Configure'', verify that the Coincidence Gate is set to the value 38 {{:wiki:l3gui-fpga.png|L3 GUI FPGA control}} | * In the tab ''FPGA Configure'', verify that the Coincidence Gate is set to the value 38 {{:wiki:l3gui-fpga.png|L3 GUI FPGA control}} |
| * Select the option "always record" | * Select the option "always record" |
| |
| * Click again on the tab ''multilogger'' and select "enable loggers". A window will pop out with a list of ring-buffers that can be muti-logged {{:wiki:multilogger.png|Multilogger window}} | * Click again on the tab ''multilogger'' and select "enable loggers". A window will pop out with a list of ring-buffers that can be muti-logged {{:wiki:multilogger-sweeper.png|Multilogger window}} |
| |
| * Check out ''sweeper'' to enable recording data from this ring buffer | * Check out ''sweeper'' to enable recording data from this ring buffer |
| - If this didn't help, contact the Device Physicist | - If this didn't help, contact the Device Physicist |
| ==== Manual rebooting ==== | ==== Manual rebooting ==== |
| In the rare case that the RunControl GUI gets "frozen", it is possible to reboot the whole system manually. This operation requires to turn off the VME and CAMAC crates, and the spdaq computer, all them located in the rack seating near the FP box in the S3 vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq. | In the rare case that the RunControl GUI gets "frozen", it is possible to reboot the whole system manually. This operation requires to turn off the VME and CAMAC crates, and the spdaq computer, all them located in the rack seating near the FP box in the Sweeper vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq. PLEASE, contact the Device Physicist before trying this last-resource operation. |
| |
| |
| |
| |
