| Problem Reports |
|---|
| PR Number | Times | Time Lost | Description | Response |
|---|
| 4172 | 04:48-04:50 | 00:02 | Full length tails along a column on the ACQ camera for satellite GOES 14. Image saved is named 20151019T044747.5_acm_sci.fits. Checked by RA, not overexposed. The tail counts are not much above background but enough to see. See images and screen shot in the bug report.
| |
| 4192 | 05:58-06:05 | 00:07 | Hit go next on a target from the RA, the dome and structure moved but the tracker did nothing (command never turned green in the tcs gui command status box). Aborted after ~4 minutes. No error when hitting the abort button either. Tried to load the trajectory manually using the Ra/Dec tab under Trajectory in tcs gui and it did not load (command never turned green in the status box). tcs_server was found to be at 100% on htcs computer. Restarted the servers and the TCS gui and tried which solved the problem. | |
| 4088 | 06:09-06:15 | 00:06 | While on trajectory did three moves down in focus by 0.5 mm and received a HFC fault. No error codes presented. Entered Ra/Dec in manually and tried to reacquire the trajectory which worked. | |
| 4172 | 06:20 -06:20 | 00:00 | While taking another image we had a strange artifact in the center of the image which was also seen earlier but thought to be caused possibly by clouds. The image name is: 20151019T061902.4_acm_sci.fits The state of the tip TT camera was unknown so this may be a tip till issue. 20151019T062628.7_acm_sci.fits Shows another interesting feature of unknown origin... The second feature was in several frames. Checked tip and tilt visually by putting stars out of focus and making sure the light was the same all around the "donut" shaped out of focus star. | |
| 4088 | 06:32-06:35 | 00:03 | While trying to adjust focus down by 0.5 mm and I received another HFC error. Reset error and prepared to go to another target. This resolved the problem. | |
| 4193 | 07:57-08:00, 09:06-09:10 | 00:07 | Got a birdie on the ACQ camera. Restarted TCS gui and it was fixed. see screenshot in bug report. | |
| 4194 | 08:52-09:05 | 00:13 | Told the telescope to go to DIRECTV 10 but did not see any stationary points in the feild of view. Only saw stars streaking through. System shows on trajectory and the tracker appears to be operating correctly. We will try goes 14 and see if we get anything. Goes 14 showed a definite satellite so we tried to go back to DIRECTV 10 and saw nothing again. No reason why... We ended up just using GOES 14. | |
| 4176 | 09:39-09:50 | 00:11 | Got a "go next" target from the RA, then I hit go next and nothing happened. tcs_server at 100% on htcs. Executed the killall -6 tcs_server command after trying to cancel the trajectory using syscmd failed. Then I restarted tcs_server by command line (startsys -v -T) which solved the problem. | |
| 4195 | 10:20-10:20 | 00:00 | Adjusted focus twice, then turned off the ACQ camera pipeline. A minute or so after that we got an HFC fault. We were stable on this trajectory from 9:55 UTC till 10:20 UTC. No error presented other than the HFC fault. | |
| 4191 | 04:00-04:40 | 00:40 | Aborted trajectory GOES 14, moved structure off of target and tried to reacquire GOES 14 trajectory. This caused an HFC fault. No other errors given. In htcs terminal I got an error that I havent seen before (see below).
Traceback (most recent call last):
File "/opt/het/hetdex/bin/trajectory", line 454, in
tcs.go_next( move_structure=MoveStructure, move_dome=MoveDome )
File "", line 3, in go_next_method
pytcs.error: remote exception: failed to acquire trajectory.
Cleared HFC fault, unchecked the move structure and dome boxes in the trajectory tab just in case, moved structure to 185 degrees and attempted to acquire the trajectory for GOES 14 again. While trying to reacquire the trajectory the tracker did bring the satellite into ACQ camera field of view but then the brakes engaged and no error was given even though the trajectory was not acquired. Restarted dSpace and reinitialized then retried same procedure in previous sentences to acquire trajectory for GOES 14. The tracker then properly acquired the trajectory.
| |
| 4187 | 06:37-06:40 | 00:03 | Going to a new target the structure moved correctly then the brakes engaged and I received a "no currently active trajectory" error (Trajectory Az: 0.0). No HFC fault or any other errors present. Cleared error and tried to reacquire without moving structure or dome since they were at correct azimuth which worked.
{
"__exception_type": 1,
"__exception_string": "no currently active trajectory.",
"__exception_file": "tcs_driver.cpp",
"__exception_line": 461,
"__exception_func": "cancel_trajectory",
"__effective_id": 48,
"__original_id": 26,
"__origin": "tcsGuiTcsAsyncCommandSender.jove.1660.01179d5c3->tcp://192.168.66.31:30300",
"__handler": "go_next",
"__async": "true",
"__done": "true",
"__ack": "false",
"__error": "true",
"__data_time": "1445236634.607351709",
"__wire_time": "1445236634.607352909",
"__data": "false",
"__pid": 31718
} | |
| 4188 | 07:05-07:10 | 00:05 | KNOWN PROBLEM
Az:180 recieved the east/west incompatible error again on a target from the RA. Reloaded target manually and went to it without moving structure or dome. Error message below.
{
"__exception_type": 7,
"__exception_string": "Requested azimuth (180.010580) and direction East are incompatible.",
"__exception_file": "point.cpp",
"__exception_line": 43,
"__exception_func": "Point",
"__effective_id": 93,
"__original_id": 39,
"__origin": "tcsGuiTcsAsyncCommandSender.jove.1660.01179d5c3->tcp://192.168.66.31:30300",
"__handler": "go_next",
"__async": "true",
"__done": "true",
"__ack": "false",
"__error": "true",
"__data_time": "1445238272.000848563",
"__wire_time": "1445238272.000851253",
"__data": "false",
"__pid": 31718
} | |