UPDATES ON THE WORK DONE ON THE MINI-TIME PROJECTION CHAMBER Mayra - - PowerPoint PPT Presentation

updates on the work done on the mini time projection
SMART_READER_LITE
LIVE PREVIEW

UPDATES ON THE WORK DONE ON THE MINI-TIME PROJECTION CHAMBER Mayra - - PowerPoint PPT Presentation

UPDATES ON THE WORK DONE ON THE MINI-TIME PROJECTION CHAMBER Mayra Lopez-Thibodeaux 05-23-13 Trigger 2 Inside TPC Vessel Trigger = A signal blob of electrons over threshold makes it to the FEI4 This tells the FEI4 system to read out


slide-1
SLIDE 1

UPDATES ON THE WORK DONE ON THE MINI-TIME PROJECTION CHAMBER

Mayra Lopez-Thibodeaux

05-23-13

slide-2
SLIDE 2

Trigger

Trigger =

 A signal blob of electrons over

threshold makes it to the FEI4

 This tells the FEI4 system to read

  • ut this signal as an event

Note that the chip will trigger even if a single pixel makes it over threshold. Then the surrounding pixels will be read out too.

Inside TPC Vessel

2

slide-3
SLIDE 3

Trigger Control in STControl

3

Trigger Control per run in Basic Par’s tab

The trigger is control for every run by several functions in STControl at the Basic Par’s tab under the PixScan Panel  “Trigger type” and “Type of event” count are important

slide-4
SLIDE 4

Different External Trigger Set Ups Were Tried

4

The FEI4 internal trigger was set up externally by connecting it from the chip board to the USBpix board’s ground and HitOr pins Also, an external trigger was set up to be done by the scope connected to the x-ray signal

slide-5
SLIDE 5

Event Trigger type Necessary in STControl

 With no trigger event count, data from more than one x-ray event might be

gathered

 The internal self trigger source scan under trigger type does not seem to

follow the number of event count given, but keeps triggering until it is stopped

5

Internal self trigger source scan occupancy plot under data record event count (1 event at high rate) Internal self trigger source scan occupancy plot under trigger event count

slide-6
SLIDE 6

Testing of the FEI4 Internal Trigger

6

What 5 events should look like

The HitOr from another FEI4 tested for five events under gave a signal output on the scope similar to this picture

 The test vessel was opened to test

  • ur FEI4 HitOr trigger directly

 Its signal output was consistent with

the tests done previously

 We concluded this function of our

FEI4 is broken The FEI4 being tested directly

HitOr trigger being tested for 5 events

HitOr trigger signal on the scope

slide-7
SLIDE 7

Solution: Integration of another FEI4

 The avalanche detector consisting of

two GEMs in series above the pixel chip with thin insulating spacers in between GEMs and between the pixel chip and the bottom GEM will have to be taken apart

 Another FEI4 will be mounted and

wired bonded on our pixel chip board

7

The Double GEM and FEI4 package at the bottom of the field cage

Side view illustration of the detector package

slide-8
SLIDE 8

Future Plans

 Data acquisition using the TESTBEAM external trigger

source scan in STControl will be used

 This scan does write the raw data

 Most probably, the internal trigger will be set up

externally by connecting it to the HitOr pin of the USBpix

8

External Trigger TESTBEAM_EUDAQ Source Scan