David's Astronomy Pages Notes - Session S797 Attempt (2020-08-06)

Notes (S796)

Notes Main

Home Page

Notes (S797)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (1),  Minor Issues (9),  Continuous Improvement (5)
	No Images from 2020-08-06 >>
	2020-08-07
	Potential Observing Session not utilised (2020-08-07)

Session Aims & Highlights (2020-08-06)

Main aims

1. AutoStart. Conduct first live test of AutoStart (new observatory mod)
2. Focusing with Wide Search. Conduct first live test of autofocusing of both Foc1 (Main Scope) and Foc2 (Secondary Scope) systems using a precursive widened search range
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,  AstroGuard 1.4.2,   AstroPlan 1.15.3,  AstroShCap 1.2.23, AstroVOE 1.3.6
  (AstroWeather 1.10.9, AstroAllSky 3.6)
  

Highlights

• AutoStart. First live test of AutoStart was conducted, which uncovered some issues which was not unexpected and wll help strengthen the code ready for subsequent testing in forthcoming sessions
•  Focusing with Wide Search.   Tests of wide search option basically worked. Foc1 test was completetly successful. Foc2 wide focusing test was working until a programing bug in reporting led to an unhandled .net exception that caused the AstroMain program to stop before the standard focusing was achieved.
• AstroGuard. AstroGuard worked as per design and closed down the observatory after 15 minutes of inactivity from AstroMain following program crash.

Lowlights

• AstroMain crash.  A programing bug associated with new Foc Wide Focusing reporting led to an unhandled .net exception that caused the AstroMain program
• Targets. No targets were imaged due to cloud and the AstroMain program crash

Summary Plots & Logs

Observing Plan

Observing Result

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 good condition (5-12% cloud cover) in first half of night becoming more cloudy in second half of night (24-90% cloud cover) with light/moderate wind (10-13 mph) , no rain and a minimum temperature of 15°C. In the event conditions cloud developed at 22:45, then cleared at 00:15 to 01:15 before becoming cloudy with odd partially clear patch for remainder of night

Session Event Log

Time     Event Detail 22:32:31   Camera1 Connected SBIG Camera Connected (set point -15°C) 22:32:33 Session Created Live Session Created (2020-08-06 S00797 Attempt, ImageSaveNum: 797001) 22:33:16   Services Started Observatory Services started 22:33:17 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:33:20 Session Pending Session pending (2020-08-06) 22:33:22 Session Initiating Session initiating (2020-08-06) 22:33:24   Plan Requested Observing Plan requested from AstroPlan (1.15.3) 22:34:19   Plan Loaded Observing Plan loaded to queue (2020-08-06 V1 BEST PLAN, Plan ID: 529) 22:34:24   Camera1 Connected SBIG Camera Connected (set point -10°C) 22:34:30 Observatory (Manual) Observatory placed in Manual Mode 22:34:53   Services Stopped Observatory Services stopped 22:35:00   Obs.Manager Started Obs.Manager started 22:35:02   Obs.Overseer Started Obs.Overseer started 22:35:06   Services Started Observatory Services started 22:35:23   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 22:37:13   Services Started Observatory Services started 22:37:47 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:37:52 Session Pending Session pending (2020-08-06) 22:37:54 Session Initiating Session initiating (2020-08-06) 22:37:56   Plan Loaded Observing Plan loaded to queue (2020-08-06 V1 BEST PLAN, Plan ID: 529) 22:37:58   Camera1 Connected SBIG Camera Connected (set point -10°C) 22:41:16   Telescope Connected Telescope Connected (TheSky6) 22:41:30 Session Equilibration Session ready for dome & camera equilibration 22:42:15   Dome Opened Dome opened (opening time 45s) 22:42:18   Equilibration Started Dome Equilibration started 22:42:56   Telescope Connected Telescope Connected (TheSky6) 22:45:15   Equilibration Ended Dome Equilibration ended (3.0 mins total) 22:45:17 Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Shutter) 22:45:21   Equilibration Started Dome Equilibration started 22:45:23   Equilibration Ended Dome Equilibration ended (0.0 mins total) 22:45:25 Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Shutter) 22:45:27 Wait On Weather Waiting For acceptable conditions 22:46:01   Dome Closed Dome closed (closing time 40s) 22:47:56 Session Suspended Session suspended 22:47:58   Dome Closed Dome already closed (closed at 22:46, closing time 40s) 22:48:00   Queue Started Observing Queue started (23 targets selected) 22:58:02   Dome Port Lost Dome Port Lost 22:58:07   Dome Port Changed Dome Port changed from COM9 to COM14 23:10:41   Telescope Connected Telescope Connected (TheSky6) 23:17:08     Target Cancelled Target cancelled (1/23, C/2020 F3 (NEOWISE)) due to cloud 23:31:42     Target Cancelled Target cancelled (2/23, NGC 6741) due to cloud 23:40:32     Target Cancelled Target cancelled (3/23, HIP 87937) due to cloud 23:51:01     Target Cancelled Target cancelled (4/23, NGC 6704) due to cloud 00:03:00     Target Cancelled Target cancelled (5/23, Berkeley 43) due to cloud 00:16:19     Target Cancelled Target cancelled (6/23, GCVS S Cyg) due to cloud 00:20:34 Session Resuming Session resuming 00:21:19   Dome Opened Dome opened (opening time 45s) 00:21:22 Session Running Session running 00:21:24   Queue Resumed Observing Queue resumed 00:22:24       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:26:25   SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (reducing clarity) 00:26:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 00:27:10   SoftSuspend Cancelled Soft Suspend is cancelled due to Improved Conditions 00:29:56       Focusing Failed Foc1 Focusing Failed - failed QC check (Quadratic) 00:29:59       Focusing Started Foc2 Focusing Started (Secondary Scope, using ShCap) 00:32:14       Focusing Failed Foc2 Focusing Failed - program bug/unhandled exception in newly added code 00:32:15 Program Crashed AstroMain crashed due to unhandled exception in Foc2 focusing code 00:47:00 Session Closing Observatory is being closed down by AstroGuard, after 15 mins of inactivity from AstroMain 00:47:47   Dome Closed Dome closed by AstroGuard (closing time 47s) 00:48:45   Dome Parked Dome parked by AstroGuard (parking time 58s) 00:48:57   Telescope Parked Telescope parked by AstroGuard (praking time 12s)

Session Alerts

Time     Alert Detail 23:01:07 Dome Alert DomeRecords have stopped updating

Back to Top

Operational Issues (2020-08-06, S797 Attempt)

• Critical Issues (0)
• Major Issues (1)
• Minor Issues (9)
• Continuous Improvement (5)

[ Prev | Next ]

Critical Issues

• None

Major Issues

• AstroMain program stopped due to unhandled .net exception asscociated with recently modified Foc2 Focusing code.  An unhandled exception (conversion error) occurred at 00:32, which was caused by recent modification to the code for reporting Foc2 focusing results for Wide Range focus searching.  Problem was recognised during prior testing but had only been applied to Foc1 Focusing and not to Foc2 Focusing. AstroGuard operated as per design to keep the Observatory safe after 15 mins of inactivity from AstroMain.   Issue is classified as Major as it brought the session to a complete end,   but safeguards operated to prevent leaving the observatory in danger.
  Fixed 2020-08-07 (AstroMain 3.27.1)

Minor Issues

• AutoStart not starting session due to Light Conditions (failed SunAlt check). Although the 'CanResume' light test succeeded on Cloud Sensor Light readings (0.1) the light test failed on Sun Alt value (+3.6 degs).   This was unexpected because Sun Alt was -8.5 degs at the time. There have been instances before where AstroMain can have the wrong SunAlt value when starting and has updated to the value from AllSky Computer.  It's unclear why AstroMain had an incorrect value. Issue was resolved by cancelling AutoStart, and restarting Observatory Services where upon AstroMain began using the correct Sun Alt value (-9.0 etc). Problem is probably best resolved by having AstroMain calculate Sun Alt by its own code (Astro Routines) rather than depend on TheSky which can't be depended upon session is running. This will be handled via a new funtion GetSunAltNow().  Although issue was thought to be fixed in AstroMain 3.27.1, the same problem cropped up in Session S797 (2020-08-08)
  Fixed 2020-08-09 (AstroMain 3.27.2)
   
• AutoStart not starting session at 22:32 due to Cloud, but proceeded to start Live Session a few seconds later (still 22:32).
  It seems that AutoStart should be waiting for a longer period of improved conditions before committing to the initiation a new live session.  CanResume acceptance criteria to be examined and made appropriate in the context of AutoStart. Investigating :
   At 22:32 (Sun Alt -9.0 deg ) clarity values ranged from 27 to 28.5.   First Clarity value after starting new session was 27, with AllSky Stars of 3.
  >> Investigate   (Session, AstroMain)
   
• AutoStart's Start Night Services didn't turn on Telescope Power & wait 60s, leading to the Start Telescope service to fail.  Code to be examined to see if this is a problem with Live/Test computer or a mode change away from AutoStart when new Session was created.  Code shows that Power wasn't checked & turned on because the  session wasn't a live one at the moment that Telescope Service was being started. This is a consequence of AutoStart running Start Services whilst Session was still a general one.    When running on Observatory Computer the AstroMain program should always check/turn on scope power, unless a Telescope Simulator is being used.
  Fixed 2020-08-07 (AstroMain 3.27.1)
   
• PHD2 showing error message re ASCOM name/property and unable to connect to Mount.   Problem seems to have been caused by AstroMain connecting to PHD2 Server and requesting PHD2 to Connect to Mount even though AstroMain's own attempt to connect to Telescope had failed (as power wasn't on).   This is one of the extra checks that has to take place for AutoStart to hardened for reliant automation.  
  Fixed 2020-08-07 (AstroMain 3.27.1)
   
• Telescope in TheSky and on AllSky Annotated Image pointing to incorrect location.   After going back to Normal Mode, powering up the Telescope and restarting Night Services, a connection to scope through DeviceHub.Telescope was made.  Upon returning to Fully-Automated mode TheSky was commanded to connect to telescope.   It was noticed that whilst the Obs.Viewer was showing the scope pointing to expected coordinates c. Az 183 Alt 2 (close to Start-Up from Park position) and matching the coordinates on Device Hub's telescope tab, the TheSky scope was pointing to Az 98, Alt 5 (at c. 22:42).  Earlier TheSky had produced the message "The Telescope object is null" which had to be manually acknowledged.   The problem was resolved at 23:10 by disconnecting & reconnecting the scope in TheSky.   Investigating showed that TheSky was carrying Ra 0, Dec 0 coordinates for the scope, which at 22:42 corresponded to Az 98, Alt 5 position for the scope shown in TheSky virtual sky.  These Ra 0, Dec 0 coordinates are reported by AstroMain's 'Connect Telescope' routine.  AstroMain needs to recognise the presence of the issue and moderate it's automated actions accordingly, alert user,  abort session  / use ASCOM only for parking scope.  Problem was most-likely a consequence of earlier Telescope Power Up  / failed scope connection problem.
  Resolved 2020-08-06  (Session),  Alerts Added 2020-08-07 (AstroMain 3.27.1)
   
• 'Tele Dec' showing as -99° on ObsViewer from 22:32 (start of session) to 22:36. After creating new session via AutoStart at 22:32 Telescope Declination was displayed wth vcNull value (-99).   Why was value vcNull and why was it shown as -99 rather than converted to  "--" for display.   Value was vcNull because Telescope wasn't connected (power was still off).   Code has been corrected so that is shows '--' when value is vcNull.    At the same time TeleAz (180) and Tele Alt (0) were shown as these where default values assuming that scope was probably parked, rather than being known values
  Fixed 2020-08-07 (AstroMain 3.27.1)
   
• 'Dome Az' showing as "--" at 22:34. Dome Az which was displayed as 90° at 22:32 to 22:33, is displayed as "--" at 22:34:16 & 22:34:48 when Session was transitioning between "Initiating" and "Manual" states, afterwhich it is displaying as 90° again at 22:35:19. Examining log files shows that ASCOM. Dome Service was stopped at 22:33:47 and restarted at 22:35:00. This explains why Dome Az was displayed as  "--" (vcNull) at the times it did.
  Closed 2020-08-07 (Session)
   
• 'Dome's COM Port Changed from COM9 to COM14.  Dome COM POrt has an occasional habit of switching between these two port numbers which stops data communication between the ASCOM.Dome object and the Dome itself.  Workarounds have been employed in AstroMain and AstroGuard to close ASCOM.Dome, modify the Dome Port Number in ASCOM.Dome/Hub properties and restart the ASCOM.Dome.   The details of this had been forgotten and when COM Port was seen to change and manual Dome slews couldn't be actioned a user intervention was made to disconnect and reconnect the Dome in DeviceHub. This may have not been necessary and could have interferred with actions being taken by AstroMain/AstroGuard themselves.
  Resolved 2020-08-06 (Session, User Awareness)
   
• Text boxes for 'Rain Trim' and 'Few Stars Threshold' are sometimes missing from the Obs.Manager Tab picture that is uploaded to website.  Rain Trim and Few Stars Thresshold and possibly also Temp (all TextBox fields) are missing from Manager picture on website, but other data (Label fields) are shown ok. The 'Rain Risk' value (NumericUpDown field) is also incorrectly display on the Manager Tab picture, appearing as a white outline box without the risk value (2) being visible. At other times fields show ok suggesting the problem is a paint issue of some kind.  Solution adopted in AstroMain 3.xx.x which temporarily switches form to show the relevant Tab before capturing the Tab as an image.
  Resolved (Date ?)  (AstroMain)
   
• Wind Data from WRM80 Weather Station (speed & direction) has become intermittent or absent.  Over last 24 hours wind sensor data has been playing up. Attempt to get it working by restarting the Base Unit failed. WInd Data came back later by itself for 8 hours or so, but has been going off again. Need to check the strength of batteries in Wind Sensor.  Fixed by replacing batteries in Wind Sensor and resetting wind sensor and base unit. Data has been stable for 4 days now (2020-09-04 to 2020-09-08)
  Fixed 2020-09-04 (Observatory)
   
• AstroMain loosing connection with Pegasus Powerbox and can't be reconnected (2020-08-07). A common problem with Pegasus Powerbox driver/client is that connection to Pegasus Powerbox becomes lost in someway.  This leads to an dialog box saying connection to powerbix has been lost.   When this happens AstroMain runs a routine to reconnect the Pegasus Powerbox / Server. This reconnection process is typically successful but this evening it wasn't. Restarting Powerbox Services, nor Restarting  AstroMain were able to fix the issue. The only solution that worked was to restart the Pegasus Powerbox Software.  This might be more of an issue during a live session.  It would be helpful to have a button routine that would explicity stop & restart Powerbox Services without having to close all services (such as Telescope service).   Button routine implemented (date unknown).
  Fixed (AstroMain / Pegasus )

Continuous Improvement

• A 'DomeRecords have resumed' standdown record should be sent to Session Alerts if/when updating resumes.  Whilst a 'DomeRecords have stopped updating' alert (Red) is inserted in the database table Session Alerts, it would be helpful to insert a standdown record (Green) when dome records resume
  Done 2020-08-07 (AstroMain 3.27.1)
   
• Calculate SunAlt using AstroRoutines.vb.  To ensure that AstroMain / Obs.Manager always has the correct SunAlt it would be useful to calculate sun alt using an AstroRoutine function rather than depend on either TheSky6 program or communications with the AllSky computer.  This is to avoid the problem that stopped AutoStart from starting at 22:26
  Done 2020-08-07 (AstroMain 3.27.1)
   
• Simulator (Sim) checkboxes should be hidden by default when running AstroMain on Observatory Computer.  Checkboxes to be shown by default when on Development Computer.  Need a button toggle on 'More' tabe to show the checkbox fields if/when required  for observatory testing.
  Done 2020-08-07 (AstroMain 3.27.1)
   
• The progress of the AutoStart monitor needs to be uploaded to website.  Following two Live AutoStart files are created:  Session.LatestAutoStartLog.log &  Session.LatestAutoStartReport.htm, written with the routine ObservatoryManager.WriteLatestLiveAutoStartLogs() and reset with the routine ObservatoryManager.ResetLiveAutoStartFiles()
  Done 2020-08-07 (AstroMain 3.27.1, AstroPlan 15.4, WebSite)
   
• A 'UPB.Switch has been successfully restarted' standdown record should be sent to Session Alerts if/when UPB Switch driver is reconnected.  Whilst a 'UPB.Switch has unexpectedly disconnected' alert (Red) is inserted in the database table 'Session Alerts', it would be helpful to insert a standdown record (Green) when the UPB Switch service is restored
  Done 2020-08-07 (AstroMain 3.27.1)

[ Prev | Next ]

Back to Top

AutoStart - Results (2020-08-06)

2020-08-06 was the first live test of AutoStart (new observatory mode).  Although pre-Session Weather forecast showed good condition (5-12% cloud cover) in first half of night becoming more cloudy in second half of night (24-90% cloud cover), skies were cloudy in early evening and din't clear until 01:15. It is probable that a Live Session wouldn't have been intitated. However it was expected to be dry and it was an opportunity to test AutoStart routine under the sort conditions that it is designed for.

Result: Failed Test (Clear Night) though several bugs and issues were identified for resolution before the next test (2020-08-08).  A Live Session Attempt was manually initiated but a new bug (nothing to do with AutoStart), caused the AstroMain program to crash, leaving AstroGuard program to make the Observatory Safe after 15 minutes of inactivity from AstroMain.

Attempt 1:   AutoStart Mode was initiated from AstroMain 3.27 program at 20:33.
It's operational window was from 22:26 (30 minutes before descending Sun Alt -11 deg) to 02:47 (30 minutes before ascending Sun Alt -12 deg)
AutoStart was unable to run at 22:26 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:32, with operational window  from 22:32 ('Now') to 02:47
AutoStart deemed that conditions were unsuitable for starting an observatory session at 22:32 due to cloud and began to waiting for better conditions
At 22:32+ AutoStart deemed that conditions were suitable for starting an observatory session 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 properly connected to.  AutoStart failed to pick up the issue and commanded PHD2 and TheSky6 to connect with an 'unconnected' Telescope causing those programs to have problems. e.g.  Ra=0/Dec=0 Scope Coords in TheSky

After a while user intervention was made to abort Automated Operations.
Session was continued by invoking Fully-Automated operations directly without the use of AutoStart

Report Logs :

USER INTERVENTION AT THIS POINT >>

2020-08-07

Potential Observing Session not utilised (2020-08-07)

2020-08-07 was another night where a potential observing session was not utilised (see Issue - Potential Observing Sessions not utilised (2020-07-29 & 2020-08-03).

The night had exactly the sort of conditions that AutoStart was designed for. ('AutoStart - New Observatory Mode'). Although an updated test version of AutoStart had been essentially created in time (AstroMain 3.27.1 with bug fixes folllowing session on 2020-08-06) it hadn't yet been deployed onto the Observatory Computer.

A new attempt to test AutoStart will be conducted on 2020-08-08

2020-08-07

Weather Forecast for 2020-08-07 Weather forecast for the night (generated at 21:00) shows relatively cloudy conditions (min cloud cover 30% at 23:00, increasing to 86-100% by dawn. Wind 9-11mph with low risk of light rain (4-9%). Temperature falling from 18 degC  to 13 degC. (API data from darksky.net)

Although updated code for new Observatory Mode AutoStart was essentially ready (AstroMain 3.27.1) it was not loaded onto Observatory Computer.  As it turned out the night of 2020-08-07 would have been an idea utilisation of the AutoStart.  The night had exactly the sort of conditions that AutoStart was designed for. ('AutoStart - New Observatory Mode')

2020-08-07

Weather Forecast for 2020-08-07 Weather forecast for the night (generated at 21:00) shows relatively cloudy conditions (min cloud cover 30% at 23:00, increasing to 86-100% by dawn. Wind 9-11mph with low risk of light rain (4-9%). Temperature falling from 18 degC  to 13 degC. (API data from darksky.net)

Actual Weather for 2020-08-07 In the event conditions skies were cloudy at dusk becoming partly cloudy to cloudy (short clear patch at 23:30), with no rain Skies cleared at 02:15 and gave at least 1.5 hours of good observing time if Observatory had been operating.  Conditions very good with light wind and 30+ AllSky Stars.

Cloud Sensor & Stars Plot - 2020-08-07

Night Sky Summary Plot - 2020-08-07

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

Back to Top