David's Astronomy Pages Notes - Session 764 (2020-03-27)

Notes (S763)

Notes Main

Home Page

Notes (S765)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (1),  Minor Issues (6),  Continuous Improvement (0)
	Images from 2020-03-27 >>
	PHD2 Version 2.6.7
	Investigation: Dome Closing Issue
	Investigation: Telescope Parking Issue

Session Aims & Highlights (2020-03-27)

Main aims

1. Targets: Acquire images of a number of comets and deep sky objects
   

Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, PHD2,  POTH Hub
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.6dev3
   
• AstroMain 3.20.3 ,  Astroguard 1.2.11,   AstroPlan 1.14,  AstroShCap 1.2.15, AstroVOE 1.3.5, UPB 1.4.17  (AstroWeather 1.8.6, AstroAllSky 3.5.1)
  

Highlights

• Good Conditions.  Good seeing / good condition enabled productive session with good guiding
• Targets.  x targets successfully imaged

Lowlights

•   Sky transparency. Sky transparency poor for some targets due to haze along horizons

Summary Plots & Logs

Observing Plan

Observing Result

Dome & Scope Slewing Performance

Slew/Centering Performance

Guiding Performance

Sky Conditions (Locate Frames)

Night Sky Summary Plot Top axis: Sky Brightness at Zenith (in ADU/s) Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)

Pre-Session Weather Forecast (API data from darksky.net) Forecast not saved/archived due to technical issue. In the event skies were ...

Session Event Log

Time     Event Detail 19:53:31 Session Created Live Session Created (2020-03-27 S00764, ImageSaveNum: 764001) 19:54:54   Scope Switched On Telescope power has been switched on via UPB Powerbox. 19:59:03   Services Started Observatory Services started 19:59:21   Camera1 Connected SBIG Camera Connected (set point -20°C) 19:59:25   Telescope Connected Telescope Connected (TheSky6) 20:01:02   Shutter Opened Shutter opened (opening time 45s) 20:02:10       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:03:38       Focusing Aborted Foc1 Focusing Aborted 20:05:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:06:19       Focusing Aborted Foc1 Focusing Aborted 20:07:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:11:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 20:14:22       Focusing Started Foc2 Focusing Started (Secondary Scope, using ShCap) 20:14:54       Focusing Started Foc2 Focusing Started (Secondary Scope, using ShCap) 20:16:52       Focusing Completed Foc2 AutoFocus Completed (Profile No 4) 20:17:31 Observatory (Auto) Observatory placed in Fully-Automated Mode 20:17:34 Session Pending Session pending (2020-03-27) 20:17:36 Session Initiating Session initiating (2020-03-27) 20:17:38   Plan Requested Observing Plan requested from AstroPlan (1.14) 20:18:40   Plan Loaded Observing Plan loaded to queue (2020-03-27 V1 BEST PLAN, Plan ID: 488) 20:18:43   Camera1 Connected SBIG Camera Connected (set point -20°C) 20:18:52   Telescope Connected Telescope Connected (TheSky6) 20:19:04 Session Equilibration Session ready for dome & camera equilibration 20:19:07   Equilibration Started Dome Equilibration started 20:19:09   Equilibration Skipped Dome Equilibration skipped by user 20:19:11 Session Running Session running 20:19:13   Queue Started Observing Queue started (37 targets selected) 20:23:34     Target Started (1/37) Target started (1/37, GCVS RR Tau) 20:28:08       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:30:57       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 20:37:05     Target Completed Target completed (1/37, GCVS RR Tau) 20:37:07     Target Started (2/37) Target started (2/37, C/2020 A2 (Iwamoto)) 20:39:17       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:42:08       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 20:50:17     Target Completed Target completed (2/37, C/2020 A2 (Iwamoto)) 20:50:19     Target Started (3/37) Target started (3/37, Scholz's Star) 20:52:51     Target Aborted (3/37) Target aborted (3/37, Scholz's Star) due to GRB Alert 20:52:53     Target Started (4/38) Target started (4/38, C/2019 Y1 (ATLAS)) 20:54:19 Critical Conditions Alert Critical Conditions Alert (Obs.Manager will close the Shutter) 20:54:21   HardSuspend Called Hard Suspend is called due to Critical Conditions (other condition) 20:54:40     Target Aborted (4/38) Target aborted (4/38, C/2019 Y1 (ATLAS)) due to other condition 20:54:42   Queue Paused Queue pausing for HardSuspend 20:54:45 Session Suspended Session suspended 20:55:34   Shutter Closed Shutter closed (closing time 49s) 20:56:49 Session Resuming Session resuming 20:57:34   Shutter Opened Shutter opened (opening time 45s) 20:57:36 Session Running Session running 20:57:38   Queue Resumed Observing Queue resumed 20:57:40     Target Started (4/38) Target started (4/38, C/2019 Y1 (ATLAS)) 21:02:26     Target Aborted (4/38) Target aborted (4/38, C/2019 Y1 (ATLAS)) due to GRB Alert 21:02:40     Target Aborted (5/38) Target aborted (5/38, GCVS U Mon) due to Priority 1 ToO Target 21:02:42     Target Started (6/39) Target started (6/39, C/2019 Y1 (ATLAS)) 21:15:10     Target Completed Target completed (6/39, C/2019 Y1 (ATLAS)) 21:21:13     Target Started (7/39) Target started (7/39, GCVS SY Cnc) 21:23:58       Focusing Failed Foc1 Focusing Failed - unable to find a star (TCF-S) 21:28:43     Target Completed Target completed (7/39, GCVS SY Cnc) 21:30:52     Target Started (8/39) Target started (8/39, GCVS AM CVn) 21:34:20       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:38:01       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 21:40:46     Target Completed Target completed (8/39, GCVS AM CVn) 21:40:48     Target Started (9/39) Target started (9/39, LAMOST-HVS1) 21:44:59       Focusing Failed Foc1 Focusing Failed - unable to find a star (TCF-S) 21:50:02     Target Completed Target completed (9/39, LAMOST-HVS1) 21:50:11     Target Started (10/39) Target started (10/39, GCVS DX Cnc) 21:51:47       Focusing Failed Foc1 Focusing Failed - star is too dim (TCF-S) 21:57:58     Target Completed Target completed (10/39, GCVS DX Cnc) 21:58:00     Target Started (11/40) Target started (11/40, NGC 2674) 22:02:53     Target Aborted (11/40) Target aborted (11/40, NGC 2674) due to GRB Alert 22:02:55     Target Started (12/41) Target started (12/41, NGC 5157) 22:24:15     Target Completed Target completed (12/41, NGC 5157) 22:24:17     Target Started (13/42) Target started (13/42, 88P/Howell) 22:26:43     Target Aborted (13/42) Target aborted (13/42, 88P/Howell) due to GRB Alert 22:26:45     Target Missed (14/42) Target's time slot was missed (14/42, GCVS ER UMa) 22:26:47     Target Started (15/42) Target started (15/42, GCVS CM Tau) 22:27:40     Target Aborted (15/42) Target aborted (15/42, GCVS CM Tau) due to Priority 1 ToO Target 22:27:42     Target Started (16/43) Target started (16/43, M49) 22:30:46       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:34:13       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 22:52:53     Target Completed Target completed (16/43, M49) 22:52:55     Target Started (17/44) Target started (17/44, Ross 128) 22:55:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:58:35       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 23:04:07     Target Completed Target completed (17/44, Ross 128) 23:04:09     Target Missed (18/44) Target's time slot was missed (18/44, GCVS U Gem) 23:04:11     Target Missed (19/44) Target's time slot was missed (19/44, GCVS RZ LMi) 23:04:13     Target Missed (20/44) Target's time slot was missed (20/44, GCVS AM Her) 23:04:15     Target Started (21/44) Target started (21/44, NGC 4700) 23:06:48       Focusing Failed Foc1 Focusing Failed - star is too dim (TCF-S) 23:24:23     Target Completed Target completed (21/44, NGC 4700) 23:24:25     Target Started (22/45) Target started (22/45, IC 1222) 23:46:18     Target Completed Target completed (22/45, IC 1222) 23:46:20     Target Started (23/46) Target started (23/46, M100) 00:07:34     Target Completed Target completed (23/46, M100) 00:07:36     Target Missed (24/46) Target's time slot was missed (24/46, GCVS S Cyg) 00:07:38     Target Missed (25/46) Target's time slot was missed (25/46, GCVS GK Per) 00:07:40     Target Missed (26/46) Target's time slot was missed (26/46, 155P/Shoemaker) 00:07:42     Target Started (27/46) Target started (27/46, GCVS U Her) 00:10:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:13:52       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 00:18:08 User Intervention User request to close and finish session 00:18:11     Target Completed Target partially completed (27/46, GCVS U Her) 00:18:13   Queue Aborted Job Queue aborted 00:18:15 Session Closing Session closing 00:27:24   Dome Parked Dome parked (parking time 31s) 00:27:29   Dome Parked Dome parked 00:32:13   Scope Switched Off Telescope Power has been switched off via UPB Powerbox. 00:33:02   Services Stopped Observatory Services stopped 00:33:10 Program Closed Program closed by User

Back to Top

Operational Issues (2020-03-27, S764)

• Critical Issues (0)
• Major Issues (1)
• Minor Issues (6)
• Continuous Improvement (0)

[ Prev | Next ]

Critical Issues

•  None

Major Issues

• Dome Closure Issue.   Dome closure wasn't recorded. ObsManager waiting for 6-7 minutes and then moved onto to Park Dome. An investigation was made (See Investigation: Dome Closing Issue) but was unable to find a clear cause. It is supposed that there was an initial problem with the dome sensor or a glitch in the Shutter Unit.   Issue was investigated (see Investigation: Dome Closing Issue).    Recommendation is to close the issue (2020) and record the issue as unexplained glitch.  Should the issue be related to the other Dome issue where the shutter system sometimes falls asleep and stops giving fresh information then it is possible the issue will have been fixed by installation of Pulsar Shutter Software Version 1.25 on 2021-03-31).  Issue confirmed to have been fixed.
  Fix 2021-03-31 (Pulsar Dome)

Minor Issues

• Foc1 best focus position was very different to that expected.  1st focusing attempt began with the focuser at 2067 (T=3.5°C). This is consistent with settings from the previous session (S763, 8 days beforehand) where the final focus profile measurements had set the best focus position at 2512 (T= 0.2°C) with focus offset of -870 (average focus offset for session S763 had been -717).  Profile 1 and 2 were aborted as it was evident that best focus position was much higher than expected value (ie 3500+ rather than 2067). Profile 3 measurements set the best focus position at 3760 (T= 4.0°C, focus offset 891)   This equates with a 1760 jump in expected focus position.   (average focus offset of 817 in S764  compares with average offset of -717 in S763, ie average 1534 jump in expected focus). There had been no known change in main LX200 mirror position and change can only be explained in terms of a significant atmospheric change between the two sessions.   (Update: There was a similar large change in focus offset between sessions S774 and S775. A Continuous Improvement ticket has been raised to allow a more flexible aproach to Autofocusing)
  Closed.  User to be aware of possible large jumps in focus position between sessions due to different atmospheric conditions  (Session)
   
• Issues autoguiding C/2019 Y1 (Atlas) even though skies were clear. Was this because of sky position (Alt 18deg, NW or NWN sky) or because prior target was the same. Unable to determine what caused the issue on this occasion.  Since this session Guide Reference pictures are saved which can now better aid diagnosis.
   Closed 2021-02-09 (AstroMain/Session)
   
• C/2019 Y1 (Atlas) actual position lay some 7 arc min away from forecast position which meant the comet wasn't placed centerally on images.
  Resolved using N/W offset (AstroDatabase)
   
• Two or three autoguiding runs failed , with quite a lot of lost star events. Frame 1 ok, but star lost for Frames 2+, Examining data suggests that problem was caused by cloud, low star S/N
  Closed (Session)
    
• Unexpected Session Suspension at 20:55 . Session suspended and shutter closed at 20:55 even though sky was clear and conditions good.   Session resumed after a few minutes.  Long standing issue. (Update: New information indicates a data/sensor glith where the sensor unit temperature suddently reads 0.0 which knocks back the clarity reading by 15 units or so)
  Part Fixed  2020-05-05 (AstroMain 3.21.6)
   
• Telescope Parking Issue.   Parking process failed for some unknown reason,   Report File shows 'Process Aborted', but there are no messages relating to Scope parking in the log file.  Scope was switched off after 30s as per design.   Investigation made (See Investigation: Telescope Parking Issue) but was unable to find a clear cause.   As there was a prior problem with Dome Closure & Parking there may have been a general problem or glitch. Recommendation is to close the issue
  Closed following investigation (Observatory / AstroMain)

Continuous Improvement

•  None

[ Prev | Next ]

Back to Top

PHD2 Version 2.6.7

New version of PHD2 (2.6.7) was installed on the observatory computer.

Back to Top

Investigation: Dome Closing Issue

Issue: Dome Closing Issue.  
Dome Closure at end of session took an unexplainably long time. 

The issue was only discovered whilst investigating another observatory shutdown issue concerning Telescope Parking (see Investigation : Telescope Parking Issue)

AstroMain Report Logs

Logs showing the Shutter starting to close, but fail to show a message saying that closure has been achieved. Instead there is a delay of show 7 minutes until Dome Parking is begun.  It is odd that there are two Park Dome section - was there user intervention to separately park the dome at same time as Obs.Manager was still in Closing state ?

Session Events

AstroMain ObsPics 
Obs Pics show the Dome Open and Pointing to Az 108 at 00:18:08 with session running ( taking pictures of Target 27/46, GCVS U Her) prior to user intervention to abort and finish the session, using xxxx option. At 00:18:41 the session is shutting down (closing) and dome is closing according to Flag Text and Cross-Section but shows as 'Dome Closed' on Plan-View. The dome seems to stay in this ambiguous state until the final ObsPic at 00:32:45. At 00:27:10 the dome has become unslaved and has started rotating to its Park position. At 00:27:41 the Dome is shown to be Parked, but at 00:28:32, the dome is shown as Unparked and at Az 092 where it remains until final ObsPic at 00:32:45

AstroGuard
AstroGuard shows Dome Closing at 00:18 and records that the Shutter has taken an unexpectedly long time to close (>67s)

  Dome Safety                  Info      2020-03-27 20:54 (Local)
  Dome Safety                  Info      Dome is closing
  Dome Safety                  Ok        Shutter has closed (42s)

  Dome Safety                  Ok        2020-03-27 20:56 (Local)
  Dome Safety                  Ok        Shutter Can Open
  Dome Safety                  Ok        Shutter is opening
  Dome Safety                  Ok        Shutter has opened (41s)

  Dome Safety                  Info      2020-03-28 00:18 (Local)
  Dome Safety                  Info      Dome is closing
  Dome Safety                  Warning   Shutter taken >62s to close
  Dome Safety                  Warning   Shutter taken >67s to close

Ascom Trace Logs
ASCOM Trace Log for Dome shows

Conclusion
Commands to close Shutter doesn't appear to have completed for some unknown reason.  Dome was believed to have been Closed when viewed the following day.  Was there a sensor problem or glitch in the Shutter unit, so that it reported an incorrect state ?

It is unclear why there seems to have been two park operations going on and why there was a request to slew dome  to 100° or later on why the dome moved to 92°. It is presumed that user applied a second Park operation (via AstroMain) and applied a azimuth movement via POTH Hub to 100° or later via Dome Control Unit to Az 92°

It is proposed that the issue is closed and put down to a undiagnosed glitch.

Update 2021-03-21

Should the issue be related to the other dome issue where the shutter system sometimes falls asleep and stops giving fresh information then it is possible the issue will have been fixed by installation of Pulsar Shutter Software Version 1.25 on 2021-03-31.

Back to Top

Investigation: Telescope Parking Issue

Issue: Telescope Parking Issue.  
Parking process failed for some unknown reason,   Report File shows 'Process Aborted', but there are no messages relating to Scope parking in the log file.  Scope was switched off after 30s as per design.
 
Whilst investigating this problem, a further shutdown issue concerning Dome Closure was also found (see Investigation : Dome Closing Issue)

AstroMain Report Logs

Logs show Obs.Manager being apparently frozen at 00:28:30 but is seems to be operating at ~ 00:29 when Park Telescope begins

AstroMain ObsPics
Obs Pic at 00:18:08 show the Dome Open and Telescope tracking at Az 107° / Alt 32°  with the session running (taking pictures of Target 27/46, GCVS U Her) prior to user intervention to abort and finish the session, using xxxx option. After closing and parking the dome (with somewhat ambiguous dome state information) , the Telescope is tracking at to Az 109° / Alt 34° at 00:29:04  with Dome having unparked and moved to Az 092°.   At 00:29:38 the scope is slewing towards its near park position (Az 180° / Alt 5°) which it reaches by 00:30:09 where it remains to around 00:31 .  At 00:31:11 the scope has unexplainably begun to move position and sits at Az 175° / 13°) at 00:31:43.
At 00:32:15 the Scope is shown parked (Az 180° / Alt 0°) with its power switched off.

Session Events

AstroGuard
AstroGuard doesn't show anything regarding Telescope

Conclusion
Its uncertain precisely what has happened during Telescope Parking operation. The data is rather ambiguous, and it is uncertain whether there was a more general problem that also saw problems with Dome Closure and Parking.  The scope is believed to have parked ok

It is proposed that the issue is closed and put down to a undiagnosed glitch.

Back to Top