After coming home for dinner, no one on watch, so took it. Monitor was not running, so started it .... after ~10min things started, but monitor stopped itself, tried to restart, but it stopped again. The 'client_abort_acq' did not work, so stopped or_scheduler. Then tried to close the hatch and dome ... the hatch closed, but when the upper hatch closed I could see the lower hatch was not closed properly, despite Astelos reporting it closed ... so opened the uper/lower hatces agin... then the telescope slewed to a new objece (despite the monitor was not running!): ... then I closed the lower and uppper hatch, parked the telescope ... during which the 'both-limits-active' ocurred.. and then the telescope powered off.... Not sure what all the reasons for this are, but guessing perhaps the new(?) monitor.
Old comments:
2024-04-19 07:58: [Mads]: Two monitors were started, since the new one was running fine on the new virtual machine (192.168.66.193). The old monitor was started causing confusion. Many commands to the telescope might have triggered even more issues like the both limit switch active issue. This was solved by rebooting the server system (Astelco's).
2024-04-18 23:24: [Frank Grundahl]: see description above.
