| Date | Description | Person(s) | Hardware Group | Action performed | Attachment | Edit | Site | Task(?) |
| 2025-04-22 |
Mail from system indicating problem with QHY detector |
Frank |
Spectrograph Detector |
stopped detector daemon, power-cycled the QHY, started qhy-daemon and set temperature to -5 - seem to be running again. |
None |
Edit |
MtKent |
|
| 2025-04-17 |
No update of preview images, and no new data on disk, even though we followed alpha Cen A nicely |
Frank |
Spectrograph Detector |
Logged in to detector HP-PC. Stopped the camera-server. Power-cycled the camera from hw as obs (pdu_control spec-room 20 2/1) - Restarted camera server. Remember to set the cooler temperature !! Observations now seem to be going on. It seems we had the same problem yesterday (20250416) so no spectra here. |
None |
Edit |
MtKent |
|
| 2025-04-14 |
Clar wether for a number of hours... but no data obtained although we were tracking. probably a software issue with data storage. |
Hans Kjeldsen |
IT, software, computers |
Nothing.. |
None |
Edit |
MtKent |
246 |
| 2025-04-08 |
Adjust the Fabry-Perot illumination of the science fibers |
Frank |
Spectrograph |
Duncan helped to correct the misalignment of the FabryPerot light source, such that calibrations now work again for FP. The exposure time should be 2s. |
None |
Edit |
MtKent |
|
| 2025-03-17 |
No connection to anything in the FUT dome! Likely because of no power so perhaps breaker switch needs a turn again?! Please investigate. |
Karsten |
|
|
None |
Edit |
MtKent |
242 |
| 2025-03-03 |
Spectre did not contain data |
Mads |
Detector |
Noticed that the preview images did not get updated and found out that the QHY detector did not work as it should and did not readout data. After a power cycle and restart of software it seems to have recovered. |
None |
Edit |
MtKent |
|
| 2025-02-23 |
No connection to anything in the FUT dome (again). Breaker switch or something else? You can wait until daytime to fix. |
Karsten |
|
|
None |
Edit |
MtKent |
243 |
| 2025-01-27 |
Weather data has not updated since yesterday |
Karsten |
|
|
None |
Edit |
MtKent |
240 |
| 2024-11-21 |
Weather data not updated since about 00:10 local Mount Kent time (15:10 DK time) |
Karsten |
|
|
None |
Edit |
MtKent |
236 |
| 2024-11-12 |
No connection to T1 guide camera |
Mads |
T1 fibre guider |
The camera is not seen from the controlling computer in the spectrogragh room. The PC was rebooted which did not help. Maybe the USB cable has come loose somewhere? |
None |
Edit |
MtKent |
234 |
| 2024-11-12 |
Connection to the T1 Monitor was lost around 23 local time. Got an error message about "T1 monitor deamon is hanging somewhere". Activated shutdown. |
Jonatan Rudrasingam |
T1 monitor |
Activated shutdown. Added to task |
None |
Edit |
MtKent |
235 |
| 2024-10-30 |
There appears to be a problem with observation of beta Hyi where star seems to be defocused (see attached image). The overview plot of the observation also lacks flux. |
Jonatan Rudrasingam |
Telescope |
Added it to the task. Contacted Frank and Mads |
Show |
Edit |
MtKent |
232 |
| 2024-10-30 |
There appears to be a problem with observation of beta Hyi where star seems to be defocused (see attached image). The overview plot of the observation also lacks flux. |
Jonatan Rudrasingam |
Telescope |
Added it to the task. Contacted Frank and Mads |
Show |
Edit |
MtKent |
233 |
| 2024-10-23 |
T1 monitor crashed. This happen after an observed star came under the telescope altitude limit (low object). This appear to be the same problem which happen on 18th October. Update: Connection to the T1 monitor is established, but the connection to the Scheduler is lost (according to the SODA webpage) Update 2: Connection to Scheduler is reestablsihed. |
Jonatan Rudrasingam |
Telescope |
Shutdown initiated until problem can be solved. Added it to the task |
None |
Edit |
MtKent |
231 |
| 2024-10-18 |
Connection to the T1 Monitor was lost around 5:00 local time. Encoder set is no. Overall obs state is 174. Global state is 0. Woke up (around 45 minutes later) and noticed this. Took the watchman shift and activated shutdown. |
Jonatan Rudrasingam |
Telescope |
Shutdown initiated until problem can be solved. Added it to the task |
None |
Edit |
MtKent |
229 |
| 2024-10-11 |
This morning before observation a T1 monitor daemon is hanging warning occured. Shortly afterwards a homing warning occured. Looking at obs page AZ motors are not enabled, Encoders set is no, Ready state is not ready. Overall obs state is 64. Motion state is on homing. I don't know if it is a software problem or a hardware problem. Update: when writing this logbook and after activating shutdown the software on T1 Monitor and the Scheduler is not up to date on the soda webpage. |
Jonatan Rudrasingam |
Telescope |
Shutdown initiated until problem can be solved. Tasked the problem to Jack Soutter |
Show |
Edit |
MtKent |
228 |
| 2024-10-11 |
This morning before observation a T1 monitor daemon is hanging warning occured. Shortly afterwards a homing warning occured. Looking at obs page AZ motors are not enabled, Encoders set is no, Ready state is not ready. Overall obs state is 64. Motion state is on homing. I don't know if it is a software problem or a hardware problem. Update: when writing this logbook and after activating shutdown the software on T1 Monitor and the Scheduler is not up to date on the soda webpage. |
Jonatan Rudrasingam |
Telescope |
Shutdown initiated until problem can be solved. Tasked the problem to Jack Soutter |
None |
Edit |
MtKent |
225 |
| 2024-10-11 |
This morning before observation a T1 monitor daemon is hanging warning occured. Shortly afterwards a homing warning occured. Looking at obs page AZ motors are not enabled, Encoders set is no, Ready state is not ready. Overall obs state is 64. Motion state is on homing. I don't know if it is a software problem or a hardware problem. Update: when writing this logbook and after activating shutdown the software on T1 Monitor and the Scheduler is not up to date on the soda webpage. |
Jonatan Rudrasingam |
Telescope |
Shutdown initiated until problem can be solved. Tasked the problem to Jack Soutter |
Show |
Edit |
MtKent |
227 |
| 2024-10-11 |
This morning before observation a T1 monitor daemon is hanging warning occured. Shortly afterwards a homing warning occured. Looking at obs page AZ motors are not enabled, Encoders set is no, Ready state is not ready. Overall obs state is 64. Motion state is on homing. I don't know if it is a software problem or a hardware problem. Update: when writing this logbook and after activating shutdown the software on T1 Monitor and the Scheduler is not up to date on the soda webpage. |
Jonatan Rudrasingam |
Telescope |
Shutdown initiated until problem can be solved. Tasked the problem to Jack Soutter |
Show |
Edit |
MtKent |
226 |
| 2024-10-01 |
Regular electrical power check |
Mads |
All |
Powered off critical systems yesterday and restarted things today (2024-10-02) |
None |
Edit |
MtKent |
|
| 2024-09-25 |
Connection to telescope( Tel-com?) is lost around 12:30 UTC/22:30 local time. Last data was taken around the time. No further data were taken or shown in the obs page. On the SODA webpage the status on the Telescope Power and Telescope Motion are shown as "Error" |
Jonatan Rudrasingam |
Telescope |
Shutdown initiated until problem can be solved. Contacted Mads and Frank via. email. |
None |
Edit |
MtKent |
|
| 2024-09-07 |
Iodine cell not heated for about two hours from 16:10 to 18 UTC |
Mads |
Iodine cell |
Heater was re-enabled and started heating again |
None |
Edit |
MtKent |
|
| 2024-08-22 |
Observation of beta Aql was stopped due to bad weather (clouds). Dome closed but a T1 shutdown error message occurred even through the dome closed properly. |
Jonatan Rudrasingam |
Dome |
|
None |
Edit |
MtKent |
|
| 2024-07-29 |
No connection to SONG Tel-Com 1. The telescope control computer is not reachable on the network |
Mads |
Tel-com |
Tried to power cycled the computer which did not help. On site assistance is needed to investigate the issue. |
None |
Edit |
MtKent |
222 |
| 2024-07-23 |
No connection to FUT CMOS detector. I get the error "Could not connect to the camera." for any attempted operation with the camera. Have tried to turn off, wait, and the on again without any effect. Could you try to de- and re-attach the usb connectors and test the usb connection? Let me know when if you need me at the other end for troubleshooting. Thanks |
Karsten |
FUT CMOS detector |
|
None |
Edit |
MtKent |
221 |
| 2024-07-10 |
I observed two things as watcher... 1. the telescope did not observe any targets for a period of time near the end of the night, although dome was open and weather was OK. 2. 15 minutes later I lost contact to the webpage and could not even see the Watchman-site and in case of emergency therefore no close the telescope (or call.. since info. on actions is on the webside). The webside was active again 15 minutes later and nothing went wrong and I did not needed to perform any actions. |
Hans Kjeldsen, AU |
Telescope |
nothing - I informed Frank and Mads via SMS |
None |
Edit |
MtKent |
220 |
| 2024-01-15 |
Weather data is not being updated (for days now) |
Karsten |
All |
|
None |
Edit |
MtKent |
239 |
