| Problem Reports |
|---|
| PR Number | Times | Time Lost | Description | Response |
|---|
| 4183 | 02:14-02:18, 08:12-08:12 | 00:04 | Telescope not going to requested RA and DEC. Requested RA: 21.1146 Requested Dec: -6.00934. Actual RA: 21.12854 Actual Dec: -5.9755. Is this within tolerance (seems like a bit)? Tracker Postion X: approx. -0.158 Y:approx. +0.4094. We chose a different target and that worked fine.
Throughout the night I kept an eye on this problem and on average the pointing was off by 0.02 hrs for RA (0.02 hrs too high). Dec movements seemed to be better than listed above for the rest of the night. These RA errors held true even after dspace was reset and reinitialized. | |
| 4184 | 02:30-02:36 | 00:06 | HFC fault slewing to target at AZ:180 Degrees. The PWr column is all oranged out. Reset falt and reacquired trajectory the tracker did not move though it showed in tcs gui as being on trajectory (green bubble in trajectory tab). Was not tracking the sky. Aborted and tried a second time and it finally moved to the correct place. | |
| 4185 | 05:24-06:24 | 01:00 | While slewing to target got the error below accompanied by an HFC fault. Target RA: 0.428669 hrs Dec: 68.8445 degrees. Tried to send the trajectory through again and got a similar error posted below the first error. Tried to clear the HFC fault and it just kept coming back.
{
"__exception_type": 1,
"__exception_string": "failed to acquire trajectory.",
"__exception_file": "tcs_driver.cpp",
"__exception_line": 502,
"__exception_func": "go_next",
"__effective_id": 195,
"__original_id": 73,
"__origin": "tcsGuiTcsAsyncCommandSender.jove.18818.005b645b4->tcp://192.168.66.31:30300",
"__handler": "go_next",
"__async": "true",
"__done": "true",
"__ack": "false",
"__error": "true",
"__data_time": "1445145772.001603206",
"__wire_time": "1445145772.001604882",
"__data": "false",
"__pid": 8225
}
{
"__exception_type": 1,
"__exception_string": "failed to acquire trajectory.",
"__exception_file": "tcs_driver.cpp",
"__exception_line": 502,
"__exception_func": "go_next",
"__effective_id": 197,
"__original_id": 75,
"__origin": "tcsGuiTcsAsyncCommandSender.jove.18818.005b645b4->tcp://192.168.66.31:30300",
"__handler": "go_next",
"__async": "true",
"__done": "true",
"__ack": "false",
"__error": "true",
"__data_time": "1445146070.001544442",
"__wire_time": "1445146070.001545967",
"__data": "false",
"__pid": 8225
}
| Called: Amy
She walked me though how to find out why the fault was not resetting. We found out that it was because the tracker was skewed. She came up to the HET and helped fix the skew as well as helped work through the computer completely locking up. We restarted the computer and all of the software and things seem to be working now. |
| 4190 | 06:15-06:15 | 00:00 | Firefox weather profile would not launch and gave the following error after we restarted the computer. Tried the kill Firefox shortcut with no luck.
Error:
Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.
| |
| 4186 | 07:18-07:46 | 00:28 | Failed to acquire trajectory. Tried to abort and got the message below. Restarted TCS for good measure. Tried to set up on another target and got another HFC fault with no errors messages. This occurred right after a -0.5 focus adjustment. I reloaded the target and tried again but the tracker did not move then eventually fired the brakes with no errors. Going to try to restart dspace and tcs to see if that helps with these problems. After resetting the previously mentioned things I received another HFC fault for a different target at the same Azimuth (dome and structure set not to move).
tracker_abort caught an exception: 'Timeout waiting for message ID 18 ACK. Receiver for tcsGuiTcsAsyncCommandSender is likely offline.'
| |
| 4187 | 07:46-08:05, 09:47-10:15, 11:16-11:20 | 00:51 | Hit go next on target from RA and recieved error below. Cleared the error and input the trajectory by Right Ascension and Declination. Loaded the trajectory and hit go next. It slewed to object ok but then I got an HFC fault after trying to move down in focus twice with an increment of 0.5. No error was presented at the time. Tried to go to the trajectory a second time and the tracker did not seem to move, then the brakes fired and the trajectory was never acquired, no errors given.
{
"__exception_type": 1,
"__exception_string": "no currently active trajectory.",
"__exception_file": "tcs_driver.cpp",
"__exception_line": 461,
"__exception_func": "cancel_trajectory",
"__effective_id": 9,
"__original_id": 7,
"__origin": "tcsGuiTcsAsyncCommandSender.jove.26308.05daa164f->tcp://192.168.66.31:30300",
"__handler": "go_next",
"__async": "true",
"__done": "true",
"__ack": "false",
"__error": "true",
"__data_time": "1445154385.922848218",
"__wire_time": "1445154385.922849194",
"__data": "false",
"__pid": 31357
}
This error occured again for no known reason (target was sent by RA)... error message below. Tried to reacquire the trajectory and the tracker did not move but was indicating it was on trajectory in the tcs gui(green bubble in trajectory tab of tcs gui). Aborted and Tried again and got an HFC fault.
{
"__exception_type": 1,
"__exception_string": "no currently active trajectory.",
"__exception_file": "tcs_driver.cpp",
"__exception_line": 461,
"__exception_func": "cancel_trajectory",
"__effective_id": 118,
"__original_id": 66,
"__origin": "tcsGuiTcsAsyncCommandSender.jove.26308.05daa164f->tcp://192.168.66.31:30300",
"__handler": "go_next",
"__async": "true",
"__done": "true",
"__ack": "false",
"__error": "true",
"__data_time": "1445161654.818126232",
"__wire_time": "1445161654.818127171",
"__data": "false",
"__pid": 31357
}
First trajectory after restarting tcs gui with structure and dome movement boxes checked I received the error above again. Tried to reacquire with no dome or structure movement since telescope/dome already at correct location. With the dome and structure movement unchecked it acquired the trajectory properly. | |
| 4188 | 08:43-08:47 | 00:04 | Got an error when going to the next target sent from the RA. Does east or west have to be chosen correctly when going to object from resident astronomer (I dont recall this ever occuring before tonight)? Error below is below.
{
"__exception_type": 7,
"__exception_string": "Requested azimuth (180.010680) and direction East are incompatible.",
"__exception_file": "point.cpp",
"__exception_line": 43,
"__exception_func": "Point",
"__effective_id": 70,
"__original_id": 42,
"__origin": "tcsGuiTcsAsyncCommandSender.jove.26308.05daa164f->tcp://192.168.66.31:30300",
"__handler": "go_next",
"__async": "true",
"__done": "true",
"__ack": "false",
"__error": "true",
"__data_time": "1445157801.000728014",
"__wire_time": "1445157801.000729615",
"__data": "false",
"__pid": 31357
| |
| 4189 | 11:27-11:27 | 00:00 | While closing the dome up I got an Async error about the shutter. Restarted tcs gui the status still showed UNKNOWN. Moved dome in azimuth a little bit then aborted and the options came back for the dome shutter. I was then able to shut it normally. See error below.
{
"__exception_type": 0,
"__exception_string": "Shutter stopped at wrong position (UNKNOWN)",
"__exception_file": "unknown",
"__exception_line": 0,
"__exception_func": "unknown",
"__effective_id": 71,
"__original_id": 15,
"__origin": "tcsGuiLegacyAsyncCommandSender.jove.26308.03e8cef1a->tcp://192.168.66.31:30800",
"__handler": "dome_CloseShutter",
"__async": "true",
"__done": "true",
"__ack": "false",
"__error": "true",
"__data_time": "1445167991.716923493",
"__wire_time": "1445167991.716924739",
"__data": "false",
"__pid": 31364
} | |