Subject: 3.5m Night Log 20201226 From: cgray@apo.nmsu.edu Date: Sun, 27 Dec 2020 13:28:05 +0000 (UTC) Apache Point Observatory 3.5m Telescope Night Log Saturday, December 26, 2020 PROG PI ASTRONOMER OBSERVER(S) -------------------------------------------------------------------- CU07 J.Bally J.Bally AP01 T.Murphy R.McMillan CU05 J.Dexter J.Dexter ACTUAL PROG INSTRUMENT START FINISH -------------------------------------------------------------------- CU07 NICFPS 18:17 18:25 CU07 NICFPS 18:48 21:24 CU07 ECHELLE 21:29 23:04 AP01 APOLLO 23:08 00:01 CU05 TSPEC 00:15 06:15 PROG SCHEDULED WEATH EQUIP OBS NOT USED I/ROW/DTN START FINISH D B D B D B D B ----------------------------------------------------------------- CU07/R 17:13 23:10 0 0 0 1.4 0.0 4.6 0 0 AP01/R 23:10 00:10 0 0 0 0 0.0 1.0 0 0 CU05/R 00:10 06:56 0 0 0 0 2.0 4.7 0 0 note: scheduled times listed include instrument change time ------------- ACTIVITY LOG -------------- Observing Specialist: C.Gray Golly, what a night to wrap up Krampus. So many problems tonight! I went into much more detail in PRs 1994 and 1995 but this is the summary. First up to bat: DIS DIS wasn't taking exposures during checkout. Initially it was throwing the "cannot not take an exposure while another exposure is running error" but a hub StartNubs DisExpose process didn't work. I tried restarting the ICC but then was given the error: 2020-12-26 23:17:33 APO.Candace 57 dis f distxt=""; UNPARSEDTEXT="WARNING: exposure active during command error (cannot close shutter (state=closed))\"\"" With the error came the suggestion to try "dis init cameras" and that finally worked. One issue down. ------------ Coming round on first: Nicfps While Nicfps was fine during checkout, CU07 couldn't change the fowler sampling. I was giving the error: 2020-12-27 00:03:29 APO.Candace 96 nicfps w UNPARSEDTEXT="NFS setting Error: 0x455252" 2020-12-27 00:03:29 APO.Candace 96 nicfps f NFS=0 A nicfps nubs, nicfpsExpose, and exopse init solved the problem. Then, after the first slew (rotation angle of 100, putting nicfps upside down) the same issues happened and we couldn't change the fowler or take an exposure. I tried the same steps and, and the end of read out, the image wouldn't finished reading out. I found that if I did a Stop Script and tried to take another exposure I could, but not of them would read to file and I was given the error 2020-12-27 00:18:15 CU07.bally.nicfpsExpose 7 nicfps w UNPARSEDTEXT="\"Error: readout TIMEOUT!\"" I tried VNCing into NICFPS to restart the ICS but could not connect to the computer and it wasn't pinging. I did a power cycle on the nicfps computer and was then able to connect into VNC and started the ICS. however, we still couldn't take images. We were getting the error: 2020-12-27 00:48:01 .perms 0 perms w permsTxt="Actor nicfps already registered for access control." 2020-12-27 00:48:04 nicfpsExpose 2 fits w hubTxt="Overwriting header for nicfps" This was a port error and, following the pdf instructions on the wiki for how to reconnect the motor controller, NICFPS started taking images again. At least, it did for a little while and then we had the issue again and I had to do another power cycle to the computer. ---------- Sliding into second, we have gcam: Like NCFPS, gcam was fine during checkout. After we had nicfps finally in order, we found we couldn't take gcam exposures. It too was throwing the "cannot take an exposure while another exposure is running." I tried the simple hub startnubs gcamera, startNubs gcam, gcamera expose init to no avail. I couldn't ping the computer but I was also given the error that gcam wasn't connected. I tried a power cycle via the intermediate power box on the I-bead. Again, I could ping but couldn't take an exposure and was still told gcam wasn't connected. However, it gave the warning: 2020-12-27 02:17:38 .gcamera.0 0 gcamera w RawLine="sudo chmod a+rw /dev/bus/usb/006/076" Bill thinks this could be a sign of a connector/cable issue. A PR (1994) was sent. -------------------------- Taking a walk to third base are the dome sensors. When I started this afternoon I noticed that the dome temp, humidity, air sensors weren't being reported. However, that was due to me having a typo when I was turning lamps on and off yesterday morning and I accidentally turned off the sensors with a pset 1 0 and was easily fixed with pset 1 1. ---------- Brining us home are the lamps: They are still not talking. We have to turn them on/off by hand. And the fireworks at the end is the mote light. It was flashing when I came in to start checkout exposures but had stopped flashing when I walked up to the dome floor. I called Ben and he said he's check it one when he got on site in the morning. ------- FAILURE LOG ------- FAILURE MODE TIME PROG INSTR TI/SHU START FINISH DESCRIPTION ---------------------------------------------------------------------- CU07 N I/U 17:13 18:48 Nicfps not reading/communicating ---------------- FOCUS LOG --------------- Time Instrument Focus Az El Temp Strc Prim Sec Air filt FWHM -------------------------------------------------------------------------- 18:16 NICFPS 628( 1104) 246 40 4.4 646.0 646.0 646.0 646.0 H2-2.12 1.22 18:48 NICFPS 376( 1063) 244 34 4.9 4.5 5.0 4.6 4.8 BrG-2.16 0.84 21:35 ecamera 439( -458) 37 45 5.3 5.2 5.7 5.4 5.2 ND3 1.84 23:08 APOLLO 475( 1262) -39 70 4.7 4.1 4.7 4.0 4.3 530 1.50 ------------- WEATHER LOG ---------------- Wind Precip.or Time Temp F Dewp F MPH Direction Dust Sky Conditions ------------------------------------------------------------------ 16:00 40 14 14 29 (NNE) 78 clear none 17:00 39 12 12 348 (NNW) 111 clear none 18:00 40 11 15 11 (N) 114 clear none 19:00 41 11 11 3 (N) 113 clear none 20:00 41 10 13 345 (NNW) 139 mstly clr none 21:00 42 8 14 308 (NW) 142 mstly clr none 22:00 40 8 6 345 (NNW) 146 mstly clr none 23:00 40 9 14 324 (NW) 146 clear none 00:00 41 11 19 330 (NNW) 157 clear none 01:00 41 9 12 2 (N) 106 clear none 02:00 40 4 10 345 (NNW) 116 clear none 03:00 41 6 5 10 (N) 172 clear none 04:00 43 -1 15 319 (NW) 189 clear none 05:00 43 -2 11 288 (WNW) 179 clear none 06:00 41 -5 11 339 (NNW) 166 clear none Note: the wind was coming from the azimuth listed. The convention used is north=0 degrees, east=90 degrees. The dust count is particles > 1u per 0.1 cubic feet. ---------- TELESCOPE SOFTWARE ---------- Current TCC version: 1.4.2 Current HUB version: v20171231_01 Current TUI version: 2.6.0