This weekend we had a weird case in which the telescope didn't move for part of the night, but moved fine before and the following morning. Initialising the telescope systems, setting the Zenith position, and updating telescope coordinates, followed by trying to move the telescope results in the telescope server hanging (Bifrost can be closed but there's a TelescopeServer process that cannot be killed) and needing to restart Heimdall.
One clue of what may be happening is that when one sets the Zenith coordinates the RA should be the same as the LST. But when the problem was happening the LST would be for 4:00, 4:30, ... but the RA was always set to exactly 02:00:34. This morning, when the telescope started working again, the RA and LST matched again. There must be a bug in the TelescopeServer that is setting the RA incorrectly for certain ranges of LSTs.
This weekend we had a weird case in which the telescope didn't move for part of the night, but moved fine before and the following morning. Initialising the telescope systems, setting the Zenith position, and updating telescope coordinates, followed by trying to move the telescope results in the telescope server hanging (Bifrost can be closed but there's a
TelescopeServer
process that cannot be killed) and needing to restart Heimdall.One clue of what may be happening is that when one sets the Zenith coordinates the RA should be the same as the LST. But when the problem was happening the LST would be for 4:00, 4:30, ... but the RA was always set to exactly 02:00:34. This morning, when the telescope started working again, the RA and LST matched again. There must be a bug in the
TelescopeServer
that is setting the RA incorrectly for certain ranges of LSTs.