Date   

Re: Mach-2 can not reach target

Roland Christen
 


I have ASI6200 with a 7 position filter wheel attached behind the flattener.
I would love to see how that works. I've been thinking about a QHY 600 camera.

Rolando


-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 4:46 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Sorry, I have done now the right on! I will report when all is fine now!
By the way I am imaging with a Stowaway on the Mach2. It is a nice combination and I am happy with the performance. I have ASI6200 with a 7 position filter wheel attached behind the flattener.

Konstantin


Am 17.08.2020 um 22:15 schrieb uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io>:


As Roland said I can prevent this with the $SLD0# command.
Well, Roland said it wrong and Howard said it right. Use :LR0# to turn off the RA limits at the Meridian.

Rolando


-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 3:10 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Hello Howard,

I have set the limits on both sides! The problem is to move from a cw up position on the east direct to a cw up position in the west. As Roland said I can prevent this with the $SLD0# command. I will test that. 

Grüsse

Konstantin v. Poschinger


Hammerichstr. 5
22605 Hamburg
040/8805747
0171/1983476

Am 17.08.2020 um 21:42 schrieb Howard Hedlund <howard@...>:

Setting an appropriate meridian delay BEFORE the counterweight shaft goes up will also avoid the problem.  This is easily set in APCC.


Re: Mach-2 can not reach target

Bill Long
 

Nice looking rig. Love my Eagle pier my Mach 1 rides on. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Konstantin von Poschinger <KPoschinger@...>
Sent: Monday, August 17, 2020 2:46 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach-2 can not reach target
 
Sorry, I have done now the right on! I will report when all is fine now!
By the way I am imaging with a Stowaway on the Mach2. It is a nice combination and I am happy with the performance. I have ASI6200 with a 7 position filter wheel attached behind the flattener.

Konstantin


Am 17.08.2020 um 22:15 schrieb uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io>:


As Roland said I can prevent this with the $SLD0# command.
Well, Roland said it wrong and Howard said it right. Use :LR0# to turn off the RA limits at the Meridian.

Rolando


-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 3:10 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Hello Howard,

I have set the limits on both sides! The problem is to move from a cw up position on the east direct to a cw up position in the west. As Roland said I can prevent this with the $SLD0# command. I will test that. 

Grüsse

Konstantin v. Poschinger


Hammerichstr. 5
22605 Hamburg
040/8805747
0171/1983476

Am 17.08.2020 um 21:42 schrieb Howard Hedlund <howard@...>:

Setting an appropriate meridian delay BEFORE the counterweight shaft goes up will also avoid the problem.  This is easily set in APCC.


Re: Mach-2 can not reach target

Konstantin von Poschinger
 

Sorry, I have done now the right on! I will report when all is fine now!
By the way I am imaging with a Stowaway on the Mach2. It is a nice combination and I am happy with the performance. I have ASI6200 with a 7 position filter wheel attached behind the flattener.

Konstantin


Am 17.08.2020 um 22:15 schrieb uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io>:


As Roland said I can prevent this with the $SLD0# command.
Well, Roland said it wrong and Howard said it right. Use :LR0# to turn off the RA limits at the Meridian.

Rolando


-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 3:10 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Hello Howard,

I have set the limits on both sides! The problem is to move from a cw up position on the east direct to a cw up position in the west. As Roland said I can prevent this with the $SLD0# command. I will test that. 

Grüsse

Konstantin v. Poschinger


Hammerichstr. 5
22605 Hamburg
040/8805747
0171/1983476

Am 17.08.2020 um 21:42 schrieb Howard Hedlund <howard@...>:

Setting an appropriate meridian delay BEFORE the counterweight shaft goes up will also avoid the problem.  This is easily set in APCC.


Re: Mach-2 can not reach target

Roland Christen
 


Then I send the $SLD0# command.
That is not a valid command.

Roland


-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 4:29 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Hi Howard,

I just started my mount. The first thing I saw a red blinking singn and in the error log window it says that the RA limits has reached. I tryed to clear it. It won’t. Then I send the $SLD0# command. It wont clear either. I have to do the find home. After that and clearing the error it went fine. I am now imaging from a cw up position. 

Konstantin

Am 17.08.2020 um 23:09 schrieb Howard Hedlund <howard@...>:

Hi Konstantin!

$SLD0#  won't do anything since it is not a valid command in the command set.  :LR0#  is the proper command, beginning with a colon  :  not a $ sign.  By the way, that is a zero, not a capital O.


Re: Mach-2 can not reach target

Konstantin von Poschinger
 

Hi Howard,

I just started my mount. The first thing I saw a red blinking singn and in the error log window it says that the RA limits has reached. I tryed to clear it. It won’t. Then I send the $SLD0# command. It wont clear either. I have to do the find home. After that and clearing the error it went fine. I am now imaging from a cw up position. 

Konstantin

Am 17.08.2020 um 23:09 schrieb Howard Hedlund <howard@...>:

Hi Konstantin!

$SLD0#  won't do anything since it is not a valid command in the command set.  :LR0#  is the proper command, beginning with a colon  :  not a $ sign.  By the way, that is a zero, not a capital O.


Re: Mach-2 can not reach target

Howard Hedlund
 

Hi Konstantin!

$SLD0#  won't do anything since it is not a valid command in the command set.  :LR0#  is the proper command, beginning with a colon  :  not a $ sign.  By the way, that is a zero, not a capital O.


Re: Mach-2 can not reach target

Roland Christen
 


As Roland said I can prevent this with the $SLD0# command.
Well, Roland said it wrong and Howard said it right. Use :LR0# to turn off the RA limits at the Meridian.

Rolando


-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 3:10 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Hello Howard,

I have set the limits on both sides! The problem is to move from a cw up position on the east direct to a cw up position in the west. As Roland said I can prevent this with the $SLD0# command. I will test that. 

Grüsse

Konstantin v. Poschinger


Hammerichstr. 5
22605 Hamburg
040/8805747
0171/1983476

Am 17.08.2020 um 21:42 schrieb Howard Hedlund <howard@...>:

Setting an appropriate meridian delay BEFORE the counterweight shaft goes up will also avoid the problem.  This is easily set in APCC.


Re: Mach-2 can not reach target

Konstantin von Poschinger
 

Hello Howard,

I have set the limits on both sides! The problem is to move from a cw up position on the east direct to a cw up position in the west. As Roland said I can prevent this with the $SLD0# command. I will test that. 

Grüsse

Konstantin v. Poschinger


Hammerichstr. 5
22605 Hamburg
040/8805747
0171/1983476

Am 17.08.2020 um 21:42 schrieb Howard Hedlund <howard@...>:

Setting an appropriate meridian delay BEFORE the counterweight shaft goes up will also avoid the problem.  This is easily set in APCC.


Re: Mach-2 can not reach target

Howard Hedlund
 

Setting an appropriate meridian delay BEFORE the counterweight shaft goes up will also avoid the problem.  This is easily set in APCC.


Re: Mach-2 can not reach target

Roland Christen
 

The :LRO# limits are not set at the meridian, they are set with the scope completely upside down and they prevent the scope from wrapping around and causing internal cord wrap. DO NOT turn these limits off!

Roland



-----Original Message-----
From: Howard Hedlund <howard@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 2:32 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Correction:  Sending $LR0#  and $LR2#  is for the ENCODER limits, not the internal limits.  Turn the internal limits off by sending  :LR0#.  :LR2#  turns them back on.


Re: Mach-2 can not reach target

Howard Hedlund
 

If you are using APCC, you can do this easily from the Terminal window accessed from the Setup tab.  You can also do this from the CP4/5's web page.  Just click on the Terminal button to open a page for command lines.


Re: Mach-2 can not reach target

Roland Christen
 

Sorry, I was wrong, the encoder OFF is remembered so it will not come back on when power is cycled.

Roland



-----Original Message-----
From: uncarollo2 <chris1011@...> via groups.io <chris1011@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Mon, Aug 17, 2020 2:31 pm
Subject: Re: [ap-gto] Mach-2 can not reach target


Is the $LD0# command stored and also working the next time I initialize the mount or do I have to send the command every session new.
No, it is not stored. The mount comes up in Limits ON mode by default.

Roland


-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 1:54 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Hi Roland,

thanks very much for that Info. It will help me till the new firmware will be released.
I have one Question: Is the $LD0# command stored and also working the next time I initialize the mount or do I have to send the command every session new.

Konstantin


Am 17.08.2020 um 20:16 schrieb uncarollo2 <chris1011@...> via groups.io <chris1011@...>:

Hello Konstantin,

The CP5 has a built-in encoder limit which turns the mount off and parks it when the scope tracks approximately 1 minute past the meridian. This limit comes up as default ON when you initialize the mount. We put this into our latest CP firmware to solve the problem of users that let the mount track past the meridian unattended and eventually crash the scope into the pier. These limits are independent of any limits set in APCC at this point.

Right now APCC and the ASCOM driver do not have a way to set this internal limit off, but we are working on it and will have an automatic solution in the next release.

For now you can turn this limit OFF by opening the Terminal Mode in APCC and typing in and sending the following command: $LD0#

The command $LD2# turns the internal limits back ON, if desired. The mount will bounce back a couple of degrees when the limit is reached and park itself. The motors will de-energize. When the limits are set and the limit has been reached, the mount will be in park mode and will need to be un-parked from present position in order to begin tracking and slewing.

The bounce-back will put the mount back into CWT down mode so that all commands to move from external software will be active again when the mount is unparked

Hope this helps for now.

Roland Christen
Astro-Physics inc.





-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Sun, Aug 16, 2020 9:01 am
Subject: Re: [ap-gto] Mach-2 can not reach target

Hi Terri,

no I am using only MaximDL. The error can be avoided if you slew first in a cw up position an do the flip from that position. As Ray have said it seems to be a firmware bug. We have t wait for answers from Howard.

Konstantin



Am 16.08.2020 um 15:12 schrieb Terri Zittritsch <theresamarie11@...>:

Konstantin, you are not alone... I've had 2 nights interrupted by RA limit errors that can not be cleared as well..   Right after a meridian flip, the software seems to lock up while trying to do the plate solve and center right at the meridian.    I've sent my logs to Roland.

I've now had it happen on 2 different targets.   I use SGPro as well.. so I was using SGPro plus APCC plus the ASCOM driver.
Are you using SGPro and/or were you imaging right around the meridian?

Terri



Re: Mach-2 can not reach target

Howard Hedlund
 

Correction:  Sending $LR0#  and $LR2#  is for the ENCODER limits, not the internal limits.  Turn the internal limits off by sending  :LR0#.  :LR2#  turns them back on.


Re: Mach-2 can not reach target

Roland Christen
 


Is the $LD0# command stored and also working the next time I initialize the mount or do I have to send the command every session new.
No, it is not stored. The mount comes up in Limits ON mode by default.

Roland


-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Mon, Aug 17, 2020 1:54 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Hi Roland,

thanks very much for that Info. It will help me till the new firmware will be released.
I have one Question: Is the $LD0# command stored and also working the next time I initialize the mount or do I have to send the command every session new.

Konstantin


Am 17.08.2020 um 20:16 schrieb uncarollo2 <chris1011@...> via groups.io <chris1011@...>:

Hello Konstantin,

The CP5 has a built-in encoder limit which turns the mount off and parks it when the scope tracks approximately 1 minute past the meridian. This limit comes up as default ON when you initialize the mount. We put this into our latest CP firmware to solve the problem of users that let the mount track past the meridian unattended and eventually crash the scope into the pier. These limits are independent of any limits set in APCC at this point.

Right now APCC and the ASCOM driver do not have a way to set this internal limit off, but we are working on it and will have an automatic solution in the next release.

For now you can turn this limit OFF by opening the Terminal Mode in APCC and typing in and sending the following command: $LD0#

The command $LD2# turns the internal limits back ON, if desired. The mount will bounce back a couple of degrees when the limit is reached and park itself. The motors will de-energize. When the limits are set and the limit has been reached, the mount will be in park mode and will need to be un-parked from present position in order to begin tracking and slewing.

The bounce-back will put the mount back into CWT down mode so that all commands to move from external software will be active again when the mount is unparked

Hope this helps for now.

Roland Christen
Astro-Physics inc.





-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Sun, Aug 16, 2020 9:01 am
Subject: Re: [ap-gto] Mach-2 can not reach target

Hi Terri,

no I am using only MaximDL. The error can be avoided if you slew first in a cw up position an do the flip from that position. As Ray have said it seems to be a firmware bug. We have t wait for answers from Howard.

Konstantin



Am 16.08.2020 um 15:12 schrieb Terri Zittritsch <theresamarie11@...>:

Konstantin, you are not alone... I've had 2 nights interrupted by RA limit errors that can not be cleared as well..   Right after a meridian flip, the software seems to lock up while trying to do the plate solve and center right at the meridian.    I've sent my logs to Roland.

I've now had it happen on 2 different targets.   I use SGPro as well.. so I was using SGPro plus APCC plus the ASCOM driver.
Are you using SGPro and/or were you imaging right around the meridian?

Terri



Re: Mach-2 can not reach target

Dean Jacobsen
 

On Mon, Aug 17, 2020 at 11:16 AM, uncarollo2 <chris1011@...> wrote:
The CP5 has a built-in encoder limit which turns the mount off and parks it when the scope tracks approximately 1 minute past the meridian. This limit comes up as default ON when you initialize the mount. We put this into our latest CP firmware to solve the problem of users that let the mount track past the meridian unattended and eventually crash the scope into the pier. These limits are independent of any limits set in APCC at this point.
Now I'm confused.  I haven't seen this behavior yet.  However, I use one of two pre-configured meridian tracking limits maps.  I also set the "Action when limit reached" box to "Just Warn".  My experience has been that the mount will continue tracking through the meridian limit until such time that I execute a manual meridian flip.
 
--
Dean Jacobsen
http://astrophoto.net/wp/
Image Gallery - http://astrophoto.net/wp/image-gallery/
Astrobin - https://www.astrobin.com/users/deanjacobsen/ 


Re: Multiple limits set?

 

Thanks roland, yes I picked that up from your previous post :)


On Mon, Aug 17, 2020 at 11:53 AM uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:
Go into APCC terminal mode and type in: $LD0#
This will turn off the encoder limits.

Roland Christen
Astro-Physics Inc.



-----Original Message-----
From: Brian Valente <bvalente@...>
To: main@ap-gto.groups.io
Sent: Sun, Aug 16, 2020 8:27 pm
Subject: [ap-gto] Multiple limits set?

Hi folks

Where are all the places you can set limits? We have AP1600 with encoders

we turned off AE limits in APCC as a test, and we're still getting errors that we've hit the RA limit and it's bouncing back. I know 'bounce back' is an option for setting limits, but it seems they are being applied from another screen or program? we are just using SGP for now. 

any pointers appreciated. thanks

image.png
image.png
--
Brian 



Brian Valente



--
Brian 



Brian Valente


Re: Mach-2 can not reach target

Konstantin von Poschinger
 

Hi Roland,

thanks very much for that Info. It will help me till the new firmware will be released.
I have one Question: Is the $LD0# command stored and also working the next time I initialize the mount or do I have to send the command every session new.

Konstantin


Am 17.08.2020 um 20:16 schrieb uncarollo2 <chris1011@...> via groups.io <chris1011@...>:

Hello Konstantin,

The CP5 has a built-in encoder limit which turns the mount off and parks it when the scope tracks approximately 1 minute past the meridian. This limit comes up as default ON when you initialize the mount. We put this into our latest CP firmware to solve the problem of users that let the mount track past the meridian unattended and eventually crash the scope into the pier. These limits are independent of any limits set in APCC at this point.

Right now APCC and the ASCOM driver do not have a way to set this internal limit off, but we are working on it and will have an automatic solution in the next release.

For now you can turn this limit OFF by opening the Terminal Mode in APCC and typing in and sending the following command: $LD0#

The command $LD2# turns the internal limits back ON, if desired. The mount will bounce back a couple of degrees when the limit is reached and park itself. The motors will de-energize. When the limits are set and the limit has been reached, the mount will be in park mode and will need to be un-parked from present position in order to begin tracking and slewing.

The bounce-back will put the mount back into CWT down mode so that all commands to move from external software will be active again when the mount is unparked

Hope this helps for now.

Roland Christen
Astro-Physics inc.





-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Sun, Aug 16, 2020 9:01 am
Subject: Re: [ap-gto] Mach-2 can not reach target

Hi Terri,

no I am using only MaximDL. The error can be avoided if you slew first in a cw up position an do the flip from that position. As Ray have said it seems to be a firmware bug. We have t wait for answers from Howard.

Konstantin



Am 16.08.2020 um 15:12 schrieb Terri Zittritsch <theresamarie11@...>:

Konstantin, you are not alone... I've had 2 nights interrupted by RA limit errors that can not be cleared as well..   Right after a meridian flip, the software seems to lock up while trying to do the plate solve and center right at the meridian.    I've sent my logs to Roland.

I've now had it happen on 2 different targets.   I use SGPro as well.. so I was using SGPro plus APCC plus the ASCOM driver.
Are you using SGPro and/or were you imaging right around the meridian?

Terri



Re: Multiple limits set?

Roland Christen
 

Go into APCC terminal mode and type in: $LD0#
This will turn off the encoder limits.

Roland Christen
Astro-Physics Inc.



-----Original Message-----
From: Brian Valente <bvalente@...>
To: main@ap-gto.groups.io
Sent: Sun, Aug 16, 2020 8:27 pm
Subject: [ap-gto] Multiple limits set?

Hi folks

Where are all the places you can set limits? We have AP1600 with encoders

we turned off AE limits in APCC as a test, and we're still getting errors that we've hit the RA limit and it's bouncing back. I know 'bounce back' is an option for setting limits, but it seems they are being applied from another screen or program? we are just using SGP for now. 

any pointers appreciated. thanks

image.png
image.png
--
Brian 



Brian Valente


Re: Mach-2 can not reach target

Roland Christen
 

Also please make sure that you have the latest driver version 5.30.10. loaded.

I have been busy all morning here testing various scenarios with my mount in the observatory and I cannot make it hang up with the limits on or off. I cannot reproduce what you are experiencing.

Rolando



-----Original Message-----
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Mon, Aug 17, 2020 1:16 pm
Subject: Re: [ap-gto] Mach-2 can not reach target

Hello Konstantin,

The CP5 has a built-in encoder limit which turns the mount off and parks it when the scope tracks approximately 1 minute past the meridian. This limit comes up as default ON when you initialize the mount. We put this into our latest CP firmware to solve the problem of users that let the mount track past the meridian unattended and eventually crash the scope into the pier. These limits are independent of any limits set in APCC at this point.

Right now APCC and the ASCOM driver do not have a way to set this internal limit off, but we are working on it and will have an automatic solution in the next release.

For now you can turn this limit OFF by opening the Terminal Mode in APCC and typing in and sending the following command: $LD0#

The command $LD2# turns the internal limits back ON, if desired. The mount will bounce back a couple of degrees when the limit is reached and park itself. The motors will de-energize. When the limits are set and the limit has been reached, the mount will be in park mode and will need to be un-parked from present position in order to begin tracking and slewing.

The bounce-back will put the mount back into CWT down mode so that all commands to move from external software will be active again when the mount is unparked

Hope this helps for now.

Roland Christen
Astro-Physics inc.





-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Sun, Aug 16, 2020 9:01 am
Subject: Re: [ap-gto] Mach-2 can not reach target

Hi Terri,

no I am using only MaximDL. The error can be avoided if you slew first in a cw up position an do the flip from that position. As Ray have said it seems to be a firmware bug. We have t wait for answers from Howard.

Konstantin



Am 16.08.2020 um 15:12 schrieb Terri Zittritsch <theresamarie11@...>:

Konstantin, you are not alone... I've had 2 nights interrupted by RA limit errors that can not be cleared as well..   Right after a meridian flip, the software seems to lock up while trying to do the plate solve and center right at the meridian.    I've sent my logs to Roland.

I've now had it happen on 2 different targets.   I use SGPro as well.. so I was using SGPro plus APCC plus the ASCOM driver.
Are you using SGPro and/or were you imaging right around the meridian?

Terri


Re: Mach-2 can not reach target

Roland Christen
 

Hello Konstantin,

The CP5 has a built-in encoder limit which turns the mount off and parks it when the scope tracks approximately 1 minute past the meridian. This limit comes up as default ON when you initialize the mount. We put this into our latest CP firmware to solve the problem of users that let the mount track past the meridian unattended and eventually crash the scope into the pier. These limits are independent of any limits set in APCC at this point.

Right now APCC and the ASCOM driver do not have a way to set this internal limit off, but we are working on it and will have an automatic solution in the next release.

For now you can turn this limit OFF by opening the Terminal Mode in APCC and typing in and sending the following command: $LD0#

The command $LD2# turns the internal limits back ON, if desired. The mount will bounce back a couple of degrees when the limit is reached and park itself. The motors will de-energize. When the limits are set and the limit has been reached, the mount will be in park mode and will need to be un-parked from present position in order to begin tracking and slewing.

The bounce-back will put the mount back into CWT down mode so that all commands to move from external software will be active again when the mount is unparked

Hope this helps for now.

Roland Christen
Astro-Physics inc.





-----Original Message-----
From: Konstantin von Poschinger <KPoschinger@...>
To: main@ap-gto.groups.io
Sent: Sun, Aug 16, 2020 9:01 am
Subject: Re: [ap-gto] Mach-2 can not reach target

Hi Terri,

no I am using only MaximDL. The error can be avoided if you slew first in a cw up position an do the flip from that position. As Ray have said it seems to be a firmware bug. We have t wait for answers from Howard.

Konstantin



Am 16.08.2020 um 15:12 schrieb Terri Zittritsch <theresamarie11@...>:

Konstantin, you are not alone... I've had 2 nights interrupted by RA limit errors that can not be cleared as well..   Right after a meridian flip, the software seems to lock up while trying to do the plate solve and center right at the meridian.    I've sent my logs to Roland.

I've now had it happen on 2 different targets.   I use SGPro as well.. so I was using SGPro plus APCC plus the ASCOM driver.
Are you using SGPro and/or were you imaging right around the meridian?

Terri

9121 - 9140 of 81568