Date: Thu, 20 Apr 2000 02:14:16 -0600 From: Dan Long Subject: 2.5m obslog 000419 (MJD 51654) APACHE POINT OBSERVATORY SDSS 2.5M OBSERVING LOG Wednesday April 19 2000 (MJD 51654) OBSERVING TEAM: =============== Dan Long (APO) Atsuko Nitta Kleinman (APO) Visitors: Peregrine M. McGehee (LANL) THE PLAN: ========= Shakedown. Test the health of the telescope. After that test imager and then spectro. SYNOPSIS: ========= We didn't get much further tonight than testing the health of the telescope. We could not talk to the secondary. Imager biases were taken. A cartridge was put on later in the evening and the new SOP commands tested without starlight down fibers. GENERAL COMMENTS (see Problems below for details): ================================================== At the start of the afternoon checkout the MCP was found in a very unhappy state ( v4_2_2 ). Clinometer not changing with alt position alt would run toward zenith as soon as amps enabled hold cured that problem j and k would be immediately reset to zero when attempting to move. d and m would move the telescope as desired. Rebooting the mcp ( via reset button ) cured all these ills. Fiducials were set without difficulty. Rotator was moved without having to go to un-monitored mode I did find a problem later when using the TCC to move the telescope. After issuing an axis init I would get an error the first, and sometimes the second, time I attempted slewing. The track would fail because of the inability to set MS.OFF for TEL1 and sometimes other axes. Repeated attempts of the same TRACK command would work on the second or third try. This behavior was repeatable at least for the half dozen or so times I tried it. While chasing down the M2 problem, we took biases with the imager. We got a wrong number of pix error across the entire array in frame 36 of run 1382. It got 2130 when it expected 2128. We spent about 3 hours trying to get the M2 galil to communicate. In short nothing we tried would work. There was power to the controller, and no LEDs lit on the fiber transceiver. The problem really appears to be inside the M2 controller box, possibly with the M2 galil itself. Without being able to move the secondary our on sky possibilities were extremely limited. We decided to put on cartridge 6 plate 315 ( one of the ones with known fiber angles ) and test some of the new SOP commands. No starlight went down fibers, but we were able to test the new functionality of some commands. goStare does prompt if no -init has been issued in a SOP session loadCartridge does set the gFiber *rot* array doNextScience does abort if no cartridge is loaded preCalib and postCalib worked gotoField -gflat doesn't complete. It is not clear whether this is a bug or if the problem with the first track failing after an axis init. The ff lamps are left on and the ff screen left closed. The normal gotoField correctly complains that the telescope isn't slewing. However if the track command is repeated and the telescope does slew, the complaint from SOP continues. instChange successfully slews the telescope but all the while complains that it can't talk to the TCC. DATA ACQUISITION (see IOP/SOP output below): =========================================== IMAGING: -------- Run Flavor Frames Notes --- ------ ------ ----- 1382 bias 36 Wrong number of pix SkyGang: -------- SPECTROSCOPY: ------------- Frame flavor expTime Notes ----- ------ ------- ----- TAPES ===== MIRROR NUMBERS ============== *** Info taken at nominal primary piston *** Primary: setmir( cmd ): n/a galil( act ): linear gauges Tonight Nominal 1 = Axial A = 1.9314 1.9315 2 = Axial B = 0.5559 0.5570 3 = Axial C = 0.5554 0.5570 4 = Transverse = 0.4089 0.4075 5 = East Lateral = 1.8979 1.8980 6 = West Lateral = 0.3979 0.3990 Secondary: ( inst=spectro focus=-100 alt=xxx deg T=xxxC) setmir( act ): galil ( act ): linear gauges 1 = Axial A = -1.3099 2 = Axial B = -1.2649 3 = Axial C = -1.2720 4 = Transverse = -0.0529 FOCUS LOG: ========== M1 Piston M2 Piston Temp Wind Time Inst setmir TCC setmir Az El C Dir MPH filt FWHM " WEATHER SYNOPSIS ================ High winds during the day, but died down by the sunset. Skies were clear. WEATHER DATA: ============= Wind Time Temp F Dewp F MPH Direction Dust DIMM Sky 16:01 51 6 36 284 (WNW) 2497 17:01 53 8 17 265 (W) 2811 18:01 53 8 22 281 (W) 691 19:01 51 7 28 286 (WNW) 1488 20:01 47 4 12 324 (NW) 1234 21:01 45 2 4 8 (N) 490 1.0 Clear 22:01 45 2 7 354 (N) 414 1.2 Clear 23:01 44 3 12 355 (N) 408 1.1 Clear 00:01 44 4 12 14 (NNE) 350 1.6 Clear 01:01 45 3 0 98 (E) 456 1.7 Clear 02:01 44 3 7 344 (NNW) 463 1.5 Clear pcl=partly cloudy, mclear=mostly clear LN2 SCHEDULE: ============= Spectrographs were filled at 23:50. 01:15 Dewar wt 61 lb Imager dewar was changed around 15:00. 01:15 Dewar wt 185 lb TELESCOPE STATUS: ================= Stowed at 35 deg alt, with cartridge 6 mounted. INTERLOCKS: ----------- None bypassed. SOFTWARE USED: -------------- IOP/SOP: v3_13_1 Watcher: v2_8_2 MCP: v4_2_2 TPM: v1_0_8 AstroDa: 14_24 TCC: 2.2.6 PROBLEMS IN DETAIL: =================== We spent about 3 hours trying to get the M2 galil to communicate. We worked backward through the link checking communications. The first to complain was the TCC. A host session didn't show any characters either. A telnet session to the terminal server port got no response. Craig noticed that the LEDs on the fiber transceiver at the secondary were out. Trying that module downstairs would light the LEDs. We then checked that the box was getting power. There was 32V between pins C and A on the power connector to the box. We checked the voltages on the pins from the RS232 port. On the phone cable end which goes to the fiber transceiver starting at the white wire ( connector pointed up, pins facing me ) the voltages were -10, 0, 0, 0, -11, -10 referenced to the controller box case ground. For comparison on the M1 the same string of voltage readings were +11, -11, 0, 0, 0, 0. Craig was able to get his laptop to talk to the M1 galil directly. He then tried the same thing on the M2 with permutations of baud rate and handshaking and got nothing. Next we tried using the laptop in place of the galil, and were able to talk back and forth between the laptop and a telnet session to port 3000. The problem really appears to be inside the M2 controller box, possibly with the M2 galil itself. DATA LOGS FROM IOP/SOP: =======================