Meridian flip failed

Glass17

NINA configured with 5 minutes after meridian flips and 15 minutes max after meridian flip.
Approximately 5 minutes after meridian flip or a little bit early mount stop still with no diagnostic.
Tracking reports ON.
Guider stars drift as would not be tracking.
No cables snagging or tension or whatever.
A lot of space before hitting mount, may be one more RA hour to go.
It looks like mount reached some internal limit and blocked tracking.
Issue was resolved by manual moving mount back cross meridian and re-enabling NINA sequence, as the result "Centre after drift" triggered slew command which moved mount to other side of the pier.

Glass17

The same issue tonight. On the same place. Mount freeze slightly after meridian and before 5 minutes after meridian flip

Moved by buttons back and resumed NINA session to unblock the mount

PMTeam@ZWO

Glass17 Could you please note the NINA and ASCOM etc. versions, then we can try to reproduce that issue. Thank you.

Glass17

Failed third night, second object:
Stopped tracking 11!!! minutes before meridian

NINA

2022-08-31T03:59:47.0260|INFO|MeridianFlipTrigger.cs|ShouldTrigger|261|Meridian Flip - There is still time remaining - max remaining time 00:15:07, next instruction time 120, next instruction Category: Camera, Item: TakeExposure, ExposureTime 120, Gain 100, Offset 250, ImageType LIGHT, Binning 1x1 - and the telescope reports expected pier side pierWest. Automated Flip is not necessary.
2022-08-31T03:59:47.0260|INFO|SequenceItem.cs|Run|206|Starting Category: Camera, Item: TakeExposure, ExposureTime 120, Gain 100, Offset 250, ImageType LIGHT, Binning 1x1
2022-08-31T03:59:47.0270|INFO|CameraVM.cs|Capture|726|Starting Exposure - Exposure Time: 120s; Filter: ; Gain: 100; Offset 250; Binning: 1x1;
2022-08-31T03:59:47.4660|DEBUG|BaseImageData.cs|PrepareSave|111|Saved temporary image at C:\N.I.N.A\e72cb93e-98f7-4f77-b6ee-951942da9646.fits
2022-08-31T03:59:47.4670|DEBUG|Utility.cs|CalculateSunSeparation|96|Sun angle: 122.63
2022-08-31T03:59:47.4670|DEBUG|Utility.cs|CalculateMoonSeparation|43|Moon angle: 158.68
2022-08-31T03:59:47.4680|INFO|BaseImageData.cs|FinalizeSave|163|Saving image at C:\N.I.N.A\LIGHT_30.00s\2022-08-30_M_33\M_33_ATR3CMOS26000KMA_FLEN910_ANGL0.00_B_G100_OFS250_1x1_30.00s_2022-08-31_03-59-11-15.00C.fits
2022-08-31T03:59:47.6250|DEBUG|SessionMetaDataWatcher.cs|GetOutputDirectory|458|MetaDataOutputDirectory is empty, defaulting to image save directory
2022-08-31T03:59:47.6250|DEBUG|SessionMetaDataWatcher.cs|WriteAcquisitionMetaData|69|AcquisitionDetails file name: AcquisitionDetails -> C:\N.I.N.A\LIGHT_30.00s\2022-08-30_M_33\AcquisitionDetails
2022-08-31T03:59:47.6260|DEBUG|SessionMetaDataWatcher.cs|WriteImageMetaData|111|ImageMetaData file name: ImageMetaData -> C:\N.I.N.A\LIGHT_30.00s\2022-08-30_M_33\ImageMetaData
2022-08-31T03:59:47.6260|INFO|SessionMetaDataWatcher.cs|WriteImageMetaData|132|Writing JSON image metadata: C:\N.I.N.A\LIGHT_30.00s\2022-08-30_M_33\ImageMetaData.json
2022-08-31T03:59:48.3630|INFO|ImageSolver.cs|Solve|41|Platesolving with parameters: FocalLength: 910 PixelSize: 3.76 SearchRadius: 30 BlindFailoverEnabled: True Regions: 5000 DownSampleFactor: 0 MaxObjects: 500 Reference Coordinates RA: 01:33:45 Dec: 30° 35' 34" Epoch: J2000
2022-08-31T03:59:49.0500|INFO|BaseImageData.cs|FinalizeSave|163|Saving image at C:\Users\virog\AppData\Local\NINA\PlateSolver\0kejym3v.wcy.fits
2022-08-31T03:59:49.0500|DEBUG|CLISolver.cs|StartCLI|162|Starting process 'C:\Program Files\astap\astap.exe' with args '-f "C:\Users\virog\AppData\Local\NINA\PlateSolver\0kejym3v.wcy.fits" -fov 0.986727 -z 0 -s 500 -r 30 -ra 1.562546 -spd 120.592746'
2022-08-31T03:59:49.3290|DEBUG|SessionHistoryVersionManager.cs|flushQueue|79|flushing session history queue, 1 items
2022-08-31T03:59:49.3290|DEBUG|SessionHistoryVersionManager.cs|flushQueue|84|writing session history, version 299
2022-08-31T03:59:51.8450|INFO|ImageSolver.cs|Solve|54|Platesolve successful: Coordinates: RA: 01:33:44; Dec: 30° 35' 43"; Epoch: J2000
2022-08-31T03:59:51.8460|INFO|CenterAfterDriftTrigger.cs|PlatesolvingImageFollower_PropertyChanged|192|Drift: 0.197859580678636 / 0.75 arc minutes
2022-08-31T04:01:47.8349|DEBUG|ImageSaveController.cs|Enqueue|51|Enqueuing image to be saved with id 641
2022-08-31T04:01:47.8439|DEBUG|ImageSaveController.cs|DoWork|60|Dequeuing image to be saved with id 641
2022-08-31T04:01:48.0009|INFO|SequenceItem.cs|Run|224|Finishing Category: Camera, Item: TakeExposure, ExposureTime 120, Gain 100, Offset 250, ImageType LIGHT, Binning 1x1
2022-08-31T04:01:48.0169|INFO|SequenceTrigger.cs|Run|114|Starting Trigger: DitherAfterExposures, After Exposures: 0
2022-08-31T04:01:48.0169|INFO|SequenceTrigger.cs|Run|114|Starting Trigger: DitherAfterExposures, After Exposures: 7
2022-08-31T04:01:48.0169|INFO|SequenceItem.cs|Run|206|Starting Category: * Instruction Set *, Item: NINA.Sequencer.Container.SequentialContainer, Strategy: SequentialStrategy, Items: 1, Conditions: Triggers:
2022-08-31T04:01:48.0169|INFO|SequenceItem.cs|Run|206|Starting Category: Guider, Item: Dither
2022-08-31T04:01:48.0249|DEBUG|PHD2Guider.cs|SendMessage|753|Phd2 - Sending message '{"id":"99","method":"get_app_state"}'
2022-08-31T04:01:48.3939|DEBUG|PHD2Guider.cs|SendMessage|773|Phd2 - Received message answer '{"jsonrpc":"2.0","result":"Guiding","id":"99"}'
2022-08-31T04:01:48.3939|DEBUG|PHD2Guider.cs|SendMessage|753|Phd2 - Sending message '{"id":"5","method":"dither","params":{"amount":2.0,"raOnly":false,"settle":{"pixels":0.25,"time":5,"timeout":30}}}'
2022-08-31T04:01:48.5479|DEBUG|PHD2Guider.cs|ProcessEvent|936|PHD2 - Lock position set at x:270.694 y:842.401
2022-08-31T04:01:48.5649|DEBUG|PHD2Guider.cs|SendMessage|773|Phd2 - Received message answer '{"jsonrpc":"2.0","result":0,"id":"5"}'
2022-08-31T04:01:50.0629|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 0, Distance: 0.91
2022-08-31T04:01:50.6939|DEBUG|StarDetector.cs|ModelPSF|327|Modeling PSFs using a parallel partition size of 100 and a pixel scale of 0.852258979658332 arcsec/pixel
2022-08-31T04:01:52.6218|INFO|HocusFocusStarDetection.cs|Detect|367|Average HFR: 2.22720103979638, HFR σ: 0.374465842183991, Detected Stars 953
2022-08-31T04:01:52.9309|DEBUG|Utility.cs|CalculateSunSeparation|96|Sun angle: 122.64
2022-08-31T04:01:52.9318|DEBUG|Utility.cs|CalculateMoonSeparation|43|Moon angle: 158.69
2022-08-31T04:01:52.9328|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 0, Distance: 0.65
2022-08-31T04:01:53.5228|DEBUG|BaseImageData.cs|PrepareSave|111|Saved temporary image at C:\N.I.N.A\fee7acc8-79ea-4f92-9139-5fb78b9b3786.fits
2022-08-31T04:01:53.5238|DEBUG|Utility.cs|CalculateSunSeparation|96|Sun angle: 122.64
2022-08-31T04:01:53.5248|DEBUG|Utility.cs|CalculateMoonSeparation|43|Moon angle: 158.69
2022-08-31T04:01:53.5258|INFO|BaseImageData.cs|FinalizeSave|163|Saving image at C:\N.I.N.A\LIGHT_120.00s\2022-08-30_M_33\M_33_ATR3CMOS26000KMA_FLEN910_ANGL0.00_L_G100_OFS250_1x1_120.00s_2022-08-31_03-59-47-15.10C.fits
2022-08-31T04:01:53.6148|DEBUG|SessionMetaDataWatcher.cs|GetOutputDirectory|458|MetaDataOutputDirectory is empty, defaulting to image save directory
2022-08-31T04:01:53.6148|DEBUG|SessionMetaDataWatcher.cs|WriteAcquisitionMetaData|69|AcquisitionDetails file name: AcquisitionDetails -> C:\N.I.N.A\LIGHT_120.00s\2022-08-30_M_33\AcquisitionDetails
2022-08-31T04:01:53.6158|DEBUG|SessionMetaDataWatcher.cs|WriteImageMetaData|111|ImageMetaData file name: ImageMetaData -> C:\N.I.N.A\LIGHT_120.00s\2022-08-30_M_33\ImageMetaData
2022-08-31T04:01:53.6158|INFO|SessionMetaDataWatcher.cs|WriteImageMetaData|132|Writing JSON image metadata: C:\N.I.N.A\LIGHT_120.00s\2022-08-30_M_33\ImageMetaData.json
2022-08-31T04:01:54.3608|INFO|ImageSolver.cs|Solve|41|Platesolving with parameters: FocalLength: 910 PixelSize: 3.76 SearchRadius: 30 BlindFailoverEnabled: True Regions: 5000 DownSampleFactor: 0 MaxObjects: 500 Reference Coordinates RA: 01:33:45 Dec: 30° 35' 34" Epoch: J2000
2022-08-31T04:01:54.4888|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 0, Distance: 0.51
2022-08-31T04:01:55.1188|INFO|BaseImageData.cs|FinalizeSave|163|Saving image at C:\Users\virog\AppData\Local\NINA\PlateSolver\maq2bckl.2tf.fits
2022-08-31T04:01:55.1188|DEBUG|CLISolver.cs|StartCLI|162|Starting process 'C:\Program Files\astap\astap.exe' with args '-f "C:\Users\virog\AppData\Local\NINA\PlateSolver\maq2bckl.2tf.fits" -fov 0.986727 -z 0 -s 500 -r 30 -ra 1.562546 -spd 120.592746'
2022-08-31T04:01:55.9318|DEBUG|SessionHistoryVersionManager.cs|flushQueue|79|flushing session history queue, 1 items
2022-08-31T04:01:55.9318|DEBUG|SessionHistoryVersionManager.cs|flushQueue|84|writing session history, version 300
2022-08-31T04:01:56.0118|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 0, Distance: 0.42
2022-08-31T04:01:58.0458|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 0, Distance: 0.4
2022-08-31T04:01:58.9128|INFO|ImageSolver.cs|Solve|54|Platesolve successful: Coordinates: RA: 01:33:44; Dec: 30° 35' 42"; Epoch: J2000
2022-08-31T04:01:58.9128|INFO|CenterAfterDriftTrigger.cs|PlatesolvingImageFollower_PropertyChanged|192|Drift: 0.197045800839918 / 0.75 arc minutes
2022-08-31T04:01:59.5678|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 0, Distance: 0.36
2022-08-31T04:02:01.0818|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 0, Distance: 0.31
2022-08-31T04:02:02.6018|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 0, Distance: 0.24
2022-08-31T04:02:04.6258|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 2, Distance: 0.21
2022-08-31T04:02:06.1658|DEBUG|PHD2Guider.cs|ProcessEvent|887|PHD2 settling started. Time: 3, Distance: 0.21
2022-08-31T04:02:07.6888|DEBUG|PHD2Guider.cs|ProcessEvent|898|PHD2 settle completed
2022-08-31T04:02:08.1298|INFO|SequenceItem.cs|Run|224|Finishing Category: Guider, Item: Dither
2022-08-31T04:02:08.1298|INFO|SequenceItem.cs|Run|224|Finishing Category: * Instruction Set *, Item: NINA.Sequencer.Container.SequentialContainer, Strategy: SequentialStrategy, Items: 1, Conditions: Triggers:
2022-08-31T04:02:08.1298|INFO|SequenceItem.cs|Run|206|Starting Category: Filter Wheel, Item: SwitchFilter, Filter: L
2022-08-31T04:02:08.1308|INFO|SequenceItem.cs|Run|224|Finishing Category: Filter Wheel, Item: SwitchFilter, Filter: L
2022-08-31T04:02:08.1388|INFO|SequenceTrigger.cs|Run|114|Starting Trigger: DitherAfterExposures, After Exposures: 0
2022-08-31T04:02:08.1388|INFO|SequenceTrigger.cs|Run|114|Starting Trigger: RestoreGuiding
2022-08-31T04:02:08.1398|INFO|SequenceItem.cs|Run|206|Starting Category: * Instruction Set *, Item: NINA.Sequencer.Container.SequentialContainer, Strategy: SequentialStrategy, Items: 1, Conditions: Triggers:
2022-08-31T04:02:08.1398|INFO|SequenceItem.cs|Run|206|Starting Category: Guider, Item: StartGuiding
2022-08-31T04:02:08.1398|DEBUG|PHD2Guider.cs|SendMessage|753|Phd2 - Sending message '{"id":"99","method":"get_app_state"}'
2022-08-31T04:02:08.1698|DEBUG|PHD2Guider.cs|SendMessage|773|Phd2 - Received message answer '{"jsonrpc":"2.0","result":"Guiding","id":"99"}'
2022-08-31T04:02:08.1698|INFO|PHD2Guider.cs|StartGuidingPrivate|464|Phd2 - App is already guiding. Skipping start guiding
2022-08-31T04:02:08.1698|INFO|SequenceItem.cs|Run|224|Finishing Category: Guider, Item: StartGuiding
2022-08-31T04:02:08.1708|INFO|SequenceItem.cs|Run|224|Finishing Category: * Instruction Set *, Item: NINA.Sequencer.Container.SequentialContainer, Strategy: SequentialStrategy, Items: 1, Conditions: Triggers:
2022-08-31T04:02:08.1938|DEBUG|AutofocusAfterHFRIncreaseTrigger.cs|ShouldTrigger|214|Autofocus condition extrapolated original HFR: 2.20703555588585 extrapolated current HFR: 2.22894002808695
2022-08-31T04:02:08.1938|INFO|SequenceItem.cs|Run|206|Starting Category: Camera, Item: TakeExposure, ExposureTime 120, Gain 100, Offset 250, ImageType LIGHT, Binning 1x1
2022-08-31T04:02:08.1948|INFO|CameraVM.cs|Capture|726|Starting Exposure - Exposure Time: 120s; Filter: ; Gain: 100; Offset 250; Binning: 1x1;
2022-08-31T04:04:08.9866|DEBUG|ImageSaveController.cs|Enqueue|51|Enqueuing image to be saved with id 642
2022-08-31T04:04:08.9966|DEBUG|ImageSaveController.cs|DoWork|60|Dequeuing image to be saved with id 642
2022-08-31T04:04:09.1576|INFO|SequenceItem.cs|Run|224|Finishing Category: Camera, Item: TakeExposure, ExposureTime 120, Gain 100, Offset 250, ImageType LIGHT, Binning 1x1
2022-08-31T04:04:09.1736|INFO|SequenceTrigger.cs|Run|114|Starting Trigger: DitherAfterExposures, After Exposures: 0
2022-08-31T04:04:09.1736|INFO|MeridianFlipTrigger.cs|ShouldTrigger|200|Meridian Flip - Telescope is not tracking. Skip flip evaluation

Glass17

Running NINA Version 2.0.1.9001
ASCOM 6.6.0.3444

Glass17

Today it is reoccurred one second object and at exactly the same 12 or 11 minutes before meridian flip (according NINA); but AM5 log showed Azimuth 182.5 and repeating "It might hit the tripod legs after meridian flip so tracking has been stopped". There was not meridian flip, but it is happens during (in the middle) of 120 second exposure.

03:59:53.283 PulseGuide Set Direction: guideNorth, Duration: 14
03:59:53.342 <-- W#
03:59:53.342 SideOfPier W
03:59:53.342 --> :Mgn0014#
03:59:53.344 Slewing Get
03:59:53.344 --> :GU#
03:59:53.357 PulseGuide Over
03:59:53.357 IsPulseGuiding Get False
03:59:53.451 <-- NG0181211#
03:59:53.451 Slewing Get False
03:59:53.452 CanSetGuideRates Get True
03:59:53.452 GuideRateRightAscension G
03:59:53.452 --> :Ggr#
03:59:53.560 <-- 0.50#
03:59:53.560 GuideRateRightAscension 0.5
03:59:53.561 CanSetGuideRates Get True
03:59:53.562 GuideRateDeclination Get
03:59:53.562 --> :Ggr#
03:59:53.668 <-- 0.50#
03:59:53.668 GuideRateDeclination 0.5
03:59:53.806 RightAscension Get
03:59:53.807 --> :GR#
03:59:53.915 <-- 01:35:02#
03:59:53.915 RightAscension 01:35:02
03:59:53.915 Declination Get
03:59:53.915 --> :GD#
03:59:54.023 <-- +3042:28#
03:59:54.023 Declination 30:42:28"
03:59:54.023 Azimuth Get
03:59:54.024 --> :GZ#
03:59:54.131 <-- 18232:28#
03:59:54.131 Azimuth 18232:28#
03:59:54.131 Altitude Get
03:59:54.132 --> :GA#
03:59:54.241 <-- +7012:52#
03:59:54.241 Altitude +70*12:52#
03:59:54.242 CanSlewAsync Get True
03:59:54.242 Slewing Get
03:59:54.242 --> :GU#
03:59:54.350 <-- nNG0080210#
03:59:54.350 Slewing Get False
03:59:54.350 Tracking Get
03:59:54.351 --> :GAT#
03:59:54.461 <-- e8#
03:59:54.464 Tracking It might hit the tripod legs after meridian flip so tracking has been stopped
03:59:54.464 Tracking False
03:59:54.476 --> :GU#
03:59:54.588 <-- nNG0080210#
03:59:54.589 --> :GAT#
03:59:54.680 AtPark Get Do not support Park
03:59:54.680 AtHome Get
03:59:54.699 <-- e8#
03:59:54.699 FreshUIThead It might hit the tripod legs after meridian flip so tracking has been stopped
03:59:54.699 --> :GU#
03:59:54.704 IsPulseGuiding Get False
03:59:54.704 PulseGuide Set Direction: guideWest, Duration: 438
03:59:54.813 <-- nNG0080210#
03:59:54.813 AtHome False
03:59:54.813 --> :Mgw0438#
03:59:54.814 CanSetTracking Get True
03:59:54.815 CanSetDeclinationRate Get True
03:59:54.815 CanSetRightAscensionRate True
03:59:54.816 Tracking Get
03:59:54.816 --> :GAT#
03:59:54.921 <-- e8#

Walf@ZWO

AM5 will stop after ML now indeed

Glass17

So, we need to stop the session a few minutes before the meridian, wait for a few minutes after the meridian, and only then tmake a flip?
This is not what we do with other ASCOM mounts.
There must be some overlap, at least 15-20 minutes, when the mount can move behind the meridian line?

Could you share instructions on setting up AM5 for automation flip in NINA and other applications?

ajobacho

I have the same issue. The problem is that ASCOM and NINA (or Stellarium) don't have the same Az/Alt coordinates as you can see in the picture. So, the mount stops when thinks that has arrived to meridian, but NINA send the order for flipping later. I have observed that if the hand controller is connected and I use the ASI Mount app to go to an object, there not any difference and the coordinates between ASCOM and Stellarium coincide.

Glass17

ajobacho Try to check off "Daylight Saving time".
I think they still have this one hour in RA difference>

kaiyung

I use Nina exclusively and am about to test out my AM5, so I am very interested in seeing this issue resolved.

Kai

ajobacho

Glass17 Thank you, this solution works, now the coordinates are similar, but is a temporary solution until october when the Dayling Saving Time will be off in Spain.

kaiyung

ajobacho since you are using NINA with AM5, do you experience the dithering issue referenced in another thread in this mount forum?

ajobacho

kaiyung I haven't checked that. I'll check it today or tomorrow if the clouds allow it.

ajobacho

Hello, last night I could make some test although it was cloudy. I observed some things:

Coordinates of NINA and ASCOM ar equal, but not with Stellarium.
If I use Stellarium to go to an objet at east of meridian and near of it, the mount goes to east instead west as it thinks that the object has passed the meridian.
The mount did the meridian flip one our before that the object past meridian.
One thing very curious: The mount is not able to go to any object near of the celestian equator. For example, with M2 (near of the equator) NINA was making plate solves and slews to M2 a lot of times but never arrived to M2. Also it is not was possible to go with ASCOM arrows, only using the hand controller or the app it was possible.
There wasn't any problem with PHD2 dithering.

Attach a picture attempting to go to star Heze near of equator, it is impossilble with Stellarium or with the ASCOM arrows.

w7ay

ajobacho If I use Stellarium to go to an objet at east of meridian and near of it, the mount goes to east instead west as it thinks that the object has passed the meridian.

The mount did the meridian flip one [h]our before that the object past meridian.

Check the time setting for Stellarium, specifically accounting for Daylight Saving Time (1 hour difference).

Chen

ajobacho

Here is part of the log

ascomasimount2247416390.txt

2MB

ajobacho

Stellarium has the time and coordinates correct, the mount and NINA has the coordinates wrong. When I put Daylight Saving off in the ASCOM AM5 driver all is sincronised an working correctly. The only problem is , that sometimes the meridian flip doesn't happen because the mount arrives to its limit and stops before NINA send the order to flip.
I'll open a ticket to send the complete log of this night

w7ay

ajobacho Stellarium has the time and coordinates correct, the mount and NINA has the coordinates wrong.

Mounts will stop tracking when they have reached the Meridian Limit. In the case of the AM5, I surmise that the Meridian Limit is today fixed at the Meridian itself.

After a target has transited the Meridian (i.e., when Local Sidereal Time minus Right Ascension has turned into a negative number), a GOTO command that is sent to a German mount will cause the mount to perform a Meridian Flip. I.e., a German mount will perform a Meridian flip upon receiving a GOTO command when the mount discovers that the target and the OTA are on the same side side of the pier.

If your mount has stopped, that means that the mount thinks that it has reached the Meridian Limit (in this case, the Meridian itself). This is based on the Local Sidereal Time of the clock that is in the Mount.

If the mount does not autonomously flip when it hits the meridian limit, then it is up to the controlling program to issue a GOTO (to the same target coordinates), after the mount has reach its Meridian Limit,

There are a couple of reasons for a Meridian flip to not happen.

One reason is that the computer program is assuming that the mount is autonomously flipping once it reaches the Meridian Limit. Some mounts' Meridian treatment allows you to set it to autonomously flipping. The AM5 does not do that (at least today, as far as I can tell -- I do not have an AM5 to check). For these mounts, the computer program is responsible to send a GOTO command to the mount. Check for that GOTO command in your log -- no GOTO, no flip for the AM5.

Another reason for not flipping is that the Local Sidereal Time (LST) clock in the computer program is different from the LST clock in the mount. Confusion with Daylight Saving Time is the usual culprit for this. That is why it is important to check if the two LST are the same. If there is a 1 hour delay in the computer program's LST clock relative to the mount's LST clock, the GOTO command (thus the flip) will be late by 1 hour.

The stars don't care what the UTC is, what the UTC offset is, what your local time is, what your longitude is, or whether you are observing Daylight Saving Time (DST). The stars only care about Local Sidereal Time. If the Local Sidereal Time is not properly computed based upon UTC, offset, longitude and DST, then there will be problems (we see this in ASIAIR all the time, and that is why mounts that are connected to the ASIAIR need to have DST turned off).

Another possibility is that the mount has not accounted properly to syncing with the stars. This can happen when the mount is not perfectly level. A difference of 1º of east-west leveling can cause a 4 minute (in time) difference between when the mount thinks a target has reached Meridian to when the computer thinks the mount has reached Meridian. If the mount is not accounting for leveling (this is usually done by the mount's model when it is synced to the stars), then you can also experience a delay if the computer program uses plate solves to determine the Transit time of the target. Some mounts allow you to accurately set this parameter so that you can depend just on the mount's index mark (and not require star syncing), see for example the procedure for the RainbowAstro mounts (I don't remember reading of such a procedure in the AM5 manual):

https://www.youtube.com/watch?v=7IC1j8i-1H4

Chen

ajobacho

As I can't submit a ticket and I can't attach here the completed log, you can download the log from this link:
https://drive.google.com/file/d/1m8ujul3moRJtlexEuuejSaiHp0tDtt2k/view?usp=sharing

ajobacho

@Walf@ZWO#58267
I suppose that you have the log file, haven't you?