Re : RE: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour


Apr 16, 2017

 


----------------------------

#56566 Apr 16, 2017

Hi Ray,

Three days ago, when imaging.41P/Tuttle-Giacobini-Kresak, I've noticed a vertical nucleus trail even if I was tracking on the comet. .I've inspected images took 3 weeks earlier and saw also a small nucleus trail but at that time I thought it was an elongated form nucleus but I was wrong. .This time, it was more evident that the mount was not tracking the comet as it should.

The weird part is that imaging session began with this behaviour and my last imaging session was ok.

I began to suspect APCC tracking correction but seems to have nothing to do because tracking correction was enabled during my last imaging tests.

However, in inspecting log files I've noticed something that needs to be share to your attention.

Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and APCC. .Please note the difference in value between the two AP ASCOM log sections (AP ASCOM driver that produce vertical nucleus trail and.AP ASCOM driver WITH good comet tracking). .One :RDxxxxx# is negative and the other is positive. .The problem seems related to this anomaly.

Ray, I will sent you complete logs and images on request.

ASCOM and APCC updated to their latest version.

HAPPY EASTER!!!

Regards,Yves





ACP v7 (DC3-Dreams) time in UT01:10:17 . Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)01:10:17 . [flip check: .Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F WF=no]01:10:17 . (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec).

AP ASCOM driver that produce vertical nucleus trail028681 2017-04-13 21:10:17.420: . . . . . .ASCOM: Info . . .: SET RightAscensionRate = 6.65091663831767E-03028682 2017-04-13 21:10:17.440: . . . . . Driver: Info . . .: CommandBool TX=':RR-0.00665#'028683 2017-04-13 21:10:17.445: . . . . . Driver: Info . . .: CommandBool Reply Received (TX=':RR-0.00665#'), RX='1'028684 2017-04-13 21:10:17.448: . . . . . .ASCOM: Info . . .: SET DeclinationRate = -0.044520572702055028685 2017-04-13 21:10:17.466: . . . . . Driver: Info . . .: CommandBool TX=':RD-0.00296#'028686 2017-04-13 21:10:17.474: . . . . . Driver: Info . . .: CommandBool Reply Received (TX=':RD-0.00296#'), RX='1'



----------------------------

#56567 Apr 16, 2017

UPDATE: The comet was always.on the same side of the meridian (East) during my tests.



Le 16/04/17 . 14:08, "'yves.laroche@...' yves.laroche@... [ap-gto]" ap-gto@yahoogroups.com> a .crit : Hi Ray,

Three days ago, when imaging.41P/Tuttle-Giacobini-Kresak, I've noticed a vertical nucleus trail even if I was tracking on the comet. .I've inspected images took 3 weeks earlier and saw also a small nucleus trail but at that time I thought it was an elongated form nucleus but I was wrong. .This time, it was more evident that the mount was not tracking the comet as it should.

The weird part is that imaging session began with this behaviour and my last imaging session was ok.

I began to suspect APCC tracking correction but seems to have nothing to do because tracking correction was enabled during my last imaging tests.

However, in inspecting log files I've noticed something that needs to be share to your attention.

Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and APCC. .Please note the difference in value between the two AP ASCOM log sections (AP ASCOM driver that produce vertical nucleus trail and.AP ASCOM driver WITH good comet tracking). .One :RDxxxxx# is negative and the other is positive. .The problem seems related to this anomaly.

Ray, I will sent you complete logs and images on request.

ASCOM and APCC updated to their latest version.

HAPPY EASTER!!!

Regards,Yves





ACP v7 (DC3-Dreams) time in UT01:10:17 . Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)01:10:17 . [flip check: .Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F WF=no]01:10:17 . (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec).

AP ASCOM driver that produce vertical nucleus trail028681 2017-04-13 21:10:17.420: . . . . . .ASCOM: Info . . .: SET RightAscensionRate = 6.65091663831767E-03028682 2017-04-13 21:10:17.440: . . . . . Driver: Info . . .: CommandBool TX=':RR-0.00665#'028683 2017-04-13 21:10:17.445: . . . . . Driver: Info . . .: CommandBool Reply Received (TX=':RR-0.00665#'), RX='1'028684 2017-04-13 21:10:17.448: . . . . . .ASCOM: Info . . .: SET DeclinationRate = -0.044520572702055028685 2017-04-13 21:10:17.466: . . . . . Driver: Info . . .: CommandBool TX=':RD-0.00296#'028686 2017-04-13 21:10:17.474: . . . . . Driver: Info . . .: CommandBool Reply Received (TX=':RD-0.00296#'), RX='1'



----------------------------

#56570 Apr 16, 2017

Yves,



When switching side of pier, the declination direction has to be multiplied by -1. Is it possible that the pier side had changed?



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma



> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Sunday, April 16, 2017 11:09 AM

> To: ap-gto@yahoogroups.com

> Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

>

>

>

> Hi Ray,

>

> Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed a vertical

> nucleus trail even if I was tracking on the comet. I've inspected images took 3

> weeks earlier and saw also a small nucleus trail but at that time I thought it was an

> elongated form nucleus but I was wrong. This time, it was more evident that the

> mount was not tracking the comet as it should.

>

> The weird part is that imaging session began with this behaviour and my last

> imaging session was ok.

>

> I began to suspect APCC tracking correction but seems to have nothing to do

> because tracking correction was enabled during my last imaging tests.

>

> However, in inspecting log files I've noticed something that needs to be share to

> your attention.

>

> Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and APCC.

> Please note the difference in value between the two AP ASCOM log sections (AP

> ASCOM driver that produce vertical nucleus trail and AP ASCOM driver WITH good

> comet tracking). One :RDxxxxx# is negative and the other is positive. The problem

> seems related to this anomaly.

>

> Ray, I will sent you complete logs and images on request.

>

> ASCOM and APCC updated to their latest version.

>

> HAPPY EASTER!!!

>

> Regards,

> Yves

>

>

>

> ACP v7 (DC3-Dreams) time in UT

> 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> WF=no]

> 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

>

> AP ASCOM driver that produce vertical nucleus trail

> 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> RightAscensionRate = 6.65091663831767E-03

> 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool TX=':RR-

> 0.00665#'

> 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> Received (TX=':RR-0.00665#'), RX='1'

> 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> -0.044520572702055

> 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> 0.00296#'

> 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> Received (TX=':RD-0.00296#'), RX='1'

>

> APCC

> 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-0.00665#

> 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX from

> VPort 0: :RR-0.00665#

> 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> 0.00665#), TX: 1

> 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate Change:

> -0.00665

> 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> '21:10:17.4#'

> 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX = '#:GS#'

> 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-0.00296#

> 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> '09:46:22.7#'

> 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX = '#:GR#'

> 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX from

> VPort 0: :RD-0.00296#

> 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> 0.00296#), TX: 1

>

>

> **********************************************************************************************

> *********************************

>

>

> AP ASCOM driver WITH good comet tracking

> 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> RightAscensionRate = 6.50663785895112E-03

> 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool TX=':RR-

> 0.00651#'

> 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> Received (TX=':RR-0.00651#'), RX='1'

> 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> -4.48155149186675E-02

> 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> TX=':RD0.00298#'

> 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> Received (TX=':RD0.00298#'), RX='1'

>

>

> END OF LOG

>

>

>







----------------------------

#56571 Apr 16, 2017

Ray,

UPDATE: The comet was always.on the same side of the meridian (East) during my tests.

Yves

Le 16/04/17 . 14:53, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-gto@yahoogroups.com> a .crit : Yves,



When switching side of pier, the declination direction has to be multiplied by -1. Is it possible that the pier side had changed?



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma



> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Sunday, April 16, 2017 11:09 AM

> To: ap-gto@yahoogroups.com

> Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

>

>

>

> Hi Ray,

>

> Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed a vertical

> nucleus trail even if I was tracking on the comet. I've inspected images took 3

> weeks earlier and saw also a small nucleus trail but at that time I thought it was an

> elongated form nucleus but I was wrong. This time, it was more evident that the

> mount was not tracking the comet as it should.

>

> The weird part is that imaging session began with this behaviour and my last

> imaging session was ok.

>

> I began to suspect APCC tracking correction but seems to have nothing to do

> because tracking correction was enabled during my last imaging tests.

>

> However, in inspecting log files I've noticed something that needs to be share to

> your attention.

>

> Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and APCC.

> Please note the difference in value between the two AP ASCOM log sections (AP

> ASCOM driver that produce vertical nucleus trail and AP ASCOM driver WITH good

> comet tracking). One :RDxxxxx# is negative and the other is positive. The problem

> seems related to this anomaly.

>

> Ray, I will sent you complete logs and images on request.

>

> ASCOM and APCC updated to their latest version.

>

> HAPPY EASTER!!!

>

> Regards,

> Yves

>

>

>

> ACP v7 (DC3-Dreams) time in UT

> 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> WF=no]

> 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

>

> AP ASCOM driver that produce vertical nucleus trail

> 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> RightAscensionRate = 6.65091663831767E-03

> 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool TX=':RR-

> 0.00665#'

> 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> Received (TX=':RR-0.00665#'), RX='1'

> 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> -0.044520572702055

> 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> 0.00296#'

> 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> Received (TX=':RD-0.00296#'), RX='1'

>

> APCC

> 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-0.00665#

> 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX from

> VPort 0: :RR-0.00665#

> 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> 0.00665#), TX: 1

> 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate Change:

> -0.00665

> 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> '21:10:17.4#'

> 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX = '#:GS#'

> 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-0.00296#

> 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> '09:46:22.7#'

> 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX = '#:GR#'

> 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX from

> VPort 0: :RD-0.00296#

> 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> 0.00296#), TX: 1

>

>

> **********************************************************************************************

> *********************************

>

>

> AP ASCOM driver WITH good comet tracking

> 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> RightAscensionRate = 6.50663785895112E-03

> 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool TX=':RR-

> 0.00651#'

> 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> Received (TX=':RR-0.00651#'), RX='1'

> 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> -4.48155149186675E-02

> 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> TX=':RD0.00298#'

> 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> Received (TX=':RD0.00298#'), RX='1'

>

>

> END OF LOG

>

>

>







----------------------------

#56572 Apr 16, 2017

Then I'm not sure I understand your logs. Why would ACP send a positive rate one night, and a negative the next?



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma



> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Sunday, April 16, 2017 12:29 PM

> To: ap-gto@yahoogroups.com

> Subject: Re : RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

>

>

>

> Ray,

>

>

> UPDATE: The comet was always on the same side of the meridian (East) during my

> tests.

>

> Yves

>

>

> Le 16/04/17 . 14:53, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> gto@yahoogroups.com> a .crit :

>

>

>

> Yves,

>

> When switching side of pier, the declination direction has to be multiplied by -1. Is it

> possible that the pier side had changed?

>

> -Ray Gralak

> Author of APCC (Astro-Physics Command Center): www.astro-

> physics.com/index.htm?products/accessories/software/apcc/apcc

> Author of PEMPro: www.ccdware.com

> Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> Author of PulseGuide: www.pulseguide.com

> Author of Sigma: www.gralak.com/sigma

>

> > -----Original Message-----

> > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > Sent: Sunday, April 16, 2017 11:09 AM

> > To: ap-gto@yahoogroups.com

> > Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> >

> >

> >

> > Hi Ray,

> >

> > Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed a vertical

> > nucleus trail even if I was tracking on the comet. I've inspected images took 3

> > weeks earlier and saw also a small nucleus trail but at that time I thought it was

> an

> > elongated form nucleus but I was wrong. This time, it was more evident that the

> > mount was not tracking the comet as it should.

> >

> > The weird part is that imaging session began with this behaviour and my last

> > imaging session was ok.

> >

> > I began to suspect APCC tracking correction but seems to have nothing to do

> > because tracking correction was enabled during my last imaging tests.

> >

> > However, in inspecting log files I've noticed something that needs to be share to

> > your attention.

> >

> > Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and

> APCC.

> > Please note the difference in value between the two AP ASCOM log sections (AP

> > ASCOM driver that produce vertical nucleus trail and AP ASCOM driver WITH

> good

> > comet tracking). One :RDxxxxx# is negative and the other is positive. The problem

> > seems related to this anomaly.

> >

> > Ray, I will sent you complete logs and images on request.

> >

> > ASCOM and APCC updated to their latest version.

> >

> > HAPPY EASTER!!!

> >

> > Regards,

> > Yves

> >

> >

> >

> > ACP v7 (DC3-Dreams) time in UT

> > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > WF=no]

> > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> >

> > AP ASCOM driver that produce vertical nucleus trail

> > 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> > RightAscensionRate = 6.65091663831767E-03

> > 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool TX=':RR-

> > 0.00665#'

> > 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> > Received (TX=':RR-0.00665#'), RX='1'

> > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> > -0.044520572702055

> > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> > 0.00296#'

> > 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> > Received (TX=':RD-0.00296#'), RX='1'

> >

> > APCC

> > 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-0.00665#

> > 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX from

> > VPort 0: :RR-0.00665#

> > 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> > 0.00665#), TX: 1

> > 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate Change:

> > -0.00665

> > 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> > '21:10:17.4#'

> > 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX = '#:GS#'

> > 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-0.00296#

> > 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> > '09:46:22.7#'

> > 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX = '#:GR#'

> > 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX from

> > VPort 0: :RD-0.00296#

> > 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> > 0.00296#), TX: 1

> >

> >

> >

> **********************************************************************************************

> > *********************************

> >

> >

> > AP ASCOM driver WITH good comet tracking

> > 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> > RightAscensionRate = 6.50663785895112E-03

> > 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool TX=':RR-

> > 0.00651#'

> > 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> > Received (TX=':RR-0.00651#'), RX='1'

> > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> > -4.48155149186675E-02

> > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > TX=':RD0.00298#'

> > 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> > Received (TX=':RD0.00298#'), RX='1'

> >

> >

> > END OF LOG

> >

> >

> >

>

>

>

>







----------------------------

#56574 Apr 16, 2017

> The weird part is that imaging session began with this behaviour and my last> > imaging session was ok.



----------------------------

#56575 Apr 16, 2017

If that's so, something misconfigured the dec direction value in the driver. There is an option in the driver to configure that after the first slew. If you had that misconfigured then the value could be sent as a negative. That is the only explanation that I can think of since you say the scope was on the same side of pier.



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma



> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Sunday, April 16, 2017 1:06 PM

> To: ap-gto@yahoogroups.com

> Subject: Re : RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> behaviour

>

>

>

> Ray,

>

> ACP was sending approx. same orbital values on the same night according to the

> logs. However ASCOM logs show different sign values between :RD-0.00296 and

> :RD0.00298

>

>

> ACP logs

> 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> WF=no]

> 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

>

> 07:07:36 Comet elements for 0041P --> RA=16:49:37 Dec=57. 31' 23" (J2000)

> 07:07:36 [flip check: Tn=-300s HAc=-3913s GW=F HAz=-3915s DWz=F WF=no]

> 07:07:36 (doing orbital tracking. RA 0.0979 "/sec, Dec -0.0448 "/sec)

>

>

>

>

> Regards,

> Yves

>

>

>

>

>

> Le 16/04/17 . 15:48, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> gto@yahoogroups.com> a .crit :

>

>

>

> Then I'm not sure I understand your logs. Why would ACP send a positive rate one

> night, and a negative the next?

>

> -Ray Gralak

> Author of APCC (Astro-Physics Command Center): www.astro-

> physics.com/index.htm?products/accessories/software/apcc/apcc

> Author of PEMPro: www.ccdware.com

> Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> Author of PulseGuide: www.pulseguide.com

> Author of Sigma: www.gralak.com/sigma

>

> > -----Original Message-----

> > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > Sent: Sunday, April 16, 2017 12:29 PM

> > To: ap-gto@yahoogroups.com

> > Subject: Re : RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> >

> >

> >

> > Ray,

> >

> >

> > UPDATE: The comet was always on the same side of the meridian (East) during

> my

> > tests.

> >

> > Yves

> >

> >

> > Le 16/04/17 . 14:53, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> > gto@yahoogroups.com> a .crit :

> >

> >

> >

> > Yves,

> >

> > When switching side of pier, the declination direction has to be multiplied by -1. Is

> it

> > possible that the pier side had changed?

> >

> > -Ray Gralak

> > Author of APCC (Astro-Physics Command Center): www.astro-

> > physics.com/index.htm?products/accessories/software/apcc/apcc

> > Author of PEMPro: www.ccdware.com

> > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > Author of PulseGuide: www.pulseguide.com

> > Author of Sigma: www.gralak.com/sigma

> >

> > > -----Original Message-----

> > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > Sent: Sunday, April 16, 2017 11:09 AM

> > > To: ap-gto@yahoogroups.com

> > > Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> > >

> > >

> > >

> > > Hi Ray,

> > >

> > > Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed a

> vertical

> > > nucleus trail even if I was tracking on the comet. I've inspected images took 3

> > > weeks earlier and saw also a small nucleus trail but at that time I thought it was

> > an

> > > elongated form nucleus but I was wrong. This time, it was more evident that the

> > > mount was not tracking the comet as it should.

> > >

> > > The weird part is that imaging session began with this behaviour and my last

> > > imaging session was ok.

> > >

> > > I began to suspect APCC tracking correction but seems to have nothing to do

> > > because tracking correction was enabled during my last imaging tests.

> > >

> > > However, in inspecting log files I've noticed something that needs to be share to

> > > your attention.

> > >

> > > Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and

> > APCC.

> > > Please note the difference in value between the two AP ASCOM log sections

> (AP

> > > ASCOM driver that produce vertical nucleus trail and AP ASCOM driver WITH

> > good

> > > comet tracking). One :RDxxxxx# is negative and the other is positive. The

> problem

> > > seems related to this anomaly.

> > >

> > > Ray, I will sent you complete logs and images on request.

> > >

> > > ASCOM and APCC updated to their latest version.

> > >

> > > HAPPY EASTER!!!

> > >

> > > Regards,

> > > Yves

> > >

> > >

> > >

> > > ACP v7 (DC3-Dreams) time in UT

> > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > > WF=no]

> > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > >

> > > AP ASCOM driver that produce vertical nucleus trail

> > > 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> > > RightAscensionRate = 6.65091663831767E-03

> > > 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool TX=':RR-

> > > 0.00665#'

> > > 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> > > Received (TX=':RR-0.00665#'), RX='1'

> > > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> > > -0.044520572702055

> > > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> > > 0.00296#'

> > > 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> > > Received (TX=':RD-0.00296#'), RX='1'

> > >

> > > APCC

> > > 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-0.00665#

> > > 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX from

> > > VPort 0: :RR-0.00665#

> > > 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> > > 0.00665#), TX: 1

> > > 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate Change:

> > > -0.00665

> > > 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> > > '21:10:17.4#'

> > > 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX = '#:GS#'

> > > 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-0.00296#

> > > 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> > > '09:46:22.7#'

> > > 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX = '#:GR#'

> > > 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX from

> > > VPort 0: :RD-0.00296#

> > > 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> > > 0.00296#), TX: 1

> > >

> > >

> > >

> >

> **********************************************************************************************

> > > *********************************

> > >

> > >

> > > AP ASCOM driver WITH good comet tracking

> > > 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> > > RightAscensionRate = 6.50663785895112E-03

> > > 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool TX=':RR-

> > > 0.00651#'

> > > 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> > > Received (TX=':RR-0.00651#'), RX='1'

> > > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> > > -4.48155149186675E-02

> > > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > > TX=':RD0.00298#'

> > > 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> > > Received (TX=':RD0.00298#'), RX='1'

> > >

> > >

> > > END OF LOG

> > >

> > >

> > >

> >

> >

> >

> >

>

>

>

>







----------------------------

#56576 Apr 16, 2017

Ray,

The ASCOM Calibrate move directions on first slew (recommend) was disabled. .Were you talking about that option?

If yes, how DEC direction could change during the same night if that previous option was still disabled?



Yves



Le 16/04/17 . 16:17, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-gto@yahoogroups.com> a .crit : If that's so, something misconfigured the dec direction value in the driver. There is an option in the driver to configure that after the first slew. If you had that misconfigured then the value could be sent as a negative. That is the only explanation that I can think of since you say the scope was on the same side of pier.



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma



> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Sunday, April 16, 2017 1:06 PM

> To: ap-gto@yahoogroups.com

> Subject: Re : RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> behaviour

>

>

>

> Ray,

>

> ACP was sending approx. same orbital values on the same night according to the

> logs. However ASCOM logs show different sign values between :RD-0.00296 and

> :RD0.00298

>

>

> ACP logs

> 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> WF=no]

> 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

>

> 07:07:36 Comet elements for 0041P --> RA=16:49:37 Dec=57. 31' 23" (J2000)

> 07:07:36 [flip check: Tn=-300s HAc=-3913s GW=F HAz=-3915s DWz=F WF=no]

> 07:07:36 (doing orbital tracking. RA 0.0979 "/sec, Dec -0.0448 "/sec)

>

>

>

>

> Regards,

> Yves

>

>

>

>

>

> Le 16/04/17 . 15:48, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> gto@yahoogroups.com> a .crit :

>

>

>

> Then I'm not sure I understand your logs. Why would ACP send a positive rate one

> night, and a negative the next?

>

> -Ray Gralak

> Author of APCC (Astro-Physics Command Center): www.astro-

> physics.com/index.htm?products/accessories/software/apcc/apcc

> Author of PEMPro: www.ccdware.com

> Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> Author of PulseGuide: www.pulseguide.com

> Author of Sigma: www.gralak.com/sigma

>

> > -----Original Message-----

> > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > Sent: Sunday, April 16, 2017 12:29 PM

> > To: ap-gto@yahoogroups.com

> > Subject: Re : RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> >

> >

> >

> > Ray,

> >

> >

> > UPDATE: The comet was always on the same side of the meridian (East) during

> my

> > tests.

> >

> > Yves

> >

> >

> > Le 16/04/17 . 14:53, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> > gto@yahoogroups.com> a .crit :

> >

> >

> >

> > Yves,

> >

> > When switching side of pier, the declination direction has to be multiplied by -1. Is

> it

> > possible that the pier side had changed?

> >

> > -Ray Gralak

> > Author of APCC (Astro-Physics Command Center): www.astro-

> > physics.com/index.htm?products/accessories/software/apcc/apcc

> > Author of PEMPro: www.ccdware.com

> > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > Author of PulseGuide: www.pulseguide.com

> > Author of Sigma: www.gralak.com/sigma

> >

> > > -----Original Message-----

> > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > Sent: Sunday, April 16, 2017 11:09 AM

> > > To: ap-gto@yahoogroups.com

> > > Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> > >

> > >

> > >

> > > Hi Ray,

> > >

> > > Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed a

> vertical

> > > nucleus trail even if I was tracking on the comet. I've inspected images took 3

> > > weeks earlier and saw also a small nucleus trail but at that time I thought it was

> > an

> > > elongated form nucleus but I was wrong. This time, it was more evident that the

> > > mount was not tracking the comet as it should.

> > >

> > > The weird part is that imaging session began with this behaviour and my last

> > > imaging session was ok.

> > >

> > > I began to suspect APCC tracking correction but seems to have nothing to do

> > > because tracking correction was enabled during my last imaging tests.

> > >

> > > However, in inspecting log files I've noticed something that needs to be share to

> > > your attention.

> > >

> > > Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and

> > APCC.

> > > Please note the difference in value between the two AP ASCOM log sections

> (AP

> > > ASCOM driver that produce vertical nucleus trail and AP ASCOM driver WITH

> > good

> > > comet tracking). One :RDxxxxx# is negative and the other is positive. The

> problem

> > > seems related to this anomaly.

> > >

> > > Ray, I will sent you complete logs and images on request.

> > >

> > > ASCOM and APCC updated to their latest version.

> > >

> > > HAPPY EASTER!!!

> > >

> > > Regards,

> > > Yves

> > >

> > >

> > >

> > > ACP v7 (DC3-Dreams) time in UT

> > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > > WF=no]

> > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > >

> > > AP ASCOM driver that produce vertical nucleus trail

> > > 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> > > RightAscensionRate = 6.65091663831767E-03

> > > 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool TX=':RR-

> > > 0.00665#'

> > > 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> > > Received (TX=':RR-0.00665#'), RX='1'

> > > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> > > -0.044520572702055

> > > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> > > 0.00296#'

> > > 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> > > Received (TX=':RD-0.00296#'), RX='1'

> > >

> > > APCC

> > > 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-0.00665#

> > > 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX from

> > > VPort 0: :RR-0.00665#

> > > 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> > > 0.00665#), TX: 1

> > > 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate Change:

> > > -0.00665

> > > 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> > > '21:10:17.4#'

> > > 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX = '#:GS#'

> > > 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-0.00296#

> > > 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> > > '09:46:22.7#'

> > > 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX = '#:GR#'

> > > 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX from

> > > VPort 0: :RD-0.00296#

> > > 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> > > 0.00296#), TX: 1

> > >

> > >

> > >

> >

> **********************************************************************************************

> > > *********************************

> > >

> > >

> > > AP ASCOM driver WITH good comet tracking

> > > 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> > > RightAscensionRate = 6.50663785895112E-03

> > > 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool TX=':RR-

> > > 0.00651#'

> > > 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> > > Received (TX=':RR-0.00651#'), RX='1'

> > > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> > > -4.48155149186675E-02

> > > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > > TX=':RD0.00298#'

> > > 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> > > Received (TX=':RD0.00298#'), RX='1'

> > >

> > >

> > > END OF LOG

> > >

> > >

> > >

> >

> >

> >

> >

>

>

>

>







----------------------------

#56579 Apr 16, 2017

Yes, that option. Internal Dec direction could be changed by sending a command to the mount or by clicking a button in the driver's UI.



Perhaps it is better to not turn off "recommended" options...



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma



> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Sunday, April 16, 2017 1:34 PM

> To: ap-gto@yahoogroups.com

> Subject: Re : RE: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> behaviour

>

>

>

> Ray,

>

> The ASCOM Calibrate move directions on first slew (recommend) was disabled.

> Were you talking about that option?

>

> If yes, how DEC direction could change during the same night if that previous option

> was still disabled?

>

>

> Yves

>

>

>

>

> Le 16/04/17 . 16:17, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> gto@yahoogroups.com> a .crit :

>

>

>

> If that's so, something misconfigured the dec direction value in the driver. There is

> an option in the driver to configure that after the first slew. If you had that

> misconfigured then the value could be sent as a negative. That is the only

> explanation that I can think of since you say the scope was on the same side of pier.

>

> -Ray Gralak

> Author of APCC (Astro-Physics Command Center): www.astro-

> physics.com/index.htm?products/accessories/software/apcc/apcc

> Author of PEMPro: www.ccdware.com

> Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> Author of PulseGuide: www.pulseguide.com

> Author of Sigma: www.gralak.com/sigma

>

> > -----Original Message-----

> > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > Sent: Sunday, April 16, 2017 1:06 PM

> > To: ap-gto@yahoogroups.com

> > Subject: Re : RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > behaviour

> >

> >

> >

> > Ray,

> >

> > ACP was sending approx. same orbital values on the same night according to the

> > logs. However ASCOM logs show different sign values between :RD-0.00296 and

> > :RD0.00298

> >

> >

> > ACP logs

> > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > WF=no]

> > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> >

> > 07:07:36 Comet elements for 0041P --> RA=16:49:37 Dec=57. 31' 23" (J2000)

> > 07:07:36 [flip check: Tn=-300s HAc=-3913s GW=F HAz=-3915s DWz=F WF=no]

> > 07:07:36 (doing orbital tracking. RA 0.0979 "/sec, Dec -0.0448 "/sec)

> >

> >

> >

> >

> > Regards,

> > Yves

> >

> >

> >

> >

> >

> > Le 16/04/17 . 15:48, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> > gto@yahoogroups.com> a .crit :

> >

> >

> >

> > Then I'm not sure I understand your logs. Why would ACP send a positive rate

> one

> > night, and a negative the next?

> >

> > -Ray Gralak

> > Author of APCC (Astro-Physics Command Center): www.astro-

> > physics.com/index.htm?products/accessories/software/apcc/apcc

> > Author of PEMPro: www.ccdware.com

> > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > Author of PulseGuide: www.pulseguide.com

> > Author of Sigma: www.gralak.com/sigma

> >

> > > -----Original Message-----

> > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > Sent: Sunday, April 16, 2017 12:29 PM

> > > To: ap-gto@yahoogroups.com

> > > Subject: Re : RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> behaviour

> > >

> > >

> > >

> > > Ray,

> > >

> > >

> > > UPDATE: The comet was always on the same side of the meridian (East) during

> > my

> > > tests.

> > >

> > > Yves

> > >

> > >

> > > Le 16/04/17 . 14:53, "'Ray Gralak (Groups)' groups3@... [ap-gto]"

> ap-

> > > gto@yahoogroups.com> a .crit :

> > >

> > >

> > >

> > > Yves,

> > >

> > > When switching side of pier, the declination direction has to be multiplied by -1.

> Is

> > it

> > > possible that the pier side had changed?

> > >

> > > -Ray Gralak

> > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > Author of PEMPro: www.ccdware.com

> > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > Author of PulseGuide: www.pulseguide.com

> > > Author of Sigma: www.gralak.com/sigma

> > >

> > > > -----Original Message-----

> > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > Sent: Sunday, April 16, 2017 11:09 AM

> > > > To: ap-gto@yahoogroups.com

> > > > Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> > > >

> > > >

> > > >

> > > > Hi Ray,

> > > >

> > > > Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed a

> > vertical

> > > > nucleus trail even if I was tracking on the comet. I've inspected images took 3

> > > > weeks earlier and saw also a small nucleus trail but at that time I thought it

> was

> > > an

> > > > elongated form nucleus but I was wrong. This time, it was more evident that

> the

> > > > mount was not tracking the comet as it should.

> > > >

> > > > The weird part is that imaging session began with this behaviour and my last

> > > > imaging session was ok.

> > > >

> > > > I began to suspect APCC tracking correction but seems to have nothing to do

> > > > because tracking correction was enabled during my last imaging tests.

> > > >

> > > > However, in inspecting log files I've noticed something that needs to be share

> to

> > > > your attention.

> > > >

> > > > Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and

> > > APCC.

> > > > Please note the difference in value between the two AP ASCOM log sections

> > (AP

> > > > ASCOM driver that produce vertical nucleus trail and AP ASCOM driver WITH

> > > good

> > > > comet tracking). One :RDxxxxx# is negative and the other is positive. The

> > problem

> > > > seems related to this anomaly.

> > > >

> > > > Ray, I will sent you complete logs and images on request.

> > > >

> > > > ASCOM and APCC updated to their latest version.

> > > >

> > > > HAPPY EASTER!!!

> > > >

> > > > Regards,

> > > > Yves

> > > >

> > > >

> > > >

> > > > ACP v7 (DC3-Dreams) time in UT

> > > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21"

> (J2000)

> > > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > > > WF=no]

> > > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > > >

> > > > AP ASCOM driver that produce vertical nucleus trail

> > > > 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> > > > RightAscensionRate = 6.65091663831767E-03

> > > > 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool TX=':RR-

> > > > 0.00665#'

> > > > 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> > > > Received (TX=':RR-0.00665#'), RX='1'

> > > > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> > > > -0.044520572702055

> > > > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> > > > 0.00296#'

> > > > 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> > > > Received (TX=':RD-0.00296#'), RX='1'

> > > >

> > > > APCC

> > > > 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-0.00665#

> > > > 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX from

> > > > VPort 0: :RR-0.00665#

> > > > 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> > > > 0.00665#), TX: 1

> > > > 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate Change:

> > > > -0.00665

> > > > 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> > > > '21:10:17.4#'

> > > > 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX = '#:GS#'

> > > > 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-0.00296#

> > > > 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> > > > '09:46:22.7#'

> > > > 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX = '#:GR#'

> > > > 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX from

> > > > VPort 0: :RD-0.00296#

> > > > 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> > > > 0.00296#), TX: 1

> > > >

> > > >

> > > >

> > >

> >

> **********************************************************************************************

> > > > *********************************

> > > >

> > > >

> > > > AP ASCOM driver WITH good comet tracking

> > > > 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> > > > RightAscensionRate = 6.50663785895112E-03

> > > > 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool TX=':RR-

> > > > 0.00651#'

> > > > 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> > > > Received (TX=':RR-0.00651#'), RX='1'

> > > > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> > > > -4.48155149186675E-02

> > > > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > > > TX=':RD0.00298#'

> > > > 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> > > > Received (TX=':RD0.00298#'), RX='1'

> > > >

> > > >

> > > > END OF LOG

> > > >

> > > >

> > > >

> > >

> > >

> > >

> > >

> >

> >

> >

> >

>

>

>

>







----------------------------

#56580 Apr 16, 2017

Ray,

Ok concerning the ASCOM option.

Here are two sections of ASCOM logs already reported earlier.

028684 2017-04-13 21:10:17.448: . . . . . .ASCOM: Info . . .: SET DeclinationRate = -0.044520572702055028685 2017-04-13 21:10:17.466: . . . . . Driver: Info . . .: CommandBool TX=':RD-0.00296#'

004275 2017-04-14 03:07:36.386: . . . . . .ASCOM: Info . . .: SET DeclinationRate = -4.48155149186675E-02004276 2017-04-14 03:07:36.410: . . . . . Driver: Info . . .: CommandBool TX=':RD0.00298#'



----------------------------

#56582 Apr 16, 2017

Hi Yves,



The ":NS#" command swaps N/S directions. The driver normalizes the direction when that option is selected so that Dec autoguider moves are always normalized based on pier side.



However, I just checked the code and the *only* way the driver changes DeclinationRate sign is if their has been a pier flip. So, are you sure that in 6 hours of time (9:10 pm to 3.07 am) that there could not have been a pier flip?



BTW, by ASCOM (and A-P) definition, a pier flip includes any scope movement where the scope's Dec axis moves through Dec=90 (or Dec=-90). Their doesn't have to be a physical pier flip, but one usually will happen if the same object is being targeted.



If you are sure there wasn't a pier flip, then it had to be ACP sending an inverted rate.



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma



> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Sunday, April 16, 2017 6:20 PM

> To: ap-gto@yahoogroups.com

> Subject: Re : RE: RE: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> behaviour

>

>

>

> Ray,

>

> Ok concerning the ASCOM option.

>

> Here are two sections of ASCOM logs already reported earlier.

>

> 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> -0.044520572702055

> 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> 0.00296#'

>

> 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> -4.48155149186675E-02

> 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> TX=':RD0.00298#'

>

> In the first log section,The SET DeclinationRate has a negative value like the

> CommandBool TX=':RD-0.00296#' BUT this was causing bad tracking.

> In the second log section The SET DeclinationRate has a negative value as

> opposite to the CommandBool TX=':RD-0.00298#' who has positive value. However

> the comet tracking was ok.

>

> According to the logs, does the :RDxxxx# value should always be multiplying the

> SET DeclinationRate by -1? Does these values are related to each other?

>

> What is the internal DEC direction protocol command that would cause my

> problem? Thanks a lot!

>

> Regards,

> Yves

>

>

>

> Le 16/04/17, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> gto@yahoogroups.com> a .crit :

>

>

>

> Yes, that option. Internal Dec direction could be changed by sending a command to

> the mount or by clicking a button in the driver's UI.

>

> Perhaps it is better to not turn off "recommended" options...

>

> -Ray Gralak

> Author of APCC (Astro-Physics Command Center): www.astro-

> physics.com/index.htm?products/accessories/software/apcc/apcc

> Author of PEMPro: www.ccdware.com

> Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> Author of PulseGuide: www.pulseguide.com

> Author of Sigma: www.gralak.com/sigma

>

> > -----Original Message-----

> > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > Sent: Sunday, April 16, 2017 1:34 PM

> > To: ap-gto@yahoogroups.com

> > Subject: Re : RE: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > behaviour

> >

> >

> >

> > Ray,

> >

> > The ASCOM Calibrate move directions on first slew (recommend) was disabled.

> > Were you talking about that option?

> >

> > If yes, how DEC direction could change during the same night if that previous

> option

> > was still disabled?

> >

> >

> > Yves

> >

> >

> >

> >

> > Le 16/04/17 . 16:17, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> > gto@yahoogroups.com> a .crit :

> >

> >

> >

> > If that's so, something misconfigured the dec direction value in the driver. There is

> > an option in the driver to configure that after the first slew. If you had that

> > misconfigured then the value could be sent as a negative. That is the only

> > explanation that I can think of since you say the scope was on the same side of

> pier.

> >

> > -Ray Gralak

> > Author of APCC (Astro-Physics Command Center): www.astro-

> > physics.com/index.htm?products/accessories/software/apcc/apcc

> > Author of PEMPro: www.ccdware.com

> > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > Author of PulseGuide: www.pulseguide.com

> > Author of Sigma: www.gralak.com/sigma

> >

> > > -----Original Message-----

> > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > Sent: Sunday, April 16, 2017 1:06 PM

> > > To: ap-gto@yahoogroups.com

> > > Subject: Re : RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > > behaviour

> > >

> > >

> > >

> > > Ray,

> > >

> > > ACP was sending approx. same orbital values on the same night according to

> the

> > > logs. However ASCOM logs show different sign values between :RD-0.00296

> and

> > > :RD0.00298

> > >

> > >

> > > ACP logs

> > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21" (J2000)

> > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > > WF=no]

> > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > >

> > > 07:07:36 Comet elements for 0041P --> RA=16:49:37 Dec=57. 31' 23" (J2000)

> > > 07:07:36 [flip check: Tn=-300s HAc=-3913s GW=F HAz=-3915s DWz=F

> WF=no]

> > > 07:07:36 (doing orbital tracking. RA 0.0979 "/sec, Dec -0.0448 "/sec)

> > >

> > >

> > >

> > >

> > > Regards,

> > > Yves

> > >

> > >

> > >

> > >

> > >

> > > Le 16/04/17 . 15:48, "'Ray Gralak (Groups)' groups3@... [ap-gto]"

> ap-

> > > gto@yahoogroups.com> a .crit :

> > >

> > >

> > >

> > > Then I'm not sure I understand your logs. Why would ACP send a positive rate

> > one

> > > night, and a negative the next?

> > >

> > > -Ray Gralak

> > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > Author of PEMPro: www.ccdware.com

> > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > Author of PulseGuide: www.pulseguide.com

> > > Author of Sigma: www.gralak.com/sigma

> > >

> > > > -----Original Message-----

> > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > Sent: Sunday, April 16, 2017 12:29 PM

> > > > To: ap-gto@yahoogroups.com

> > > > Subject: Re : RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > behaviour

> > > >

> > > >

> > > >

> > > > Ray,

> > > >

> > > >

> > > > UPDATE: The comet was always on the same side of the meridian (East)

> during

> > > my

> > > > tests.

> > > >

> > > > Yves

> > > >

> > > >

> > > > Le 16/04/17 . 14:53, "'Ray Gralak (Groups)' groups3@... [ap-gto]"

> > ap-

> > > > gto@yahoogroups.com> a .crit :

> > > >

> > > >

> > > >

> > > > Yves,

> > > >

> > > > When switching side of pier, the declination direction has to be multiplied by -

> 1.

> > Is

> > > it

> > > > possible that the pier side had changed?

> > > >

> > > > -Ray Gralak

> > > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > > Author of PEMPro: www.ccdware.com

> > > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > > Author of PulseGuide: www.pulseguide.com

> > > > Author of Sigma: www.gralak.com/sigma

> > > >

> > > > > -----Original Message-----

> > > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > > Sent: Sunday, April 16, 2017 11:09 AM

> > > > > To: ap-gto@yahoogroups.com

> > > > > Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> > > > >

> > > > >

> > > > >

> > > > > Hi Ray,

> > > > >

> > > > > Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed a

> > > vertical

> > > > > nucleus trail even if I was tracking on the comet. I've inspected images took

> 3

> > > > > weeks earlier and saw also a small nucleus trail but at that time I thought it

> > was

> > > > an

> > > > > elongated form nucleus but I was wrong. This time, it was more evident that

> > the

> > > > > mount was not tracking the comet as it should.

> > > > >

> > > > > The weird part is that imaging session began with this behaviour and my

> last

> > > > > imaging session was ok.

> > > > >

> > > > > I began to suspect APCC tracking correction but seems to have nothing to

> do

> > > > > because tracking correction was enabled during my last imaging tests.

> > > > >

> > > > > However, in inspecting log files I've noticed something that needs to be

> share

> > to

> > > > > your attention.

> > > > >

> > > > > Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver and

> > > > APCC.

> > > > > Please note the difference in value between the two AP ASCOM log sections

> > > (AP

> > > > > ASCOM driver that produce vertical nucleus trail and AP ASCOM driver

> WITH

> > > > good

> > > > > comet tracking). One :RDxxxxx# is negative and the other is positive. The

> > > problem

> > > > > seems related to this anomaly.

> > > > >

> > > > > Ray, I will sent you complete logs and images on request.

> > > > >

> > > > > ASCOM and APCC updated to their latest version.

> > > > >

> > > > > HAPPY EASTER!!!

> > > > >

> > > > > Regards,

> > > > > Yves

> > > > >

> > > > >

> > > > >

> > > > > ACP v7 (DC3-Dreams) time in UT

> > > > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21"

> > (J2000)

> > > > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > > > > WF=no]

> > > > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > > > >

> > > > > AP ASCOM driver that produce vertical nucleus trail

> > > > > 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> > > > > RightAscensionRate = 6.65091663831767E-03

> > > > > 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool TX=':RR-

> > > > > 0.00665#'

> > > > > 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> > > > > Received (TX=':RR-0.00665#'), RX='1'

> > > > > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> > > > > -0.044520572702055

> > > > > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> > > > > 0.00296#'

> > > > > 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> > > > > Received (TX=':RD-0.00296#'), RX='1'

> > > > >

> > > > > APCC

> > > > > 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-

> 0.00665#

> > > > > 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX from

> > > > > VPort 0: :RR-0.00665#

> > > > > 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> > > > > 0.00665#), TX: 1

> > > > > 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate

> Change:

> > > > > -0.00665

> > > > > 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> > > > > '21:10:17.4#'

> > > > > 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX = '#:GS#'

> > > > > 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-

> 0.00296#

> > > > > 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> > > > > '09:46:22.7#'

> > > > > 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX = '#:GR#'

> > > > > 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX from

> > > > > VPort 0: :RD-0.00296#

> > > > > 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> > > > > 0.00296#), TX: 1

> > > > >

> > > > >

> > > > >

> > > >

> > >

> >

> **********************************************************************************************

> > > > > *********************************

> > > > >

> > > > >

> > > > > AP ASCOM driver WITH good comet tracking

> > > > > 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> > > > > RightAscensionRate = 6.50663785895112E-03

> > > > > 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool TX=':RR-

> > > > > 0.00651#'

> > > > > 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> > > > > Received (TX=':RR-0.00651#'), RX='1'

> > > > > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> > > > > -4.48155149186675E-02

> > > > > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > > > > TX=':RD0.00298#'

> > > > > 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> > > > > Received (TX=':RD0.00298#'), RX='1'

> > > > >

> > > > >

> > > > > END OF LOG

> > > > >

> > > > >

> > > > >

> > > >

> > > >

> > > >

> > > >

> > >

> > >

> > >

> > >

> >

> >

> >

> >

>

>

>

>







----------------------------

#56583 Apr 16, 2017

Thanks Ray for your input,

Hi Yves,

The ":NS#" command swaps N/S directions. The driver normalizes the direction when that option is selected so that Dec autoguider moves are always normalized based on pier side.



----------------------------

#56586 Apr 17, 2017

There was no :NS# code in my ASCOM logs.



A keypad press can also do this without being logged. But as I said, after looking at the code the only way that the declination would be made negative is by changing side-of-pier.

> Anyway, I will give another try on tuesday night if weather permits with "Calibrate

> move directions on first slew" enabled.



You should do that, but I don't think that will help this problem.



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma

> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Sunday, April 16, 2017 10:52 PM

> To: ap-gto@yahoogroups.com

> Subject: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

>

>

>

> Thanks Ray for your input,

>

>

> Hi Yves,

>

> The ":NS#" command swaps N/S directions. The driver normalizes the direction

> when that option is selected so that Dec autoguider moves are always normalized

> based on pier side.

>

> There was no :NS# code in my ASCOM logs.

>

>

>

> Hi Yves,

>

> The ":NS#" command swaps N/S directions. The driver normalizes the direction

> when that option is selected so that Dec autoguider moves are always normalized

> based on pier side.

>

> However, I just checked the code and the *only* way the driver changes

> DeclinationRate sign is if their has been a pier flip. So, are you sure that in 6 hours

> of time (9:10 pm to 3.07 am) that there could not have been a pier flip?

>

> There was no pier flip during that period. The comet crossed the meridian at 04:12

> local time.

>

>

>

> BTW, by ASCOM (and A-P) definition, a pier flip includes any scope movement

> where the scope's Dec axis moves through Dec=90 (or Dec=-90). Their doesn't have

> to be a physical pier flip, but one usually will happen if the same object is being

> targeted.

>

> My mount was always around DEC=+57*46:51(comet 041p) except for autofocus

> star that was on the same side of meridian.

>

>

>

> If you are sure there wasn't a pier flip, then it had to be ACP sending an inverted

> rate.

>

> I really don't know what could be the problem. Three weeks ago I had the same

> problem and three days ago the problem only occured at the beginning of my

> imaging run but disappeared during the same night.

>

>

> Anyway, I will give another try on tuesday night if weather permits with "Calibrate

> move directions on first slew" enabled.

>

>

> I will let you know about my results.

>

>

> Best regards,

> Yves

>

>

>

>

>

>

>

>

> Le 17/04/17 . 00:25, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> gto@yahoogroups.com> a .crit :

>

>

>

> Hi Yves,

>

> The ":NS#" command swaps N/S directions. The driver normalizes the direction

> when that option is selected so that Dec autoguider moves are always normalized

> based on pier side.

>

> However, I just checked the code and the *only* way the driver changes

> DeclinationRate sign is if their has been a pier flip. So, are you sure that in 6 hours

> of time (9:10 pm to 3.07 am) that there could not have been a pier flip?

>

> BTW, by ASCOM (and A-P) definition, a pier flip includes any scope movement

> where the scope's Dec axis moves through Dec=90 (or Dec=-90). Their doesn't have

> to be a physical pier flip, but one usually will happen if the same object is being

> targeted.

>

> If you are sure there wasn't a pier flip, then it had to be ACP sending an inverted

> rate.

>

> -Ray Gralak

> Author of APCC (Astro-Physics Command Center): www.astro-

> physics.com/index.htm?products/accessories/software/apcc/apcc

> Author of PEMPro: www.ccdware.com

> Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> Author of PulseGuide: www.pulseguide.com

> Author of Sigma: www.gralak.com/sigma

>

> > -----Original Message-----

> > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > Sent: Sunday, April 16, 2017 6:20 PM

> > To: ap-gto@yahoogroups.com

> > Subject: Re : RE: RE: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital

> tracking

> > behaviour

> >

> >

> >

> > Ray,

> >

> > Ok concerning the ASCOM option.

> >

> > Here are two sections of ASCOM logs already reported earlier.

> >

> > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> > -0.044520572702055

> > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> > 0.00296#'

> >

> > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> > -4.48155149186675E-02

> > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > TX=':RD0.00298#'

> >

> > In the first log section,The SET DeclinationRate has a negative value like the

> > CommandBool TX=':RD-0.00296#' BUT this was causing bad tracking.

> > In the second log section The SET DeclinationRate has a negative value as

> > opposite to the CommandBool TX=':RD-0.00298#' who has positive value.

> However

> > the comet tracking was ok.

> >

> > According to the logs, does the :RDxxxx# value should always be multiplying the

> > SET DeclinationRate by -1? Does these values are related to each other?

> >

> > What is the internal DEC direction protocol command that would cause my

> > problem? Thanks a lot!

> >

> > Regards,

> > Yves

> >

> >

> >

> > Le 16/04/17, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> > gto@yahoogroups.com> a .crit :

> >

> >

> >

> > Yes, that option. Internal Dec direction could be changed by sending a command

> to

> > the mount or by clicking a button in the driver's UI.

> >

> > Perhaps it is better to not turn off "recommended" options...

> >

> > -Ray Gralak

> > Author of APCC (Astro-Physics Command Center): www.astro-

> > physics.com/index.htm?products/accessories/software/apcc/apcc

> > Author of PEMPro: www.ccdware.com

> > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > Author of PulseGuide: www.pulseguide.com

> > Author of Sigma: www.gralak.com/sigma

> >

> > > -----Original Message-----

> > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > Sent: Sunday, April 16, 2017 1:34 PM

> > > To: ap-gto@yahoogroups.com

> > > Subject: Re : RE: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > > behaviour

> > >

> > >

> > >

> > > Ray,

> > >

> > > The ASCOM Calibrate move directions on first slew (recommend) was disabled.

> > > Were you talking about that option?

> > >

> > > If yes, how DEC direction could change during the same night if that previous

> > option

> > > was still disabled?

> > >

> > >

> > > Yves

> > >

> > >

> > >

> > >

> > > Le 16/04/17 . 16:17, "'Ray Gralak (Groups)' groups3@... [ap-gto]"

> ap-

> > > gto@yahoogroups.com> a .crit :

> > >

> > >

> > >

> > > If that's so, something misconfigured the dec direction value in the driver. There

> is

> > > an option in the driver to configure that after the first slew. If you had that

> > > misconfigured then the value could be sent as a negative. That is the only

> > > explanation that I can think of since you say the scope was on the same side of

> > pier.

> > >

> > > -Ray Gralak

> > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > Author of PEMPro: www.ccdware.com

> > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > Author of PulseGuide: www.pulseguide.com

> > > Author of Sigma: www.gralak.com/sigma

> > >

> > > > -----Original Message-----

> > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > Sent: Sunday, April 16, 2017 1:06 PM

> > > > To: ap-gto@yahoogroups.com

> > > > Subject: Re : RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > > > behaviour

> > > >

> > > >

> > > >

> > > > Ray,

> > > >

> > > > ACP was sending approx. same orbital values on the same night according to

> > the

> > > > logs. However ASCOM logs show different sign values between :RD-0.00296

> > and

> > > > :RD0.00298

> > > >

> > > >

> > > > ACP logs

> > > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21"

> (J2000)

> > > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > > > WF=no]

> > > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > > >

> > > > 07:07:36 Comet elements for 0041P --> RA=16:49:37 Dec=57. 31' 23"

> (J2000)

> > > > 07:07:36 [flip check: Tn=-300s HAc=-3913s GW=F HAz=-3915s DWz=F

> > WF=no]

> > > > 07:07:36 (doing orbital tracking. RA 0.0979 "/sec, Dec -0.0448 "/sec)

> > > >

> > > >

> > > >

> > > >

> > > > Regards,

> > > > Yves

> > > >

> > > >

> > > >

> > > >

> > > >

> > > > Le 16/04/17 . 15:48, "'Ray Gralak (Groups)' groups3@... [ap-gto]"

> > ap-

> > > > gto@yahoogroups.com> a .crit :

> > > >

> > > >

> > > >

> > > > Then I'm not sure I understand your logs. Why would ACP send a positive

> rate

> > > one

> > > > night, and a negative the next?

> > > >

> > > > -Ray Gralak

> > > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > > Author of PEMPro: www.ccdware.com

> > > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > > Author of PulseGuide: www.pulseguide.com

> > > > Author of Sigma: www.gralak.com/sigma

> > > >

> > > > > -----Original Message-----

> > > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > > Sent: Sunday, April 16, 2017 12:29 PM

> > > > > To: ap-gto@yahoogroups.com

> > > > > Subject: Re : RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > > behaviour

> > > > >

> > > > >

> > > > >

> > > > > Ray,

> > > > >

> > > > >

> > > > > UPDATE: The comet was always on the same side of the meridian (East)

> > during

> > > > my

> > > > > tests.

> > > > >

> > > > > Yves

> > > > >

> > > > >

> > > > > Le 16/04/17 . 14:53, "'Ray Gralak (Groups)' groups3@... [ap-gto]"

> > > ap-

> > > > > gto@yahoogroups.com> a .crit :

> > > > >

> > > > >

> > > > >

> > > > > Yves,

> > > > >

> > > > > When switching side of pier, the declination direction has to be multiplied by

> -

> > 1.

> > > Is

> > > > it

> > > > > possible that the pier side had changed?

> > > > >

> > > > > -Ray Gralak

> > > > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > > > Author of PEMPro: www.ccdware.com

> > > > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > > > Author of PulseGuide: www.pulseguide.com

> > > > > Author of Sigma: www.gralak.com/sigma

> > > > >

> > > > > > -----Original Message-----

> > > > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > > > Sent: Sunday, April 16, 2017 11:09 AM

> > > > > > To: ap-gto@yahoogroups.com

> > > > > > Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> > > > > >

> > > > > >

> > > > > >

> > > > > > Hi Ray,

> > > > > >

> > > > > > Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed a

> > > > vertical

> > > > > > nucleus trail even if I was tracking on the comet. I've inspected images

> took

> > 3

> > > > > > weeks earlier and saw also a small nucleus trail but at that time I thought

> it

> > > was

> > > > > an

> > > > > > elongated form nucleus but I was wrong. This time, it was more evident

> that

> > > the

> > > > > > mount was not tracking the comet as it should.

> > > > > >

> > > > > > The weird part is that imaging session began with this behaviour and my

> > last

> > > > > > imaging session was ok.

> > > > > >

> > > > > > I began to suspect APCC tracking correction but seems to have nothing to

> > do

> > > > > > because tracking correction was enabled during my last imaging tests.

> > > > > >

> > > > > > However, in inspecting log files I've noticed something that needs to be

> > share

> > > to

> > > > > > your attention.

> > > > > >

> > > > > > Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver

> and

> > > > > APCC.

> > > > > > Please note the difference in value between the two AP ASCOM log

> sections

> > > > (AP

> > > > > > ASCOM driver that produce vertical nucleus trail and AP ASCOM driver

> > WITH

> > > > > good

> > > > > > comet tracking). One :RDxxxxx# is negative and the other is positive. The

> > > > problem

> > > > > > seems related to this anomaly.

> > > > > >

> > > > > > Ray, I will sent you complete logs and images on request.

> > > > > >

> > > > > > ASCOM and APCC updated to their latest version.

> > > > > >

> > > > > > HAPPY EASTER!!!

> > > > > >

> > > > > > Regards,

> > > > > > Yves

> > > > > >

> > > > > >

> > > > > >

> > > > > > ACP v7 (DC3-Dreams) time in UT

> > > > > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21"

> > > (J2000)

> > > > > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s

> DWz=F

> > > > > > WF=no]

> > > > > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > > > > >

> > > > > > AP ASCOM driver that produce vertical nucleus trail

> > > > > > 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> > > > > > RightAscensionRate = 6.65091663831767E-03

> > > > > > 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool TX=':RR-

> > > > > > 0.00665#'

> > > > > > 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> > > > > > Received (TX=':RR-0.00665#'), RX='1'

> > > > > > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> > > > > > -0.044520572702055

> > > > > > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> > > > > > 0.00296#'

> > > > > > 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> > > > > > Received (TX=':RD-0.00296#'), RX='1'

> > > > > >

> > > > > > APCC

> > > > > > 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-

> > 0.00665#

> > > > > > 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX

> from

> > > > > > VPort 0: :RR-0.00665#

> > > > > > 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> > > > > > 0.00665#), TX: 1

> > > > > > 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate

> > Change:

> > > > > > -0.00665

> > > > > > 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> > > > > > '21:10:17.4#'

> > > > > > 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX =

> '#:GS#'

> > > > > > 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-

> > 0.00296#

> > > > > > 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> > > > > > '09:46:22.7#'

> > > > > > 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX =

> '#:GR#'

> > > > > > 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX

> from

> > > > > > VPort 0: :RD-0.00296#

> > > > > > 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> > > > > > 0.00296#), TX: 1

> > > > > >

> > > > > >

> > > > > >

> > > > >

> > > >

> > >

> >

> **********************************************************************************************

> > > > > > *********************************

> > > > > >

> > > > > >

> > > > > > AP ASCOM driver WITH good comet tracking

> > > > > > 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> > > > > > RightAscensionRate = 6.50663785895112E-03

> > > > > > 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool TX=':RR-

> > > > > > 0.00651#'

> > > > > > 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> > > > > > Received (TX=':RR-0.00651#'), RX='1'

> > > > > > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> > > > > > -4.48155149186675E-02

> > > > > > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > > > > > TX=':RD0.00298#'

> > > > > > 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> > > > > > Received (TX=':RD0.00298#'), RX='1'

> > > > > >

> > > > > >

> > > > > > END OF LOG

> > > > > >

> > > > > >

> > > > > >

> > > > >

> > > > >

> > > > >

> > > > >

> > > >

> > > >

> > > >

> > > >

> > >

> > >

> > >

> > >

> >

> >

> >

> >

>

>

>

>







----------------------------

#56597 Apr 18, 2017

Hi Yves,

> In my case, no keypad plugged.

>

> . According to my ASCOM logs, pierside=west (telescope pointing east) all night

> long

> . ACP orbital tracking values were consistent

> . The ASCOM SET DeclinationRate was always a negative value (good tracking or

> not)

> . ASCOM logs :RD-0.00296# --> bad tracking ; :RD0.00296# --> good tracking



Yves, I checked again and I can't find any way for the declination rate to become negative in the driver unless pier side had changed. So, did you manually change the rate to a positive value to check if that fixes the drift? Or, do you believe the driver did that on its own?

> Does the :NS# command is only affected the :RDxxxx# command?



As I said before, after looking at the driver's source code I cannot find any way that the NS command would affect the :RD command. A positive value to the RD (or RR) command always produces a clockwise motion independent of the NS command.

> Should the :NS# command is not supposed to affect the SET DeclinationRate also?



I'm not sure I understand what you are asking, but the RD command *is* the declination rate command. And, as I said, it is not affected by the NS command. Only the autoguider and button press move commands are affected.



Anyway, let's take this off line. If you can reproduce the behavior then please:



1) Use the APCC log zipper application and include all of the logs and settings (APCC+driver).

2) include complete information about your telescope setup

3) whether or not you were using a pointing/tracking rate model

4) the time when the problem occurred, or line numbers in the logs.

5) include ACP log(s) showing the rates it was trying to send.



Please send your zip file + information to groups3 at Gralak dot com and copy Howard at A-P so that A-P is in the loop.



Best regards,



-Ray Gralak

Author of APCC (Astro-Physics Command Center): www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc

Author of PEMPro: www.ccdware.com

Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

Author of PulseGuide: www.pulseguide.com

Author of Sigma: www.gralak.com/sigma



> -----Original Message-----

> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> Sent: Monday, April 17, 2017 9:07 AM

> To: ap-gto@yahoogroups.com

> Subject: Re : RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> behaviour

>

>

>

> Ray,

>

>

> In my case, no keypad plugged.

>

> . According to my ASCOM logs, pierside=west (telescope pointing east) all night

> long

> . ACP orbital tracking values were consistent

> . The ASCOM SET DeclinationRate was always a negative value (good tracking or

> not)

> . ASCOM logs :RD-0.00296# --> bad tracking ; :RD0.00296# --> good tracking

>

>

> Does the :NS# command is only affected the :RDxxxx# command?

>

>

> Should the :NS# command is not supposed to affect the SET DeclinationRate also?

>

>

>

>

> Regards,

> Yves

>

>

>

>

>

> Le 17/04/17 . 08:11, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> gto@yahoogroups.com> a .crit :

>

>

>

> > There was no :NS# code in my ASCOM logs.

>

> A keypad press can also do this without being logged. But as I said, after looking at

> the code the only way that the declination would be made negative is by changing

> side-of-pier.

>

> > Anyway, I will give another try on tuesday night if weather permits with "Calibrate

> > move directions on first slew" enabled.

>

> You should do that, but I don't think that will help this problem.

>

> -Ray Gralak

> Author of APCC (Astro-Physics Command Center): www.astro-

> physics.com/index.htm?products/accessories/software/apcc/apcc

> Author of PEMPro: www.ccdware.com

> Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> Author of PulseGuide: www.pulseguide.com

> Author of Sigma: www.gralak.com/sigma

>

> > -----Original Message-----

> > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > Sent: Sunday, April 16, 2017 10:52 PM

> > To: ap-gto@yahoogroups.com

> > Subject: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> >

> >

> >

> > Thanks Ray for your input,

> >

> >

> > Hi Yves,

> >

> > The ":NS#" command swaps N/S directions. The driver normalizes the direction

> > when that option is selected so that Dec autoguider moves are always normalized

> > based on pier side.

> >

> > There was no :NS# code in my ASCOM logs.

> >

> >

> >

> > Hi Yves,

> >

> > The ":NS#" command swaps N/S directions. The driver normalizes the direction

> > when that option is selected so that Dec autoguider moves are always normalized

> > based on pier side.

> >

> > However, I just checked the code and the *only* way the driver changes

> > DeclinationRate sign is if their has been a pier flip. So, are you sure that in 6

> hours

> > of time (9:10 pm to 3.07 am) that there could not have been a pier flip?

> >

> > There was no pier flip during that period. The comet crossed the meridian at 04:12

> > local time.

> >

> >

> >

> > BTW, by ASCOM (and A-P) definition, a pier flip includes any scope movement

> > where the scope's Dec axis moves through Dec=90 (or Dec=-90). Their doesn't

> have

> > to be a physical pier flip, but one usually will happen if the same object is being

> > targeted.

> >

> > My mount was always around DEC=+57*46:51(comet 041p) except for autofocus

> > star that was on the same side of meridian.

> >

> >

> >

> > If you are sure there wasn't a pier flip, then it had to be ACP sending an inverted

> > rate.

> >

> > I really don't know what could be the problem. Three weeks ago I had the same

> > problem and three days ago the problem only occured at the beginning of my

> > imaging run but disappeared during the same night.

> >

> >

> > Anyway, I will give another try on tuesday night if weather permits with "Calibrate

> > move directions on first slew" enabled.

> >

> >

> > I will let you know about my results.

> >

> >

> > Best regards,

> > Yves

> >

> >

> >

> >

> >

> >

> >

> >

> > Le 17/04/17 . 00:25, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> > gto@yahoogroups.com> a .crit :

> >

> >

> >

> > Hi Yves,

> >

> > The ":NS#" command swaps N/S directions. The driver normalizes the direction

> > when that option is selected so that Dec autoguider moves are always normalized

> > based on pier side.

> >

> > However, I just checked the code and the *only* way the driver changes

> > DeclinationRate sign is if their has been a pier flip. So, are you sure that in 6

> hours

> > of time (9:10 pm to 3.07 am) that there could not have been a pier flip?

> >

> > BTW, by ASCOM (and A-P) definition, a pier flip includes any scope movement

> > where the scope's Dec axis moves through Dec=90 (or Dec=-90). Their doesn't

> have

> > to be a physical pier flip, but one usually will happen if the same object is being

> > targeted.

> >

> > If you are sure there wasn't a pier flip, then it had to be ACP sending an inverted

> > rate.

> >

> > -Ray Gralak

> > Author of APCC (Astro-Physics Command Center): www.astro-

> > physics.com/index.htm?products/accessories/software/apcc/apcc

> > Author of PEMPro: www.ccdware.com

> > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > Author of PulseGuide: www.pulseguide.com

> > Author of Sigma: www.gralak.com/sigma

> >

> > > -----Original Message-----

> > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > Sent: Sunday, April 16, 2017 6:20 PM

> > > To: ap-gto@yahoogroups.com

> > > Subject: Re : RE: RE: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital

> > tracking

> > > behaviour

> > >

> > >

> > >

> > > Ray,

> > >

> > > Ok concerning the ASCOM option.

> > >

> > > Here are two sections of ASCOM logs already reported earlier.

> > >

> > > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate =

> > > -0.044520572702055

> > > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool TX=':RD-

> > > 0.00296#'

> > >

> > > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate =

> > > -4.48155149186675E-02

> > > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > > TX=':RD0.00298#'

> > >

> > > In the first log section,The SET DeclinationRate has a negative value like the

> > > CommandBool TX=':RD-0.00296#' BUT this was causing bad tracking.

> > > In the second log section The SET DeclinationRate has a negative value as

> > > opposite to the CommandBool TX=':RD-0.00298#' who has positive value.

> > However

> > > the comet tracking was ok.

> > >

> > > According to the logs, does the :RDxxxx# value should always be multiplying the

> > > SET DeclinationRate by -1? Does these values are related to each other?

> > >

> > > What is the internal DEC direction protocol command that would cause my

> > > problem? Thanks a lot!

> > >

> > > Regards,

> > > Yves

> > >

> > >

> > >

> > > Le 16/04/17, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-

> > > gto@yahoogroups.com> a .crit :

> > >

> > >

> > >

> > > Yes, that option. Internal Dec direction could be changed by sending a

> command

> > to

> > > the mount or by clicking a button in the driver's UI.

> > >

> > > Perhaps it is better to not turn off "recommended" options...

> > >

> > > -Ray Gralak

> > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > Author of PEMPro: www.ccdware.com

> > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > Author of PulseGuide: www.pulseguide.com

> > > Author of Sigma: www.gralak.com/sigma

> > >

> > > > -----Original Message-----

> > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > Sent: Sunday, April 16, 2017 1:34 PM

> > > > To: ap-gto@yahoogroups.com

> > > > Subject: Re : RE: RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital

> tracking

> > > > behaviour

> > > >

> > > >

> > > >

> > > > Ray,

> > > >

> > > > The ASCOM Calibrate move directions on first slew (recommend) was

> disabled.

> > > > Were you talking about that option?

> > > >

> > > > If yes, how DEC direction could change during the same night if that previous

> > > option

> > > > was still disabled?

> > > >

> > > >

> > > > Yves

> > > >

> > > >

> > > >

> > > >

> > > > Le 16/04/17 . 16:17, "'Ray Gralak (Groups)' groups3@... [ap-gto]"

> > ap-

> > > > gto@yahoogroups.com> a .crit :

> > > >

> > > >

> > > >

> > > > If that's so, something misconfigured the dec direction value in the driver.

> There

> > is

> > > > an option in the driver to configure that after the first slew. If you had that

> > > > misconfigured then the value could be sent as a negative. That is the only

> > > > explanation that I can think of since you say the scope was on the same side

> of

> > > pier.

> > > >

> > > > -Ray Gralak

> > > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > > Author of PEMPro: www.ccdware.com

> > > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > > Author of PulseGuide: www.pulseguide.com

> > > > Author of Sigma: www.gralak.com/sigma

> > > >

> > > > > -----Original Message-----

> > > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > > Sent: Sunday, April 16, 2017 1:06 PM

> > > > > To: ap-gto@yahoogroups.com

> > > > > Subject: Re : RE: RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > > > > behaviour

> > > > >

> > > > >

> > > > >

> > > > > Ray,

> > > > >

> > > > > ACP was sending approx. same orbital values on the same night according

> to

> > > the

> > > > > logs. However ASCOM logs show different sign values between :RD-

> 0.00296

> > > and

> > > > > :RD0.00298

> > > > >

> > > > >

> > > > > ACP logs

> > > > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21"

> > (J2000)

> > > > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s DWz=F

> > > > > WF=no]

> > > > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > > > >

> > > > > 07:07:36 Comet elements for 0041P --> RA=16:49:37 Dec=57. 31' 23"

> > (J2000)

> > > > > 07:07:36 [flip check: Tn=-300s HAc=-3913s GW=F HAz=-3915s DWz=F

> > > WF=no]

> > > > > 07:07:36 (doing orbital tracking. RA 0.0979 "/sec, Dec -0.0448 "/sec)

> > > > >

> > > > >

> > > > >

> > > > >

> > > > > Regards,

> > > > > Yves

> > > > >

> > > > >

> > > > >

> > > > >

> > > > >

> > > > > Le 16/04/17 . 15:48, "'Ray Gralak (Groups)' groups3@... [ap-gto]"

> > > ap-

> > > > > gto@yahoogroups.com> a .crit :

> > > > >

> > > > >

> > > > >

> > > > > Then I'm not sure I understand your logs. Why would ACP send a positive

> > rate

> > > > one

> > > > > night, and a negative the next?

> > > > >

> > > > > -Ray Gralak

> > > > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > > > Author of PEMPro: www.ccdware.com

> > > > > Author of Astro-Physics V2 ASCOM Driver: www.gralak.com/apdriver

> > > > > Author of PulseGuide: www.pulseguide.com

> > > > > Author of Sigma: www.gralak.com/sigma

> > > > >

> > > > > > -----Original Message-----

> > > > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > > > Sent: Sunday, April 16, 2017 12:29 PM

> > > > > > To: ap-gto@yahoogroups.com

> > > > > > Subject: Re : RE: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking

> > > > behaviour

> > > > > >

> > > > > >

> > > > > >

> > > > > > Ray,

> > > > > >

> > > > > >

> > > > > > UPDATE: The comet was always on the same side of the meridian (East)

> > > during

> > > > > my

> > > > > > tests.

> > > > > >

> > > > > > Yves

> > > > > >

> > > > > >

> > > > > > Le 16/04/17 . 14:53, "'Ray Gralak (Groups)' groups3@... [ap-

> gto]"

> > > > ap-

> > > > > > gto@yahoogroups.com> a .crit :

> > > > > >

> > > > > >

> > > > > >

> > > > > > Yves,

> > > > > >

> > > > > > When switching side of pier, the declination direction has to be multiplied

> by

> > -

> > > 1.

> > > > Is

> > > > > it

> > > > > > possible that the pier side had changed?

> > > > > >

> > > > > > -Ray Gralak

> > > > > > Author of APCC (Astro-Physics Command Center): www.astro-

> > > > > > physics.com/index.htm?products/accessories/software/apcc/apcc

> > > > > > Author of PEMPro: www.ccdware.com

> > > > > > Author of Astro-Physics V2 ASCOM Driver:

> www.gralak.com/apdriver

> > > > > > Author of PulseGuide: www.pulseguide.com

> > > > > > Author of Sigma: www.gralak.com/sigma

> > > > > >

> > > > > > > -----Original Message-----

> > > > > > > From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]

> > > > > > > Sent: Sunday, April 16, 2017 11:09 AM

> > > > > > > To: ap-gto@yahoogroups.com

> > > > > > > Subject: [ap-gto] 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour

> > > > > > >

> > > > > > >

> > > > > > >

> > > > > > > Hi Ray,

> > > > > > >

> > > > > > > Three days ago, when imaging 41P/Tuttle-Giacobini-Kresak, I've noticed

> a

> > > > > vertical

> > > > > > > nucleus trail even if I was tracking on the comet. I've inspected images

> > took

> > > 3

> > > > > > > weeks earlier and saw also a small nucleus trail but at that time I

> thought

> > it

> > > > was

> > > > > > an

> > > > > > > elongated form nucleus but I was wrong. This time, it was more evident

> > that

> > > > the

> > > > > > > mount was not tracking the comet as it should.

> > > > > > >

> > > > > > > The weird part is that imaging session began with this behaviour and my

> > > last

> > > > > > > imaging session was ok.

> > > > > > >

> > > > > > > I began to suspect APCC tracking correction but seems to have nothing

> to

> > > do

> > > > > > > because tracking correction was enabled during my last imaging tests.

> > > > > > >

> > > > > > > However, in inspecting log files I've noticed something that needs to be

> > > share

> > > > to

> > > > > > > your attention.

> > > > > > >

> > > > > > > Here are parts of my log files from ACP (DC3-Dreams), ASCOM driver

> > and

> > > > > > APCC.

> > > > > > > Please note the difference in value between the two AP ASCOM log

> > sections

> > > > > (AP

> > > > > > > ASCOM driver that produce vertical nucleus trail and AP ASCOM driver

> > > WITH

> > > > > > good

> > > > > > > comet tracking). One :RDxxxxx# is negative and the other is positive.

> The

> > > > > problem

> > > > > > > seems related to this anomaly.

> > > > > > >

> > > > > > > Ray, I will sent you complete logs and images on request.

> > > > > > >

> > > > > > > ASCOM and APCC updated to their latest version.

> > > > > > >

> > > > > > > HAPPY EASTER!!!

> > > > > > >

> > > > > > > Regards,

> > > > > > > Yves

> > > > > > >

> > > > > > >

> > > > > > >

> > > > > > > ACP v7 (DC3-Dreams) time in UT

> > > > > > > 01:10:17 Comet elements for 0041P --> RA=16:47:15 Dec=57. 47' 21"

> > > > (J2000)

> > > > > > > 01:10:17 [flip check: Tn=-300s HAc=-25260s GW=F HAz=-25262s

> > DWz=F

> > > > > > > WF=no]

> > > > > > > 01:10:17 (doing orbital tracking. RA 0.1000 "/sec, Dec -0.0445 "/sec)

> > > > > > >

> > > > > > > AP ASCOM driver that produce vertical nucleus trail

> > > > > > > 028681 2017-04-13 21:10:17.420: ASCOM: Info : SET

> > > > > > > RightAscensionRate = 6.65091663831767E-03

> > > > > > > 028682 2017-04-13 21:10:17.440: Driver: Info : CommandBool

> TX=':RR-

> > > > > > > 0.00665#'

> > > > > > > 028683 2017-04-13 21:10:17.445: Driver: Info : CommandBool Reply

> > > > > > > Received (TX=':RR-0.00665#'), RX='1'

> > > > > > > 028684 2017-04-13 21:10:17.448: ASCOM: Info : SET DeclinationRate

> =

> > > > > > > -0.044520572702055

> > > > > > > 028685 2017-04-13 21:10:17.466: Driver: Info : CommandBool

> TX=':RD-

> > > > > > > 0.00296#'

> > > > > > > 028686 2017-04-13 21:10:17.474: Driver: Info : CommandBool Reply

> > > > > > > Received (TX=':RD-0.00296#'), RX='1'

> > > > > > >

> > > > > > > APCC

> > > > > > > 0168115 2017-04-13 21:10:17.396: Info, VPort1(COM15), RX: :RR-

> > > 0.00665#

> > > > > > > 0168116 2017-04-13 21:10:17.396: Info, ProcessVPortCommand, RX

> > from

> > > > > > > VPort 0: :RR-0.00665#

> > > > > > > 0168117 2017-04-13 21:10:17.396: Info, VPort1(COM15), (RX: :RR-

> > > > > > > 0.00665#), TX: 1

> > > > > > > 0168118 2017-04-13 21:10:17.397: Info, Virtual Port 0, External Rate

> > > Change:

> > > > > > > -0.00665

> > > > > > > 0168119 2017-04-13 21:10:17.398: Debug, Command Thread, RX =

> > > > > > > '21:10:17.4#'

> > > > > > > 0168120 2017-04-13 21:10:17.398: Debug, Command Thread, TX =

> > '#:GS#'

> > > > > > > 0168121 2017-04-13 21:10:17.419: Info, VPort1(COM15), RX: :RD-

> > > 0.00296#

> > > > > > > 0168122 2017-04-13 21:10:17.425: Debug, Command Thread, RX =

> > > > > > > '09:46:22.7#'

> > > > > > > 0168123 2017-04-13 21:10:17.425: Debug, Command Thread, TX =

> > '#:GR#'

> > > > > > > 0168124 2017-04-13 21:10:17.426: Info, ProcessVPortCommand, RX

> > from

> > > > > > > VPort 0: :RD-0.00296#

> > > > > > > 0168125 2017-04-13 21:10:17.426: Info, VPort1(COM15), (RX: :RD-

> > > > > > > 0.00296#), TX: 1

> > > > > > >

> > > > > > >

> > > > > > >

> > > > > >

> > > > >

> > > >

> > >

> >

> **********************************************************************************************

> > > > > > > *********************************

> > > > > > >

> > > > > > >

> > > > > > > AP ASCOM driver WITH good comet tracking

> > > > > > > 004272 2017-04-14 03:07:36.342: ASCOM: Info : SET

> > > > > > > RightAscensionRate = 6.50663785895112E-03

> > > > > > > 004273 2017-04-14 03:07:36.365: Driver: Info : CommandBool

> TX=':RR-

> > > > > > > 0.00651#'

> > > > > > > 004274 2017-04-14 03:07:36.383: Driver: Info : CommandBool Reply

> > > > > > > Received (TX=':RR-0.00651#'), RX='1'

> > > > > > > 004275 2017-04-14 03:07:36.386: ASCOM: Info : SET DeclinationRate

> =

> > > > > > > -4.48155149186675E-02

> > > > > > > 004276 2017-04-14 03:07:36.410: Driver: Info : CommandBool

> > > > > > > TX=':RD0.00298#'

> > > > > > > 004277 2017-04-14 03:07:36.415: Driver: Info : CommandBool Reply

> > > > > > > Received (TX=':RD0.00298#'), RX='1'

> > > > > > >

> > > > > > >

> > > > > > > END OF LOG

> > > > > > >

> > > > > > >

> > > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > > >

> > > > >

> > > > >

> > > > >

> > > > >

> > > >

> > > >

> > > >

> > > >

> > >

> > >

> > >

> > >

> >

> >

> >

> >

>

>

>

>







----------------------------

#56599 Apr 18, 2017

Hi Ray,

Le 18/04/17 . 10:25, "'Ray Gralak (Groups)' groups3@... [ap-gto]" ap-gto@yahoogroups.com> a .crit : Hi Yves,



> In my case, no keypad plugged.

>

> . According to my ASCOM logs, pierside=west (telescope pointing east) all night

> long

> . ACP orbital tracking values were consistent

> . The ASCOM SET DeclinationRate was always a negative value (good tracking or

> not)

> . ASCOM logs :RD-0.00296# --> bad tracking ; :RD0.00296# --> good tracking



Yves, I checked again and I can't find any way for the declination rate to become negative in the driver unless pier side had changed. So, did you manually change the rate to a positive value to check if that fixes the drift? Or, do you believe the driver did that on its own?



Contact Us
This Site's Privacy Policy
Google's privacy policies

S
e
n
i
o
r
T
u
b
e
.
o
r
g