Fig 1.   Slew Path Table for Target 28/36 (AT2024xhn)
Highlighted in red is an apparent anomaly where the Telescope moves from Az 306.88 to Az 6.72 in only 0.8s

 Time:  0.0, Slewing: 0, Slew:   0.000, Az: 316.65, Alt: 44.11, Angle: 0.000, Ra: 21.4581, Dec: 60.19
Time:  3.3, Slewing: 1, Slew:   2.075, Az: 316.66, Alt: 44.11, Angle: 2.075, Ra: 21.1806, Dec: 60.08
Time:  4.4, Slewing: 1, Slew:   5.889, Az: 315.31, Alt: 45.04, Angle: 3.814, Ra: 20.6783, Dec: 59.60
Time:  5.4, Slewing: 1, Slew:   9.730, Az: 312.12, Alt: 46.40, Angle: 3.841, Ra: 20.1772, Dec: 59.23
Time:  6.5, Slewing: 1, Slew:  13.730, Az: 309.69, Alt: 48.27, Angle: 4.000, Ra: 19.6575, Dec: 59.05
Time:  7.6, Slewing: 1, Slew:  17.752, Az: 307.35, Alt: 50.37, Angle: 4.021, Ra: 19.1358, Dec: 59.06
Time:  9.1, Slewing: 1, Slew:  21.773, Az: 302.94, Alt: 52.57, Angle: 4.021, Ra: 18.6142, Dec: 59.05
Time:  9.9, Slewing: 1, Slew:  25.994, Az: 300.74, Alt: 57.27, Angle: 4.221, Ra: 18.0667, Dec: 59.04
Time: 10.9, Slewing: 1, Slew:  29.943, Az: 298.75, Alt: 59.60, Angle: 3.948, Ra: 17.5547, Dec: 59.04
Time: 11.8, Slewing: 1, Slew:  33.949, Az: 298.75, Alt: 59.60, Angle: 4.006, Ra: 17.0353, Dec: 59.04
Time: 12.9, Slewing: 1, Slew:  37.934, Az: 296.78, Alt: 62.00, Angle: 3.985, Ra: 16.5186, Dec: 59.04
Time: 13.7, Slewing: 1, Slew:  41.859, Az: 294.90, Alt: 64.43, Angle: 3.925, Ra: 16.0097, Dec: 59.04
Time: 14.6, Slewing: 1, Slew:  45.733, Az: 293.14, Alt: 66.87, Angle: 3.874, Ra: 15.5075, Dec: 59.04
Time: 15.6, Slewing: 1, Slew:  49.718, Az: 291.53, Alt: 69.30, Angle: 3.985, Ra: 14.9908, Dec: 59.04
Time: 16.5, Slewing: 1, Slew:  53.593, Az: 290.03, Alt: 71.82, Angle: 3.876, Ra: 14.4883, Dec: 59.04
Time: 17.5, Slewing: 1, Slew:  57.580, Az: 288.80, Alt: 74.30, Angle: 3.987, Ra: 13.9714, Dec: 59.04
Time: 18.4, Slewing: 1, Slew:  61.454, Az: 287.89, Alt: 76.87, Angle: 3.874, Ra: 13.4692, Dec: 59.04
Time: 19.2, Slewing: 1, Slew:  65.621, Az: 287.61, Alt: 79.38, Angle: 4.167, Ra: 12.9289, Dec: 59.04
Time: 21.1, Slewing: 1, Slew:  69.728, Az: 292.69, Alt: 84.68, Angle: 4.107, Ra: 12.3964, Dec: 59.04
Time: 22.0, Slewing: 1, Slew:  73.665, Az: 306.88, Alt: 87.03, Angle: 3.938, Ra: 11.8858, Dec: 59.04
Time: 22.8, Slewing: 1, Slew:  77.661, Az:   6.72, Alt: 88.29, Angle: 3.996, Ra: 11.3678, Dec: 59.04
Time: 23.9, Slewing: 1, Slew:  81.607, Az:  56.60, Alt: 86.71, Angle: 3.946, Ra: 10.8561, Dec: 59.04
Time: 25.6, Slewing: 1, Slew:  89.569, Az:  68.32, Alt: 84.28, Angle: 3.972, Ra:  9.8239, Dec: 59.04
Time: 26.6, Slewing: 1, Slew:  93.440, Az:  71.65, Alt: 81.75, Angle: 3.871, Ra:  9.3219, Dec: 59.04
Time: 27.5, Slewing: 1, Slew:  97.367, Az:  72.40, Alt: 79.25, Angle: 3.927, Ra:  8.8128, Dec: 59.04
Time: 28.5, Slewing: 1, Slew: 101.314, Az:  72.06, Alt: 76.71, Angle: 3.946, Ra:  8.3011, Dec: 59.04
Time: 29.3, Slewing: 1, Slew: 105.236, Az:  71.14, Alt: 74.17, Angle: 3.923, Ra:  7.7925, Dec: 59.04
Time: 30.4, Slewing: 1, Slew: 108.697, Az:  69.88, Alt: 71.66, Angle: 3.460, Ra:  7.3439, Dec: 59.04
Time: 31.4, Slewing: 1, Slew: 110.928, Az:  68.58, Alt: 69.47, Angle: 2.231, Ra:  7.0547, Dec: 59.04
Time: 32.3, Slewing: 1, Slew: 111.890, Az:  67.67, Alt: 68.06, Angle: 0.962, Ra:  6.9300, Dec: 59.04
Time: 33.3, Slewing: 1, Slew: 112.193, Az:  67.27, Alt: 67.46, Angle: 0.302, Ra:  6.8908, Dec: 59.04
Time: 34.4, Slewing: 1, Slew: 112.272, Az:  67.14, Alt: 67.27, Angle: 0.079, Ra:  6.8806, Dec: 59.04
Time: 35.5, Slewing: 1, Slew: 112.296, Az:  67.11, Alt: 67.22, Angle: 0.024, Ra:  6.8775, Dec: 59.04
Time: 37.4, Slewing: 1, Slew: 112.351, Az:  67.09, Alt: 67.21, Angle: 0.056, Ra:  6.8844, Dec: 59.02
Time: 38.5, Slewing: 1, Slew: 112.379, Az:  67.10, Alt: 67.24, Angle: 0.028, Ra:  6.8808, Dec: 59.03
Time: 39.4, Slewing: 1, Slew: 112.394, Az:  67.12, Alt: 67.27, Angle: 0.015, Ra:  6.8789, Dec: 59.03
Time: 40.6, Slewing: 1, Slew: 112.403, Az:  67.13, Alt: 67.29, Angle: 0.009, Ra:  6.8778, Dec: 59.03
Time: 41.3, Slewing: 1, Slew: 112.405, Az:  67.14, Alt: 67.30, Angle: 0.002, Ra:  6.8775, Dec: 59.03
Time: 42.1, Slewing: 1, Slew: 112.414, Az:  67.14, Alt: 67.30, Angle: 0.009, Ra:  6.8764, Dec: 59.03
Time: 44.3, Slewing: 1, Slew: 112.420, Az:  67.14, Alt: 67.30, Angle: 0.006, Ra:  6.8772, Dec: 59.03
Time: 44.9, Slewing: 0, Slew: 112.421, Az:  67.14, Alt: 67.31, Angle: 0.000, Ra:  6.8772, Dec: 59.03

Fig 2. Telescope Slew Path from S1255, with path to Target 28/36 (AT2024xhn) highlighted
Slew path to Target 28/36 (AT2024xhn) is completely valid, but is a relatively rare one that happens to pass very close to Zenith and thus through a region where Az changes very quickly.  The apparent scope path analomy where Telescope Az changes by 59 in only 0.8s  thereby explained.

Issue

1)  CCDCamera froze on a number of occasions likely related to CCDSoft.Camera/SBIG Camera issues (2024-10-12 , S1254) 
 - 1a [20:16]
 - 1b [23:55]
 - 1c [00:34 & 00:38]
 
2) CCDCamera & CCDSoft froze on a multiple of occasions likely related to CCDSoft.Camera/SBIG Camera issues (2024-10-14, S1255)
 - 2a  [19:58]
 - 2b  [20:12,  20:15]
 - 2c  [20:37]
 - 2d  [21:01, 21:03, 21:04, 21:06, 21:08, 21:11]
 - 2e  [21:36, 21:37, 21:39, 21:42, 21:44]

Description

1) S1254  2024-10-12  Red alerts raised with messages like "CcdCamera appears to be frozen (last cycle at 20:14:30) in section 'GetCameraProperties / State' ).  .

2) S1255  2024-10-14 Red alerts raised with messages like "Take Image failed (Command timed-out)", "CcdCamera appears to be frozen (last cycle at 19:58:09 ) in section 'GetCameraProperties / State' ).  Whilst issue occured  it was noticed that when watching CCDSoft it's Camera Status field will show progress like "Exposing Light (165.25s left)" but then suddenly freeze and not progress any further, with CCDCamera seemingly freezing at the same time.

Analysis

1)

2a)  19:58. 

• After successfully taking 2 Locate frames and a Focus frame for Focus Field, the Focus Profile (wide) was commenced.
• Whilst taking "1s box (C)  1/20"  - error message  "CcdCamera is frozen (19:58) in section 'GetCameraProperties / State'
  
  The last successful camera interaction by CCDCamera was a 'Set Delay(0)' operation at 19:57:58  just before 'Foc1 FocusProfile, wide'  begins
  Problem with CCDCamera is evident at 19:58:11 when a 'Get Status' operation timed out after 2s
  
  FocusFrame 1/20 is logged as commencing at 19:58:14,  CCDCamera records multiple 'timed out after 2s' messages from 19:58:13 and 19:58:41 when CCDCamera was eventually reported as frozen.  The first 'CCD Camera is Pending' (13s) message occured at 19:58:22, indicating that CCDCamera froze at 19:58:09 , which is consistent with time that was 2s seconds before the 'Get Status' operation timed out after 2s.
  
• CCDSoft/SBIG camera automatically restarted  - "CCDSoft being restarted (attempt to fix frozen CcdCamera)"
• Connect Camera failed on 1st attempt with error - "SBIG driver: Operating system error"
• Connect Camera failed on 2nd attempt with error  - "SBIG driver: Camera not found"
• 1s box (C) 2/20 .. 6/20 introduced but reported without any results/values.
  Each failed on AttachToActiveImager with exception message - "Command Failed"
• Focus Profile aborted - "Star has been lost. Aborting Profile "
  
• Moved onto Foc2 Focusing which was successful. (used SharpCap / ZWO Camera to acquire focus frames & CCDSoft to perfom star evaluation).

2b) 20:12

• Taking 15s Locate Frame 1 for Target 1 (AT2024wpc)
• ObsOverseer reported  "Task in TakeImage/Start is taking a long time? (20:11)"
• Job Executor reported Image Failure "Error: command failed. Error code = 206 (0xce)"
  and reported "CCD Image [0000] has not saved to disk. Restarting CCDSoft... "
  
  This failure is not surprising as the last Camera re-connection attempt during Focus Field 20 was unsuccessful (2 attempts made and both failed with errors), and there had been no attempt to resolve the Camera Issue.
  
  Call to TakeImage was made at 20:11:47, but already at 20:10:57 to 20:11:31 CCDCamera was failing to Get & Set various Camera properties with messages "timed out after 2s" for each command. In fact the "timed out after 2s" messages were produced all the time between 19:58:11 & 20:11:31
  
• CCDSoft/SBIG camera automatically restarted  - "CCDSoft being restarted (attempt to fix frozen CcdCamera)"
• Camera reconnection was successful
• Locate Frame 1 was succesfully taken
   
• "Taking 15s Locate Frame 2"  - Failed
• ObsOvereer reported "Camera.TakeImageTask in TakeImage/TakeImage is taking a long time? (20:14)"
• Job Executor reported "Image failed  (Timed-out) "
• "Taking 30s Locate Frame 3"  -Failed
• ObsOverseer reported Warning "CcdCamera is frozen (20:15) in section 'GetCameraProperties / Temperature' "
• Job Executor restarted CCDSoft+SBIG camera - "CCDSoft being restarted (attempt to fix frozen CcdCamera)"
• Camera re-connection was successful
• ObsOverseer gave message "Camera.TakeImageTask in TakeImage/TakeImage is taking a long time? (20:16) "
• JobExecution reports results from Locate Frame 3 and its Image Link
• "Taking 30s Locate Frame 4" - Successful

Ideas

• Could the operation to restart CCDSoft begin earlier than 30s ?
• If CCDCamera is already Pending then it is probably best to try to resolve the Camera issue (and if neccessary wait a full 30s) before attempting to take an Image
• After failure to make Camera Reconnection during Near Zenith Foc1 Focusing, CCD Camera should have been allowed to remain in a frozen condition for so long and to begin to take a Locate Frame for Target 1

Conclusion

• The

Actions:

ASCOM Platform upgraded on Development Computer today (2024-10-16) from version 6.6 SP1 to the new 7.0 version.

The following installations were made:
 - AscomPlatform700.4619.exe

Installation Notes:

• Note this installation now installs the Developer Tools at the same time (it no longer requires a separate download/installation)
  
  
• Following installation of ASCOM 7.0 the DeviceHub program was updated from 6.6.1.1 to  7.0.0.0
   
• Installation of ASCOM 7.0 wouldn't add the new Conform Universal (ConformU) program on the Development Computer as it found a Platform 6 version of conform on the computer. 
  
  
  
  The existing Conform program was uninstalled and the latest version of the Conform Universal download via https://ascom-standards.org/Downloads/DevTools.htm. This accessed the https://github.com/ASCOMInitiative/ConformU/releases page from where the latest v4.0.0 version was downloaded (ConformU.4.0.0+32688.Setup.exe) and separately installed.
  
  On the Observatory Computer, Conform 6.6 will be first uninstalled from the computer (the existing ConformU program v. 1.0.0.10609 was left) before installing ASCOM Platform 7.

New Features:

Additional features and applications in Platform 7:

•  ASCOM Remote - This is now included with the Platform and enables Windows COM drivers to appear to be Alpaca devices that can be used by network connected Windows, Linux, MacOS, IOS and Android clients.
   
• Omni-Simulators - These are now the default Platform simulators and provide a better base to add new features in future. The original Platform simulators continue to be available and can be enabled in place of the Omni-Simulators through an option in the Diagnostics Tool.
   
• JustAHub - This is a straightforward hub application that can host 32bit in-process DLL COM drivers to enable them to work with 64bit applications. Initially it supports camera and filter wheel drivers and will be extended to other device types in future releases. Release candidate testers: Please note that JustAHub replaces the Camera Hub application distributed in the release candidates. If you used the Camera Hub, you will need to reconfigure your client applications to use JustAHub instead.
   
• Default log file location - This can now be changed through the Diagnostics Tool. This affects output from all drivers and applications that use the Platform TraceLogger component, software whose developers have written their own logging tools will continue to use the locations set within the software.
   
• Platform Updates - A weekly update check has been added to notify you when a Platform update is available. This can be enabled / disabled through the Diagnostics Tool.
  

Problems

• Unable to Open Properties for a Dome or Telescope Simulator.  A Setup dialog appears
  
  
  
• Omni-Simulator Devices
  - These are now the default Platform simulators
  - The OmniSimulators can be started through the ASCOM Omni-Simulators entry in the Start menu
   ('ASCOM Omni-Simulators'  puts on a console style window, write some text/message and then minimises itself to the TaskBar)
  - The user interface is browser based and can be accessed by navigating to Omni-Simulator Home (http://localhost:32323).
   
• Device Hub 7.0.0
  Trying the new DeviceHub version revealed a significant problem that preventing changing the Telescope and Dome Drivers to the new Omni Simulators and caused DeviceHub to crash.  The problem and workaround is described under DeviceHub 7.0.0 section below

Actions
 Add button to AstroMain Observatory Tab to all access to Omni Setup.   Done

Update - 2024-10-22
ASCOM 7 Platform was subsequently updated to 7.0.1 on Developement Computer on 2024-10-22 (see ASCOM 7.0.1 notes, 2024-10-22)

Update - 2024-10-22
ASCOM Platform on the Observatory Computer was upgraded from 6.6 SP1 to 7.0.1 on  2024-10-24, including the updated 7.0.1 version of DeviceHub, which fixes an issue seen in 7.0.0.

The new ASCOM 7 platform was used during live session the same night (S1259 2024-10-29.  However problems were encountered with DeviceHub 7.0.1 and after a frustrating couple of hours, DeviceHub program was downgraded to the former 6.6.1.1 version in order to achieve a stable working system and deliever at least some of the aims of the sessions.  Unfortunately due to the issue caused by introduction of DeviceHub 7.0.1  two important targets (T CrB and C/2023 A3  (Tsuchinshan-ATLAS)  ) couldn't be acquired.

A note on the problems has been sent to Peter Simpson (ASCOM).

Upgrade to DeviceHub 7.0.0
DeviceHub was automatically upgraded on Development Computer today (2024-10-16) as a consequence of installing the new ASCOM Platform 7.

DeviceHub noted to have changed from  6.6.1.1  to the new 7.0.0 version.

It is assumed that the 7.0.0 version is fundamentally the same as 6.6.1.4 version (released 2023-12-08) which is the most recent version shown on github
https://github.com/ASCOMInitiative/ASCOMDeviceHub/releases

Changes since last installed version
Changes between 6.6.1.4 and the 6.6.1.1 version are described as following

•  Update telescope status when initiating a meridian flip before returning to the calling application to ensure that the telescope status, especially the slewing flag, is immediately up-to-date. (6.6.1.2)
•  Correctly persist Dome Layout settings when changed through the dome driver's SetupDialog method (6.6.1.3)
•  Fix a bug in dome altitude slewing (6.6.1.4)
  
  (see earlier notes on 6.6.1.1) 

First Experience with new 7.0.0 version 
Trying the new DeviceHub version revealed a significant problem that preventing changing the Telescope and Dome Drivers to the new Omni Simulators and caused DeviceHub to crash.  . This is described below and has also been reported on the ASCOM Talk Forum (https://ascomtalk.groups.io/g/Help/message/47540).

I eventually managed to get DeviceHub to work for Telescope & Dome (so it still works) but there is an issue with 'Device Hub Application and Device Setup' that prevents making/saving any changes.

If I try to make any setup change, whether to change the Telescope Device or the Dome Device or a Polling Rate, or indeed no change at all, and then click the Ok button the Telescope and Dome Control Tabs on the Main Window go blank, and I'm kept on the Setup Window.  If I click on Cancel button, then after a few moments,  DeviceHub crashes.

To make any changes, for example to change DeviceHub's Telescope Device from say ASCOM.Simulator.Telescope to ASCOM.OmniSim.Telescope, I eventually found that I had to resort to using ASCOM Profile Explorer.  Changing values in the Profile Explorer and then reopening DeviceHub then allow DeviceHub to pick up the changes I want.

Steps to repeat issue:
  Open DeviceHub  
  Go to Tools/Setup/Telescope Setup  (I get Fig 1.  on my computer).  
  Make a change on Telescope Setup, e.g. changing  Polling Rate from 0.50 to 1.00  
  Click Ok        (I get Fig 2. on my computer)  
  Click Cancel  (I get a DeviceHub crash) 

 - If I don't press ok, but directly press Cancel it closes the Setup window and returns to the main window.

 - If I don't make any change at all,  and click Ok, the Control Tabs still go blank and clicking Cancel still crashes the program 
 
 - The issue is still present after restarting the computer.

Fig 1.

 
Fig 2.


Fig 3. For Info my DeviceHub Setup Tab shows

Updates:
None to date (awaiting response/replies from ASCOM Talk Forum).