Re: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour


Ray Gralak
 

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): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://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@gralak.com [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): http://www.astro-
physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://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




Join main@ap-gto.groups.io to automatically receive all group messages.