TWiki> LHCb Web>LHCbRICH>JRichEcControl (revision 9)EditAttachPDF

JRichEcControl GUI


JRichEcControl, JRichEcConfigurator and JRichTBTrigger are all part of the RICHECKIT package. Click the link to download it. Move the .tgz file to the location you wish to install the files, then unpack it using:

tar xzf RICHECKIT.tgz

You should then check that execution permission is set on the feb-proxy program. The packaging utility sometimes removes this permission.

After installing the RICHECKIT, change directory to the installation area and run the GUI as follows:

PATH=$PATH:./ java -Djava.library.path=./ -jar JRichEcControl.jar

ALERT! The following step is a prerequisite that you need to do before you can successfully operate the data acquistion but it should only be done for the first installation as it will overwrite any customisations you have done to your preferences.

Go to the Main menu and select Import. Locate the file RICH-CLARO-PD.xml that should be in the place where you installed the package and click Open to load the contents. Repeat this until you have imported the following files:

File name Description
RICH-CLARO-PD.xml CLARO hardware channel maps
RICH-MAROC3-PD.xml MAROC3 hardware channel maps
RICH-xy.xml Configurator xy to anode map
Chimaera2.xml Known Chimaera2 boards
configuratorLabels.xml Configurator label customisations

You should then exit and restart JRichEcControl.

Expert DAQ

The Expert DAQ panel is opened from Settings->Expert DAQ. The MAC address and IP address that are shown in the panel should correspond to the ethernet port on the DAQ PC. These addresses can be set in the JRichEcConfigurator through the Settings->PC network... panel, and should not need to be changed once the system is configured.

During beamtests, the number of MEP events per ethernet packet was increased to reduce the network packet loss. The optimal setting is probably the maximum number of events that will fit in a single Ethernet fragment. In this firmware the fragment buffer is around 1kb so up to about 16 events per MEP is optimal.

DB pulser

The settings for the internal pulser on the digital boards are controlled via the Settings->DB pulser... panel. The textfield Pulse count sets the total number of pulses generated on the DB. The Pulse delay is in units of DB clock ticks. Generally, for setups using the trigger board to distribute triggers, it is better to use the trigger board to generate pulser triggers rather than the internal DB pulser.

Threshold/Testpulse(DAC) scan

Threshold/Testpulse(DAC) scans can be launched from the Settings->Threshold/Testpulse(DAC) scan panel, which asks for the number of events per threshold setting, as well as the range of thresholds and increment size (which can be negative). The threshold or testpulse scan is started from the corresponding Threshold scan or Testpulse scan button. To record the scan, the Recording checkbox in the JRichEcControl panel should be ticked, but the Start and Stop buttons on the JRichEcControl panel should not be used to control the scan.

In case the scan gets stuck, use Interrupt to clean up before you can continue with a new scan or other new run.


JRichEcConfigurator allows you to manage settings for both CLARO-based or MAROC-based systems. How these are used depends on the run control program. Typically you can ignore the settings for the MAROC if you are working with the standard CLARO-based EC. The FEB system can be selected in the JRichEcControl panel using Settings->FEB type->CLARO/MAROC3.

Chimaera2 reference manual

For more details on how to set up the hardware and software please read the Chimaera2 reference manual.

-- FlorisKeizer - 2015-07-24

Edit | Attach | Watch | Print version | History: r12 < r11 < r10 < r9 < r8 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r9 - 2015-09-23 - StephenWotton
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback