| Problem Reports |
|---|
| PR Number | Times | Time Lost | Description | Response |
|---|
| 4090 | 03:05-03:05, 09:52 - 09:52 | 00:00 | tracker_abort caught an exception: 'Timeout waiting for message ID 7 ACK. Receiver for tcsGiuTcsAsyncCommandSender is likely offline.'
Had attempted to do a trajectory directly from what is sent, ie, letting the load trajectory deal with structure and dome. It moved structure and dome but never started even a slew to target. When finally Aborted got the above error box. | Exitted/restarted TCS and as the structure was now set down to its 4 decimal place, put the last 2 of the decimal places in, loaded and went next and the tracker slewed and tracked on target.
Did note on second instance the TCS server was not running when looking at the 'top' command on htcs; restarted it again. |
| 4064 | 05:53-05:53, 09:36 - 09:36 | 00:00 | TCS running very slowly. Have info from a 'top' on htcs when this happened couple times. File is slow-log.txt on jove desktop.
Second instance listed while trying to load traj and then Go Next, each time getting TCS errors of 'Timeout wating for message ID 142 ACK. Receiver for tcsGuiTcsAsyncCommandSender is likely offline..' | Exit/restart TCS. |
| 4091 | 06:04-06:04 | 00:00 | Got HFC fault while slewing to lower right; had already gone slow slew to center before the faster slew to lower right;tried to clear it on dSpace using TCS method twice, does not clear, now gonna try clearing in eng mode. NOW a skew shows up skew=0.031104.
Was moving from center to lower right. | Called: Herman
Somehow between Matt and myself we went through skew recovery and succeeded on second attempt. |
| 4092 | 07:00-07:00 | 00:00 | tcsGuiTcsAsyncCommanderSender.htcs "Expected DONE for message ID 4 but got 3" obtained upon attempting to slow slew from the gotten-out-of-skew to center. Oddly, it gave this message but then it went ahead and made the move. | |