Date   

Re: “Lost in Space” remote resume

Ray Gralak
 

APCC when it was positioned for all sky sync. Guess the mount thought the CW was up. Could that be it?
Yes, maybe. It depends on what changed.

Was this the first time the mount was used after the time had changed? If the mount's time and timezone got out of sync by one hour in RA that could make the mount appear to be lost.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Jim Fakatselis
Sent: Friday, November 13, 2020 10:54 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] “Lost in Space” remote resume

Hmmm…I positioned the scope myself and I know the CW was down, however, I believe I saw the CW up flag in
APCC when it was positioned for all sky sync. Guess the mount thought the CW was up. Could that be it?



Thank you Ray.





Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10



From: Ray Gralak <mailto:groups3@gralak.com>
Sent: Saturday, November 14, 2020 12:28 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] “Lost in Space” remote resume



My question is why didn’t the first method work?


There are at least two possibilities:



1. the mount was in a counterweight-up position when synched.



2. the synch coordinates were bad, which can happen, and is the very reason for the option to prevent errant
recalls.



-Ray Gralak

Author of PEMPro

Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro

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



-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Jim Fakatselis
Sent: Friday, November 13, 2020 6:40 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] “Lost in Space” remote resume
[Edited Message Follows]
Ray,
Last week my observatory Mach1GTO got lost and the slews became corrupted, i.e. lost in space. Found that
all

sky solve with Maxim resulted in an error in APCC that indicated I was too far from the position the mount
thought

it was pointing to.
One of the two suggestions you had recommended for that remote resync was:
“ In APCC's advanced settings, you can uncheck "Prevent errant RECALs". That will allow the platesolve/sync to
be used anywhere in the sky. Make sure to reenable the option afterwards.”
After doing another all sky search in Maxim it came up with a plate solve solution and I synced this new mount
position in Maxim to plate solve coordinates. This did not result in the mount being restored to the proper
position. As I tried to park it, it started driving towards the pier.
Can APCC not sync it properly through Maxim? Or what did I do incorrectly?
I then tried your other suggestion using a camera on my observatory to bring it close to Park 3 as I could
ascertain by looking at mount in camera with errant recals restored. When I parked it to current position then
unparked from Park 3 it work as you said. All was good
My question is why didn’t the first method work?
Thanks in advance,
Jim













<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-
email&utm_content=emailclient&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-
email?utm_medium=email&utm_source=link&utm_campaign=sig-
email&utm_content=emailclient&utm_term=link>


Re: best power schema for nomad set up

Andrea Lucchetti
 

Thanks a lot. 
Andrea


Re: “Lost in Space” remote resume

Jim Fakatselis
 

Hmmm…I positioned the scope myself and I know the CW was down, however, I believe I saw the CW up flag in APCC when it was positioned for all sky sync. Guess the mount thought the CW was up. Could that be it?

 

Thank you Ray.

 

 

Sent from Mail for Windows 10

 

From: Ray Gralak
Sent: Saturday, November 14, 2020 12:28 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] “Lost in Space” remote resume

 

> My question is why didn’t the first method work?

 

There are at least two possibilities:

 

1. the mount was in a counterweight-up position when synched.

 

2. the synch coordinates were bad, which can happen, and is the very reason for the option to prevent errant recalls.

 

-Ray Gralak

Author of PEMPro

Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro

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

 

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

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Jim Fakatselis

> Sent: Friday, November 13, 2020 6:40 PM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] “Lost in Space” remote resume

>

> [Edited Message Follows]

>

>

> Ray,

> Last week my observatory Mach1GTO got lost and the slews became corrupted, i.e. lost in space.  Found that all

> sky solve with Maxim resulted in an error in APCC that indicated I was too far from the position the mount thought

> it was pointing to.

>

>

> One of the two suggestions you had recommended for that remote resync was:

>

>

> “ In APCC's advanced settings, you can uncheck "Prevent errant RECALs". That will allow the platesolve/sync to

> be used anywhere in the sky. Make sure to reenable the option afterwards.”

>

>

>

>

> After  doing another all sky search in Maxim it came up with a plate solve solution and I synced this new mount

> position in Maxim to plate solve coordinates. This did not result in the mount being restored to the proper

> position.  As I tried to park it, it started driving towards the pier.

>

> Can APCC not sync it properly through Maxim?  Or what did I do incorrectly?

>

> I then tried your other suggestion using a camera on my observatory to bring it close to Park 3 as I could

> ascertain by looking at mount in camera with errant recals restored. When I parked it to current position then

> unparked from Park 3 it work as you said. All was good

>

> My question is why didn’t the first method work?

>

> Thanks in advance,

> Jim

>

>

>

>

 

 

 

 

 

 


Virus-free. www.avast.com


Re: Guide rate always being set to 1.

Ray Gralak
 

However, every time I start up PHD 2, it sets it to 1x. I have
changed all the settings I can find in PHD to 0.5x but it still changes it.
Any suggestions?
Changing the guide rate in PHD2 will not change the rate in the mount. You need to set the guide rate in the driver and/or APCC.

That said, as others have mentioned, 1.0x is the recommended guide rate.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Tom Blahovici
Sent: Thursday, November 12, 2020 8:43 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Guide rate always being set to 1.

Hi,
I have the CP4 and have set the guide rate to 0.5x. It is set this way in each Ascom driver as well. I am using
APCC standard.
I understand that I should use a guide rate of 0.5x. However, every time I start up PHD 2, it sets it to 1x. I have
changed all the settings I can find in PHD to 0.5x but it still changes it.
Any suggestions?
Thanks, Tom


Re: APCC Pro v1.8.8.3

Ray Gralak
 

Ray, I just updated to this version of pro. I seemed to have lost my pointing model and horizon limits. Is there a
way to get them back or do they get erased with the update? Dui
Installing an update does not erase settings.

Luckily, APCC make1s a backup of all settings every time it starts. You can use this menu item to reload all settings:

File->Load Settings.

When the windows opens to specify the settings file, you should navigate to this folder and select one of the ".ApccZ" files (sorting the files by date in the dialog can make it easier to find the latest files):

C:\ProgramData\Astro-Physics\APCC\Backups

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Dui @ DDHO
Sent: Friday, November 13, 2020 9:15 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro v1.8.8.3

Ray, I just updated to this version of pro. I seemed to have lost my pointing model and horizon limits. Is there a
way to get them back or do they get erased with the update? Dui


Re: “Lost in Space” remote resume

Ray Gralak
 

My question is why didn’t the first method work?
There are at least two possibilities:

1. the mount was in a counterweight-up position when synched.

2. the synch coordinates were bad, which can happen, and is the very reason for the option to prevent errant recalls.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Jim Fakatselis
Sent: Friday, November 13, 2020 6:40 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] “Lost in Space” remote resume

[Edited Message Follows]


Ray,
Last week my observatory Mach1GTO got lost and the slews became corrupted, i.e. lost in space. Found that all
sky solve with Maxim resulted in an error in APCC that indicated I was too far from the position the mount thought
it was pointing to.


One of the two suggestions you had recommended for that remote resync was:


“ In APCC's advanced settings, you can uncheck "Prevent errant RECALs". That will allow the platesolve/sync to
be used anywhere in the sky. Make sure to reenable the option afterwards.”




After doing another all sky search in Maxim it came up with a plate solve solution and I synced this new mount
position in Maxim to plate solve coordinates. This did not result in the mount being restored to the proper
position. As I tried to park it, it started driving towards the pier.

Can APCC not sync it properly through Maxim? Or what did I do incorrectly?

I then tried your other suggestion using a camera on my observatory to bring it close to Park 3 as I could
ascertain by looking at mount in camera with errant recals restored. When I parked it to current position then
unparked from Park 3 it work as you said. All was good

My question is why didn’t the first method work?

Thanks in advance,
Jim




“Lost in Space” remote resume

Jim Fakatselis
 
Edited

Ray,
Last week my observatory Mach1GTO got lost and the slews became corrupted, i.e. lost in space.  Found that all sky solve with Maxim resulted in an error in APCC that indicated I was too far from the position the mount thought it was pointing to. 

One of the two suggestions you had recommended for that remote resync was:


 In APCC's advanced settings, you can uncheck "Prevent errant RECALs". That will allow the platesolve/sync to be used anywhere in the sky. Make sure to reenable the option afterwards.”

After  doing another all sky search in Maxim it came up with a plate solve solution and I synced this new mount position in Maxim to plate solve coordinates. This did not result in the mount being restored to the proper position.  As I tried to park it, it started driving towards the pier.  

Can APCC not sync it properly through Maxim?  Or what did I do incorrectly? 

I then tried your other suggestion using a camera on my observatory to bring it close to Park 3 as I could ascertain by looking at mount in camera with errant recals restored. When I parked it to current position then unparked from Park 3 it work as you said. All was good  

My question is why didn’t the first method work?

Thanks in advance,
Jim


Re: Yet Another M31: knocking the rust off in bortle 8

Worsel
 

Dale

Great image!  Thanks for sharing!

Bryan


Re: Guide rate always being set to 1.

thefamily90 Phillips
 

When doing Lunar and Planetary images, and the scope is not perfectly aligned, the 0.5 X works wonders keeping the planet, crater, etc in the middle of the screen while capturing an AVI. So, 0.5x is not outdated for lunar and planetary imaging. I can’t speak to Deep Sky time lapse imaging.

Jim


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Worsel via groups.io <bryancashion@...>
Sent: Friday, November 13, 2020 7:22:25 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Guide rate always being set to 1.
 
Tom

Here is the logic.

At 0.5 x sidereal guide rates, any given correction takes twice as long as 1x.  Hence, stars will not be as sharp.  As Woody noted, computer guiding algorithms have no problem 'watching' the guide star at 1x sidereal and making a corrective move in fractions of a second.  A human doing manual guiding will almost certainly overshoot / undershoot; resulting in smeared stars.  Hence, the now out-dated suggestion of 0.5x..

Bryan


Re: Yet Another M31: knocking the rust off in bortle 8

Bill Long
 

Nice job!


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Dale Ghent <daleg@...>
Sent: Friday, November 13, 2020 10:08 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Cc: main@ap-ug.groups.io <main@ap-ug.groups.io>
Subject: [ap-gto] Yet Another M31: knocking the rust off in bortle 8
 
After a summer of little time for astrophotography and my main imaging rig undergoing a near total reconfiguration to accommodate a QHY600, I finally was able to get a few sessions in over the month of October and break in the new system. I haven't seriously imaged broadband before because I live under lusciously gray bortle 8 skies in the jet stream-inflicted mid-Atlantic, and escaping this atmospheric morass means a few hours' drive in any of the cardinal directions... so I've just kind of stuck to narrowband. I'm actually pretty happy with the outcome of this little project, my first Ha+LRGB. I've since fixed some spacing and tilt and am working on some more targets as weather allows.

https://eur05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astrobin.com%2Ffull%2Fhrq1cy%2F0%2F&amp;data=04%7C01%7C%7C8c4b26f442054ccf7cbe08d887ff191f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637408876986187082%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=52g0dY%2Fpd9ln3bpO8AIj5PKI6jwcidVjYxuPp%2FhDckw%3D&amp;reserved=0

Details in the tech card, etc.

/dale





Re: Yet Another M31: knocking the rust off in bortle 8

Don Anderson
 

Very well done Dale! You should be pleased with that one. Gives me incentive to try LRGB in my Bortle 8 skies!

Don Anderson


On Friday, November 13, 2020, 11:08:17 a.m. MST, Dale Ghent <daleg@...> wrote:


After a summer of little time for astrophotography and my main imaging rig undergoing a near total reconfiguration to accommodate a QHY600, I finally was able to get a few sessions in over the month of October and break in the new system. I haven't seriously imaged broadband before because I live under lusciously gray bortle 8 skies in the jet stream-inflicted mid-Atlantic, and escaping this atmospheric morass means a few hours' drive in any of the cardinal directions... so I've just kind of stuck to narrowband. I'm actually pretty happy with the outcome of this little project, my first Ha+LRGB. I've since fixed some spacing and tilt and am working on some more targets as weather allows.


Details in the tech card, etc.

/dale




Re: Guide rate always being set to 1.

Worsel
 

Tom

Here is the logic.

At 0.5 x sidereal guide rates, any given correction takes twice as long as 1x.  Hence, stars will not be as sharp.  As Woody noted, computer guiding algorithms have no problem 'watching' the guide star at 1x sidereal and making a corrective move in fractions of a second.  A human doing manual guiding will almost certainly overshoot / undershoot; resulting in smeared stars.  Hence, the now out-dated suggestion of 0.5x..

Bryan


Re: best power schema for nomad set up

Roland Christen
 

Anything from 11.5 to 24 volts will work fine. Below 18 volts the max slew rate is limited to 1200x.

Rolando



-----Original Message-----
From: Andrea Lucchetti <andlucchett@...>
To: main@ap-gto.groups.io
Sent: Fri, Nov 13, 2020 2:35 pm
Subject: Re: [ap-gto] best power schema for nomad set up

Following the suggestion,
I am going to use the battery to power my MAch2.

I assume that 13.8v or even 14.2 when charged 100% is perfectly fine given that it can be run also at 24V.

can someone please confirm this?
Thank you
Andrea


Re: [ap-ug] Yet Another M31: knocking the rust off in bortle 8

Roland Christen
 

That's extremely nice.

Rolando


-----Original Message-----
From: Dale Ghent <daleg@...>
To: main@ap-gto.groups.io
Cc: main@ap-ug.groups.io
Sent: Fri, Nov 13, 2020 12:08 pm
Subject: [ap-ug] Yet Another M31: knocking the rust off in bortle 8

After a summer of little time for astrophotography and my main imaging rig undergoing a near total reconfiguration to accommodate a QHY600, I finally was able to get a few sessions in over the month of October and break in the new system. I haven't seriously imaged broadband before because I live under lusciously gray bortle 8 skies in the jet stream-inflicted mid-Atlantic, and escaping this atmospheric morass means a few hours' drive in any of the cardinal directions... so I've just kind of stuck to narrowband. I'm actually pretty happy with the outcome of this little project, my first Ha+LRGB. I've since fixed some spacing and tilt and am working on some more targets as weather allows.


Details in the tech card, etc.

/dale




Re: Guide rate always being set to 1.

Roland Christen
 

Guide rates for AP mounts should always be set at 1x sidereal.

Roland Christen
Astro-Physics



-----Original Message-----
From: Tom Blahovici <tom.va2fsq@...>
To: main@ap-gto.groups.io
Sent: Thu, Nov 12, 2020 10:43 pm
Subject: [ap-gto] Guide rate always being set to 1.

Hi,
I have the CP4 and have set the guide rate to 0.5x. It is set this way in each Ascom driver as well.  I am using APCC standard.
I understand that I should use a guide rate of 0.5x.  However, every time I start up PHD 2, it sets it to 1x.  I have changed all the settings I can find in PHD to 0.5x but it still changes it.
Any suggestions?
Thanks, Tom


Re: best power schema for nomad set up

Andrea Lucchetti
 

Following the suggestion,
I am going to use the battery to power my MAch2.

I assume that 13.8v or even 14.2 when charged 100% is perfectly fine given that it can be run also at 24V.

can someone please confirm this?
Thank you
Andrea


Re: [ap-ug] Yet Another M31: knocking the rust off in bortle 8

Pete Lardizabal
 

Very nice rendering Dale. Amazing image given the sky conditions! Wonderful to see the imagers employing capable methods and equipped to overcome dismal lighting challenges.

😎

Pete

On Nov 13, 2020, at 1:10 PM, Dale Ghent <daleg@elemental.org> wrote:

After a summer of little time for astrophotography and my main imaging rig undergoing a near total reconfiguration to accommodate a QHY600, I finally was able to get a few sessions in over the month of October and break in the new system. I haven't seriously imaged broadband before because I live under lusciously gray bortle 8 skies in the jet stream-inflicted mid-Atlantic, and escaping this atmospheric morass means a few hours' drive in any of the cardinal directions... so I've just kind of stuck to narrowband. I'm actually pretty happy with the outcome of this little project, my first Ha+LRGB. I've since fixed some spacing and tilt and am working on some more targets as weather allows.

https://www.astrobin.com/full/hrq1cy/0/

Details in the tech card, etc.

/dale




Re: Yet Another M31: knocking the rust off in bortle 8

Eduardo Oliveira
 

It came out really well!! Congrats!!

Eduardo Oliveira

Em sex., 13 de nov. de 2020 às 15:22, Karen Christen <karen@...> escreveu:

Being a fan of galaxy images, I always enjoy M31.  This is really pretty, Dale.  'Twas worth your effort.
Karen
AP


-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Dale Ghent
Sent: Friday, November 13, 2020 12:08 PM
To: main@ap-gto.groups.io
Cc: main@ap-ug.groups.io
Subject: [ap-gto] Yet Another M31: knocking the rust off in bortle 8

After a summer of little time for astrophotography and my main imaging rig undergoing a near total reconfiguration to accommodate a QHY600, I finally was able to get a few sessions in over the month of October and break in the new system. I haven't seriously imaged broadband before because I live under lusciously gray bortle 8 skies in the jet stream-inflicted mid-Atlantic, and escaping this atmospheric morass means a few hours' drive in any of the cardinal directions... so I've just kind of stuck to narrowband. I'm actually pretty happy with the outcome of this little project, my first Ha+LRGB. I've since fixed some spacing and tilt and am working on some more targets as weather allows.

https://www.astrobin.com/full/hrq1cy/0/

Details in the tech card, etc.

/dale






--
Karen Christen
Astro-Physics






Re: Yet Another M31: knocking the rust off in bortle 8

Karen Christen
 

Being a fan of galaxy images, I always enjoy M31. This is really pretty, Dale. 'Twas worth your effort.
Karen
AP

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Dale Ghent
Sent: Friday, November 13, 2020 12:08 PM
To: main@ap-gto.groups.io
Cc: main@ap-ug.groups.io
Subject: [ap-gto] Yet Another M31: knocking the rust off in bortle 8

After a summer of little time for astrophotography and my main imaging rig undergoing a near total reconfiguration to accommodate a QHY600, I finally was able to get a few sessions in over the month of October and break in the new system. I haven't seriously imaged broadband before because I live under lusciously gray bortle 8 skies in the jet stream-inflicted mid-Atlantic, and escaping this atmospheric morass means a few hours' drive in any of the cardinal directions... so I've just kind of stuck to narrowband. I'm actually pretty happy with the outcome of this little project, my first Ha+LRGB. I've since fixed some spacing and tilt and am working on some more targets as weather allows.

https://www.astrobin.com/full/hrq1cy/0/

Details in the tech card, etc.

/dale






--
Karen Christen
Astro-Physics


Yet Another M31: knocking the rust off in bortle 8

Dale Ghent
 

After a summer of little time for astrophotography and my main imaging rig undergoing a near total reconfiguration to accommodate a QHY600, I finally was able to get a few sessions in over the month of October and break in the new system. I haven't seriously imaged broadband before because I live under lusciously gray bortle 8 skies in the jet stream-inflicted mid-Atlantic, and escaping this atmospheric morass means a few hours' drive in any of the cardinal directions... so I've just kind of stuck to narrowband. I'm actually pretty happy with the outcome of this little project, my first Ha+LRGB. I've since fixed some spacing and tilt and am working on some more targets as weather allows.

https://www.astrobin.com/full/hrq1cy/0/

Details in the tech card, etc.

/dale

5501 - 5520 of 79681