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

2017/10/05 (Thursday)

Previous Day

Status: warm. All mixture in dump. LN2 traps warm and pumped out. Contaminants from fridge were pumped out at 220 K. Cryostat vacuum jacket pumped out. Cryostat in pit, IVC full of N2.
0945 MC(Cernox) = 296.8 K on LakeShore display, 297.8 on LabVIEW vi. Lab thermometer reads 297.35 K. So actually maybe the LabVIEW calibration is closer (but the LakeShore is more conservative in terms of warming).
0940 Experiment with DCRC1
  1. Set randoms rate in MIDAS to 0.5 Hz instead of usual 5 Hz
  2. also note: ChargeWaveFormLength 151384, PhononWaveFormLength 512, left over from run, same as yesterday
  3. start MIDAS run at 9:41 with only DCRC1 enabled and set as Master.
  4. after 8 minutes (9:49) DCRC1 is still not stuck
1112 DCRC1 is stuck. Even slow randoms triggering will break it. But it seems to last longer. Worth investigating more.
1115 Stop run and turn off programs. Restart DCRC1 using “RESET” command in telnet. (i.e. don't physically power cycle it)
1121 Start programs and start new run with same settings as above.
1136 DCRC1 is stuck. Stop run, turn off programs, physically power cycle DCRC1.
1138 Set the signal generator to 10Hz with wr 42 0004, wr 43 0000.
1140 rd 14 = 0000, rt = 00000000 (not triggering), rd 15 = 02A0 (memory write enabled)
1142 wr 15 12A0, rd 15 = 1220 That's okay, the 2→A flip is a bit that shows the trigger list is no longer empty. Indeed, rt is updating with triggers. However, 0x02 and 0x03 (SDRam read addresses) are not being updated and so neither is 0x14 (SDRam data port). It's the job of the user (or something like tower/trigger front end programs) to decide if they want the triggers in rt and, if so, update 0x02, and 0x03 appropriately.
1147 Let it sit like this for a while. It's triggering internally on the test signal, but no requests are being made to output the data. rd 0 is updating.
1206 rt = 00000001;3F25A342 Let's write this address to read out some data. wr 4 3F25, wr 5 A342 Now 0x02 and 0x03 have been updated and 14 is updating. So it's putting the data from that address in 14. I think each rd 14 queues up the next set of data to be put into 14. Not sure if 0x14 is still being updated somehow when we're not reading it. rd 0 is still updating.
1328 0x00 and 0x14 still updating
1351 De-installation began this morning. Got as far as removing 4K stage, 100mK stage, 30 mK stage, strip line buckle, and the tower.
1501 0x00 and 0x14 still updating
1738 0x00 and 0x14 still updating
1739 Start DCRC programs. rt = 00000000. Starting DCRC driver overwrote the signal generator trigger settings. Use ODD to start triggering on sig gen again and turn off random triggers. rt is updating, 0x00 is updating.
1746 0x00 and 0x14 still updating
1747 Start a run. 0x00 and 0x14 are stuck immediately, but rt is still updating and 0x02 and 0x03 are still being updated. The software is still seeing the trigger list from rt and requesting data via writes to 0x02,0x03, but the internal buffer pointer (0x00,0x01) and the data port 0x14 are not updating.
1757 MO 1 returns that the board temperature is 35.0 C. Stop the run.
1800 0x00 and 0x14 are still stuck. Writing to 0x04,0x05 updates 0x02,0x03 but not 0x14 (still stuck).
1802 Stop programs. Board Temp still 35.0 C, 0x00, 0x14 still stuck despite updates of 0x02,0x03.
Also, 0x10,0x11 are stuck even though rt is updating still. They should contain the buffer pointer of the most recent trigger. If 0x00,0x01 is not updating, it may make sense that these are stuck too.
1812 RESET DCRC1 without unplugging it. Now 0x00,0x01 is updating again.
1816 Start programs, turn off all triggering. 0x00,0x01 are updating.
1820 Start run, 0x00,0x01 are updating, but 0x02,0x03,0x14,rt are not (no triggering set)
1821 Board feels cooler than before, but MO 1 still reports 35.0 C
1834 0x00,0x01 still updating
1835 With Anthony's printrd program running on port 5000, start triggering on 10Hz test signal. Towerfe crashes, and printrd hangs at “middle of while loop” on the 0th iteration.
1839 Stop run, close programs. 0x00 still updating.
1841 Restart dcrc programs and run with no triggering, telnet on port 5000. Start test signal triggering, 0x00,0x02, and rt are updating.
1949 0x00,0x02, and rt are updating.
2033 0x00,0x02, and rt are updating.

Next Day