ID |
Date |
Author |
Type |
Category |
Subject |
41
|
16 Jul 2019 03:17 |
Marco Rescigno | Routine | General | run 772, scintillation events triggering on all channels |
Majority of 5, threshold at 1000 ADC count, 13 channels enabled (10 trigger signals) 50 Hz, 30 us window.
58 k events recorded. |
42
|
16 Jul 2019 03:51 |
Marco Rescigno | Routine | General | run 773, scintillation events triggering on all 24 channels |
Majority of 5, threshold at 1000 ADC count, 24 channels enabled (16 trigger signals) 100 Hz, 30 us window.
38 k events recorded. |
43
|
16 Jul 2019 03:53 |
Marco Rescigno | Routine | General | run 774, scintillation events triggering on all 24 channels and 200 us window |
Majority of 8, threshold at 1000 ADC count, 24 channels enabled (16 trigger signals) 10 Hz, 200 us window, trigger at 9.5 microseconds.
10 k events recorded.
By direct inspection pileup seems at the 10 % level in the 200 us window. |
Attachment 1: PileupEvent.png
|
|
44
|
25 Oct 2019 07:17 |
Simone Stracka | Routine | Hardware | Photoelectronics 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 Stracka | Routine | Hardware | MB2 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
|
|
Attachment 2: iv_warm_1.png
|
|
Attachment 3: iv_warm_1_zoom.png
|
|
Attachment 4: IndividualTileAtLNGS.png
|
|
46
|
26 Oct 2019 07:33 |
Sam Hill | Problem | Software | Test of IV Script |
People: Simone, Sam, Tom, Edgar
Tested IV curve python script that runs using MIDAS. Measured resistance consistant with resistor specification. elog:46/1
The resistance is attached to ch11, and we called the script (channels go from 0 to 24):
chnum=11 ; python3 iv_curve.py --no_steering --caen_chan $chnum --stop_v 3 --step_v 0.001 --filename ivcurve_`date +%s`_$chnum.txt
Issues:
No readout of trip condiotion therefore python script overides power supply trip and attemps to bring back voltage to next value. Potentially dangerous. Script only terminates with the final voltage value. See attached plot elog:46/1
Script terminated with error message:
Traceback (most recent call last):
File "iv_curve.py", line 287, in <module>
iv.run()
File "iv_curve.py", line 269, in run
self.set_caen_and_wait_for_readback(voltage)
File "iv_curve.py", line 223, in set_caen_and_wait_for_readback
raise RuntimeError("CAEN HV didn't respond to request to set voltage to %s; latest readback voltage is %s" % (voltage, rdb))
RuntimeError: CAEN HV didn't respond to request to set voltage to 2.976; latest readback voltage is 0.052000001072883606
|
Attachment 1: IV_curve_29K.png
|
|
47
|
27 Oct 2019 06:08 |
Simone Stracka | Configuration | Hardware | Converters 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
|
|
Attachment 2: converters.jpg
|
|
Attachment 3: adc0_ttl.jpg
|
|
48
|
28 Oct 2019 06:28 |
Simone Stracka | Problem | Software | Need python3 package tkinter on DAQ pc |
We need python3 package tkinter installed on ds-proto-daq in order to run the steering module GUI.
I don't have root privileges.
|
49
|
28 Oct 2019 08:33 |
Ben Smith | Problem Fixed | Software | Need python3 package tkinter on DAQ pc |
I have installed the python3-tkinter package from yum. I checked that "import tkinter" works from a python3 prompt. |
50
|
28 Oct 2019 14:10 |
Ben Smith | Problem Fixed | Software | Converters installed in VME crate |
> V1725 board #0 logic level is set to TTL (boards #1, #2, #3 to NIM)
There was a problem with CMakeLists for the V1725 driver, and the frontend was only connecting to 1 board. This is now fixed, and all the boards should have the same (TTL) logic level. |
51
|
28 Oct 2019 14:56 |
Simone Stracka | Problem | Software | Issues with network configuration for steering module |
We have tried to connect the steering module to the DAQ pc via Luigi's USB-Ethernet adapter.
That does not appear to work. We'll receive another USB-Ethernet adapter tomorrow, and it should be configured to have a static IP address : 192.168.121.1 and NetMask 255.255.255.0
For the time being, we are using Tom's laptop.
|
52
|
28 Oct 2019 15:10 |
Simone Stracka | Configuration | Hardware | LV 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
|
|
53
|
01 Nov 2019 06:07 |
Ben Smith | Problem Fixed | Software | Restoration of network settings |
For a few days we were unable to access ds-proto-daq remotely. We were also unable to reach the outside world from ds-proto-daq.
To gain more control over the network settings, I have disabled the automatic configuration by dracut. I created the file /etc/dracut.conf.d/no-ifcfg.conf with the single line `omit_dracutmodules+="ifcfg"`.
I then set the following contents in /etc/sysconfig/network-scripts:
# cat ifcfg-enp0s31f6
NAME=enp0s31f6
DEVICE=enp0s31f6
ONBOOT=yes
NETBOOT=yes
UUID=4887c207-13da-4424-8307-116ef2163fd8
IPV6INIT=no
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
HWADDR=18:31:BF:2E:00:12
BOOTPROTO=dhcp
IPV6_PRIVACY=no
AUTOCONNECT_PRIORITY=1
DNS1=137.138.16.5
DNS2=137.138.17.5
PEERDNS=no
# cat ifcfg-enp5s0
TYPE=Ethernet
PROXY_METHOD=None
BROWSER_ONLY=no
BOOTPROTO=static
DHCPCLASS=
IPADDR=192.168.1.1
PREFIX=24
NETMASK=255.255.255.0
GATEWAY=
DEFROUTE=no
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
HWADDR=68:05:CA:8E:66:5C
ONBOOT=yes
DEVICE=enp5s0
Network settings are now correct, and have survived a reboot. We are able to talk to both the local network and the outside world. We are also able to connect to ds-proto-daq from lxplus, and via the web proxy. |
54
|
01 Nov 2019 06:15 |
Ben Smith | Problem Fixed | Software | Restoration of elog |
After booting, the elog was only showing logs from before July, and was missing the "For Shifters" category. It appears we were loading the incorrect config file. The running command was:
/usr/sbin/elogd -D -c /etc/elogd.cfg -s /usr/share/elog/ -d /var/lib/elog/logbooks/
while it should have been:
/usr/sbin/elogd -D -x -c /home/dsproto/online/elog/elogd.cfg -s /usr/share/elog
rc.local was set up to run the latter command, but rc.local~ had the prior version. Perhaps that was being picked up. I have deleted the rc.local~ version, and will see if elog starts correctly next time we reboot. |
55
|
01 Nov 2019 06:50 |
Alex Kish | Configuration | Hardware | Turn off the fields |
Ramp down the fields, in 200V steps.
Nominal values:
1st ring: 4180 V
wire gate: 3780 V
cathode: 6180 V |
56
|
01 Nov 2019 09:06 |
Alex Kish | Routine | General | run 826, zero-field with gas pocket |
Gas pocket: ON
Fields: OFF
Threshold: 400 ADCc below baseline
Threshold extend: 5x16 = 80ns
Comment: Noise appeared on event 4200 |
58
|
01 Nov 2019 09:49 |
Alex Kish | Configuration | Hardware | Turn off the fields |
Ramp UP the fields, in 100V steps.
Nominal values:
1st ring: 4180 V
wire gate: 3780 V
cathode: 6180 V |
60
|
01 Nov 2019 10:56 |
Alex / Marco | Routine | General | run 829, with nominal fields |
Gas pocket: ON
Fields: ON
Threshold: 200 ADCc below baseline
Threshold extend: 5x16 = 80ns
Comment: Noise appeared on event 48500 |
61
|
03 Nov 2019 07:46 |
Alex Kish | Routine | General | run 833, with nominal fields |
Gas pocket: ON
Fields: ON (wire gate 3780 V, 1st ring 4180 V, cathode 6180 V)
Threshold: 200 ADCc below baseline
Threshold extend: 5x16 = 80ns
TPC Pressure: 242 mbarg
SiPM HV: 65V
Comment: noise conditions good, 1e5 evts |
62
|
03 Nov 2019 08:15 |
Alex Kish | Routine | General | run 834, drift field ON, extraction OFF |
Gas pocket: ON
Fields: drift field ON (1st ring 4180 V, cathode 6180 V), extraction field OFF (wire gate 0 V)
Threshold: 200 ADCc below baseline
Threshold extend: 5x16 = 80ns
TPC Pressure: 244 mbarg
SiPM HV: 65 V
Comment: noise conditions good, 1e5 evts |