Date: Mon, 21 Aug 2000 05:25:03 -0600 From: "s. a. snedden" Subject: 2.5-m obslog 20000820 (MJD 51777) Sunday, August 20, 2000 Apache Point Observatory SDSS 2.5m Observing Log (MJD 51777) OBSERVING TEAM: =============== Dan Long (APO) Stephanie Snedden (APO) Lucianne Walkowicz - PT (JHU) Gary Long - PT (JHU) VISITORS: ========= Scott Burles (UC) David Schlegel (PU) Russell Owen -by phone (UW) THE PLAN: ========= The fourth night of shakedown. Redo pointing model, after problems from last night's were discovered. SYNOPSIS FOR NIGHT: =================== Frustrating night. We can't point well until the fiducial corrections are enabled. We can't do spectroscopy until sp2 collimator motor is repaired. SOP was succesfully exercised. TELESCOPE STATUS: ================= Stowed at 30 deg alt with the engineering camera on. Counterweights at 130. INTERLOCKS: =========== None bypassed SOFTWARE USED: ============== IOP/SOP: v3_17_5 Watcher: v2_8_3 MCP: v4_3_2 TPM: v2_0_0 AstroDa: 14_33 TCC: 2.4.0b2 WEATHER SYNOPSIS (see below for hourly data): ============================================= Partly cloudy with periods of mostly cloudy early in the night. Mostly clear after midnight. GENERAL COMMENTS (see Problems below for details): ================================================== Pointing Model: --------------- Scot K. pointed out that last night we had been using MCP version 4_3_1, not 4_3_2. Could this have caused the pointing offsets in altitude that we saw last night, or are they caused by the fiducial correction not being made? Apparently the MCP had rebooted during the afternoon yesterday, and when it did, it came up with the older version of the MCP. We are not clear why switchMcp didn't set 4_3_2 as current. We decided we needed to redo the pointing model. We opened at sunset to variably cloudy skies. As soon as we could, we went to an fk5 star and found we needed an altitude offset of .02 deg (72 arcsec) to center it. Checks of other stars showed the same constant offset in altitude. We started a pointing model, and at the same time monitored the murmur log fiducial messages. Every time we slewed to a new star, we got the "dsc_E_trcErr MS.ON is disabled for altitude; not applying" message. Our problem is that no corrections are being made to the altitude axis. We can't do a pointing model under these conditions. At this point, we called Robert, but couldn't reach him, then we called Russell to see if this message was entirely MCP internal, or if there was something we could try from the TCC. The MS.On is internal to the MCP, but Russell suggested we do a 'talk tcc_tel2 correct'. We tried this, and indeed the altitude fiducial was corrected, but the rotator suddenly started correcting itself as well to some huge value. Unfortunately, all axes appear to see the correct command, and Dan thinks the rotator may have corrected itself to the next number that happened to come along...which was interpreted as some large fiducial error number. Getting MS.ON working for all axes is a "high-critical" task. Spectro Checkout: ----------------- Since we could not do a pointing model, and Scott B and David were on-site, we decided to try to track down the problem we saw with mechMoveColl. We decided that what we have is a mechanical problem with sp2 collimator motor A (see problems section). This is a "high-critical" situation. We then decided to check spectro guiding, so the corrector and cartidge 8 were mounted. In spite of our altitude errors, the field was aquired without too much trouble and guiding appeared to be fine. We did notice a software bug in startMon -simple (problems section). GuiderFocus worked well. Pre and post calibs, data acquisition (doNextScience), scale changes and diamondPoints were all tested. All worked well. Note that scaleChange now queries the TCC for the current scale and applies the appropriate scale change based on the current scale. The final task we could do tonight was to check wavelength positioning on sp1's CCDs. Arcs were taken, however the "Son-of-Spectro" web page did not update with the wavemin and wavemax values. In fact, we saw that none of the flats and arcs taken earlier made it onto the web page either. See the problems section. DATA ACQUISITION (see IOP/SOP output below): ============================================ IMAGING: -------- Run Type --- ---- 1638 bias SPECTROSCOPY: ------------- Exposure Type -------- ---- 6025 bias 6026 bias 6027 science 6028 post-flat 6029 post-arc 6030 Diamond offset in Az +1.5 ALT +0 6031 Diamond offset in Az +1.5 ALT +0 6032 Diamond offset in Az +0 ALT +1.5 6033 Diamond offset in Az +0 ALT +1.5 6034 pre-flat 6035 pre-arc 6036 bias 6037 test arc 6038 test arc 6039 bias 6040 test arc MIRRORS: ======== Values after collimation: PRIMARY: -------- MIGS Axial A= 1.9309 Axial B= 0.5584 Axial C= 0.5554 Transverse D= 0.4065 Lateral E= 1.9160 Lateral F= 0.4160 GALILS Commanded: 4751.,-2743.,591.,-10848.,14572.,14119. Actual: 4750., -2750., 600., -10850., 14550., 14100. SETMIR VALUES primDesOrient: 0.00, -2.30, 11.70, 640.50, 128.10 primOrient: 0.00, -2.28, 11.84, 639.70, 127.98 SECONDARY: ---------- Focus:0.0 Temp: 15.1 C Altitude: 47.9 deg MIGS Axial A= -1.2920 Axial B= -1.1890 Axial C= -1.2419 Transverse D= .2339 GALILS Commanded: 1500156.,1461562.,1532149.,-2328.,-7117. Actual: 1500071., 1461514., 1532166., -2350., -7100. SETMIR VALUES secDesOrient: 1188.98, -20.00, -8.00, 50.00, -1.26 secOrient: 1188.95, -20.03, -7.98, 49.57, -1.190 FOCUS LOG: ========== M1 Piston M2 Piston Temp Wind Time Inst setmir TCC setmir Az Alt C Dir MPH filt FWHM LN2 SCHEDULE: ============= Spectros filled at 04:45. Weight 86 lb. Imager weight at 04:45= 133 lb. WEATHER DATA: ============= Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky Precip. ---- ----- ----- -------------- ---- ---- --- ------ 16:01 67 43 8 331 (NNW) 416 - mcl none 17:01 69 43 6 49 (NE) 426 - mcl none 18:01 70 42 1 260 (W) 352 - mcl none 19:01 68 40 0 301 (WNW) 329 - pcl none 20:01 65 38 1 210 (SSW) 323 - pcl none 21:01 65 39 1 177 (S) 324 - pcl none 22:01 64 40 4 182 (S) 414 1.3 pcl none 23:01 65 40 2 215 (SW) 348 - pcl none 00:01 62 37 16 128 (SE) 1256 1.6 clear none 01:01 62 37 15 136 (SE) 1324 1.3 clear none 02:01 59 37 12 119 (ESE) 1407 1.4 clear none 03:01 60 32 7 100 (E) 1118 1.6 clear none 04:01 60 33 9 115 (ESE) 1139 1.8 clear none [pmt]cl = partly, mostly, totally cloudy PROBLEMS: ========= MCP MS.ON --------- The fiducial corrections for the altitude axis (at least) are not enabled. We cannot do a pointing model, or science without them. The first thing you see is that no altitude correction is made. The fiducial crossings register and there are error values given, but they are apparently never implemented. The result is that there are effectively no altitude fiducials, and despite the lack of an obvious error message, I'm not sure the other axes are corrected upon fiducial crossings either. If I cross the heretofore only valid fiducial and apply it via the menu, the position for the axis changes, which would seem to indicate that the updates are not happening automatically. If one forces a correction ( from TELRUN: TALK TCC_TEL2 CORRECT ), the correction is applied but the time we tried, the rotator also applied a very bogus correction and ended up saying its position was 8800 deg. I set the rotator position by hand to something within a few degrees of correct, then moved the rotator via the menu. Its position was never corrected after passing fiducials Here is a sample of the messages one sees when making a slew that crosses fiducials. : Aug 20 21:10:02 sdssmcp tLatch dsc_E_trcErr MS.ON is disabled for altitude; not applying Aug 20 21:10:08 sdssmcp tLatch dsc_E_trcErr Failed to identify rotator fiducial at 10.48 Aug 20 21:10:10 sdssmcp tLatch dsc_S_trcSucc failed to read latch position: status = 0 axis 0x8 Aug 20 21:10:12 sdssmcp tLatch dsc_S_trcSucc failed to read latch position: status = 0 axis 0x8 Aug 20 21:10:15 sdssmcp tLatch dsc_E_trcErr Failed to identify rotator fiducial at -0.22 Aug 20 21:10:15 sdssmcp tLatch dsc_I_trcInfo alt fiducial 28.93 deg Aug 20 21:10:15 sdssmcp tLatch dsc_I_trcInfo err = -36 poserr = 2325 ticks Aug 20 21:10:16 sdssmcp tLatch dsc_I_trcInfo az fiducial 2.27 deg Aug 20 21:10:16 sdssmcp tLatch dsc_I_trcInfo err = 408757 poserr = -1075332966 ticks Aug 20 21:10:17 sdssmcp tLatch dsc_S_trcSucc failed to read latch position: status = 0 axis 0xa Aug 20 21:10:21 sdssmcp tLatch dsc_S_trcSucc failed to read latch position: status = 0 axis 0x8 Aug 20 21:10:23 sdssmcp tLatch dsc_S_trcSucc failed to read latch position: status = 0 axis 0x8 A "high-critical" PR was filed. Sp2 collimator motor A: ----------------------- The problems we saw two nights ago are hardware, not software related. Something is apparently broken or disconnected on sp2's collimator motor A. Last time, we only tried moving the sp2 actuators. Tonight, we moved those of sp1 as well and had no problems with them. We also pistoned B and C individually on sp2, and they responded. We think that while Sp2 was being worked on, something may have been disconnected or brokem on collimator motor A. We checked the connections at the spectrograph, and they all appeared to be seated. A 'high-critical" PR has been filed. SOP StartMon -simple: --------------------- StarMon -simple no longer displays statistics in the SaoDisplay window (FWHM, counts & efficiency). StartMon does show all statistics, the problem is just in the -simple version. A PR has been filed. SON-OF-SPECTRO: --------------- We took several flats and arcs tonight, but nothing showed up on the Son-of-Spectro web page. The latest date on the logfile-current.html page is from two nights ago, when we did the left-right fiber positioning test. Is Son-of-Spectro down? MCP issues: ----------- The following MCP PRs were filed tonight. mcp/1263: MCP rebootus interruptus: . . . f85f42 e280 ASR .L #0x1,D0 f85f44 3182 0a00 MOVE .W D2,(0,A0,D0.L*2) AXIS DIO316 Shutdown: 4 interrupts f85f481 4280 CLR .L D0 f85f4a 242e fffc MOVE .L (0xfffc,A6),D2 f85f4e 4e5e UNLK A6 f85f50 4e75 RTS _ADC128F1ReadReg16: f85f52 4e56 0000 LINK .W A6,#0 f85f56 222e 0008 MOVE .L (0x8,A6),D1 f85f5a 202e 000c MOVE .L (0xc,A6),D0 f85f5e 226e 0010 MOVEA .L (0x10,A6),A1 f85f62 41f9 00f8 61acBARCODE OCTAL232 shutdown: clo Press any key to stop a Got this far in a remote reboot ( ctrl-x from mcp console port ) and apparently something in the connection put a character on the line which was interpreted by the mcp boot sequence as an indication to stop. I had to push the reset button on the crate to get a complete reboot. This happened on two separate occasions tonight. --------------------------------------------------------------------- mcp/1265: The mcp will hang if one uses "s" to stop the rotator when it is moving at slew rates. --------------------------------------------------------------------- mcp/1267: Whenever the altitude goes out of closed loop, the brake does not come on. It acts like the old monitor feature when it is disabled. This is potentially dangerous if the telescope is top heavy and goes out of closed loop. It could come down to the 15 degree stop quite quickly and hit hard, since the windscreen is still following the telescope in this case.