Problem(s) Encountered:

We continued to have guide probe issues tonight, including the failed

return to origin (X=#### Y=0, with one surprising variation of X=0 Y=###), along with three WARNING: not at X CW limit errors that required a MIS power-cycle. Also sometimes the probe still just landed in the wrong place.

We were able to reduce the impact on our data by sending the probe to origin in between every target and selecting guide stars as close to origin as possible while still keeping them further away from the detector FOV than usual.

Solutions:

I’m not sure what else to say about this.  I brought everything down and reboot machines just to see if that may help.  That said, I moved the guide probe around a bunch today and saw nothing odd.

It should be noted that “Warning: not at X CW limit” error is a red herring and in all likelihood, can be ignored.