Date   

Re: Some odd RA issues/configure ASCOM?

Mike Shade
 

Hi Mike,

But, on this topic, if I were to want to bypass the guider relays...to
rule
that out...

Setup Maxim 5.18 to guide via ASCOM direct. As I am using The Sky 6... in
the mix here, along with ACP, and an older version of Focusmax do I need
to
configure anything with the "observatory control window" in Maxim or just
use the AP ASCOM driver? Maxim's help mentions this, but it doesn't look
like I need to do so for ASCOM direct. I have nothing configured in the
now, rather not add another layer of complexity if not needed.
It's been a long time since I used Maxim 5.x, but I don't think you want to
use "ASCOM Direct". You
want "Telescope", and you need to setup the Telescope to use the
Astro-Physics ASCOM driver in the
observatory window, *and* you need to connect to the driver in the
Observatory window. If you don't
connect, then I don't think Maxim will be able to use the driver.



Thanks Ray. I think when I tried this before it was ASCOM direct and I
think that bypasses The Sky 6. If I recall, it worked (calibrated) but
there was some issue in regards to proper guiding corrections or something.

I would prefer, if possible to not have another layer of software in the
system...already have Focusmax/Maxim/Sky 6/ACP. Up until I restarted after
monsoon shutdown, it was a good system, generated good data.

Perhaps others, with direct experience can chime in. I hate to have to
reinvent the wheel.



Would calibration be about the same as for guiding through the relays,
looking for a movement of 40 pixels or so?
I can't tell you how many pixels movement should occur as that depends on
image scale, guider rate,
and duration of exposure. However, if you do, say, 20 seconds per axis, that
should be good enough.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 1:48 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues/configure ASCOM?



No, it is not an ASCOM driver issue. Not 100% sure that it is an
autoguiding issue either but in my mind at least it very well could be.

But, on this topic, if I were to want to bypass the guider relays...to
rule
that out...

Setup Maxim 5.18 to guide via ASCOM direct. As I am using The Sky 6... in
the mix here, along with ACP, and an older version of Focusmax do I need
to
configure anything with the "observatory control window" in Maxim or just
use the AP ASCOM driver? Maxim's help mentions this, but it doesn't look
like I need to do so for ASCOM direct. I have nothing configured in the
now, rather not add another layer of complexity if not needed.

Would calibration be about the same as for guiding through the relays,
looking for a movement of 40 pixels or so?

In the AP ASCOM driver, would I guide at 1X, .5X, or .25X? I currently
guide at 1X with the relays.

What about aggressiveness during guiding? With the relays run 6 to 6.5,
similar or...? Run this higher? I seem to have a recollection that the
issue was that the scope was getting sent corrections or something when I
tried this before but might not have had it setup right.

Anything else I am missing here?

Thanks...

Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com

In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights

International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 12:59 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?

Yes (or through whatever the native STL6303E uses for guiding).
Ok, in that case the ASCOM driver is not involved in this autoguiding
issue.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 12:31 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?



Yes (or through whatever the native STL6303E uses for guiding). I did
try
guiding through ASCOM direct or whatever it was, didn't seem to work
very
well if I recall. There seemed to be an issue with corrections being
sent
to the mount. It may have been as simple of not knowing the right
settings
for that configuration. Not running USB to the mount, USB of course to
the
camera.

A finicky guider relay might account for this though. The system
calibrates
just fine with a 40+ pixel movement in both RA and DEC. I have replaced
the
guider dongle on the camera and will try another guider cable. Over the
years have seen guider cables do weird and unexpected things.

Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com

In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be
half

a year since I watched her April rising in the east? Low in the
southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights

International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 11:08 AM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?

Hi Mike,

I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on the camera.
Are you autoguiding through relays?

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 9:58 AM
To: ap-gto@...
Subject: [ap-gto] Some odd RA issues?



Here is the scenario: AP1600GTO permanent in observatory with CP4
controller, Planewave CDK17,
Optec
Gemini focuser-rotator/SBIG STL6303E camera, unbinned resolution
.64"/pixel. Running Maxim 5.18
and
ACP. So far so good. Now here is where it gets curious. As I am in SE
AZ,
had to shut down for
monsoon
from early July to middle of September. All electronics were
unplugged,
I
do not suspect
lightning damage.
Prior to shutdown in July this system returned round stars across the
frame in 10-minute subs,
guided.



After starting up again in September, noticed that the stars were ever
so
slightly off in RA,
maybe a pixel or
two, just enough to be not quite round, again in RA only. However,
images
in RA last night showed
several
frames where there were actually double stars. Looking at the guider
log
showed some pretty good
jumps in
RA. The guider calibrates just fine with a 40+/ pixel move, and I have
been able to do a 5-minute
unguided
with round stars after startup in September. Of course checked primary
mirror spacing,
collimation, if
everything is snug, cable drag and so on. I have remeshed the gears
and
redone PEC, issues
persists.
This is a random issue. The Maxim guider log shows some hefty jumps in
RA
but NOT in DEC.



It is curious that prior to shutdown it worked like a
champ...now...some
issues with a number of
images that
are just out of round enough as to be useless, in RA. It is always in
RA.
I have looked for
rodent damage,
none.



I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on
the camera.
Anyone else seen this or have thoughts? I know this is about as broad
as
"gee doc, I have a
headache"...could be anything.



AP driver number is 5.09.07.









Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on
their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be
half

a year since I watched her April rising in the east? Low in the
southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: www.darksky.org
<http://www.darksky.org/>












Re: Some odd RA issues/configure ASCOM?

Ray Gralak
 

Hi Mike,

But, on this topic, if I were to want to bypass the guider relays...to rule
that out...

Setup Maxim 5.18 to guide via ASCOM direct. As I am using The Sky 6... in
the mix here, along with ACP, and an older version of Focusmax do I need to
configure anything with the "observatory control window" in Maxim or just
use the AP ASCOM driver? Maxim's help mentions this, but it doesn't look
like I need to do so for ASCOM direct. I have nothing configured in the
now, rather not add another layer of complexity if not needed.
It's been a long time since I used Maxim 5.x, but I don't think you want to use "ASCOM Direct". You
want "Telescope", and you need to setup the Telescope to use the Astro-Physics ASCOM driver in the
observatory window, *and* you need to connect to the driver in the Observatory window. If you don't
connect, then I don't think Maxim will be able to use the driver.

Would calibration be about the same as for guiding through the relays,
looking for a movement of 40 pixels or so?
I can't tell you how many pixels movement should occur as that depends on image scale, guider rate,
and duration of exposure. However, if you do, say, 20 seconds per axis, that should be good enough.

-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, October 1, 2017 1:48 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues/configure ASCOM?



No, it is not an ASCOM driver issue. Not 100% sure that it is an
autoguiding issue either but in my mind at least it very well could be.

But, on this topic, if I were to want to bypass the guider relays...to rule
that out...

Setup Maxim 5.18 to guide via ASCOM direct. As I am using The Sky 6... in
the mix here, along with ACP, and an older version of Focusmax do I need to
configure anything with the "observatory control window" in Maxim or just
use the AP ASCOM driver? Maxim's help mentions this, but it doesn't look
like I need to do so for ASCOM direct. I have nothing configured in the
now, rather not add another layer of complexity if not needed.

Would calibration be about the same as for guiding through the relays,
looking for a movement of 40 pixels or so?

In the AP ASCOM driver, would I guide at 1X, .5X, or .25X? I currently
guide at 1X with the relays.

What about aggressiveness during guiding? With the relays run 6 to 6.5,
similar or...? Run this higher? I seem to have a recollection that the
issue was that the scope was getting sent corrections or something when I
tried this before but might not have had it setup right.

Anything else I am missing here?

Thanks...

Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com

In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights

International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 12:59 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?

Yes (or through whatever the native STL6303E uses for guiding).
Ok, in that case the ASCOM driver is not involved in this autoguiding issue.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 12:31 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?



Yes (or through whatever the native STL6303E uses for guiding). I did try
guiding through ASCOM direct or whatever it was, didn't seem to work very
well if I recall. There seemed to be an issue with corrections being sent
to the mount. It may have been as simple of not knowing the right settings
for that configuration. Not running USB to the mount, USB of course to the
camera.

A finicky guider relay might account for this though. The system
calibrates
just fine with a 40+ pixel movement in both RA and DEC. I have replaced
the
guider dongle on the camera and will try another guider cable. Over the
years have seen guider cables do weird and unexpected things.

Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com

In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights

International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 11:08 AM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?

Hi Mike,

I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on the camera.
Are you autoguiding through relays?

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 9:58 AM
To: ap-gto@...
Subject: [ap-gto] Some odd RA issues?



Here is the scenario: AP1600GTO permanent in observatory with CP4
controller, Planewave CDK17,
Optec
Gemini focuser-rotator/SBIG STL6303E camera, unbinned resolution
.64"/pixel. Running Maxim 5.18
and
ACP. So far so good. Now here is where it gets curious. As I am in SE
AZ,
had to shut down for
monsoon
from early July to middle of September. All electronics were unplugged,
I
do not suspect
lightning damage.
Prior to shutdown in July this system returned round stars across the
frame in 10-minute subs,
guided.



After starting up again in September, noticed that the stars were ever
so
slightly off in RA,
maybe a pixel or
two, just enough to be not quite round, again in RA only. However,
images
in RA last night showed
several
frames where there were actually double stars. Looking at the guider log
showed some pretty good
jumps in
RA. The guider calibrates just fine with a 40+/ pixel move, and I have
been able to do a 5-minute
unguided
with round stars after startup in September. Of course checked primary
mirror spacing,
collimation, if
everything is snug, cable drag and so on. I have remeshed the gears and
redone PEC, issues
persists.
This is a random issue. The Maxim guider log shows some hefty jumps in
RA
but NOT in DEC.



It is curious that prior to shutdown it worked like a champ...now...some
issues with a number of
images that
are just out of round enough as to be useless, in RA. It is always in
RA.
I have looked for
rodent damage,
none.



I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on
the camera.
Anyone else seen this or have thoughts? I know this is about as broad as
"gee doc, I have a
headache"...could be anything.



AP driver number is 5.09.07.









Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be
half

a year since I watched her April rising in the east? Low in the
southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: www.darksky.org
<http://www.darksky.org/>












Re: Some odd RA issues/configure ASCOM?

Mike Shade
 

I calibrate at about 0 degrees dec east of the meridian. I am of course guiding through the guider relays currently.



If anyone can assist in setting up ASCOM direct, I'll try that again, perhaps earlier attempts were not configured properly...



Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: <http://www.darksky.org/> www.darksky.org



From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 2:48 PM
To: ap-gto@...
Subject: Re: [ap-gto] Some odd RA issues/configure ASCOM?





Mike,



How high up on DEC are you initially Calibrating your guider?



I assume, as a matter of course, that you would calibrate the guider right at the Celestial Equator & Prime Meridian. The guider software “should scale” its guide movements

at the actual DEC target guiding start position - (which is provided to it by TSX). Some software (e.g. CCDSOFT), may need the target star’s DEC value to be entered by the user.



Obviously, if you start off by calibrating at a high DEC angle, the guiding will either be much less precise or fail entirely.



In such case, this could account for your occasional “larger guiding jumps”, if seeing conditions cause momentary loss of target.



Joe





[Non-text portions of this message have been removed]


Re: Some odd RA issues/configure ASCOM?

Joe Zeglinski
 

Mike,
 
    How high up on DEC are you initially Calibrating your guider?
 
    I assume, as a matter of course, that you would calibrate the guider right at the Celestial Equator & Prime Meridian.  The guider software “should scale” its guide movements
  at the actual DEC target guiding start position - (which is provided to it by TSX). Some software (e.g. CCDSOFT), may need the target star’s DEC value to be entered by the user.
 
    Obviously, if you start off by calibrating at a  high DEC angle, the guiding will either be much less precise or fail entirely.
 
In such case, this could account for your occasional “larger guiding jumps”,  if seeing conditions cause momentary loss of target.
 
Joe


Re: Some odd RA issues/configure ASCOM?

Mike Shade
 

No, it is not an ASCOM driver issue. Not 100% sure that it is an
autoguiding issue either but in my mind at least it very well could be.



But, on this topic, if I were to want to bypass the guider relays...to rule
that out...



Setup Maxim 5.18 to guide via ASCOM direct. As I am using The Sky 6... in
the mix here, along with ACP, and an older version of Focusmax do I need to
configure anything with the "observatory control window" in Maxim or just
use the AP ASCOM driver? Maxim's help mentions this, but it doesn't look
like I need to do so for ASCOM direct. I have nothing configured in the
now, rather not add another layer of complexity if not needed.



Would calibration be about the same as for guiding through the relays,
looking for a movement of 40 pixels or so?



In the AP ASCOM driver, would I guide at 1X, .5X, or .25X? I currently
guide at 1X with the relays.



What about aggressiveness during guiding? With the relays run 6 to 6.5,
similar or...? Run this higher? I seem to have a recollection that the
issue was that the scope was getting sent corrections or something when I
tried this before but might not have had it setup right.



Anything else I am missing here?



Thanks...



Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org



From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 12:59 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?





Yes (or through whatever the native STL6303E uses for guiding).
Ok, in that case the ASCOM driver is not involved in this autoguiding issue.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 12:31 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?



Yes (or through whatever the native STL6303E uses for guiding). I did try
guiding through ASCOM direct or whatever it was, didn't seem to work very
well if I recall. There seemed to be an issue with corrections being sent
to the mount. It may have been as simple of not knowing the right settings
for that configuration. Not running USB to the mount, USB of course to the
camera.

A finicky guider relay might account for this though. The system
calibrates
just fine with a 40+ pixel movement in both RA and DEC. I have replaced
the
guider dongle on the camera and will try another guider cable. Over the
years have seen guider cables do weird and unexpected things.

Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com

In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights

International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 11:08 AM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?

Hi Mike,

I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on the camera.
Are you autoguiding through relays?

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 9:58 AM
To: ap-gto@...
Subject: [ap-gto] Some odd RA issues?



Here is the scenario: AP1600GTO permanent in observatory with CP4
controller, Planewave CDK17,
Optec
Gemini focuser-rotator/SBIG STL6303E camera, unbinned resolution
.64"/pixel. Running Maxim 5.18
and
ACP. So far so good. Now here is where it gets curious. As I am in SE
AZ,
had to shut down for
monsoon
from early July to middle of September. All electronics were unplugged,
I
do not suspect
lightning damage.
Prior to shutdown in July this system returned round stars across the
frame in 10-minute subs,
guided.



After starting up again in September, noticed that the stars were ever
so
slightly off in RA,
maybe a pixel or
two, just enough to be not quite round, again in RA only. However,
images
in RA last night showed
several
frames where there were actually double stars. Looking at the guider log
showed some pretty good
jumps in
RA. The guider calibrates just fine with a 40+/ pixel move, and I have
been able to do a 5-minute
unguided
with round stars after startup in September. Of course checked primary
mirror spacing,
collimation, if
everything is snug, cable drag and so on. I have remeshed the gears and
redone PEC, issues
persists.
This is a random issue. The Maxim guider log shows some hefty jumps in
RA
but NOT in DEC.



It is curious that prior to shutdown it worked like a champ...now...some
issues with a number of
images that
are just out of round enough as to be useless, in RA. It is always in
RA.
I have looked for
rodent damage,
none.



I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on
the camera.
Anyone else seen this or have thoughts? I know this is about as broad as
"gee doc, I have a
headache"...could be anything.



AP driver number is 5.09.07.









Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be
half

a year since I watched her April rising in the east? Low in the
southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: www.darksky.org
<http://www.darksky.org/>








Re: Some odd RA issues?

Ray Gralak
 

Yes (or through whatever the native STL6303E uses for guiding).
Ok, in that case the ASCOM driver is not involved in this autoguiding issue.

-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, October 1, 2017 12:31 PM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?



Yes (or through whatever the native STL6303E uses for guiding). I did try
guiding through ASCOM direct or whatever it was, didn't seem to work very
well if I recall. There seemed to be an issue with corrections being sent
to the mount. It may have been as simple of not knowing the right settings
for that configuration. Not running USB to the mount, USB of course to the
camera.

A finicky guider relay might account for this though. The system calibrates
just fine with a 40+ pixel movement in both RA and DEC. I have replaced the
guider dongle on the camera and will try another guider cable. Over the
years have seen guider cables do weird and unexpected things.

Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com

In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights

International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 11:08 AM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?

Hi Mike,

I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on the camera.
Are you autoguiding through relays?

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 9:58 AM
To: ap-gto@...
Subject: [ap-gto] Some odd RA issues?



Here is the scenario: AP1600GTO permanent in observatory with CP4
controller, Planewave CDK17,
Optec
Gemini focuser-rotator/SBIG STL6303E camera, unbinned resolution
.64"/pixel. Running Maxim 5.18
and
ACP. So far so good. Now here is where it gets curious. As I am in SE AZ,
had to shut down for
monsoon
from early July to middle of September. All electronics were unplugged, I
do not suspect
lightning damage.
Prior to shutdown in July this system returned round stars across the
frame in 10-minute subs,
guided.



After starting up again in September, noticed that the stars were ever so
slightly off in RA,
maybe a pixel or
two, just enough to be not quite round, again in RA only. However, images
in RA last night showed
several
frames where there were actually double stars. Looking at the guider log
showed some pretty good
jumps in
RA. The guider calibrates just fine with a 40+/ pixel move, and I have
been able to do a 5-minute
unguided
with round stars after startup in September. Of course checked primary
mirror spacing,
collimation, if
everything is snug, cable drag and so on. I have remeshed the gears and
redone PEC, issues
persists.
This is a random issue. The Maxim guider log shows some hefty jumps in RA
but NOT in DEC.



It is curious that prior to shutdown it worked like a champ...now...some
issues with a number of
images that
are just out of round enough as to be useless, in RA. It is always in RA.
I have looked for
rodent damage,
none.



I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on
the camera.
Anyone else seen this or have thoughts? I know this is about as broad as
"gee doc, I have a
headache"...could be anything.



AP driver number is 5.09.07.









Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: www.darksky.org
<http://www.darksky.org/>








Re: [ap-ug] FW: Save-the-Date: The 2018 Robotic Telescopes, Student Research & Education Conference AND the interNational Astro Teaching Summit July 23-27, 2018

 

Hi Chris,

We met Rachel at AIC. She impressed us as being very energetic and committed to getting young people excited about astronomy and science in general. We plan to support her efforts and other vendors in attendance do too. 

Marj Christen
Astro-Physics

On Sep 28, 2017, at 1:56 PM, 'Christopher Erickson' christopher.k.erickson@... [ap-ug] <ap-ug@...> wrote:

 

 
 
 
-Christopher Erickson
Observatory engineer
Summit Kinetics
Waikoloa, HI 96738
www.summitkinetics.com
 


From: Robotic Telescopes, Student Research and Education [mailto:info=rtsre.org@...] On Behalf Of Robotic Telescopes, Student Research and Education
Sent: Thursday, September 28, 2017 9:28 AM
To: christopher.k.erickson@...
Subject: Save-the-Date: The 2018 Robotic Telescopes, Student Research & Education Conference AND the interNational Astro Teaching Summit July 23-27, 2018

View this email in your browser

Save the Date: July 23-27, 2018 Hilo, Hawaii

 

It is with great pleasure that we announce the dates for the 2nd annual Conference on Robotic Telescopes, Student Research and Education (RTSRE, rtsre.net) to be held in Hilo on the lush eastern coast of the Big Island of Hawai’i July 23rd - 25th, 2018! The conference will be co-located with the interNational Astronomy Teaching Summit (iNATS) from July 25th - 27th, 2018. The overlap is being coordinated by both planning committees, providing an entire five-days of highly valuable sessions and workshops. The RTSRE conference series focuses on building a sustainable community around the educational, technical and student research uses of robotic telescopes, from small through to large aperture and from radio through to gamma-ray. It aims to be a meeting place for astronomers, educators, researchers, and observatory and telescope network developers and managers, in a continuing effort to share and combine resources, develop and enhance education and research programs, and foster global conversations and collaborations. The co-located CAPER Team’s iNATS astronomy education summit at the end of the week provides worldwide networking opportunities and hands-on workshops designed to expand educators’ teaching strategy toolkit designed for innovative astronomy professors, school teachers, and outreach professionals.  Both individual and joint meeting registration opportunities are available.

The diverse program meeting includes a family program, guided-tours of observatories, visiting the astronomy and cultural education center & planetarium and the national volcano park, and a workshop for novice robotic telescope users and educators to learn how to do hands-on astronomy research projects with their students.

Student researchers are highly encouraged to attend and present their scientific work at the conference in a special poster session. A combined RTSRE+iNATS peer reviewed conference proceedings will also be open for contribution.

The conference has arranged special ocean-side room rates for attendees at the Hilo Hawaiian Hotel at 71 Banyan Drive, Hilo, HI 96720, telephone: +1 (808) 935-9361.

We look forward to seeing you there!

Rachel Freed, on behalf of the RTSRE 2018 SOC
 







This email was sent to christopher.k.erickson@...
why did I get this?    unsubscribe from this list    update subscription preferences
Robotic Telescopes, Student Research and Education · 58 Ryans Road · Eltham, VIC 3095 · Australia

Email Marketing Powered by MailChimp

Virus-free. www.avg.com


Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3

Ray Gralak
 

I tried PHD2 along with theskyX just because I couldn’t guide with theskyX ;-) But only one instance of the
driver is started and it shows 2 clients.
Please explain exactly how you have TheSkyX and PHD2 connected, and the versions of each. And exactly how are you determining that PHD2 is not working?

-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, October 1, 2017 11:20 AM
To: ap-gto@...
Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3



I tried PHD2 along with theskyX just because I couldn’t guide with theskyX ;-) But only one instance of the
driver is started and it shows 2 clients.

I reported this to SBisque.



Le 1 oct. 2017 à 22:14, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-
gto@...> a écrit :


I think you probably should report the issue to Software Bisque as it sounds like a bug in TheSkyX.

I don't understand why you would be using PHD2 with TheSkyX? That said, I would make sure that
two instances of the driver are not being started.

-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 <http://www.ccdware.com/>
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
Author of Sigma: http://www.gralak.com/sigma

> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Sunday, October 1, 2017 8:04 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
CP3
>
>
>
> I’m getting close to an answer...
>
> I did a new test: using PHD2 alone connected to the ASCOM V2 driver and pulseguiding works!!
>
> TheSkyX alone with ASCOM V2: pulseguiding fails
>
> TheSkyX + PHD2 both connected to ASCOM V2 : pulseguide fails for both. But it is not like PHD2
can’t
> connect to the ASCOM driver: it can connect and it is possible to calibrate the guiding but the
pulseguide
> commands fail.
>
> What next?
>
>
>
>
> Le 1 oct. 2017 à 18:31, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-
> gto@...> a écrit :
>
>
> Hi David,
>
> > I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not
> works
> > from TheskyX and PHD2. I’m going to try the 5.10.01b
>
> Ok, that proves that the driver's PulseGuide function is working, so I don't think the problem is in the
> driver.
>
> It could be that TheSkyX is trying to use the driver in a cross-threaded manner. Applications written
in
> .Net automatically get their ASCOM calls marshalled into a single thread, but non-net applications,
like
> TheSkyX and PHD2, must be careful to perform all calls to an ASCOM driver on the same thread
that the
> driver was created. If not, a cross-threaded operation might occur which will cause unexpected
behavior.
>
> -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 <http://www.ccdware.com/>
<http://www.ccdware.com/>
> Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
> Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
<http://www.pulseguide.com/>
> Author of Sigma: http://www.gralak.com/sigma
>
> > -----Original Message-----
> > From: ap-gto@... [mailto:ap-gto@...]
> > Sent: Sunday, October 1, 2017 7:26 AM
> > To: ap-gto@...
> > Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
> CP3
> >
> >
> >
> > I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not
> works
> > from TheskyX and PHD2. I’m going to try the 5.10.01b
> >
> >
> >
> > Le 1 oct. 2017 à 17:51, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-
> > gto@...> a écrit :
> >
> >
> > Hi David,
> >
> > > Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is
still
> > > impossible (even from PHD2 which is supposed to be independent of TheSkyX)
> >
> > The driver's pulseguide code hasn't changed in a long time so I've created a test script to
hopefully
> > isolate the problem, or prove that the driver's PulseGuide function is working correctly. It connects
to
> the
> > mount and issues ten 500 msec (1/2 second) PulseGuide moves to RA and Dec.
> >
> > At the end of the ten moves it reads the RA and Dec again and calculates the difference between
> the
> > start and end. This should be non-zero if both RA and Dec moved.
> >
> > To run the test:
> >
> > 1. Download the file and save it. If needed you will need to remove the ".txt" file extension. This
will
> > make it a vbscript file. It is in plain text so you can read it.
> >
> > 2. Make sure no other application is already connected to the mount through the driver.
> >
> > 3. Double-click the file ("it should be named AP-PulseGuideTest.vbs").
> >
> > The driver should show and after about 10 seconds the message with the movements displayed.
If
> the
> > movements are "0" then use the AP Driver's log zipper program to capture the log and email it to
me
> at
> > GROUPS3 AT GRALAK DOT COM.
> >
> > http://www.gralak.com/apdriver/AP-PulseGuideTest.vbs.txt
> >
> > Again, save and rename the file to "AP-PulseGuideTest.vbs" (no ".txt" file extension) and double-
> click
> > it from file manager.
> >
> > -Ray Gralak
> > Author of APCC (Astro-Physics Command Center): http://www.astro- <http://www.astro-/>
> > physics.com/index.htm?products/accessories/software/apcc/apcc
> > Author of PEMPro: http://www.ccdware.com <http://www.ccdware.com/>
<http://www.ccdware.com/>
> <http://www.ccdware.com/>
> > Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
> > Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
<http://www.pulseguide.com/>
> <http://www.pulseguide.com/>
> > Author of Sigma: http://www.gralak.com/sigma
> >
> > > -----Original Message-----
> > > From: ap-gto@... [mailto:ap-gto@...]
> > > Sent: Saturday, September 30, 2017 11:46 PM
> > > To: ap-gto@...
> > > Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
> > CP3
> > >
> > >
> > >
> > > Hello all,
> > >
> > > George and Howard from AP could access to my remote setup with teamviewer but they
couldn't
> > find a
> > > solution.
> > >
> > > It looks like there is a problem with the ASCOM V2 driver. I have installed the last one (5.10)
when
> I
> > started
> > > with my first AP mount recently. The pulseguing has never worked from TheSkyX or from
PHD2. I
> > know
> > > people who are struggling with this new driver and they had to get back to an older one
> > (successfully).
> > >
> > > Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is
still
> > > impossible (even from PHD2 which is supposed to be independent of TheSkyX)
> > >
> > > So far, only the native Astro-Physics driver in TheSkyX is 100% functional: I can guide with
> > TheSkyX or
> > > PHD2. But this driver is limited and I really want to use the ASCOM V2.
> > >
> > > This is my current setup:
> > >
> > > Mount: AP900GTO CP3
> > > Computer: shuttle DH110SE
> > > Operating system: windows 10
> > > Software: theskyX pro ( camera add-on), PHD2, CCDautopilot.
> > >
> > > David
> > >
> > >
> > >
> > > Le mar. 26 sept. 2017 à 18:57, George george@... [ap-gto] <ap-
> > gto@...> a
> > > écrit :
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > David,
> > >
> > >
> > >
> > > Call me regarding your connection. I’ll need more info and it’s faster via phone. Be at your astro
> > > computer so that we can review settings.
> > >
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > > George
> > >
> > >
> > >
> > > George Whitney
> > >
> > > Astro-Physics, Inc.
> > >
> > > Phone: 815-282-1513
> > >
> > > Email: george@...
> > >
> > >
> > >
> > > From: ap-gto@... [mailto:ap-gto@...]
> > > Sent: Tuesday, September 26, 2017 12:23 AM
> > > To: ap-gto@...
> > > Subject: [ap-gto] ASCOM guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hello everyone,
> > >
> > >
> > >
> > > Couple of months ago I purchased a used AP900GTO with the CP2 control box. I have been
> using
> > it
> > > with theskyX pro in a remote observatory. I quickly realized that ASCOM guiding (pulseguiding)
> was
> > not
> > > possible with the CP2. So I recently moved to the CP3 control box but I'm still struggling: when
I'm
> > trying the
> > > buttons "+X,-X,+Y,-Y" on the autoguider panel in theskyX , I get an error message "command
not
> > supported,
> > > error=11000". It was the same message when it was still the CP2.
> > >
> > >
> > >
> > > I use the ASCOM V2 driver and I changed the version of the control box in the setup. The
mount
> is
> > > correctly recognized when I press "check COM port", the chip version is V1. Everything is
working
> > well,
> > > except guiding. In theskyX I have selected "pulseguide" instead of "relays" in the autoguider
setup.
> > >
> > >
> > >
> > > Did I miss something? Should I reinstall the ASCOM driver? Something wrong with the mount?
It
> is
> > > like I'm still in CP2... :-(
> > >
> > >
> > >
> > > I also tried to guide with PHD2. I got this message "Pulseguide fails".
> > >
> > >
> > >
> > > Thank you for your help,
> > >
> > >
> > >
> > > David
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
>
>
>
>
>





Re: Some odd RA issues?

Mike Shade
 

Guiding through the guide chip on the STL6303E.



Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org



From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 11:35 AM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?





Off-axis or piggyback guiding?





-Christopher Erickson
Observatory engineer
Summit Kinetics

Waikoloa, HI 96738
<http://www.summitkinetics.com/> www.summitkinetics.com





_____

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 1, 2017 6:58 AM
To: ap-gto@...
Subject: [ap-gto] Some odd RA issues?

Here is the scenario: AP1600GTO permanent in observatory with CP4
controller, Planewave CDK17, Optec Gemini focuser-rotator/SBIG STL6303E
camera, unbinned resolution .64"/pixel. Running Maxim 5.18 and ACP. So far
so good. Now here is where it gets curious. As I am in SE AZ, had to shut
down for monsoon from early July to middle of September. All electronics
were unplugged, I do not suspect lightning damage. Prior to shutdown in
July this system returned round stars across the frame in 10-minute subs,
guided.



After starting up again in September, noticed that the stars were ever so
slightly off in RA, maybe a pixel or two, just enough to be not quite round,
again in RA only. However, images in RA last night showed several frames
where there were actually double stars. Looking at the guider log showed
some pretty good jumps in RA. The guider calibrates just fine with a 40+/
pixel move, and I have been able to do a 5-minute unguided with round stars
after startup in September. Of course checked primary mirror spacing,
collimation, if everything is snug, cable drag and so on. I have remeshed
the gears and redone PEC, issues persists. This is a random issue. The
Maxim guider log shows some hefty jumps in RA but NOT in DEC.



It is curious that prior to shutdown it worked like a champ...now...some
issues with a number of images that are just out of round enough as to be
useless, in RA. It is always in RA. I have looked for rodent damage, none.



I am suspecting something with guiding, easiest is weird guider cable, maybe
the guider plug on the camera. Anyone else seen this or have thoughts? I
know this is about as broad as "gee doc, I have a headache"...could be
anything.



AP driver number is 5.09.07.









Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: www.darksky.org
<http://www.darksky.org/>







<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam
paign=sig-email&utm_content=emailclient> Image removed by sender.

Virus-free.
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam
paign=sig-email&utm_content=emailclient> www.avg.com


Re: Some odd RA issues?

Mike Shade
 

Yes (or through whatever the native STL6303E uses for guiding). I did try
guiding through ASCOM direct or whatever it was, didn't seem to work very
well if I recall. There seemed to be an issue with corrections being sent
to the mount. It may have been as simple of not knowing the right settings
for that configuration. Not running USB to the mount, USB of course to the
camera.



A finicky guider relay might account for this though. The system calibrates
just fine with a 40+ pixel movement in both RA and DEC. I have replaced the
guider dongle on the camera and will try another guider cable. Over the
years have seen guider cables do weird and unexpected things.



Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: <http://www.darksky.org/>
www.darksky.org



From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 01, 2017 11:08 AM
To: ap-gto@...
Subject: RE: [ap-gto] Some odd RA issues?





Hi Mike,

I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on the camera.
Are you autoguiding through relays?

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/apcc/ap
cc
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, October 1, 2017 9:58 AM
To: ap-gto@...
Subject: [ap-gto] Some odd RA issues?



Here is the scenario: AP1600GTO permanent in observatory with CP4
controller, Planewave CDK17,
Optec
Gemini focuser-rotator/SBIG STL6303E camera, unbinned resolution
.64"/pixel. Running Maxim 5.18
and
ACP. So far so good. Now here is where it gets curious. As I am in SE AZ,
had to shut down for
monsoon
from early July to middle of September. All electronics were unplugged, I
do not suspect
lightning damage.
Prior to shutdown in July this system returned round stars across the
frame in 10-minute subs,
guided.



After starting up again in September, noticed that the stars were ever so
slightly off in RA,
maybe a pixel or
two, just enough to be not quite round, again in RA only. However, images
in RA last night showed
several
frames where there were actually double stars. Looking at the guider log
showed some pretty good
jumps in
RA. The guider calibrates just fine with a 40+/ pixel move, and I have
been able to do a 5-minute
unguided
with round stars after startup in September. Of course checked primary
mirror spacing,
collimation, if
everything is snug, cable drag and so on. I have remeshed the gears and
redone PEC, issues
persists.
This is a random issue. The Maxim guider log shows some hefty jumps in RA
but NOT in DEC.



It is curious that prior to shutdown it worked like a champ...now...some
issues with a number of
images that
are just out of round enough as to be useless, in RA. It is always in RA.
I have looked for
rodent damage,
none.



I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on
the camera.
Anyone else seen this or have thoughts? I know this is about as broad as
"gee doc, I have a
headache"...could be anything.



AP driver number is 5.09.07.









Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their
lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: www.darksky.org
<http://www.darksky.org/>




Re: Some odd RA issues?

Christopher Erickson
 

Off-axis or piggyback guiding?
 
 
-Christopher Erickson
Observatory engineer
Summit Kinetics
Waikoloa, HI 96738
www.summitkinetics.com
 



From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, October 1, 2017 6:58 AM
To: ap-gto@...
Subject: [ap-gto] Some odd RA issues?

Here is the scenario:  AP1600GTO permanent in observatory with CP4 controller, Planewave CDK17, Optec Gemini focuser-rotator/SBIG STL6303E camera, unbinned resolution .64"/pixel.  Running Maxim 5.18 and ACP.  So far so good.  Now here is where it gets curious.  As I am in SE AZ, had to shut down for monsoon from early July to middle of September.  All electronics were unplugged, I do not suspect lightning damage.  Prior to shutdown in July this system returned round stars across the frame in 10-minute subs, guided.

 

After starting up again in September, noticed that the stars were ever so slightly off in RA, maybe a pixel or two, just enough to be not quite round, again in RA only.  However, images in RA last night showed several frames where there were actually double stars.  Looking at the guider log showed some pretty good jumps in RA.  The guider calibrates just fine with a 40+/ pixel move, and I have been able to do a 5-minute unguided with round stars after startup in September.  Of course checked primary mirror spacing, collimation, if everything is snug, cable drag and so on.  I have remeshed the gears and redone PEC, issues persists.  This is a random issue.  The Maxim guider log shows some hefty jumps in RA but NOT in DEC.

 

It is curious that prior to shutdown it worked like a champ...now...some issues with a number of images that are just out of round enough as to be useless, in RA.  It is always in RA.  I have looked for rodent damage, none.

 

I am suspecting something with guiding, easiest is weird guider cable, maybe the guider plug on the camera.  Anyone else seen this or have thoughts?  I know this is about as broad as "gee doc, I have a headache"...could be anything.

 

AP driver number is 5.09.07.

 

 

 

 

Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com

 

In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their lights.

Vega, the brightest one, is now dropping towards the west.  Can it be half

a year since I watched her April rising in the east?  Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights

 

International Dark Sky Association: www.darksky.org

 


Virus-free. www.avg.com


Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3

David Attie <davattie@...>
 

I tried PHD2 along with theskyX just because I couldn’t guide with theskyX ;-) But only one instance of the driver is started and it shows 2 clients.

I reported this to SBisque.


Le 1 oct. 2017 à 22:14, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...> a écrit :

I think you probably should report the issue to Software Bisque as it sounds like a bug in TheSkyX.

I don't understand why you would be using PHD2 with TheSkyX? That said, I would make sure that two instances of the driver are not being started. 

-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, October 1, 2017 8:04 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
> 
> 
> 
> I’m getting close to an answer...
> 
> I did a new test: using PHD2 alone connected to the ASCOM V2 driver and pulseguiding works!!
> 
> TheSkyX alone with ASCOM V2: pulseguiding fails
> 
> TheSkyX + PHD2 both connected to ASCOM V2 : pulseguide fails for both. But it is not like PHD2 can’t
> connect to the ASCOM driver: it can connect and it is possible to calibrate the guiding but the pulseguide
> commands fail.
> 
> What next?
> 
> 
> 
> 
> Le 1 oct. 2017 à 18:31, 'Ray Gralak (Groups)' groups3@... [ap-gto] > gto@...> a écrit :
> 
> 
> Hi David,
> 
> > I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not
> works
> > from TheskyX and PHD2. I’m going to try the 5.10.01b
> 
> Ok, that proves that the driver's PulseGuide function is working, so I don't think the problem is in the
> driver.
> 
> It could be that TheSkyX is trying to use the driver in a cross-threaded manner. Applications written in
> .Net automatically get their ASCOM calls marshalled into a single thread, but non-net applications, like
> TheSkyX and PHD2, must be careful to perform all calls to an ASCOM driver on the same thread that the
> driver was created. If not, a cross-threaded operation might occur which will cause unexpected behavior.
> 
> -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 <http://www.ccdware.com/>
> Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
> Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
> Author of Sigma: http://www.gralak.com/sigma
> 
> > -----Original Message-----
> > From: ap-gto@... [mailto:ap-gto@...]
> > Sent: Sunday, October 1, 2017 7:26 AM
> > To: ap-gto@...
> > Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
> CP3
> >
> >
> >
> > I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not
> works
> > from TheskyX and PHD2. I’m going to try the 5.10.01b
> >
> >
> >
> > Le 1 oct. 2017 à 17:51, 'Ray Gralak (Groups)' groups3@... [ap-gto] > > gto@...> a écrit :
> >
> >
> > Hi David,
> >
> > > Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still
> > > impossible (even from PHD2 which is supposed to be independent of TheSkyX)
> >
> > The driver's pulseguide code hasn't changed in a long time so I've created a test script to hopefully
> > isolate the problem, or prove that the driver's PulseGuide function is working correctly. It connects to
> the
> > mount and issues ten 500 msec (1/2 second) PulseGuide moves to RA and Dec.
> >
> > At the end of the ten moves it reads the RA and Dec again and calculates the difference between
> the
> > start and end. This should be non-zero if both RA and Dec moved.
> >
> > To run the test:
> >
> > 1. Download the file and save it. If needed you will need to remove the ".txt" file extension. This will
> > make it a vbscript file. It is in plain text so you can read it.
> >
> > 2. Make sure no other application is already connected to the mount through the driver.
> >
> > 3. Double-click the file ("it should be named AP-PulseGuideTest.vbs").
> >
> > The driver should show and after about 10 seconds the message with the movements displayed. If
> the
> > movements are "0" then use the AP Driver's log zipper program to capture the log and email it to me
> at
> > GROUPS3 AT GRALAK DOT COM.
> >
> > http://www.gralak.com/apdriver/AP-PulseGuideTest.vbs.txt
> >
> > Again, save and rename the file to "AP-PulseGuideTest.vbs" (no ".txt" file extension) and double-
> click
> > it from file manager.
> >
> > -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 <http://www.ccdware.com/>
> <http://www.ccdware.com/>
> > Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
> > Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
> <http://www.pulseguide.com/>
> > Author of Sigma: http://www.gralak.com/sigma
> >
> > > -----Original Message-----
> > > From: ap-gto@... [mailto:ap-gto@...]
> > > Sent: Saturday, September 30, 2017 11:46 PM
> > > To: ap-gto@...
> > > Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
> > CP3
> > >
> > >
> > >
> > > Hello all,
> > >
> > > George and Howard from AP could access to my remote setup with teamviewer but they couldn't
> > find a
> > > solution.
> > >
> > > It looks like there is a problem with the ASCOM V2 driver. I have installed the last one (5.10) when
> I
> > started
> > > with my first AP mount recently. The pulseguing has never worked from TheSkyX or from PHD2. I
> > know
> > > people who are struggling with this new driver and they had to get back to an older one
> > (successfully).
> > >
> > > Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still
> > > impossible (even from PHD2 which is supposed to be independent of TheSkyX)
> > >
> > > So far, only the native Astro-Physics driver in TheSkyX is 100% functional: I can guide with
> > TheSkyX or
> > > PHD2. But this driver is limited and I really want to use the ASCOM V2.
> > >
> > > This is my current setup:
> > >
> > > Mount: AP900GTO CP3
> > > Computer: shuttle DH110SE
> > > Operating system: windows 10
> > > Software: theskyX pro ( camera add-on), PHD2, CCDautopilot.
> > >
> > > David
> > >
> > >
> > >
> > > Le mar. 26 sept. 2017 à 18:57, George george@... [ap-gto] > > gto@...> a
> > > écrit :
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > David,
> > >
> > >
> > >
> > > Call me regarding your connection. I’ll need more info and it’s faster via phone. Be at your astro
> > > computer so that we can review settings.
> > >
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > > George
> > >
> > >
> > >
> > > George Whitney
> > >
> > > Astro-Physics, Inc.
> > >
> > > Phone: 815-282-1513
> > >
> > > Email: george@...
> > >
> > >
> > >
> > > From: ap-gto@... [mailto:ap-gto@...]
> > > Sent: Tuesday, September 26, 2017 12:23 AM
> > > To: ap-gto@...
> > > Subject: [ap-gto] ASCOM guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hello everyone,
> > >
> > >
> > >
> > > Couple of months ago I purchased a used AP900GTO with the CP2 control box. I have been
> using
> > it
> > > with theskyX pro in a remote observatory. I quickly realized that ASCOM guiding (pulseguiding)
> was
> > not
> > > possible with the CP2. So I recently moved to the CP3 control box but I'm still struggling: when I'm
> > trying the
> > > buttons "+X,-X,+Y,-Y" on the autoguider panel in theskyX , I get an error message "command not
> > supported,
> > > error=11000". It was the same message when it was still the CP2.
> > >
> > >
> > >
> > > I use the ASCOM V2 driver and I changed the version of the control box in the setup. The mount
> is
> > > correctly recognized when I press "check COM port", the chip version is V1. Everything is working
> > well,
> > > except guiding. In theskyX I have selected "pulseguide" instead of "relays" in the autoguider setup.
> > >
> > >
> > >
> > > Did I miss something? Should I reinstall the ASCOM driver? Something wrong with the mount? It
> is
> > > like I'm still in CP2... :-(
> > >
> > >
> > >
> > > I also tried to guide with PHD2. I got this message "Pulseguide fails".
> > >
> > >
> > >
> > > Thank you for your help,
> > >
> > >
> > >
> > > David
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 



Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3

Ray Gralak
 

I think you probably should report the issue to Software Bisque as it sounds like a bug in TheSkyX.

I don't understand why you would be using PHD2 with TheSkyX? That said, I would make sure that two instances of the driver are not being started.

-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, October 1, 2017 8:04 AM
To: ap-gto@...
Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3



I’m getting close to an answer...

I did a new test: using PHD2 alone connected to the ASCOM V2 driver and pulseguiding works!!

TheSkyX alone with ASCOM V2: pulseguiding fails

TheSkyX + PHD2 both connected to ASCOM V2 : pulseguide fails for both. But it is not like PHD2 can’t
connect to the ASCOM driver: it can connect and it is possible to calibrate the guiding but the pulseguide
commands fail.

What next?




Le 1 oct. 2017 à 18:31, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-
gto@...> a écrit :


Hi David,

> I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not
works
> from TheskyX and PHD2. I’m going to try the 5.10.01b

Ok, that proves that the driver's PulseGuide function is working, so I don't think the problem is in the
driver.

It could be that TheSkyX is trying to use the driver in a cross-threaded manner. Applications written in
.Net automatically get their ASCOM calls marshalled into a single thread, but non-net applications, like
TheSkyX and PHD2, must be careful to perform all calls to an ASCOM driver on the same thread that the
driver was created. If not, a cross-threaded operation might occur which will cause unexpected behavior.

-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 <http://www.ccdware.com/>
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
Author of Sigma: http://www.gralak.com/sigma

> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Sunday, October 1, 2017 7:26 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
CP3
>
>
>
> I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not
works
> from TheskyX and PHD2. I’m going to try the 5.10.01b
>
>
>
> Le 1 oct. 2017 à 17:51, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-
> gto@...> a écrit :
>
>
> Hi David,
>
> > Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still
> > impossible (even from PHD2 which is supposed to be independent of TheSkyX)
>
> The driver's pulseguide code hasn't changed in a long time so I've created a test script to hopefully
> isolate the problem, or prove that the driver's PulseGuide function is working correctly. It connects to
the
> mount and issues ten 500 msec (1/2 second) PulseGuide moves to RA and Dec.
>
> At the end of the ten moves it reads the RA and Dec again and calculates the difference between
the
> start and end. This should be non-zero if both RA and Dec moved.
>
> To run the test:
>
> 1. Download the file and save it. If needed you will need to remove the ".txt" file extension. This will
> make it a vbscript file. It is in plain text so you can read it.
>
> 2. Make sure no other application is already connected to the mount through the driver.
>
> 3. Double-click the file ("it should be named AP-PulseGuideTest.vbs").
>
> The driver should show and after about 10 seconds the message with the movements displayed. If
the
> movements are "0" then use the AP Driver's log zipper program to capture the log and email it to me
at
> GROUPS3 AT GRALAK DOT COM.
>
> http://www.gralak.com/apdriver/AP-PulseGuideTest.vbs.txt
>
> Again, save and rename the file to "AP-PulseGuideTest.vbs" (no ".txt" file extension) and double-
click
> it from file manager.
>
> -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 <http://www.ccdware.com/>
<http://www.ccdware.com/>
> Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
> Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
<http://www.pulseguide.com/>
> Author of Sigma: http://www.gralak.com/sigma
>
> > -----Original Message-----
> > From: ap-gto@... [mailto:ap-gto@...]
> > Sent: Saturday, September 30, 2017 11:46 PM
> > To: ap-gto@...
> > Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
> CP3
> >
> >
> >
> > Hello all,
> >
> > George and Howard from AP could access to my remote setup with teamviewer but they couldn't
> find a
> > solution.
> >
> > It looks like there is a problem with the ASCOM V2 driver. I have installed the last one (5.10) when
I
> started
> > with my first AP mount recently. The pulseguing has never worked from TheSkyX or from PHD2. I
> know
> > people who are struggling with this new driver and they had to get back to an older one
> (successfully).
> >
> > Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still
> > impossible (even from PHD2 which is supposed to be independent of TheSkyX)
> >
> > So far, only the native Astro-Physics driver in TheSkyX is 100% functional: I can guide with
> TheSkyX or
> > PHD2. But this driver is limited and I really want to use the ASCOM V2.
> >
> > This is my current setup:
> >
> > Mount: AP900GTO CP3
> > Computer: shuttle DH110SE
> > Operating system: windows 10
> > Software: theskyX pro ( camera add-on), PHD2, CCDautopilot.
> >
> > David
> >
> >
> >
> > Le mar. 26 sept. 2017 à 18:57, George george@... [ap-gto] <ap-
> gto@...> a
> > écrit :
> >
> >
> >
> >
> >
> >
> >
> > David,
> >
> >
> >
> > Call me regarding your connection. I’ll need more info and it’s faster via phone. Be at your astro
> > computer so that we can review settings.
> >
> >
> >
> > Regards,
> >
> >
> >
> > George
> >
> >
> >
> > George Whitney
> >
> > Astro-Physics, Inc.
> >
> > Phone: 815-282-1513
> >
> > Email: george@...
> >
> >
> >
> > From: ap-gto@... [mailto:ap-gto@...]
> > Sent: Tuesday, September 26, 2017 12:23 AM
> > To: ap-gto@...
> > Subject: [ap-gto] ASCOM guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hello everyone,
> >
> >
> >
> > Couple of months ago I purchased a used AP900GTO with the CP2 control box. I have been
using
> it
> > with theskyX pro in a remote observatory. I quickly realized that ASCOM guiding (pulseguiding)
was
> not
> > possible with the CP2. So I recently moved to the CP3 control box but I'm still struggling: when I'm
> trying the
> > buttons "+X,-X,+Y,-Y" on the autoguider panel in theskyX , I get an error message "command not
> supported,
> > error=11000". It was the same message when it was still the CP2.
> >
> >
> >
> > I use the ASCOM V2 driver and I changed the version of the control box in the setup. The mount
is
> > correctly recognized when I press "check COM port", the chip version is V1. Everything is working
> well,
> > except guiding. In theskyX I have selected "pulseguide" instead of "relays" in the autoguider setup.
> >
> >
> >
> > Did I miss something? Should I reinstall the ASCOM driver? Something wrong with the mount? It
is
> > like I'm still in CP2... :-(
> >
> >
> >
> > I also tried to guide with PHD2. I got this message "Pulseguide fails".
> >
> >
> >
> > Thank you for your help,
> >
> >
> >
> > David
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>





Re: Some odd RA issues?

Ray Gralak
 

Hi Mike,

I am suspecting something with guiding, easiest is weird guider cable,
maybe the guider plug on the camera.
Are you autoguiding through relays?

-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, October 1, 2017 9:58 AM
To: ap-gto@...
Subject: [ap-gto] Some odd RA issues?



Here is the scenario: AP1600GTO permanent in observatory with CP4 controller, Planewave CDK17,
Optec
Gemini focuser-rotator/SBIG STL6303E camera, unbinned resolution .64"/pixel. Running Maxim 5.18
and
ACP. So far so good. Now here is where it gets curious. As I am in SE AZ, had to shut down for
monsoon
from early July to middle of September. All electronics were unplugged, I do not suspect
lightning damage.
Prior to shutdown in July this system returned round stars across the frame in 10-minute subs,
guided.



After starting up again in September, noticed that the stars were ever so slightly off in RA,
maybe a pixel or
two, just enough to be not quite round, again in RA only. However, images in RA last night showed
several
frames where there were actually double stars. Looking at the guider log showed some pretty good
jumps in
RA. The guider calibrates just fine with a 40+/ pixel move, and I have been able to do a 5-minute
unguided
with round stars after startup in September. Of course checked primary mirror spacing,
collimation, if
everything is snug, cable drag and so on. I have remeshed the gears and redone PEC, issues
persists.
This is a random issue. The Maxim guider log shows some hefty jumps in RA but NOT in DEC.



It is curious that prior to shutdown it worked like a champ...now...some issues with a number of
images that
are just out of round enough as to be useless, in RA. It is always in RA. I have looked for
rodent damage,
none.



I am suspecting something with guiding, easiest is weird guider cable, maybe the guider plug on
the camera.
Anyone else seen this or have thoughts? I know this is about as broad as "gee doc, I have a
headache"...could be anything.



AP driver number is 5.09.07.









Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com



In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their lights.

Vega, the brightest one, is now dropping towards the west. Can it be half

a year since I watched her April rising in the east? Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights



International Dark Sky Association: www.darksky.org <http://www.darksky.org/>




Fw: Some odd RA issues?

Joe Zeglinski
 

(possible duplicate)
Mike,
 
     I think there have been several recent OPTEC firmware updates. Try shutting down the Gemini, once you have focused on a target, so as to eliminate the OPTEC device – in your 10 minute and longer subs. Maybe the Gemini rotator motor is drifting ever so slowly.
 
    As Stan suggested – minimize the extra’s, during the test.
Joe


Re: Some odd RA issues?

Joe Zeglinski
 

Mike,
 
     I think there have been several recent OPTEC firmware updates. Try shutting down the Gemini, once you have focused on a target, so as to eliminate the OPTEC device – in your 10 minute and longer subs. Maybe the Gemini rotator motor is drifting ever so slowly.
 
    As Stan suggested – minimize the extra’s, during the test.
Joe


Some odd RA issues?

Mike Shade
 

Here is the scenario:  AP1600GTO permanent in observatory with CP4 controller, Planewave CDK17, Optec Gemini focuser-rotator/SBIG STL6303E camera, unbinned resolution .64"/pixel.  Running Maxim 5.18 and ACP.  So far so good.  Now here is where it gets curious.  As I am in SE AZ, had to shut down for monsoon from early July to middle of September.  All electronics were unplugged, I do not suspect lightning damage.  Prior to shutdown in July this system returned round stars across the frame in 10-minute subs, guided.

 

After starting up again in September, noticed that the stars were ever so slightly off in RA, maybe a pixel or two, just enough to be not quite round, again in RA only.  However, images in RA last night showed several frames where there were actually double stars.  Looking at the guider log showed some pretty good jumps in RA.  The guider calibrates just fine with a 40+/ pixel move, and I have been able to do a 5-minute unguided with round stars after startup in September.  Of course checked primary mirror spacing, collimation, if everything is snug, cable drag and so on.  I have remeshed the gears and redone PEC, issues persists.  This is a random issue.  The Maxim guider log shows some hefty jumps in RA but NOT in DEC.

 

It is curious that prior to shutdown it worked like a champ...now...some issues with a number of images that are just out of round enough as to be useless, in RA.  It is always in RA.  I have looked for rodent damage, none.

 

I am suspecting something with guiding, easiest is weird guider cable, maybe the guider plug on the camera.  Anyone else seen this or have thoughts?  I know this is about as broad as "gee doc, I have a headache"...could be anything.

 

AP driver number is 5.09.07.

 

 

 

 

Mike J. Shade: mshade@q.com

Mike J. Shade Photography:

mshadephotography.com

 

In War: Resolution

In Defeat: Defiance

In Victory: Magnanimity

In Peace: Goodwill

Sir Winston Churchill

Already, in the gathering dusk, a few of the stars are turning on their lights.

Vega, the brightest one, is now dropping towards the west.  Can it be half

a year since I watched her April rising in the east?  Low in the southwest

Antares blinks a sad farwell to fall...

Leslie Peltier, Starlight Nights

 

International Dark Sky Association: www.darksky.org

 


Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3

David Attie <davattie@...>
 

I’m getting close to an answer...

I did a new test: using PHD2 alone connected to the ASCOM V2 driver and pulseguiding works!!

TheSkyX alone with ASCOM V2: pulseguiding fails

TheSkyX + PHD2 both connected to ASCOM V2 : pulseguide fails for both. But it is not like PHD2 can’t connect to the ASCOM driver: it can connect and it is possible to calibrate the guiding but the pulseguide commands fail.

What next?



Le 1 oct. 2017 à 18:31, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...> a écrit :

Hi David,

> I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not works
> from TheskyX and PHD2. I’m going to try the 5.10.01b

Ok, that proves that the driver's PulseGuide function is working, so I don't think the problem is in the driver. 

It could be that TheSkyX is trying to use the driver in a cross-threaded manner. Applications written in .Net automatically get their ASCOM calls marshalled into a single thread, but non-net applications, like TheSkyX and PHD2, must be careful to perform all calls to an ASCOM driver on the same thread that the driver was created. If not, a cross-threaded operation might occur which will cause unexpected behavior.

-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, October 1, 2017 7:26 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
> 
> 
> 
> I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not works
> from TheskyX and PHD2. I’m going to try the 5.10.01b
> 
> 
> 
> Le 1 oct. 2017 à 17:51, 'Ray Gralak (Groups)' groups3@... [ap-gto] > gto@...> a écrit :
> 
> 
> Hi David,
> 
> > Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still
> > impossible (even from PHD2 which is supposed to be independent of TheSkyX)
> 
> The driver's pulseguide code hasn't changed in a long time so I've created a test script to hopefully
> isolate the problem, or prove that the driver's PulseGuide function is working correctly. It connects to the
> mount and issues ten 500 msec (1/2 second) PulseGuide moves to RA and Dec.
> 
> At the end of the ten moves it reads the RA and Dec again and calculates the difference between the
> start and end. This should be non-zero if both RA and Dec moved.
> 
> To run the test:
> 
> 1. Download the file and save it. If needed you will need to remove the ".txt" file extension. This will
> make it a vbscript file. It is in plain text so you can read it.
> 
> 2. Make sure no other application is already connected to the mount through the driver.
> 
> 3. Double-click the file ("it should be named AP-PulseGuideTest.vbs").
> 
> The driver should show and after about 10 seconds the message with the movements displayed. If the
> movements are "0" then use the AP Driver's log zipper program to capture the log and email it to me at
> GROUPS3 AT GRALAK DOT COM.
> 
> http://www.gralak.com/apdriver/AP-PulseGuideTest.vbs.txt
> 
> Again, save and rename the file to "AP-PulseGuideTest.vbs" (no ".txt" file extension) and double-click
> it from file manager.
> 
> -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 <http://www.ccdware.com/>
> Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
> Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
> Author of Sigma: http://www.gralak.com/sigma
> 
> > -----Original Message-----
> > From: ap-gto@... [mailto:ap-gto@...]
> > Sent: Saturday, September 30, 2017 11:46 PM
> > To: ap-gto@...
> > Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
> CP3
> >
> >
> >
> > Hello all,
> >
> > George and Howard from AP could access to my remote setup with teamviewer but they couldn't
> find a
> > solution.
> >
> > It looks like there is a problem with the ASCOM V2 driver. I have installed the last one (5.10) when I
> started
> > with my first AP mount recently. The pulseguing has never worked from TheSkyX or from PHD2. I
> know
> > people who are struggling with this new driver and they had to get back to an older one
> (successfully).
> >
> > Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still
> > impossible (even from PHD2 which is supposed to be independent of TheSkyX)
> >
> > So far, only the native Astro-Physics driver in TheSkyX is 100% functional: I can guide with
> TheSkyX or
> > PHD2. But this driver is limited and I really want to use the ASCOM V2.
> >
> > This is my current setup:
> >
> > Mount: AP900GTO CP3
> > Computer: shuttle DH110SE
> > Operating system: windows 10
> > Software: theskyX pro ( camera add-on), PHD2, CCDautopilot.
> >
> > David
> >
> >
> >
> > Le mar. 26 sept. 2017 à 18:57, George george@... [ap-gto] > gto@...> a
> > écrit :
> >
> >
> >
> >
> >
> >
> >
> > David,
> >
> >
> >
> > Call me regarding your connection. I’ll need more info and it’s faster via phone. Be at your astro
> > computer so that we can review settings.
> >
> >
> >
> > Regards,
> >
> >
> >
> > George
> >
> >
> >
> > George Whitney
> >
> > Astro-Physics, Inc.
> >
> > Phone: 815-282-1513
> >
> > Email: george@...
> >
> >
> >
> > From: ap-gto@... [mailto:ap-gto@...]
> > Sent: Tuesday, September 26, 2017 12:23 AM
> > To: ap-gto@...
> > Subject: [ap-gto] ASCOM guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hello everyone,
> >
> >
> >
> > Couple of months ago I purchased a used AP900GTO with the CP2 control box. I have been using
> it
> > with theskyX pro in a remote observatory. I quickly realized that ASCOM guiding (pulseguiding) was
> not
> > possible with the CP2. So I recently moved to the CP3 control box but I'm still struggling: when I'm
> trying the
> > buttons "+X,-X,+Y,-Y" on the autoguider panel in theskyX , I get an error message "command not
> supported,
> > error=11000". It was the same message when it was still the CP2.
> >
> >
> >
> > I use the ASCOM V2 driver and I changed the version of the control box in the setup. The mount is
> > correctly recognized when I press "check COM port", the chip version is V1. Everything is working
> well,
> > except guiding. In theskyX I have selected "pulseguide" instead of "relays" in the autoguider setup.
> >
> >
> >
> > Did I miss something? Should I reinstall the ASCOM driver? Something wrong with the mount? It is
> > like I'm still in CP2... :-(
> >
> >
> >
> > I also tried to guide with PHD2. I got this message "Pulseguide fails".
> >
> >
> >
> > Thank you for your help,
> >
> >
> >
> > David
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 



Re: RA issues with the Ascom V2 5.10 driver

OlivDeso
 

Thank You Ray, I will take some log file as soon as the sky allows, which could take several days.

At my side, the pulse guide works with the 5.10, using PHD2 and ascom. 

The goto works at the end, thought it first slew to the west, when it come back to the target to the east, it it still pretty accurate.


@David : yes the 5.03 works fine. I did not make any update between the 5.03 and the 5.10 (or 5.09 may be on one PC). I fully uninstalled the 5.03 before installing the 5.10 as advised by Ray. But may be I should have cleaned the registery data base...

I am using a USB to RS232 converter since years with AP mounts, which has always worked fine so far, on the same PC.

-> I will take some traces for Ray
-> I will retry to install the driver after having cleaned, as much as I can, the PC
-> I will try on another PC using win 10/64 (so far I used only win 7/64)

If I find something I will tell you

Olivier.

Le dimanche 1 octobre 2017 à 16:14:21 UTC+2, 'Ray Gralak (Groups)' groups3@... [ap-gto] a écrit :


 

The latest version of the driver is 5.10.01b. If you are using that we will need to see a log file. If you are not using it you can get that version here:

http://www.gralak.com/apdriver/AstroPhysics_V2_Setup_5.10.01b.exe

If the problem still occurs you should use the AP Log Zipper utility to capture the logs and settings files for us to look at. Please include the exact time that you observed the problem and if possible, a screen shot.

-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, October 1, 2017 5:47 AM
> To: ap-gto@...
> Subject: [ap-gto] RA issues with the Ascom V2 5.10 driver
>
>
>
> Hello,
>
> We are facing some problems with the latest Ascom 5.10 driver.
>
> Same functionning on 2 PCs and 3 mounts :
>
>
> PC win7/64, ascom V6.2 : upgraded from Ascom V2 driver 5.03 to 5.10 after having de-installed the 5.3
> before installing the 5.10
>
> Mounts : AP1100 (N°10 and 11) and one mach 1 -> they all have the CP3 and V chip
>
>
> symptoms:
>
> - the Ra field is empty in the Ascom V2 driver windows. The DEC field is correct
> - the cartography software ("cartes du ciel" does not shows the right RA position, the DEC seems correct)
> - when a goto is initiated between 2 "close" targets in the same constelation, the mount slew much more to
> the west (45 to 180°) then go back to the target, slewing to the east.
> If I press the stop button of the Hand controler while the mount is slewing to the west, it stops, then it goes
> back to the target after a couple of seconds.
>
> re-installing the 5.03 after hading re-installed the 5.10 solved the problem.
>
> Is this a known problem?
> Is there something to configure on the PC, or to clean. (registery data base of esle?)
>
> Any advice would be appreciated
>
> thanks
>
> Olivier
>
>
>


Re: ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3

Ray Gralak
 

Hi David,

I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not works
from TheskyX and PHD2. I’m going to try the 5.10.01b
Ok, that proves that the driver's PulseGuide function is working, so I don't think the problem is in the driver.

It could be that TheSkyX is trying to use the driver in a cross-threaded manner. Applications written in .Net automatically get their ASCOM calls marshalled into a single thread, but non-net applications, like TheSkyX and PHD2, must be careful to perform all calls to an ASCOM driver on the same thread that the driver was created. If not, a cross-threaded operation might occur which will cause unexpected behavior.

-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, October 1, 2017 7:26 AM
To: ap-gto@...
Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to CP3



I just tried your script and I got non-zero values for both RA and DEC, so it looks ok. But it still not works
from TheskyX and PHD2. I’m going to try the 5.10.01b



Le 1 oct. 2017 à 17:51, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-
gto@...> a écrit :


Hi David,

> Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still
> impossible (even from PHD2 which is supposed to be independent of TheSkyX)

The driver's pulseguide code hasn't changed in a long time so I've created a test script to hopefully
isolate the problem, or prove that the driver's PulseGuide function is working correctly. It connects to the
mount and issues ten 500 msec (1/2 second) PulseGuide moves to RA and Dec.

At the end of the ten moves it reads the RA and Dec again and calculates the difference between the
start and end. This should be non-zero if both RA and Dec moved.

To run the test:

1. Download the file and save it. If needed you will need to remove the ".txt" file extension. This will
make it a vbscript file. It is in plain text so you can read it.

2. Make sure no other application is already connected to the mount through the driver.

3. Double-click the file ("it should be named AP-PulseGuideTest.vbs").

The driver should show and after about 10 seconds the message with the movements displayed. If the
movements are "0" then use the AP Driver's log zipper program to capture the log and email it to me at
GROUPS3 AT GRALAK DOT COM.

http://www.gralak.com/apdriver/AP-PulseGuideTest.vbs.txt

Again, save and rename the file to "AP-PulseGuideTest.vbs" (no ".txt" file extension) and double-click
it from file manager.

-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 <http://www.ccdware.com/>
Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver
Author of PulseGuide: http://www.pulseguide.com <http://www.pulseguide.com/>
Author of Sigma: http://www.gralak.com/sigma

> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Saturday, September 30, 2017 11:46 PM
> To: ap-gto@...
> Subject: Re: [ap-gto] ASCOM V2 guiding (pulseguide) doesn't work even after upgrading CP2 to
CP3
>
>
>
> Hello all,
>
> George and Howard from AP could access to my remote setup with teamviewer but they couldn't
find a
> solution.
>
> It looks like there is a problem with the ASCOM V2 driver. I have installed the last one (5.10) when I
started
> with my first AP mount recently. The pulseguing has never worked from TheSkyX or from PHD2. I
know
> people who are struggling with this new driver and they had to get back to an older one
(successfully).
>
> Unfortunately, I tried many different older versions of ASCOM V2 driver but the pulseguiding is still
> impossible (even from PHD2 which is supposed to be independent of TheSkyX)
>
> So far, only the native Astro-Physics driver in TheSkyX is 100% functional: I can guide with
TheSkyX or
> PHD2. But this driver is limited and I really want to use the ASCOM V2.
>
> This is my current setup:
>
> Mount: AP900GTO CP3
> Computer: shuttle DH110SE
> Operating system: windows 10
> Software: theskyX pro ( camera add-on), PHD2, CCDautopilot.
>
> David
>
>
>
> Le mar. 26 sept. 2017 à 18:57, George george@... [ap-gto] <ap-
gto@...> a
> écrit :
>
>
>
>
>
>
>
> David,
>
>
>
> Call me regarding your connection. I’ll need more info and it’s faster via phone. Be at your astro
> computer so that we can review settings.
>
>
>
> Regards,
>
>
>
> George
>
>
>
> George Whitney
>
> Astro-Physics, Inc.
>
> Phone: 815-282-1513
>
> Email: george@...
>
>
>
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Tuesday, September 26, 2017 12:23 AM
> To: ap-gto@...
> Subject: [ap-gto] ASCOM guiding (pulseguide) doesn't work even after upgrading CP2 to CP3
>
>
>
>
>
>
>
>
>
> Hello everyone,
>
>
>
> Couple of months ago I purchased a used AP900GTO with the CP2 control box. I have been using
it
> with theskyX pro in a remote observatory. I quickly realized that ASCOM guiding (pulseguiding) was
not
> possible with the CP2. So I recently moved to the CP3 control box but I'm still struggling: when I'm
trying the
> buttons "+X,-X,+Y,-Y" on the autoguider panel in theskyX , I get an error message "command not
supported,
> error=11000". It was the same message when it was still the CP2.
>
>
>
> I use the ASCOM V2 driver and I changed the version of the control box in the setup. The mount is
> correctly recognized when I press "check COM port", the chip version is V1. Everything is working
well,
> except guiding. In theskyX I have selected "pulseguide" instead of "relays" in the autoguider setup.
>
>
>
> Did I miss something? Should I reinstall the ASCOM driver? Something wrong with the mount? It is
> like I'm still in CP2... :-(
>
>
>
> I also tried to guide with PHD2. I got this message "Pulseguide fails".
>
>
>
> Thank you for your help,
>
>
>
> David
>
>
>
>
>
>
>
>
>
>
>
>