| Problem Reports |
|---|
| PR Number | Times | Time Lost | Description | Response |
|---|
| 4321 | 00:31-02:26 | 01:55 | Could not go to any trajectory.
Error received: Failed to adjust trajectory for current tracker position.
Received error regardless of tracker position.
| Called: Jim
Jim restarted the log server and then a restart of dspace, servers and gui appeared to fix the problem. |
| 4564 | 02:12-02:14 | 00:02 | TO night report will not accept a PR including quotations. Will revert to previous state of the PR.
double quotes not working in ops checklist not working either | |
| 4508 | 04:10-04:15, 04:58-05:05 | 00:12 | Lost tracker and tcs server communications while tracker was in motion and on trajectory | Called: jim
restart servers and tried again |
| 4565 | 04:15-04:55, 05:55-10:25 | 05:10 | Essentially the same loop of unable to track on sky;
would loose comms to tcs and tracker server;
errors of - Failed to adjust trajectory to compensate for the current tracker position - and -TMCS failed to acquire trajectory
in a continuous loop...
see PR for further info | Called: jim
able to get trajectory started if everything was power cycled but only for a short time... then loop would occur again. |
| 4562 | 05:10-10:25 | 05:15 | SAMS lost comm to Bank; all sensors on 1/3 of array reporting -384 | |
| 4566 | 05:15-06:20 | 01:05 | Constant beeping being heard from dome enclosure; unsure as to what the source or reason for this is... | Called: George
George came up and assured us it wasn't a LN2 issue; He speculated it was coming from the pfip but unknown as it stopped before further information could be attained. |