Upper part of the frame was mounted. In order to do so, the valve was closed, turbo wire and hose were disconnected and then connected. Valve was opened again. See pictures 1-2.

Bottom part of the tent was constructed with 3 heaters (from one of the controllers) at the front, 4 in the middle, and 4 at the back (4+4 from the other controller). See pictures 3.

Thermocouples were tested and connected to TC08 modules.

Wire connecting to four heaters was damaged which caused a spark and sound when the upper tent was being constructed. This caused a power failure two times, turning off all three pumps. The upper valve was immediately closed. Power supplies of heaters were disconnected and pumps were turned on again. Valve was opened again as well.

Construction of tent is paused. Waiting for the wire to be repaired by tomorrow and start again.

With the help of OG, the baking tent was built. MG started baking around 11:30 am with a rate of 0.2 K/minute.

Heating update can be found on:  https://web-docs.gsi.de/~lestinsk/baking.php (CARME temperature plot now visible as well - thanks Michael!)

where, device - 192.168.207.192 is for CARME.

Ch1: CARME chamber long tape (2 kW)

Ch2: CF100 flanges exit side

Ch3: CF100 bellows exit side

Ch5:  200 W (x3) CF 100 flanges

Ch6:  40 W CF 100 flange

Ch8: VAT 100 gate valve to ring

example: in 39:50, 39 is the temperature and 50 is the set temperature.

1. Detector

2. Chamber back

3. Strain relief

4. Target

5. Front CARME

6. Top hanging

7. Middle middle CARME

8. Middle bottom

1. Middle top

2. End middle

3. Elbow

4. Valve

5. Magnet pipe

6. End back

7. Float

8. End bottom

10:10  IE514 2.0e-08mbar

Upstream part of the CARME is covered.

09:26  IE514 1.96e-08mbar

10:30  IE514 1.80e-08mbar

Most of the CARME is covered by the baking tent. The tent needs to be closed and a bit covered from the front (upstream), end (downstream), and bottom side. TCs are labeled with a marker in the sequence 1-1 to 2-8.

1-1 Internal TC 1
1-2 Internal TC 2
1-3 Internal TC 3
1-4 CARME front top
1-5 CARME front bottom
1-6 Top hanging middle
1-7 CARME middle middle
1-8 CARME middle bottom

2-1 CARME middle top
2-2 CARME back middle
2-3 Elbow
2-4 Valve
2-5 Magnet pipe
2-6 CARME back top
2-7 CARME back float
2-8 CARME back bottom

Also, TC extensions would be needed to connect to TC-8 modules.

Run 77 started at 06:48

Cooler voltage setpoint 247.0 V.

07:05

DSSSD bias & leakage current OK - attachments 1 & 2

FEE64 temperatures OK - attachment 3

ADC data item stats OK - attachment 4

per FEE64 Rate spectra OK - attachment 5

Beam intensity 8.45e+7 particles

Target density ~5.34E11 atoms/cm2

09:02

DSSSD bias & leakage current OK - attachments 6 & 7

FEE64 temperatures OK - attachment 8

ADC data item stats OK - attachment 9

per FEE64 Rate spectra OK - attachment 10

Beam intensity 7.85e+7 particles

Target density ~5.29E11 atoms/cm2

11:00

DSSSD bias & leakage current OK - attachments 11 & 12

FEE64 temperatures OK - attachment 13

ADC data item stats OK - attachment 14

per FEE64 Rate spectra OK - attachment 15

Beam intensity 8.5e+7 particles

Target density ~6.1E11 atoms/cm2

13:00

DSSSD bias & leakage current OK - attachments 16 & 17

FEE64 temperatures OK - attachment 18

ADC data item stats OK - attachment 19

per FEE64 Rate spectra OK - attachment 20

Beam intensity 8.2e+7 particles

Target density ~6.1E11 atoms/cm2

Run 48 started. Everything is running again. We started at 3E13 at/cm2

D+ beam deuterium target. D+ beam energy is still 0.5 MeV/u. (beam calc calculation is 0.5143 MeV/u). See previous entry for beamcalc.

All four detectors positioned fully out and stationary, however we switched off detector #4.

Left potentiometer = -3.03mm (corresponds to x = 0, which is the more trustworthy value)

Right potentiometer = 1.74 mm (corresponds to y = -500, which is the more trustworthy value)

Ring cycle time is 10 seconds.

Cooler set value = 297.2 V, 8 mA. Read value = 296.7 V, 7 mA

All leakage currents look good (except dssd4, currently turned off)

Beam position. Vertical =0.0mm , Horizontal=0.0 mm

Data rate ~ 108kB/s

16:40  Change Gasjet target Y=-500 to Y=0
17:37  Change Gasjet target Y= 0 to Y= 500

20:30 We now take some time to optimize the areal density
20:30  Change Gasjet target Y= 500 to Y= 1000 (resulting in 2E12)
20:32  Change Gasjet target Y= 1000 to Y= 500 (resulting in 4E12)
20:33  Change Gasjet target Y= 500 to Y= 0 (resulting in 7E12)
20:35  Change Gasjet target Y= 0 to Y= -500 (resulting in 1.1E13)
20:37  Change Gasjet target Y= -500 to Y= -1000 (resulting in 1.8E13, still increasing and amazing for almost 1h)

21:48: Since approximately 20min its just going down systematically from a stable 2E13 to 6E12...) Lets try another round of optimization...
21:48  Change Gasjet target Y= -1000 to Y= -1500 (starting at 7E12 and resulting in 2E12)
21:49  Change Gasjet target Y= -1500 to Y= -1000 (starting at 2E12 and resulting in 6E12)
21:50  Change Gasjet target Y= -1000 to Y= -500 (starting at 6E12 and resulting in 9E12)
21:51  Change Gasjet target Y= -500 to Y= 0 (starting at 9E12 and resulting in 1.3E13 but dropping back to 7E12 within 3min)

21:54  Change Gasjet target. Leaving Y at 0, but moving X from 0 to -500 (starting at 6E12 and resulting in 3E12)
21:55  Change Gasjet target. Leaving Y at 0, but moving X from -500 to 0 (starting at 3E12 and resulting in 4E12)
21:56  Change Gasjet target. Leaving Y at 0, but moving X from 0 to +500 (starting at 4E12 and resulting in 6E12)

21:59  Change Gasjet target. Leaving X at 500, but moving Y from 0 to +500 (starting at 5E12 and resulting in 7E11...)
22:00  Change Gasjet target. Leaving X at 500, but moving Y from +500 to 0 (starting at 7E11 and resulting in 2E12)

Side comment: It seems no matter what we do, that there is a general decrease within the last 30min...

22:00  Change Gasjet target. Leaving X at 500, but moving Y from +500 to 0 (starting at 7E11 and resulting in 2E12)

Okay... No matter what we do... Its still decreasing...

22:03  Change Gasjet target. Leaving Y at 0, but moving X from 500  to 0 (starting at 1E12 and resulting in 2E12)
22:06  Change Gasjet target. Leaving X at 0, but moving Y = 0 from  to -500 (starting at 2E12 and resulting in 5E12
22:09  Change Gasjet target. Leaving X at 0, but moving Y = -500 from  to -1000 (starting at 5E12 and just randomly fluctuating within the next 15min... and more decreasing than increasing...)

22:25  Change Gasjet target. Leaving X at 0, but moving Y = -1000 from  to -1500 (starting at 1E12 and resulting in 2E12... )
22:31  Change Gasjet target. Leaving X at 0, but moving Y = -1500 from  to -2000 (starting at 1E12 and resulting in 8E11... ) Whaaaat????
22:32  Change Gasjet target. Leaving X at 0, but moving Y = -2000 from  to -1000 (starting at 9E11 and resulting in 4E12... ) Okaaaay lets wait and see...

01:00

Run stopped.

Final statistics very high. Over 10,000 counts for 3He and 3H, Over 5000 counts for proton.

Final energy histogram and xy plot on final attachments

no change:

Check Clock Status': Passed 5, Failed 0

Check ADC Calibration: Passed 5, Failed 0

'Check the White rabbit decoder status: Passed 0, Failed 5

target density at S1: 2.1-2.4e-8

temp: 116K

no change:

Check Clock Status': Passed 5, Failed 0

Check ADC Calibration: Passed 5, Failed 0

'Check the White rabbit decoder status: Passed 0, Failed 5

target density at S1: 2.1-2.4e-8

temp: 116K

no change:

Check Clock Status': Passed 5, Failed 0

Check ADC Calibration: Passed 5, Failed 0

'Check the White rabbit decoder status: Passed 0, Failed 5

target density at S1: 2.1-2.3e-8

temp: 116K

beam at injection: 7e7

A target temperature walkthrough has been initiated at 20:41 since the target density at S1 had slightly decreased (with ~0.1-0.2)

Current temprature 116K

set to 126K at 20:41

set to 95K at 20:47:30

set to 108.5K at 21:01:30, at this temperature was a sweetspot observerd for target density.

set to 109.7 at 21:08:30

set to 110K at 21:13:30 - we keep at this value for a while. the values at S1 are changing between 2.2-2.9e-8

no change:

Check Clock Status': Passed 5, Failed 0

Check ADC Calibration: Passed 5, Failed 0

'Check the White rabbit decoder status: Passed 0, Failed 5

target density at S1: 2.3-2.7e-8

temp: 110K

beam at injection: 7e7

no change:

Check Clock Status': Passed 5, Failed 0

Check ADC Calibration: Passed 5, Failed 0

'Check the White rabbit decoder status: Passed 0, Failed 5

target density at S1: 2.2-2.7e-8

temp: 110K

beam at injection: 7e7

We opened one up and soldered a co-ax cable to one of the +6v power contacts at the output of the filter board.

Connecting this to a 'scope we observed a level of +/- 5mv noise with no FEE connected.

Connecting one FEE made little difference.

Re-connected the FEE to the power supply in the cabinet and wired a co-ax to a spare FEE power plug. 

Ran the system with two FEEs on the bench top and two in the cabinet. The benchtop FEEs were connected to the NIM bin in the cabinet with copper braid.

Using a PB4 in the NIM bin and my test input cards on the FEE mezzanine connector, the following readings were taken using the 'integrate' function in the spectrum browser.

Shaping 8us, negative pulse.

aida02, ASIC1, ch0 Peak width => 16.58 channels ( full 16 bit spectra )

aida03, ASIC1, ch0 Peak width => 18.48 channels ( full 16 bit spectra )

aida04, ASIC1, ch0 Peak width => 18.05 channels ( full 16 bit spectra )

These could be better but the output of the PB4 was not perfect. I think ASIC 1 Ch0 is normally the worst on the mezzanine.

Attachments 1 to 6 are the waveforms and some zoomed in.

The co-ax from the power supply was connected to a 'scope and showed a noise level of +/-50mv. 

Fourier analysis of this noise showed two peaks 109kHz and 218kHz. ( Attachments 7 & 8 )

When using the VITAR connected to the HDMI port of the root MACB the settings for all the MACB in the system 0x3.

This setting takes the Clock and Data line from the input HDMI and outputs it via teh HDMI output ports.

When using the Emulator connected via the SMA connectors on the back of the root MACB then the setting for the root MACB should be 0xD and all others should be 0x3.

Attached is the .jed file for programming the MACB and the .vhd source file to help with understanding of the settings.

This is a suggested sequence of actions to help with the current problem with the White Rabbit timestamp distribution. Test the system between each intervention. If a test provides an answer to the problem then proceed accordingly rather than continue with the suggestions.

• Please sketch the current MACB wiring.
• Unplug and replug the connectors of the VETAR HDMI connecting cable. If possible clean the pcb and cable HDMI connectors with contact cleaner.
• Disconnect the VETAR and connect the Emulator. If the clocks are not correct then at the Local and Waveform control page change the entry for LMK03200 control register at offset 5 to 0xB. If clocks are now ok then repeat for all the FEEs. Be aware that this value will be set back to 0x1B during SETUP. If the Emulator fails then continue with VETAR and setting 0x1B.
• Connect one or more FEE64 to the base MACB.
• Change the base MACB and repeat the test above.
• Connect a FEE to the VETAR direct. 

I am at present unable to advise further. However should there be more then I will update this entry.

Motor position ok

Data rate: 1030kbytes/s

T ok

System wide check ok

plots uploaded

DAQ crashed soon afterwards

PB found pictures of the original dirty assembly, before screws and components were shipped to DL.
See attached.

Steps taken:
- MIDAS_Releases, Embedded and Exports files brought across from the previously working SL6 aida-gsi install. Brought as tar balls to preserve ownership
- dhcpd.conf set up with same IP addresses as used on the SL6 install from aida-gsi
- nfs-utils package installed on centos7
- Paths to directories listed in /etc/exports checked that they point to the correct locations on the centos system
- Firewall disabled to confirm that it is not interfering
- setenforce 0 to confirm selinux is not interfering.


- Attachment 1 Screenshot of FEE console for aida04 as it stops booting.
- Attachment 2 text dump of /var/log/messages during the FEE boot sequence
- Attachment 3 text dump from tcpdump filtered to aida04
- Attachment 4 /var/lib/dhcp/dhcp.leases file as mentioned in the /var/log/messages dump
- Attachment 5 A copy of dhcpd.conf
- Attachment 6 A copy of /etc/hosts
- Attachment 7 A copy of /etc/exports    
- Attachment 8 Text dump of ifconfig -a (Note the FEEs are conencted to p4p1)

From the messages dump it seems there is an issue being encountered with dhcp leases for the static IP addresses of the FEEs. They are then getting assigned new IP addresses which are getting put in the leases file.