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

2015/12/31 (Thursday)

Previous Day

Currently: the DCRCs are connected to wall ethernet ports: DCRC55/33/50 → 00043-AH/00043-AN/00043-AE. AH and AE are on the south wall near the fridge, AN is near the circuit breakers by the entrance.
previous setup: iZIP mode, DIB1/2/3 → cables → 3.2 MHz filters → DCRC55/33/50
Cf source near detector for overnight activation.
0925 Tower/MC(H35)/MC sensor/Cold Plate = 38.6/28.541.0/151 mK, Still = 1.04 K / 0.11 mbar, G1/G2 = 110/100 mbar, 1K Pot = 1.73 K / 24 mbar, Main bath = 69.7%
1015 Disconnect ethernet cables from DCRCs to turn off power, then plug them into DIBs, as in last run: DIB1/2/3 → cables → 3.2 MHz filters → DCRC55/33/50
1030 Plug ethernet cable into DCRC55: power comes back up. Attempt to communicate via Telnet, with command telnet 131.225.53.84 5000, but this does not work. As it turns out, Anthony has changed the addresses of the DCRCs:
DCRC New address
55 192.168.96.1
33 192.168.96.2
50 192.168.96.3
These addresses can be seen in the ODB. However the name of the DCRC is not present: it's just “DCRC1”, “DCRC2”, “DCRC3” on the ODB, i.e. the corresponding DIB numbers.
1050 Started all three DCRCs with telnet sessions on port 5000. Issued wr 15 0, wr 15 20, rd 30 commands. On DCRC33, rd 30 returned 0000, so did wr 30 0900, then wr 30 0800.
1055 Started the three MIDAS DAQ programs (dcrc, tower, trigger)
1115 On MIDAS ODB in Equipment/TriggerFE/Settings set the PileupCut to 0.0032768 s (i.e. one entire trace length)
1125 On MIDAS ODB, DIB1 phonon VGAGain (aka “output gain” in LabVIEW terminology) were set to 0. Reset these to 5. Now the VGAGains of DIB1/2/3 are 5/2/5 as before.
a lot of other phonon settings on DIB1 are clearly set wrong, will need to reset them
1135 Try zapping with MIDAS. Still pressure and tower temperature increases seen, so it seems to have worked.
1140 Establish timing link through telnet sessions
1203 Attempt to flash with Midas via flashandflash.py program. We noticed that this had a default setting of flashing for .1 s and resting for 5 s, and a total flashing time of .1 hours. This seemed wrong, as the Labview program flashes for 100 us, and rests for 5000 us, a tenth of these values. We changed the flash settings to these values and set the flash duration for one minute (0.017 hours). The script then starting 12000 loops of flashing, which was certainly too many. After about a minute it had only gone through ~20 loops, though the temperature had risen to 240 mK and appeared stable. We stopped the program immediately, and then used odbedit to load run00652.odb, which caused the temperature to fall back to normal. These settings were chosen because this data was taken on December 18th at 00:48, as indicated by the odb file in /home/hep/cdmssoft/scdmsDAQ/MidasDAQ/online/data/livedata/. EDIT: We have learned that 100 ms flashing on and 5 s sec off ARE correct, and the labview units are just wrong. We likely just bogged it down with such small values. Our bad.
1205 Loading the ODB settings set the charge biases to -/+ 4 V, so reset these to zero on the ODB
1240 Tower has cooled to around 40 mK. Using MIDAS pulse viewer to check phonons:
DIB1 pB was railed at 1.2 V. Adjusting the offset from -0.4 to -0.11 fixed it.
DIB2 All phonons railed at -1.2 V. Adjustments in offset don't seem to help.
DIB3 Sinusoidal noise seen at 7050 Hz, very prominent in pC at 60 mVpp.
1330 Main bath = 62.5%
1330 Try zapping all phonons again.
1355 7 kHz noise still quite prominent in DIB3pC.
1405 Still having trouble with DIB2. No pulses are present, phonon or charge. Try flashing DIB2 only, to see whether there is any communication at all. Tower climbs to 64 mK so yes, there is communication.
1532 Fill LN2 cold trap full.
1615 Main bath = 57.9%
1645 Tower oscillating a bit, has been as low as 38.1 mK, currently 39.5 mK. MC(H35) = 29.5 mK. 1KPot, Still, circulating pressures very close to this morning's values.

Next Day