Subject: 2.5m obslog 20190828 (SJD 58724) From: kinemuchi@apo.nmsu.edu Date: Thu, 29 Aug 2019 10:36:20 +0000 (UTC) APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Wednesday August 28, 2019 (SJD 58724) ---- Observing Team ---- Katie Grabowski Karen Kinemuchi Conor Sayres (on phone) ---- Observing Plan ---- Engineering ---- Observing Summary ---- * Tried to gather fiducial data, but crossings stopped reporting after accepting errors on rotator. See log for more details. * TCC could not talk to new MCP. Called Conor for help. Did not slew telescope via TCC this evening. * 4000 dust counts * There are 3 birds trapped in the enclosure. ---- Observing Log ---- 00:00Z Ventilation begins. We plan on gathering fiducial data in the night. Radar is around, and we see dust in the basin. We are monitoring the dust and weather, but expect to get the fiducial data tonight. Engineering camera is mounted on the telescope. Counterweight values are manually set in the lower enclosure. 23:55Z SP1: 3.8 e-6 SP2: 2.5 e-7 02:38Z SP1: 3.7 e-6 SP2: 2.7 e-7 03:42Z SP1: 3.6 e-6 SP2: 2.7 e-7 06:55Z SP1: 3.4 e-6 SP2: 2.4 e-7 09:07Z SP1: 3.1 e-6 SP2: 2.2 e-7 10:27Z SP1: 3.0 e-6 SP2: 2.1 e-7 01:56Z We are starting the new TCC and try to move the telescope to 70 with it. In prep for home/relax mirrors. Trying to get the new TCC to work, but getting errors. Called Conor. He's on to help us. Error messages: 02:07:35 OBSERVER.conor 4 tcc w axisConnState=Failed,Failed,Disconnected 02:07:35 OBSERVER.conor 4 tcc f text="Sub-command(s) failed: STATUS: not connected; STATUS: not connected; STATUS: not connected" 02:07:35 CmdDone: OBSERVER.conor 4 tcc axis status 02:07:39 CmdStarted: OBSERVER.conor 5 tcc axis connect 02:07:41 OBSERVER.conor 5 tcc f text="Sub-command(s) failed: : SDSSAxisDevice(rot1) failed to connect: Sub-command(s) failed: STATUS: Expected 5 values for status but got 'altMsOn'; : SDSSAxisDevice(alt) failed to connect: Sub-command(s) failed: STATUS: disconnected; : SDSSAxisDevice(az) failed to connect: Sub-command(s) failed: STATUS: disconnected" 02:07:41 CmdDone: OBSERVER.conor 5 tcc axis connect 02:09:17 OBSERVER.conor 9 tcc f text="Sub-command(s) failed: STATUS: not connected; STATUS: not connected; STATUS: not connected" 02:09:17 CmdDone: OBSERVER.conor 9 tcc axis status tcc axis connect 02:13:54 OBSERVER.conor 14 tcc f text="Sub-command(s) failed: : SDSSAxisDevice(rot1) failed to connect: Sub-command(s) failed: STATUS: Expected 5 values for status but got 'altMsOn'; : SDSSAxisDevice(alt) failed to connect: Sub-command(s) failed: STATUS: disconnected; : SDSSAxisDevice(az) failed to connect: Sub-command(s) failed: STATUS: disconnected" 02:13:54 CmdDone: OBSERVER.conor 14 tcc axis connect Conor is having trouble with getting garbled messages from the MCP. He's restarted the TCC, and the mirror status window shows some numbers now. We will not move the telescope with the TCC tonight until these issues are resolved. We will move the telescope with the MCP only. Went to gather fiducial data. Tried to check fiducial crossing between 0 and 16, but it doesn't normally read, so I went to -16 instead. Rotator fiducials from STUI script: 05:51:08 -5 -1.1 bad 05:51:11 79 -3.6 176 05:51:15 80 -8.4 165 05:51:19 81 -13.1 132 05:51:56 -5 -15.3 bad Accepted fiducial at -16 Observations:Fiducial Monitor script doesn't show any of the "bad" error lines getclock timestamp of 1567057982 moved rotator to 0 05:51:59 81 -13.1 -2 05:52:03 80 -8.4 20 05:52:07 79 -3.6 32 05:53:04 -5 -1.1 bad moved rotator to -190. All fiducial crossings read. Some humming of the rotator ~index 88-90. Errors >|600| greater than index 96 05:53:06 79 -3.6 47 05:53:10 80 -8.4 34 05:53:14 81 -13.1 6 05:53:18 82 -17.9 -34 05:53:22 83 -22.6 -41 05:53:26 84 -27.3 -64 05:53:30 85 -32.1 -83 05:53:34 86 -36.8 -100 05:53:38 87 -41.6 -156 05:53:43 88 -46.3 -205 05:53:46 89 -51.0 -242 05:53:50 90 -55.8 -284 05:53:54 91 -60.5 -334 05:53:58 92 -65.3 -385 05:54:02 93 -70.0 -437 05:54:06 94 -74.8 -500 05:54:11 95 -79.5 -536 05:54:14 96 -84.2 -559 05:54:19 97 -89.0 -591 05:54:23 98 -93.7 -622 05:54:26 99 -98.5 -632 05:54:30 100 -103.2 -676 05:54:34 101 -108.0 -698 05:54:38 102 -112.7 -688 05:54:42 103 -117.4 -687 05:54:46 104 -122.2 -708 05:54:50 105 -126.9 -707 05:54:54 106 -131.7 -709 05:54:58 107 -136.4 -712 05:55:03 108 -141.1 -719 05:55:06 109 -145.9 -694 05:55:10 110 -150.6 -689 05:55:14 111 -155.4 -675 05:55:18 112 -160.1 -657 05:55:22 113 -164.8 -649 05:55:26 114 -169.6 -12849 Slewed back to 16 degrees to check canonincal fiducial index #75, at 15.3 degrees, but none of the crossings read on the way back. Did hub startNubs mcp and mcp set.time to see if that would get it to start reading again. Moved from +/30 to see if it would read any of the crossings it read previously, but it didn't. getclock timestamp of 15670585500 Tried the same thing with altitude next: 05:47:04 Alt: ind=3, deg= 46.2, err= 461 05:47:40 Alt: ind=4, deg= 60.4, err= 499 05:48:19 Alt: ind=5, deg= 75.5, err= 477 05:48:53 Alt: ind=6, deg= 88.8, err= 40 These were slews on the way up to zenith, before moving the rotator. Moved down to 50 degrees and back up to 85-90 degrees, but none of the fiducial indices read. getclock timestamp of 1567058722 Same problem with Az, where none of the fiducials are reading. Checking the list of processes the mcp is running shows all of them running. The status of the semaphores is consistent with whether STUI or the MCP have control. We also believe that the mcpMenu is reading the correct fiducial crossings as we did the slews. The STUI fiducials gui isn't getting the information, so it is not providing those numbers. 10:31Z Giving up. No radar nearby and pumping on the cameras appear to be ok. ---- Telescope Status ---- 00:00Z Started ventilation