Subject: Re: [sloan-25mlog 3215] 2.5m obslog 20161119 (SJD 57712) From: Olena Malanushenko Date: Sun, 20 Nov 2016 23:46:14 +0000 --Apple-Mail=_92A61192-406D-45A0-9258-5B29DB735092 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Nov 20, 2016, at 8:23 PM//Nov 20, 2016, Andr=C3=A9s Marcelo Almeida = Toro wrote: >=20 > Hello John >=20 > Just to clarify about the fiducials, after clear them they were ok. = Later in the night we had again high fiducials with AZ, we tried to = accept them several times, but did not work. Later fiducials number were = ok. I didn't see any problems going to field and get stars into the = fibers when fiducials were high. >=20 > Cheers >=20 > Andres >=20 7:20:43 Az: ind=3D31, deg=3D257.1, err=3D -1227=20 error is too large to be corrected ( > 600) 07:20:51 Az: ind=3D30, deg=3D242.1, err=3D -1155=20 error is too large to be corrected ( > 600) 07:20:58 Az: ind=3D29, deg=3D227.1, err=3D -1041=20 error is too large to be corrected ( > 600) 07:21:28 Az: ind=3D25, deg=3D167.4, err=3D -944=20 error is too large to be corrected ( > 600) 07:33:16 Az: ind=3D20, deg=3D 92.3, err=3D 764=20 error is too large to be corrected ( > 600) 07:33:24 Az: ind=3D19, deg=3D 77.3, err=3D 848=20 error is too large to be corrected ( > 600) 07:33:39 Az: ind=3D17, deg=3D 47.3, err=3D 1087=20 error is too large to be corrected ( > 600) 07:33:46 Az: ind=3D16, deg=3D 32.3, err=3D 1232=20 error is too large to be corrected ( > 600) 07:37:40 Az: ind=3D14, deg=3D 2.2, err=3D 1609=20 error is too large to be corrected ( > 600) 07:48:09 Az: ind=3D13, deg=3D-12.8, err=3D 1732=20 error is too large to be corrected ( > 600) 07:59:46 Az: ind=3D12, deg=3D-27.8, err=3D 1631=20 error is too large to be corrected ( > 600) 08:36:21 Az: ind=3D10, deg=3D-57.8, err=3D 1806=20 error is too large to be corrected ( > 600) 08:41:41 Az: ind=3D12, deg=3D-27.8, err=3D 1537=20 error is too large to be corrected ( > 600) 08:41:48 Az: ind=3D13, deg=3D-12.8, err=3D 1408=20 error is too large to be corrected ( > 600) 08:41:56 Az: ind=3D14, deg=3D 2.2, err=3D 1308=20 error is too large to be corrected ( > 600) 08:42:11 Az: ind=3D16, deg=3D 32.3, err=3D 1073=20 error is too large to be corrected ( > 600) 08:42:18 Az: ind=3D17, deg=3D 47.3, err=3D 921=20 error is too large to be corrected ( > 600) 08:42:26 Az: ind=3D18, deg=3D 62.3, err=3D 811=20 error is too large to be corrected ( > 600) 08:42:33 Az: ind=3D19, deg=3D 77.3, err=3D 695=20 error is too large to be corrected ( > 600) 08:42:41 Az: ind=3D20, deg=3D 92.3, err=3D 728=20 error is too large to be corrected ( > 600) 08:49:21 Az: ind=3D20, deg=3D 92.3, err=3D 560=20 08:49:29 Az: ind=3D19, deg=3D 77.3, err=3D 110=20 08:49:36 Az: ind=3D18, deg=3D 62.3, err=3D 106=20 08:49:44 Az: ind=3D17, deg=3D 47.3, err=3D 122=20 09:16:37 Az: ind=3D16, deg=3D 32.2, err=3D 146=20 10:09:10 Az: ind=3D16, deg=3D 32.2, err=3D -112=20 10:09:18 Az: ind=3D17, deg=3D 47.3, err=3D -159=20 10:09:25 Az: ind=3D18, deg=3D 62.3, err=3D -109=20 10:09:33 Az: ind=3D19, deg=3D 77.3, err=3D -96=20 10:09:40 Az: ind=3D20, deg=3D 92.3, err=3D 12=20 10:16:46 Az: ind=3D20, deg=3D 92.3, err=3D -164=20 10:16:54 Az: ind=3D19, deg=3D 77.3, err=3D 116=20 10:17:01 Az: ind=3D18, deg=3D 62.3, err=3D 95=20 10:17:09 Az: ind=3D17, deg=3D 47.3, err=3D 117=20 10:17:16 Az: ind=3D16, deg=3D 32.2, err=3D 146=20 10:36:34 Az: ind=3D14, deg=3D 2.2, err=3D 250=20 11:05:22 Az: ind=3D13, deg=3D-12.8, err=3D 448=20 11:36:11 Az: ind=3D13, deg=3D-12.8, err=3D -175=20 11:36:19 Az: ind=3D14, deg=3D 2.2, err=3D -158=20 11:36:34 Az: ind=3D16, deg=3D 32.2, err=3D -262=20 11:36:41 Az: ind=3D17, deg=3D 47.3, err=3D -158=20 11:36:49 Az: ind=3D18, deg=3D 62.3, err=3D -125=20 11:36:56 Az: ind=3D19, deg=3D 77.3, err=3D -124=20 11:37:04 Az: ind=3D20, deg=3D 92.3, err=3D 36=20 12:05:26 Az: ind=3D25, deg=3D167.4, err=3D -689=20 error is too large to be corrected ( > 600) 12:46:00 Az: ind=3D25, deg=3D167.4, err=3D -606=20 error is too large to be corrected ( > 600) 13:19:16 Az: ind=3D25, deg=3D167.4, err=3D -606=20 error is too large to be corrected ( > 600) 23:42:53 Az: ind=3D25, deg=3D167.4, err=3D -606=20 error is too large to be corrected ( > 600) > 2016-11-20 10:02 GMT-07:00 John Downey >: >=20 > > On Nov 20, 2016, at 9:17 AM, Kaike Pan > wrote: > > > > Andres is doing great as a new observer. Just in case there is any = issue with his afternoon checkout, > > I went to the site yesterday (dayshift has not started yesterday). = Here I was there when these happened. >=20 > Yes, I don't doubt it at all, just needed a little clarification as to = the nature of the problems seen yesterday. >=20 > > > >> On Nov 20, 2016, at 8:31 AM, John Downey > wrote: > >> > >>> Notes: > >>> > >>> 1) 6:14 - 8:47 AZ fiducials could not be read. > >>> > >> > >> What does this mean? Later in the log I see "fiducials ok". > >> Did no AZ fiducials read during afternoon checkout? Did the usual = ones not read? Did this change after afternoon checkout? > > > > Andres and Elena can correct me if this is not what you want to = state. > > several AZ fiducials around ID=3D21 would not read, but fiducials = are fine when they are read out at other IDs. At least, this is > > what I saw during afternoon checkout and several days ago. > > >=20 > Ok, that is just what we needed to know. This is "normal" for the = moment, and though not desirable, not something we are planning to = correct before Dec flex time. The current plan for Dec engineering is = to adjust the AZ read head and hopefully reduce the number of misses in = the low 20's, then take fiducial data the next morning so that the night = staff can take pointing model data. >=20 >=20 > >> > >> > >>> Had problems with altitude, when moving from instrument change = position to stow > >>> position. Had to powercycle the altitude amplifier and the wind = baffle. It seems > >>> the same problem as last night. > >> > >> I do not believe this is the same problem as the previous night, = based on what I saw remotely Friday night and what I was told of the = problem yesterday afternoon. > >> > >> The problem Friday night was that the ALT axis would not move at = moderate to high speed using the MCP, but it was moved several degrees = at a slow velocity using the MCP - hence the long shot of power cycling = the Glentek in the hopes that the brownout mentioned had somehow upset = it. We got lucky and it worked. > >> > >> The problem yesterday afternoon was, as far as I can tell from = Kaike's description afterwards, that the windbaffle was not moving - the = telescope would move with the TCC for ~30 arcmin before tripping and was = fixed by power cycling the windbaffle ALT amplifier. > >> > >> Before we can call it the same problem, we will need to see both = again when engineering staff is on site. The Glentek problem we are = simply assuming none of the module lights were red, but we would need to = confirm that (I'm afraid I was only half awake and I don't remember if I = asked Gordon about that). Probably there was an indication of what part = of the Glentek was unhappy, though there is also the slim chance that = something else was unhappy and power cycling the Glentek cleared it. I = don't think so, however, because it would move slowly but not quickly, = the problem was most likely in the Glentek. > > > > After a cartridge change and fiducial check, the telescope would not = move to 121, 30 from 121, 90. "Axis init" cleared all axis, but the alt = brake came back on, the motion stopped after a few arc minute movement = in alt. We cleared axis and moved it again, the same. These symptoms = were the same as those observed in the previous night up to this point. > > > > However, we didn=E2=80=99t try yo move the telescope from MCP. so we = didn=E2=80=99t know if the telescope would move fine from MCP with a = lower speed. > > We powered cycle altitude amplifiers and moved the telescope again. = The results were the same: "Axis init" cleared all axis, but the alt = brake came back on, the motion stopped after a few arc minute movement = in alt. With the four attempts: two without powering cycle alt = amplifiers and two with, the altitude axes moved about 40 arc minutes or = so. > > > > When the telescope stopped, alt forward permission and back = permission bits were set, and altitude logic tree show = =E2=80=9Cwind_alt_fault=E2=80=9D was true (green). I meant to check WB = amp LED, but unfortunately, I had a stop engaged before I went down, so = no information was collected. > > Anyway, I turned WB knife switch off and on, things works fine from = then: We moved the telescope several times between stow and > > instrument changes without any issue. > > > > Before I left the site, I showed Elena and Andres how to check WB = LED error code if there is any, and told them that if the same problem = happening again, don=E2=80=99t engage any stop button, go downstair to = check and write error code on WB LED, then call JohnD with the code. = Fortunately, system worked fine last fine. >=20 > The clue that this is not the same as Friday night is the distance = moved before the telescope brakes came on - Friday night movement was = unrestricted through several degrees at a velocity increment of 1000 = (though I don't recall now how many increments Gordon was using to check = it). It was the velocity, not the distance moved that was limiting = motion. >=20 > Last night, clearly the windbaffle was not moving, so the telescope = was driving normally until it hit the windbaffle bumper. Thirty or = forty arc minutes is just about that distance (I had this happen once = before when the new ALT system was installed last summer). The = synchronizing device moves the baffle to follow the telescope rather = than the other way around, so nothing prevents the telescope from = driving into the baffle bumper. >=20 > If the problem does not repeat in the next week, I doubt there is much = to worry about here. > ____________________________________________________________ > Logs of Nightly APO Activities > > = https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html = >=20 >=20 > --=20 > Andres Almeida Toro > Magister en Ciencias F=C3=ADsicas > Asistente Operaciones Proyecto APOGEE2 > Asistente de Investigaci=C3=B3n Acad=C3=A9mica=20 > Direcci=C3=B3n de Investigaci=C3=B3n=20 > Universidad de La Serena > ____________________________________________________________ > Logs of Nightly APO Activities > = https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html --Apple-Mail=_92A61192-406D-45A0-9258-5B29DB735092 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 On Nov 20, 2016, at 8:23 PM//Nov 20, 2016, Andr=C3=A9s = Marcelo Almeida Toro wrote:Hello JohnJust to clarify about the fiducials, after clear them they = were ok. Later in the night we had again high fiducials with AZ, we = tried to accept them several times, but did not work. Later fiducials = number were ok. I didn't see any problems going to field and get stars = into the fibers when fiducials were high.CheersAndres7:20:43 Az: = ind=3D31, deg=3D257.1, err=3D = -1227 = error is too large to be corrected ( > = 600)07:20:51 Az: ind=3D30, deg=3D242.1, = err=3D -1155 = error is too large to be corrected ( = > 600)07:20:58 Az: ind=3D29, deg=3D227.1,= err=3D -1041 = error is too large to be corrected ( = > 600)07:21:28 Az: ind=3D25, deg=3D167.4,= err=3D -944 = error is too large to be corrected ( = > 600)07:33:16 Az: ind=3D20, deg=3D = 92.3, err=3D 764 = error is too large to be = corrected ( > 600)07:33:24 Az: ind=3D19, = deg=3D 77.3, err=3D 848 = error is too = large to be corrected ( > 600)07:33:39 Az: = ind=3D17, deg=3D 47.3, err=3D = 1087 = error is too large to be corrected ( > = 600)07:33:46 Az: ind=3D16, deg=3D 32.3, = err=3D 1232 = error is too large to be corrected ( = > 600)07:37:40 Az: ind=3D14, deg=3D = 2.2, err=3D 1609 = error is too large to = be corrected ( > 600)07:48:09 Az: ind=3D13, = deg=3D-12.8, err=3D 1732 = error is too = large to be corrected ( > 600)07:59:46 Az: = ind=3D12, deg=3D-27.8, err=3D = 1631 = error is too large to be corrected ( > = 600)08:36:21 Az: ind=3D10, deg=3D-57.8, = err=3D 1806 = error is too large to be corrected ( = > 600)08:41:41 Az: ind=3D12, deg=3D-27.8,= err=3D 1537 = error is too large to be corrected ( = > 600)08:41:48 Az: ind=3D13, deg=3D-12.8,= err=3D 1408 = error is too large to be corrected ( = > 600)08:41:56 Az: ind=3D14, deg=3D = 2.2, err=3D 1308 = error is too large to = be corrected ( > 600)08:42:11 Az: ind=3D16, = deg=3D 32.3, err=3D 1073 = error is too = large to be corrected ( > 600)08:42:18 Az: = ind=3D17, deg=3D 47.3, err=3D = 921 = error is too large to be corrected ( > = 600)08:42:26 Az: ind=3D18, deg=3D 62.3, = err=3D 811 = error is too large to be corrected ( = > 600)08:42:33 Az: ind=3D19, deg=3D = 77.3, err=3D 695 = error is too large to be = corrected ( > 600)08:42:41 Az: ind=3D20, = deg=3D 92.3, err=3D 728 = error is too = large to be corrected ( > 600)08:49:21 Az: = ind=3D20, deg=3D 92.3, err=3D = 560 08:49:29 Az: ind=3D19, deg=3D = 77.3, err=3D 110 08:49:36 Az: = ind=3D18, deg=3D 62.3, err=3D = 106 08:49:44 Az: ind=3D17, deg=3D = 47.3, err=3D 122 09:16:37 Az: = ind=3D16, deg=3D 32.2, err=3D = 146 10:09:10 Az: ind=3D16, deg=3D = 32.2, err=3D -112 10:09:18 Az: = ind=3D17, deg=3D 47.3, err=3D = -159 10:09:25 Az: ind=3D18, deg=3D = 62.3, err=3D -109 10:09:33 Az: = ind=3D19, deg=3D 77.3, err=3D = -96 10:09:40 Az: ind=3D20, deg=3D = 92.3, err=3D 12 10:16:46 Az: ind=3D20,= deg=3D 92.3, err=3D -164 10:16:54 = Az: ind=3D19, deg=3D 77.3, err=3D = 116 10:17:01 Az: ind=3D18, deg=3D = 62.3, err=3D 95 10:17:09 Az: ind=3D17,= deg=3D 47.3, err=3D 117 10:17:16 = Az: ind=3D16, deg=3D 32.2, err=3D = 146 10:36:34 Az: ind=3D14, deg=3D = 2.2, err=3D 250 11:05:22 Az: = ind=3D13, deg=3D-12.8, err=3D = 448 11:36:11 Az: ind=3D13, deg=3D-12.8,= err=3D -175 11:36:19 Az: ind=3D14, = deg=3D 2.2, err=3D -158 11:36:34 = Az: ind=3D16, deg=3D 32.2, err=3D = -262 11:36:41 Az: ind=3D17, deg=3D = 47.3, err=3D -158 11:36:49 Az: = ind=3D18, deg=3D 62.3, err=3D = -125 11:36:56 Az: ind=3D19, deg=3D = 77.3, err=3D -124 11:37:04 Az: = ind=3D20, deg=3D 92.3, err=3D = 36 12:05:26 Az: ind=3D25, deg=3D167.4, = err=3D -689 = error is too large to be corrected ( = > 600)12:46:00 Az: ind=3D25, deg=3D167.4,= err=3D -606 = error is too large to be corrected ( = > 600)13:19:16 Az: ind=3D25, deg=3D167.4,= err=3D -606 = error is too large to be corrected ( = > 600)23:42:53 Az: ind=3D25, deg=3D167.4,= err=3D -606 = error is too large to be corrected ( = > 600)2016-11-20 10:02 GMT-07:00 John Downey : > On Nov 20, 2016, at 9:17 AM, Kaike Pan = wrote: > > Andres is doing great as a new observer. Just in case there is any = issue with his afternoon checkout, > I went to the site yesterday (dayshift has not started yesterday). = Here I was there when these happened. Yes, I don't doubt it at all, just needed a little clarification = as to the nature of the problems seen yesterday. > >> On Nov 20, 2016, at 8:31 AM, John Downey wrote: >> >>> Notes: >>> >>> 1) 6:14 - 8:47 AZ fiducials could not be read. >>> >> >> What does this mean? Later in the log I see "fiducials = ok". >> Did no AZ fiducials read during afternoon checkout? Did = the usual ones not read? Did this change after afternoon = checkout? > > Andres and Elena can correct me if this is not what you want to = state. > several AZ fiducials around ID=3D21 would not read, but fiducials = are fine when they are read out at other IDs. At least, this is > what I saw during afternoon checkout and several days ago. > Ok, that is just what we needed to know. This is "normal" = for the moment, and though not desirable, not something we are planning = to correct before Dec flex time. The current plan for Dec = engineering is to adjust the AZ read head and hopefully reduce the = number of misses in the low 20's, then take fiducial data the next = morning so that the night staff can take pointing model data. >> >> >>> Had problems with altitude, when moving from instrument = change position to stow >>> position. Had to powercycle the altitude amplifier and the = wind baffle. It seems >>> the same problem as last night. >> >> I do not believe this is the same problem as the previous = night, based on what I saw remotely Friday night and what I was told of = the problem yesterday afternoon. >> >> The problem Friday night was that the ALT axis would not move = at moderate to high speed using the MCP, but it was moved several = degrees at a slow velocity using the MCP - hence the long shot of power = cycling the Glentek in the hopes that the brownout mentioned had somehow = upset it. We got lucky and it worked. >> >> The problem yesterday afternoon was, as far as I can tell from = Kaike's description afterwards, that the windbaffle was not moving - the = telescope would move with the TCC for ~30 arcmin before tripping and was = fixed by power cycling the windbaffle ALT amplifier. >> >> Before we can call it the same problem, we will need to see = both again when engineering staff is on site. The Glentek problem = we are simply assuming none of the module lights were red, but we would = need to confirm that (I'm afraid I was only half awake and I don't = remember if I asked Gordon about that). Probably there was an = indication of what part of the Glentek was unhappy, though there is also = the slim chance that something else was unhappy and power cycling the = Glentek cleared it. I don't think so, however, because it would = move slowly but not quickly, the problem was most likely in the = Glentek. > > After a cartridge change and fiducial check, the telescope would = not move to 121, 30 from 121, 90. "Axis init" cleared all axis, but the = alt brake came back on, the motion stopped after a few arc minute = movement in alt. We cleared axis and moved it again, the same. These = symptoms were the same as those observed in the previous night up to = this point. > > However, we didn=E2=80=99t try yo move the telescope from MCP. so = we didn=E2=80=99t know if the telescope would move fine from MCP = with a lower speed. > We powered cycle altitude amplifiers and moved the telescope again. = The results were the same: "Axis init" cleared all axis, but the = alt brake came back on, the motion stopped after a few arc minute = movement in alt. With the four attempts: two without powering cycle alt = amplifiers and two with, the altitude axes moved about 40 arc minutes or = so. > > When the telescope stopped, alt forward permission and back = permission bits were set, and altitude logic tree show = =E2=80=9Cwind_alt_fault=E2=80=9D was true (green). I meant to check WB = amp LED, but unfortunately, I had a stop engaged before I went down, so = no information was collected. > Anyway, I turned WB knife switch off and on, things works fine from = then: We moved the telescope several times between stow and= > instrument changes without any issue. > > Before I left the site, I showed Elena and Andres how to check WB = LED error code if there is any, and told them that if the same problem = happening again, don=E2=80=99t engage any stop button, go downstair to = check and write error code on WB LED, then call JohnD with the code. = Fortunately, system worked fine last fine. The clue that this is not the same as Friday night is the = distance moved before the telescope brakes came on - Friday night = movement was unrestricted through several degrees at a velocity = increment of 1000 (though I don't recall now how many increments Gordon = was using to check it). It was the velocity, not the distance = moved that was limiting motion. Last night, clearly the windbaffle was not moving, so the telescope was = driving normally until it hit the windbaffle bumper. Thirty or = forty arc minutes is just about that distance (I had this happen once = before when the new ALT system was installed last summer). The = synchronizing device moves the baffle to follow the telescope rather = than the other way around, so nothing prevents the telescope from = driving into the baffle bumper. If the problem does not repeat in the next week, I doubt there is much = to worry about here. ____________________________________________________________ Logs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html-- Andres = Almeida ToroMagister en Ciencias F=C3=ADsicasAsistente Operaciones Proyecto APOGEE2Asistente de Investigaci=C3=B3n Acad=C3=A9mica Direcci=C3=B3n de Investigaci=C3=B3n Universidad de La Serena ____________________________________________________________Logs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/= index.html= --Apple-Mail=_92A61192-406D-45A0-9258-5B29DB735092--