Date: Fri, 13 Aug 2021 15:04:20 -0600 From: APO Subject: Re: [sloan-25mlog 5599] Re: 2.5m obslog 20210811 (SJD 59438) =0A= =0A= =0A= =0A= =0A= =0A= I found the problem. There=E2=80=99s a short in the 1= m switch. It broke and wasn=E2=80=99t normally closed like it should have b= een. I made a weekend repair and will have James fix it on Monday.I tried to do the evening calls but it was giving me a cal bo= x error. I checked the power and the lamp power boxes don=E2=80=99t look li= ke they are working. The fuses were all good so I don=E2=80=99t know why.&n= bsp;=0A= Ryan WagnerTelescope Tech = Inter.2001 Apache Point Rd.Sunspot, NM. 88349= rwagner@apo.nmsu.com=0A= =0A= =0A= =0A= From: Wilson, John C (jcw6z) Sent:= Friday, August 13, 2021 12:09To: Daniel Oravetz; Ryan Wagne= rCc: obs-report-25m@apo.nmsu.eduSubject: Re: [sloan-2= 5mlog 5599] Re: 2.5m obslog 20210811 (SJD 59438) =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Ryan,=0A= =0A= =0A= =0A= =0A= It could be that the single switch trigger bolt/bushing are, incorrectly, i= n the same position for both 1m and dense ports. I think I saw that w= hile the parts were at uva.=0A= =0A= =0A= =0A= =0A= Thanks,=0A= =0A= =0A= =0A= =0A= John=0A= =0A= =0A= =0A= =0A= Get Outlook for iOS=0A= =0A= =0A= From: sloan-25mlog on behalf of Daniel Oravetz =0A= Sent: Friday, August 13, 2021 1:42:42 PM=0A= To: Ryan Wagner =0A= Cc: obs-report-25m@apo.nmsu.edu =0A= Subject: [sloan-25mlog 5599] Re: 2.5m obslog 20210811 (SJD 59438)=0A= =0A= =0A= =0A= Hi Ryan,=0A= =0A= The MCP reads the gang connector position from the PLC and then the=0A= mcp.apogeeGang keyword gets read in STUI for that STUI MCP gang-connector=0A= status. Currently, the PLC is showing BOTH the apogee_gc_at_1m AND=0A= apogee_gc_at_dense bits are set (see attached screenshot). So the MCP= =0A= seems to be doing what it's supposed to -- reading what the PLC is saying=0A= and then populating apogeeGang with that value -- but the PLC seems to be=0A= wrong, or maybe there's a hardware issue in the switches causing both= =0A= those bits to be set at the same time?=0A= =0A= The value being broadcast ('44') isn't a "valid" value, it isn't in the= =0A= gangMap tabulation that STUI uses to make sense of the values:=0A= =0A= gangMap =3D {0: self.GANG_UNKNOWN,=0A= &nb= sp; 1: self.GANG_DISCONNECTED,=0A= &nb= sp; 2: self.GANG_ON_CARTRIDGE,=0A= &nb= sp; 4: self.GANG_ON_PODIUM,=0A= &nb= sp; 12: self.GANG_AT_DENSE,=0A= &nb= sp; 20: self.GANG_AT_SPARSE,=0A= &nb= sp; 36: self.GANG_AT_1M=0A= &nb= sp; }=0A= =0A= So there's a '?' instead:=0A= =0A= strVal =3D self.mcpModel.apogeeG= angLabelDict.get(keyVar[0], "?")=0A= =0A= The crux of the problems still seems to be at the PLC level or the=0A= switches, though, because that's what MCP is reading and then passing up=0A= the chain.=0A= =0A= I sent an email to Jeff to clarify the handling of the MCP/TPM GUI in this=0A= case - if both the 1m AND Dense bits are set, seems like the MCP/TPM GUI=0A= should be displaying a status that's NOT "Dense", but a '?' of its own.= =0A= =0A= Dan=0A= =0A= > Audrey,=0A= > I think I see where you are seeing the 1m readout when it is in the de= nse=0A= > pak port. The MCP shows the correct location but it seems like there i= s a=0A= > miscommunication between the MCP and STUI. STUI is showing a =C3=A2=E2= =82=AC=C5=93?" On my=0A= > computer for the gang location. I=C3=A2=E2=82=AC=E2=84=A2m not sure ho= w to fix the readout in=0A= > STUI but when I ran 'hub startNubs mcp' I got :=0A= > 20:54:13 .mcp 29 mcp i apogeeGang=3D44=0A= > 20:54:13 InvalidKeywordData=3Dmcp.apogeeGang, ['44=C3=A2=E2=82=AC=E2= =84=A2]=0A= >=0A= > So I am pretty sure there is a communication error or an error in the = STUI=0A= > code somewhere.=0A= >=0A= > I tried to do evening cals to see if an error popped up and it said th= at=0A= > gan is supposed to be at =C3=A2=E2=82=AC=E2=84=A212=C3=A2=E2=82=AC=E2= =84=A2 so I think that a few numbers need to be=0A= > changed or something.=0A= >=0A= >=0A= > Sorry, not sure what to do about it.=0A= >=0A= > Jos=C3=83=C2=A9 or Conor?=0A= >=0A= > Thanks,=0A= >=0A= > Ryan=0A= >=0A= >> On Aug 12, 2021, at 03:15, asimmons@apo.nmsu.edu wrote:=0A= >>=0A= >> The APOGEE gang connector is currently plugged into the dense pack= =0A= >> within the=0A= >> podium. However, the connector reads from the software that it cur= rently=0A= >> resides=0A= >> in the 1m.=0A= >=0A= > ____________________________________________________________=0A= > Logs of Nightly APO Activities =0A= > =0A= https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html=0A= >=0A= =0A= =0A= =0A= =0A= =