Gotthard related stuff

for now very short: run the Exp2 DAQ with EXPERIMENT_GOTTHARD included as shown below. AND press the start button in the Gotthard DAQ (you get there from the Gotthard panel lower left button "Gotthard DAQ"

20

21

\\

22

23

* Main Gotthard panel for users :

24

25

[[image:attach:Clipboard05.gif||height="400"]]

\\

\\

* Exp2 DAQ RC gui for recording Gotthard data. EXPERIMENT_GOTTHARD has to be included

31

32

[[image:attach:Clipboard01.gif||height="400"]]

\\

== Operation hints (June 2023): ==

37

38

(% style="list-style-type: square;" %)

39

* **Where is the GOTTHARD GUI:** FLASH2 - Panel: Infrastructure tab → Miscellaneous tab → FLASH2 GOTTHARD ctrl button

40

* **Never change a running system:** Do not change parameters while the Detector is running/taking data, The detector will crash.

41

* Furthermore the module will crash if recieving to much light (e.g. illuminating with flash light during data dating.

42

* **Checking/switching server:** The server is reachable from the GOTTHARD GUI (lower left corner find the status of the server PC "hasfl2det01") click it to open server/watchdog control. The server is otherwise found under FLASH.SYSTEM → HASFL2DET01.WATCH. Open control of SVR.GOTTHARD (for start/stop/reboot)

43

44

(% style="list-style-type: square;" %)

45

* **Robooting the GOTTHARD** (if it has crashed):

46

(% style="list-style-type: square;" %)

47

** soft reboot: 1. open console on linux DESY PC, 2. type "telnet (Hostname/IP)" e.g. "telnet cfeld-gotthard02" , 3. you are logged on the GOTTHARD module as /root, type "reboot", 4. wait until server/GUI has reconnected to the module

48

** hard reset: power down the GOTTHARD, wait some seconds, Repower the module, wait for reconnection to server/GUI

49

* **In case of a crashes** (no data taking, no reaction on input: Reboot the detector) or if GUI input returns error: Check connection (Power/Data), check GOTTHARD server

50

51

Using burst mode (standard operation as of June 2023)

52

53

(% style="list-style-type: square;" %)

54

* Do not change the delay in the GOTTHARD GUI. The Alignment to the FEL pulses are done by adjusting the FLASH trigger: FL2EXP1/RTM.TRG6, it can be opened from the GOTTHARD GUI or from FLASH2 → Beamlines → FL26 → Exp. control → Patch Panel26-2 → MTCA Trigger 2

55

* Exposure range is 100ns < Exposure < ~~1/3 * Frame periode

56

* The periode is: 9968ns for 100kHz,

57

58

== Modules and their exchange ==

59

60

Two (Three) modules available (physically at FLASH):

61

62

(% class="wrapped relative-table" style="width: 64.2451%;" %)

|=(((

hostname

)))|=(((

Status

)))|=(((

Sensor

)))|=(% colspan="1" %)(((

Sensor image

)))|=(((

config file

)))

|(((

cfeld-gotthard02

)))|(((

**standard**/online/working

78

)))|(((

79

(% class="content-wrapper" %)

80

(((

81

two small areas of damaged pixels

82

)))

83

)))|(% colspan="1" %)(((

84

(% class="content-wrapper" %)

85

(((

86

[[image:attach:cfeld-gotthard02.jpg||height="250"]]

87

)))

88

)))|(((

89

bchip_mpc1922Receiver.config_cfeld-gotthard02

)))

|(((

hasdslabgh

)))|(((

working

)))|(((

first 1/3 is blind, strong base line offset in the center and a further blind bunch and the end

97

)))|(% colspan="1" %)(((

98

(% class="content-wrapper" %)

99

(((

100

[[image:attach:hasdslabgh.jpg||height="250"]]

101

)))

102

)))|(((

103

bchip_mpc1922Receiver.config

)))

|(((

cfeld-gotthard01

)))|(((

was working (2018), backilluminated! the sensor front is Al-shielded for x-rays

109

)))|(((

110

?

111

)))|(% colspan="1" %)(((

112

\\

113

)))|(((

114

bchip_mpc1922Receiver_petra.config

)))

\\

To change a module the respective config file has to be selected. However changing it will crash the server, thus, it is not possible to change on the fly. Connact Sören if there is the need to exchange a module. However, the differences in the configs are only the hostname. (**To be tested: On the fly might work, if one edits the config-file itself after switching of the server instead of selecting another config file in the GUI. But how to transport this information to the GUI? → Display the first line of the config file!**) The config files are located at the **hasfl2det01: /export/doocs/server/gotthard_server/cfgs/**

\\

== GOTTHARD Server ==

124

125

The server for GOTTHARD (FLASH2) runs on **hasfl2det01**. Its watchdog and control (svr.GOTTHARD) can be found under** FLASH.SYSTEMS - HASFL2DET01.**

\\

== Main Parameters and limits ==

130

131

(% class="wrapped" %)

|=(((

Parameter

)))|=(((

Design

)))|=(% colspan="1" %)(((

Real /tested

)))

|(((

Max Frames

)))|(((

125

)))|(% colspan="1" %)(((

120

)))

|(((

Max. exposition time

)))|(((

~~2/3 of period time

)))|(% colspan="1" %)(((

\\

)))

|(((

Min. period time

)))|(((

ca. 930 ns

)))|(% colspan="1" %)(((

\\

)))

|(((

Max repetition frequ.

162

)))|(((

163

1 MHz

164

)))|(% colspan="1" %)(((

165

833 kHz (software limited)

)))

\\

== Soft reset a GOTTHARD Module ==

171

172

(% style="list-style-type: square;" %)

173

* Open console on Linux PC (connected to DESY net)

174

* write "telnet cfeld-gotthard02" (or the respective Host name or IP of the module)

175

(% style="list-style-type: square;" %)

176

** you should be connected to the GOTTHARD onboard system → </root:

177

* type: "reboot"

178

(% style="list-style-type: square;" %)

179

** the module reboots (wait ~~1-2 min), the telnat connection will be cut due to reboot.

\\

== Triggering the Gotthard with a burst trigger ==

184

185

it is also possible to trigger the Gotthard not only with 10 Hz but with a burst trigger

186

187

here are some Info from PIS (June 2023)

I think one does not need to set it in GUI when running in continuous mode. In G1, whether the detector is running in burst or continuous mode depends on the setting of the "number of frames" in trigger mode. If the number of frames sets to 1, it will be in continuous mode (1 trigger -> 1 frame).

194

195

Since G1 accepts triggers from the lemo connector, one can also use the bunch train trigger. The spacing of the trigger train needs to be larger than 3.2 ms, which is the readout time of G1.

196

197

Regarding the detector setting (assuming it is 200 kHz pulse rate, 100 pulses per train):

198

199

* timing mode: trigger

200

* number of frames: 1

201

* number of triggers: M x N (M is the number of trains and N is the pulses per train, one can also take a bit more frames per train to track the pedestal/dark)

202

* period: < 5 us (1/200 kHz = 5 us, the period needs to be slightly smaller than 5 us since the detection of the trigger only starts after the period is reached)

203

* exposure time: > 93 ns and smaller than period

204

205

Alignment: One of the four lemo connectors on G1 outputs its exposure window. Using an oscilloscope, one can use a photodiode under the beam and align the pulses from the diode and the exposure window of G1 by fine tuning the exposure time of G1 and/or the setting of "delay after trigger" from the detector, or "delay time" of the wave-generator (if a wave-generator is used to generate the triggers for every pulse). After this, one can do a fine scan of trigger delay to find an optimal setting with highest signal after putting G1 under the beam.

\\

by:

Dr. Jiaguo Zhang

Paul Scherrer Institut