As part of investigating and attempting to fix a show-stopping issue where connection can no longer be made to the Observatory's 12" LX200GPS scope (see Investigation - Unable to Connect to LX200GPS Scope, 2021-04-17) the then latest 1.0.0.296, 2021-03-02 version of Chris Dawson's  ASCOM driver for Meade Telescopes including the LX200GPS model was downloaded and installed onto the development and observatory computers today (2021-04-19) .   

Meade Generic Website : https://bitbucket.org/cjdskunkworks/meadeautostar497/wiki/Home

The new telescope driver (named  'ASCOM.MeadeGeneric.Telescope' ) is listed as 'Meade Generic' in ASCOM Telescope Chooser. When active the driver is listed as the 'ASCOM.Meade.net.Server.exe'  process in the Windows Task Manager.  

The set of fields on the Meade Generic Settings are quite different from those on LX200GPS/R Setting driver Telescope Driver properties.  In particular there is no checkbox/fields for specifying AutoSet Time/Date or  how coordinates are returned when the Scope is Parked.   There is however a field for specifying Guiding Rate (default value 10.0779 arc seconds/second (67% of sidereal time). (I normally use a Guiding Rate of 90% of sidereal time, which would correspond to 13.53 arc seconds/second. or 0.003763944 arc deg/sec (0.90)

The Meade Generic Driver used for first time today (2021-04-20) during a daytime test.  Connection to scope was successful, but Time/Date is not AutoSet, the Scope initialises with Time 20:00:00 and the last used Date.  Time/Date has to be manually entered via the scope's AutoStar II handbox at the Date Prompts.

Site (CLAIR ABZ) was found to have become set to UTC offset +01. This was changed back to correct value of +00,  but this then required scope to be resynced to Park Position in TheSky6 and the Telescope's Park Position reset to current position using the scope's AutoStar II handbox.

(Did this change cause the scope to slew from  Az 43.9/Alt 22 to Az 358.6/Alt 34.3 when making slew for Target 17/18 (Nova Per 2020) in session S888 (2021-04-20) ? )

(TPoint model in S888B Document was deleted to sync the scope and prior S886 model will need to be reopened at next session.

The Meade Generic Driver was used a live night session for the first time duuring session S888 (2021-04-20)

Supported Actions
The driver's SupportedActions Array list indicates 2 available actions
   handbox
   site

Action parameters associated with 'handbox' action are
   readdisplay - returns the message displayed on Autostar II handbox
   enter
   mode
   longmode
   goto
   0, 1, 2, 3, 4, 5, 6, 7, 8, 9
   up, down, back, forward
   ?

Action parameters associated with 'site' action are
   count - returns 4
   select
   getname
   setname

Whilst it seems helpful to develop routines using these Actions, e.g.    Msg = Scope.Action("handbox", "readdisplay") these actions would only work if using MeadeGeneric driver and wouldn't work if using the MeadeLX200GPS driver. It is therefore probably better to use the Meade based command    Msg = CommandString (":ED#, True) in order to give a driver independant solution.

Actions:
  Create new AstroMain version that can optionally use the 'Meade Generic' telescope instead of the 'Meade LX200GPS/R'
  Create new function to set Telescope's UTC Date/Time and apply function when first connecting to Telescope using 'Meade Generic'
  Set DeviceHub.Telescope's trace level to True.

Update 2021-04-27 (1.1.0.337)

Key isssues with MeadeGeneric telescope driver (1.0.0.296) have now been fixed (1.1.0.337, 2021-04-27), and the driver is believed to now be in a fit state to use in live sessions moving forward  (subsequently it was shown that the driver still had a issue with tracking state, whereby the scope's actual tracking state wasn't being turned on/turned off when requested by client.

(A workaround had been found for the recent show-stopping issue with the older MeadeLX200GPS driver so this was for a short time available as an alternate, ready-to go, back-up option, however trying to use MeadeLX200GPS driver in session S898, 2021-05-22, showed a new issue in accessing that the driver that prevented connection to scope. )

Update 2021-04-30 (Tracking State Issue)

During session S893 (2021-04-30) is was discoved that telescope Tracking remained on even though Tracking was switched off (02:09) though the MeadeGeneric driver .  The problem was diagnosed as being a bug in MeadeGeneric (basically a failure to command the LX200GPS to turn off tracking). The issue has been communicated to the author of MeadeGeneric Driver (2021-05-11) and logged as an issue in the driver's bitbucket project site (https://bitbucket.org/cjdskunkworks/meadeautostar497/issues/24/get-set-tracking).  

If no fix is forthcoming a workaround could be implemented using CommandBlind and CommandString calls to interact directly with the scope.  Until the driver is fixed (or a workaround is implemented) it is proposed to switch back to using the MeadeLX200GPS driver. (In session S898, 2021-05-22, it became evident that there was a new issue in accessing that the MeadeLX200GPS driver that prevented connection to scope. )

Update 2021-05-22 (AstroMain fix for Tracking State Issue)

A workaround has been added to AstroMain 3.40.1 (2021-05-22) so that calling Set  Scope.Tracking = False  also sends a ":AL#"  (Land Mode) command to the scope to physically turn off tracking, and calling Set Scope.Tracking = True also sends a ":AP#"  (Polar Mode) command to the scope to physically turn on tracking.

An attempt to use :GW# to read the tracking state of the scope didn't seem to work (DeviceHub logs  "Command :GW#, Raw True (failed) " ) and causes performance issues to AstroMain's Obs.Monitor.    This is not a total showstopper, prrovided that Tracking is turned off / turned off from AstroMain Client there is no problem.  An issue only arises if another application is used to turn on/off tracking as this doesn't physically effect the tracking state of the scope and will confuse  AstroMain.

Update 2021-07-18 (1.2.0.344)
MeadeGeneric telescope driver was updated to 1.2.0.344 (this followed issues with version 1.3.0.352 that was installed for testing on 2021-07-17).
The 1.2.0 version doesn't yet include support for Get/Set Tracking and the earlier workaround in AstroMain using AL and AP commands to set telescope Tracking state still needs to be used.

Update 2021-08-16 (1.3.1.361)
MeadeGeneric telescope driver was updated to 1.3.1.361. This fixes an early limitationand means that Set/GetTracking is now fully implemented and working for LX200GPS scope.  The GW command was also confirmed to now work.  MeadeGeneric Telescope Driver (1.3.1)

Issue : Intermittent issue during Target Centering Jogs '"Unable to start the direct slew!!!".  

Description: During target centering TheSky6 frequently put up an 'ASCOM Device Hub' dialog box with the error message 'Unable to startthe direct slew!!!'   This holds up the execution of Job Queue in AstroMain until the dialog box is acknowledged. If the dailog is not seen/not acknowledged, AstroMain's Obs.Overseer eventually intervenes to make the observatory safe (turning off tracking and closing the dome shutter).   Session could only be kept going by remote monitoring and acknowledging the dialog box each time it appeared. Telescope Jogs appear to take place even though dialog box is shown ?.

Analysis :

Examining the Jog Operation associated with Centering 1 operation for Target 4/17 (Nova Per 2020) at 01:05

Report File shows :

  Centering 1                           2021-04-21 01:05  (Local)
  Taking 10s image (C)...     Ok        [00888034] 00:05:53 (UT)  Full Locate C
  Linking image (UCA/USNO)... Ok        Stars 29, Scale 1.402, Angle 179.3°

  Reviewing position (1)...   Ok        Pointing Error:  3.44 arc mins (W: -2.54', N: -2.33')  
  Updating Slew Adjustment..  Ok        Updated Adjustment W 0.8, N 1.7 [arc mins]
  Reviewing position (1)...   Ok        Jog Required:    3.44 arc mins (W= 2.54', N= 2.33')
  Applying JogW Adjustment    Ok        JogWAdj=0.13'
  Jogging ...                 **        
> Obs.Overseer                Warning   Telescope.Jog task In MakeJogCorrection/JogN Is taking a Long time? (01:06)
  **                          Ok        Est. Scope Change: 3.02 arc mins (W= -0.10', N= 3.01')

Log File shows

01:05:51.17 | Nova Per 2020              TakeLocateImage        Info    | Locate Image No.  1
01:05:51.17 | Nova Per 2020              Filter                 Info    | Confirming C filter (1)

01:06:06.69 | Nova Per 2020              LinkImage              Ok      | IamAlive: ImageAndLink

01:06:08.50 | Nova Per 2020              Offset                 Data    | 3.44
01:06:08.50 | Nova Per 2020              SepN                   Data    | 2.327
01:06:08.50 | Nova Per 2020              SepW                   Data    | 2.538
01:06:08.50 | Nova Per 2020              OffsetO                Data    | 3.44
                                             | 
01:06:09.50 | Nova Per 2020              Jog                    Data    | Net Jog    W: 2.67', N: 2.33'
01:06:09.50 | Nova Per 2020              Making Jog             Info    | 3.54 arc mins (W= 2.67', N= 2.33')
01:06:09.50 | Nova Per 2020              Telescope.GetRaDec     Ok      | IamAlive: MakeJogCorrection, PreJogPosition
01:06:09.56 | Nova Per 2020              Continue               Ok      | IamAlive: MakeJogCorrection
01:06:09.56 | Nova Per 2020              Making W Jog           Info    | W= 2.67' (3.71' at Dec 44.0)
01:06:09.56 | Nova Per 2020              Telescope.Jog          Ok      | IamAlive: MakeJogCorrection, JogW
01:06:13.01 | Nova Per 2020              Continue               Ok      | IamAlive: MakeJogCorrection
01:06:13.01 | Nova Per 2020              Jog                    Info    | Sleeping For 0.5 secs
01:06:13.52 | Nova Per 2020              Making N Jog           Info    | N= 2.33'
01:06:13.52 | Nova Per 2020              Telescope.Jog          Ok      | IamAlive: MakeJogCorrection, JogN
01:06:55.91 | Observatory Overseer       Check.Operation        Info    | Task In MakeJogCorrection/JogN is taking a Long time? (Telescope.Jog)

01:08:30.66 | Nova Per 2020              Continue               Ok      | IamAlive: MakeJogCorrection
01:08:30.66 | Nova Per 2020              Jog                    Info    | Sleeping For 0.5 secs
01:08:31.17 | Nova Per 2020              Jog                    Ok      | [W] [N]  Jog Completed 
01:08:31.17 | Nova Per 2020              Telescope.GetRaDec     Ok      | IamAlive: MakeJogCorrection, PostJogPosition
01:08:31.27 | Nova Per 2020              Continue               Ok      | IamAlive: MakeJogCorrection
01:08:31.27 | Nova Per 2020              Scope (Pre-Jog)        Data    | RA= 04 30 46.957  Dec= +43 59 35.88 | Current Epoch
01:08:31.27 | Nova Per 2020              Scope (Post-Jog)       Data    | RA= 04 30 47.534  Dec= +44 02 36.75 | Current Epoch
01:08:31.27 | Nova Per 2020              Scope Change           Data    | 3.02 arc mins (W= -0.10', N= 3.01')
01:08:31.27 | Nova Per 2020              Jog Discrepancy        Data    | 2.73 arc mins (W= -2.64', N= 0.69')
01:08:31.27 | Nova Per 2020              Get rawJogW Discrep.   Data    | rawJogW Discrepancy= -2.64'
01:08:31.27 | Nova Per 2020              Update JogWAdj         Ok      | JogWAdj updated to 0.18' (nJogs= 52)
01:08:31.27 | Nova Per 2020              Continue               Ok      | IamAlive: CentreTarget

Meade.Generic.Telescope trace file shows

01:06:09.595 SlewToCoordinatesAsync    Ra=4.49347377511668, Dec=42.2326154754363
01:06:09.595 TargetRightAscension Set  4.49347377511668
01:06:09.595 TargetRightAscension Set  :Sr04:29.61#
01:06:09.626 TargetDeclination Set     42.2326154754363
01:06:09.626 TargetDeclination Set     :Sd+42*13.96#
01:06:09.922 DoSlewAsync               Slewing to target
01:06:09.922 SlewSettleTime Get        0 Seconds

01:06:11.186 RightAscension            Get - 04:29:53 convert to 4.49805555555556 04:29:53
01:06:11.592 Declination               Get - +42[DF]13:29 convert to 42.2247222222222 42:13:29"

01:06:13.620 SlewToCoordinatesAsync    Ra=4.49700257604004, Dec=42.2720129146783
01:06:13.620 TargetRightAscension Set  4.49700257604004
01:06:13.620 TargetRightAscension Set  :Sr04:29.82#
01:06:13.651 TargetDeclination Set     42.2720129146783
01:06:13.651 TargetDeclination Set     :Sd+42*16.32#

01:06:19.236 RightAscension            Get - 04:29:40 convert to 4.49444444444444 04:29:40
01:06:19.266 Declination               Get - +42[DF]14:27 convert to 42.2408333333333 42:14:27"

01:06:19.436 RightAscension            Get - 04:29:40 convert to 4.49444444444444 04:29:40
01:06:19.476 Declination               Get - +42[DF]14:27 convert to 42.2408333333333 42:14:27"

01:06:23.321 RightAscension            Get - 04:29:43 convert to 4.49527777777778 04:29:43
01:06:23.384 Declination               Get - +42[DF]14:43 convert to 42.2452777777778 42:14:43"

01:06:23.758 RightAscension            Get - 04:29:45 convert to 4.49583333333333 04:29:45
01:06:24.148 Declination               Get - +42[DF]14:46 convert to 42.2461111111111 42:14:46"

01:06:37.065 RightAscension            Get - 04:29:55 convert to 4.49861111111111 04:29:55
01:06:37.096 Declination               Get - +42[DF]16:23 convert to 42.2730555555556 42:16:23"

01:06:40.980 RightAscension            Get - 04:29:56 convert to 4.49888888888889 04:29:56
01:06:41.012 Declination               Get - +42[DF]16:24 convert to 42.2733333333333 42:16:24"

01:06:41.214 RightAscension            Get - 04:29:56 convert to 4.49888888888889 04:29:56
01:06:41.246 Declination               Get - +42[DF]16:24 convert to 42.2733333333333 42:16:24"

01:06:45.036 RightAscension            Get - 04:29:56 convert to 4.49888888888889 04:29:56
01:06:45.114 Declination               Get - +42[DF]16:24 convert to 42.2733333333333 42:16:24"

01:06:49.170 RightAscension            Get - 04:29:54 convert to 4.49833333333333 04:29:54
01:06:49.202 Declination               Get - +42[DF]16:23 convert to 42.2730555555556 42:16:23"

01:06:53.211 RightAscension            Get - 04:29:55 convert to 4.49861111111111 04:29:55
01:06:53.242 Declination               Get - +42[DF]16:23 convert to 42.2730555555556 42:16:23"

01:07:01.682 RightAscension            Get - 04:29:56 convert to 4.49888888888889 04:29:56
01:07:01.713 Declination               Get - +42[DF]16:23 convert to 42.2730555555556 42:16:23"

01:07:18.592 RightAscension            Get - 04:29:55 convert to 4.49861111111111 04:29:55
01:07:18.623 Declination               Get - +42[DF]16:23 convert to 42.2730555555556 42:16:23"

Hypothesis
Hypothesis is that dialog pops up when Telescope.Jog (N/S)  is sent before a preceeding Telescope.Jog (E/W) has been completed.

Meade Generic Trace Log shows that Jog is being actioned by called Scope.SlewToCoordinatesAsync.   If execution returns immediately  then a second call to Jog could result in the message seen.

Conclusion:

Actions:
  Add a button function to mark occurances of "Unable to start the Direct Slew" dialog in log and report files.  (btnRecordDirectSlewIssue)

Update 2021-04-24 (Issue Fixed)

MeadeGeneric driver has now been fixed (1.0.1.327) so that Slewing Property returns the correct/appropriate value (property corrected to show the value TRUE when the scope is physically slewing or is still settling after a slew).   Issue confirmed to be fully fixed following  in session S890 (2021-04-24).

Update 2021-04-30 (Two further cases)

Whilst the primary reason behind problem was solved with v 1.0.1.327 version of the MeadeGeneric driver,  occasional residual cases of the issue evidently still occur. Two cases occurred in Session S893 (2021-04-30) which were investigated (see Investigation - JobQueue Freezing during Telescope.Jog, 2021-05-01 ).  Problem may relate to delay in DeviceHub.Telescope moving to a fast polling rate when a slew is requested. Hypothesis is that after a call to Telescope.Jog  the TheSky6 program doesn't see Slewing=True quick enough after requesting the slew and returns execution back to AstroMain client which then submits another jog before the first jog has finished.  A Scope.Jog routine has been added to AstroMain (3.39.7), that monitors the telescope's slewing property and only proceeds and makes a second Jog once the first jog is truely finished.

Issue : Majority of Slew Path on Slewing Chart are drawn as straight line paths and not the expected curved paths.  

Description.  Scope Slewing Graph on Dome/Scope Slewing Chart mostly show straight line path between starting coords and ending coordinates rather than curved path.  Issue is believed to be due to use of MeadeGeneric driver (Whilst some straight line path segments have previously occured when using DeviceHub.Telescope with MeadeLX200GPS driver these earlier issues had been fixed.)

Analysis :

Examining the slew to Target 4/17 (Nova Per 2020) at 01:05,  tabulated as a 25s slew from Az 280.0/Alt 62.2 to Az 331.0/Alt 14.9.

The Log file shows:

01:05:21.39 ObjectAzAlt            | Az = 331.7 Alt= 16.4 Airmass=3.52
01:05:21.76 SlewTheSkyScopeToRaDec | Calling SlewTheSkyScope(RaDec)
01:05:21.76 PreSlew AzAlt(Scope)   | Az= 280.0 Alt=62.2
01:05:21.78 PreSlew Az(Dome)       | Az: 274.6
01:05:21.78 Set Telescope          | Setting Telescope.Asynchronous = 1
01:05:21.78 Slew Scope             | Calling Telescope.SlewToRaDec
01:05:21.78 Slew Scope(Coords)     | Ra= 04 30 44.435 Dec=+43 58 28.83 | Epoch Current
01:05:21.78 ScopePath              | Az: 280.04, Alt: 62.15, Slew: 0.000, Time: 0.0
01:05:23.51 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 1.7
01:05:25.57 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 3.8 Angular Change: 0.00 (Static)
01:05:25.75 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 4.0 Angular Change: 0.00 (Static)
01:05:25.96 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 4.2 Angular Change: 0.00 (Static)
01:05:26.16 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 4.4 Angular Change: 0.00 (Static)
01:05:26.36 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 4.6 Angular Change: 0.00 (Static)
01:05:26.57 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 4.8 Angular Change: 0.00 (Static)
01:05:26.77 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 5.0 Angular Change: 0.00 (Static)
01:05:26.97 ScopePath              | Az: 280.06, Alt: 62.14, Slew: 0.003, Time: 5.2 Angular Change: 0.00 (Static)
01:05:48.90 Set Telescope          | Setting Telescope.Asynchronous = 0
01:05:48.94 SlewAngle              | Total: 0.003, Direct: 102.065
01:05:48.94 SlewTime(Scope)        | Scope Slew Time = 24.7s
01:05:48.94 SlewTime(Dome)         | Dome Slew Time = 27.1s
01:05:48.94 SlewTime(Overall)      | Overall Slew Time =27.1s
01:05:50.46 PostSlewSettle         | Continuing (Telescope has already settled for >= 5 seconds)
01:05:50.46 PostSlew AzAlt(Scope)  | Az= 331.0 Alt=14.9
01:05:50.50 SlewSpeed(Scope)       | Scope Slew Speed= 4.1 deg/s | 102.1 degs in 25s

The slew is made using TheSky6.Telescope.SlewToRaDec in the Asynchonous mode.  and the routine then enters a monitoring loop that examines objScope.Azimuth & objScope.Altitude.  This loop indicates at a small initial movement of 0.003 degs but then no apparent movement of the scope during the perod 1.7s to 5s after the slew initiated The SlewTheSkyScope() routine assumes that the scope has finished slewing and stops further ScopePath tracing after 5s. The routine eventually realises that Scope Slew took a much longer time that the 1.7s initially recognised.

The Meade.Generic.Telescope trace file shows :

01:05:10.143 RightAscension             Get - 10:38:57 convert to 10.6491666666667 10:38:57
01:05:10.205 Declination                Get - +52[DF]00:51 convert to 52.0141666666667 52:00:51"

01:05:13.419 RightAscension             Get - 10:38:56 convert to 10.6488888888889 10:38:56
01:05:13.450 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"
01:05:13.466 Altitude                   62.1574785948659
01:05:13.669 RightAscension             Get - 10:38:56 convert to 10.6488888888889 10:38:56
01:05:13.700 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"
01:05:13.700 Azimuth Get                   280.033201368113
01:05:14.059 RightAscension             Get - 10:38:56 convert to 10.6488888888889 10:38:56
01:05:14.090 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"
01:05:14.152 RightAscension             Get - 10:38:56 convert to 10.6488888888889 10:38:56
01:05:14.183 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"
01:05:14.308 RightAscension             Get - 10:38:56 convert to 10.6488888888889 10:38:56
01:05:14.355 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"

01:05:17.522 RightAscension             Get - 10:38:58 convert to 10.6494444444444 10:38:58
01:05:17.600 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"
01:05:17.600 Altitude                   62.1530235230056
01:05:17.787 RightAscension             Get - 10:38:58 convert to 10.6494444444444 10:38:58
01:05:17.834 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"
01:05:17.849 Azimuth Get                   280.038761474126
01:05:18.005 Slewing                    Result = False
01:05:18.676 RightAscension             Get - 10:38:57 convert to 10.6491666666667 10:38:57
01:05:18.723 Declination                Get - +52[DF]00:52 convert to 52.0144444444444 52:00:52"
01:05:18.770 IsSlewingToTarget          IsSlewing = False : result =
01:05:18.801 RightAscension             Get - 10:38:57 convert to 10.6491666666667 10:38:57
01:05:18.832 Declination                Get - +52[DF]00:52 convert to 52.0144444444444 52:00:52"
01:05:18.879 RightAscension             Get - 10:38:57 convert to 10.6491666666667 10:38:57
01:05:18.926 Declination                Get - +52[DF]00:52 convert to 52.0144444444444 52:00:52"

(>>05:21.78  >> Calling Telescope.SlewToRaDec with asynchronous mode True  << from client log )
01:05:21.796 SlewToCoordinatesAsync     Ra=4.49683650985014, Dec=42.2146667961722

01:05:22.077 RightAscension             Get - 10:38:58 convert to 10.6494444444444 10:38:58
01:05:22.108 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"
01:05:22.108 Altitude                   62.1419165044871
01:05:22.108 TargetRightAscension Set   4.49683650985014
01:05:22.108 TargetRightAscension Set   :Sr04:29.81#
01:05:22.139 TargetDeclination Set      42.2146667961722
01:05:22.139 TargetDeclination Set      :Sd+42*12.88#
01:05:22.373 DoSlewAsync                Slewing to target
01:05:22.373 SlewSettleTime Get         0 Seconds

01:05:22.904 RightAscension             Get - 10:38:57 convert to 10.6491666666667 10:38:57
01:05:22.951 Declination                Get - +52[DF]00:56 convert to 52.0155555555556 52:00:56"
01:05:22.951 Azimuth Get                   280.055385597346
01:05:23.200 IsSlewingToTarget          IsSlewing = False : result = [7F]
01:05:23.200 Slewing                    Result = False
(>>05:26.77  >> 5.0s after slew started << from client log )

01:05:26.882 RightAscension             Get - 09:55:56 convert to 9.93222222222222 09:55:56
01:05:26.960 Declination                Get - +45[DF]26:18 convert to 45.4383333333333 45:26:18"
01:05:26.960 Altitude                   52.5528141630356
01:05:27.319 RightAscension             Get - 09:55:51 convert to 9.93083333333333 09:55:51
01:05:27.677 Declination                Get - +43[DF]37:50 convert to 43.6305555555556 43:37:50"
01:05:27.677 Azimuth Get                   275.559882985181
01:05:27.958 IsSlewingToTarget          IsSlewing = False : result = [7F]
01:05:27.958 Slewing                    Result = False

01:05:31.624 RightAscension             Get - 08:36:15 convert to 8.60416666666667 08:36:15
01:05:31.687 Declination                Get - +42[DF]15:18 convert to 42.255 42:15:18"
01:05:31.687 Altitude                   39.9054840611718
01:05:31.983 RightAscension             Get - 08:16:14 convert to 8.27055555555556 08:16:14
01:05:32.014 Declination                Get - +42[DF]15:18 convert to 42.255 42:15:18"
01:05:32.030 Azimuth Get                   292.111872198048
01:05:32.061 Declination                Get - +42[DF]14:09 convert to 42.2358333333333 42:14:09"
01:05:32.451 RightAscension             Get - 08:16:26 convert to 8.27388888888889 08:16:26
01:05:32.654 IsSlewingToTarget          IsSlewing = False : result = [7F]
01:05:32.654 Slewing                    Result = False

01:05:36.320 RightAscension             Get - 06:56:54 convert to 6.94833333333333 06:56:54
01:05:36.382 Declination                Get - +42[DF]14:01 convert to 42.2336111111111 42:14:01"
01:05:36.398 Altitude                   27.9895722724924
01:05:36.694 RightAscension             Get - 06:38:09 convert to 6.63583333333333 06:38:09
01:05:36.741 Declination                Get - +42[DF]14:01 convert to 42.2336111111111 42:14:01"
01:05:36.741 Azimuth Get                   308.709790435548
01:05:37.115 Declination                Get - +42[DF]15:42 convert to 42.2616666666667 42:15:42"
01:05:37.162 RightAscension             Get - 06:38:09 convert to 6.63583333333333 06:38:09
01:05:37.349 IsSlewingToTarget          IsSlewing = False : result = [7F]
01:05:37.349 Slewing                    Result = False

01:05:41.000 RightAscension             Get - 05:18:04 convert to 5.30111111111111 05:18:04
01:05:41.094 Declination                Get - +42[DF]14:01 convert to 42.2336111111111 42:14:01"
01:05:41.094 Altitude                   18.4121322706165
01:05:41.406 RightAscension             Get - 05:17:38 convert to 5.29388888888889 05:17:38
01:05:41.437 Declination                Get - +42[DF]14:01 convert to 42.2336111111111 42:14:01"
01:05:41.452 Azimuth Get                   322.552961088593
01:05:41.842 Declination                Get - +42[DF]14:27 convert to 42.2408333333333 42:14:27"
01:05:41.936 RightAscension             Get - 04:57:45 convert to 4.9625 04:57:45
01:05:42.061 IsSlewingToTarget          IsSlewing = False : result = [7F]
01:05:42.061 Slewing                    Result = False

01:05:45.711 RightAscension             Get - 04:30:50 convert to 4.51388888888889 04:30:50
01:05:45.774 Altitude                   14.9031767431447
01:05:45.992 RightAscension             Get - 04:29:50 convert to 4.49722222222222 04:29:50
01:05:46.039 Declination                Get - +42[DF]14:01 convert to 42.2336111111111 42:14:01"
01:05:46.054 Azimuth Get                   331.024002395054
01:05:46.257 IsSlewingToTarget          IsSlewing = False : result = [7F]
01:05:46.257 Slewing                    Result = False
01:05:46.132 RightAscension             Get - 04:29:50 convert to 4.49722222222222 04:29:50
01:05:45.774 Declination                Get - +42[DF]14:01 convert to 42.2336111111111 42:14:01"
(>>05:48.94  >> ~ Slew Finished   : << from client log)

01:05:50.017 Altitude                   14.831139934357
01:05:50.750 Azimuth Get                   331.032840343473
01:05:50.984 IsSlewingToTarget          IsSlewing = False : result = [7F]
01:05:50.984 Slewing                    Result = False

01:05:54.931 Altitude                   14.8238065637338
01:05:55.165 Azimuth Get                   331.035757668424
01:05:55.336 IsSlewingToTarget          IsSlewing = False : result =
01:05:55.336 Slewing                    Result = False
01:05:59.018 Altitude                   14.8224452946673
01:05:59.252 Azimuth Get                   331.041669370593
01:05:59.424 IsSlewingToTarget          IsSlewing = False : result =
01:05:59.424 Slewing                    Result = False

Conclusion:
It would seem that Meade Generic isn't updating the Slewing property, and DeviceHub therefore doesn't recognise that Scope is slewing and doesn't move to Fast Polling.
The SlewTheSkyScope() routine currently assumes that fast polling will have begun before 5s have passed,  and doesn't recognosize that the first  coordinate set with 'significantly moved' coordinates may not be received until some 6s or 7s after slewing has started.

It is likely that 5s settle period added by  Scope.SlewTheSkyScope()  , isn't always getting added because AstroMains sometimes think that scope hasn't moved for 5s so that a 5s settle has already been taken up.   This might explain why some images during session show wobbly trailed star traces indicative of the scope still settling following a slew.

Actions:
  AstroMain. Modify AstroMain's SlewTheSkyScope() routine so that at least 8s is waited before concluding that a telescope slew has finished.
  Meade Generic. Contact MeadeGeneric author to report that Slewing Property isn't being updated to True during a slew, and request a fix.
  Meade Generic. Contact MeadeGeneric author to report inconsistency in formtting of Get Property messages in the Meade.Generic.Telescope trace file.

Update 2021-04-24 (Issue Fixed)

MeadeGeneric driver has now been fixed (1.0.1.327) so that Slewing Property returns the correct/appropriate value (property corrected to show the value TRUE when the scope is physically slewing or is still settling after a slew).   Issue confirmed to be fully fixed following  in session S890 (2021-04-24).

Issue : Scope appearing to slew anti-clockwise across the Due North Plane from Az 43.9° to Az 358.6° (a critical violation)              

Description.  Session S888 unexpectedly closed & finished before acquiring Target 18/18.   Although logs say 'Script (Active Plan) was aborted by the user' it would seem that it was aborted by the Job queue manager when it was found that the scope had moved to unsafe area beyond Az 349° (ie the az 349 to 360°) with alt < 65° from a position at Az 43.9° / Alt  22°

> Telescope Safety            Alert     2021-04-21 03:36 (Local)
> Telescope Safety            Alert     Telescope has moved beyond  Az 349°
  Turn Off Tracking..         Ok        Telescope Tracking is OFF
> Telescope Safety            Action    Telescope will be moved to a safe position
  Scope Speed:                Info      24.5 deg/s        (307.7 degs in 13s)

Slew table indicates that the scope moved from Az 43.9/Alt 22 to Az 358.6/Alt 34.3 (in 13s).

                    Az1  Az2   Alt1 Alt2 Time Angle Speed
C/2020 T2 (Palomar) 43.9 358.6 22.0 34.3 13s  307.7 24.50

Since the scope has seemed to have crossed from the NE sky to the adjacent NNW sky (moving across Az 0 (due north)  this is taken to be a critical violation since equipment could be damaged due to cable wraping around the pier

Analysis :

Prior to slew to Target 17/18 (C/2020 T2 (Palomar) the scope was as at Az 43.9 / Alt 22.0.   This appears to where the scope happened to be after

• centering Jog for Locate Frame 1 -3  of Target 13/18 (61 Cyg) had warning messages 'Telescope.Jog task In MakeJogCorrection/JogS Is taking a Long time?'
   
• centering Jog for Locate Frame 1 of Target 14/18 (AT2021hkn) had a warning message 'Telescope.Jog task In MakeJogCorrection/JogS Is taking a Long time?'
   
• slew to Target 15/18 (GCVS HH And, Target Az 47.9 / Alt 26.4) at 03:26  failed with message "Scope isn't pointing to the target (Ang Sep. = 1.6 arc degs) Possible 'Timed out waiting for received data' problem ? "  and
   
•  slew to Target 16/18 (WDS GRB 34, Target Az 42.2 / Alt 22.9) at 03:28 failed with message "Scope isn't pointing to the target (Ang Sep. = 7.7 arc degs).   Possible 'Timed out waiting for received data' problem ?".

After waiting 8 minutes the scope attempted slew to Target 17/18 (C/2020 T2 (Palomar, Target Az 244.0 / Alt 55.1).

ObsPics show the following

03:36:35 : scope at Az 44 / Alt 22 and slewing to Target C/2020 T2 (Palomar),
03:37:06 : scope at Az 283 / Alt 65 with Tracking Off and Dome Closing.
03:37:38 : scope at Az 245 / Alt 10 with Tracking Off (Dome nearly closed).

Log file show the following

03:36:34 : scope at Az 43.9 / Az 22.0.  
03:36:49 : scope.SetTrackingOff,
03:36:51 : scope at Az= 358.6 Alt=34.3. 

ObsCam Images show the following

03:36:37 : scope stationary at position consistent with Az 43.9 / Alt 22.0
03:36:38 : scope beginning to slew

03:36:39 to 43:   scope slewing clockwise

03:36:44:  scope slewing clockwise at  ~ Az 90  (but TeleComm fields reports scope at Az 25.2 / Alt 21.7
03:36:49 : scope slewing clockwise at  ~ Az 110  (but TeleComm fields reports scope slewing at Az 358.6 / Alt 34.3
03:37:00 : scope slewing clockwise at  ~ Az 180 (but TeleComm fields reports scope stationary at Az 108.9/ Alt 47.6
03:37:05 : scope slewing clockwise at ~ Az  200 (but  TeleComm fields reports scope stationary at Az 282.9/ Alt 65.0
03:37:11 : scope at position at ~ Az 220 -  244.0 ?  / ? Alt 55  (but  TeleComm fields reports scope stationary at Az 261.3 Alt 65.6

Scope was being operated with MeadeGeneric 1.0.0.296 driver and DeviceHub

Conclusion:
It is would seem that telescope positions reported from the driver somehow became incorrect at or before 03:36 and led to the warning that the scope had appeared to have crossed clockwise over the Due North Plane. It is absolutely clear from ObsCam images that the scope itself was operating correctly and was rotating clockwise towards the Target 17/18 (C/2020 T2 (Palomar) with no danger of wrapping the cables around the pier or crashing into the scope Azimuth stops.

It is concluded that the issue is somehow related to flaw/issues in the MeadeGeneric 1.0.0.296 driver and/or initialisation of the LX200 at startup. These flaws/issues have since been corrected.  The issue 'Scope appearing to slew across Due North Plane' is therefore tentatively closed.

Update 2021-08-13
Issue resurfaced in some later sessions, e.g S902 (2021-07-24) & S904 (2021-08-09).  Reinvestigating the issue an anomaly was found in the reporting of RA positions by the LX200GPS/R telescope during certain slew.  For example is S904 Target 12/17, (AT2021hkn / Nova Cas 2021 (02:29:32 to 02:29:59)  involved a slew from RA 00h 45’ / Dec 39° 45’ to Ra 23h 26’ / 61° 08’ (ie. a slew of about 24 degs).    Whilst the reported Dec positions show a normal path from 39° 45’ to 61° 08’, the reported Ra positions show an unexpected “long-route path” route  from 00h 45’ to 12h 00’ to 23h 26m , instead of the expected “short-route”  & indeed actual telescope path from 00h 45’ to 00h 00’ to 23h 59’ to 23h 26’.    A workaround was adopted in AstroMain 3.40.9 (2021-08-13 ) by making SlewTheSkyScope() function access Scope.Az/Alt values direct from the telescope rather calculating Az/Alt from the reported Scope.Ra/Dec position which may sometimes have invalid values during slewing.