-- SebastianGrinstein - 2014-12-07


See also the powering-modules category of the IFAE elogs. Note: to access the elog from outside you need to use VPN tunnelling.

USBPix FEI3 Connectivity


fei3_usbpix_setup.png


power.png

USBpix FEI4 with adaptor card

With flex devices

Connectivity-FEI4flex-adaptercard.png

With PCB devices and RJ45 cable

Connectivity-FEI4pcb-adaptercard.png

With PCB and flat cable

Connectivity_flatcable.png

USBPix FEI4 with BIC

With flex devices

Connectivity-FEI4flex-BIC.png

With PCB devices


Connectivity-FEI4pcb-BICpng.png

USBPix QUAD with BIC


Screen_shot_2014-12-07_at_5.42.41_PM.png


Screen_shot_2014-12-07_at_5.40.10_PM.png

Telescope Setup

Telescope setup is identical to USBpix-FEi4 pcb connection

pyBAR with USBPIX

  • The connection of an FEI4 PCB to USBpix to be read by pyBAR is the same as STcontrol with PCB devices:
    pybar_1.png</verbatim>
  • Note:
    • VDDA: 1.5V (350mA after scan)
    • VDDD: 1.2V (150mA)
    • 2V for the USBpix adaptor card. This is taken from the -25V supply (to -0.8V) and the 1.2V of the digital, using only the E3631A supply.

HSIO2 setup

Preparations on Linux server:

- Follow instructions on https://twiki.cern.ch/twiki/bin/view/Atlas/RCEGen3Development and https://twiki.cern.ch/twiki/bin/view/Atlas/RCEGen3PixelApplication for installation

- For DHCP: define rce# under /etc/hosts the way you set it in your dhcp (/etc/dhcp/dhcpd.conf ). Note: the rce# which is used under /etc/hosts will define the number you have to use in cosmicGui and calibGui for your rce!

Starting routine:

1. Starting calibserver on HSIO2:

- ssh to HSIO2 (pwd root - this is in case of the IFAE HSIO2 at the IFAE Laptop - other setups will vary).

ssh root@rce2

- If the host RCE2 is not found, try to restart the DHCP server:

sudo service dhcpd restart

- Export required libraries. Mandatory, but not required on IFAE HSIO2 because it is done on startup (c.f. .bashrc)

ssh root@rce2 export PATH=/root/pixelrce/bin:$PATH; export LD_LIBRARY_PATH=/root/pixelrce/lib:$LD_LIBRARY_PATH

- Start the caliberver on the HSIO2 and leave it running. If it crashes at some point, you have to restart it.

calibserver

In case you can not start calibserver because it is already running (on another instance), you can kill it by using:

kill $(ps aux | grep 'calibserver' | awk '{print $2}')

2. Starting calibGui or cosmicGui on Linux server:

- Set up environment (not required on IFAE Laptop since its in .bashrc):

cd ~/daq/rce
source scripts/setup-gen3.sh

- start calibGui or cosmicGui:

calibGui
cosmicGui

Source code for HSIO2 scans:

- Connect to HSIO2 (either physically or via ssh: ssh -X pixels@172NOSPAMPLEASE.16.15.16) and look at file:

vim /home/pixels/pixelrce/rce/pixelrce/server/PixScan.cc

HSIO2 lemo connectors:

HSIO2_lemoConnectors.jpg

1-4: PMT inputs for scintillators.
12, 11: Trigger inputs 1 and 2 (TTL - used 12 for Testbeam trigger with Barcelona Triggerboard - called ext1 in cosmicGui)
10: L1A out
9: busy out
8: reset (short to GND for rebooting HSIO)
Rest: Debugging/unused.

Troubleshooting:

1. All scans crash:

- probably connection to FEI4 is faulty. Check RCE number, powering of modules, position of ethernet cables (+ In & Outlink), GA in config files.

2. Noise / Threshold scans crash:

- If you connected a lot of modules try to do it only with ~3 modules. Datarate might be too high

3. Connection to HSIO2 via ssh is not stable / loses packages:

- Try cooling the DTM board.

H35 setup

Powering information:

8 Pin molex naming scheme (looking on PCB):

1 2 3 4

5 6 7 8

1. "normal" powering:

Set jumper J5 and J8 to 3.3V reg and 2.5V reg.

Pin 4 to GND, Pin 8 to 5.6V (2.0 A compliance)

2. External powering (Karlsruhe irradiated modules):

Remove J6 jumper and use a cable to short 3.3V ext from J5 with the pin on J6 thats facing away of J5.

Pin 2,3,4 to GND, 6 to 5.7 (or higher) V, 7 to 3.4 (or higher) V

Starting GUI:

1. Start server on ZYNQ board:

In /home/pixels/H35client/firmware do: "source connectToServer.sh 1" (number depending on MAC address/IP of ZYNQ board) -> Yes to reset credentials -> user/pwd: root/root

2. Start H35 readout GUI:

In /home/pixels/H35client/build do: "./H35client".

RD53A with YARR and BDAQ53

See detailed instruction for RD53A module characterization here: https://travelling-module.readthedocs.io/en/latest/procedure/

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng Connectivity-FEI4flex-BIC.png r1 manage 1365.4 K 2014-12-22 - 11:43 IvanLopezPaz Connectivity set-up
PNGpng Connectivity-FEI4flex-adaptercard.png r1 manage 957.7 K 2014-12-22 - 11:43 IvanLopezPaz Connectivity set-up
PNGpng Connectivity-FEI4pcb-BICpng.png r1 manage 1259.4 K 2014-12-22 - 11:43 IvanLopezPaz Connectivity set-up
PNGpng Connectivity-FEI4pcb-adaptercard.png r1 manage 1261.0 K 2014-12-22 - 11:43 IvanLopezPaz Connectivity set-up
PNGpng Connectivity_flatcable.png r1 manage 523.4 K 2015-04-07 - 16:13 DavidVazquezFurelos1 Connectivity set-up
JPEGjpg HSIO2_lemoConnectors.jpg r1 manage 541.9 K 2016-05-09 - 11:00 FabianAlexanderFoerster HSIO2 lemo connector numbering
PNGpng Screen_shot_2014-12-07_at_5.40.10_PM.png r1 manage 46.1 K 2014-12-07 - 18:14 SebastianGrinstein  
PNGpng Screen_shot_2014-12-07_at_5.42.41_PM.png r1 manage 517.0 K 2014-12-07 - 18:14 SebastianGrinstein  
PNGpng fei3_usbpix_setup.png r1 manage 1591.9 K 2014-12-07 - 15:12 SebastianGrinstein  
PNGpng power.png r1 manage 479.3 K 2014-12-07 - 15:13 SebastianGrinstein  
PNGpng pybar_1.png r1 manage 911.8 K 2015-05-19 - 11:35 SebastianGrinstein  
Edit | Attach | Watch | Print version | History: r13 < r12 < r11 < r10 < r9 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r13 - 2020-12-02 - StefanoTerzo
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

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