David's Astronomy Pages Notes - Session 797 (2020-08-08)

Notes (S796)

Notes Main

Home Page

Notes (S798)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (2),  Minor Issues (9),  Continuous Improvement (8)
	AutoStart Results (2020-08-08)
	Images from 2020-08-08 >>
	2020-08-09
	AutoStart Results (2020-08-09)
	2020-08-11
	Observatory Alarm System (AstroAlarm)
	2020-08-17
	Virtual Weather Station - Database Glitch
	2020-08-18
	AllSky Computer Problems (BSOD & Failed Windows Startup)
	AllSky Computer,  Potential Replacement

Session Aims & Highlights (2020-08-08)

Main aims

1. AutoStart. Conduct second live test of AutoStart (new observatory mode)
2. Focusing with Wide Search. Conduct live test of autofocusing of Foc2 (Secondary Scope) systems using a precursive widened search range (test failed in previous session)
3. Targets. Acquire images of a number of targets if conditions allow.

Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, PHD2,  DeviceHub 4.6.1.10, UPB 1.5 
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.9
   
• AstroMain 3.27.1,  AstroGuard 1.4.2,   AstroPlan 1.15.4,  AstroShCap 1.2.23, AstroVOE 1.3.6
  (AstroWeather 1.10.9, AstroAllSky 3.6)
  

Highlights

• AutoStart. Second live test of AutoStart was conducted, which uncovered some residual issues and some new ones. Fixing these will strengthen the code ready for subsequent testing in forthcoming sessions
•  Focusing with Wide Search.   Foc2 test of wide search option worked in principle. Wide Search found approximate best focus that was used for the narrower focus profiling.   A potential issue with backlash was found which will require use of a larger backlash amount and further testing.

Lowlights

• AutoStart Fixes. Some issues believed fixed in AstroMain 3.27.1 were found out to be not entirely fixed and require more work.
• SBIG Camera/CCDSoft Issues. Time lost when SBIG Driver failed to find camera and then later when CCDSoft Camera Name/Filter Wheel settings became unexplainably changed.

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) Pre-Session Weather forecast showed semi-clear conditions (33-37% cloud cover) becoming cloudy by dawn (82-96%) with very light wind (3-5 mph), no rain and a minimum temperature of 12°C. In the event conditions were clear in early part of night (up to 40 AllSky Stars) before a cloudy interval at 00:45 and 01:30 after which sky was semi-clouded until 03:30 when sky clouded over.  Entire night was dry and calm.

Session Event Log

Time     Event Detail 17:48:00 Session Monitoring AutoStart monitoring for Live Session opportunity starting between 22:19 & 02:55 17:48:02   AutoStart Waiting AutoStart waiting till earliest start time at 22:19 22:19:00   AutoStart Delayed AutoStart delayed due to light conditions (sun alt) 22:21:00 User Intervention User intervention to workaround bug (sun alt) 22:21:02 Session Monitoring AutoStart monitoring for Live Session opportunity starting between 22:21 & 02:55 22:21:04 Session AutoStarting Session autostarting (22:21) 22:21:57 Session Created Live Session Created (2020-08-08 S00797, ImageSaveNum: 797001) 22:22:15   Services Started Observatory Services started 22:23:00 User Intervention User intervention to workaround bug (scope power on) 22:23:14 Observatory (Manual) Observatory placed in Manual Mode 22:23:48   Services Stopped Observatory Services stopped 22:25:07   Obs.Manager Started Obs.Manager started 22:25:09   Obs.Overseer Started Obs.Overseer started 22:25:13   Services Started Observatory Services started 22:25:38   Scope Switched On Telescope power has been switched on via UPB Powerbox. 22:28:00 Session Monitoring AutoStart monitoring for Live Session opportunity starting between 22:28 & 02:55 22:28:02 Session AutoStarting Session autostarting (22:28) 22:28:35 Observatory (AutoStart) Observatory placed in Auto-Start Mode 22:29:48   Services Started Observatory Services started 22:29:56 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:30:00 Session Pending Session pending (2020-08-08) 22:30:02 Session Initiating Session initiating (2020-08-08) 22:30:04   Plan Requested Observing Plan requested from AstroPlan (1.15.4) 22:31:24   Plan Loaded Observing Plan loaded to queue (2020-08-08 V1 BEST PLAN, Plan ID: 530) 22:31:32   Telescope Connected Telescope Connected (TheSky6) 22:31:45 Session Equilibration Session ready for dome & camera equilibration 22:32:30   Dome Opened Dome opened (opening time 45s) 22:32:33   Equilibration Started Dome Equilibration started 22:36:00 User Intervention User intervention to workaround SBIG camera connection issue 22:36:22   Equilibration Ended Dome Equilibration ended (3.9 mins total) 22:36:24 Observatory (Manual) Observatory placed in Manual Mode 22:38:49   Telescope Parked Telescope parked (parking time 30s) 22:39:19   Telescope Switched Off Telescope Power has been switched off via UPB Powerbox. 22:41:51   Services Stopped Observatory Services stopped 22:42:02   Obs.Manager Started Obs.Manager started 22:42:04   Obs.Overseer Started Obs.Overseer started 22:42:08   Services Started Observatory Services started 22:42:17   Services Stopped Observatory Services stopped 22:42:31 Program Closed Program closed by User 23:06:00 Session Monitoring AutoStart monitoring for Live Session opportunity starting between 23:06 & 02:55 23:06:02 Session AutoStarting Session autostarting (23:06) 23:06:31 Session Resumed Live Session Resumed (2020-08-08 S00797, ImageSaveNum: 797001) 23:07:05   Services Started Observatory Services started 23:07:13 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:07:17 Session Pending Session pending (2020-08-08) 23:07:19 Session Initiating Session initiating (2020-08-08) 23:07:21   Plan Requested Observing Plan requested from AstroPlan (1.15.4) 23:08:22   Plan Loaded Observing Plan loaded to queue (2020-08-08 V1 BEST PLAN, Plan ID: 530) 23:08:30   Telescope Connected Telescope Connected (TheSky6) 23:08:42 Session Equilibration Session ready for dome & camera equilibration 23:09:11   Camera1 Connected SBIG Camera Connected (set point -10°C) 23:09:27   Dome Opened Dome opened (opening time 45s) 23:09:30   Equilibration Started Dome Equilibration started 23:10:08   Equilibration Skipped Dome Equilibration skipped by user 23:10:10 Session Running Session running 23:10:12   Queue Started Observing Queue started (23 targets selected) 23:10:45       Focusing Failed Foc1 Focusing Failed - star is lost (TCF-S) 23:10:48       Focusing Started Foc2 Focusing Started (Secondary Scope, using ShCap) 23:13:27       Focusing Completed Foc2 AutoFocus Completed (Profile No 1, wide) 23:15:22       Focusing Completed Foc2 AutoFocus Completed (Profile No 1) 23:15:25     Target Started (1/23) Target started (1/23, NGC 6741) 23:18:02       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:21:18       Focusing Completed Foc1 AutoFocus Completed (Profile No 2) 23:31:15     Target Completed Target completed (1/23, NGC 6741) 23:31:17     Target Started (2/23) Target started (2/23, Berkeley 91) 23:33:32       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:36:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 23:42:34     Target Completed Target completed (2/23, Berkeley 91) 23:42:37     Target Started (3/23) Target started (3/23, GCVS U Her) 23:45:43       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:48:39       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 23:56:06     Target Completed Target completed (3/23, GCVS U Her) 23:56:09     Target Started (4/23) Target started (4/23, GCVS AM Her) 23:58:17       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:01:08       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 00:06:05     Target Completed Target completed (4/23, GCVS AM Her) 00:06:07     Target Started (5/23) Target started (5/23, GCVS S Cyg) 00:21:53     Target Completed Target partially completed (5/23, GCVS S Cyg) 00:21:55     Target Started (6/23) Target started (6/23, GCVS FG Sge) 00:24:21       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:27:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 00:29:38     Target Completed Target completed (6/23, GCVS FG Sge) 00:29:40     Target Started (7/23) Target started (7/23, 61 Cyg) 00:31:28       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:34:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 00:36:03     Target Completed Target completed (7/23, 61 Cyg) 00:36:05     Target Started (8/23) Target started (8/23, GCVS SS Cyg) 00:38:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:41:28       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 00:42:51 Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Shutter) 00:42:53   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 00:42:54     Target Aborted (8/23) Target aborted (8/23, GCVS SS Cyg) due to cloud 00:42:57   Queue Paused Queue pausing for HardSuspend 00:42:59 Session Suspended Session suspended 00:43:46   Dome Closed Dome closed (closing time 49s) 00:47:38     Target Cancelled Target cancelled (8/23, GCVS SS Cyg) due to cloud 00:52:57   Camera1 SetPoint SBIG Camera Set Point Temperature Updated (new set point -15°C) 00:57:11     Target Cancelled Target cancelled (9/23, GCVS BL Lac) due to cloud 01:06:01     Target Cancelled Target cancelled (10/23, HIP 87937) due to cloud 01:16:29     Target Cancelled Target cancelled (11/23, NGC 6704) due to cloud 01:26:17     Target Cancelled Target cancelled (12/23, GCVS CY Lyr) due to cloud 01:33:01   Camera1 SetPoint SBIG Camera Set Point Temperature Updated (new set point -10°C) 01:35:45     Target Cancelled Target cancelled (13/23, GCVS CI Cyg) due to cloud 01:37:11 Session Resuming Session resuming 01:37:56   Dome Opened Dome opened (opening time 45s) 01:37:59 Session Running Session running 01:38:01   Queue Resumed Observing Queue resumed 01:38:03     Target Started (14/23) Target started (14/23, Kinman Dwarf) 01:41:20       Focusing Failed Foc1 Focusing Failed - unable to find a star (TCF-S) 01:56:31     Target Completed Target completed (14/23, Kinman Dwarf) 01:56:33     Target Started (15/23) Target started (15/23, GCVS Z And) 01:59:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:02:42       Focusing Failed Foc1 Focusing Failed - failed QC check (Quadratic) 02:03:13 Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Shutter) 02:03:15   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 02:03:36     Target Aborted (15/23) Target aborted (15/23, GCVS Z And) due to cloud 02:03:38   Queue Paused Queue pausing for HardSuspend 02:03:39 Session Suspended Session suspended 02:04:29   Dome Closed Dome closed (closing time 49s) 02:05:44 Session Resuming Session resuming 02:06:29   Dome Opened Dome opened (opening time 45s) 02:06:31 Session Running Session running 02:06:33   Queue Resumed Observing Queue resumed 02:06:35     Target Started (16/23) Target started (16/23, Berkeley 102) 02:09:30       Focusing Failed Foc1 Focusing Failed - star is lost (TCF-S) 02:13:29 Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Shutter) 02:13:31   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 02:13:34     Target Aborted (16/23) Target aborted (16/23, Berkeley 102) due to cloud 02:13:36   Queue Paused Queue pausing for HardSuspend 02:13:38 Session Suspended Session suspended 02:14:20   Dome Closed Dome closed (closing time 40s) 02:15:43     Target Cancelled Target cancelled (16/23, Berkeley 102) due to cloud 02:21:45 Session Resuming Session resuming 02:22:30   Dome Opened Dome opened (opening time 45s) 02:22:32 Session Running Session running 02:22:34   Queue Resumed Observing Queue resumed 02:22:36     Target Started (17/23) Target started (17/23, GCVS HH And) 02:24:16       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:27:08       Focusing Failed Foc1 Focusing Failed - failed QC check (Quadratic) 02:27:16   SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (reducing clarity) 02:28:31   SoftSuspend Cancelled Soft Suspend is cancelled due to Improved Conditions 02:29:04     Target Completed Target completed (17/23, GCVS HH And) 02:29:06     Target Started (18/23) Target started (18/23, WDS GRB 34) 02:31:01       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:33:39       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 02:35:38     Target Completed Target completed (18/23, WDS GRB 34) 02:35:40     Target Started (19/23) Target started (19/23, Berkeley 95) 02:40:16       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:43:17       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 02:49:34     Target Completed Target completed (19/23, Berkeley 95) 02:49:37     Target Started (20/23) Target started (20/23, Berkeley 100) 02:52:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:55:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 03:01:12     Target Completed Target partially completed (20/23, Berkeley 100) 03:01:14     Target Started (21/23) Target started (21/23, Berkeley 1) 03:03:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:06:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 03:12:20     Target Completed Target completed (21/23, Berkeley 1) 03:12:22     Target Started (22/23) Target started (22/23, GCVS RX And) 03:13:50       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:16:57       Focusing Failed Foc1 Focusing Failed - failed QC check (Quadratic) 03:19:32     Target Completed Target completed (22/23, GCVS RX And) 03:19:34     Target Started (23/23) Target started (23/23, UGC 1032) 03:22:57       Focusing Failed Foc1 Focusing Failed - unable to find a star (TCF-S) 03:24:36 Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Shutter) 03:24:38   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 03:24:40     Target Aborted (23/23) Target aborted (23/23, UGC 1032) due to cloud 03:24:42   Queue Paused Queue pausing for HardSuspend 03:24:45 Session Suspended Session suspended 03:25:31   Dome Closed Dome closed (closing time 46s) 03:34:47   Camera1 SetPoint SBIG Camera Set Point Temperature Updated (new set point -15°C) 03:40:21     Target Cancelled Target cancelled (23/23, UGC 1032) due to cloud 03:40:26   Queue Completed Job Queue completed 03:40:33 Session Closing Session closing 03:40:37   Dome Closed Dome already closed (closed at 03:25, closing time 46s) 03:41:05   Dome Parked Dome parked (parking time 27s) 03:41:52   Telescope Parked Telescope parked (parking time 40s) 03:42:22   Telescope Switched Off Telescope Power has been switched off via UPB Powerbox. 03:43:09   Services Stopped Night Services stopped 03:43:11 Session Housekeeping Housekeeping Started (Cleanup FITS, Create Fits Summary, Transfer Files) 03:43:23 Session Finished Session Finished

Session Alerts

Time     Alert Detail 22:23:14 Scope Alert TheSky's scope is reporting a RA=0/Dec=0 position or is not connected

Back to Top

Operational Issues (2020-08-08, S797)

• Critical Issues (0)
• Major Issues (2)
• Minor Issues (9)
• Continuous Improvement (8)

[ Prev | Next ]

Critical Issues

• None

Major Issues

• CCDSoft producing  "SBIG Driver: Camera not found" message when attempting  "Connect Camera".  Problem was last seen xxxxxx and based on that experience, the SBIG camera was powered off/powered on and the Observatory Computer restarted. Checking Camera Connection is one of the first tasks that AutoStart needs to perform - if there is a problem the routine can return to Normal mode, without passing problem into Fully Automated mode.
  Resolved by User Intervention, 2020-08-08  (Session).  Camera check for Autostarted added 2020-08-09 (AstroMain 3.27.2)
   
• CCDSoft producing  "SBIG Driver: A camera was detected, but is not match the one selected".  After restarting SBIG Camera and restarting the observatory computer, a second error message was produced from CCDSoft when attempting 'Camera Connect'.  Examining the CCDSoft Camera showed that Camera had somehow became set to 'Celeston PixCel237' and the Filter Wheel set to 'None Selected' . A similar issue was since once before and again the reason why Camera had reset itself is baffling.  Problem occurred shortly after an issue staring CCDSoft why it produced the message 'you are about to open another copy of the program'  Issue was resolved in the session by intervening to changing Camera and Filter Wheel settings back to SBIG ST-10/10XE and SBIG CFW-10. Checking Camera Connection is one of the first tasks that AutoStart needs to perform - if there is a problem the routine can return to Normal mode, without passing a critical problem into a Live Session. Is there a way to read what camera / filter wheel  CCDSoft is set to use ?
  Resolved by User Intervention, 2020-08-08  (Session).  Camera check for Autostarted added 2020-08-09 (AstroMain 3.27.2)

Minor Issues

• AutoStart not starting session due to Light Conditions (failed SunAlt check). Although an attempt was made to fix this problem in AstroMain 3.27.1 with coding change & new GetSunAltNow() function using AstroRoutines, AutoStart nevertheless failed to run at 22:19 with the same issue.  Manager Tab was showing SunAlt to be seemingly 'stuck' on +23.6 deg (rather than having updated to -9 deg). Resolved at time by returning to Normal Mode and restarting Services, which fixed the problem.  Later with observatory in Fully Automated mode the Sun Alt field was noticed to be updating as normal.  It would seem that the thread in which updates to SunAlt are made isn't called when the Observatory Mode is in AutoStart mode.
  Fixed 2020-08-09 (AstroMain 3.27.2)
   
• AutoStart's Start Night Services didn't turn on Telescope Power & wait 60s, leading to the Start Telescope service to fail.  Issue occured during AutoStart's first test session (2020-08-06) and although an attempt had been made to fix it in AstroMain 3.27.1 the problem arose again in the new session (2020-08-08).  
  (Fix to stop PHD2 from attempting to connect to mount in this situation worked again, but a connect to scope via TheSky was still commanded and produced the "The Telescope object is null" message & associated Ra=0/Dec=0 issue ). Problem identified (Scope.SetPowerOn_Quiet()  wasn't recognising the AutoStart Mode within its check of valid conditions )
  Fixed 2020-08-09 (AstroMain 3.27.2)
   
• "Unable to connect to Mount:" messages produced when trying PHD2 is requested to connect. It is presumed that message is a by product of a bug introduced during recent code modifications.  Checking code confirmed that bug did indeed relate to recent code changes. Bug fixed in PHD2.StartPHD2()
  Fixed 2020-08-09 (AstroMain 3.27.2)
   
• Observatory Manager not seeing Cloud Sensor / Weather Data from AllSky Computer. Issue appeared after starting AstroMain, following a Computer restart. Issue resolved itself after a couple of minutes, but not before logging onto AllSky Computer to check/confirm that computer was running and Weather server was working ok
  Resolved itself during Session 2020-08-08 (Session)
   
• ObsViewer showing Telescope Power On (Green) when the Telescope Power was actually off.  This occurred after using manual button 'Park Scope' which parked scope and turned its Power off after 30s.  Checking UPB Software showed that Power to Telescope was indeed off. This is the fiirst time this particular issue has been seen.  Resolved by Stopping and Restarting Services.  Examining ObsPics indicates a 1 minute window between 22:39:19 (Power Switched Off) and 22:41 (All Services stopped) when the Scope PowerState should have become set to 0 (Off) leading to Red Traffic light on ObsViewer.  Examining code (RunObservatoryMonitoring() ) where Scope.PowerState variable is set indicates that the only reason that Scope.PowerState wouldn't change from 1 to 0 over a course of 1 minute would if PowerBox.SwitchLock Is Stuck to On (i.e. PowerBox.bSwitchLockIsOn = True) or the Switch Driver (objPowerBox) isn't updating with values from the UPB Software/Powerbox. Log messages added to help trace instances where Switch Lock is On.  Issue deemed closed following review 2021-05-13
  Closed 2021-05-13  (AstroMain)
   
• TheSky6 and CCDSoft5 both producing message that a second copy of the program is about to open.  This occurred after employing 'Launch Programs' from AstroLaunch after restarting the Observatory Computer (during which AstroProtect ran and the Dome and Telescope are checked to ensure that they were safe).
  Issue closed (2020-10-20) as problem has not been seen in the 20 sessions since the incident occurred in S797.
  Closed 2020-10-20 (AstroMain)
   
• Near-Zenith Focus Locate Frame (Foc1) contained trailed stars.  Whilst trailed stars didn't prevent the detection of a bright star that could be used for Focusing, the image  was unable to provide reliable pixel coordinates for the star and the following Focus Frames didn't contain the star (or indeed any star object). As a consequence AuutoFocusing failed. Issue might be helped by using a longer 'wait for telescope to settle' time. FocusScopeNearZenith() routine has been updated to include a 5 sec sleep after slew to allow time for scope to properly settle.
  Fixed 2020-08-09 (AstroMain 3.27.2)
   
• Condensation patches in corners of first few CCD Images.  SBIG camera's CCD Dessicator needs to be regenerated.
  Problem still present in S803 (2020-09-01) . Struggled on into September with the problem not becoming any worse than effecting the first few frames in each new session. Dessicator finally renewed and reinserted in CCD Camera on 2020-09-23
  Fixed 2020-09-23  (Observatory CCD Camera)
    
• Foc2 autofocusing on (TS-80 Scope) using ASI camera not working sufficiently well. Although precursive wide range focusing had clearly defined the approximate position of best focus. (Best Focus at Steps 8801,  FWHM 3.18" ), the subsequent standard focusing was unable to generate a well formed focus profile but nevertheless picked a best focus based on best (sharpest) FWHM value (Best Focus at Steps 8826, FWHM 9.72").  Autoguiding with PHD2 showed that telescope wasn't sufficiently focused.   User intervention used to change Focus Offset from -250 to 0 which sharpened the stars in PHD2 to a level that was better suited for autoguding.  Prehaps Backlash isn't working or the amount of backlash is too low.  To try to eliminate backlash as the factor, the amount of Observatory Foc2 backlash is increased from 2500 to 3500 steps.  Foc2 focusing confirmed to now be fixed using combination of increased backlash and precursive wide focus search method
  Fixed  2020-08-31 (AstroMain 3.28.1 / Session)

Continuous Improvement

• Make AutoStart check camera connection before preceeding to Start Night Services (Telescope etc).  In the event of a problem with CCD Camera connection from CCDSoft , AutoStart should send out a Session Alert and return the Observatory to Normal mode before embarking on a live session.
  Done 2020-08-09 (AstroMain 3.27.2)
   
• Several log messages have a typo where '....  Fail,  ...'  contains a unnecessary comma.   Code modified in 6 places to remove the unnecessary comma.
  Fixed 2020-08-09 (AstroMain 3.27.2)
   
• Make AutoStart check that AllSkyStarState is SkyState.Good before creating a live session. To make sure that conditions are suitable for a session we make sure than CanResume() is True, but need some extra tighter criteria , we need AllSkyStarState = SkyState.Good
  (this occurs when StarCount >= TooFewStarsThreshold() + 5 or  StarCount >= TooFewStarsThreshold() &  MinutesSince(TimeSufficientStars) > 8 )
  Criteria may need adapting further based on forthcoming experience and results from AutoStart.  How many minutes of clear sky is required to say its worth observing ? 
  Done 2020-08-10 (AstroMain 3.27.3)
   
• Add general session events to SessionEvents table to record start of Session Monitoring,  Session AutoStarting,  Session Cancelling. Add these as historic live session events and post them on them the session's Observing Results chart.
  Done  2020-08-10 (AstroMain 3.27.3, AstroPlan 15.5)
   
• The progress of the AutoStart monitor on Website needs to be revised to include Events and Alerts.   This will be handled by calling AstroPlan's SaveHtmReport("General", -10) routine.  
  Done 2020-08-10 (AstroMain 3.27.3, AstroPlan 15.5, WebSite)
  
  Warning: Potential problems can theroretically arise if Targets Database is loaded to Observatory Computer without recreating General Session which might lead to historic Events and Alerts being reported, rather than data for the current live night date.
   
• Develop an Observatory Alarms System (AstroAlarm) to provide auditory alarms etc for certain alerts & events associated with the Observatory (and specifically wake-up alarms sounding on IPAD to wake user in event of critical equipment issues). See system description for AstroAlarm. Prototype has been built (see Observatory Alarms web page) and proof of concept routines developed in AstroMain and AstroPlan for alarm generation and upload
  Done 2020-08-10 (AstroMain 3.28, AstroPlan 16.0, WebSite)
   
• AstroVoe should make initial check that TheSky6 is running and then automatically start the VOE Event Client
  Done 2020-10-05 (AstroVOE 1.4)
   
• Initial (blank) Focus Profile chart should ensure that it is using correct range and has correct reference line before its first draw.
  Done 2020-10-18 (AstroMain 3.10.8)

[ Prev | Next ]

Back to Top

AutoStart - Results (2020-08-08)

2020-08-08 was the second live test of AutoStart (new observatory mode).  The night had expected to be clear through the evening and the night was forecast to be dry and semi-clear .  Whilst a LIve Session would have been intitated anyway, AutoStart was used anyway to test its new and evolving routine.

 Skies were cloudy in the early evening and the DarkSky weather forecast for the night  showed dry but relatively cloudy conditions (cloud cover 53 to 76%), though another forecast source (xcweather.co.uk) offered slightly more encouragement and suggested a potential 2 hour interval of clear skies at around 00:30 - 02:30 in the morning.  

Result: Partially Successful Test (Clear Night) a Live Session was created and after 4 attempts and significant user intervention an automated session was finally kicked off and executed.  Several bugs and issues identified for resolution before the next test (2020-08-09)

Attempt 1:   AutoStart Mode was initiated from AstroMain 3.27.1 program at 17:48.
It's operational window was from 22:19 (30 minutes before descending Sun Alt -11 deg) to 02:55 (30 minutes before ascending Sun Alt -12 deg)
AutoStart was unable to run at 22:19 due to light conditions.   This was due to a bug that was failing to update SunAlt when observatory was in the new AutoStart mode).

User intervention was made to cancel AutoStart and Restart Observatory Services

Attempt 2:   AutoStart Mode was re-initiated at 22:21, with operational window  from 22:21 ('Now') to 02:55
AutoStart deemed that conditions were suitable for starting an observatory session at 22:21 and proceeded to create a Live Session.

Session began executing. Night Services were started but due to a bug the Telescope Power was not commanded to switch on and the telescope was therefore not connected to.  AutoStart routine picked up that there was a problem with Telescope connection through Ra=0/Dec=0 Scope Coords in TheSky, aborted automated operations and returned the observatory to Manual Mode.

User Intervention was made to set Scope Power On

Attempt 3:  AutoStart Mode was re-initiated at 22:28. with operational window from 22:28 ('Now') to 02:55
AutoStart deemed that conditions were suitable for starting an observatory session at 22:28 and proceeded to reopen the Live Session.

Session began executing. Night Services were started and the Telescope was connected to ok.  Execution continued despite finding a problem connecting to CCD Camera and had reached and opened the Observatory for Temperature Equilibration,  before user monitoring recognised the camera problem

User Intervention was made to abort automated operations, restore communication to CCD Camera, involving parking scope, power cycling CCD Camera and restarting Computer and restarting Observatory Software etc, fixing a problem with CCDSoft Camera Settings and turning the Scope Power On

Attempt 4:  AutoStart Mode was re-initiated at 23:06, with operational window from 23:06 ('Now') to 02:55
AutoStart deemed that conditions were suitable for starting an observatory session at 23:06 and proceeded to reopen the Live Session.

Session began executing. Night Services were started and the Telescope again connected to ok.  Execution continued despite finding another problem connecting to CCD Camera (Settings problem in CCDSoft). A User Intevention was made to Achieve Camera connection without stopping Automated Operations.  Automated operartions were conducted  for remainder of the session including automatically closing the observatory down at 03:40


Report Logs :

USER INTERVENTION AT THIS POINT >>

Remainder of session report log not shown here.

Back to Top

2020-08-09

AutoStart - Results (2020-08-09)

2020-08-09 was the third live test of AutoStart (new observatory mode).  The night had exactly the sort of conditions that AutoStart is designed for. Skies were cloudy in the early evening and the DarkSky weather forecast for the night  showed dry but relatively cloudy conditions (cloud cover 53 to 76%), though another forecast source (xcweather.co.uk) offered slightly more encouragement and suggested a potential 2 hour interval of clear skies at around 00:30 - 02:30 in the morning.  

Rather than stay up until 01:00 just in case the skies cleared, AutoStart Mode was initiated from AstroMain 3.27.2 program at 22:03.
It's operational window was from 22:39 (20 minutes before descending Sun Alt -12 deg) to 02:59 (30 minutes before ascending Sun Alt -12 deg)
AutoStart was unable to run at 22:39 due to cloud, and monitoring continued pending suitable observing conditions.  Conditions didn't improve and at 02:59 AutoStart was automatically cancelled.  

Result: Successful Test (Cloudy Night) - a Live Session was not created.

2020-08-09

Weather Forecast for 2020-08-09 The Weather forecast for the night (generated at 21:00) didn't look particularly good with relatively cloudy conditions (cloud cover 53 to 76%) but dry and fairly calm (6-8 mph wind). Temperature falling from 13-14 degC.  (API data from darksky.net) Another Weather Forecast source (xcweather.co.uk) offered slightly more encouragement and indicated a potential 2 hour peirod of clear skies at around 1-2am in the morning.

Actual Weather for 2020-08-09 In the event conditions skies were cloudy for pretty much the entire night, with a few short partial breaks in the cloudy,  but with no more than ~ 15 AllSkyStars &  maximum clarity of ~ 25  The night was howver dry throughout (no rain) and winds were light.

Night Sky Summary Plot - 2020-08-09

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

Cloud Sensor & Stars Plot - 2020-08-09

 

Back to Top

2020-08-11

Observatory Alarm System (AstroAlarm)

AstroAlarm is a new AstroSuite product & web app being developed to provide auditory sounds/alarms for various events and alerts associated with the Clair Dome Observatory (for prototype see Observatory Alarms web page).

It will comprise a set of Javascript & HTML5 Code within an 'Observatory Alarms' webpage on the Observatory Website and associated Observatory Software routines (within varous AstroSuite programs : AstroMain, AstroGuard, AstroProtect, AstroAllSky) that will set Alarms based on various Event/Alert triggers.

It's principal aim is for the 'Observatory Alarms' web page to be left running in Safari on an IPad beside my bed at night and for it to sound an alarm) if there is critical observatory condition or alert (e.g.  if the shutter hasn't closed)  

Beside a night-time mode (which sounds alarms for a select number of conditions critical events), there will be a wake-and-reassure alarm to indicate that observatory session has successfully closed down at the end of the session.

(In due course the system may be converted to a iOS App but this won't be attempted until the system has been fully prototyped and specification has hardened and been tested over a period of time)

Sleep Mode

"Wake-and-attend"  - purpose:  wake user as there is a critical condition requiring immediate attention (e.g. the shutter hasn't closed when it should)

"Wake-and-check" - purpose:  wake user as the session has stalled (in a safe state) but requires restarting

"Wake-and-reassure"  - purpose:  wake user briefly as the session has finished and successfully closed down the observatory (shutter closed, dome and scope parked etc

"Wake-at-specific-time " - purpose:  wake user at a specific time (hh:mm) or particular sun altitude (deg).

Normal Mode

'Wake' alarms as above, plus following 'Inform' events

"Session_has_started" - purpose:  notify user than session has started.

"Shutter_has_opened" - purpose:  notify user than observatory dome has opened.

"Telescope_is_slewing" - purpose:  notify user than telescope is slewing to a target

"Shutter_has_closed" - purpose:  notify user than observatory dome has closed.

Alarm trigger mechanism

Development, Testing & Deployment

• 1st Test Code : Proof of concept test web page  (2020-08-11)
• 1st Test Version : Working code ready for live test, AstroMain 3.27  (2020-08-06)
• 1st Live Test : Live test, AstroMain 3.27  (2020-08-06, S797 Attempt)
  

Back to Top

2020-08-17

Virtual Weather Station - Database Glitch

Whilst trying to resolve Weather data and displays issues that have affected recent days (wind data offline and gaps in temperature/pressure data), it was noticed in testing on Development Computer and then in Live Weather Graphs from AllSky Computer that no data was plotting from 13th Aug 00:00 to 17th Aug 16:09, when previously data had been plotting in this time interval.

Investigating further should that the VWS database (dbase.csv file) had a time gap of around one month between 2020-07-18 14:46 and 2020-08-17 16:09.

It is unclear how or why this happened. Prehaps the VWS program had performed an automatic database resize on 2020-08-17 and there was a flaw in its algorithum for doing this or it had encountered some block on the dbase file or something else. Eitherway it resulted in lost of mid-term weather data.

2020-08-18

AllSky Computer Problems (BSOD & Failed Windows Startup)

AllSky/Weather Computer has been having a serious of problems in recent days with the appearance of Blue Screen of Death (BSOD) crashes, with stop messages "Critical Structure Corruption" and "DPC Watchdog Violation".   Could be system file corruption, could be a driver problem but is hard to diagnose and fix. Even worse are the crashes when everything stops / no messages at allos

Since the problems are not continuous and difficult to resolve I'm had resigned myself to just struggling on with the intermittent problems and the annoying requirement to have to visit the observatory every so often to restart the computer. 

With BSOD crashes I can make things a little easier to manage by setting the computer to automatically reboot following a BSOD, so that the login & restart of AllSky/Weather programs can at least be performed remotely without needing a visit the computer to Power Off/Power On the computer.

However this morning (2020-08-18) Windows 10 wouldn't load when the computer was re-started and windows diagnostics couldn't resolve the issue, and sounds being made from disk didn't sound too good.  I was about to give up and just order a new computer (Toshiba Dynabook Satellite Pro C50-E-102)  when I eventually got Windows 10 to load.

Automatic Reboot was enabled, using the method
>  Open elevated (Admin) Command Prompt
>   wmic RecoverOS set AutoReboot = True

and Windows Update was run
- Window Feature Update to Windows 10, version 1903 installed
- Various Windows Update installed,
- Net 4.8 Framework Update installed

Back to Top

AllSky Computer,  Potential Replacement

At some point the AllSky/Weather Computer will fail or it becomes simply to problematic to continue with, and will need to be replaced.

A potential replacement (Toshiba Dynabook Satellite Pro C50-E-102) has been identified and the question is whether to wait untill the existing computer fails or get the replacement ahead of time and get it setup and running with all the necessary programs & hardware offline, without having to endure a potentially long outage if the AllSky Computer was to stop with no backup pre-prepared.

Toshiba Dynabook Satellite Pro C50-E-102 
 at laptopsdirect : https://www.laptopsdirect.co.uk/toshiba-dynabook-satellite-pro-c50-e-102-core-i5-8250u-8gb-512gb-ssd-15.6-i-a1pys20e111d/version.asp

Back to Top