| Problem Reports |
|---|
| PR Number | Times | Time Lost | Description | Response |
|---|
| 02:53-03:20 | 00:27 | Two hexapod velocity faults and a rho following error fault prompted a restart of dSpace. Afterward no such faults occurred.
32000/02:53 H4 velocity FAULT
32459/03:01 H3 velocity fault
32880/03:08 Rho following error fault | |
| 05:00-05:00 | 00:00 | Strange trails -- perhaps due to tiny tracker or guide probe jumps -- on GC2 | |
| 4476 | 06:04-06:07 | 00:03 | Every time TCS displays an error about trajectories starting more than 1 hour in the future, it is not possible to load any more trajectories without a TCS+GUI restart. tcs_server ended up using 300% cpu before restart. | |
| 4477 | 06:12-06:18 | 00:06 | Dome error aborted track; TCS seemed to lose communication with dome. Dome az displayed 9999. Had to operate dome through DAS GUI after resolving track issue. | |
| 4478 | 05:20-05:22 | 00:02 | At 44350 An unceremonious abort occurred. Niv said that TMCS sent error to TCS but it did not display in GUI. | |
| 4479 | 04:33-04:33 | 00:00 | During track occurring at 04:33 no current trajectory information was displayed, and Cancel button was not available to be pressed. Aborted track by issuing cancel command from command line. | |
| 4480 | 08:00-11:11 | 03:11 | PFIP shutter was not operational | Called: Herman, George
|