David's Astronomy Pages Notes - Session 1052 (2022-11-01)

Notes (S1051)

Notes Main

Home Page

Notes (S1053)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (2),  Minor Issues (14),  Small Defects (1),  Continuous Improvement (2)
	Images from 2022-11-01 >>        [ Local Files >> ]

Session Aims & Highlights (2022-11-01)

Main aims

1. AstroMain.  Check new AstroMain version (3.56.7) for any issues introduced by recent changes and additions.
2. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
3. CCDSoft / SBIG : Understand issues with CCDSoft not responding, SBIG Issues, AstroMain ObsMonitor lockups.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, DeviceHub 6.6.0.16,  MeadeGeneric 1.3.5.414, UPB 1.5, ASCOM 6.6
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.11dev2
   
• AstroMain 3.56.7  AstroPlan 1.32.6,   AstroShCap 1.3.12, AstroGuard 1.10.1
  AstroVOE 1.12  AstroSN 1.8.6,  AstroProtect 1.7,  AstroMove 1.9.4
  (AstroWeather 1.19.2, AstroAllSky 3.17.1,  AstroObsCam 1.10.1, AstroLaunch 1.10.3

Highlights

• Targets. Only 5 out of 19 planned targets where successfully acquired due to cloud (
• AstroMain. A number of teething issues related to new or recently modified code. 
• CCDSoft/SBIG Camera/AstroMain. Various issues with exceptions from SBIG Camera

Notes:

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)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 23:27:19 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:27 & 05:18 23:27:20 Session AutoStarting Session autostarting (23:27) 23:27:40   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 23:27:47   SBIG Camera Reset SBIG Camera being power-cycled 23:28:17 Session Created Session Created (Live, 2022-11-01 S01052, ImageSaveNum: 1052001) 23:28:20   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 23:30:00   Services Started Observatory Services started 23:30:07 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:30:10 Session Pending Session pending (2022-11-01) 23:30:12 Session Initiating Session initiating (2022-11-01) 23:30:14   Plan Requested Observing Plan requested from AstroPlan (1.32.6) 23:31:06   Plan Loaded Observing Plan loaded to queue (Plan ID: 814) 23:31:30   Camera1 Connected SBIG Camera connected (set point -15°C) 23:31:37   Telescope Connected Telescope connected (TheSky6) 23:32:01 Session Equilibration Session ready to Open Dome 23:32:46   Dome Opened Dome opened (opening time 45s) 23:33:16 Session Running Session running 23:33:19   Queue Started Observing Queue started (19 targets selected) 23:33:22     Target Started (NrZen) Target started (Focus Field 2, HIP 9508) 23:33:35   Dome Unparked Dome unparked 23:38:23       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:40:58       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 23:42:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 23:43:01       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 23:45:07       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 23:46:49       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 23:47:06     Target Completed (NrZen) Target completed (Focus Field 2, HIP 9508) 23:47:10     Target Started (1/19) Target started (1/19, AT2022whd (CV)) 23:50:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:52:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 23:58:16     Target Completed Target completed (1/19, AT2022whd (CV)) 23:58:42     Target Started (2/19) Target started (2/19, Jupiter) 00:01:23       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 00:05:43     Target Completed Target completed (2/19, Jupiter) 00:10:08     Target Started (3/19) Target started (3/19, NGC 873 w/SN2022xjk) 00:14:57       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:30:59     Target Completed Target completed (3/19, NGC 873 w/SN2022xjk) 00:32:08     Target Started (4/19) Target started (4/19, NGC 946 w/SN2022yid) 00:36:03       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:38:47   SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 00:52:22     Target Completed Target completed (4/19, NGC 946 w/SN2022yid) 00:52:24   Queue Paused Queue paused for Session Suspension 00:52:26 Session Suspended Session suspended 00:53:13   Dome Closed Dome closed (closing time 50s) 00:58:42 Session Resuming Session resuming 00:59:28   Dome Opened Dome opened (opening time 46s) 00:59:31 Session Running Session running 00:59:33   Queue Resumed Observing Queue resumed 00:59:34     Target Started (5/19) Target started (5/19, NGC 7448 w/SN2022wsp) 01:18:24     Target Completed Target partially completed (5/19, NGC 7448 w/SN2022wsp) 01:18:28     Target Started (6/19) Target started (6/19, NGC 7495 w/SN2022ubb) 01:23:17       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:25:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:37:58   SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 01:41:17     Target Completed Target completed (6/19, NGC 7495 w/SN2022ubb) 01:41:19   Queue Paused Queue paused for Session Suspension 01:41:21 Session Suspended Session suspended 01:42:10   Dome Closed Dome closed (closing time 51s) 01:57:04     Target Cancelled Target cancelled (7/19, NGC 5894 w/SN2022pgf) due to cloud 02:19:04     Target Cancelled Target cancelled (8/19, AT2022vxe) due to cloud 02:31:10     Target Cancelled Target cancelled (9/19, GCVS BL Lac) due to cloud 02:43:10     Target Cancelled Target cancelled (10/19, AT2022why) due to rain 03:03:10     Target Cancelled Target cancelled (11/19, UGC 1514 w/SN2022ovq) due to cloud 03:25:10     Target Cancelled Target cancelled (12/19, UGC 2508 w/AT2022trp) due to cloud 03:47:11     Target Cancelled Target cancelled (13/19, AT2022tqu) due to cloud 04:08:09 Program Resumed AstroMain UI resumed again at 04:08 after 6s 04:09:10     Target Cancelled Target cancelled (14/19, UGC 3923 w/SN2022rqc) due to cloud 04:10:30 Session Resuming Session resuming 04:11:38   Dome Opened Dome opened (opening time 68s) 04:11:41 Session Running Session running 04:11:43   Queue Resumed Observing Queue resumed 04:12:14     Target Started (15/19) Target started (15/19, GCVS SY Cnc) 04:14:39     Dome Slew Dome slew held up at Az. 246.4, 222.3, 221.7° (Total delay 63s) 04:17:27       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 04:20:43     Target Completed Target completed (15/19, GCVS SY Cnc) 04:21:41     Target Started (16/19) Target started (16/19, C/2020 V2 (ZTF)) 04:22:16   Dome Unparked Dome unparked 04:23:53     Dome Slew Dome slew held up at Az. 88.6, 66.3° (Total delay 78s) 04:26:23       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 04:45:00     Target Completed Target completed (16/19, C/2020 V2 (ZTF)) 04:45:04     Target Started (17/19) Target started (17/19, NGC 3938 w/SN2022xlp) 04:48:08       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 05:04:16     Target Completed Target completed (17/19, NGC 3938 w/SN2022xlp) 05:05:42 TheSkyScopeMonitor Frozen TheSkyScopeMonitor appears to be frozen at around 08:05 05:06:01     Target Started (18/19) Target started (18/19, UGC 6983 w/SN2022pru) 05:09:01       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 05:25:36     Target Completed Target completed (18/19, UGC 6983 w/SN2022pru) 05:28:01     Target Started (19/19) Target started (19/19, IC 901 w/AT2022sgr) 05:28:24   Dome Unparked Dome unparked 05:31:57       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 05:46:03   SBIG Camera Take Image failed, Error Code 219 (Command in progress) 05:46:36     Target Failed Target failed due to other condition - SbigCamera (19/19, IC 901 w/AT2022sgr) 05:46:39   Queue Completed Job Queue completed 05:46:48 Session Closing Session closing 05:47:38   Dome Closed Dome closed (closing time 45s) 05:47:56   Dome Parked Dome parked (parking time 11s), Az: 90.0 deg 05:49:18   Telescope Parked Telescope parked (parking time 79s) 05:49:33   Telescope State Scope parked Turn scope off. (Handbox) 05:50:04   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 05:50:20 Program Hung AstroMain's Obs.Manager hung whiilst Closing CCD Camera during Closing Stage 8 05:54:18 Obs.Monitor Frozen Obs.Monitor appears to be frozen at around 05:54 in section Monitor Camera1 08:03:50 User Intervention User Intervention to Restart CCDSoft in order to unlock Obs.Manager 08:03:51   CCDSoft Restarting CCDSoft being restarted (user action) 08:04:54   CCDSoft Restarting CCDSoft being restarted (user action) 08:04:57   SBIG Camera Reset SBIG Camera being power-cycled 08:05:00   Services Stopped Night Services stopped 08:05:02 Session Housekeeping Session Housekeeping started (Create Fits Summary, Transfer Files) 08:05:04   SBIG Camera Reset SBIG Camera being power-cycled 08:05:28 Session Finished Session Finished 08:05:42   Camera1 Connected SBIG Camera connected (set point -20°C)

Session Alerts

Time     Alert Detail 01:18:34 Anomalous Dome Slew Dome slew resumed at Az 263.2° (T+1.6s) 05:46:03 SBIG Camera Alert Take Image failed, Error Code 219 (Command in progress) 05:54:48 Obs.Monitor Obs.Monitor appears to be frozen in section Monitor Camera1 (last cycle at 05:54:18) 08:04:55 Obs.Monitor Obs.Monitor has resumed again after 130.6 mins 08:07:25 TheSkyScope Monitor TheSkyScopeMonitor appears to be frozen (last cycle at 08:05:42)

Back to Top

Operational Issues (2022-11-01, S1052)

• Critical Issues (0)
• Major Issues (2)
• Minor Issues (14)
• Small Defects (1)
• Continuous Improvement (2)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• Obs.Manager frozen in section Running (00:52) and in section Suspended (00:54). Obs.Overseer reported "Obs.Manager is Frozen in section Running" from 00:52:34 until 00:53:04. And then reported "Obs.Manager is Frozen in section Suspended" from  00:54:35 to 00:59:23.   There were no log messages to indicate that Obs.Manager had resumed again after each episode.  Problem seemed to resolve itself when Session began running again.  Unclear what caused Obs.Manager to freeze.   It is unclear why freezes in excess of 120s during period 00:54:35 to 00:59:23 didn't trigger reporting / resumption messages.   Examining messages suggests that ObsManager was resumed for 10s intervals every 30-35s or so, which explains why the expected message didn't appear.   Closed after review 2022-11-02 and after adding extra code to record resumption of Obs.Manager for freezes > 20s (instead of >120s).
  Resolved itself in-session  2022-11-02 (Session, AstroMain).
   
• Obs.Manager progress stalled whilst in Session Closing stage 8 whilst trying to close-down CCD Camera (05:50).  Due to a non-responsive CCDSoft.Camera a call to disconnect the camera caused Obs.Manager to either lock up or be otherwise unable to make progress within the Closing Session stage. Although Observatory was completely safe by this point , dome closed & parked, telescope parked & turned-off, the lock-up prevented the Session from moving to HouseKeeping and Finished Stages.
  The closure state of the observatory was in initially doubt based on Current Session Page on the website until a visual check of the observatory and remote connection was performed.  The 'stall' was resolved at 08:03 by using the 'Restart CCDSoft' button routine from AstroMain's More/Backdoor Tab.   The report file suggest that the problem occured when Camera.Disconnect was called .
     Close Camera                     2022-11-02 05:50 (Local, GMT)
     Turn off CCD Cooling ...    Ok   Cooling is Off (CCD Cooling)
     Turn off CCD Fan ...        Ok   Fan is Off (CCD Fan)
     Wait for CCD to re-warm...  Ok   -20.0°C (CCD Temperature)
     Wait for CCD to re-warm...  Ok   -20.0°C (CCD Temperature)
     Wait for CCD to re-warm...  Ok   -20.0°C (CCD Temperature)
     Disconnect Camera ...       **   (Continued below)
   > Obs.Overseer Warning Obs.Monitor is frozen (05:54) in section Monitor Camera1
  The underlying cause of the issue is that the CloseDownCamera2() routine (executed as a thread by call to CloseDownCameraByThread in Closing Stage 7) freezes when it tries to call CCDSoft.Camera.Disconnect object. But the principal symptoms (ObsManager progress stalled) is due to the code in Closing Stage 8 which only progresses when the bCloseDownCameraDone flag has been raised (which it can't because CloseDownCamera2 is frozen and can't raise it).  The issue is fixed by setting a time-out for the wait step in Closing Stage 8  so that progress continues if MinutesSince (StartCloseDownCameraTime) is > 4 minutes.
  Fixed  2022-11-02 (AstroMain 3.56.8, CCDSoft.Camera)

Minor Issues

• Foc1FieldsUpdater reported as pending/frozen when it probably isn't (21:57). After newly installing AstroMain 3.56.7 onto the Observatory Computer and starting AstroMain's ObsMonitor services including new Foc1FieldsUpdater, AstroMain's ObsOverseer and ObsMonitor/Foc1FieldsUpdater started indicating that the Foc1FieldsUpdater was pending and then frozen, are then wrote message pairs to the logfile every 5s.
  
    21:58:11.14 | Observatory Overseer Check Foc1FieldsUpdater Alert | Foc1FieldsUpdater is Frozen (125s)
  21:58:11.16 | Observatory Monitor Check Foc1FieldsUpdater Info | Foc1Fields.Updater has resumed (cycle = 125.1s)
  This would seem to be a teething issue. Bug fixed 2022-11-02 (Foc1FieldsCycleTimePoint wasn't being set during each cycle).
  Fixed  2022-11-02 (AstroMain 3.56.8)
   
• AstroMove operation to copy session / night file from Observatory in morning stalled whilst copying session's Analysis folder.   Copying of files to Log folder  seemed to stop at the point of the Session log file which was showing with size 6,415,872 KB (6.1 GB).   It is presumed this was the reason why the operation had stalled or was taking a very long time.   The session log file was moved out of from the session folder on the Observatory Computer and the 'Copy Files from Observatory' restarted. Issue is closed (The reason for the excessively large log file is covered under a separate issue).  Prehaps AstroMove could check file size first and not attempt to copy any files over say 1 GB ?
  Resolved 2022-11-02 (Session, AstroMove)
   
• Session created log file that was 6.1 GB in size.  A session log file was 6.1 GB in size and was so big it stalled AstroMove's operation to move files from Observatory session. Log file is presumed to be filled by excess of log messages "UpdateFoc1Fields (trace) |  Ignored as Camera1 is not currently accessible" which seem to be written out hundreds of times per second whilst bRestartingCCDSoft flag is active. Problem present even after session finished.  Problem is a teething issue following the relocation of the code from RunObsMonitor into the new RunFoc1FieldsUpdater() routine. Bug fixed in AstroMain 3.56.8 (the Foc1FieldsCycleTimePoint wasn't being set during each cycle).
  Fixed  2022-11-02 (AstroMain 3.56.8)
   
• Unable to open session log file.  The session log file ("2022-11-01 S01052 Observatory (run).log") is too large to open in TextPad or NotePad.  Whilst is can be opened in Micropsft Large File Viewer App it isn't easily to overllok the huge number of unwelcome UpdateFoc1Fields (trace) messages or save a cut down version.   A custom routine has been created in AstroMain 3.56.8 called FilterOutLinesFromFile(FilePath as string, TextToSearchFor as string) that can be called in such a circumstance. When routine was run against the session's 6.1 GB log file  51,703,228 lines were removed, 28,921 lines were retained, and the resulting file size dropped to a more normal size of only 3.37 MB.
  Fixed 2022-11-02 (AstroMain 3.56.8)
   
• AstroPlan seemed to stop uploading files to website (00:52). Current Session Page not showing session images & files older than 00:52. AstroPlan seemed to stop uploading files to website at around 00:52 or at somepoint thereafter.  Files relating to Observatory Finishing at 08:05 where not uploaded even though AstroPlan was still running.  AstroPlan was restarted and allowed to make a complete upload of session files, after which Latest Session web page showed the expected images & files. Issue deemed to be resolved/closed.
  Resolved 2022-11-02 (Session, AstroPlan)
   
• Starting AstroMain Session is very slow.  When a new session is created or any previous general session was resumed following a live session, the operation takes a long time and seems to hang for prolonged period whilst CCDSoft is being restarted in order to set a new AutoSave Number (this is done by setting a value in the Registry and needs the CCDSoft application to not be running at the time).   The RestartCCDSoft operation is taking 66s.   Part of the delay is because the call to Disconnect the camera consumes 30s before a time-out condition intervenes allowing the operation to continue. Then there is a delay of 30s whilst the SBIG Camera is power cycled and allowed to initialise including allowing the filter wheel time to reset itself at filter 1. Problem repeatable. Problem solved by starting RestartCCDSoft as a threaded operation.
  Fixed  2022-11-02 (AstroMain 3.56.8)
   
• Obs.Overseer / Obs.Manager are not writing any log message when frozen Obs.Manager thread resumes again  (00:09, 00:14, 00:59). After logged freezes of ObsManager and apparent resumptions the ObsOverseer or Obs.Manager itself isn't logging the fact that Obs.Manager has resumed again. It would be helpful if log shows a message "Obs.Manager has resumed again" to indicate definitively the time when it resumed and how long the freeze was for. Code introduced that will insert 'Obs.Manager has resumed" message for freeze longer than 20s instead of 120s previously. 
  Fixed  2022-11-02 (AstroMain 3.56.8)
   
• Series of 'Switch On Dehumidifier.  Dehumidifier is already on' message were reported every 12s (05:50 to 08:03).  Between 05:50 and 08:03 there were 666 report lines saying that Dehumidifier is already on.
  
   Switch On Dehumidifier.    Ok        Dehumidifier is already on
  
  After ObsMonitor became frozen at 05:54 updating of DeConzDehumidifier() record would have stopped.   It is supposed that the record had .On = False and ManagerDehumidifier() routine believing that the Dehumidifier was off tried to turn on the Dehumidifier with a call to SwitchOnDehumidifier() which then called SwitchDeconzDevice(DeConzDehumidifierID ). After the first call the Dehumidifier was turned on, but this new setting didn't become reflected in the DeConzDehumidifier() record as the ObsMonitor was frozen.  Issue fixed in AstroMain 3.56.8 so that DeConzDehumidifier.On  is set True or False as appropriate following successful calls to SwitchDeconzDevice().   This fix resolves the problem of mutiple report messages but of course doesn't resolve the issue causing ObsMonitor to freeze.
  Fixed 2022-11-02 (AstroMain 3.56.8)
   
• Series of 'TheSkyScopeMonitor has resumed again' message were reported every 5s (08:09+ and 09:00+).  After ObsManager was unlocked up at 08:04 by user intervention and after a new General session (2022-11-02) was started at 09:00 , multiple report lines were written to screen every 5s saying saying
       > TheSkyScopeMonitor   Info    TheSkyScopeMonitor has resumed again (09: 55)
  This is possibily an artefact of the earlier issue with AstroMain's ObsManager. Issue not present after restarting AstroMain.
  Bug fixed in AstroMain 3.56.8 (the flag  bTheSkyScopeReportedAsFrozen wasn't being set to False after reporting resumption of TheSkyScopeMonitor).
  Fixed 2022-11-02 (AstroMain 3.56.8) 
   
• Session Event & Session Alert not being generated when TakeImageAsync() routine times-out waiting for Camera.TakeImage() operation to be completed. During Image 4/5 of Target 19/19, IC 901 w/AT2022sgr) the logfile show that TakeImageAsync() routine recorded that the TakeImage() operation had timed-out (05:45:02). During Image 5/5 the logfile shows an exception from Camera.TakeImage "Command in progress. Error code = 219"  (05:46). The latter event generates a 'SBIG Camera Alert' with description "Take Image failed, Error Code 219 (Command in progress)", but the former (and indeed the most important event) does not.  Issue fixed in AstroMian 3.56.8. 
  Fixed 2022-11-03 (AstroMain 3.56.8)  
   
• Job Queue not highlighting an issue taking last 2 images from final target (05:46). During Image 4/5 of Target 19/19, IC 901 w/AT2022sgr) the logfile show that TakeImageAsync() routine recorded that the TakeImage() operation had timed-out (05:45:02). During Image 5/5 the logfile shows an exception from Camera.TakeImage "Command in progress. Error code = 219"  (05:46). However, the Report file doesn't give any indication of issue against either image, though evidence of a problem is indicated by the reuse of the Image number 01052124 that belonged to Image 3/3, and the target is reported to have failed 'due to 'other condition - SbigCamera'. 
  
    Taking 180s image (C)... Ok    [01052122] (3x3 180s, Full 3x3 180s C, 05:32:15 UT, Sky 55/+30)
  Taking 180s image (C)... Ok    [01052123] (3x3 180s, Full 3x3 180s C, 05:35:20 UT, Sky 64/+37)
  Taking 180s image (C)... Ok    [01052124] (3x3 180s, Full 3x3 180s C, 05:38:26 UT, Sky 78/+48) 
  Taking 180s image (C)... Ok    [01052124] (3x3 180s, Full 3x3 180s C, 05:38:26 UT, Sky 105/+70)
  Taking 180s image (C)... Ok    [01052124] (3x3 180s, Full 3x3 180s C, 05:38:26 UT, Sky 114/+76)
  Target Result:           Fail  Target failed (Due to other condition - SbigCamera)
  The 'date modified' time of 05:46 is suggestive that file has been 'resaved' during post-image processing of Image 4 and Image 5. FITS Header show Date Obs of 05:38:26 which is clearly a lot earlier than last modified time of 05:46:13 (vs file creation time of 05:41:28)
  Fixed 2022-11-03 (AstroMain 3.56.8)  
   
• Obs.Monitor reported as 'Pending in section Refresh Dome Picture'. Obs.Overseer reported 'Obs.Monitor is Pending (7s) in section: Refresh Dome Picture' at 23:42:53 (resumed after 8.5s) . Similar event at 23:58:23 (resumed after 7.8s) and 00:09:00 (resumed after 15.5s).   At around 00:09:05.35, Obs.Overseer reported that "Obs.Manager is Frozen in section When TheSky6 Running" (no message recording resumption ?) and "TheSkyScopeMonitor is Pending (18s)" (which resumed after 18.5s)
  At 00:14:33 Obs.Overseer reported "Obs.Manager is Frozen in section When TheSky6 Running",  "Obs.Monitor is Frozen (17s) in section : Refresh Dome Picture" and "TheSkyScopeMonitor is Pending (19s)".   Investigations inconclusive as to cause.   This might relay to slow-downs in TheSky6 or it might relate to the heavily load writing 6 GB of message to log file.  Proposal is to monitor the next couple of sessions for any repeat instances of the issue. Closed after review on 2022-11-12 following improvements and stability shown in sessions S1057 & S1058.
  Closed after review 2022-11-12 (Session, AstroMain, TheSky6).
   
• Obs.Monitor frozen in section 'Monitor Camera1' (05:54) . After the problem with CCDSoft.Camera during image 4/5 of the final target of the session, the ObsMonitor began to freeze in section 'Monitor Camera 1' for intervals of 10s at a time.  But at 05:54 and about the time that Camera.Disconnect was called in Closing Stage 7/8 the ObsMonitor completely froze up in section 'Monitor Camera1'. Closed after review on 2022-11-12 following improvements and stability shown in sessions S1057 & S1058.
  Closed after review 2022-11-12 (Session, AstroMain, TheSky6).
   
• Exception from Camera.TakeImage "Command in progress. Error code = 219" during final image of session (05:46:03). During Image 5/5 of Target 19/19, IC 901 w/AT2022sgr) the log files show. Problem seemed to have begun during Image 4/5 at around 05:45:02.49 when TakeImageAsync reported that TakeImage() operation had timed-out.  This would have caused the TakeImage thread to be locked until it was cleared by the later manual intervention to RestartCCDSoft() at 08:05 and explained why the call to Camera.TakeImage() failed at 05:46. So after successfully taking 124 images and not slew or centering movement between the Image 3/5 and the failure during Image 4/5 (suggesting that a cable movement /disconnection is unlikely cause) why is CCDSoft.Camera failing ?   After CCDSoft.Camera stopped responding during Image 4/5  the Obs.Monitor became Pending (8s) in section: Monitor Camera1.  This seemed to be a slowing of CCDSoft.Camera response since ObsMonitor resumed after 10s.  This pending/resumed pattern continued until xxx.  Closed after review on 2022-11-12 following improvements and stability shown in sessions S1057 & S1058.
  Closed after review 2022-11-12  (Session, AstroMain, CCDSoft).
   
• Planned images of Jupiter didn't contain the planet / Telescope didn't appear to slew to the commanded location (23:58).  Problem was initially put down to cloud, but following a similar observation/issue in the following session (S1053, 2022-11-03).  Issue investigated (see Investigation - Slewing Discrepency (Jupiter)) and finally understood following a yet further occurance of the issue in session S1057 (2022-11-07), when it was determined that the problem was due to the slew being made explicitly through objScope.SlewToCoordinatesAsync() by passing TPoint coordinate modification rather than being made through TheSky6.Telescope. Jupiter lay close to with RA 0/RA 24 and TheSky6 slewing was explicitly bypassed as a fix to an earlier issue (S827) where DeviceHub rejected a RA value from TheSky6/TPoint becuase it lay just outside the range 0.0 to 24.0. A partial workaround was added in AstroMain 3.57.1 which adds a custom 41' adjustment to the target dDec value when using objScope.SlewToCoordinatesAsync() to slew to Jupiter, thereby roughly replacing the correction that would otherwise be applied by TheSky6/TPoint (current model).  This alllowed the successful centering/imagin of Jupiter during session S1058 (2022-11-12).  A more complete solution has now been provided by the new TeleLink telescope 'driver'.
  Fixed 2022-11-12 (AstroMain 3.57.1) and 2022-11-14 (AstroMain 3.57.2, TeleLink 1.0)

Small Defects

• Problem with the phasing of Report Lines during Park Dome operation. At the end of session whilst running Session Closing procedures the following report lines were issued whilst parking the dome.
  
      Park Dome                      2022-11-02 05:47 (Local, GMT)
    Turn off Dome Slaving... Ok    Slaving is Off
    Slew Dome to Az 90°...
    Turn off Dome Slaving... Ok    Slaving is Off
  Ok Dome at Az 90.0° (Park Position)
  The second 'Turn off Dome Slaving' messages are unexpected and interrupt the reporting of results from the 'Slew Dome to Az 90°' operation.
  They are produced by a call to SetSlavingOff() from within SlewDomeToAzimuth() routine and would only report messages  is objDome.Slaving = true, which shouldn't be the case since the first call to SetSlavingOff() would be expected to successfully set  objDome.Slaved = False.  The ParkDome2 code has been changed to include a 1000ms  delay before calling SlewDomeToAzimuth() as an attempt to ensure that objDome.Slaved has time to be registered by Device Hub.  Proposal is to monitor next couple of sessions for a repeat of this issue, and to then close the issue if there are no further cases. The same problem happened in the following session (S1053, 2022-11-03), showing that there is a real, but unexplained small defect here.  Tracing added to SetSlavingOff() in AstroMain 3.56.10 to measure the time taken for (Get) objDome.Slaved to turn to False after using (Set) objDome.Slaved = False, with a time-out of 8s.  One option would be to to call SetSlavingOff (CallMode.Quiet) and edit SetSlavingOff (() to suppress reporting when Mode is CallMode.Quiet.  Problem didn't occur in sessions S1054 - S1056, suggesting that there was a time-limited glitch operating in  both the S1053 & S1054 sessions or the newly added loop that enquires on the state of objDome.Slaved triggers DeviceHub into giving the correct value.  The issue is closed after review (2022-11-10) but further new sessions will be examined for any reoccurence of the problem.
  Closed after review  2022-11-10 (AstroMain 3.56.8)

• When Restarting CCDSoft in order to set the session's AutoSave No. the SBIG Camera shouldn't be power-cycled. After modifying RestartCCDSoft to include a power recycle of the SBIG camera, the process of starting AstroMain Observatory has become very prolonged and annoying. Suggest that powercycle is not performed when RestartCCDSoftMode is .AutoStart.
  Done 2022-11-02 (AstroMain 3.56.8).
   
• COM Ports List should show 'ConBee II"  against COM7. AfteConBee II USB STick is present on Observatory Computer's COM7 port.  The Ports List  table produced by AstroMain shows COM7 as a used port but the associated name field is blank.  How can we get ConBee II listed as the name ?
  Done 2022-11-02 (AstroMain 3.56.8).

[ Prev | Next ]

Back to Top