ID |
Date |
Author |
Category |
Subject |
51
|
Wed May 11 23:34:39 2022 |
Patrick, Carsten | Detectors | Particle Detectors / Scraper positions |
Voltages of particle detectors off.
Scraper positions:
GE02DS3HG: -8
GE01DD2AG: -25
GE01DD2IG: 6
GE02DD2_G: -30 |
77
|
Mon May 16 22:57:40 2022 |
Patrick, Kristian, David, Ruijiu | Detectors | Switched off nitrogen |
Background counts with nitrogen and air.
Less multiphoton events with air (see pictures, histogram extended to 30 with nitrogen).
Read in 4_Lasersteps/Counts
nitrogen:
XUV: 15e4
Middle: 8e4
North: 9e4
air:
XUV: 13e4
Middle: 1.2e4
North: 0.7e4 |
Attachment 1: 2022-05-16_PMTs_after_nitrogen_off.png
|
|
80
|
Tue May 17 10:38:44 2022 |
Konstantin | Detectors | PMT North changed |
PMT located at the northern window was again replaced by the narrow-band PMT (ET Enterprise type 9423 SB, SN: 650). |
85
|
Mon May 30 01:13:40 2022 |
Konstantin, Max, Patrick | Detectors | XUV-Detector voltage off |
XUV-Detector shows up to 100 kHz and, therefore, was turned off. |
88
|
Mon May 30 08:35:41 2022 |
Kristian, Simon, Ken, Ragan | Detectors | Changed PMT North |
We did not see any signal at PMT North which was the narrowband PMT. Changed it to the old solar blind PMT. Now we see the resonance. It is about 3 times larger as PMT middle, most likely because of the larger window. CFD threshold was set. I also increased the CFD threshold for PMT middle slightly.
HV for PMT North: 1600 V |
89
|
Mon May 30 09:28:43 2022 |
Ken, Kristian, Simon, Ragan | Detectors | XUV-Detector |
9:27 XUV-Detector is running again.
-5V cathode, 8A main coil, 2.4A sec.coil
Rate without beam was:
Park position: ~300Hz
Pump beneath the detector is now shut down, new rate: <10Hz.
Threshold was adjusted to trigger only on "nice" signals.
Rate with beam in and laser:
Park position: ~400Hz
147mm: ~1.4kHz
with 2e6 ions |
101
|
Tue May 31 19:37:30 2022 |
Carsten, Max, Wilfried | Detectors | SASZ and NASZ voltages switched off |
SASZ and NASZ voltages were switched off bevor we went back to 209Bi. Laser beam stabilization turned off. |
103
|
Tue May 31 21:08:04 2022 |
Carsten, Max | Detectors | XUV detector automation off |
We deactivated the automation of the XUV detector. It stays out now. |
109
|
Fri Jun 3 12:01:17 2022 |
Danyal | Detectors | switched off XUV detector on 1 June ~17:00 |
I have switched off the XUV detector on 1 June at about 17:00.
The high voltages of the MCP (in ESR laser lab) were turned off and inside the ESR cave the power supplies (coils and cathode) and the crate were turned off.
Also the new "control box" for the detector was switched off.
And I checked (visually) that the XUV detector (and the Cu detector too) were indeed "moved out".
Danyal |
5
|
Tue Apr 26 16:28:14 2022 |
Carsten | DAQ | Cable of Bunch HF disconnected and 1.995Mhz signal connected for DAQ tests |
see subject. |
8
|
Wed May 4 22:45:12 2022 |
Carsten, Sebastian | DAQ | Q-Switch Signal (ch15) fixed |
The "dead" Q-Switch signal was converted
two times... This explains why in the
Thorium experiment the Q-Switch signal
(ch15) was empty.
First conversion from TTL to NIM in the
ESR Laserlab and unfortunately the signal
was plugged in a second Level Adapter as
TTL in
the Messhütte and was "again" converted
into a NIM for DAQ1/2.
Now the Q-Switch is converted from TTL to
NIM in the ESR Laserlab. The NIM is
afterwards guided through a Logic Fan
In/Out to the 2 DAQs. |
12
|
Fri May 6 10:30:23 2022 |
Sebastian | DAQ | laser busy / dye out signal fixed |
Solution for a working laser busy / dye out signal was to disable the FCU and set the FCU status to "False" (see attached picture).
Remark: FCU unit will not be used for Bismuth experiment! |
Attachment 1: CobraFix_LaserBusy.PNG
|
|
13
|
Fri May 6 10:35:06 2022 |
Sebastian | DAQ | laser step complete cabling changed |
I changed the laser step complete cabling from a quad coinc (see attached picture) to a Logic Fan In / Fan out (same as laser scan complete).
The "detour" through the quad coinc yielded to a very short laser step complete signal of ~500ns...
Due to the change it is now ~15µs long and has the same length as the laser scan complete signal (~15µs). |
Attachment 1: stepComplete_beforeChange_QuadCoincCabling.PNG
|
|
20
|
Mon May 9 17:01:02 2022 |
Carsten | DAQ | directories / paths / comments / reduction factors /startup.scom files for the 2 DAQs |
DAQ1 (original):
-user atplaser
-runs on lxg1050
-data in lxg1297:/data.lcoal2/208Bi
-go4 in ~/go4/208Bi
-mbs /esr/usr/atplaser/mbsrun/208Bi
Since the Go4 Code is still under development (clean up etc.), I still plan to submit regular updates, the last version before is always in ~go4/208Bi
It is planne that all essentialy settings can be done via the automatically loaded script files SetParamters.C and SetConditions.C, so that no recompilation (and change of code) is required (work in progress).
DAQ2 (new / enhanced):
additional 25ps TDC and ADC
-user stoe_exp
-runs on lxg0155
-data in lxg0155:/data.lcoal2/E128
-go4 in ~/E128
-mbs /esr/usr/stoe_exp/E128
There are no two different startup-files on each system (startup.scom and startup0.scom)
i.e. @startup0 in mbs -> Starts everything WITHOUT file writing
and @startup in mbs -> Starts everything WITH file writing (including onnect rfio and open file). For this, rawDispRFIO64, has to be started (locally __IN__ the data directory).
Please note that the different path and file names are on purpose, so that they can be distinguished after the run. |
21
|
Mon May 9 17:14:02 2022 |
Carsten | DAQ | NTCAP DAQ |
The NTCap DAQ computer in the HKR (Schottky logbook) is started, and all preparations for data taking (mounting of NAS etc.) are done.
Parameters for NTCAP DAQ will be adjusted as soon as beam is available. |
23
|
Mon May 9 19:05:17 2022 |
Wilfried | DAQ | Q-Switch signals + 0.5 ms and +1 ms in VUPROM |
We have generated two additional signals which are fed into two VUPROM channels:
Q-Switch + 0.5 ms --> channel 9
Q-Switch + 1.0 ms --> channel 10
(channel numbering 0-15)
The delays are generated by the two channels of a DGG222 |
31
|
Tue May 10 22:29:45 2022 |
Jan Glorius | DAQ | DAQ2 shaper settings |
Attached are the MSCF shaper settings applied on Tue May 10 at 22:30. |
Attachment 1: setting_e128.v1
|
1652214506
Tue May 10 22:28:26 CEST 2022
e127pi:mrcc:mscf2:getGainCommon 15
e127pi:mrcc:mscf2:getShapingTimeCommon 0
e127pi:mrcc:mscf2:getThresholdCommon 200
e127pi:mrcc:mscf2:getPzCommon 255
e127pi:mrcc:mscf2:getGain1 15
e127pi:mrcc:mscf2:getGain2 10
e127pi:mrcc:mscf2:getGain3 15
e127pi:mrcc:mscf2:getGain4 15
e127pi:mrcc:mscf2:getShapingTime1 0
e127pi:mrcc:mscf2:getShapingTime2 0
e127pi:mrcc:mscf2:getShapingTime3 0
e127pi:mrcc:mscf2:getShapingTime4 1
e127pi:mrcc:mscf2:getThreshold1 255
e127pi:mrcc:mscf2:getThreshold2 3
e127pi:mrcc:mscf2:getThreshold3 4
e127pi:mrcc:mscf2:getThreshold4 255
e127pi:mrcc:mscf2:getThreshold5 222
e127pi:mrcc:mscf2:getThreshold6 2
e127pi:mrcc:mscf2:getThreshold7 20
e127pi:mrcc:mscf2:getThreshold8 255
e127pi:mrcc:mscf2:getThreshold9 2
e127pi:mrcc:mscf2:getThreshold10 10
e127pi:mrcc:mscf2:getThreshold11 255
e127pi:mrcc:mscf2:getThreshold12 255
e127pi:mrcc:mscf2:getThreshold13 100
e127pi:mrcc:mscf2:getThreshold14 255
e127pi:mrcc:mscf2:getThreshold15 255
e127pi:mrcc:mscf2:getThreshold16 255
e127pi:mrcc:mscf2:getPz1 100
e127pi:mrcc:mscf2:getPz2 100
e127pi:mrcc:mscf2:getPz3 100
e127pi:mrcc:mscf2:getPz4 100
e127pi:mrcc:mscf2:getPz5 100
e127pi:mrcc:mscf2:getPz6 100
e127pi:mrcc:mscf2:getPz7 100
e127pi:mrcc:mscf2:getPz8 100
e127pi:mrcc:mscf2:getPz9 100
e127pi:mrcc:mscf2:getPz10 100
e127pi:mrcc:mscf2:getPz11 100
e127pi:mrcc:mscf2:getPz12 100
e127pi:mrcc:mscf2:getPz13 100
e127pi:mrcc:mscf2:getPz14 100
e127pi:mrcc:mscf2:getPz15 100
e127pi:mrcc:mscf2:getPz16 100
e127pi:mrcc:mscf2:getSingleChMode 1
e127pi:mrcc:mscf2:getRcMode 1
e127pi:mrcc:mscf2:getAutoPZ 18
e127pi:mrcc:mscf2:getMultiplicityHi 8
e127pi:mrcc:mscf2:getMultiplicityLo 0
e127pi:mrcc:mscf2:getSumTrgThresh 18
e127pi:mrcc:mscf2:getBlrOn 1
e127pi:mrcc:mscf2:getCoincTime 121
e127pi:mrcc:mscf2:getThreshOffset 70
e127pi:mrcc:mscf2:getShaperOffset 35
e127pi:mrcc:mscf2:getBlrThresh 25
e127pi:mrcc:mscf2:getECLDelay 18
|
32
|
Tue May 10 22:37:10 2022 |
Jan Glorius | DAQ | DAQ2 cabling docu |
|
Attachment 1: e128_daq2_cabling.ods
|
43
|
Wed May 11 14:48:31 2022 |
Konstantin | DAQ | Voltage range of the Keysight DMM changed from 10V to 1V |
During the setup of the ion beam the voltage range of the Keysight DMM was changed from 10V to 1V. Additionally, the name of the high-voltage divider was adjusted (this changes only the filename of the file, which is stored at the local pc decpc003). |
Attachment 1: VoltageRangeChanged.png
|
|
46
|
Wed May 11 18:13:04 2022 |
Wilfried, Phillip, Max | DAQ | laser scan/step complete |
The scaler channel laser scan complete and laser step complete is interchanged in go4. Carsten will fix this on the software side.
Additionally the laser scan complete signal was not there in the first place. After checking the signal on multiple points, the signal was suddenly back in the DAQ.
Possibly there is a bad cable/contact somewhere (on the Labjack?). The signal should be checked in go4 from time to time. |