|
Re: [ap-ug] Great American Eclipse 2017
George,
Great analogy...
Michael
toggle quoted messageShow quoted text
At 08:20 AM 4/17/2017, you wrote:
Fritz,
Good luck trying to be mobile with 50,000,000 on a very limited number of
roads in a very restricted zone. Visualize trying to get to
Woodstock and add a couple zeros!
Regards,
George
George Whitney
Astro-Physics, Inc.
Phone: 815-282-1513
Email: george@...
From: ap-gto@...
[
mailto:ap-gto@...]
Sent: Saturday, April 15, 2017 10:26 AM
To: ap-gto@...
Subject: [ap-gto] Re: [ap-ug] Great American Eclipse 2017
Joel,
It is going to be cloudy east of the Mississippi. Even from a fixed
location out west, the odds only climb to 70 or 80% for clear skies,. I
figure with mobility I can push my odds to 90%, Do NOT pick a single
location and plan on seeing the eclipse from there. You must be
mobile.
fritz k
|
|
|
Re: Is it recommended to tighten ra/dec clutches during mount transportation?
Rolando,
I wonder ... leaving the clutches fully tightened may
not affect “the clutches” themselves, but since they are tightened down onto the
fully meshed worm, I would think that any severe bump on the mount will transmit
some the toque to the worm gear bearings, and worm tooth, before they slip.
However, clutches are well designed to slip with an OTA crashing into the pier,
so there is always some assurance that the problem won’t happen.
I would favour a “slightly” loosened clutch, to
let the axle “slip” (more easily than in an emergency), if it needs to during a
vehicle or airline cargo bounce.’container Leaving it completely loose would
cause awkward handling when the user picks it up before retightening clutches
during setup, and equally so during take-down. Besides, you normally need to
loosen clutches for a comfortable resting position, after packing the mount into
its transport container anyway. Retightening them again for the trip serves no
purpose. Might even explain why some may have been damaged during carrier
delivery.
Not a big deal, but somewhat looser clutches can do no
harm.
Joe
toggle quoted messageShow quoted text
From: chris1011@... [ap-gto]
Sent: Monday, April 17, 2017 12:07 PM
To: ap-gto@...
Subject: Re: [ap-gto] Is it recommended to tighten ra/dec clutches
during mount transportation?
The clutches don't really do
anything, so you can leave them tight or loose, as you
wish.
Rolando
|
|
|
Re : RE: RE: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
|
|
|
Re: Is it recommended to tighten ra/dec clutches during mount transportation?
The clutches don't really do anything, so you can leave them tight or loose, as you wish.
Rolando
toggle quoted messageShow quoted text
-----Original Message-----
From: leonid.shatz@... [ap-gto]
To: ap-gto
Sent: Mon, Apr 17, 2017 11:04 am
Subject: [ap-gto] Is it recommended to tighten ra/dec clutches during mount transportation?
Hello group,
As I'm getting ready for first light test of the new Mach1, I wonder if there are any safety recommendations for transporting the case to remote site, i.e. is recommended to tighten the clutches on RA/DEC or leave them loose or doesn't matter to avoid mechanical damage. If I recall correctly, I've received the original box from AP with all clutches tightened, but I'm not sure if that's done on purpose.
Thanks,
Leo S.
|
|
|
Re: [ap-ug] Great American Eclipse 2017
Fritz,
Good luck trying to be mobile with 50,000,000 on a very limited number of roads in a very restricted zone. Visualize trying to get to Woodstock and add a couple zeros!
Regards,
George
George Whitney
Astro-Physics, Inc.
Phone: 815-282-1513
Email: george@...
toggle quoted messageShow quoted text
From: ap-gto@... [mailto:ap-gto@...]
Sent: Saturday, April 15, 2017 10:26 AM
To: ap-gto@...
Subject: [ap-gto] Re: [ap-ug] Great American Eclipse 2017
Joel,
It is going to be cloudy east of the Mississippi. Even from a fixed
location out west, the odds only climb to 70 or 80% for clear skies,. I
figure with mobility I can push my odds to 90%, Do NOT pick a single
location and plan on seeing the eclipse from there. You must be mobile.
fritz k
|
|
|
Re: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
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): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apccAuthor of PEMPro: http://www.ccdware.comAuthor of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriverAuthor of PulseGuide: http://www.pulseguide.comAuthor of Sigma: http://www.gralak.com/sigma-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 10:52 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 6:20 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 1:34 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 1:06 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 12:29 PM
To: ap-gto@...
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@...> 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 11:09 AM
To: ap-gto@...
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
|
|
|
Is it recommended to tighten ra/dec clutches during mount transportation?
Hello group,
As I'm getting ready for first light test of the new Mach1, I wonder if there are any safety recommendations for transporting the case to remote site, i.e. is recommended to tighten the clutches on RA/DEC or leave them loose or doesn't matter to avoid mechanical damage. If I recall correctly, I've received the original box from AP with all clutches tightened, but I'm not sure if that's done on purpose.
Thanks,
Leo S.
|
|
|
Yes it is, but we AP owners get a free copy that you have to use the right installer for so you can provide your AP key.
toggle quoted messageShow quoted text
From: ap-gto@... on behalf of bryancashion@... [ap-gto]
Sent: Sunday, April 16, 2017 11:09 PM
To: ap-gto@...
Subject: [ap-gto] Re: AP PEM Pro Installer
Bill
PEMPro is a CCDWARE product.
http://ccdware.com/downloads/
|
|
ccdware.com
CCDWARE products are available here for download in fully working trial versions. You can freely download and install these versions on your ...
|
Bryan
|
|
|
Bill
PEMPro is a CCDWARE product.
Bryan
|
|
|
Re: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
|
|
|
Re: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
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): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apccAuthor of PEMPro: http://www.ccdware.comAuthor of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriverAuthor of PulseGuide: http://www.pulseguide.comAuthor of Sigma: http://www.gralak.com/sigma
-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 6:20 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 1:34 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 1:06 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 12:29 PM
To: ap-gto@...
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@...> 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 11:09 AM
To: ap-gto@...
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
|
|
|
Hey where can I find the AP installer. I have my key, but cannot seem to find my CD....
|
|
|
Re : RE: RE: RE: RE: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
|
|
|
Re: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
toggle quoted messageShow quoted text
-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 1:34 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 1:06 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 12:29 PM
To: ap-gto@...
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@...> 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 11:09 AM
To: ap-gto@...
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
|
|
|
Geoff: I like your M42 image. I would appreciate if you can clarify the following. Your exposures where?:
R = 22@20s or 22@150s G = 22@150s or 22@20s B = 12@250s L = 20@600s
Thanks, Héctor R. Santini V.P. SED/R&D Infomedika, Inc. 181 FD Roosevelt Ave. San Juan, PR 00918 W:(787)620-2474 F:(787)620-8608 C:(787)509-3256
On Apr 15, 2017, at 4:48 AM, ghsmith45@... [ap-gto] < ap-gto@...> wrote: Had fun (?) processing this one. Judging by comments from other posts I've made you'll either love it or hate it. Most of the data comes from January
this year, but the seeing with my FLI Proline 16803 wasn't quite as good as I would have liked.
Fortunately I had some good data from December 2013 taken with my QSI
540wsg camera over a much smaller field of view than I have with my current
setup. The seeing was good enough to almost get 6 stars in the
trapezium. They appear as bumps on the brighter stars, so I used that
data for the central region.
http://www.astrobin.com/291646/B/
Higher res here http://www.astrobin.com/full/291646/B/
Details:
Mount: AP900GTO Telescope: 12.5" PlaneWave CDK Cameras: FLI 16803, QSI 540 wsg
Exposures:22@20s (QSI),
22@150s, 12@250s, 20@600s (FLI)
total 5.2h
Dates: Jan 2017, Dec 2013
FOV: 49' x 49'
Processing: PixInsight.
Geoff
|
|
|
Ahhh... I missed that before. Thanks, Ray.
--- Kerry
|
|
|
Re : RE: RE: RE: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
|
|
|
Re: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
toggle quoted messageShow quoted text
-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 1:06 PM
To: ap-gto@...
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@...> 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): 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 12:29 PM
To: ap-gto@...
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@...> 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@... [mailto:ap-gto@...]
Sent: Sunday, April 16, 2017 11:09 AM
To: ap-gto@...
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
|
|
|
Re : RE: RE: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
|
|
|
Re : RE: RE: 41P/Tuttle-Giacobini-Kresak orbital tracking behaviour
|
|
|
