UMN CDMS Wiki archive
start › cdms › k100 › run_diary › 20150901

2015/09/01 (Tuesday)

previous day

Current setup: DIB1/2/3 → cables → 3.2 MHz filters → DCRC55/33/50. Overnight, Cf source in shield activating detector, detector baking
0920 Remove Cf-252 source
0925 Tower = 261 mK, Still = 0.11 mbar, G1/G2 = 175 mbar, 1K Pot = 1.72 K / 22 mbar, Main bath = 15.1%.
0927 Stop baking detector. Tower falls to 32 mK after 30 minutes
0930 Fill LN2 cold trap Dewar
1025 Commence LHe transfer (13.1%).
1100 Finish transfer (67.7%).
1330 Take data: Start DAQDAQ2 taking 4 10-minute series of -/+4V data (Frontend Gain: 1, Output Gain: 3=setting), with standard 6s flash, 20min cooldown in between series.
1540 Data run finished. Apply -/+2V bias and check phonon threshold settings.
The values from yesterday still give good triggering.
1551 Zero charge bias and flash for 30s.
Modify DAQ files in MultiDAQ for -/+2V data. Nominal Qi/Qo values in below table:
Qi Qo
DCRC55 -1.995V -1.962V
DCRC33 2.3659V 2.3831V
1607 Mixing Chamber at 31.7mK. Take data: Start DAQDAQ2 taking 4 10-minute series of -/+2V data (Frontend Gain: 1, Output Gain: 3), with standard 6s flash, 20min cooldown in between series.
1715 TCP/IP error from MultiDAQ during 2nd data series. One of the connections to DCRC50 didn't close properly, so the next time MultiDAQ started up and tried to connect, it threw the error. Stop DAQDAQ2 and flash to neutralize crystal.
To confirm and fix the connection issue:
1 Make sure all LabVIEW programs are stopped or at least disconnected from DCRCs.
2 Send sock to all three DCRCs via Putty.
3 Make a note of any connections to port 1.
4 Send quit 1 to any DCRCs that are still connected on port 1. This quits that specific connection and MultiDAQ should be able to connect the next time it starts up.
1729 Take data: Start DAQDAQ2 to take 1 last 10-minute series of -/+2V data.
1754 Series done. Charge already zeroes thanks to DAQDAQ2.
Set to bake overnight.
1756 Fill LN2 cold trap full.
1820 Place Cf source in shield near detector for overnight activation

next day