Date   

Re: Trouble with MaxDome II slaving to APPM

Ray Gralak
 

It's a problem with APPM, not MAXDome.
Again, not really. For MaxDome operation and setting up slaving of the dome to the scope, please take a look at this link:

https://cdn.diffractionlimited.com/help/maxdome/MaxDome.htm

-Ray


Re: Trouble with MaxDome II slaving to APPM

Ray Gralak
 

Shane,

You can use the "Passive"mode (in "AP Point Mapper -> Dome Settings" and
ASCOM's Device Hub or SGP's Dome Slaving, but you will likely have to
add significant delays so that APPM can recognize that the dome is
moving . The big disadvantage of this is that your mapping settings
will take hours--I guess that's OK since you shouldn't need to do them
that often...
How much delay do you have configured in APPM for passive dome mode?

If it is 5+5 seconds for each point, then 360 points would add up to 3600 seconds (1 hour) maximum of extra time. If it takes "hours" to create a model, then maybe the dome driver is not promptly reporting movements, which would allow you to reduce the delays?

-Ray


Re: Trouble with MaxDome II slaving to APPM

Ray Gralak
 

Hi Shane,

According to Ray, there are no plans to fix APPM's "Active" mode as he
believes that dome geometry should be built into the dome driver. But
it's not. ASCOM standards do not include dome geometry, nor the ability
for the low level drivers (dome and telescope) to exchange information
and send commands to each other. Every other application I've used that
claims to do dome/mount slaving/coordination implements dome geometry.
ASCOM has argued that each application writer doesn't have to reinvent the wheel to use a device, like a telescope mount. However, to actively control a Dome, as you point out, applications HAVE to reinvent the wheel (i.e., dome geometry). My guess at the reason for the "dumb" ASCOM Dome driver API is to "protect" early commercial applications that had already included the dome geometry functionality.

According to Ray, there are no plans to fix APPM's "Active" mode as he
believes that dome geometry should be built into the dome driver.
And that's true because using Passive mode works well enough. You should not have to build a model very often with a permanent setup, so if it takes a little longer, so what. You can build a model on a moonlit night or when the skies have a thin cirrus layer.

That said, soon there may be a platform where people can post new feature requests, and users can vote for the features that interest them. Then, based on popularity and difficulty of implementation, A-P will prioritize and potentially authorize new features to be built into APCC. So, Shane, you can post your feature request there and let other mount owners vote on it.

I don't really know why there is an "Active" mode--I guess if you have a
really small scope or a really wide dome slot, it might work. But my
scope is a 4 inches and the doe slot is 18 inches wide and I still can't
use it.
Active mode works with POTH, which has since been deprecated by the ASCOM team. The "replacement " application, Device Hub, does not include the necessary functionality from POTH, and the author has decided not to port it. BTW, I even offered a solution that would be an extension of the ASCOM API, but it was rejected. So, if you want to put blame somewhere, put it on ASCOM. ASCOM is not providing full backward compatibility for their platform and has mantras that they say they follow, except when they don't.

-Ray



-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Shane Ramotowski
Sent: Monday, September 20, 2021 4:33 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Trouble with MaxDome II slaving to APPM

Hi Alan,

I ran into this a few months ago. AAPM does not have a way to do dome
geometry so it's dome positioning command are wrong. They are all based
from the center of the dome instead of where the telescope is. You've
seen the first dome slew; the rest are incorrect also most end up with
the dome partially or totally occluding the scope.

There is an extended topic about this from February:
<https://ap-gto.groups.io/g/main/message/76596>

According to Ray, there are no plans to fix APPM's "Active" mode as he
believes that dome geometry should be built into the dome driver. But
it's not. ASCOM standards do not include dome geometry, nor the ability
for the low level drivers (dome and telescope) to exchange information
and send commands to each other. Every other application I've used that
claims to do dome/mount slaving/coordination implements dome geometry.

I don't really know why there is an "Active" mode--I guess if you have a
really small scope or a really wide dome slot, it might work. But my
scope is a 4 inches and the doe slot is 18 inches wide and I still can't
use it.

You can use the "Passive"mode (in "AP Point Mapper -> Dome Settings" and
ASCOM's Device Hub or SGP's Dome Slaving, but you will likely have to
add significant delays so that APPM can recognize that the dome is
moving . The big disadvantage of this is that your mapping settings
will take hours--I guess that's OK since you shouldn't need to do them
that often...

The good news is that both Device Hub and SGP are smart enough to slew
the dome to the correct position, even when the mount goes counterweight
up!

Good Luck - Shane

On 9/19/2021 4:47 PM, alanericksonf6@... wrote:
Hi. I'm trying to run APPM with MaxDome II. The first image attempt at
the zenith fails due to the dome being 180 degrees off. The scope is
on the west side of the mount / counterweights on the east. The dome
shutter azimuth is east, but it really should be west because that's
where the scope is. Image attached. Any ideas?

Thanks.
-Alan

--
Shane Ramotowski
kor@...
https://www.kor-astro.net




Re: Trouble with MaxDome II slaving to APPM

Ray Gralak
 

APPM’s calling the shots in regards to the maxdome moves, so I betcha I’d be calling for help here too.
Actually, APPM is not calling the shots. Because of the poor API design of the ASCOM Dome drivers, the dome driver is usually “dumb” and doesn’t know about mount geometry, so APPM’s “Active” mode usually won’t work.

So, the only way to use a dome with APPM is to put it in “passive” mode where it just watches the dome’s movement until it stops. APPM has configurable delays to wait before starting for checking for dome movement, as well as a time to wait after the dome stops moving.

-Ray


From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Seb@stro
Sent: Sunday, September 19, 2021 9:59 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Trouble with MaxDome II slaving to APPM


This really isn't the right forum for MaxDome-II support.

Not sure why it wouldn’t be...

APPM’s calling the shots in regards to the maxdome moves, so I betcha I’d be calling for help here too.

Funny how some people seem to first think of integrated systems issues as if all problems can only be solved by troubleshooting single component as if it were sitting alone.


Seems pretty obvious to me that when two (or more) pieces of hardware and/or software are integrated together, there are not so many other options but to inquire for help from the parties involved (be it a manufacturer, developer, vendor, etc.)


I unfortunately can’t be of much help to the op’s issue, but man I would definitely not discourage him asking for help here about this !


Sébastien


Re: APPM - error

Ray Gralak
 

Hi Ted,

I am glad that APPM and APCC Pro are working well for you!

Is this particular 95-point model only applicable for this equipment, image scale and imaging season?
In general, yes. However, if polar alignment changes enough because of ground settling, or if you change equipment balance significantly, then the model may not work as well.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ted Mickle via groups.io
Sent: Sunday, September 19, 2021 2:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM - error

Ray,

I ran my first-ever APPM model three nights back, a 95 point model.

Since then, using APPM I’ve run hours of 900 second narrowband imaging unguided and marvel at the small
round stars, even in regions of the sky that were not included in the original model (created with a Tak 130,
1100 GTO and QHY 600M).

Is this particular 95-point model only applicable for this equipment, image scale and imaging season?

Thanks for APPM - it’s transformed my astroimaging.

Ted




On Sep 19, 2021, at 13:16, Ray Gralak <iogroups@...> wrote:

HI Ron,

Now what does "verify" check box do?
It runs the same steps to collect sky data points but with the active model for the purpose of diagnosing
pointing or tracking problems.

and how often should I make a new model?
We might ask you to run this if you have a dramatic pointing or tracking problem with a model, which
doesn't appear to be the case. You are better off using this time for imaging!

-Ray


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ron Kramer
Sent: Sunday, September 19, 2021 10:38 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM - error

thanks for the assists Ray - and thanks for the nina compatible updates.
Now what does "verify" check box do?
and how often should I make a new model?
I did a 300, 600 and 1000 second exposure after the APPM model was applied and I had round stars with
no
guiding even at 1000.
And at a good HFR of 3.48 (average is often higher even when guiding).
My max before the model was about 60-90 seconds and I'd still see eggs.


On Sun, Sep 19, 2021 at 12:24 PM Ray Gralak <iogroups@...> wrote:


Hi Ron,

> Results were well worth it. BEFORE the point model I would get oblong stars if I went over 60-90
second
> exposures. Last night I did 1000 second exposure and had round stars. It blew me away.

That's excellent! I'm glad you got everything working! :-)

Best regards,

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ron Kramer
> Sent: Sunday, September 19, 2021 6:03 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APPM - error
>
> MAYBE that was the fix. I had great results last night. The pop up error never appeared. And one of
the
> solutions I tried was to update ASTAP. I was using the latest but I went back and noticed there is a
dev
> release that is newer and I had installed that.
>
> I made other changes to settings. I went full frame, and bin2 and I sed a APPM setting from default
to 0.
> Something or everything made it work... but could be it was using the dev release of ASTAP that
fixed it.
>
> Results were well worth it. BEFORE the point model I would get oblong stars if I went over 60-90
second
> exposures. Last night I did 1000 second exposure and had round stars. It blew me away.
>
>
>
>










--

Ron Kramer
https://www.facebook.com/Ron.R.Kramer







Re: Trouble with MaxDome II slaving to APPM

Shane Ramotowski
 

It's a problem with APPM, not MAXDome. <https://ap-gto.groups.io/g/main/message/76596>

- Shane

On 9/19/2021 5:55 PM, Christopher Erickson wrote:
This really isn't the right forum for MaxDome-II support. Diffraction Limited has their own support forum and there is the Observatory forum on Cloudy Nights.

Is this something that has worked reliably in the past and suddenly started to fail?

I would double-check your az encoder mechanical setup and your MaxDome-II ASCOM driver parameters. Extraneous light near the az encoder can fool an optosenser.

-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com <http://www.summitkinetics.com>

On Sun, Sep 19, 2021, 1:04 PM <alanericksonf6@... <mailto:alanericksonf6@...>> wrote:

Hi. I'm trying to run APPM with MaxDome II. The first image
attempt at the zenith fails due to the dome being 180 degrees off.
The scope is on the west side of the mount / counterweights on the
east. The dome shutter azimuth is east, but it really should be
west because that's where the scope is. Image attached. Any ideas?

Thanks.
-Alan

--
Shane Ramotowski
kor@...
https://www.kor-astro.net


Re: Trouble with MaxDome II slaving to APPM

Shane Ramotowski
 

Hi Alan,

I ran into this a few months ago.  AAPM does not have a way to do dome geometry so it's dome positioning command are wrong.  They are all based from the center of the dome instead of where the telescope is.  You've seen the first dome slew; the rest are incorrect also most end up with the dome partially or totally occluding the scope.

There is an extended topic about this from February: <https://ap-gto.groups.io/g/main/message/76596>

According to Ray, there are no plans to fix APPM's "Active" mode as he believes that dome geometry should be built into the dome driver.  But it's not.  ASCOM standards do not include dome geometry, nor the ability for the low level drivers (dome and telescope) to exchange information and send commands to each other. Every other application I've used that claims to do dome/mount slaving/coordination implements dome geometry.

I don't really know why there is an "Active" mode--I guess if you have a really small scope or a really wide dome slot, it might work.  But my scope is a 4 inches and the doe slot is 18 inches wide and I still can't use it.

You can use the "Passive"mode (in "AP Point Mapper -> Dome Settings" and ASCOM's Device Hub or SGP's Dome Slaving, but you will likely have to add significant delays so that APPM can recognize that the dome is moving .  The big disadvantage of this is that your mapping settings will take hours--I guess that's OK since you shouldn't need to do them that often...

The good news is that both Device Hub and SGP are smart enough to slew the dome to the correct position, even when the mount goes counterweight up!

Good Luck - Shane

On 9/19/2021 4:47 PM, alanericksonf6@... wrote:
Hi. I'm trying to run APPM with MaxDome II. The first image attempt at the zenith fails due to the dome being 180 degrees off. The scope is on the west side of the mount / counterweights on the east. The dome shutter azimuth is east, but it really should be west because that's where the scope is. Image attached. Any ideas?

Thanks.
-Alan

--
Shane Ramotowski
kor@...
https://www.kor-astro.net


Re: Cloudy Nights post about the Mach 2 needs clarification

M Hambrick
 

There seems to have been some sort of cyber-security incident at Cloudy Nights. Since a couple days ago you must sign into your account just to be able to look at the classified listings. This morning, the classified menu tab is not even visible until you have signed in.

Mike


Re: Trouble with MaxDome II slaving to APPM

Sébastien Doré
 


This really isn't the right forum for MaxDome-II support.

Not sure why it wouldn’t be...

APPM’s calling the shots in regards to the maxdome moves, so I betcha I’d be calling for help here too. 

Funny how some people seem to first think of integrated systems issues as if all problems can only be solved by troubleshooting single component as if it were sitting alone.

Seems pretty obvious to me that when two (or more) pieces of hardware and/or software are integrated together, there are not so many other options but to inquire for help from the parties involved (be it a manufacturer, developer, vendor, etc.) 

I unfortunately can’t be of much help to the op’s issue, but man I would definitely not discourage him asking for help here about this !

Sébastien 




Re: Trouble with MaxDome II slaving to APPM

Christopher Erickson
 

This really isn't the right forum for MaxDome-II support. Diffraction Limited has their own support forum and there is the Observatory forum on Cloudy Nights.

Is this something that has worked reliably in the past and suddenly started to fail?

I would double-check your az encoder mechanical setup and your MaxDome-II ASCOM driver parameters. Extraneous light near the az encoder can fool an optosenser.

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

On Sun, Sep 19, 2021, 1:04 PM <alanericksonf6@...> wrote:
Hi. I'm trying to run APPM with MaxDome II. The first image attempt at the zenith fails due to the dome being 180 degrees off. The scope is on the west side of the mount / counterweights on the east. The dome shutter azimuth is east, but it really should be west because that's where the scope is. Image attached. Any ideas?

Thanks.
-Alan


Trouble with MaxDome II slaving to APPM

Alan Erickson
 

Hi. I'm trying to run APPM with MaxDome II. The first image attempt at the zenith fails due to the dome being 180 degrees off. The scope is on the west side of the mount / counterweights on the east. The dome shutter azimuth is east, but it really should be west because that's where the scope is. Image attached. Any ideas?

Thanks.
-Alan


Re: APPM - error

Ted Mickle
 

Ray,

I ran my first-ever APPM model three nights back, a 95 point model.

Since then, using APPM I’ve run hours of 900 second narrowband imaging unguided and marvel at the small round stars, even in regions of the sky that were not included in the original model (created with a Tak 130, 1100 GTO and QHY 600M).

Is this particular 95-point model only applicable for this equipment, image scale and imaging season?

Thanks for APPM - it’s transformed my astroimaging.

Ted

On Sep 19, 2021, at 13:16, Ray Gralak <iogroups@...> wrote:

HI Ron,

Now what does "verify" check box do?
It runs the same steps to collect sky data points but with the active model for the purpose of diagnosing pointing or tracking problems.

and how often should I make a new model?
We might ask you to run this if you have a dramatic pointing or tracking problem with a model, which doesn't appear to be the case. You are better off using this time for imaging!

-Ray


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ron Kramer
Sent: Sunday, September 19, 2021 10:38 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM - error

thanks for the assists Ray - and thanks for the nina compatible updates.
Now what does "verify" check box do?
and how often should I make a new model?
I did a 300, 600 and 1000 second exposure after the APPM model was applied and I had round stars with no
guiding even at 1000.
And at a good HFR of 3.48 (average is often higher even when guiding).
My max before the model was about 60-90 seconds and I'd still see eggs.


On Sun, Sep 19, 2021 at 12:24 PM Ray Gralak <iogroups@...> wrote:


Hi Ron,

> Results were well worth it. BEFORE the point model I would get oblong stars if I went over 60-90
second
> exposures. Last night I did 1000 second exposure and had round stars. It blew me away.

That's excellent! I'm glad you got everything working! :-)

Best regards,

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ron Kramer
> Sent: Sunday, September 19, 2021 6:03 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APPM - error
>
> MAYBE that was the fix. I had great results last night. The pop up error never appeared. And one of
the
> solutions I tried was to update ASTAP. I was using the latest but I went back and noticed there is a
dev
> release that is newer and I had installed that.
>
> I made other changes to settings. I went full frame, and bin2 and I sed a APPM setting from default
to 0.
> Something or everything made it work... but could be it was using the dev release of ASTAP that
fixed it.
>
> Results were well worth it. BEFORE the point model I would get oblong stars if I went over 60-90
second
> exposures. Last night I did 1000 second exposure and had round stars. It blew me away.
>
>
>
>










--

Ron Kramer
https://www.facebook.com/Ron.R.Kramer






Re: APPM - error

Ray Gralak
 

HI Ron,

Now what does "verify" check box do?
It runs the same steps to collect sky data points but with the active model for the purpose of diagnosing pointing or tracking problems.

and how often should I make a new model?
We might ask you to run this if you have a dramatic pointing or tracking problem with a model, which doesn't appear to be the case. You are better off using this time for imaging!

-Ray


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ron Kramer
Sent: Sunday, September 19, 2021 10:38 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM - error

thanks for the assists Ray - and thanks for the nina compatible updates.
Now what does "verify" check box do?
and how often should I make a new model?
I did a 300, 600 and 1000 second exposure after the APPM model was applied and I had round stars with no
guiding even at 1000.
And at a good HFR of 3.48 (average is often higher even when guiding).
My max before the model was about 60-90 seconds and I'd still see eggs.


On Sun, Sep 19, 2021 at 12:24 PM Ray Gralak <iogroups@...> wrote:


Hi Ron,

> Results were well worth it. BEFORE the point model I would get oblong stars if I went over 60-90
second
> exposures. Last night I did 1000 second exposure and had round stars. It blew me away.

That's excellent! I'm glad you got everything working! :-)

Best regards,

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ron Kramer
> Sent: Sunday, September 19, 2021 6:03 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APPM - error
>
> MAYBE that was the fix. I had great results last night. The pop up error never appeared. And one of
the
> solutions I tried was to update ASTAP. I was using the latest but I went back and noticed there is a
dev
> release that is newer and I had installed that.
>
> I made other changes to settings. I went full frame, and bin2 and I sed a APPM setting from default
to 0.
> Something or everything made it work... but could be it was using the dev release of ASTAP that
fixed it.
>
> Results were well worth it. BEFORE the point model I would get oblong stars if I went over 60-90
second
> exposures. Last night I did 1000 second exposure and had round stars. It blew me away.
>
>
>
>










--

Ron Kramer
https://www.facebook.com/Ron.R.Kramer


Re: APPM - error

Ron Kramer
 

thanks for the assists Ray - and thanks for the nina compatible updates. 
Now what does "verify" check box do?
and how often should I make a new model? 
I did a 300, 600 and 1000 second exposure after the APPM model was applied and I had round stars with no guiding even at 1000. 
And at a good HFR of 3.48  (average is often higher even when guiding).
My max before the model was about 60-90 seconds and I'd still see eggs.


On Sun, Sep 19, 2021 at 12:24 PM Ray Gralak <iogroups@...> wrote:
Hi Ron,

> Results were well worth it.  BEFORE the point model I would get oblong stars if I went over 60-90 second
> exposures.  Last night I did 1000 second exposure and had round stars.  It blew me away.

That's excellent! I'm glad you got everything working! :-)

Best regards,

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ron Kramer
> Sent: Sunday, September 19, 2021 6:03 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APPM - error
>
> MAYBE that was the fix.  I had great results last night. The pop up error never appeared.  And one of the
> solutions I tried was to update ASTAP. I was using the latest but I went back and noticed there is a dev
> release that is newer and I had installed that.
>
> I made other changes to settings.  I went full frame, and bin2 and I sed a APPM setting from default to 0.
> Something or everything made it work... but could be it was using the dev release of ASTAP that fixed it.
>
> Results were well worth it.  BEFORE the point model I would get oblong stars if I went over 60-90 second
> exposures.  Last night I did 1000 second exposure and had round stars.  It blew me away.
>
>
>
>









Re: Mount Synchronization Memory Lapse

Ray Gralak
 

Hi Jerome,

The first thing to check is that latitude/longitude/time are correct (on APCC's Site tab). If any of those are wrong, you can have proper RA/Dec, but the wrong Altitude/Azimuth.

If you are not running the latest APCC, you should update. Some of the earlier versions would only try to read Lat/Long once, and if the mount was not powered, APCC would use Lat=0. Later versions of APCC will try to read Lat/Long more robustly.

But to answer your question, one way to restore mount position is to:

1) Move the mount to the park 3 position by loosening the clutches and manually moving the scope, or via move buttons if you are remote and have a camera viewing the scope.
2) Tighten the clutches if you had loosened and manually moved the mount in the previous step.
3) Use APCC or the ASCOM driver to park the mount at the current position
4) Use APCC or the ASCOM driver to unpark from the Park 3 position.
5) Slew the scope to someplace away from Park 3.
6) Do a plate solve and recal to regain precise sky position.

Another way to do this is to do an All-Sky plate solve and recal. But you will have to temporarily uncheck "Prevent errant RECALs" in APCC's advanced settings. That is, after successfully recalibrating, go back into APCC's advanced settings and set the checkbox option for "Prevent errant RECALs" .

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Jerome A Yesavage
Sent: Saturday, September 18, 2021 9:02 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Mount Synchronization Memory Lapse

Hello,
I have a nice new camera attached to my Mach1 but I failed to check the balance before messing with the
camera. The scope is now way out of synch with what I see in ACP. I have run the ACP findlostscope script
and it says it corrects, but it does not. The fine team at Astrophysics saved my buns on this one time in the
past with another synchronization procedure purely done through APCC... but I cannot remember the
procedure nor find my notes.

Can somebody tell me what the procedure is?

The ALT reading on APCC and APC differs by 40 DEG.

BTW, the new lightweight camera is a ZWO ASI 6200... it does not produce lightweight files.... they are
100MB...

JY


Re: APPM - error

Ray Gralak
 

Hi Ron,

Results were well worth it. BEFORE the point model I would get oblong stars if I went over 60-90 second
exposures. Last night I did 1000 second exposure and had round stars. It blew me away.
That's excellent! I'm glad you got everything working! :-)

Best regards,

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ron Kramer
Sent: Sunday, September 19, 2021 6:03 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM - error

MAYBE that was the fix. I had great results last night. The pop up error never appeared. And one of the
solutions I tried was to update ASTAP. I was using the latest but I went back and noticed there is a dev
release that is newer and I had installed that.

I made other changes to settings. I went full frame, and bin2 and I sed a APPM setting from default to 0.
Something or everything made it work... but could be it was using the dev release of ASTAP that fixed it.

Results were well worth it. BEFORE the point model I would get oblong stars if I went over 60-90 second
exposures. Last night I did 1000 second exposure and had round stars. It blew me away.




Re: Tool Buckets to schlep an 1100GTO

Harley Davidson
 

Very interesting Elenillor, nice idea.

tony

On 9/19/2021 9:17 AM, Elenillor wrote:
I will be trying some flexible tool buckets for the 1100GTO. Nominally 12" diameter x 15" high I added a Kydex sleeve and a 1" thick closed foam disk in the bottom to keep the buckets upright and round. The Dec assembly just fits with the DoveDV10 plate attached. Will add a few foam wedges as needed to keep things from flopping around. 

Just for storage in the house, transport to the car and from the car to scope setup. Will have see how the system work in real life.



Tool Buckets to schlep an 1100GTO

Elenillor
 

I will be trying some flexible tool buckets for the 1100GTO. Nominally 12" diameter x 15" high I added a Kydex sleeve and a 1" thick closed foam disk in the bottom to keep the buckets upright and round. The Dec assembly just fits with the DoveDV10 plate attached. Will add a few foam wedges as needed to keep things from flopping around. 

Just for storage in the house, transport to the car and from the car to scope setup. Will have see how the system work in real life.


Re: APPM - error

Ron Kramer
 

Thanks Dale.  I made several tweaks including your full-frame, bin2 and its working great.  THANK YOU!

I always had to guide at over 60-90 second exposures.  After APPM last night I did 300 sec, then 500, then 800 then 1000 second exposures and all had excellent stars and low HFR.  I'm amazed. 

only problem was APPM sometimes didn't want for the dome to slew/settle. (about 10% of the time).  But with the scope 1/2 way in the slit it was still able to get enough stars to solve. 

 


Re: APPM - error

Ron Kramer
 

MAYBE that was the fix.  I had great results last night. The pop up error never appeared.  And one of the solutions I tried was to update ASTAP. I was using the latest but I went back and noticed there is a dev release that is newer and I had installed that.

I made other changes to settings.  I went full frame, and bin2 and I sed a APPM setting from default to 0.  Something or everything made it work... but could be it was using the dev release of ASTAP that fixed it. 

Results were well worth it.  BEFORE the point model I would get oblong stars if I went over 60-90 second exposures.  Last night I did 1000 second exposure and had round stars.  It blew me away. 

 

5741 - 5760 of 86888