David's Astronomy Pages Notes - Session 803 (2020-09-01)

Notes (S802)

Notes Main

Home Page

Notes (S804)

	2020-09-01 (Session 803)
	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (7),  Continuous Improvement (4)
	Images from 2020-09-01 >>
	Pulsar Dome - Corroded Home Magnet

Session Aims & Highlights (2020-09-01)

Main aims

1. Targets. Acquire images of a number of targets if conditions allow.
2. Obs.Manager. Examine response of Obs.Manager to the loss of AllSky/Weather information in the case that the AllSky/Weather computer crashes, hibernates or otherwise goes offline, which was considered a likely event given the number of daytime outages in past 48 hours.
   (in the event the AllSky/Weather computer remained responsive for the entire session.)

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.28.2,  AstroGuard 1.4.3,   AstroPlan 1.16,  AstroShCap 1.2.23, AstroVOE 1.3.6
  (AstroWeather 1.10.11, AstroAllSky 3.6)
  

Highlights

• AutoStart. AutoStart was successfully used to kick off the session.
• Foc1 Focusing. A number of targets were successfully imaged once the focus issue was resolved.

Lowlights

• Cloud. Conditions deteriorated after less than 1 hour and only 6 targets were observed.

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 dry conditons for the night with minimum temperature of 13°C,  but fairly cloudy in first part of night (52 to 72% cloud cover) but gradually clearing towards dawn (37 - 4% cloud cover). Wind was forecast to be moderate (20 mph), and it was not expected that conditions would be suitable for an observing session. In the event conditions were less windy that expected and after seeing sky clearing at 01:00 - 01:30 a session was initiated via AutoStart around 01:30. Cloud unfortunately developed around 02:30 which persisted till Dawn. Minimum outside temperature was 13.5°C.

Session Event Log

Time     Event Detail 01:21:34 Session Created Live Session Created (2020-09-01 S00803, ImageSaveNum: 803001) 01:21:36   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 01:23:23   Services Started Observatory Services started 01:23:31 Observatory (Auto) Observatory placed in Fully-Automated Mode 01:23:33 Session Monitoring AutoStart monitoring for Live Session opportunity starting between 01:20 & 04:10 01:23:35 Session AutoStarting Session autostarting (01:20) 01:23:37 Session Pending Session pending (2020-09-01) 01:23:39 Session Initiating Session initiating (2020-09-01) 01:23:41   Plan Requested Observing Plan requested from AstroPlan (1.16) 01:23:52   Plan Loaded Observing Plan loaded to queue (2020-09-01 V1 BEST PLAN, Plan ID: 537) 01:24:04   Camera1 Connected SBIG Camera Connected (set point -10°C) 01:24:11   Telescope Connected Telescope Connected (TheSky6) 01:24:22 Session Equilibration Session ready for dome & camera equilibration 01:25:07   Dome Opened Dome opened (opening time 45s) 01:25:10   Equilibration Started Dome Equilibration started 01:27:33   Equilibration Ended Dome Equilibration ended (2.4 mins total) 01:27:35 Session Running Session running 01:27:37   Queue Started Observing Queue started (17 targets selected) 01:28:35       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:32:26       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 01:35:17       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 01:35:20       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 01:37:36       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 01:38:01       Focusing Failed Foc2 Focusing Check Failed 01:38:04     Target Started (1/17) Target started (1/17, GCVS Z And) 01:43:27     Target Completed Target partially completed (1/17, GCVS Z And) 01:43:29     Target Started (2/17) Target started (2/17, GCVS HH And) 01:45:39       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:48:57       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 01:50:37     Target Completed Target completed (2/17, GCVS HH And) 01:50:39     Target Started (3/17) Target started (3/17, WDS GRB 34) 01:52:48       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:55:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:57:30     Target Completed Target completed (3/17, WDS GRB 34) 01:57:33     Target Started (4/17) Target started (4/17, Berkeley 63) 02:00:09       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:02:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 02:08:27     Target Completed Target completed (4/17, Berkeley 63) 02:08:29     Target Started (5/17) Target started (5/17, GCVS S Cyg) 02:10:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:13:17       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 02:22:54     Target Completed Target completed (5/17, GCVS S Cyg) 02:22:56     Target Started (6/17) Target started (6/17, GCVS SS Cyg) 02:24:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:27:15       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 02:30:46     Target Completed Target completed (6/17, GCVS SS Cyg) 02:30:59   SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 02:31:02   Queue Paused Queue paused for SoftSuspend 02:31:04 Session Suspended Session suspended 02:31:49   Dome Closed Dome closed (closing time 44s) 02:43:54     Target Cancelled Target cancelled (7/17, 61 Cyg) due to cloud 02:53:14     Target Cancelled Target cancelled (8/17, GCVS BL Lac) due to cloud 03:03:52     Target Cancelled Target cancelled (9/17, GCVS DY Per) due to cloud 03:12:50     Target Cancelled Target cancelled (10/17, GCVS CI Cyg) due to other condition 03:21:15     Target Cancelled Target cancelled (11/17, GCVS RX And) due to cloud 03:34:01     Target Cancelled Target cancelled (12/17, GCVS U And) due to cloud 03:46:42     Target Cancelled Target cancelled (13/17, GCVS TT Ari) due to cloud 03:57:59     Target Cancelled Target cancelled (14/17, GSC 1224:29) due to cloud 04:06:35     Target Cancelled Target cancelled (15/17, GCVS GK Per) due to cloud 04:25:50     Target Cancelled Target cancelled (16/17, GCVS CM Tau) due to cloud 04:47:09     Target Cancelled Target cancelled (17/17, GCVS RR Tau) due to cloud 04:47:14   Queue Completed Job Queue completed 04:47:19 Session Closing Session closing 04:47:24   Dome Closed Dome already closed (closed at 02:31, closing time 44s) 04:48:36   Dome Park Aborted Dome Park aborted (0s, Az=90.1degs) 04:49:26   Telescope Parked Telescope parked (parking time 45s) 04:49:57   Telescope Switched Off Telescope Power has been switched off via UPB Powerbox. 04:50:45   Services Stopped Night Services stopped 04:50:47 Session Housekeeping Housekeeping Started (Cleanup FITS, Create Fits Summary, Transfer Files) 04:50:49 Session Finished Session Finished

Session Alerts

Time     Alert Detail 04:48:36 Dome Failed To Park Parking aborted after 3 mins, Rotation Drive wheels are likely to be slipping (Dome at Az 90.1 degs)

Back to Top

Operational Issues (2020-09-01, S803)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (7)
• Continuous Improvement (4)

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Problem starting Virtual Weather Station (AllSky/Weather Computer).   Prior to session there were issues trying to start Virtual Weather Station (vws.exe).  The program would ask for confirmation of language (English), before recommending that program needs to be run as Administrator, before closing.  When run as Administrator the program gave the same messages and shut down again.  A computer restart didn't fix the problem.  Problem might have been caused as a side effect of looking at Task Scheduler and accidently leaving the LaunchVws task 'open' when trying to start Vws program.   Whatever the cause the problem seemed to be caused by some corruption of the program or its registry settings.  Attempting to reinstall Virtual Weather Station over itself couldn't be achieved (Program Install wouldn't recognise that an installation was required). In the end the program was uninstalled and then re-installled.   The specification of existing vws charts were unfortunately lost, but the program managed to pickup the existing dbase.csv file and data was picked up ok by AstroWeather program and passed on to the Observatory Computer ok to allow session to be carried out normally.  The only impact was that vws charts on the website weren't updated . These will require the re-creation of charts in vws (on either the current AllSky/Weather computer or the new replacement computer (pending) ). 
  Resolved 2020-09-01  (AllSky/Weather Computer)
   
• Foc2 Check Focus Frames didn't produce any FWHM values.   All 3 focus frames taking as part of post-focusing focus check failed to produce a FWHM measurement.  Check Frames weren't saved to file by AstroShCap and therefore they couldn't be examined to see if a star was present or not. Problem occured at ~01:37.  AstroMain regular log file didn't show any errors, but the file path (C:\Data\ZWO Imaging\SharpCap\2020-08-31 S00802\FOCUS\Focus_02_8610.fits) points to preceeding session folder and not the current folder !   AstroShCap report file lists the 3 Check Focus Check Frames  (all Focus_02_8610.fits), but none of these files appears to have been saved.   AstroShCap's log files indicates that LogFocus Frame successfully saved to C:\Data\ZWO Imaging\SharpCap\2020-08-31 S00802\FOCUS\Focus_02_8610.fits . The save folder (2020-08-31 S00802) is unexpected.    Checking the single fts image Focus_02_8610.fits (from 3rd check frame) shows that it although it contains data (variation in pixel values)it does contain any star object, which explains why AstroMain routine couldn't get a FWHM measurement.  AllSky Images taken at this time suggest the passage of a small cloud over the Focus Star Field at around this time, but it doesn't seem at all thick enough to hide the star from view The AstroShCap report shows that the 3 check frames are preceeded by a   ' 14/14     8473     --     --  Fail'  line which is out of place.  It is propsed to add a thread.sleep line to ensure that ShCap's FWHM Monitor (for profile) is fully completed/closed before FHWM Monitor (for focus check) is begun and to ensure check focus frames are uniquely saved to file.   It turned out that SharpCap crashed (or partially crashed) during this time with a  System.InvalideOperationException (Frame delivered twice) error.
  Closed 2019-09-02 (AstroMain / AstroShCap)
   
• Foc2 Focusing at start of session didn't include a precursive wide focus search. It would seem that Foc2 wide option was turned off during previous session and hadn't been turned back on my user.  AutoStart should ensure wide search is on.
  Fixed 2020-09-02 (AstroMain 3.28.3)
   
• Misleading 'Dome Failed to Park' Alert. Alert produced whilst closing the session to say that 'Parking aborted after 3 mins, Rotation Drive wheels are likely to be slipping (Dome at Az 90.1 degs)'. The final Slew to Park Azimuth (090 deg) appears to have been largely normal (71s to slew from 253.5deg, i.e. 2.3 deg/s), but as the slew didn't reach 90.0 deg after 3 minutes it produced the alert, and aborted the final 'Park'.  Problem is not an issue with a slipping drive , but an anomaly within either the Pulsar Dome Rotation Drive Unit, the Pulsar Dome Driver or DeviceHub , which leads to the Dome considering itself at Park when it is at 90.1 deg (rather than the official Park Azimuth of 90.0 degs).   Code to be altered to record a note that scope is Parked at 90.1 deg, but not produce the misleading Alert.
  Fixed 2020-09-02 (AstroMain 3.28.3)
   
• 'Current Session' Web Page has a long section of overbolden text.   Starting from 'Most Recent Targets' section heading the web page has a long section of overbolden text (normal text is bold, headers are double bold).  This is most-likely due to unbalanced / unclosed bold or strong tag.
  Fixed 2020-09-02 (Website)
   
• SharpCap crashed with Exception Message 'System.InvalideOperationException, Frame delivered twice, Exception message had Date/Time 2020-09-02 00:37:38 and wasn't noticed until the following day. AstroShCap wasn't directly affected and continued to be responsive. It is believed this happened at 01:37:38 local time and corresponds to the problem with Foc2 Focus Check Frames (see above). A 3s delay is added prior to calling CheckFocus_Foc2 to allow AstroShCap processes to complete, before starting new process.
  Closed 2020-09-02 pending any future re-occurance  (Website)
   
• After session was suspended at 02:31  AllSky '_Scope' pictures were only recorded on AllSky Computer up to 03:21:28.' _Scope' pictures should have been recorded at start / end times for each plan target until end of job queue / end of session at 04:47. It is presumed this happen because 'Scope/Target Name remained as "Suspended" all this time and therefore didn't trigger a picture save even though Target 0 was changing as the queue moved onto each plan Target in turn.
  Fixed 2020-09-02   (AstroAllSky 3.6.1 )

Continuous Improvement

• Foc2 Check Focus Frames taken with ShCap should be uniquely saved to file (.fts) . Frames should be suffixed as '_check.  and  further suffixed with the check number (1,2,3 etc).   Currently the last check frame will overwrite the first two frames and might overwrite a profile frame if one happened to exist at the best focus position. New flag bFocusProfileCheck to indicate if Focus Check is active or not in AstroMain. New local variable (framecount) in AstroShCap.
  Done 2020-09-02 (AstroMain 3.28.3 & AstroShCap 1.2.24)
   
• AstroShCap should start new report & log files if the program isn't shut between sessions but is 'reused' for a new session.
  Done 2020-09-02 (AstroShCap 1.2.24)
   
• Focusing Profile start time/duration should be reset following completion of wide profile and before starting a standard profile. Profile 1 is shown as duration 6.8 minutes, whilst it should really show 2.9 minutes (6.8 minutes minus 3.9 minutes for Profile 1 Wide)
  Done 2020-09-02 (AstroMain 3.28.3)
   
• Insert Thread.Sleep between finishing Foc2 Profile and taking Foc2 Focus Check Frames.  This is a precautionary fix that might prevent System.InvalideOperationException, Frame delivered twice problem that prevented Foc2 Check Frames from being successfully obtained. A 3s delay is added prior to calling CheckFocus_Foc2.
  Done 2020-09-02 (AstroMain 3.28.3)

[ Prev | Next ]

Back to Top

Pulsar Dome - Corroded Home Magnet

After encountering some problems with relaibly performing recalibration of the Pulsar Dome, the 'Home' magnet which is using by dome controller to recognise when the dome is in it's home position was checked and found to be highly corroded. All the original casing had flaked away with a lot of semi magnetic rusted residue surrounding a central magnetic hub.   Three months later the magnet had corroded even further and dome calibration had stopped working altogether.

For occasions when the dome has lost azimuth precision, a <1 degree error is enough to prevent the two halves of the induction charger to align sufficiently well to allow effective recharging of the shutter unit battery, a work around has been discovered when after rotating the dome to the park position and with the two halves of the induction charger in alignment the ASCOM SyncToAzmiuth command can be used to reset the dome to the park azimuth (090 deg in case of my observatory)

Photo of corroded home magnet, 2020-09-01 (Magnet is about 2 years old)

[ Larger Image ]

Back to Top