HW-Time-Slice Firmware-Filter Software vx2740 Steering Module Reports MVM MVM Vexos MVM-Bug listing MVM TRIUMF Local DS Prototype DS Cryogenic For Shifters BCIT-31 ChronoBox Run Operation DS-DAQ
  CERN DS-Proto0 read-only backup, Page 5 of 8  Not logged in ELOG logo
ID Date Author Type Categoryup Subject
  141   18 Nov 2019 03:03 Julie / Pascal / EdgarRoutineGeneralRandom Trigger runs suggested by Simone (4 runs ~ 200 k evts)

Run 1234  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

 Drift field 200 V/cm Extraction 3.78 kV/cm

SIPM HV: 65V

Number of events: 200k

Problem with DAQ at 40k, force to restart manually 

Run 1235  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

 Drift field 200 V/cm Extraction 3.78 kV/cm

SIPM HV: 65V

Number of events: 200k

Problem with DAQ at 70k, force to restart manually 

Run 1237  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

 Drift field 200 V/cm Extraction 3.78 kV/cm
 

SIPM HV: 65V

Number of events: 40k

Run 1238  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

 Drift field 200 V/cm Extraction 3.78 kV/cm

SIPM HV: 65V

Number of events: 40k

 

  142   18 Nov 2019 07:01 Julie / EdgarRoutineGeneralRandom Trigger runs suggested by Simone, S1 data

PDM 15 and PDM 19 strange behaviour, lot of noise

Run 1239  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1240  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1241 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1242 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1243 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1244 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1245 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1246 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1247 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1248 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1249 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1250 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1251 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

Run 1252 Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 200us, 100us pre-trigger

No field

SIPM HV: 65V

Number of events: 40k

 

  143   18 Nov 2019 07:20 Ben SmithRoutineGeneralDisk cleanup
Lazy logger has caught up with the backlog, and continues to transfer new files to darkside01 as they are written.
EOS currently contains data for runs 822-1201.

I have deleted the following runs from ds-proto-daq:
* runs < 700 that were taken with gzip compression
* runs 800-1100 that are available on EOS and darkside01

The following files remain:
* runs 700-800 that haven't been copied to EOS (but are on darkside01). If they're of interest, they should be copied to EOS.
* runs 1200+ that haven't been copied to EOS yet (but will be soon).

Disk usage has improved from 85% to 33%.
  144   19 Nov 2019 00:14 Pascal/JulieRoutineGeneralLaser run

Run 1252 Laser run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Laser Intensity: MAX

Threshold: external clock, laser set to 1kHz

Trace length: 12us, 5us pre-trigger

SIPM HV: 65V

Number of events: 100k

Low trigger rate - must restart manually 

 

 

Run 1253 Laser run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Laser Intensity: MAX

Threshold: external clock, laser set to 1kHz

Trace length: 12us, 5us pre-trigger

SIPM HV: 65V

Number of events: 100k

 

Run 1254 Laser run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Laser Intensity: MIN

Threshold: external clock, laser set to 1kHz

Trace length: 12us, 5us pre-trigger

SIPM HV: 65V

Number of events: 100k

  145   19 Nov 2019 00:57 Julie/ PascalRoutineGeneralRandom Trigger runs suggested by Simone, S1 data / 1ms

Run 1255  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 1000us, 500us pre-trigger

No field

SIPM HV: 65V

Number of events: 10k

 

Run 1256  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 1000us, 500us pre-trigger

No field

SIPM HV: 65V

Number of events: 10k

--> Stop after 1.7k evts (10:16)

 

Run 1257  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 1000us, 500us pre-trigger

No field

SIPM HV: 65V

Number of events: 10k

  146   19 Nov 2019 01:39 Julie / PascalRoutineGeneralRandom Trigger runs suggested by Simone, S1 data / 3ms

Run 1258  Physics run

Chronobox: External trigger Enable

Chronobox: Enable Channel [ch_enable]: 0x00000000

Threshold: external clock,  set to 50 Hz

Trace length: 3000us, 1500us pre-trigger

No field

SIPM HV: 65V

Number of events: 10k

--> stopped after 4.7k (end of the data taking at 11:00)

  148   20 Nov 2019 04:47 Sam HillRoutineGeneralIV Curve - warming up

Temp at start: 

A: 242.7K    B: 278.16K    C: 86.4K    D: 240.89K

Temp at End:

A: 248.87K    B: 278.24K    C: 86.37K    D: 247.75K

Took iv curves, data is on DAQ PC here: /home/dsproto/online/dsproto_sy4527/ivdata_191120

  151   14 Oct 2020 08:39 Tom ThorpeRoutineGeneralLog regarding MB2 removal from Proto-0

Drive folder with data files and some pictures:  https://drive.google.com/drive/folders/1Sr27kQTOO2kciBY7v-wYBP06tWLVEjiP

Lab notes @ CERN

11/10/2020

11:00 – First look at MB2.  Noticed on some of the PDMs that some of the tile PCB are more delaminated than others.  PDM 25 also had the FEB connectors more inserted than any other PDMs.  No other differences noticed.

11:30 – Connected SMU and switching matrix to MB2.  Power w/o steering module.  Checked that all channels match by running photo current tests with and w/o a flashlight on one corner.  Using the computer form Pisa with Labview scripts from Matteo.  Everything is ok.

12:00 – Replace plastic shields around Proto-0 for IV curve measurements in dark conditions.  PDM 1 breakdown is around 63V.  Looks ok.  PDM 2 is over 65V…. Seems high.

12:30 - PDM 6 People walking, disrupted the light conditions.  IV curve will be jagged.  Will go for lunch.  Closing door and turning off exterior lights.  Current will decrease

15:30 – IV curves look fine.  …/MB2_retriveval_CERN/data_files/iv_warm_1

16:00 – Took forward IV curves.  Saved as …/MB2_retriveval_CERN/data_files/forward_warm_1.  They look fine.  Checked old pictures of the lamination of the tile PCB and they have always varied in thickness, from before the LNGS LN test.

16:45 – Power FEBs on to look at noise spectra with 20V bias on the tiles.  

18:00 – PDM 2, 4, 6, and 25 have very odd power spectra.  George said they look like they’re not connected.

18:30 – Saving FFT to disk for analysis.  Saved as …/MB2_retriveval_CERN/data_files/noise_warm_1

19:00 – PDM 2,4,6 and 25 have one of the differential lines disconnected.  Using a light and looking at the differential outputs on the scope, this is obvious.  20V bias and FEBs powered at 5V.  Saved as …/MB2_retriveval_CERN/data_files/waveform_light_1

19:30 – Started another round of reverse IV curves in dark conditions.  Saved as …/MB2_retriveval_CERN/data_files/iv_warm_2

21:15 – IV still going.  EP will come back to shut off the LV supplies

 

12/12/2020

10:00 – Checking connectivity of all the differential lines.  One side of PDM 6 is not connected.  2, 4, and 25 are connected.  Doesn’t explain what we saw yesterday.  Channel 2 and 4 now are responding to light on both differential lines.  The only thing that has changed is unplugging the external signal cable and plugging it back in.  PDM 6 is the only one now not responding on both lines.

10:30 – Checking the power spectra.  PDM 4 and 6 are bad on both differential lines.  PDM 2 looks fine.  Seems to be non-repeatable.

11:00 – Disconnected the signal patch board from the finger strip.  Holding the patch and reconnecting the entire signal path and pinging now shows PDM 6 and 25 have one differential line disconnected.

11:30 – Checking the power spectra on every PDM channel directly from the fingerstrip with a flat cable.

12:30 – PDMs 2, 4, 6 power spectra from the fingerstrip look normal.  Both connections are there.  Light response is normal.  Channel 13, however, now has one differential line disconnected and the other looks abnormal.  Saving waveform data with 60Hz light on as waveform_light_2.

All of this is pointing to multiple connection issues…

15:00 – It looks like PDM 13 is disconnected from the fingerstrip, or at least it is pulled further away than the others.  This is likely also due to the removal of the patch.  PDM 2 also looks pulled a bit further.

15:30 – Unmounted MB2 and put on the stand to do an optical inspection.  The microscope didn’t allow a close enough look at the wirebonds to search for any broken ones.  A close look by eye didn’t reveal any obvious damage.

16:00 – Packed everything up.  MB2 needs a closer look, likely needs to be disassembled.

Attachment 1: forward_warm_1.png
forward_warm_1.png
Attachment 2: iv_warm_1.png
iv_warm_1.png
Attachment 3: iv_warm_2.png
iv_warm_2.png
  3   13 Dec 2018 11:02 ThomasRoutineHardwareTesting V1725 digitizers
Couple weeks of work documented in one elog...

V1725 serial numbers: 455, 392, 460, 462, 474

firmware: DPP-ZLE+

The 3818 kernel module not getting loaded on start-up... it is in /etc/rc.local, but not getting called

[root@ds-proto-daq ~]# grep 3818 /etc/rc.local 
# Load A3818 driver...
/sbin/insmod  /home/dsproto/packages/A3818Drv-1.6.0/src/a3818.ko

Called manually for now...

Reworked and cleaned up DEAP version of V1725 code
- Updated register map
- Removed smartQT code

Quick test: the V1725 seems to be getting busy at a maximum rate of 10kHz (with no samples being saved though).

Got preliminary documentation from CAEN for ZLE-plus firmware... posted here:

/home/dsproto/packages/CAEN_ZLE_Info

In particular, manual shows how the data structure is different for ZLE-plus data banks (as compared to V1720 ZLE data banks).

Fixed the /etc/rc.local setup so that the A3818 driver is loaded and mhttpd/mlogger is started on reboot.

Looking at V1725-ZLE register list.  I don't entirely understand how we are going to do the trigger outputs and the busy.  The manual makes it clear that the triggers from each pair of channels are combined together and send to the trigger logic.  So there should be 8 trigger primitives from the board.  The LVDS IO connector allows to configure groups of 4 outputs as being for either the trigger outputs or the busy/veto outputs.  So I guess I will configure the first two groups to output the trigger primitives and the third group to output the BUSY information.

Added code to do the ADC calibration; added extra equipment for reading out ADC temperatures periodically.

Renewed the lets-encrypt SSL certificate... but haven't set up automatic renewal yet...

[root@ds-proto-daq ~]# certbot renew --apache
[root@ds-proto-daq ~]# systemctl restart httpd

Analyzer program basically working.  Pushed to bitbucket:

https://bitbucket.org/ttriumfdaq/dsproto_analyzer/src
  6   17 Jan 2019 15:47 ThomasRoutineHardwareAdded raided HD to ds-proto-daq
Added pair of 10TB hard-drives in raid-1 to ds-proto-daq.  MIDAS data files will get written to this raid volume.

[dsproto@ds-proto-daq tmp]$ df -h /data
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0        9.1T  180M  8.6T   1% /data
[dsproto@ds-proto-daq tmp]$ cat /proc/mdstat 
Personalities : [raid1] 
md0 : active raid1 sdc1[1] sdb1[0]
      9766435648 blocks super 1.0 [2/2] [UU]
      [>....................]  resync =  0.9% (88214784/9766435648) finish=4372.8min speed=36886K/sec
      bitmap: 73/73 pages [292KB], 65536KB chunk

unused devices: <none>
  10   06 Feb 2019 14:12 PierreConfigurationHardwareExtended Trigger Time Tag (ETTT)
Confirmed this ETTT configuration is working.

                     ETTT Enabled [22..21] = b10
                      |
                      v
Data [0x811C] = 0x 00 4 D 013C

                ETTT Time [47..32]
                 |  Ch Mask[16..0]  Time[31..0]
                 |    TTTTTT           |
Header 1         v    v    v           v
0xa0001914 0x00 0025 ff 0xff1ca598 0xe9c6e8a1   < event 1
0xa0001914 0x00 0025 ff 0xff1ca599 0xe9c82e25   < event 2

dTime :  0x25e9c82e25 &#8722; 0x25e9c6e8a1 = 0x14584 => 83332
Time interval: 8ns  => 666.7e-6s => Freq: 1500Hz corresponding the current trigger rate

PAA
  12   08 Feb 2019 12:08 ThomasProblemHardwareInstalled Marco's A3818; didn't work
I installed Marco's A3818 PCIe card.  Didn't seem to work.  I got communication errors talking to link 2.  The
communication problems didn't happen right away, but happened once the run started.

I swapped the fibres going to port 2 and port 3 on the A3818.  The problem stayed with port 2.  So I conclude
that this A3818 module is no good.
  13   13 Feb 2019 16:45 PierreProblemHardwareA3818 from Marco
Checking again Marco's A3818:
- Port #2 (third from top of card) is acting up.
- change the SFP makes no difference.
- Symptoms: Get stuck on Rx/Tx.
- Need more investigation...
  16   05 Mar 2019 14:20 ThomasRoutineHardwareInstalled network card
I installed a PCIe 1Gbps network card and configured it as a private network.  The PC (ds-proto-daq) is
192.168.1.1.  I guess we can make the chronobox 192.168.1.2.

[root@ds-proto-daq ~]# ifconfig enp5s0
enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::bb27:5db:f778:d584  prefixlen 64  scopeid 0x20<link>
        ether 68:05:ca:8e:66:5c  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 27  bytes 4145 (4.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  memory 0xf72c0000-f72e0000  
  22   27 Mar 2019 08:57 PierreConfigurationHardwareCERN setup
Found that the Trigger out from the CB is on output1
Trigger / Not used
Clock   / Not used

Set frontend to use NIM in/out instead of TTL as there is a nice
NIM-TTL-NIM adaptor CAEN Nim module available
  44   25 Oct 2019 07:17 Simone StrackaRoutineHardwarePhotoelectronics activities on October, 24

Crew: Edgar Sanchez Garcia, Sam Hill, Simone Stracka, Tom Thorpe, Yi Wang

Morning: Tested photocurrents for MB2 on tabletop using SMU and Keithley switching matrix.  All measured between 1-10 microAmps.

Afternoon: Tested PDU mounting procedure with TPC assembled and with the mockup.  No showstoppers. This will be the procedure for installation
With the mockup on the table we double checked the resistances.  Confirmed all values are as before cooling indicating no additional damage to the wire-bondings.

 

  45   25 Oct 2019 07:44 Simone StrackaRoutineHardwareMB2 activities on October 25
Crew: Edgar Sanchez Garcia, Sam Hill, Simone Stracka, Tom Thorpe, Yi Wang

Morning: Set up equipment for the IV curve measurements. We enable the interlock system in the SMU in order to go higher than 42 V (handle with care).

Afternoon:  Measuring IV curves.  Note there is a voltage drop in the LV cable that needs to be compensated for.  

Chan 1 is set at +3.3V drawing 1.46A; sense line reads +2.39V
Chan 2 is set at -3.3V drawing 1.46A; sense line reads -2.39V
IV curves are scanning from 0-80V in 200mV steps w/ 100uA limit: elog:45/2 , elog:45/3
The two runs are visible ( elog:45/1 for color code and mapping )
Compare to elog:45/4 , obtained when probing individual tiles under more controlled light conditions
Attachment 1: TileFEBMapping_MB2.png
TileFEBMapping_MB2.png
Attachment 2: iv_warm_1.png
iv_warm_1.png
Attachment 3: iv_warm_1_zoom.png
iv_warm_1_zoom.png
Attachment 4: IndividualTileAtLNGS.png
IndividualTileAtLNGS.png
  47   27 Oct 2019 06:08 Simone StrackaConfigurationHardwareConverters installed in VME crate

People: Edgar, Simone

Installed differential to single-ended converters in VME crate, and turned crate back on. elog:47/2

Channel count in the converters is 0 to 15 starting from the low end. Wired according to:
left board, channels 0..15 = PDM slot 1..16
right board, channels 0..8 = PDM slot 17..25

N.B. V1725 board #0 logic level is set to TTL (boards #1, #2, #3 to NIM) elog:47/3

In ODB / Equipment / V1725_Data00 / Settings /  set Channel Mask to 0x1555 for all V1725 boards (enables channels 0 2 4 6 8 10 12)
(board 0 receives 7 PDM inputs, boards 1,2,3 receive 6 PDM each)

In https://ds-proto-daq.cern.ch/chronobox/ , set Enable Channel [ch_enable] = 0x3F3F3F7F , Channel Assignment [ch_assign] = 0x00393340.
9 central PDM's assigned to "top" group, external PDM's assigned to "bottom" group elog:47/1

Wiki instructions with the script to get the CDM back into a sensible state seem outdated. The variables seem fine, though ... 
[dsproto@ds-proto-daq ~]$ esper-tool read 192.168.1.5 cdm ext_clk
[49999632]
[dsproto@ds-proto-daq ~]$ esper-tool read 192.168.1.5 lmk pll1_ld
[1]
[dsproto@ds-proto-daq ~]$ esper-tool read 192.168.1.5 lmk pll2_ld
[1]

 

 

 

Attachment 1: PDMadcCh.png
PDMadcCh.png
Attachment 2: converters.jpg
converters.jpg
Attachment 3: adc0_ttl.jpg
adc0_ttl.jpg
  52   28 Oct 2019 15:10 Simone StrackaConfigurationHardwareLV for steering module and current status of CAEN mainframe

The HV board from Naples did not turn on: Yury gave it to the CAEN guys to check and/or bring back for replacement.

Yi and Luigi rented a new HV module (A1519). The HV module (A1520P) we used for tests of the I-V script is also present in the Mainframe (see below).
The first 24 channels (slots 0 and 1) are therefore HV. If the new HV does not show up on time we'll try and adapt the cables to work with A1519.

The A2517A module is LV. This is currently operated from the DAQ pc using CAEN_HVPSS_ChannelsController.jnlp (located in the Desktop/SteeringModule folder).
The three low voltage channels (0,1,2) should be turned on at the same time by setting Pw = ON.

Settings: 

Channel 0 and 1: I0Set = 2.0 A , V0Set = 2.5 V ,  UNVThr = 0 V, OVVThr = 3.0 V, Intck = Disabled
IMon = 1.44 (this depends on the illumination) , VMon = 2.48 V , VCon = 2.79 V

Channel 2: I0Set = 1.0 A , V0Set = 5.0 V ,  UNVThr = 0 V, OVVThr = 5.5 V, Intck = Disabled
IMon = 0.07 , VMon = 4.998 V , VCon = 5.02 V

In case the channels trip they cannot be ramped back up unless the alarms are cleared.

 

Attachment 1: CAENmainframe.png
CAENmainframe.png
  55   01 Nov 2019 06:50 Alex KishConfigurationHardwareTurn off the fields
Ramp down the fields, in 200V steps.
Nominal values:
1st ring: 4180 V
wire gate: 3780 V
cathode: 6180 V
ELOG V3.1.4-cb3afcd8