David's Astronomy Pages Notes - Session 1263 (2024-11-06)

Notes (S1262)

Notes Main

Home Page

Notes (S1264A)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (4),  Small Defects (3),  Continuous Improvement (4)
	Images from 2024-11-06 >>
	Current/Latest Session >>

Session Aims & Highlights (2024-11-06)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. AstroMain.  Check new 3.72 version of AstroMain
3. PHD2. Continue to check operation and performance of PHD2 Guiding though new DeviceHub DH 7.0 version

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6, CCDSoft5, DeviceHub 7.02 RC4, MeadeGeneric 1.3.9, UPB 1.5, ASCOM 7.0.2 RC4,  Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.72.1,  AstroPlan 1.42.4  AstroShCap 1.3.15, AstroGuard 1.10.5   (any new items or versions in bold)
  AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.7,  AstroMove 1.13   
  AstroWeather 1.25, AstroAllSky 3.20.6,  AstroObsCam 1.11.4 (not 1.11.5), AstroLaunch 1.11.5

Highlights

• Targets.15/19 planned targets observations were completed, with 2 further targets partially completed. Two targets failed due to cloud.
• AstroMain. No notable issues with new AstroMain 3.72.1 version
• DeviceHub. There were no issues associated wth running DH 7.0.2 RC4, though there were issues with some Dome Slaving
  Dome. There was issues opening/closing shutter during session. Dome closed and parked ok at end of session.

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 00:23:45 Session Monitoring AutoStart monitoring for Live Session opportunity between 00:23 & 05:25 00:23:47 Session AutoStarting Session autostarting (00:23) 00:24:08   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 00:24:35   Camera1 Connected SBIG Camera connected (Set point -20°C) 00:24:37 Session Created Session Created (Live, 2024-11-06 S01263, ImageSaveNum: 1263001) 00:24:42   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 00:26:37   Services Started Observatory Services started 00:26:44 Observatory (Auto) Observatory placed in Fully-Automated Mode 00:26:47 Session Pending Session pending (2024-11-06) 00:26:49 Session Initiating Session initiating (2024-11-06) 00:26:59   Camera1 Connected SBIG Camera connected (Set point -10°C) 00:27:06   Plan Requested Observing Plan requested from AstroPlan (1.42.4) 00:27:36   Plan Loaded Observing Plan loaded to queue (Plan ID: 1044) 00:28:18   Telescope Connected Telescope connected (TheSky6) 00:28:42 Session Equilibration Session ready to Open Dome 00:29:27   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 00:30:07 Session Running Session running 00:30:10   Queue Started Observing Queue started (19 targets selected) 00:30:13     Target Started (NrZen) Target started (Focus Field 3, HIP 14181) 00:30:24       Dome Unparked Dome unparked 00:33:58       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:36:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 00:39:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 00:39:36       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 00:41:33       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 00:43:22       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 00:43:40     Target Completed (NrZen) Target completed (Focus Field 3, HIP 14181) 00:43:44     Target Started (1/19) Target started (1/19, NGC 473 w/AT2024zzo) 00:49:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:52:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 01:08:31     Target Completed Target completed (1/19, NGC 473 w/AT2024zzo) 01:08:35     Target Started (2/19) Target started (2/19, GSC 1224:29) 01:12:29       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 01:19:10     Target Completed Target completed (2/19, GSC 1224:29) 01:19:14     Target Started (3/19) Target started (3/19, AT2024zys (CV)) 01:22:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:25:33       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:31:33     Target Completed Target completed (3/19, AT2024zys (CV)) 01:31:37     Target Started (4/19) Target started (4/19, AT2024aaao (CV)) 01:36:29       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:39:13       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:45:23     Target Completed Target completed (4/19, AT2024aaao (CV)) 01:45:27     Target Started (5/19) Target started (5/19, GCVS BL Lac) 01:49:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:51:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:55:45     Target Completed Target completed (5/19, GCVS BL Lac) 01:55:49     Target Started (6/19) Target started (6/19, AT2023vww (CV)) 01:59:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:01:57       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 02:08:00     Target Completed Target completed (6/19, AT2023vww (CV)) 02:08:04     Target Started (7/19) Target started (7/19, AT2024agp (CV)) 02:11:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:13:51       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 02:19:52     Target Completed Target completed (7/19, AT2024agp (CV)) 02:19:56     Target Started (8/19) Target started (8/19, AT2024eei (CV)) 02:24:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:26:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 02:32:41     Target Completed Target completed (8/19, AT2024eei (CV)) 02:32:45     Target Started (9/19) Target started (9/19, AT2023tkp) 02:52:26     Target Completed Target completed (9/19, AT2023tkp) 02:52:30     Target Started (10/19) Target started (10/19, AT2022acgb) 02:56:24       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:58:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 03:15:26     Target Completed Target completed (10/19, AT2022acgb) 03:15:30     Target Started (11/19) Target started (11/19, WDS GRB 34) 03:20:05       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:22:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 03:24:47     Target Completed Target completed (11/19, WDS GRB 34) 03:24:51     Target Started (12/19) Target started (12/19, LEDA 2078778 w/SN2024xqe) 03:28:49       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 03:44:51     Target Completed Target completed (12/19, LEDA 2078778 w/SN2024xqe) 03:44:55     Target Started (13/19) Target started (13/19, LEDA 1579406 w/SN2024qfh) 03:48:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:51:24       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 04:07:25     Target Completed Target completed (13/19, LEDA 1579406 w/SN2024qfh) 04:07:29     Target Started (14/19) Target started (14/19, C/2017 K2 (PANSTARRS)) 04:10:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:13:22       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 04:21:36     Target Completed Target completed (14/19, C/2017 K2 (PANSTARRS)) 04:21:41     Target Started (15/19) Target started (15/19, C/2022 E2 (ATLAS)) 04:26:14       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 04:35:06     Target Completed Target completed (15/19, C/2022 E2 (ATLAS)) 04:35:10     Target Started (16/19) Target started (16/19, SN 2024epx) 04:37:37   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 04:37:39   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 04:37:41     Target Aborted (16/19) Target aborted (16/19, SN 2024epx) due to cloud 04:37:43   Queue Paused Queue paused for Session Suspension 04:37:45 Session Suspending Session suspending 04:38:33   Dome Closed Dome closed (Closing time 50s, Zigbee 42s) 04:38:36 Session Suspended Session suspended 04:40:38 Session Resuming Session resuming 04:40:48   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 04:40:50   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 04:40:52   Queue Paused Observing Queue pausing for Session Suspension 04:41:22   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 04:41:25 Session Running Session running 04:41:27   Queue Resumed Observing Queue resumed 04:41:29   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 04:41:31   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 04:43:28 Session Suspending Session suspending 04:44:13   Dome Closed Dome closed (Closing time 45s, Zigbee 42s) 04:44:16 Session Suspended Session suspended 04:46:18 Session Resuming Session resuming 04:47:03   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 04:47:06 Session Running Session running 04:47:08   Queue Resumed Observing Queue resumed 04:47:09     Target Started (16/19) Target started (16/19, SN 2024epx) 04:48:03       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 04:48:48       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 04:50:49       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 04:51:08       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 05:01:28     Target Completed Target partially completed (16/19, SN 2024epx) 05:01:32     Target Started (17/19) Target started (17/19, UGC 5426 w/AT2024aanq) 05:12:25   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 05:12:27   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 05:12:30     Target Aborted (17/19) Target aborted (17/19, UGC 5426 w/AT2024aanq) due to cloud 05:12:32   Queue Paused Queue paused for Session Suspension 05:12:34 Session Suspending Session suspending 05:13:16   Dome Closing Dome closure failed after 45s (ShutterState=4) 05:13:21 Session Suspended Session suspended 05:16:02     Target Cancelled Target cancelled (17/19, UGC 5426 w/AT2024aanq) due to cloud 05:38:22     Target Cancelled Target cancelled (18/19, NGC 3443 w/SN2024ehs) due to cloud 05:38:53 Session Resuming Session resuming 05:39:38   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 05:39:41 Session Running Session running 05:39:43   Queue Resumed Observing Queue resumed 05:41:26     Target Started (19/19) Target started (19/19, NGC 5235 w/SN2024grb) 05:41:38     Target Failed (19/19) Target failed due to slew error (19/19, NGC 5235 w/SN2024grb) 05:41:40   Queue Completed Job Queue completed 05:41:44 Session Closing Session closing 05:42:34   Dome Closed Dome closed (Closing time 45s, Zigbee 43s) 05:43:10   Dome Parked Dome parked (parking time 28s), Az: 90.0 deg 05:43:54   Telescope Parked Telescope parked (parking time 38s total) 05:44:18   Telescope State Handbox reads 'Scope parked Turn scope off.' 05:44:40   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 05:46:06   Services Stopped Night Services stopped 05:46:09 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 05:46:31     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 05:47:19     Dome Find Park found (Best Park Az 90.4°) 05:47:25     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.4°) 05:47:27   Dome Parked Dome parked 05:47:34   Dome Charging Dome is parked and re-charging Ok (21mA) 05:47:36 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 00:26:44 Red Alert Unexpected Scope Movement Scope appears to be tracking even though Tracking=False 00:44:09 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 223.8° (T+18.6s) 01:32:07 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 321.0° (T+24.9s) 02:20:23 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 205.8° (T+20.9s) 02:20:41 Yellow Alert Dome Discrepency Difference between Dome Az and Slave Az is > 1 deg (AT2024eei) 02:52:49 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 143.3° (T+13.2s) 04:08:07 Yellow Alert Dome Discrepency Difference between Dome Az and Telescope Az is > 8 deg (C/2017 K2 (PANSTARRS)) 04:08:09 Yellow Alert Dome Discrepency Difference between Dome Az and Slave Az is > 1 deg (C/2017 K2 (PANSTARRS)) 05:13:16 Red Alarm Dome Closing Dome closure failed after 45s (ShutterState=4) 05:47:34 Green Clear Dome Charging Dome is parked and re-charging Ok (21mA)

Back to Top

Operational Issues (2024-11-06 S1263)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (4)
• Small Defects (3)
• Continuous Improvement (4)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• There were 4 yellow-alert cases where the Slaved Dome Slew paused during the Telescope Slew operation  (00:44, 01:32, 02:20,  02:52). During 4 slews there were Yellow Alerts raised by the SlewMonitor with the messages like "Dome slew resumed at Az 223.8° (T+18.6s) .  This is issue that dome goes to a particular Az. Stops slewing and the Slews again.  To be investigated  - does the issue cause sufficient problem to raise with author of the relevant driver or program (dome, telescope, devicehub) ?. Issue eventually fixed on 2024-11-15 by enabling DeviceHub's Composite Slewing and making adjustments to how AstroMain's Slew Monitor operates.
  Resolved 2024-11-15  (DeviceHub Composite Slewing, AstroMain 3.72.5)
   
• There were 2 yellow-alert cases where difference between Dome Az and Slave Az was >1 deg (02:20, 04:08).  During 2 slews yellow alerts were raised for 'Dome Discrepency' with the message "Difference between Dome Az and Slave Az is > 1 deg". To be investigated and compared with previous cases of the problem. Is this a significant issue or not. Issue eventually fixed on 2024-11-15 by enabling DeviceHub's Composite Slewing and making adjustments to how AstroMain's Slew Monitor operates.
  Resolved 2024-11-15  (DeviceHub Composite Slewing, AstroMain 3.72.5)
   
• There was a 'Dome Closing' alarm with ShutterState=4 (05:13). During session suspension at 05:12 due to cloud a red alert/alarm was raised at 05:13:16  "Dome closure failed after 45s (ShutterState=4)".  The closure was successful within normal time as shown by Zigbee Bottom Shutter sensor, but the Pulsar Dome Driver didn't seem to get the correct respons . There was no issue reopening the shutter and a final closure of the shutter at the end of the session. This seems to be glitch in the Pulsar Dome system ? Report files shows the message  "Close Dome...  Fail      Dome closure has stopped (Dome closure failed (45s, ShutterState=4)) ".  Log file indicates that Zigbee saw the shutter becoming closed at 05:13:15 and that the 'Dome closure has stopped' failure  was logged at 05:13:16..   ShutterState 4 corresponds to ShutterState.shutterError  ("Dome Shutter status error").  Pulsar log file show CloseShutter' request at 05:12:31, with shutter state immediately changing to 3 (shutterClosing). At 05:13:16, Volatile record and Get ShutterStatus show 84. A status number never seen before. The next volatile record at 05:13:17 and the following GetS hutterStatus show 1 (shutter.Closed), this suggest a data commns glitch between the Shutter Unit and the Dome Control and/or Dome Driver.  DeviceHub.Dome log of comms with AstroMain shows shutterError at 05:13:16.05, 05:13:16.33, 05:13:16.6, before changing to shutterClosed at 05:13:17.31.  It would seem that DeviceHub has statement that if ShutterStatus is >=4 then ShutterStatus = 4 (shutterError).   Issue closed after review 2024-11-07.  A separate continuous ticket has been raised to add a Green all-clear alert when Shutter Status becomes normal again (ie 0-3 ) following an earlier red alert (shutterError).
  To investigate 2024-11-07 (Session, Pulsar Dome)
   
• Unable to Extract Spectra correctly for images from older session (post-session). Whilst trying to extract Spectra from Images of SN2019np acquired in session S652 (2019-01-29) using AstroMain's ExtractSpectra tool (not available back in 2019) it was found that the rotation applied to the Spectral  Image (S Filter / SA100) wasn't appropriate. It is likely that the dispersion isn't appropriate for the image either.   It was't possible to temporaily change either setting whilst program was in the 'Analysis' Mode.  These settings would seem to be something best placed on the Program Settings form rather than on the Tabs shown on the ObsConsole form when the AstroMain program is running in the 'Observatory' Mode.  Issue reviewed and understood.   A separate continuous improvement ticket has been raised to relocate fields related to Spectra Image settings to the Program Settings Form.
  Resolved 2024-11-14 (AstroMain 3.72.3)

• DeviceHub's Activity Log when subsequently opened didn't show activity from the first part of the session. Whilst trying to collect information on DH Activity to use in the diagnosis of the Dome Slewing Anomalies,  DH Activity log window opened after the session had finished and contents copied to a 'DH.log' files. Examining the log showed that it contained records between 04:32:32 and 05:47:25.   Crtically the log didn't contain records during the period 00:44 to 02:52 during which the dome slewing anomalies occured. The default log capacity is 125000,  however the capacity can be changed by editing the value of 'ActivityLogCapacity' in the DeviceHub configuration file  (C:\Program Files (x86)\Common Files\ASCOM\DeviceHub\ASCOM.DeviceHub.exe.config) . The capacity could be increased ten-fold by change the setting thus
    <setting name="ActivityLogCapacity" serializeAs="String">
    <value>1250000</value>
  </setting>
  Fixed n the Observatory computer on 2024-11-07, my running NotePad As Adminstrator in order to edit and save ASCOM.DeviceHub.exe.config.  DeviceHub's Log capacity was increased to 1250000 (ie a 10-fold increase).  It should be noted that the value is reset back to default value after each new installation/update of DeviceHub.
  Fixed 2024-11-07 (DeviceHub)
   
• There was an 'Unexpected Scope Movement' alert near the start of the session (00:26).  A Red Alert was raised at 00:26:44 4 with the message "Scope appears to be tracking even though Tracking=False". Report File shows the following (indicating that the alert was raised during AutoStart operation after starting Night Services.
    Select Night Services..       Ok        Night Services    (Night services have been selected)   Start Services..              Ok        Starting   

  Start Observatory Services   
  .. (intervning lines not shown) .................
  Checking ASCOM Scope..         Ok           
  Turn Off Telescope Tracking    **                          (Continued below)
> ObsMonitor (Scope)             Alert     Scope appears to be tracking even though Tracking=False **Turn Off Telescope Tracking    Ok        Tracking is OFF   (00:26)   
  Set Fully-Automated            Ok        Setting Fully-Automtated Mode
  Get Scope.Tracking=True is the expected tracking state of the scope after turning on the LX200 Telescope, and is turned off by the post-telescope connection operation in case the telescope is not operated at all due to a failure to start/continue the session. The alert was raised just at the moment that Scale tracking was going to be turned off.  Fixed in AstroMain 3.72.2 by  skipping over this warning at the beginning of the session ( SessionState.AutoWaiting or SessionState.Initiating)
  Fixed 2024-11-07 (AstroMain 3.72.2)
   
• When Observatory Log file (htm) is opened on local computer from a past Session Notes the four links at top of page don't work (post-session).  The four links at  top of 'Observatory (run).htm' that don't work in the local environment are 'Latest Session',  'Latest Images',  'Session Notes',  'Session Images'. The htm version of the log file was designed to be updated to web page at end of a live session and permit rapid post-session evaluation of issues and their causes. The links work correctly when the Log File (htm) is opened on the Observatory WebSite.  The problem comes later on after the session is not longer the latest session and the page is opened locally from Notes page running on local computer.  The 'relative' links that function correctly on the live website, are not appropriate for the local environment.  A review needs to be undertaken to see how this issue can be resolved.   Testing show that page is written with local links when 'Finalise LogFile' is used from the AstroMain's 'Reduction Workflow' Tab. This writes the page with just two links at the top of the oage 'Session Notes' & 'Session Images'. The problem is that the Finalised LogFile' facility tends not to be used by the user.  Prehaps it needs to be an automated by 'hiding it' as a supplementary action within the  'Create Workbook (.xls)'  button routine, which is always used by the user (normally used just once).  A  'Rebuild AllLog Pages' button option is available if required to retrospectively get working links in log (htm) files from past sessions.  A separate continuous ticket has been raised to add a Add call to 'Finalise Logfile' from AstroMain's Reduction 'CreateWorkbook (xls) button routine.
  Closed after review 2024-11-07 (AstroMain, Log (htm) page, User Awareness).

Continuous Improvement

• Add call to 'Finalise Logfile' from AstroMain's Reduction 'CreateWorkbook (xls) button routine.   . To resolve a minor issue whereby the Observatory Log file (htm) can be opened on local computer with 4 links at top of page, it is proposed to add a call to 'FInalise Logfile' from AstroMain's Reduction 'CreateWorkbook (xls) button routine. This by-passes the need for user to remember and use the Finalise Logfile' button operation to write the log (htm) file with local links instead of internet links used for the latest session. Implemented in AstroMain 3.72.2.
  Done 2024-11-07 (AstroMain 3.72.2)
   
• Raise a green 'Dome Shutter' alert when ShutterStatus becomes normal again following a prior ShutterState=4 condition. During session suspension at 05:12 a red alert/alarm was raised at 05:13:16  "Dome closure failed after 45s (ShutterState=4)".  This has been investigated and shown to be a data glitch in a single Volatile record and after 1s the shutterstatus becoming shutterState=1 ( shutterClosed) .  In the event of a prior raising of a red-alert due to ShutterState=4 , a green all clear alert showed be recorded and reported. Implemented in AstroMain 3.72.6 using a new flag variable bShutterStateErrorReported(boolean) which is raised when then ShutterState Error is first reported/alerted, and a TimeShutterStateErrorReported (Date)  variable to allow the calculation of the Error Duration.
  Done 2024-11-16 (AstroMain 3.72.6)
   
• Acquire test images of Crab Nebula to demonstrate ability to separate CM Tau & adjacent star in a 60s exposure. 
  To do 2024-11-14+ (Session, AstroMain 3.72.2+)
   
• Move fields associated with Spectra Images to Program Settings Form.  Settings related to SA200 filter and Spectral Images are currently located in a 'Spectra Focusing' groupbox on Scope1 / TCF-S Focuser tab. The setting are not available when AstroMain program is in Analysis mode. In order to access these settings  from both the Observatory and Analysis Modes it is proposed to move these data fields to the Program Settings form.  Implemented .....
  Done 2024-11-14 (AstroMain 3.72.3)

[ Prev | Next ]

Back to Top