| Problem Reports |
|---|
| PR Number | Times | Time Lost | Description | Response |
|---|
| 4499 | 04:28-04:40 | 00:12 | Got many errors while trying to go to a target. HFC fault with the following errors. There was also a Prof light out for the LX Slew motor. This happened right after stacking and restarting the tcs server. Target: HR5216 Ra: 13.8389 Dec: 58.58 Az: 28.1394
Cleared the HFC fault and sent the target another time and recieved a TMCS failed to acquire trajectory error (see below). Shut down the gui and all servers and then restarted them. Details in PR
| |
| 4501 | 05:25-06:12 | 00:47 | LX Torque limit light turned red on ControlDesk. Recovery involved overriding Torque Limit on ControlDesk and slow slewing back and forth until Trq light turned green again. After recovery it worked fine. However, due to triggered recordings and possible other problems operating in ControlDesk went very slowly. | |
| 4502 | 05:00-05:00 | 00:00 | Commanding a camera filter to a certain color changes the filter, but the filter indicator does not indicate the filter commanded. Either the wrong filter is being commanded or the wrong filter is being indicated. | |
| 4500 | 05:23-05:24 | 00:01 | Got an H6 velocity fault at 41010/05:23 | |
| 4498 | 04:50-05:24, 06:13 - 10:52 | 05:13 | While trying to offset the probe so that the star of interest was in the center of the field it was noticed that the offsets were in the exact opposite direction of what they should be.
Unix time: 146147370
(Later) Offsets commanded from Guider2 Camera are offset correct distance but incorrect direction. Direction of offset varies depending on azimuth. It's suspected that offset direction is a constant that does not change depending on telescope azimuth or probe angle. We saved Guider2 images at the azimuths where we tested this. We are dead in the water as long as this does not get fixed. We did not call recommended person (Jason) due to late hour and quality of sky. We left the servers running.
| Saved a few guider 2 images and an ACAM image and Matt was going to look at the headers to probe what may be the issue. We decided to then restart the servers and gui and see if this problem still exists. |