David's Astronomy Pages
Notes - Session 664 (2019-02-17)

   
Bullet Session Aims & Highlights
 - Observing Result
 - Session Event Log
 - Night Summary Plot
 
Bullet Operational Issues
  - Critical Issues (0),  Major Issues (1),  Minor Issues (2),  Continuous Improvement (4)
  
Bullet Investigation - Shutter unexpected closed during initial dome opening
 
Bullet Images from 2019-02-17  >>
 

Session Aims & Highlights (2019-02-17)

Main aims

  1. Exoplanet Project - Finish current set of baseline images of a number of exoplanet host stars
    (this is in advance of a series of renewed attempts to detect and record an exoplanet transit )
  2. Variable Stars Project - Acquire some baseline images of a number of new variable stars
    (this includes some eclipsing binaries and other rapidly varying stars not previously observed)
  3. Variable Star & Nearby Star Monitioring - Ongoing monitoring
  4. Software & Systems  - Check stability of software and presence of any side effects following changes to AstroMain for handling Shutter Opening Issues

Equipment & Software

Highlights

Lowlights

Summary Plots & Logs

Observing Plan (2019-02-17, S664)
Image
 
Observing Result (2019-02-17, S664)
Image
Night Sky Summary Plot - 2019-02-17, S664
Top axis: Sky Brightness at Zenith (in ADU/s)
Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)
Image
  
Session Event Log (2019-02-17, S664)
Time   Event Detail
18:19 Session Created Live Session Created (2019-02-17 S00664, ImageSaveNum: 664001)
18:20 Obs.Manager Started Obs.Manager started
18:20 Services Started Observatory Services started
18:22 Observatory (Auto) Observatory placed in Fully-Automated Mode
18:22 Session Pending Session pending (2019-02-17)
18:22 Session Initiating Session initiating (2019-02-17)
18:22   Plan Requested Observing Plan requested from AstroPlan ()
18:27   Plan Loaded Observing Plan loaded to queue (2019-02-17 V1 BEST PLAN, Plan ID: 278)
18:28   Camera1 Connected SBIG Camera Connected (set point -20°C)
18:28   Telescope Connected Telescope Connected (TheSky6)
18:34   Shutter Opening Shutter opening hasn't finished after 90s
18:35 Shutter Closed Shutter closed (closing time 5s)
18:35 Shutter Closed Shutter closed (closing time 6s)
18:35 Shutter Closed Shutter closed (closing time 5s)
18:35 Shutter Closed Shutter closed (closing time 5s)
18:36 Observatory (Manual) Observatory placed in Manual Mode
18:38 Observatory (Auto) Observatory placed in Fully-Automated Mode
18:38 Session Pending Session pending (2019-02-17)
18:38 Session Initiating Session initiating (2019-02-17)
18:38   Plan Loaded Observing Plan loaded to queue (2019-02-17 V1 BEST PLAN, Plan ID: 278)
18:38   Camera1 Connected SBIG Camera Connected (set point -20°C)
18:38   Telescope Connected Telescope Connected (TheSky6)
18:38 Equilibration Started Dome Equilibration started
18:38 Equilibration Skipped Dome Equilibration skipped by user
18:38 Session Running Session running
18:38   Queue Started Observing Queue started (37 targets selected)
18:39     Target Started (1/37) Target started (1/37, GCVS FO Ori)
18:41   Focusing Started (Foc1) Foc1 Focusing Started (TCF-S)
18:44   Focusing Completed Foc1 AutoFocus Completed (Profile No 1)
18:46     Target Completed Target partially completed (1/37, GCVS FO Ori)
18:46     Target Started (2/37) Target started (2/37, GCVS RR Tau)
18:55     Target Completed Target partially completed (2/37, GCVS RR Tau)
18:55     Target Started (3/37) Target started (3/37, GCVS SS Cyg)
19:04     Target Completed Target completed (3/37, GCVS SS Cyg)
19:04     Target Started (4/37) Target started (4/37, GCVS HH And)
19:11     Target Completed Target completed (4/37, GCVS HH And)
19:12     Target Started (5/37) Target started (5/37, GCVS TV Cas)
19:19     Target Completed Target completed (5/37, GCVS TV Cas)
19:20     Target Started (6/37) Target started (6/37, GSC 1224:29)
19:27     Target Completed Target completed (6/37, GSC 1224:29)
19:29     Target Started (7/37) Target started (7/37, GCVS RX And)
19:36     Target Completed Target completed (7/37, GCVS RX And)
19:37     Target Started (8/37) Target started (8/37, GCVS GK Per)
19:44     Target Completed Target completed (8/37, GCVS GK Per)
19:45     Target Started (9/37) Target started (9/37, GCVS CN Ori)
19:51     Target Completed Target completed (9/37, GCVS CN Ori)
19:53     Target Started (10/37) Target started (10/37, HAT-P-20)
19:55   Focusing Started (Foc1) Foc1 Focusing Started (TCF-S)
20:04     Target Completed Target completed (10/37, HAT-P-20)
20:05     Target Started (11/37) Target started (11/37, Qatar-1)
20:17     Target Completed Target completed (11/37, Qatar-1)
20:19     Target Started (12/37) Target started (12/37, TrES-5)
20:31     Target Completed Target completed (12/37, TrES-5)
20:32     Target Started (13/37) Target started (13/37, GCVS FU Ori)
20:35   Focusing Started (Foc1) Foc1 Focusing Started (TCF-S)
20:39     Target Completed Target completed (13/37, GCVS FU Ori)
20:40     Target Started (14/37) Target started (14/37, GCVS SU Tau)
20:48     Target Completed Target completed (14/37, GCVS SU Tau)
20:49     Target Started (15/37) Target started (15/37, GCVS Z And)
20:57     Target Completed Target completed (15/37, GCVS Z And)
20:57     Target Started (16/37) Target started (16/37, WDS GRB 34)
21:05     Target Completed Target completed (16/37, WDS GRB 34)
21:05     Target Started (17/37) Target started (17/37, GCVS RR Leo)
21:20     Target Completed Target completed (17/37, GCVS RR Leo)
21:20     Target Started (18/37) Target started (18/37, GCVS CN Leo)
21:34     Target Completed Target completed (18/37, GCVS CN Leo)
21:34     Target Started (19/37) Target started (19/37, HAT-P-12)
21:44     Target Completed Target completed (19/37, HAT-P-12)
21:44     Target Started (20/37) Target started (20/37, GCVS ER UMa)
21:50     Target Completed Target completed (20/37, GCVS ER UMa)
21:51     Target Started (21/37) Target started (21/37, LAMOST-HVS1)
21:57     Target Completed Target completed (21/37, LAMOST-HVS1)
22:00     Target Started (22/37) Target started (22/37, CoRoT-1)
22:11     Target Completed Target completed (22/37, CoRoT-1)
22:14     Target Started (23/37) Target started (23/37, GCVS U Mon)
22:24     Target Completed Target completed (23/37, GCVS U Mon)
22:25     Target Started (24/37) Target started (24/37, GCVS NV Ori)
22:33     Target Completed Target completed (24/37, GCVS NV Ori)
22:33     Target Started (25/37) Target started (25/37, WASP-12)
22:42 Observatory (Manual) Observatory placed in Manual Mode
22:42     Target Completed Target completed (25/37, WASP-12)
22:46   Focusing Started (Foc1) Foc1 Focusing Started (TCF-S)
22:50   Focusing Aborted Foc1 Focusing Aborted
22:50   Focusing Started (Foc1) Foc1 Focusing Started (TCF-S)
22:53   Focusing Aborted Foc1 Focusing Aborted
22:55 Shutter Closed Shutter closed (closing time 49s)
22:57 Telescope Parked Telescope parked (parking time 44s)
22:58   Dome Parked Dome parked
22:58 Dome Parked Dome parked (parking time 62s)
22:59   Camera1 Disconnected SBIG Camera closed down & disconnected
22:59 Services Stopped Observatory Services stopped
   

Back to Top


Operational Issues (2019-02-17, S664)

[ Prev | Next ]

Critical Issues

Major Issues

Minor issues

Continuous Improvement

[ Prev | Next ]

Back to Top


Investigation - Shutter unexpected closed during initial dome opening

Following a shutter opening incident in the last session on 2019-02-13 S663 and following investigation into why the Pulsar Dome Controller couldn't detect that shutter had finished opening and allowed the shutter motor for up to 40 mins before it was noticed new code was added to AstroMain to intervene where shutter opening appears anomalous and prevent the motors from running ad-infinitum.

 Whilst the new modify shutter opening routines had been tested this session (S664) was the first live full-system test of the new code.

After entering 'Session Equilibrating' state, the Shutter began opening under command of the Obs.Manager, but within seconds the dome unexpectedly began to close which was noted as an Alert .   After a while the new ('opening') code kicked in with the Error message that the Shutter hadn't finished after 90s   and would have issued a new command to close the shutter.  The shutter (which was already closing)  finished closing 5s later.

Some 5 minutes later dome was opened  using the POTH.Hub panel, but again there was the message dome is unexpectedly closing (even though conditions were good).    Finally the Obs.Manager was set to Auto, and the Observatory visited to check the status of the the Dome and opened via POTH.Hub without further incident.


Session Equilibrating                   2019-02-17 18:28  (Local)
  Plan Start Time             Ok        2019-02-17 18:36  (Local)
  Open Shutter...             Opening   
  Close Shutter...            Closing   
Dome Closure:                 Alert     Dome is unexpectedly closing (Good Conditions), 2019-02-17 18:28
  Shutter Safety              Error     Shutter opening hasn't finished after 90s
  Shutter Safety              Info      There may be a mechannical or electrical issue.
  Shutter Safety              Info      Shutter will be closed.
  Close Shutter...            Ok        Shutter is Closed (5s)
  Close Shutter...            Closing   
Dome Closure:                 Alert     Dome is unexpectedly closing (Good Conditions), 2019-02-17 18:35
  Close Shutter...            Ok        Shutter is Closed (6s)
  Close Shutter...            Ok        Shutter is Closed (5s)
  Close Shutter...            Closing   
Dome Closure:                 Alert     Dome is unexpectedly closing (Good Conditions), 2019-02-17 18:35
  Close Shutter...            Ok        Shutter is Closed (5s)
  Close Shutter...            Closing   
Dome Closure:                 Alert     Dome is unexpectedly closing (Good Conditions), 2019-02-17 18:36

Observatory Mode                        2019-02-17 18:36  (Local)
  Setting Mode ...            Ok        Manual

Back in Jaunary when there were several cases of the dome shutter unexpectedy closing, but it was shown then that the commands to close weren't coming from the Obs. Computer via ASCOM but were glitches in the Cloud-Sensor - Dome Controller relay system.  However this new run of 'unexpected/non-designed' closures are clearly caused by commands sent via ASCOM, as the following trace log abstract shows

18:28:11.741 ShutterStatus 1     << Shutter is closed
18:28:13.452 ShutterStatus 1
18:28:15.621 OpenShutter         << Initial Command recieved to Open Shutter
18:28:15.621 ShutterStatus 2     << Shutter is opening
18:28:15.621 ShutterStatus 2
18:28:18.678 ShutterStatus 2
18:28:20.628 ShutterStatus 2
18:28:20.753 CloseShutter        << Command recieved to Close Shutter
18:28:21.814 ShutterStatus 3     << Shutter is closing
18:28:24.996 ShutterStatus 3
18:28:25.776 ShutterStatus 3
18:28:25.792 OpenShutter         << Command recieved to Open Shutter
18:28:27.913 ShutterStatus 2     << Shutter is opening
18:28:31.143 ShutterStatus 2
18:28:31.158 ShutterStatus 2
18:28:31.720 ShutterStatus 2
18:28:31.876 CloseShutter        << Command recieved to Close Shutter
18:28:32.235 ShutterStatus 3     << Shutter is closing
18:29:25.868 OpenShutter         << Command recieved to Open Shutter
18:29:26.726 ShutterStatus 3
18:29:29.534 ShutterStatus 1     << Shutter is closed
18:29:30.735 ShutterStatus 1

Examining the entire set of Open/Close Shutter Commands it is evident that commands are generally being issued on a 5s or 10s interval that corresponds to the cycle time of the Obs.Manger loop (5s).  On one cycle of the loop there is a command to open the shutter, whilst  on the next round there is a countermanding command to close the shutter.  This points clearly to a bug in the Obs.Manager  with two different control processes interfering with each other.

18:28:15.621 OpenShutter     << Initial Command to Close Shutter at end of session
18:28:20.753 CloseShutter
18:28:25.792 OpenShutter
18:28:31.876 CloseShutter
18:28:35.885 OpenShutter
18:28:40.799 CloseShutter
18:28:45.697 OpenShutter
18:28:50.674 CloseShutter
18:28:56.025 OpenShutter
18:29:00.876 CloseShutter
18:29:05.946 OpenShutter
18:29:10.704 CloseShutter
18:29:15.712 OpenShutter
18:29:20.720 CloseShutter
18:29:25.868 OpenShutter
18:34:53.017 OpenShutter
18:34:56.449 CloseShutter
18:35:01.550 OpenShutter
18:35:06.324 CloseShutter
18:35:11.285 OpenShutter
18:35:16.479 CloseShutter
18:35:22.719 OpenShutter
18:35:26.292 CloseShutter
18:35:31.611 OpenShutter
18:35:36.697 CloseShutter
18:35:41.533 OpenShutter
18:35:46.353 CloseShutter
18:35:51.377 OpenShutter
18:35:57.227 CloseShutter
18:36:01.423 OpenShutter
18:36:02.141 OpenShutter
18:36:06.353 CloseShutter
18:36:09.270 OpenShutter
18:36:25.041 CloseShutter

22:54:56.393 CloseShutter  << Final Command to Close Shutter at end of session

 

Code Review

Review showed

Bug found in 'Monitor Shutter Opening' whereby on the second cycle through the loop a wrongly placed CloseShutter command was caused the shutter to quickly begining closing. (close shutter should have been inside a  'If ShutterSecs > 90 ...  endif block but lay outside it).

This bug explains why the shutter begins to Close.

Code in the 'State is Equilibrating'  commands an Open Shutter if the Shutter is Closed or Closing, DomeCanOpen (ie conditions are safe) and DomeOpening is being monitored.  So this explains why the shutter begins to Open again.

 

But what causes the 'Dome Is Unexpectedly Closing' Alerts if the Shutter is Closing due to calls to CloseShutter routine which sets the MonitorShutterClosure flag to true, which is used by  'Check for Unexpected Closure' code to ignore programmed closure.

It seem that in the OpenShutter routine,  the MonitorShutterClosure flag is set to false.  (as a prelude to commanding the Shutter to Open, and setting MonitorShutterOpening flag to true).

Actions :

 

Back to Top