Problem(s) Encountered:

The remote connector for Workstation 1 appears to have died, or it''s almost dead. Around UT 5:30, during an exposure, WS1 appeared to go dead - the monitors went into power save mode and it didn''t (immediately) respond to mouse movement or hitting arrow keys. After about a minute, everything came back up, we just had to click  connect  on the remote connector screen. After that (and maybe before?) we heard a low beeping sound periodically but couldn''t find a visible cause.

Around UT 10:30, WS1 appeared to go dead again and stayed that way for about 20 minutes. We called Jules and determined that the issue was the connector, not WS1 itself. Power-cycling the connector got it working again, although the connector went on and off ~5 times in the next 3 minutes. It was enough to start a new target, but then it went off and stopped responding to power-cycling.

We borrowed the remote connector from WS2 to get our final primary target. We continued hearing the same low beeping sounds from earlier (I think these are coming from the connector but it''s not totally clear). We reconnected it to WS2 and closed up around UT 12:00.

Solutions:

The device that failed is the Dell FX100 Remote Access Device (RAD).  Hooked it back up and it showed no signs of life.  Replaced with the only spare I have (which incidentally was acquired from the National Solar Observatory a number of years ago) and all is well again.  As Rick Pogge stated:

"This is a reminder that we''re working with 5+ year old equipment that is hard to replace.  We should probably look at a replacement, e.g., a NUC properly configured to take its place.  Cost is about the same as a new Teradici, provided we can get one that is compatible with the cards in the Dell computers."

I should also mention, as a workaround, one could VNC from the usable workstation in the event of a failure.  In this instance:

Go to mdm24ws2 and open a terminal window.  From there, ssh to mdm24ws2.kpno.noao.edu (if required to use an IP address, the appropriate address can be found on a list of IPs that is displayed on the cork board in the control room) as obs24m.  If prompted for a password, use the standard MDM flavor, located on the control room white board.  Once in, type:

x11vnc -nomodtweak -display :0 and hit enter.

A bunch of info will scroll by and should end with the line port=5900.

Open tigervnc from the taskbar and enter the IP address for mdm24ws1.

This could also be performed from any user laptop that is wired to the MDM network.