TWiki> LHCb Web>LHCbRICH>RichUpgrade>RichComLab (revision 4)EditAttachPDF
This page contains information on how to configure the system and to take data in the ComLab.

Setup the system from scratch

Switch on the file server storerich01.
Switch on the chiller for the MARATON power supply and for the Kanga Box (SysLab) and SSB1 (ComLab).
Switch on the MARATON and CAEN power supplies.
Switch on the MiniDAQ (lbminidaq2-13) and the pcie40 server (lbrichpcie40-00). In case of a power cut, these two machines automatically startup. However, in order for things to be properly configured, send a poweroff command and switch them on again.
Once storerich01 is pinging, switch on pcsyslab02, pcsyslab03 and pclhcb33.
Check if the /home/WinCC folder is mounted on pcsyslab02 and lbrichpcie40-00. If not, mount it on both machines.
Follow the instructions at to setup the MiniDAQ2.
From pcsyslab02, ssh to lbrichpcie40-00.
Open the GBT server log with sudo pcie40_systemd -l.
Load the pcie40 cards firmwares with pcie40_program -n Firmware/<nameOfTheFirmware.sof>. is lab004 (SOL40), lab010 (TELL40) and lab018 (TELL40). is written on /etc/daq40.cfg. Load the firmware following the order lab004, lab010, lab018. (If the loading of the firmwares fails: sudo poweroff lbrichpcie40-00. You can switch on again typing on the web. Help: p40acceptance.)
On pcsyslab02 open a terminal and type startPA.
Run MultiMiniDAQ on workspace 6.
Run the Wiener and CAEN OPC servers on workspace 7 (use the corresponding scripts under /home/lbrich/OpcUa/, where is Wiener or CAEN).
Run R2HV1 on workspace 8.
Run R2DCS1 on workspace 9.
Run RIECS1 on workspace 10.
Open the D&N of MultiMiniDAQ, FSM tab, Open the MiniDAQ FSM and restart RICH2_DCS and RICH_HV FSMs.
On the main operations panel, press the FW Versions... button. Press Configure under config PLLs in the following order: lab004, lab010, lab018. Press Configure GBTs with the same order.
Restart the Ctrl Managers.
Browse to TFC->SOL40->sol40_004 to make disappear the SOL40 links not declared in the SOL40 firmware.
Run the elmb project on pclhcb33. Run the CAN OPC server with ~/OpcUa/ELMB/ Open and start the RICH_SAFETY FSM.
Exclude RICH_HV and RICH_DCS (Currently the HV and DCS states/commands are not implemented in the top partition).

Please respect the following workspaces convention if developing stuff on pcsyslab02:
6: MultiMiniDAQ project
7: Wiener and CAEN OPC servers
8: HV project
9: DCS project
10: ECS project
11: Safety FSM

WinCC projects

Run Control: MultiMiniDAQ (project folder on storerich01, running on pcsyslab02).
HV: R2HV1 (project folder on storerich01, running on pcsyslab02).
DCS: R2DCS1 (project folder on storerich01, running on pcsyslab02).
Safety: elmb (project folder and running on pclhcb33).

Shortcuts to open the GEDI are available under the local folder /home/lbrich/WinCC

Open the FSM


Power the frontend

Click on RICH_DCS. Take the partition by clicking on the lock. Issue a Switch_ON command. From the Power Supplies Overview in the top operations panel, you should see the LV channel switching on with voltage of 8.0 V and current around 8 A.

Power the MaPMTs in PHYSICS mode

Click on RICH_HV. Take the partition by clicking on the lock. Issue a Go_STANDBY1 command (Select the PHYSICS mode when asked for). Wait few minutes. Issue a Go_READY command. Open the power supplies overview to check everything is green (colour calculated depending on the expected current drawn by a baseboard in the dark, taking into account the tolerance of the voltage dividers).

Configure the frontend

Browse to DAQ->R2A_DAQ_FE and send a Configure command. The current of the LV goes up to 13.1 A when everything is configured properly.

Check the frontend is properly configured

DAQ->R2A_DAQ_FE->R2A_DAQ_FE_COL00. Enable the calibration pattern. Browse down to the corresponding TELL40s (tell40_10_0 for the upper half of the column, tell40_18_0 for the lower half of the column), move to the monitoring tab. Enable the loop monitoring and check if the calibration pattern (9F everywhere) is there.

How to find the latency

Ensure that the 840120 address of the TELL40s in the LBUS tab of the GBT client is set to 00001000. Browse to DAQ->R2A_DAQ_FE. Select action: DAC scan. Threshold 7. Start Step: 255. Enable the Step Run with 1 step and click START_RUN. This allows to switch on the DAC at the maximum level on all the frontend channels. On the TFC quick control panel, set the limit to 10000 (it allows to acquire around 3 orbits, 1 orbit being 3564). Enable the random trigger source with rate 40078 (the exact rate of the LHC) and Calib A with periodicity 1. Disable the TAE. Press Configure Links and enable at most 4 links per TELL40. Take a run. Data are written under the /data folder of lbrichpcie40-00. Open the raw files with daq40_frgreader and search for a F by using \F. Sign down the BXID where you have the signal (be careful to not confuse it with the EvtID). Take the difference deltaT between this number and 3087 (the bxid values writtein next to the Calib A text field in the TFC quick control panel). Convert the value of (3564-deltaT) in hex and set it for both TELL40s in the 840120 address of the TELL40s in the LBUS tab of the GBT client (the format i 00001XYZ where XYZ is the hex number).

How to acquire data with the laser

Turn the laser on (turn the driver key). Exclude the DATAFLOW partition, check that the Enable in the Step Run box is not ticked and click Apply. Click on TFC quick control in the TFC box, a panel will open where you have to make sure that the box Limited is not ticked and the box Calib A is ticked. Click Apply and close the TFC panel. Click CONFIGURE from the top, followed by a a START_RUN and a GO action. You will see the number of triggers increasing in the Triggers from TFC box. Check the laser driver box where you should be able to now see the red light corresponding to the emission ON. Always make sure that in the top of the RICH partition the state of RICH_HV is READY: if the Subdetector Type was not set correctly this could cause a trip of the HV and consequently the RICH_HV state to go into ERROR.
If the laser is not emitting (i.e. the display on the Kintex evaluation board used to control the laser is empty), use the following procedure:
- log in the Windows7 pclbtb05;
- browse to Documents/LaserPulser/programmerv2.20180116 and launch the exe Jar file;
- press the Scan button (it should find GBTx 1);
- press the Import button and select the golden file located in Documents/LaserPulser/;
- read (state goes to PauseForConfig), write, read (state goes to Idle);
- check that the display is showing oX-00h (X=0,1,2,3);
- open the GBT client->select GBT->!I2C (lbminidaq2-06,GBTid=4,SCA=0,BUS=0,Address=33,Type=GBTx,frequency=100k,SLC=Open Drain,Size=4,write 00000003)
-check that o3 register is 03 on the display, i.e. o3-03h and repeat the procedure at the beginning of this subsection.

BXID offset and Data Links alignment

To change the BXID offset: open the GBT client (Communication: Local, LBUS tab). Select the server corresponding to the TELL40 partition, Address: 840120. Type: 32 bits. Size: 1. Press Read. Copy paste the the Data Out in the Data In field. Change it accordingly (the + shift the readout window to left, the - shift the readout window to the right. Data stay where they are).
Look at hslotpixel histogram of a run with TAE enabled (you need to process it without OR, ./ is fine). Check that the majority of events are in the same bin on the y axis. If not, you need to identify the correct link (each bunch on the x axis corresponds to a data link) that is not aligned with the others.
On the GBT client, on the LBUS tab (size 1). For each address, each nibble corresponds to a link (increasing from right to left).
Address 840100: first six digits to the right are TFC links (from 0 to 5), the following 2 digits are data links 6,7.
Address 840104: data links from 8 to 15 (from right to the left).
Address 840108: data links from 16 to 23.

To move the bunches higher in the hslotpixel, you need to reduce the digit in the corresponding nibble.

How to take a run

Click on TFC quick control. Enabled Limited and set the number of events. Enable Calib A with periodicity 1 (1 pulse per orbit) or Fast Calib A with periodicity 4000 divided by the number of pulses per orbit you want (e.g. 400 if you want a pulse rate of 100 kHz). Enable or disable the TAE. Historically we used a TAE half window of 11, corresponding to 23 consecutive time slots around the BXID where the signal should sit when the right latency has been found. If you want to deliver N pulses to the column, you need to set the number of events to N x ((TAE half window) x 2 +1).

How to take a scan

DAQ->R2A_DAQ_FE. Select threshold or DAC scan and set the corresponding parameters. Click apply. On the top operations panel, enable the Step Run. Set the appropriate parameters.

How to process data

Move to the $offline folder in lbrichpcie40-00.
Process a single run: use .\ , where is the run number you have in the top operations panel, is (TAE half window x 2) +1 and is whatever character you want if you want to show the offline display.
Process a scan: use .\ , where is the run number you have in the top operations panel, is (TAE half window x 2) +1, is the start value you set under DAQ->R2A_DAQ_FE, depends on the number of steps, and is whatever character you want if you want to show the offline display.

-- GiovanniCavallero - 2019-08-13

Edit | Attach | Watch | Print version | History: r12 | r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2019-09-03 - GiovanniCavallero
    • 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.
Ideas, requests, problems regarding TWiki? Send feedback