Difference: RichSysLab (1 vs. 48)

Revision 482019-08-16 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 17 to 17
 Open the D&N of the sysLab project, FSM tab and open the MiniDAQ FSM.
Click on Restart Ctrl Managers.
On a terminal type config_fPLL.py \ No newline at end of file
Added:
>
>

Data taking

See https://twiki.cern.ch/twiki/bin/view/LHCb/RichComLab

WinCC projects

The run control is performed on pcsyslab03. The MiniDAQ and RICH_DAQ FSM are running on the SysLab project. The HV and LV power supplies, both provided by CAEN in the Kanga Box setup, is running on the powerSysLab project.

 \ No newline at end of file

Revision 472019-08-14 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 17 to 17
 Open the D&N of the sysLab project, FSM tab and open the MiniDAQ FSM.
Click on Restart Ctrl Managers.
On a terminal type config_fPLL.py
Deleted:
<
<

Install the project from scratch

Create a new WinCC project.
Copy the fwInstallation folder into the project folder and install the jcop fw components: fwCore, fwConfigurationDB, fwDIM and fwTrending.
Install the fwMiniDAQ component.
Open the MiniDAQ fsm, click on Configure Subscriptions, Configure Multi, delete existing devices, create the RICH_TELL40 type and apply the default settings for each device. Open the HW tool and create the TELL40_RICH device type using the appropriate xml. Also create the RICHPDMDB device type using the appropriate xml.
Define the other devices in the MiniDAQ FSM view and click on subscribe all. The click on the Create FSM button.
Install the fwRich component.
Open the fwRich_Configurator.pnl panel to create the new PDMDBs clicking on the Generate button.
Select the new devices in the table, select the firmwares, and click on the Update Selected button.
Click on the Generate FSM button.
Create the recipe DEFAULT/CONFIGURE in the hardware view tab.
Check that everything is ok within the fsm, i.e. try to take a run.
Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as distributed peers. (it is not needed if the config file is present in the fwRich.xml file)
Import the fwRichMiniDAQtop.dpl using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.

Add HV and DCS partitions to the MiniDAQ FSM

FSM view, configuration, Create/Configure FSM objects, Import from sys: (lbRichHV or lbRichDCS) and import RICH_HV and RICH_DCS accordingly to the selected system.
Right click on MiniDAQ partition, select Add Object(s) from FSM View, System(s) (select the system), and the type you want to add (RICH_HV or RICH_DCS), tick as Control Unit, click OK.
Generate FSM.
Change the type of MiniDAQ from MiniDAQtop to MiniDAQtopRICH.

OPC-UA servers

CAEN

You need to change _OPCUA_CAEN.Config.ConnInfo with the correct port that you can find by using sudo netstat -ltnp (there are two ports relative to the OPC server: one used to communicate with the crate, the other one in listening for the client). Useful documentation is here http://jcop.web.cern.ch/jcop-framework-caen-devices.

When creating devices in WinCC, use the simulation driver. Then run the OPC server and start the client. A message about certificates should appear in the logviewer. Go on SysMgm->Driver OPC->OPC UA Certificates. An entry in the Not Accepted text box should be present. Move the certificate to the Accepted box by using the arrow.

Go on SysMgm->Driver OPC->OPC UA Client->Manage (under subscriptions field). In Monitored items, select:
Use TimeStamp from: Server
Data change filter: Status,Value

CanOpen

Download the systec_can driver (systec_can-0.9.0p-12.cc76.x86_64.rpm) and reboot.
modprobe systec_can (in case of errors use insmod)
If dmesg complains about boot loader install systec_can-0.9.8p-3.cc76.x86_64.rpm
Install socketcan_utils-2920d417315f14397f683e5e368520421c8a9702.0.0-0.x86_64.rpm
Install OpcUaCanOpenServer-2.2.3-46cc7.x86_64.rpm
Install uaexpert-bin-centos7-x86_64-gcc4.8.2-v1.4.2-256.rpm (an opc-ua client)

The xml config file will be created when pressing create OPC config on the ELMB node in the WinCC project. Place the config file in the run directory for the ELMB OPC server.

If modprobe is not working: sudo insmod /usr/lib/modules/3.10.0-957/extra/systec_can.ko

Wiener

Add PDMDB ADC monitoring to the DCS project

On the machine running the DIM_DNS_server type

cat etc/sysconfig/dnsd
and add the line DIM_HOST_NODE=machineName.dyndns.cern.ch

Install the fwGbt and fwHw component. Add -dim_dns_node machineName.dyndns.cern.ch to the options for dim manager involving Gbt.
From the Hw tool panel, ADVANCED tab, click on XML file button and select the HWDescription_PDMDB(R,H)_ADC.xml file containing the ADC line registers. Click import. Click on Edit to check the script is reasonable. Click on Execute. Select the type and create devices in Hardware tab. Click subscribe and press OK to activate the DIM manager. Add the -dim_dns_node machineName.dyndns.cern.ch option to the corresponding manager.

 \ No newline at end of file

Revision 462019-08-13 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.

Changed:
<
<

Start the RICH Upgrade ECS

>
>

Setup the system from scratch

 
Changed:
<
<
The control of the setup is done via the MultiMiniDAQ2 project running on lbminidaq2-13. If the FSM is not already opened: open a terminal and type fsm (move to workspace 6 to do it), then right click on MiniDAQ and take the FSM clicking on the lock symbol.

How to acquire data with the laser

Turn the laser on (turn the driver key). Exclude the MEP 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.

How to acquire a full orbit

Select no more than six links in the TELL40 Links Configuration panel.
In TFC quick control enable NZS and NZS consec, limit at 4000, calibA.

In Sodin/Core0: Status&Enables tab: enable Force Trg. Cmd Config tab: Force Trg Length 4000, Trg Type 10.

How to acquire DAC scan

In DAQ box click FE. In Select action menu of FE box choose DAC scan, define channels configuration and click Apply. Then return to the main window and choose the correct step run configurations and the number of triggers on the bottom of the window. Click Apply and check if the number of triggers in the step run box equals the number of triggers in the TFC quick control menu. Then click START_RUN followed by START_TRIGGER in the MiniDAQ box. Watch the current step value in the step run block of the main window. If the value doesn't change for more than 20 seconds go to TFC and click PAUSE. After each run was finished go to MIniDAQ and click STOP_RUN.

How to start the DQ monitoring

/home/Packages/Dqmp/startdqmp.sh

standalone window: ./QtDqmp, select the RICH tab in the bar to the left and start the emulator.

Start online. Start Emulator between the available run types. Select Start in the menu to the left and select the file in the Emu Data File. Start emulator. When you have finished: Stop, Exit.

How to process data

The offline software to process data is located for each Minidaq2 in :

 /home/Packages/git/dqmp/offlineRICH2/test 

The data for each Minidaq2 are located in

/home/data/

In order to process a normal run you execute in this folder:

./runOffline.sh "fileinput.frg" "fileoutputname" "TAE" "OR"
where "OR" can take the value of 0,1 depending if you want to fill the tree for each bxid or if you want to do the OR over the TAE bxid.

There are also other 2 scripts:

./runOfflineWithOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=1
./runOfflineWithoutOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=0

If you want, not only to create the Tree but also to show the 2D hitmap and the number of hits distribution histograms you can run

./runOfflineAndShow.sh "fileinput.frg" "fileoutputname" "TAE" "OR"
where "OR" can take the value of 0,1 depending if you want to fill the tree for each bxid or if you want to do the OR over the TAE bxid.

There are also other 2 scripts:

./runOfflineAndShowWithOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=1
./runOfflineAndShowWithoutOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=0

Each run name contains the date and time at which the run was acquired and the run run number; as common convention you should provide the run number as output name to allow easy traceability (for example run pcie40_20180614_105057_main_slot_05000_link_0_run_99.frg should be processed providing outputname=run99, therefore generating tree_run99.root as output file).

In case you are processing a DAC or threshold scan you have to first process the run with

 ./runStep.sh  "run" "outputname" "TAE" start_step stop_step 

where start_step is the start_value you set in the FE panel, and then execute

  ./makeScurveGraph_hitsID "tree_#.root" "histo_#.root" "scanType" 
where tree_#.root corresponds to the output of runOffline (run99 in the example above) and "scanType" is "dac" or "th". Again the run number convention should be followed: tree_run99.root generates histo_run99.root.

To generate the file with the working points, move to the $analysis folder (on lbminidaq2-13), and run the workingPointPedestal.C macro (arguments for the routine are the histogram root file, the HV, and the number of steps above the pedestal where you want to set the threshold).

How to configure the PDMDB

Configure the master link GBTx

The bootstrapping of the master link GBTX is done via an external I2C master. This function is served by the trigger board via cables connected from the Tengja board to the PDMDB. %The trigger board connections can be found in the JRichTBTrigger topic. Move to workspace 2 in lbminidaq2-13, open an ssh connection to lbrichtb (ssh -Y richtbuser@lbrichtb) and type tb-trigger. Extra->GBTX I2C. Read on both PDMDBs until the PauseForConfig state is reached,.Write->master3g.gbt on both. Read until the Idle state is reached on both PDMDBs.

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, ./runOffline.sh 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.

Setup info in the database

The information on the PDM installed in the box can be found under PDM_2. To access them: select PDM as the default device type->HW view->Summary->select PDM_2 and press show selected. There are tags corresponding to different start validities. Clicking on the EC buttons you can access the info on the ECs (also in the EC data there are tags corresponding to different components installed in each EC).
To update the info on an EC or on the full PDM select the corresponding device type and click on update. In the new panel, showing the current configuration of the assembly, click update. In the following panel you can substitute and swap devices.

Setup the system from scratch (e.g. after a power cut)

Switch on lbminidaq2-13 (MiniDAQ2), lbrichpcie40-00 (pcie40 server and MiniDAQ3), pclbrich02, pclbtb05, pcsyslab02.
Switch on the crates for power supply.

Login to pclbtb05, Windows 10, account cern\lhcbrich (you can use vinagre to connect remotely to it) and start:

  • the DCS OPC server, by starting the OPCserver_DCS WinCC project;
  • the HV OPC server, by starting the OPCserver_HV WinCC project.

Login to pclbrich02, linux, account cern\lbrich, start the ECS and lbRichUpgradeIBCDB projects
and check that the DAQ, HV, DCS projects have auto-restarted by themselves at the power on.

Login to lbminidaq2-13 and mount pclbrich02 (sudo mount /nfs/srv02).
Type pcie40_program nameOfTheFirmware.sof (at the time of writing nameOfTheFirmware=lhcb_daq_firmware-md2-26p6l).
Type pcie40_reload.
Type config_fPLL.py.

Login to lbrichpcie40-00 and mount pclbrich02.
Type pcie40_program -c 1 nameOfTheSodinFirmware.sof.
Type pcie40_program -c 2 nameOfTheTell40Firmware.sof.
Type pcie40_program -c 3 nameOfTheTell40Firmware.sof.
Type pcie40_reload.
Type source ~/pcie40_id.sh.

Use reverse history to find the right commands.

Start the MultiMiniDAQ2 project on lbminidaq2-13.
Open the FSM and Configure from the top.
Check that in SODIN->Core0->Cmd Config the Ext is unticked and that Orbit offset is set to zero. (In the "Orbit clock" at the bottom right of the panel).

If the HV and DCS FSMs are in state DEAD, click on the state and press Restart FSM.

Follow the procedure described at the end of How to acquire data with the laser section to configure the laser driver.

Switch between prod and dev versions of the projects

Run ~/bin/gbtServer.sh "machine#"

where "machine#" is 06 or 13 depending on the DIM_DNS_NODE in use (i.e. the machine where the project is running).

>
>
Switch on lbminidaq2-13.
Type lspci | grep CERN and check the two pci are listed. If not, power cycle.
Load the firmware with pcie40_program -c 1 , where is defined under /etc/daq40.cfg.
pcie40_reload
sudo pcie40_systemd -r
sudo pcie40_systemd -l
On pcsyslab03 type startPA and run the sysLab and powerSupplies projects.
Run the CAEN OPC server addressing /home/lbrich/OpcUa/CAEN/runFull.sh
Open the D&N of the sysLab project, FSM tab and open the MiniDAQ FSM.
Click on Restart Ctrl Managers.
On a terminal type config_fPLL.py
 

Install the project from scratch

Line: 190 to 73
 cat etc/sysconfig/dnsd
and add the line DIM_HOST_NODE=machineName.dyndns.cern.ch

Install the fwGbt and fwHw component. Add -dim_dns_node machineName.dyndns.cern.ch to the options for dim manager involving Gbt.
From the Hw tool panel, ADVANCED tab, click on XML file button and select the HWDescription_PDMDB(R,H)_ADC.xml file containing the ADC line registers. Click import. Click on Edit to check the script is reasonable. Click on Execute. Select the type and create devices in Hardware tab. Click subscribe and press OK to activate the DIM manager. Add the -dim_dns_node machineName.dyndns.cern.ch option to the corresponding manager.

Deleted:
<
<

Mount

sudo vi /etc/fstab

Optical fibres for CommLab

These sketches show the proposed fibre connections for the full-column commissioning set-up. To zoom in with your browser it is best to right-click and select View image before using your browser zoom capability because the TWiki resizing is not very helpful.

RICH2-CommLab-ECS-fibres

RICH2-CommLab-Data-fibres

The sketches are for RICH2. For RICH1, replace each PDM-H with a PDM-R. Two columns breakouts are sufficient for RICH1 or RICH2 TFC/ECS. RICH1 requires 6 column breakouts for data and RICH2 requires 4. Therefore the fixed CommLab fibre installation should allow 6 MPO12 paths to the TEL40.

Machines

lbminidaq2-13

lbrichpcie40-00

storerich01

 \ No newline at end of file

Revision 452019-08-05 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 179 to 179
  The xml config file will be created when pressing create OPC config on the ELMB node in the WinCC project. Place the config file in the run directory for the ELMB OPC server.
Added:
>
>
If modprobe is not working: sudo insmod /usr/lib/modules/3.10.0-957/extra/systec_can.ko
 

Wiener

Add PDMDB ADC monitoring to the DCS project

Revision 442019-07-27 - AlessandroPetrolini

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 39 to 39
  The data for each Minidaq2 are located in
Changed:
<
<
/home/data/
>
>
/home/data/
  In order to process a normal run you execute in this folder:
Line: 79 to 79
 

How to configure the PDMDB

Changed:
<
<

Configure the master link GBTx

>
>

Configure the master link GBTx

  The bootstrapping of the master link GBTX is done via an external I2C master. This function is served by the trigger board via cables connected from the Tengja board to the PDMDB. %The trigger board connections can be found in the JRichTBTrigger topic. Move to workspace 2 in lbminidaq2-13, open an ssh connection to lbrichtb (ssh -Y richtbuser@lbrichtb) and type tb-trigger. Extra->GBTX I2C. Read on both PDMDBs until the PauseForConfig state is reached,.Write->master3g.gbt on both. Read until the Idle state is reached on both PDMDBs.
Changed:
<
<

BXID offset and Data Links alignment

>
>

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, ./runOffline.sh 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.

Changed:
<
<

Setup info in the database

>
>

Setup info in the database

  The information on the PDM installed in the box can be found under PDM_2. To access them: select PDM as the default device type->HW view->Summary->select PDM_2 and press show selected. There are tags corresponding to different start validities. Clicking on the EC buttons you can access the info on the ECs (also in the EC data there are tags corresponding to different components installed in each EC).
To update the info on an EC or on the full PDM select the corresponding device type and click on update. In the new panel, showing the current configuration of the assembly, click update. In the following panel you can substitute and swap devices.

Setup the system from scratch (e.g. after a power cut)

Changed:
<
<
Switch on lbminidaq2-13 (MiniDAQ2), lbrichpcie40-00 (pcie40 server and MiniDAQ3), pclbrich02 and pclbtb05.
>
>
Switch on lbminidaq2-13 (MiniDAQ2), lbrichpcie40-00 (pcie40 server and MiniDAQ3), pclbrich02, pclbtb05, pcsyslab02.
Switch on the crates for power supply.
 
Changed:
<
<
Switch on the crates for power supply.
>
>
Login to pclbtb05, Windows 10, account cern\lhcbrich (you can use vinagre to connect remotely to it) and start:
  • the DCS OPC server, by starting the OPCserver_DCS WinCC project;
  • the HV OPC server, by starting the OPCserver_HV WinCC project.
 
Changed:
<
<
Login to pclbtb05, Windows 10, account cern\lhcbrich (you can use vinagre to connect remotely to it) and start:
the DCS OPC server, by starting the OPCserver_DCS WinCC project;
the HV OPC server, by starting the OPCserver_HV WinCC project.
>
>
Login to pclbrich02, linux, account cern\lbrich, start the ECS and lbRichUpgradeIBCDB projects
and check that the DAQ, HV, DCS projects have auto-restarted by themselves at the power on.
 
Changed:
<
<
Login to pclbrich02, linux, account cern\lbrich, start the ECS and lbRichUpgradeIBCDB projects
and check that the DAQ, HV, DCS projects have auto-restarted by themselves at the power on.
>
>
Login to lbminidaq2-13 and mount pclbrich02 (sudo mount /nfs/srv02).
Type pcie40_program nameOfTheFirmware.sof (at the time of writing nameOfTheFirmware=lhcb_daq_firmware-md2-26p6l).
Type pcie40_reload.
Type config_fPLL.py.
 
Added:
>
>
Login to lbrichpcie40-00 and mount pclbrich02.
Type pcie40_program -c 1 nameOfTheSodinFirmware.sof.
Type pcie40_program -c 2 nameOfTheTell40Firmware.sof.
Type pcie40_program -c 3 nameOfTheTell40Firmware.sof.
Type pcie40_reload.
Type source ~/pcie40_id.sh.
 
Changed:
<
<
Login to lbminidaq2-13 and mount pclbrich02 (sudo mount /nfs/srv02). Then type pcie40_program nameOfTheFirmware.sof (at the time of writing nameOfTheFirmware=lhcb_daq_firmware-md2-26p6l). Then type pcie40_reload. Then type "config_fPLL.py*.
Login to lbrichpcie40-00 and mount pclbrich02. Type pcie40_program -c 1 nameOfTheSodinFirmware.sof. Type pcie40_program -c 2 nameOfTheTell40Firmware.sof. Type pcie40_program -c 3 nameOfTheTell40Firmware.sof. Then type pcie40_reload. Then type "source ~/pcie40_id.sh*. Use reverse history to find the right commands.
Start the MultiMiniDAQ2 project on lbminidaq2-13.
Open the FSM and Configure from the top. Check that in SODIN->Core0->Cmd Config the Ext is unticked and that Orbit offset is set to zero. (In the "Orbit clock" at the bottom right of the panel).
If the HV and DCS FSMs are in state DEAD, click on the state and press Restart FSM.
>
>
Use reverse history to find the right commands.
 
Changed:
<
<
Follow the procedure described at the end of How to acquire data with the laser section to configure the laser driver.
>
>
Start the MultiMiniDAQ2 project on lbminidaq2-13.
Open the FSM and Configure from the top.
Check that in SODIN->Core0->Cmd Config the Ext is unticked and that Orbit offset is set to zero. (In the "Orbit clock" at the bottom right of the panel).

If the HV and DCS FSMs are in state DEAD, click on the state and press Restart FSM.

Follow the procedure described at the end of How to acquire data with the laser section to configure the laser driver.

 

Switch between prod and dev versions of the projects

Revision 432019-07-26 - AlessandroPetrolini

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 98 to 98
 

Setup the system from scratch (e.g. after a power cut)

Switch on lbminidaq2-13 (MiniDAQ2), lbrichpcie40-00 (pcie40 server and MiniDAQ3), pclbrich02 and pclbtb05.

Added:
>
>
 Switch on the crates for power supply.
Changed:
<
<
Login to pclbtb05 (you can use vinagre to connect remotely to it, account lhcbrich) and start the DCS and HV OPC servers.
Login to pclbrich02 and start the ECS and lbRichUpgradeIBCDB projects (the DAQ, HV and DCS should start by itself at the power on).
>
>
Login to pclbtb05, Windows 10, account cern\lhcbrich (you can use vinagre to connect remotely to it) and start:
the DCS OPC server, by starting the OPCserver_DCS WinCC project;
the HV OPC server, by starting the OPCserver_HV WinCC project.

Login to pclbrich02, linux, account cern\lbrich, start the ECS and lbRichUpgradeIBCDB projects
and check that the DAQ, HV, DCS projects have auto-restarted by themselves at the power on.

 Login to lbminidaq2-13 and mount pclbrich02 (sudo mount /nfs/srv02). Then type pcie40_program nameOfTheFirmware.sof (at the time of writing nameOfTheFirmware=lhcb_daq_firmware-md2-26p6l). Then type pcie40_reload. Then type "config_fPLL.py*.
Login to lbrichpcie40-00 and mount pclbrich02. Type pcie40_program -c 1 nameOfTheSodinFirmware.sof. Type pcie40_program -c 2 nameOfTheTell40Firmware.sof. Type pcie40_program -c 3 nameOfTheTell40Firmware.sof. Then type pcie40_reload. Then type "source ~/pcie40_id.sh*. Use reverse history to find the right commands.
Start the MultiMiniDAQ2 project on lbminidaq2-13.

Revision 422019-07-15 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 182 to 182
 RICH2-CommLab-Data-fibres

The sketches are for RICH2. For RICH1, replace each PDM-H with a PDM-R. Two columns breakouts are sufficient for RICH1 or RICH2 TFC/ECS. RICH1 requires 6 column breakouts for data and RICH2 requires 4. Therefore the fixed CommLab fibre installation should allow 6 MPO12 paths to the TEL40. \ No newline at end of file

Added:
>
>

Machines

lbminidaq2-13

lbrichpcie40-00

storerich01

Revision 412019-06-05 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 144 to 144
  When creating devices in WinCC, use the simulation driver. Then run the OPC server and start the client. A message about certificates should appear in the logviewer. Go on SysMgm->Driver OPC->OPC UA Certificates. An entry in the Not Accepted text box should be present. Move the certificate to the Accepted box by using the arrow.
Added:
>
>
Go on SysMgm->Driver OPC->OPC UA Client->Manage (under subscriptions field). In Monitored items, select:
Use TimeStamp from: Server
Data change filter: Status,Value
 

CanOpen

Download the systec_can driver (systec_can-0.9.0p-12.cc76.x86_64.rpm) and reboot.

Revision 402019-06-04 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 136 to 136
 FSM view, configuration, Create/Configure FSM objects, Import from sys: (lbRichHV or lbRichDCS) and import RICH_HV and RICH_DCS accordingly to the selected system.
Right click on MiniDAQ partition, select Add Object(s) from FSM View, System(s) (select the system), and the type you want to add (RICH_HV or RICH_DCS), tick as Control Unit, click OK.
Generate FSM.
Change the type of MiniDAQ from MiniDAQtop to MiniDAQtopRICH.
Changed:
<
<

CAEN OPC-UA server

>
>

OPC-UA servers

 
Changed:
<
<
You need to change _OPCUA_CAEN.Config.ConnInfo with the correct port that you can find by using sudo netstat -ltnp (there are two ports relative to the OPC server: one used to communicate with the crate, the other one in listening for the client). Useful documentation is here http://jcop.web.cern.ch/jcop-framework-caen-devices
>
>

CAEN

You need to change _OPCUA_CAEN.Config.ConnInfo with the correct port that you can find by using sudo netstat -ltnp (there are two ports relative to the OPC server: one used to communicate with the crate, the other one in listening for the client). Useful documentation is here http://jcop.web.cern.ch/jcop-framework-caen-devices.

When creating devices in WinCC, use the simulation driver. Then run the OPC server and start the client. A message about certificates should appear in the logviewer. Go on SysMgm->Driver OPC->OPC UA Certificates. An entry in the Not Accepted text box should be present. Move the certificate to the Accepted box by using the arrow.

CanOpen

Download the systec_can driver (systec_can-0.9.0p-12.cc76.x86_64.rpm) and reboot.
modprobe systec_can (in case of errors use insmod)
If dmesg complains about boot loader install systec_can-0.9.8p-3.cc76.x86_64.rpm
Install socketcan_utils-2920d417315f14397f683e5e368520421c8a9702.0.0-0.x86_64.rpm
Install OpcUaCanOpenServer-2.2.3-46cc7.x86_64.rpm
Install uaexpert-bin-centos7-x86_64-gcc4.8.2-v1.4.2-256.rpm (an opc-ua client)

The xml config file will be created when pressing create OPC config on the ELMB node in the WinCC project. Place the config file in the run directory for the ELMB OPC server.

Wiener

 

Add PDMDB ADC monitoring to the DCS project

Revision 392019-06-03 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 138 to 138
 

CAEN OPC-UA server

Changed:
<
<
You need to change _OPCUA_CAEN.Config.ConnInfo with the correct port that you can find by using sudo netstat -ltnp (there are two ports relative to the OPC server: one used to communicate with the crate, the other one in listening for the client).
>
>
You need to change _OPCUA_CAEN.Config.ConnInfo with the correct port that you can find by using sudo netstat -ltnp (there are two ports relative to the OPC server: one used to communicate with the crate, the other one in listening for the client). Useful documentation is here http://jcop.web.cern.ch/jcop-framework-caen-devices
 

Add PDMDB ADC monitoring to the DCS project

Revision 382019-05-29 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 136 to 136
 FSM view, configuration, Create/Configure FSM objects, Import from sys: (lbRichHV or lbRichDCS) and import RICH_HV and RICH_DCS accordingly to the selected system.
Right click on MiniDAQ partition, select Add Object(s) from FSM View, System(s) (select the system), and the type you want to add (RICH_HV or RICH_DCS), tick as Control Unit, click OK.
Generate FSM.
Change the type of MiniDAQ from MiniDAQtop to MiniDAQtopRICH.
Added:
>
>

CAEN OPC-UA server

You need to change _OPCUA_CAEN.Config.ConnInfo with the correct port that you can find by using sudo netstat -ltnp (there are two ports relative to the OPC server: one used to communicate with the crate, the other one in listening for the client).

 

Add PDMDB ADC monitoring to the DCS project

On the machine running the DIM_DNS_server type

Revision 372019-05-27 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
Changed:
<
<
This page contains information on how to configure the system and to take data in the SysLab.
>
>
This page contains information on how to configure the system and to take data in the SysLab.
 

Start the RICH Upgrade ECS

Changed:
<
<
The control of the setup is done via the MultiMiniDAQ2 project running on lbminidaq2-13. If the FSM is not already opened: open a terminal and type fsm (move to workspace 6 to do it), then right click on MiniDAQ and take the FSM clicking on the lock symbol.
>
>
The control of the setup is done via the MultiMiniDAQ2 project running on lbminidaq2-13. If the FSM is not already opened: open a terminal and type fsm (move to workspace 6 to do it), then right click on MiniDAQ and take the FSM clicking on the lock symbol.
 

How to acquire data with the laser

Turn the laser on (turn the driver key). Exclude the MEP 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.

Changed:
<
<
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.
>
>
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.
 

How to acquire a full orbit

Line: 21 to 21
 

How to acquire DAC scan

Changed:
<
<
In DAQ box click FE. In Select action menu of FE box choose DAC scan, define channels configuration and click Apply. Then return to the main window and choose the correct step run configurations and the number of triggers on the bottom of the window. Click Apply and check if the number of triggers in the step run box equals the number of triggers in the TFC quick control menu. Then click START_RUN followed by START_TRIGGER in the MiniDAQ box. Watch the current step value in the step run block of the main window. If the value doesn't change for more than 20 seconds go to TFC and click PAUSE. After each run was finished go to MIniDAQ and click STOP_RUN.
>
>
In DAQ box click FE. In Select action menu of FE box choose DAC scan, define channels configuration and click Apply. Then return to the main window and choose the correct step run configurations and the number of triggers on the bottom of the window. Click Apply and check if the number of triggers in the step run box equals the number of triggers in the TFC quick control menu. Then click START_RUN followed by START_TRIGGER in the MiniDAQ box. Watch the current step value in the step run block of the main window. If the value doesn't change for more than 20 seconds go to TFC and click PAUSE. After each run was finished go to MIniDAQ and click STOP_RUN.
 

How to start the DQ monitoring

Line: 82 to 82
 

Configure the master link GBTx

The bootstrapping of the master link GBTX is done via an external I2C master. This function is served by the trigger board via cables connected from the Tengja board to the PDMDB.

Changed:
<
<
%The trigger board connections can be found in the JRichTBTrigger topic. Move to workspace 2 in lbminidaq2-13, open an ssh connection to lbrichtb (ssh -Y richtbuser@lbrichtb) and type tb-trigger. Extra->GBTX I2C. Read on both PDMDBs until the PauseForConfig state is reached,.Write->master3g.gbt on both. Read until the Idle state is reached on both PDMDBs.
>
>
%The trigger board connections can be found in the JRichTBTrigger topic. Move to workspace 2 in lbminidaq2-13, open an ssh connection to lbrichtb (ssh -Y richtbuser@lbrichtb) and type tb-trigger. Extra->GBTX I2C. Read on both PDMDBs until the PauseForConfig state is reached,.Write->master3g.gbt on both. Read until the Idle state is reached on both PDMDBs.
 

BXID offset and Data Links alignment

Line: 97 to 97
 

Setup the system from scratch (e.g. after a power cut)

Changed:
<
<
Switch on lbminidaq2-13 (MiniDAQ2), lbrichpcie40-00 (pcie40 server and MiniDAQ3), pclbrich02 and pclbtb05.
>
>
Switch on lbminidaq2-13 (MiniDAQ2), lbrichpcie40-00 (pcie40 server and MiniDAQ3), pclbrich02 and pclbtb05.
 Switch on the crates for power supply.
Login to pclbtb05 (you can use vinagre to connect remotely to it, account lhcbrich) and start the DCS and HV OPC servers.
Login to pclbrich02 and start the ECS and lbRichUpgradeIBCDB projects (the DAQ, HV and DCS should start by itself at the power on).
Login to lbminidaq2-13 and mount pclbrich02 (sudo mount /nfs/srv02). Then type pcie40_program nameOfTheFirmware.sof (at the time of writing nameOfTheFirmware=lhcb_daq_firmware-md2-26p6l). Then type pcie40_reload. Then type "config_fPLL.py*.
Login to lbrichpcie40-00 and mount pclbrich02. Type pcie40_program -c 1 nameOfTheSodinFirmware.sof. Type pcie40_program -c 2 nameOfTheTell40Firmware.sof. Type pcie40_program -c 3 nameOfTheTell40Firmware.sof. Then type pcie40_reload. Then type "source ~/pcie40_id.sh*. Use reverse history to find the right commands.
Changed:
<
<
Start the MultiMiniDAQ2 project on lbminidaq2-13.
>
>
Start the MultiMiniDAQ2 project on lbminidaq2-13.
 Open the FSM and Configure from the top. Check that in SODIN->Core0->Cmd Config the Ext is unticked and that Orbit offset is set to zero. (In the "Orbit clock" at the bottom right of the panel).
If the HV and DCS FSMs are in state DEAD, click on the state and press Restart FSM.
Line: 117 to 117
 

Install the project from scratch

Changed:
<
<
Create a new WinCC project.
>
>
Create a new WinCC project.
 Copy the fwInstallation folder into the project folder and install the jcop fw components: fwCore, fwConfigurationDB, fwDIM and fwTrending.
Install the fwMiniDAQ component.
Changed:
<
<
Open the MiniDAQ fsm, click on Configure Subscriptions, Configure Multi, delete existing devices, create the RICH_TELL40 type and apply the default settings for each device. Open the HW tool and create the TELL40_RICH device type using the appropriate xml. Also create the RICHPDMDB device type using the appropriate xml.
Define the other devices in the MiniDAQ FSM view and click on subscribe all. The click on the Create FSM button.
>
>
Open the MiniDAQ fsm, click on Configure Subscriptions, Configure Multi, delete existing devices, create the RICH_TELL40 type and apply the default settings for each device. Open the HW tool and create the TELL40_RICH device type using the appropriate xml. Also create the RICHPDMDB device type using the appropriate xml.
Define the other devices in the MiniDAQ FSM view and click on subscribe all. The click on the Create FSM button.
 Install the fwRich component.
Open the fwRich_Configurator.pnl panel to create the new PDMDBs clicking on the Generate button.
Select the new devices in the table, select the firmwares, and click on the Update Selected button.
Line: 129 to 129
 Create the recipe DEFAULT/CONFIGURE in the hardware view tab.
Check that everything is ok within the fsm, i.e. try to take a run.
Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as distributed peers. (it is not needed if the config file is present in the fwRich.xml file)
Changed:
<
<
Import the fwRichMiniDAQtop.dpl using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.
>
>
Import the fwRichMiniDAQtop.dpl using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.
 
Changed:
<
<

Add HV and DCS partitions to the MiniDAQ FSM

>
>

Add HV and DCS partitions to the MiniDAQ FSM

 
Changed:
<
<
FSM view, configuration, Create/Configure FSM objects, Import from sys: (lbRichHV or lbRichDCS) and import RICH_HV and RICH_DCS accordingly to the selected system.
Right click on MiniDAQ partition, select Add Object(s) from FSM View, System(s) (select the system), and the type you want to add (RICH_HV or RICH_DCS), tick as Control Unit, click OK.
Generate FSM.
Change the type of MiniDAQ from MiniDAQtop to MiniDAQtopRICH.
>
>
FSM view, configuration, Create/Configure FSM objects, Import from sys: (lbRichHV or lbRichDCS) and import RICH_HV and RICH_DCS accordingly to the selected system.
Right click on MiniDAQ partition, select Add Object(s) from FSM View, System(s) (select the system), and the type you want to add (RICH_HV or RICH_DCS), tick as Control Unit, click OK.
Generate FSM.
Change the type of MiniDAQ from MiniDAQtop to MiniDAQtopRICH.
 

Add PDMDB ADC monitoring to the DCS project

Line: 148 to 148
  sudo vi /etc/fstab
Changed:
<
<

Optcal fibres for CommLab

>
>

Optical fibres for CommLab

  These sketches show the proposed fibre connections for the full-column commissioning set-up. To zoom in with your browser it is best to right-click and select View image before using your browser zoom capability because the TWiki resizing is not very helpful.

RICH2-CommLab-ECS-fibres

RICH2-CommLab-Data-fibres

Added:
>
>
The sketches are for RICH2. For RICH1, replace each PDM-H with a PDM-R. Two columns breakouts are sufficient for RICH1 or RICH2 TFC/ECS. RICH1 requires 6 column breakouts for data and RICH2 requires 4. Therefore the fixed CommLab fibre installation should allow 6 MPO12 paths to the TEL40.

Revision 362019-05-24 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 148 to 148
  sudo vi /etc/fstab
Added:
>
>

Optcal fibres for CommLab

 
Added:
>
>
These sketches show the proposed fibre connections for the full-column commissioning set-up. To zoom in with your browser it is best to right-click and select View image before using your browser zoom capability because the TWiki resizing is not very helpful.
 
Deleted:
<
<
-- GiovanniCavallero - 2018-06-12
 \ No newline at end of file
Added:
>
>
RICH2-CommLab-ECS-fibres

RICH2-CommLab-Data-fibres

Revision 352019-03-27 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 6 to 6
 

Start the RICH Upgrade ECS

Changed:
<
<
The control of the setup is done via the MultiMiniDAQ2 project running on lbminidaq2-13.
If the VNC connection is not already opened: type krdc & on the pclbrichtb Linux machine in the Syslab, Boomarks->History->lbminidaq2-13:VNCport.
If the FSM is not already opened: open a terminal and type fsm (move to workspace 6 to do it), then right click on MiniDAQ and take the FSM clicking on the lock symbol.
>
>
The control of the setup is done via the MultiMiniDAQ2 project running on lbminidaq2-13. If the FSM is not already opened: open a terminal and type fsm (move to workspace 6 to do it), then right click on MiniDAQ and take the FSM clicking on the lock symbol.
 

How to acquire data with the laser

Revision 342019-03-19 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 104 to 104
 Login to lbminidaq2-13 and mount pclbrich02 (sudo mount /nfs/srv02). Then type pcie40_program nameOfTheFirmware.sof (at the time of writing nameOfTheFirmware=lhcb_daq_firmware-md2-26p6l). Then type pcie40_reload. Then type "config_fPLL.py*.
Login to lbrichpcie40-00 and mount pclbrich02. Type pcie40_program -c 1 nameOfTheSodinFirmware.sof. Type pcie40_program -c 2 nameOfTheTell40Firmware.sof. Type pcie40_program -c 3 nameOfTheTell40Firmware.sof. Then type pcie40_reload. Then type "source ~/pcie40_id.sh*. Use reverse history to find the right commands.
Start the MultiMiniDAQ2 project on lbminidaq2-13.
Changed:
<
<
Open the FSM and Configure from the top. Check that in SODIN->Core0->Cmd Config the Ext is unticked and that Orbit offset is set to zero. (In the "Orbit clock" at the bottom right of the panel).
>
>
Open the FSM and Configure from the top. Check that in SODIN->Core0->Cmd Config the Ext is unticked and that Orbit offset is set to zero. (In the "Orbit clock" at the bottom right of the panel).
If the HV and DCS FSMs are in state DEAD, click on the state and press Restart FSM.
  Follow the procedure described at the end of How to acquire data with the laser section to configure the laser driver.

Revision 332019-03-11 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 10 to 10
 

How to acquire data with the laser

Changed:
<
<
Turn the laser on (turn the driver key). Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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 pclhcb116;
- 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.
>
>
Turn the laser on (turn the driver key). Exclude the MEP 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.
 

How to acquire a full orbit

Line: 104 to 104
 Login to lbminidaq2-13 and mount pclbrich02 (sudo mount /nfs/srv02). Then type pcie40_program nameOfTheFirmware.sof (at the time of writing nameOfTheFirmware=lhcb_daq_firmware-md2-26p6l). Then type pcie40_reload. Then type "config_fPLL.py*.
Login to lbrichpcie40-00 and mount pclbrich02. Type pcie40_program -c 1 nameOfTheSodinFirmware.sof. Type pcie40_program -c 2 nameOfTheTell40Firmware.sof. Type pcie40_program -c 3 nameOfTheTell40Firmware.sof. Then type pcie40_reload. Then type "source ~/pcie40_id.sh*. Use reverse history to find the right commands.
Start the MultiMiniDAQ2 project on lbminidaq2-13.
Added:
>
>
Open the FSM and Configure from the top. Check that in SODIN->Core0->Cmd Config the Ext is unticked and that Orbit offset is set to zero. (In the "Orbit clock" at the bottom right of the panel).
  Follow the procedure described at the end of How to acquire data with the laser section to configure the laser driver.

Revision 322019-03-11 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 95 to 95
  The information on the PDM installed in the box can be found under PDM_2. To access them: select PDM as the default device type->HW view->Summary->select PDM_2 and press show selected. There are tags corresponding to different start validities. Clicking on the EC buttons you can access the info on the ECs (also in the EC data there are tags corresponding to different components installed in each EC).
To update the info on an EC or on the full PDM select the corresponding device type and click on update. In the new panel, showing the current configuration of the assembly, click update. In the following panel you can substitute and swap devices.
Changed:
<
<

Setup the system from scratch (when everything was off)

>
>

Setup the system from scratch (e.g. after a power cut)

 
Changed:
<
<
You will need: lbminidaq2-06, lbminidaq2-13, pclbrich02, pclhcb116.

First load the firmwares on lbminidaq2-06 and lbminidaq2-13:

cd /home/Firmware/local_quartus2
pcie40_program lhcb_daq_firmware_intclk_autocalib_ok_fixedSODIN.sof (master TFC, i.e. lbminidaq2-13)
pcie40_program lhcb_daq_firmware_extclk_autocalib_ok_fixedSODIN.sof (slaveTFC, i.e. lbminidaq2-06).
Reboot both the machines.

Open a vnc connection to lbminidaq2-13, open a terminal there and run term.sh. Start the Gbt servers on both 06 and 13 as described in section Switch between prod and dev versions of the projects.
Go the the Monster tab, type StartPA and check that the lbrichDCS, lbRichECS, lbRichHV projects are Running. Type sudo mount /nfs/srv02 on lbminidaq2-13. Go to workspace 6 and start the MultiMiniDAQ2 project. Press the Reload button next to the Gbt server connection field and check on the log viewer that the drivers for both 06 and 13 are fine.

Switch on the crate. Move to the windows machine (pclhcb116) and start the OPCserver_DCS and OPCserver_HV projects. Switch on the trigger board and the PDMDBs.

Move to workspace 2 of lbminidaq2-13 and open an ssh richtbuser@lbrichtb, type tb-trigger and load the master3g.gbt files on each pdmdb.

>
>
Switch on lbminidaq2-13 (MiniDAQ2), lbrichpcie40-00 (pcie40 server and MiniDAQ3), pclbrich02 and pclbtb05.
Switch on the crates for power supply.
Login to pclbtb05 (you can use vinagre to connect remotely to it, account lhcbrich) and start the DCS and HV OPC servers.
Login to pclbrich02 and start the ECS and lbRichUpgradeIBCDB projects (the DAQ, HV and DCS should start by itself at the power on).
Login to lbminidaq2-13 and mount pclbrich02 (sudo mount /nfs/srv02). Then type pcie40_program nameOfTheFirmware.sof (at the time of writing nameOfTheFirmware=lhcb_daq_firmware-md2-26p6l). Then type pcie40_reload. Then type "config_fPLL.py*.
Login to lbrichpcie40-00 and mount pclbrich02. Type pcie40_program -c 1 nameOfTheSodinFirmware.sof. Type pcie40_program -c 2 nameOfTheTell40Firmware.sof. Type pcie40_program -c 3 nameOfTheTell40Firmware.sof. Then type pcie40_reload. Then type "source ~/pcie40_id.sh*. Use reverse history to find the right commands.
Start the MultiMiniDAQ2 project on lbminidaq2-13.
  Follow the procedure described at the end of How to acquire data with the laser section to configure the laser driver.

Revision 312019-01-29 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 75 to 75
 
  ./makeScurveGraph_hitsID "tree_#.root" "histo_#.root" "scanType" 
where tree_#.root corresponds to the output of runOffline (run99 in the example above) and "scanType" is "dac" or "th". Again the run number convention should be followed: tree_run99.root generates histo_run99.root.
Added:
>
>
To generate the file with the working points, move to the $analysis folder (on lbminidaq2-13), and run the workingPointPedestal.C macro (arguments for the routine are the histogram root file, the HV, and the number of steps above the pedestal where you want to set the threshold).
 

How to configure the PDMDB

Configure the master link GBTx

Revision 302019-01-29 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 82 to 82
 The bootstrapping of the master link GBTX is done via an external I2C master. This function is served by the trigger board via cables connected from the Tengja board to the PDMDB. %The trigger board connections can be found in the JRichTBTrigger topic. Move to workspace 2 in lbminidaq2-13, open an ssh connection to lbrichtb (ssh -Y richtbuser@lbrichtb) and type tb-trigger. Extra->GBTX I2C. Read on both PDMDBs until the PauseForConfig state is reached,.Write->master3g.gbt on both. Read until the Idle state is reached on both PDMDBs.
Changed:
<
<

Data Links alignment

>
>

BXID offset and Data Links alignment

 
Added:
>
>
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, ./runOffline.sh 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.

Revision 292018-12-13 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 137 to 137
 

Add PDMDB ADC monitoring to the DCS project

Added:
>
>
On the machine running the DIM_DNS_server type

cat etc/sysconfig/dnsd
and add the line DIM_HOST_NODE=machineName.dyndns.cern.ch

Install the fwGbt and fwHw component. Add -dim_dns_node machineName.dyndns.cern.ch to the options for dim manager involving Gbt.
From the Hw tool panel, ADVANCED tab, click on XML file button and select the HWDescription_PDMDB(R,H)_ADC.xml file containing the ADC line registers. Click import. Click on Edit to check the script is reasonable. Click on Execute. Select the type and create devices in Hardware tab. Click subscribe and press OK to activate the DIM manager. Add the -dim_dns_node machineName.dyndns.cern.ch option to the corresponding manager.

 

Mount

sudo vi /etc/fstab

Revision 282018-12-13 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 135 to 135
 FSM view, configuration, Create/Configure FSM objects, Import from sys: (lbRichHV or lbRichDCS) and import RICH_HV and RICH_DCS accordingly to the selected system.
Right click on MiniDAQ partition, select Add Object(s) from FSM View, System(s) (select the system), and the type you want to add (RICH_HV or RICH_DCS), tick as Control Unit, click OK.
Generate FSM.
Change the type of MiniDAQ from MiniDAQtop to MiniDAQtopRICH.
Added:
>
>

Add PDMDB ADC monitoring to the DCS project

 

Mount

sudo vi /etc/fstab

Revision 272018-12-11 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 82 to 82
 The bootstrapping of the master link GBTX is done via an external I2C master. This function is served by the trigger board via cables connected from the Tengja board to the PDMDB. %The trigger board connections can be found in the JRichTBTrigger topic. Move to workspace 2 in lbminidaq2-13, open an ssh connection to lbrichtb (ssh -Y richtbuser@lbrichtb) and type tb-trigger. Extra->GBTX I2C. Read on both PDMDBs until the PauseForConfig state is reached,.Write->master3g.gbt on both. Read until the Idle state is reached on both PDMDBs.
Added:
>
>

Data Links alignment

Look at hslotpixel histogram of a run with TAE enabled (you need to process it without OR, ./runOffline.sh 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.

 

Setup info in the database

The information on the PDM installed in the box can be found under PDM_2. To access them: select PDM as the default device type->HW view->Summary->select PDM_2 and press show selected. There are tags corresponding to different start validities. Clicking on the EC buttons you can access the info on the ECs (also in the EC data there are tags corresponding to different components installed in each EC).
To update the info on an EC or on the full PDM select the corresponding device type and click on update. In the new panel, showing the current configuration of the assembly, click update. In the following panel you can substitute and swap devices.

Revision 262018-11-15 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 129 to 129
 FSM view, configuration, Create/Configure FSM objects, Import from sys: (lbRichHV or lbRichDCS) and import RICH_HV and RICH_DCS accordingly to the selected system.
Right click on MiniDAQ partition, select Add Object(s) from FSM View, System(s) (select the system), and the type you want to add (RICH_HV or RICH_DCS), tick as Control Unit, click OK.
Generate FSM.
Change the type of MiniDAQ from MiniDAQtop to MiniDAQtopRICH.
Added:
>
>

Mount

sudo vi /etc/fstab

 

-- GiovanniCavallero - 2018-06-12

Revision 252018-11-15 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 124 to 124
 Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as distributed peers. (it is not needed if the config file is present in the fwRich.xml file)
Import the fwRichMiniDAQtop.dpl using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.
Added:
>
>

Add HV and DCS partitions to the MiniDAQ FSM

FSM view, configuration, Create/Configure FSM objects, Import from sys: (lbRichHV or lbRichDCS) and import RICH_HV and RICH_DCS accordingly to the selected system.
Right click on MiniDAQ partition, select Add Object(s) from FSM View, System(s) (select the system), and the type you want to add (RICH_HV or RICH_DCS), tick as Control Unit, click OK.
Generate FSM.
Change the type of MiniDAQ from MiniDAQtop to MiniDAQtopRICH.

 

-- GiovanniCavallero - 2018-06-12 \ No newline at end of file

Revision 242018-11-13 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 13 to 13
 Turn the laser on (turn the driver key). Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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 pclhcb116;
- 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.
Added:
>
>

How to acquire a full orbit

Select no more than six links in the TELL40 Links Configuration panel.
In TFC quick control enable NZS and NZS consec, limit at 4000, calibA.

In Sodin/Core0: Status&Enables tab: enable Force Trg. Cmd Config tab: Force Trg Length 4000, Trg Type 10.

 

How to acquire DAC scan

In DAQ box click FE. In Select action menu of FE box choose DAC scan, define channels configuration and click Apply. Then return to the main window and choose the correct step run configurations and the number of triggers on the bottom of the window. Click Apply and check if the number of triggers in the step run box equals the number of triggers in the TFC quick control menu. Then click START_RUN followed by START_TRIGGER in the MiniDAQ box. Watch the current step value in the step run block of the main window. If the value doesn't change for more than 20 seconds go to TFC and click PAUSE. After each run was finished go to MIniDAQ and click STOP_RUN.

Revision 232018-10-12 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 47 to 47
 
./runOfflineWithoutOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=0
Changed:
<
<
If you want, not only to create the Three but also to show the 2D hitmap and the number of hits distribution histograms you can run
>
>
If you want, not only to create the Tree but also to show the 2D hitmap and the number of hits distribution histograms you can run
 
./runOfflineAndShow.sh "fileinput.frg" "fileoutputname" "TAE" "OR"
where "OR" can take the value of 0,1 depending if you want to fill the tree for each bxid or if you want to do the OR over the TAE bxid.
Line: 67 to 67
  where start_step is the start_value you set in the FE panel, and then execute
Changed:
<
<
  ./makeScurveGraph "tree_#.root" "histo_#.root" "scanType" 
where tree_#.root corresponds to the output of runOffline (run99 in the example above) and "scanType" is "dac" or "th". Again the run number convention should be followed: tree_run99.root generates histo_run99.root.
>
>
  ./makeScurveGraph_hitsID "tree_#.root" "histo_#.root" "scanType" 
where tree_#.root corresponds to the output of runOffline (run99 in the example above) and "scanType" is "dac" or "th". Again the run number convention should be followed: tree_run99.root generates histo_run99.root.
 

How to configure the PDMDB

Revision 222018-10-03 - RobertaCardinale

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 29 to 29
  The offline software to process data is located for each Minidaq2 in :
Changed:
<
<
 /home/Packages/offline_step/test 
>
>
 /home/Packages/git/dqmp/offlineRICH2/test 
  The data for each Minidaq2 are located in
Line: 37 to 37
  In order to process a normal run you execute in this folder:
Changed:
<
<
./runOffline.sh "run" "outputname" "TAE" 
>
>
./runOffline.sh "fileinput.frg" "fileoutputname" "TAE" "OR"
where "OR" can take the value of 0,1 depending if you want to fill the tree for each bxid or if you want to do the OR over the TAE bxid.

There are also other 2 scripts:

./runOfflineWithOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=1
./runOfflineWithoutOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=0

If you want, not only to create the Three but also to show the 2D hitmap and the number of hits distribution histograms you can run

./runOfflineAndShow.sh "fileinput.frg" "fileoutputname" "TAE" "OR"
where "OR" can take the value of 0,1 depending if you want to fill the tree for each bxid or if you want to do the OR over the TAE bxid.

There are also other 2 scripts:

./runOfflineAndShowWithOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=1
./runOfflineAndShowWithoutOR.sh "fileinput.frg" "fileoutputname" "TAE"
with the OR=0
  Each run name contains the date and time at which the run was acquired and the run run number; as common convention you should provide the run number as output name to allow easy traceability (for example run pcie40_20180614_105057_main_slot_05000_link_0_run_99.frg should be processed providing outputname=run99, therefore generating tree_run99.root as output file).

In case you are processing a DAC or threshold scan you have to first process the run with

Changed:
<
<
 ./runScans.sh  "run" "outputname" "TAE" start_step stop_step 
>
>
 ./runStep.sh  "run" "outputname" "TAE" start_step stop_step 
  where start_step is the start_value you set in the FE panel, and then execute

Revision 212018-08-02 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 19 to 19
 

How to start the DQ monitoring

Changed:
<
<
cp /home/Packages/Dqmp
>
>
/home/Packages/Dqmp/startdqmp.sh
 
Changed:
<
<
source startdqmp.sh
>
>
standalone window: ./QtDqmp, select the RICH tab in the bar to the left and start the emulator.
 
Changed:
<
<
cd $DQMP

standalone window: ./QtDqmp, select emulator.

Start online. Select Start in the menu to the left, start emulator and select the file. When you have finished: Stop, Exit.

>
>
Start online. Start Emulator between the available run types. Select Start in the menu to the left and select the file in the Emu Data File. Start emulator. When you have finished: Stop, Exit.
 

How to process data

Revision 202018-08-01 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 17 to 17
  In DAQ box click FE. In Select action menu of FE box choose DAC scan, define channels configuration and click Apply. Then return to the main window and choose the correct step run configurations and the number of triggers on the bottom of the window. Click Apply and check if the number of triggers in the step run box equals the number of triggers in the TFC quick control menu. Then click START_RUN followed by START_TRIGGER in the MiniDAQ box. Watch the current step value in the step run block of the main window. If the value doesn't change for more than 20 seconds go to TFC and click PAUSE. After each run was finished go to MIniDAQ and click STOP_RUN.
Added:
>
>

How to start the DQ monitoring

cp /home/Packages/Dqmp

source startdqmp.sh

cd $DQMP

standalone window: ./QtDqmp, select emulator.

Start online. Select Start in the menu to the left, start emulator and select the file. When you have finished: Stop, Exit.

 

How to process data

The offline software to process data is located for each Minidaq2 in :

Revision 192018-07-23 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 60 to 60
  cd /home/Firmware/local_quartus2
pcie40_program lhcb_daq_firmware_intclk_autocalib_ok_fixedSODIN.sof (master TFC, i.e. lbminidaq2-13)
pcie40_program lhcb_daq_firmware_extclk_autocalib_ok_fixedSODIN.sof (slaveTFC, i.e. lbminidaq2-06).
Reboot both the machines.
Changed:
<
<
Open a vnc connection to lbminidaq2-13, open a terminal there and run term.sh. Go the the Monster tab, type StartPA and check that the lbrichDCS, lbRichECS, lbRichHV projects are Running. Type sudo mount /nfs/srv02 on lbminidaq2-13. Go to workspace 6 and start the MultiMiniDAQ2 project.
>
>
Open a vnc connection to lbminidaq2-13, open a terminal there and run term.sh. Start the Gbt servers on both 06 and 13 as described in section Switch between prod and dev versions of the projects.
Go the the Monster tab, type StartPA and check that the lbrichDCS, lbRichECS, lbRichHV projects are Running. Type sudo mount /nfs/srv02 on lbminidaq2-13. Go to workspace 6 and start the MultiMiniDAQ2 project. Press the Reload button next to the Gbt server connection field and check on the log viewer that the drivers for both 06 and 13 are fine.
  Switch on the crate. Move to the windows machine (pclhcb116) and start the OPCserver_DCS and OPCserver_HV projects. Switch on the trigger board and the PDMDBs.
Changed:
<
<
Move to workspace 2 of lbminidaq2-13 and open an ssh richtbuser@lbrichtb, type tb-trigger.
>
>
Move to workspace 2 of lbminidaq2-13 and open an ssh richtbuser@lbrichtb, type tb-trigger and load the master3g.gbt files on each pdmdb.
  Follow the procedure described at the end of How to acquire data with the laser section to configure the laser driver.

Revision 182018-07-23 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 52 to 52
  The information on the PDM installed in the box can be found under PDM_2. To access them: select PDM as the default device type->HW view->Summary->select PDM_2 and press show selected. There are tags corresponding to different start validities. Clicking on the EC buttons you can access the info on the ECs (also in the EC data there are tags corresponding to different components installed in each EC).
To update the info on an EC or on the full PDM select the corresponding device type and click on update. In the new panel, showing the current configuration of the assembly, click update. In the following panel you can substitute and swap devices.
Changed:
<
<

How to load firmwares in the minidaq2

>
>

Setup the system from scratch (when everything was off)

 
Changed:
<
<
cd /home/Firmware/local_quartus2 pcie40_program lhcb_daq_firmware_intclk_autocalib_ok_fixedSODIN.sof
>
>
You will need: lbminidaq2-06, lbminidaq2-13, pclbrich02, pclhcb116.

First load the firmwares on lbminidaq2-06 and lbminidaq2-13:

cd /home/Firmware/local_quartus2
pcie40_program lhcb_daq_firmware_intclk_autocalib_ok_fixedSODIN.sof (master TFC, i.e. lbminidaq2-13)
pcie40_program lhcb_daq_firmware_extclk_autocalib_ok_fixedSODIN.sof (slaveTFC, i.e. lbminidaq2-06).
Reboot both the machines.

Open a vnc connection to lbminidaq2-13, open a terminal there and run term.sh. Go the the Monster tab, type StartPA and check that the lbrichDCS, lbRichECS, lbRichHV projects are Running. Type sudo mount /nfs/srv02 on lbminidaq2-13. Go to workspace 6 and start the MultiMiniDAQ2 project.

Switch on the crate. Move to the windows machine (pclhcb116) and start the OPCserver_DCS and OPCserver_HV projects. Switch on the trigger board and the PDMDBs.

Move to workspace 2 of lbminidaq2-13 and open an ssh richtbuser@lbrichtb, type tb-trigger.

Follow the procedure described at the end of How to acquire data with the laser section to configure the laser driver.

Switch between prod and dev versions of the projects

Run ~/bin/gbtServer.sh "machine#"

where "machine#" is 06 or 13 depending on the DIM_DNS_NODE in use (i.e. the machine where the project is running).

 

Install the project from scratch

Line: 73 to 91
 Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as distributed peers. (it is not needed if the config file is present in the fwRich.xml file)
Import the fwRichMiniDAQtop.dpl using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.
Deleted:
<
<

Switch between prod and dev versions of the projects

Run /bin/gbtServer.sh "machine#"

where "machine#" is 06 or 13 depending on the DIM_DNS_NODE in use.

 

-- GiovanniCavallero - 2018-06-12 \ No newline at end of file

Revision 172018-07-20 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 52 to 52
  The information on the PDM installed in the box can be found under PDM_2. To access them: select PDM as the default device type->HW view->Summary->select PDM_2 and press show selected. There are tags corresponding to different start validities. Clicking on the EC buttons you can access the info on the ECs (also in the EC data there are tags corresponding to different components installed in each EC).
To update the info on an EC or on the full PDM select the corresponding device type and click on update. In the new panel, showing the current configuration of the assembly, click update. In the following panel you can substitute and swap devices.
Added:
>
>

How to load firmwares in the minidaq2

cd /home/Firmware/local_quartus2 pcie40_program lhcb_daq_firmware_intclk_autocalib_ok_fixedSODIN.sof

 

Install the project from scratch

Create a new WinCC project.

Revision 162018-07-20 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 63 to 63
 Open the fwRich_Configurator.pnl panel to create the new PDMDBs clicking on the Generate button.
Select the new devices in the table, select the firmwares, and click on the Update Selected button.
Click on the Generate FSM button.
Added:
>
>
Create the recipe DEFAULT/CONFIGURE in the hardware view tab.
 Check that everything is ok within the fsm, i.e. try to take a run.
Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as distributed peers. (it is not needed if the config file is present in the fwRich.xml file)
Import the fwRichMiniDAQtop.dpl using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.
Added:
>
>

Switch between prod and dev versions of the projects

Run /bin/gbtServer.sh "machine#"

where "machine#" is 06 or 13 depending on the DIM_DNS_NODE in use.

 

-- GiovanniCavallero - 2018-06-12

Revision 152018-07-19 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 48 to 48
 The bootstrapping of the master link GBTX is done via an external I2C master. This function is served by the trigger board via cables connected from the Tengja board to the PDMDB. %The trigger board connections can be found in the JRichTBTrigger topic. Move to workspace 2 in lbminidaq2-13, open an ssh connection to lbrichtb (ssh -Y richtbuser@lbrichtb) and type tb-trigger. Extra->GBTX I2C. Read on both PDMDBs until the PauseForConfig state is reached,.Write->master3g.gbt on both. Read until the Idle state is reached on both PDMDBs.
Changed:
<
<

Troubleshootings

>
>

Setup info in the database

 
Changed:
<
<
If a scan is stuck on the RUNNING state without receiving triggers from TFC, send the PAUSE command to the TFC partition. The current step will be lost but the scan will continue.
>
>
The information on the PDM installed in the box can be found under PDM_2. To access them: select PDM as the default device type->HW view->Summary->select PDM_2 and press show selected. There are tags corresponding to different start validities. Clicking on the EC buttons you can access the info on the ECs (also in the EC data there are tags corresponding to different components installed in each EC).
To update the info on an EC or on the full PDM select the corresponding device type and click on update. In the new panel, showing the current configuration of the assembly, click update. In the following panel you can substitute and swap devices.
 

Install the project from scratch

Revision 142018-07-19 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 57 to 57
 Create a new WinCC project.
Copy the fwInstallation folder into the project folder and install the jcop fw components: fwCore, fwConfigurationDB, fwDIM and fwTrending.
Install the fwMiniDAQ component.
Changed:
<
<
Open the MiniDAQ fsm, click on Configure Subscriptions, Configure Multi, delete existing devices, create the RICH_TELL40 type. Open the HW tool and create the TELL40_RICH device type using the appropriate xml. Also create the RICHPDMDB device type using the appropriate xml.
Define the other devices in the MinIDAQ FSM view and click on subscribe all. The click on the Create FSM button.
>
>
Open the MiniDAQ fsm, click on Configure Subscriptions, Configure Multi, delete existing devices, create the RICH_TELL40 type and apply the default settings for each device. Open the HW tool and create the TELL40_RICH device type using the appropriate xml. Also create the RICHPDMDB device type using the appropriate xml.
Define the other devices in the MiniDAQ FSM view and click on subscribe all. The click on the Create FSM button.
 Install the fwRich component.
Open the fwRich_Configurator.pnl panel to create the new PDMDBs clicking on the Generate button.
Select the new devices in the table, select the firmwares, and click on the Update Selected button.

Revision 132018-07-18 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 55 to 55
 

Install the project from scratch

Create a new WinCC project.

Added:
>
>
Copy the fwInstallation folder into the project folder and install the jcop fw components: fwCore, fwConfigurationDB, fwDIM and fwTrending.
 Install the fwMiniDAQ component.
Changed:
<
<
Open the HW tool and create the RICHPDMDB device type using the appropriate xml.
>
>
Open the MiniDAQ fsm, click on Configure Subscriptions, Configure Multi, delete existing devices, create the RICH_TELL40 type. Open the HW tool and create the TELL40_RICH device type using the appropriate xml. Also create the RICHPDMDB device type using the appropriate xml.
Define the other devices in the MinIDAQ FSM view and click on subscribe all. The click on the Create FSM button.
 Install the fwRich component.
Deleted:
<
<
Open the MiniDAQ fsm, click on Configure Subscriptions, define the devices and click on subscribe all. The click on the Create FSM button.
 Open the fwRich_Configurator.pnl panel to create the new PDMDBs clicking on the Generate button.
Select the new devices in the table, select the firmwares, and click on the Update Selected button.
Click on the Generate FSM button.
Check that everything is ok within the fsm, i.e. try to take a run.
Deleted:
<
<
Install the fwTrending component.
 Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as distributed peers. (it is not needed if the config file is present in the fwRich.xml file)
Import the fwRichMiniDAQtop.dpl using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.

Revision 122018-07-17 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 39 to 37
 
 ./runScans.sh  "run" "outputname" "TAE" start_step stop_step 
Changed:
<
<
and then execute
>
>
where start_step is the start_value you set in the FE panel, and then execute
 
  ./makeScurveGraph "tree_#.root" "histo_#.root" "scanType" 
where tree_#.root corresponds to the output of runOffline (run99 in the example above) and "scanType" is "dac" or "th". Again the run number convention should be followed: tree_run99.root generates histo_run99.root.

Revision 112018-07-11 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 10 to 10
 

How to acquire data with the laser

Changed:
<
<
Turn the laser on (turn the driver key). Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.
>
>
Turn the laser on (turn the driver key). Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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 pclhcb116;
- 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.
 

How to acquire DAC scan

Revision 102018-07-10 - ValeriiaLukashenko1

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 12 to 12
  Turn the laser on (turn the driver key). Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.
Added:
>
>

How to acquire DAC scan

In DAQ box click FE. In Select action menu of FE box choose DAC scan, define channels configuration and click Apply. Then return to the main window and choose the correct step run configurations and the number of triggers on the bottom of the window. Click Apply and check if the number of triggers in the step run box equals the number of triggers in the TFC quick control menu. Then click START_RUN followed by START_TRIGGER in the MiniDAQ box. Watch the current step value in the step run block of the main window. If the value doesn't change for more than 20 seconds go to TFC and click PAUSE. After each run was finished go to MIniDAQ and click STOP_RUN.

 

How to process data

The offline software to process data is located for each Minidaq2 in :

Line: 32 to 36
  In case you are processing a DAC or threshold scan you have to first process the run with
Changed:
<
<
 ./runScans  "run" "outputname" "TAE" start_step stop_step 
>
>
 ./runScans.sh  "run" "outputname" "TAE" start_step stop_step 
  and then execute

Revision 92018-07-10 - RobertaCardinale

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 14 to 14
 

How to process data

Changed:
<
<
The offline software to process data is located in /home/Packages/offline_step/test for each Minidaq2. In order to process a run you execute in this folder: './runOffline.sh "run" "outputname" "TAE"'. The data for each Minidaq2 is located in /home/data. Each run name contains the date and time at which the run was acquired and the run run number; as common convention you should provide the run number as output name to allow easy traceability (for example run pcie40_20180614_105057_main_slot_05000_link_0_run_99.frg should be processed providing outputname=run99, therefore generating tree_run99.root as output file).
>
>
The offline software to process data is located for each Minidaq2 in :
 
Changed:
<
<
In case you are processing a DAC or threshold scan you have to first process the run with ./runOffline and then execute './makeScurveGraph "tree_#.root" "histo_#.root" "scanType" where tree_#.root corresponds to the output of runOffline (run99 in the example above) and "scanType" is "dac" or "th". Again the run number convention should be followed: tree_run99.root generates histo_run99.root.
>
>
 /home/Packages/offline_step/test 

The data for each Minidaq2 are located in

/home/data/

In order to process a normal run you execute in this folder:

./runOffline.sh "run" "outputname" "TAE" 

Each run name contains the date and time at which the run was acquired and the run run number; as common convention you should provide the run number as output name to allow easy traceability (for example run pcie40_20180614_105057_main_slot_05000_link_0_run_99.frg should be processed providing outputname=run99, therefore generating tree_run99.root as output file).

In case you are processing a DAC or threshold scan you have to first process the run with

 ./runScans  "run" "outputname" "TAE" start_step stop_step 

and then execute

  ./makeScurveGraph "tree_#.root" "histo_#.root" "scanType" 
where tree_#.root corresponds to the output of runOffline (run99 in the example above) and "scanType" is "dac" or "th". Again the run number convention should be followed: tree_run99.root generates histo_run99.root.
 

How to configure the PDMDB

Revision 82018-07-09 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 41 to 41
 Click on the Generate FSM button.
Check that everything is ok within the fsm, i.e. try to take a run.
Install the fwTrending component.
Changed:
<
<
Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as peers.
Import the MiniDAQ_richMod.xml using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.
>
>
Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as distributed peers. (it is not needed if the config file is present in the fwRich.xml file)
Import the fwRichMiniDAQtop.dpl using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.
 

Revision 72018-07-09 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 33 to 33
  Create a new WinCC project.
Install the fwMiniDAQ component.
Added:
>
>
Open the HW tool and create the RICHPDMDB device type using the appropriate xml.
 Install the fwRich component.
Open the MiniDAQ fsm, click on Configure Subscriptions, define the devices and click on subscribe all. The click on the Create FSM button.
Deleted:
<
<
Open the HW tool and create the RICHPDMDB device type using the appropriate xml.
 Open the fwRich_Configurator.pnl panel to create the new PDMDBs clicking on the Generate button.
Select the new devices in the table, select the firmwares, and click on the Update Selected button.
Click on the Generate FSM button.

Revision 62018-07-09 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 14 to 14
 

How to process data

Changed:
<
<
The offline software to process data is located in /home/Packages/offline_step/test for each Minidaq2. In order to process a run you execute in this folder: './runOffline.sh "run" "outputname" "TAE"'. The data for each Minidaq2 is located in /home/data. Each run name contains the date and time at which the run was acquired; as common convention you should provide the date and time as output name to allow easy trceability (for example run pcie40_20180614_105057_main_slot_05000_link_0_run_0.frg should be processed providing outputname=20180614_105057, therefore generating tree_20180614_105057.root as output file).

In case you are processing a DAC or threshold scan you have to first process the run with ./runOffline and then execute './makeScurveGraph "tree_#.root" "histo_#.root" "scanType" where tree_#.root corresponds to the output of runOffline and "scanType" is "dac" or "th". Again the date and time convention should be followed: tree_20180614_105057.root generates histo_20180614_105057.root.

>
>
The offline software to process data is located in /home/Packages/offline_step/test for each Minidaq2. In order to process a run you execute in this folder: './runOffline.sh "run" "outputname" "TAE"'. The data for each Minidaq2 is located in /home/data. Each run name contains the date and time at which the run was acquired and the run run number; as common convention you should provide the run number as output name to allow easy traceability (for example run pcie40_20180614_105057_main_slot_05000_link_0_run_99.frg should be processed providing outputname=run99, therefore generating tree_run99.root as output file).
 
Added:
>
>
In case you are processing a DAC or threshold scan you have to first process the run with ./runOffline and then execute './makeScurveGraph "tree_#.root" "histo_#.root" "scanType" where tree_#.root corresponds to the output of runOffline (run99 in the example above) and "scanType" is "dac" or "th". Again the run number convention should be followed: tree_run99.root generates histo_run99.root.
 

How to configure the PDMDB

Configure the master link GBTx

The bootstrapping of the master link GBTX is done via an external I2C master. This function is served by the trigger board via cables connected from the Tengja board to the PDMDB.

Changed:
<
<
%The trigger board connections can be found in the JRichTBTrigger topic.

Configuration of the PDMDB

Once the master link is configured, the control functions for the elementary cells should be usable immediately. After power-up the SCA should be initialised before any other control function is used. There is an Initialise button on the RICH panel to do this. It activates all the required SCA interfaces (I2C, GPIO, JTAG, ADC, DAC). At this point it is possible to configure the CLAROs by clicking the appropriate button on the panel. In general, when clicking buttons in the panel, check that the action has completed successfully (output in window on panel) before proceeding with the next operation.

The next step should be to configure the DTM modules. The DTMs are in pairs - DTM0 must always be configured before DTM1. You can configure all of the using the button: Configure all GBTx.

>
>
%The trigger board connections can be found in the JRichTBTrigger topic. Move to workspace 2 in lbminidaq2-13, open an ssh connection to lbrichtb (ssh -Y richtbuser@lbrichtb) and type tb-trigger. Extra->GBTX I2C. Read on both PDMDBs until the PauseForConfig state is reached,.Write->master3g.gbt on both. Read until the Idle state is reached on both PDMDBs.
 
Changed:
<
<
The firmware of the FPGAs can now be uploaded. There is a button
>
>

Troubleshootings

 
Changed:
<
<
Now the PDM is ready to receive TFC commands and to send data.
>
>
If a scan is stuck on the RUNNING state without receiving triggers from TFC, send the PAUSE command to the TFC partition. The current step will be lost but the scan will continue.
 
Added:
>
>

Install the project from scratch

 
Changed:
<
<

Troubleshootings

>
>
Create a new WinCC project.
Install the fwMiniDAQ component.
Install the fwRich component.
Open the MiniDAQ fsm, click on Configure Subscriptions, define the devices and click on subscribe all. The click on the Create FSM button.
Open the HW tool and create the RICHPDMDB device type using the appropriate xml.
Open the fwRich_Configurator.pnl panel to create the new PDMDBs clicking on the Generate button.
Select the new devices in the table, select the firmwares, and click on the Update Selected button.
Click on the Generate FSM button.
Check that everything is ok within the fsm, i.e. try to take a run.
Install the fwTrending component.
Modify the config file of the project to include the lbRichHV, lbRichDCS and lbRichECS as peers.
Import the MiniDAQ_richMod.xml using the Ascii Manager and append the RICH_DCS and RICH_HV partitions to the MiniDAQ fsm.
 
Deleted:
<
<
If a scan is stuck on the RUNNING state without receiving triggers from TFC, send the PAUSE command to the TFC partition. The current step will be lost but the scan will continue.
 

-- GiovanniCavallero - 2018-06-12 \ No newline at end of file

Revision 52018-07-06 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 6 to 6
 

Start the RICH Upgrade ECS

Changed:
<
<
The control of the setup is done via the lbRichECS project running on pclbrich02.
If the VNC connection is not already opened: type krdc & on the pclbrichtb Linux machine in the Syslab, Boomarks->History->pclbrich:VNCport.
If the FSM is not already opened: open a terminal and type ecs (move to workspace 6 to do it), then right click on RICH and take the FSM clicking on the lock symbol.
>
>
The control of the setup is done via the MultiMiniDAQ2 project running on lbminidaq2-13.
If the VNC connection is not already opened: type krdc & on the pclbrichtb Linux machine in the Syslab, Boomarks->History->lbminidaq2-13:VNCport.
If the FSM is not already opened: open a terminal and type fsm (move to workspace 6 to do it), then right click on MiniDAQ and take the FSM clicking on the lock symbol.
 

How to acquire data with the laser

Changed:
<
<
Turn the laser on (turn the driver key). From the top of the RICH partition open the Minidaq partition. Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.
>
>
Turn the laser on (turn the driver key). Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.
 

How to process data

Revision 42018-06-26 - GiovanniCavallero

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 16 to 16
  The offline software to process data is located in /home/Packages/offline_step/test for each Minidaq2. In order to process a run you execute in this folder: './runOffline.sh "run" "outputname" "TAE"'. The data for each Minidaq2 is located in /home/data. Each run name contains the date and time at which the run was acquired; as common convention you should provide the date and time as output name to allow easy trceability (for example run pcie40_20180614_105057_main_slot_05000_link_0_run_0.frg should be processed providing outputname=20180614_105057, therefore generating tree_20180614_105057.root as output file).
Changed:
<
<
In case you are processing a DAC scan you have to first process the run with ./runOffline and then execute './makeScurveGraph "tree_#.root" "histo_#.root" "dac"' where tree_#.root corresponds to the output of runOffline. Again the date and time convention should be followed: tree_20180614_105057.root generates histo_20180614_105057.root.
>
>
In case you are processing a DAC or threshold scan you have to first process the run with ./runOffline and then execute './makeScurveGraph "tree_#.root" "histo_#.root" "scanType" where tree_#.root corresponds to the output of runOffline and "scanType" is "dac" or "th". Again the date and time convention should be followed: tree_20180614_105057.root generates histo_20180614_105057.root.
 

How to configure the PDMDB

Line: 37 to 37
 Now the PDM is ready to receive TFC commands and to send data.
Changed:
<
<

How to take a run with an external trigger using miniDAQ1 + miniDAQ2

>
>

Troubleshootings

 
Changed:
<
<
In order to take a run using an external trigger (laser, beam, ...), it is necessary to use an hybrid system composed of a MiniDAQ1 and a MiniDAQ2. The MiniDAQ1 is able to receive the trigger from the outside world, it will propagate the TFC signal to the MiniDAQ2 system which is able to acquire the data. The connecction between MiniDAQ1 and MiniDAQ2 system is done through the fibre 6 in the bunch of fibre (1A) exiting from MiniDAQ1 which is connected to fibre 6 of the bunch of fibres which goes in the first outlet from the left (looking from the back) of the MiniDAQ2.
>
>
If a scan is stuck on the RUNNING state without receiving triggers from TFC, send the PAUSE command to the TFC partition. The current step will be lost but the scan will continue.
 
Deleted:
<
<
From the MiniDAQ2 Expert panel on the PDMDB panel, click on the button Restart control managers From the MiniDAQ2 FSM top panel send a RESET command

Navigate down through the FSM tree in TFC, SOL40_test (it refers to MiniDAQ1), Link0. In the Subdetector type text field, type EXT_TFC. Press return. The exclude the SOL40_test partition (clicking on the lock). Navigate down through the FSM tree in TFC, SODIN_test (it refers to MiniDAQ1), Core0. Tick TAE, External trigger and Limit trigger. Click on Apply Enable. Include in the tree SODIN_test2 (it refers to MiniDAQ2) partition. From the top of the FSM send a Configure command. Exclude (clicking on the lock) the SODIN_test2 (it refers to MiniDAQ2) partition. Navigate down in the SODIN_test2 partition, SODIN, Core0. Tick External TFC. Click on Apply Enable.

Now you will have only the SODIN_test and the SOL40_test2 partitions included in the tree.

In case of problems (e.g. the SOL40_test and/or the SODIN_test partitions are greyed out or they are DEAD) proceed as following:

- Do a Stop_All from the MiniDAQ2 Device Editor and Navigator (FSM tab) from the lbminidaq2-06 VNC connection;

- Move to the pclbrich02 VNC connection (MiniDAQ1) and check if the Gbt server is running (on workspace 1 there should be a connection to the ccpc1); probably it will be stuck, so the ccpc1 must be rebooted;

- Reload the firmware on the MiniDAQ1, open a connection to the ccpc1 using ssh root@ccpc1;

- type hostname. If the resulting hostname is CCPC1 in capital letters, type hostname ccpc1. Send the ecsdrv command (Bar0 and Bar2 must give successful messages, if not reboot the ccpc). Restart the GBT server

- type "echo $DIM_HOST_NODE" if the output is not "ccpc1" you have to type: export DIM_HOST_NODE=ccpc1

- move to pclbrich02 workspace 6, open the MiniDAQ Expert panel and check the GBT server connection and Configure subscriptions are green (if not something went wrong in the procedure and the steps before must be repeated)

- send a Stop_All from the MiniDAQ1 Device Editor and Navigator panel (FSM tab)

- Right click on Sol40_test partition and click on Start/Restart node. Do the same for the Sodin_test partition

- Move to the lbminidaq2-06 VNC connection and send a Start/Restart all from the Device Editor and Navigator FSM tab

- Now the commands sent through the MiniDAQ2 FSM top node should propagate correctly to the MiniDAQ1 TFC/Sol40_test and TFC/Sodin_test partitions

  -- GiovanniCavallero - 2018-06-12

Revision 32018-06-14 - SilviaGambetta

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 12 to 12
  Turn the laser on (turn the driver key). From the top of the RICH partition open the Minidaq partition. Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.
Added:
>
>

How to process data

The offline software to process data is located in /home/Packages/offline_step/test for each Minidaq2. In order to process a run you execute in this folder: './runOffline.sh "run" "outputname" "TAE"'. The data for each Minidaq2 is located in /home/data. Each run name contains the date and time at which the run was acquired; as common convention you should provide the date and time as output name to allow easy trceability (for example run pcie40_20180614_105057_main_slot_05000_link_0_run_0.frg should be processed providing outputname=20180614_105057, therefore generating tree_20180614_105057.root as output file).

In case you are processing a DAC scan you have to first process the run with ./runOffline and then execute './makeScurveGraph "tree_#.root" "histo_#.root" "dac"' where tree_#.root corresponds to the output of runOffline. Again the date and time convention should be followed: tree_20180614_105057.root generates histo_20180614_105057.root.

 

How to configure the PDMDB

Configure the master link GBTx

Revision 22018-06-14 - SilviaGambetta

Line: 1 to 1
 
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.
Line: 8 to 8
  The control of the setup is done via the lbRichECS project running on pclbrich02.
If the VNC connection is not already opened: type krdc & on the pclbrichtb Linux machine in the Syslab, Boomarks->History->pclbrich:VNCport.
If the FSM is not already opened: open a terminal and type ecs (move to workspace 6 to do it), then right click on RICH and take the FSM clicking on the lock symbol.
Added:
>
>

How to acquire data with the laser

Turn the laser on (turn the driver key). From the top of the RICH partition open the Minidaq partition. Exclude the MEP partition, check that the Enable in the Step Tun 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. Check that in the TFC box the Subdetector Type is RICH_TB2, if not select it from the menu on the right. Open the DAQ partition and send a RESET command to the TELL40 partition. Configure from the top of the Minidaq partition. Now you can send from the top a START_RUN followed by a START_TRIGGER. 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.

 

How to configure the PDMDB

Configure the master link GBTx

Revision 12018-06-12 - GiovanniCavallero

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="RichUpgrade"
This page contains information on how to configure the system and to take data in the SysLab.

Start the RICH Upgrade ECS

The control of the setup is done via the lbRichECS project running on pclbrich02.
If the VNC connection is not already opened: type krdc & on the pclbrichtb Linux machine in the Syslab, Boomarks->History->pclbrich:VNCport.
If the FSM is not already opened: open a terminal and type ecs (move to workspace 6 to do it), then right click on RICH and take the FSM clicking on the lock symbol.

How to configure the PDMDB

Configure the master link GBTx

The bootstrapping of the master link GBTX is done via an external I2C master. This function is served by the trigger board via cables connected from the Tengja board to the PDMDB. %The trigger board connections can be found in the JRichTBTrigger topic.

Configuration of the PDMDB

Once the master link is configured, the control functions for the elementary cells should be usable immediately. After power-up the SCA should be initialised before any other control function is used. There is an Initialise button on the RICH panel to do this. It activates all the required SCA interfaces (I2C, GPIO, JTAG, ADC, DAC). At this point it is possible to configure the CLAROs by clicking the appropriate button on the panel. In general, when clicking buttons in the panel, check that the action has completed successfully (output in window on panel) before proceeding with the next operation.

The next step should be to configure the DTM modules. The DTMs are in pairs - DTM0 must always be configured before DTM1. You can configure all of the using the button: Configure all GBTx.

The firmware of the FPGAs can now be uploaded. There is a button

Now the PDM is ready to receive TFC commands and to send data.

How to take a run with an external trigger using miniDAQ1 + miniDAQ2

In order to take a run using an external trigger (laser, beam, ...), it is necessary to use an hybrid system composed of a MiniDAQ1 and a MiniDAQ2. The MiniDAQ1 is able to receive the trigger from the outside world, it will propagate the TFC signal to the MiniDAQ2 system which is able to acquire the data. The connecction between MiniDAQ1 and MiniDAQ2 system is done through the fibre 6 in the bunch of fibre (1A) exiting from MiniDAQ1 which is connected to fibre 6 of the bunch of fibres which goes in the first outlet from the left (looking from the back) of the MiniDAQ2.

From the MiniDAQ2 Expert panel on the PDMDB panel, click on the button Restart control managers From the MiniDAQ2 FSM top panel send a RESET command

Navigate down through the FSM tree in TFC, SOL40_test (it refers to MiniDAQ1), Link0. In the Subdetector type text field, type EXT_TFC. Press return. The exclude the SOL40_test partition (clicking on the lock). Navigate down through the FSM tree in TFC, SODIN_test (it refers to MiniDAQ1), Core0. Tick TAE, External trigger and Limit trigger. Click on Apply Enable. Include in the tree SODIN_test2 (it refers to MiniDAQ2) partition. From the top of the FSM send a Configure command. Exclude (clicking on the lock) the SODIN_test2 (it refers to MiniDAQ2) partition. Navigate down in the SODIN_test2 partition, SODIN, Core0. Tick External TFC. Click on Apply Enable.

Now you will have only the SODIN_test and the SOL40_test2 partitions included in the tree.

In case of problems (e.g. the SOL40_test and/or the SODIN_test partitions are greyed out or they are DEAD) proceed as following:

- Do a Stop_All from the MiniDAQ2 Device Editor and Navigator (FSM tab) from the lbminidaq2-06 VNC connection;

- Move to the pclbrich02 VNC connection (MiniDAQ1) and check if the Gbt server is running (on workspace 1 there should be a connection to the ccpc1); probably it will be stuck, so the ccpc1 must be rebooted;

- Reload the firmware on the MiniDAQ1, open a connection to the ccpc1 using ssh root@ccpc1;

- type hostname. If the resulting hostname is CCPC1 in capital letters, type hostname ccpc1. Send the ecsdrv command (Bar0 and Bar2 must give successful messages, if not reboot the ccpc). Restart the GBT server

- type "echo $DIM_HOST_NODE" if the output is not "ccpc1" you have to type: export DIM_HOST_NODE=ccpc1

- move to pclbrich02 workspace 6, open the MiniDAQ Expert panel and check the GBT server connection and Configure subscriptions are green (if not something went wrong in the procedure and the steps before must be repeated)

- send a Stop_All from the MiniDAQ1 Device Editor and Navigator panel (FSM tab)

- Right click on Sol40_test partition and click on Start/Restart node. Do the same for the Sodin_test partition

- Move to the lbminidaq2-06 VNC connection and send a Start/Restart all from the Device Editor and Navigator FSM tab

- Now the commands sent through the MiniDAQ2 FSM top node should propagate correctly to the MiniDAQ1 TFC/Sol40_test and TFC/Sodin_test partitions

-- GiovanniCavallero - 2018-06-12

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