David's Astronomy Pages
Notes - Session 1278 (2024-11-29)

 
Bullet Session Aims & Highlights
 - Observing Result
 - Night Summary Plot
 - Session Event Log
Bullet Operational Issues
  - Critical Issues (0),  Major Issues (0),  Minor Issues (2),  Small Defects (13),  Continuous Improvement (17)
Bullet Images from 2024-11-29 >>         
Bullet ASCOM - Platform 7 Update 2, including DH 7.0.2
   
2024-12-02
Bullet MeadeGeneric 1.3.11.512 (Test)
   
2024-12-04
Bullet DeviceHub 7.0.3-RC2
Bullet Dome Slaving - Anomalous Dome Slew Issue Finally Resolved ?  
   
   

Session Aims & Highlights (2024-11-29)

Main aims

  1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
  2. Dome Slewing. Check dome slewing performance following adjustment to rotation driver tension on 2024-11-28.

 Equipment & Software

Highlights

Notes

Summary Plots & Logs

Observing Plan
Image
  
Observing Result
Image
   
Image
 
Dome & Scope Slewing Performance
Image
  
Slew/Centering Performance
Image
  
Guiding Performance
Image
  
Sky Conditions (Locate Frames)
Image 
  
Night Sky Summary Plot
Top axis: Sky Brightness at Zenith (in ADU/s)
Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)
Image   
  
Actual Weather vs Pre-Session Weather Forecast
Image
Image
  
Session Event Log
Time     Event Detail
00:04:25 Session Monitoring AutoStart monitoring for Live Session opportunity between 00:04 & 06:04
00:04:28 Session AutoStarting Session autostarting (00:04)
00:04:49   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.)
00:05:16   Camera1 Connected SBIG Camera connected (Set point -20°C)
00:05:18 Session Created Session Created (Live, 2024-11-29 S01278, ImageSaveNum: 1278001)
00:05:23   Scope Switched On Telescope Power has been switched on via UPB Powerbox.
00:07:18   Services Started Observatory Services started
00:07:26 Observatory (Auto) Observatory placed in Fully-Automated Mode
00:07:29 Session Pending Session pending (2024-11-29)
00:07:31 Session Initiating Session initiating (2024-11-29)
00:07:40   Camera1 Connected SBIG Camera connected (Set point -15°C)
00:07:47   Plan Requested Observing Plan requested from AstroPlan (1.42.5)
00:08:23   Plan Loaded Observing Plan loaded to queue (Plan ID: 1061)
00:09:04   Telescope Connected Telescope connected (TheSky6)
00:09:28 Session Equilibration Session ready to Open Dome
00:10:14   Dome Opened Dome opened (Opening time 46s, Zigbee 40s)
00:10:48 Session Running Session running
00:10:51   Queue Started Observing Queue started (21 targets selected)
00:10:54     Target Started (NrZen) Target started (Focus Field 6, HIP 28634)
00:11:39       Dome Unparked Dome unparked
00:14:27       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
00:16:45       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide)
00:18:52       Focusing Completed Foc1 AutoFocus Completed (Profile No 1)
00:19:16       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap)
00:21:03       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide)
00:22:52       Focusing Completed Foc2 AutoFocus Completed (Profile No 2)
00:23:11     Target Completed (NrZen) Target completed (Focus Field 6, HIP 28634)
00:24:15     Target Started (1/21) Target started (1/21, M31 w/Nova M31 2024-11b?)
00:28:38       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S)
00:44:58     Target Completed Target completed (1/21, M31 w/Nova M31 2024-11b?)
00:46:35     Target Started (2/21) Target started (2/21, GCVS RX And)
00:49:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
00:52:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 3)
00:55:36     Target Completed Target completed (2/21, GCVS RX And)
00:55:56     Target Started (3/21) Target started (3/21, M33 w/AT2024abqt)
00:59:31       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S)
01:01:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 4)
01:06:00       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars)
01:12:51   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome)
01:12:53   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud)
01:12:55     Target Aborted (3/21) Target aborted (3/21, M33 w/AT2024abqt) due to cloud
01:12:57   Queue Paused Queue paused for Session Suspension
01:12:59 Session Suspending Session suspending
01:13:41   Dome Closed Dome closed (Closing time 45s, Zigbee 42s)
01:13:42 Session Suspended Session suspended
01:15:11     Target Cancelled Target cancelled (3/21, M33 w/AT2024abqt) due to cloud
01:29:31     Target Cancelled Target cancelled (4/21, AT2024aasc (CV)) due to cloud
01:39:49     Target Cancelled Target cancelled (5/21, GCVS BL Lac) due to cloud
01:49:12     Target Cancelled Target cancelled (6/21, WDS GRB 34) due to cloud
02:08:17     Target Cancelled Target cancelled (7/21, NGC 1275 w/SN2024xav) due to cloud
02:30:37     Target Cancelled Target cancelled (8/21, AT2024accj) due to cloud
02:43:45     Target Cancelled Target cancelled (9/21, GCVS RZ LMi) due to cloud
03:04:59     Target Cancelled Target cancelled (10/21, 29P/Schwassmann-Wachmann) due to cloud
03:18:41     Target Cancelled Target cancelled (11/21, GSC 1224:29) due to cloud
03:37:57     Target Cancelled Target cancelled (12/21, LEDA 1761410 w/SN2023bip) due to cloud
03:59:56     Target Cancelled Target cancelled (13/21, KUG 1208+328 w/SN2024zsr) due to cloud
04:22:16     Target Cancelled Target cancelled (14/21, SN 2024xqt) due to cloud
04:35:42     Target Cancelled Target cancelled (15/21, T CrB) due to cloud
04:55:32     Target Cancelled Target cancelled (16/21, AT2024aart) due to cloud
05:17:52     Target Cancelled Target cancelled (17/21, NGC 5162 w/SN2024aawh) due to cloud
05:40:12     Target Cancelled Target cancelled (18/21, NGC 3389) due to cloud
06:02:32     Target Cancelled Target cancelled (19/21, M99) due to cloud
06:24:32     Target Cancelled Target cancelled (20/21, NGC 4722 w/SN2024ablh) due to cloud
06:50:40     Target Cancelled Target cancelled (21/21, NGC 5235 w/SN2024grb) due to cloud
06:50:44   Queue Completed Job Queue completed
06:50:50 Session Closing Session closing
06:50:55   Dome Closed Dome already closed (closed at 01:13, closing time 45s, zigbee 42s)
06:52:23   Dome Parked Dome parked (parking time 80s), Az: 90.0 deg
06:53:07   Telescope Parked Telescope parked (parking time 40s total)
06:53:31   Telescope State Handbox reads 'Scope parked Turn scope off.'
06:53:54   Telescope Switched Off Telescope Power has been switched off via UPB Switch.
06:55:17   Services Stopped Night Services stopped
06:55:20 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files)
06:55:27     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow)
06:56:13     Dome Find Park found (Best Park Az 90.2°)
06:56:18     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.2°)
06:56:20   Dome Parked Dome parked
06:56:25   Dome Charging Dome is parked and re-charging Ok (27mA)
06:56:27 Session Finished Session Finished
 
Session Alerts & Alarms
Time     Type       Name Detail
00:07:29 Yellow Alert Disk Space Free Space on C:\ Drive (47.26 GB) is less than 50 GB
06:55:22 Yellow Alert Disk Space Free Space on C:\ Drive (46.71 GB) is less than 50 GB
06:56:25 Green Clear Dome Charging Dome is parked and re-charging Ok (27mA)
 

Back to Top


Operational Issues (2024-11-29 S1278)

[ Prev | Next ]

Critical Issues

Major Issues

Minor Issues

Small Defects

Continuous Improvement

[ Prev | Next ]


Fig 1.   Condensation is visible in images from the Observatory's new C325WB Colour Camera
Following rain, some condensation is visible in images from the C325WB Colour Camera.
The persistance of this condensation was monitored and found to dissipate quite quickly.

Image

Fig 2.   Keogram Line Overlay - New AstroColorCam program feature.

Image

[ Prev | Next ]

Back to Top


ASCOM - Platform 7 Update 2, including DH 7.0.2

ASCOM Platform 7 on Observatory Computer was updated to 7.0.2 version today (2024-11-29 ).

This includes a number of fixes and changes since the original platform 7.0.0 & 7.0.1 was released.

Earlier notes on Platform 7 are recorded at ASCOM - Upgrade to Platform 7 (2024-10-16) ASCOM - Platform 7 Update 1 (2024-10-22)  

The following installations were made:
   - AscomPlatform702.4675.exe

The 7.0.2 Updates includes the following fixes:

Installation Notes:

Checks:

Update 2024-12-03  (7.0.3 RC1)

Observatory Computer was updated to Platform 7 Update 3 RC1 in order to pick up DeviceHub 7.0.3-rc1.4685 which includes a fix for the incorrect PollScopeTask behaviour during early part of a telescope slew where it was getting Slewing value from DH's cache, rather than getting it directly from the telescope driver.    This was successfully tested and appears to have resolved the earlier anomalous slaved dome behaviour issue,

Update 2024-12-04  (7.0.3 RC2)

Observatory Computer was updated to Platform 7 Update 3 RC2 in order to pick up DeviceHub 7.0.3-rc1.4692 which includes additonal logging to support confirmation of the fix for the incorrect PollScopeTask behaviour during early part of a telescope slew.  This was successfully tested and it was confirmed that the change made is successful (see Notes - DeviceHub 7.0.3-RC2 (2024-12-04)

7.0.3. RC2 will be used in future live sessions, pending an official release of 7.0.3 update.

DeviceHub is now being run with the default activity log file size (125000) , rather than a ten-fold size (1250000) that was used with DH 6.6, as it appears to resolve a problem whereby the DeviceHub Interface would freeze up at some point when the Activity Log window was being used.

(although telescope/dome slewing could still be accomplished whilst the DH interface was frozen, it prevented clients changing the Dome Slaving flag and would cause clients to freeze when they attempted to disconnect, which then required stopping/killing DeviceHub and other observatory software in order to regain control of the Telescope/Dome in order to finish parking operations).

Back to Top


2024-12-02


MeadeGeneric 1.3.11.512 (Test)

A series of test versions of the MeadeGeneric driver (1.3.11.509 to 1.3.11.512) was installed on the observatory computer and tested between 2024-11-19 & 2024-12-01, that aimed to resolve an issue whereby the driver wasn't return Slewing=True immediately after a call to SlewToCoordinatesAsync, which would then occasionally cause DeviceHub's PollScopeTask to cancel the telescope's 'Slewing in Progress' state, leading to anomalous slaved dome slewing.

Previously the driver would return Slewing=False until the telescope itself began slewing, but this is not the expectation or required behaviour of an ASCOM driver.

A number of test versions were necessary to iron out bugs and issues involved with the change before they were finnally resolved and the change in final test version 1.3.1.11.512 was accepted.

The change to the driver, although necessary, didn't by itself fully resolve the anomalous slave dome slewing that was seen on some telescope slews. The issue was only finally resolved by a new test version of DeviceHub (7.0.3-RC1. 4685 ) on 2024-12-03.

The change in 1.3.11.512 will be incorporated in an official 1.3.11 update in due course.

The link  https://bitbucket.org/cjdskunkworks/meadeautostar497/wiki/Release%20History  will be monitored to show when the official update is released.

Update 2024-12-14
Whilst the combination of MeadeGeneric driver 1.3.11.512 and DeviceHub 7.0.3-rc2.4692 have significantly reduce the issue of anomalous slave dome behaviour, 1 of 26 slews conducted during session S1283 (2024-12-13) contained an anomlous slew at 05:35 in which DH cancelled the 'Slewing in Progress' state shortly after requesting telescope slew.  A timeline based on AstroMain, DeviceHub and MeadeGeneric logs showed that MeadeGeneric, after initially returning Slewing=True (at 05:35:11.711), then momentarily returns Slewing=False (at 05:35:11.810), before continuing to again return Slewing=True (at 05:35:11.820) and for the remainder of slew. The problem is that DeviceHub PollScopeTask sees Slewing=False at 05:35:11.811 and cancels the telescope's 'Slew in progress' state, leading to anomalous Slave Dome Behaviour. 

Log file from the case were forwarded to Colin Dawson via Discord, however it was immediately clear what's going on to cause driver to unexpectedly return Slewing=False.
 

Update 2024-12-20
A new test version of MeadeGeneric driver (1.3.11.514) was installed on the observatory computer today (2024-12-16) which puts out more information to the log file. It will used during the next couple of live sessions in the hope that it captures a further case where driver momentarily returns Slewing=False during early part of the slew operation, that can be used to identify the source of the problem.

The new version of the driver was used in the next two live sessions (S1284-S1285) and results reviewed on 2024-12-20.  This show that in 1 out 54 slews made the MeadeGeneric Driver unexpectedly returned Slewing=False in response's to DeviceHub Initial PollScopeTask causing DH to quickly cancel its 'Slewing In Progress' state session. Details have been posted on Discord.

Back to Top


2024-12-04


DeviceHub 7.0.3-RC2

Observatory Computer was updated to ASCOM Platform 7 Update 3 RC2 today 2024-12-04 in order to pick up DeviceHub 7.0.3-rc2.4692 which includes additonal logging to support confirmation of the fix for the incorrect PollScopeTask behaviour during early part of a telescope slew.

This followed the earlier update to Platform 7 Update 3 RC1 on 2024-12-03 in order to pick up DeviceHub 7.0.3-rc1.4685 which includes a fix for the incorrect PollScopeTask behaviour during early part of a telescope slew where it was getting Slewing value from DH's cache (still False), rather than getting it directly from the telescope driver (now True). 

The two versions  were both successfully tested and it was confirmed that the change made in 7.0.3 RC1/RC2 is successful.

Earlier notes on Platform 7 are recorded at ASCOM - Upgrade to Platform 7 (2024-10-16) ASCOM - Platform 7 Update 1 (2024-10-22)  

Checks:

Notes:  DeviceHub is now being run with the default activity log file size (125000) , rather than a ten-fold size (1250000) that walue as used with DH 6.6, as it appears to resolve a problem whereby the DeviceHub Interface would freeze up at some point when the Activity Log window was being used.

(although telescope/dome slewing could still be accomplished whilst the DH interface was frozen, it prevented clients changing the Dome Slaving flag and would cause clients to freeze when they attempted to disconnect, which then required stopping/killing DeviceHub and other observatory software in order to regain control of the Telescope/Dome in order to finish parking operations).

Update 2024-12-14
Whilst the combination of MeadeGeneric driver 1.3.11.512 and DeviceHub 7.0.3-rc2.4692 have significantly reduce the issue of anomalous slave dome behaviour, 1 of 26 slews conducted during session S1283 (2024-12-13) contained an anomlous slaved dome behaviour at 05:35 in which DH cancelled the 'Slewing in Progress' state shortly after requesting telescope slew.   Whilst not caused by DeviceHub, the case exposed an issue with DeviceHub's Dome Position Recalculation.

After the dome arrived at the Target Azimuth (59.4°)  DH performed a Dome position recalculation at 05:35:27.749 due to periodic timer expiration, determined that the dome azimuth (59.40°) was away from the 'target' azimuth 75.70°  (where the telescope supposedly was) and requested a Dome. SlewToAzimuth (75.70°).  

However at that time the telescope was settling at its Target Destination (equivalent to Dome Az 59.4°) and had a Telescope Az: 58.55°, Alt: 21.03°,  which should have led if anything to a minor dome slew 59.4°  to c. 58.6° +/-  or no slew at all and not a large slew back to Az 75.70°, after which the dome then slewed back to 59.5°, delaying forward operations.

It would seem that DH's Dome Position Recalculation is using cached values for either Telescope Ra/Dec or Telescope's TargetRa/TargetDec.
The latter issue has been sent to the ASCOM Team via ASCOM Talk forum (https://ascomtalk.groups.io/g/Help/message/47784) 

Update 2024-12-17
A new version of DeviceHub ( 7.0.3-rc23.4694) have been provided from Peter Simpson which contains a fix for the issue identified on 2024-12-14. Some daytime tests today (2024-12-17) using the new DH version along with MeadeGeneric 1.3.11-514. Around 10 slews were made in total, most of these were with the dome slaved to the scope, with the telescope arriving at the target first and some with the dome arriving first.  Some tests were also made with the dome initially not slaved & then either turning slaving on during the telescope slew,  or after the telescope slew.   I didn't see anything bad happen, and I didn't see any anomalous slaved dome behaviour.    Since issues can sometimes only present with certain timing interactions (dependant on the precise timing of polling, tasks and  arrival of data from a real driver etc, it is too soon to say that the issue is resolved.  The new version will be used in the next two live session in order to get results from a further 50+ slews. 

Update 2024-12-20
The new DH 7.0.3-rc23.4694 version was used in the next two live sessions (S1284-S1285) and results reviewed on 2024-12-20 demonstrated that the Dome Slaving issue has been successfully fixed. In the 54 telescope slew made with dome slaving enabled there 1 slew in which the telescope driver returned an unexpected Slewing=False value in response to DH’s Initial PollScopeTask GetSlewing call, leading to DH cancelling the ‘Slewing In Progress State’ (1 in 54 is a much lower frequency that what it originally was, but still indicates a residual issue with the telescope driver).   

But it was good news on the DH dome slaving front.  The dome arrived at the target first (2-3s before the telescope did) and DH.Dome performed a dome position recalculation and determined that the dome’s  position was ok and that no dome slew was needed.   (Previously it was commanding the dome to slew off to an inappropriate position before then slewing back again). 
(https://ascomtalk.groups.io/g/Help/message/47806).

Based on this successful result and earlier daytime tests on 2024-12-17 the earlier dome slaving problem is now considered as fixed. 

Back to Top


Dome Slaving - Anomalous Dome Slew Issue Finally Resolved ?

Though combination of fixes/updates to MeadeGeneric Telescope Driver and to DeviceHub the long standing issue with dome slaving behaviour has finally be resolved. This was anomalous behaviour in which occasional where the slaved dome initiallys slew correctly to the target azimuth, but instead of waiting for the telescope to arrive and finish its slew, the dome slew to 1 or 2 position along the path that the telescope is slewing before eventually arriving again at the Target position, delaying the whole slew process.

MeadeGeneric 1.3.11.512 finally resolves part of the issue whereby the driver wasn't return Slewing=True immediately after a call to SlewToCoordinatesAsync, which would then occasionally cause DeviceHub's PollScopeTask to cancel the telescope's 'Slewing in Progress' state, leading to anomalous slaved dome slewing.

DeviceHub 7.0.3-rc1.4692 & DeviceHub 7.0.3-rc2.4685  resolves the other part of the issue whereby during the early part of a telescope slew DeviceHub's PollScopeTask behaviour was getting Slewing value from DH's cache (still False), rather than getting it directly from the telescope driver (now True), causing the cancellation of the telescope's 'Slewing in Progress' state, leading to anomalous slaved dome slewing.

After testing the two updates together during testing session on 2024-12-03, the two updates were again tested together during a live session S1279 (2024-12-05) and Slaved Dome operations were normal with no anomalous slaved dome slews.
 

Update 2024-12-14
Whilst the combination of MeadeGeneric driver 1.3.11.512 and DeviceHub 7.0.3-rc2.4692 have significantly reduce the issue of anomalous slave dome behaviour, 1 of 26 slews conducted during session S1283 (2024-12-13) contained an anomlous slaved dome behaviour at 05:35 in which DH cancelled the 'Slewing in Progress' state shortly after requesting telescope slew., and the dome after arriving at the target (59.4°) & whilst the telescope was settling at the target, made a large slew back to Az 75.70°, after which the dome then slewed back to 59.5°, delaying forward operations, when it should have made only a very minor slew or made no slew at all

A timeline based on AstroMain, DeviceHub and MeadeGeneric logs showed that MeadeGeneric, after initially returning Slewing=True (at 05:35:11.711), then momentarily returns Slewing=False (at 05:35:11.810), before continuing to again return Slewing=True (at 05:35:11.820) and for the remainder of slew. The problem is that DeviceHub PollScopeTask sees Slewing=False at 05:35:11.811 and cancels the telescope's 'Slew in progress' state, leading to anomalous Slave Dome Behaviour.    Log file from the case were forwarded to Colin Dawson via Discord, however it was immediately clear what's going on to cause driver to unexpectedly return Slewing=False (this will be investigated further using a new MeadeGeneric version (1.3.11.514) which collects more log information.

Analysis of logs showed that after the dome arrived at the Target Azimuth (59.4°)  DH performed a Dome position recalculation at 05:35:27.749 due to periodic timer expiration, determined that the dome azimuth (59.40°) was away from the 'target' azimuth 75.70°  (where the telescope supposedly was) and requested a Dome. SlewToAzimuth (75.70°).  

However at that time the telescope was settling at its Target Destination (equivalent to Dome Az 59.4°) and had a Telescope Az: 58.55°, Alt: 21.03°,  which should have led if anything to a minor dome slew 59.4°  to c. 58.6° +/-  or no slew at all.  It would seem that DH's Dome Position Recalculation is using cached values for either Telescope Ra/Dec or Telescope's TargetRa/TargetDec. The issue has been sent to the ASCOM Team via ASCOM Talk forum (https://ascomtalk.groups.io/g/Help/message/47784) 

Update 2024-12-20
The new DH 7.0.3-rc23.4694 version was used in the two live sessions (S1284-S1285) and results reviewed on 2024-12-20 demonstrated that the Dome Slaving issue has been successfully fixed.

 In the 54 telescope slew made with dome slaving enabled there 1 slew in which the telescope driver returned an unexpected Slewing=False value in response to DH’s Initial PollScopeTask GetSlewing call, leading to DH cancelling the ‘Slewing In Progress State’ (1 in 54 is a much lower frequency that what it originally was, but still indicates a residual issue with the telescope driver).    But it was good news on the DH dome slaving front.  The dome arrived at the target first (2-3s before the telescope did) and DH.Dome performed a dome position recalculation and determined that the dome’s  position was ok and that no dome slew was needed.   (Previously it was commanding the dome to slew off to an inappropriate position before then slewing back again).  Based on this successful result and earlier daytime tests on 2024-12-17 the earlier dome slaving problem is now considered as fixed  (https://ascomtalk.groups.io/g/Help/message/47806).

Back to Top