Date   

Re: Comet Neowise

Eric Claeys
 

Roland,
Nice picture of the comet.  Are the light streaks at about a 45 degree angle stars?
Eric


Re: [ap-ug] Comet Neowise

Richard Crisp
 

They keep getting better

I like that the best of all I’ve seen thusfar 

“Corrected” by my iPhone

On Jul 23, 2020, at 7:32 PM, Roland Christen via groups.io <chris1011@...> wrote:


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

Imaged with the 160EDF refractor on the Mach2 mount. The comet head was tracked using the Keypad Drift Model. I took one data point on the comet's nucleus (a 4 minute drift measurement), then turned on the Model to begin tracking the comet. I took a total of 40 images of 30 sec each thru LRGB filters over a period of about 1/2 hour until the comet dropped below my observatory walls. The background stars moved approximately 1/2 way across the frame during that time while the comet stayed stationary on the chip. Seeing was good but transparency was unfortunately poor with thin high clouds.

Tracking comets can be done two ways, with APCC Horizons and now with the keypad custom model. Using Horizons with emphemeris data takes a bit of doing, and is suited for permanent setups. The keypad drift model is very quick and quite accurate and can be done in a field setup in just minutes.

Roland


Re: M20 First light with ZWO ASI2600

Robert Chozick <rchozick@...>
 

Thanks Ecki. 


On Jul 24, 2020, at 6:12 AM, eckhard.voelcker via groups.io <eckhard.voelcker@...> wrote:

Nice image with lots of detail, Robert.

Ecki


Re: Comet Neowise

DFisch
 

Brilliant Andrea and thanks so much for that  “breadcrumb” trail, the option “save data for later use” escaped me, now back on track, Glad you were enjoying your new Mach2! Thanks again, Tom

On Fri, Jul 24, 2020 at 07:25 Andrea Lucchetti <andlucchett@...> wrote:
Tom, I can't check here but it is something I realized while imaging.

First you connect to the NASA site and set the query as illustrated in the manual.
Of course you need to select the right object AND the right observing location (this is the point I missed).
In this regard, the explanatory text in the Horizon application could be more precise.
You also set the time window to cover the days you need.
After running the calculations, you copy/paste in Horizon panel and the Ephemeris values get populated.

From now you have different options in the lower right end part of the application:
you can test the tracking, track the target, or save the data for a later use.
In this way you can prepare everything ahead of time and using it later even without a connection.
I haven't really tried this because I was already there, but I am pretty sure it works.

PS: if you get the message: impossible to track because object is below the horizon, just check your location is not Mars or other funny place :-)

Andrea

Il giorno ven 24 lug 2020 alle ore 13:03 DFisch <manusfisch@...> ha scritto:
Andrea as a neophyte I would love to hear more of your prelim “tracking plan” workflow. Tom Fischer, INdy

On Fri, Jul 24, 2020 at 06:51 Andrea Lucchetti <andlucchett@...> wrote:
Great image.
APCC/ Horizons is not that complex to use in a field set up, in my opinion.
I have been able to use it last week with my mach2, and it was the first time I powered up the mount :-)

You do need to be keen on setting parameters, I have spent  half an hour because I didn't update the location in the NASA website.
this is something that we can do in advance of the session, because the "tracking plan "can be saved". 
 
So I think we just have two methods also for field use, and it is great!
Andrea

--
TJF MOBILE

--
TJF MOBILE


Re: Comet Neowise

Andrea Lucchetti
 

Tom, I can't check here but it is something I realized while imaging.

First you connect to the NASA site and set the query as illustrated in the manual.
Of course you need to select the right object AND the right observing location (this is the point I missed).
In this regard, the explanatory text in the Horizon application could be more precise.
You also set the time window to cover the days you need.
After running the calculations, you copy/paste in Horizon panel and the Ephemeris values get populated.

From now you have different options in the lower right end part of the application:
you can test the tracking, track the target, or save the data for a later use.
In this way you can prepare everything ahead of time and using it later even without a connection.
I haven't really tried this because I was already there, but I am pretty sure it works.

PS: if you get the message: impossible to track because object is below the horizon, just check your location is not Mars or other funny place :-)

Andrea

Il giorno ven 24 lug 2020 alle ore 13:03 DFisch <manusfisch@...> ha scritto:
Andrea as a neophyte I would love to hear more of your prelim “tracking plan” workflow. Tom Fischer, INdy

On Fri, Jul 24, 2020 at 06:51 Andrea Lucchetti <andlucchett@...> wrote:
Great image.
APCC/ Horizons is not that complex to use in a field set up, in my opinion.
I have been able to use it last week with my mach2, and it was the first time I powered up the mount :-)

You do need to be keen on setting parameters, I have spent  half an hour because I didn't update the location in the NASA website.
this is something that we can do in advance of the session, because the "tracking plan "can be saved". 
 
So I think we just have two methods also for field use, and it is great!
Andrea

--
TJF MOBILE


Re: M20 First light with ZWO ASI2600

eckhard.voelcker@...
 

Nice image with lots of detail, Robert.

Ecki


Re: Comet Neowise

DFisch
 

Andrea as a neophyte I would love to hear more of your prelim “tracking plan” workflow. Tom Fischer, INdy

On Fri, Jul 24, 2020 at 06:51 Andrea Lucchetti <andlucchett@...> wrote:
Great image.
APCC/ Horizons is not that complex to use in a field set up, in my opinion.
I have been able to use it last week with my mach2, and it was the first time I powered up the mount :-)

You do need to be keen on setting parameters, I have spent  half an hour because I didn't update the location in the NASA website.
this is something that we can do in advance of the session, because the "tracking plan "can be saved". 
 
So I think we just have two methods also for field use, and it is great!
Andrea

--
TJF MOBILE


Re: Comet Neowise

Andrea Lucchetti
 

Great image.
APCC/ Horizons is not that complex to use in a field set up, in my opinion.
I have been able to use it last week with my mach2, and it was the first time I powered up the mount :-)

You do need to be keen on setting parameters, I have spent  half an hour because I didn't update the location in the NASA website.
this is something that we can do in advance of the session, because the "tracking plan "can be saved". 
 
So I think we just have two methods also for field use, and it is great!
Andrea


Re: Comet Neowise

Chris Carlton
 

A remarkable image indeed! Perhaps Roland can use his maths skills to calculate the width of the small outgassing core at the approx. distance of 100ish million miles distance from us. Should be possible to figure out with the known image scale. 

--

Chris Carlton, Ph. D.

Director, Carlton Astronomy Campus

Professor of Entomology, Emeritus

Department of Entomology, Louisiana State University

Baton Rouge, LA USA 70808

<a href=http://www.cleardarksky.com/c/CrAstCmpMSkey.html>


Re: Comet Neowise

Stuart <stuart.j.heggie@...>
 

Simply amazing!!!


On Thu, 23 Jul 2020 at 22:32, uncarollo2 <chris1011@...> via groups.io <chris1011=aol.com@groups.io> wrote:

Imaged with the 160EDF refractor on the Mach2 mount. The comet head was tracked using the Keypad Drift Model. I took one data point on the comet's nucleus (a 4 minute drift measurement), then turned on the Model to begin tracking the comet. I took a total of 40 images of 30 sec each thru LRGB filters over a period of about 1/2 hour until the comet dropped below my observatory walls. The background stars moved approximately 1/2 way across the frame during that time while the comet stayed stationary on the chip. Seeing was good but transparency was unfortunately poor with thin high clouds.

Tracking comets can be done two ways, with APCC Horizons and now with the keypad custom model. Using Horizons with emphemeris data takes a bit of doing, and is suited for permanent setups. The keypad drift model is very quick and quite accurate and can be done in a field setup in just minutes.

Roland


--

Stuart
http://www.astrofoto.ca/stuartheggie/


Re: [ap-ug] Comet Neowise

marc walk
 

That is an amazing image! The most detailed i’ve seen!

Marc Walk


On Jul 23, 2020, at 9:32 PM, Roland Christen via groups.io <chris1011@...> wrote:


Imaged with the 160EDF refractor on the Mach2 mount. The comet head was tracked using the Keypad Drift Model. I took one data point on the comet's nucleus (a 4 minute drift measurement), then turned on the Model to begin tracking the comet. I took a total of 40 images of 30 sec each thru LRGB filters over a period of about 1/2 hour until the comet dropped below my observatory walls. The background stars moved approximately 1/2 way across the frame during that time while the comet stayed stationary on the chip. Seeing was good but transparency was unfortunately poor with thin high clouds.

Tracking comets can be done two ways, with APCC Horizons and now with the keypad custom model. Using Horizons with emphemeris data takes a bit of doing, and is suited for permanent setups. The keypad drift model is very quick and quite accurate and can be done in a field setup in just minutes.

Roland








Comet Neowise

Roland Christen
 

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

Imaged with the 160EDF refractor on the Mach2 mount. The comet head was tracked using the Keypad Drift Model. I took one data point on the comet's nucleus (a 4 minute drift measurement), then turned on the Model to begin tracking the comet. I took a total of 40 images of 30 sec each thru LRGB filters over a period of about 1/2 hour until the comet dropped below my observatory walls. The background stars moved approximately 1/2 way across the frame during that time while the comet stayed stationary on the chip. Seeing was good but transparency was unfortunately poor with thin high clouds.

Tracking comets can be done two ways, with APCC Horizons and now with the keypad custom model. Using Horizons with emphemeris data takes a bit of doing, and is suited for permanent setups. The keypad drift model is very quick and quite accurate and can be done in a field setup in just minutes.

Roland


Re: ASCOM 6.5 released, upgrade or not?

Luca Marinelli
 

Pierre is right. I updated the ZWO ASCOM driver when I loaded software on a new computer in May 2020 but it appears that ZWO, wisely, went back to ASCOM 6.4 a couple of weeks later. I will simply update the ZWO ASCOM driver and roll back to ASCOM 6.4 to ensure compatibility with APPM. Thank you both to Pierre and Ray for the quick responses.

--Luca


On Thu, Jul 23, 2020 at 11:35 AM, Pierre Henrotay wrote:
Could you please check?
The ZWO downloads for ascom is 1.0.4.3 dated June 29.
The change log mentions a rollback to 6. 4.
The Ascom platform referenced is 6.4 also. 

Pierre


Re: MACH1 GTO Merdian Flip #Keypad

Ken Murfitt
 

Ah, terrific. I had read the meridian delay instructions quite carefully in the GTOCP4 and Keypad manuals, and how it was achieved internally and surmised that probably it was something overriding the keypad meridian delay feature. I always feel like I am pushing my luck when using the Keypad on top of whatever other software might be communicating with the mount - I can work with that if I know where the use-case boundaries are. Thanks!


Re: MACH1 GTO Merdian Flip #Keypad

Roland Christen
 

Whenever the keypad is set to EXT mode, it is advisable to always use the external app to control the mount, and that includes setting Meridian delay. In EXT you are initializing the mount via an external app and should always use that app for any setup commands, NOT the keypad. Don't use the keypad for anything other than moving around via the buttons or sending the mount to a star or object from the keypad Objects menu.

When you use EXT mode, you are defining the external app to be the main controlling element, and the keypad is then secondary.

Rolando



-----Original Message-----
From: Howard Hedlund <howard@...>
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Sent: Thu, Jul 23, 2020 2:36 pm
Subject: Re: [ap-gto] MACH1 GTO Merdian Flip #Keypad

Hi Ken,
 
I’m pretty sure I know exactly what is wrong.  The keypad performs the meridian delay by “fooling” the clock in the GTOCPx control box.   The driver is probably undoing the keypad’s clock fooling commands. 
 
There are two solutions.  Each will work, but I don’t advise mixing them.  Choose one and use that method exclusively.
 
1.       In the driver, Uncheck the boxes to “…keep mount time synced to PC time (recommended)”  That may not be a perfect quote.  Then you can do meridian delay with the keypad.  Just be sure to undo it with the keypad as well.
2.       Set meridian delay in the driver instead of the keypad.  You can then still use the keypad for your GoTo.
 
The next major keypad version will use the same method as the driver for meridian delay, so the problem will go away.
 
Mag. 7 Skies!
 
Howard Hedlund
Astro-Physics, Inc.
Phone: 815-315-7015
Please include this e-mail with your response.
 
P Consider the environment before printing this e-mail.
 
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ken Murfitt
Sent: Thursday, July 23, 2020 13:06
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] MACH1 GTO Merdian Flip #Keypad
 
I shall check those things the next time I am out, thanks.


Re: MACH1 GTO Merdian Flip #Keypad

Luke Leege
 

Any idea when the keypad revision will be available to the masses? 3-6 months?
Thanks, in advance,
Luke


Re: MACH1 GTO Merdian Flip #Keypad

Howard Hedlund
 

Hi Ken,

 

I’m pretty sure I know exactly what is wrong.  The keypad performs the meridian delay by “fooling” the clock in the GTOCPx control box.   The driver is probably undoing the keypad’s clock fooling commands. 

 

There are two solutions.  Each will work, but I don’t advise mixing them.  Choose one and use that method exclusively.

 

1.       In the driver, Uncheck the boxes to “…keep mount time synced to PC time (recommended)”  That may not be a perfect quote.  Then you can do meridian delay with the keypad.  Just be sure to undo it with the keypad as well.

2.       Set meridian delay in the driver instead of the keypad.  You can then still use the keypad for your GoTo.

 

The next major keypad version will use the same method as the driver for meridian delay, so the problem will go away.

 

Mag. 7 Skies!

 

Howard Hedlund

Astro-Physics, Inc.

Phone: 815-315-7015

www.astro-physics.com

Please include this e-mail with your response.

 

P Consider the environment before printing this e-mail.

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Ken Murfitt
Sent: Thursday, July 23, 2020 13:06
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] MACH1 GTO Merdian Flip #Keypad

 

I shall check those things the next time I am out, thanks.


Re: MACH1 GTO Merdian Flip #Keypad

Ken Murfitt
 

I shall check those things the next time I am out, thanks.


Re: MACH1 GTO Merdian Flip #Keypad

Roland Christen
 

Meridian delay does not perform a meridian flip. Those are two different things. Normally the mount will continue to track past the meridian (overhead point) until you send a GoTo. Then it will flip sides. The mount can also be set up to stop tracking at the meridian by setting the limits.

If the mount does not flip when you issue a GoTo after it has passed the meridian, then it is highly likely that the clock time is set wrong. The meridian is calculated from your local time/date/location. In the keypad main Menu pressing 4 = Time/LST will bring up your local time and LST which is the calculated Meridian Right Ascension value. (LST = Local Sidereal Time). That RA value is the point where the mount will flip sides when a GoTo is issued. So, that is a check on the operation of the mount that you need to be familiar with. Simply compare the calculated value and compare it to where your planetarium program says the meridian is. Also check the local clock time to make sure it is not set to the wrong value. Clock time is shown as military time (example 1pm = 1300 hours).

Rolando



-----Original Message-----
From: Ken M <kmurfitt@...>
To: main@ap-gto.groups.io
Sent: Thu, Jul 23, 2020 12:20 pm
Subject: [ap-gto] MACH1 GTO Merdian Flip #Keypad

Hello!

While imaging the Crescent Nebula a few nights back, I rang into a snag when attempting a meridian flip from the Keypad.
 
I tried to perform a meridian flip from the Keypad by setting RA/DEC/REV -> Meridian 2E, 1E, 0W, 1W, 2W in that order. Each time I attempted to
"re-go to" the Crescent nebula but the mount would not perform a merdian flip.
 
The scope was almost upright on the West side - well within the hour of passing the meridian.
 
I used the Tour -> Common Object Names to select the Crescent nebula. I later tried selecting NGC 6888 directly but the mount would not flip.
 
The Keypad Mount Type is set to MACH1.
 
Auto-Connect is set to EXT - my setup connects with Stellarium.
 
All other operations between the keypad, Stellarium, PHD2 and the mount seemed to be working fine.

The Keypad is relatively new (2018 model - firmware rev 4.19.3) and so I don't suspect the battery is the problem - I get no 'symptoms' of low battery ("object below horizon" etc).

Any thoughts on how to achieve a meridian flip from the Keypad please? Should I have set something from the Astro-Physics driver instead?
 
Eventually I slewed the mount manually to perform the "flip".
 
Thanks for any pointers.


MACH1 GTO Merdian Flip #Keypad

Ken Murfitt
 

Hello!

While imaging the Crescent Nebula a few nights back, I rang into a snag when attempting a meridian flip from the Keypad.
 
I tried to perform a meridian flip from the Keypad by setting RA/DEC/REV -> Meridian 2E, 1E, 0W, 1W, 2W in that order. Each time I attempted to
"re-go to" the Crescent nebula but the mount would not perform a merdian flip.
 
The scope was almost upright on the West side - well within the hour of passing the meridian.
 
I used the Tour -> Common Object Names to select the Crescent nebula. I later tried selecting NGC 6888 directly but the mount would not flip.
 
The Keypad Mount Type is set to MACH1.
 
Auto-Connect is set to EXT - my setup connects with Stellarium.
 
All other operations between the keypad, Stellarium, PHD2 and the mount seemed to be working fine.

The Keypad is relatively new (2018 model - firmware rev 4.19.3) and so I don't suspect the battery is the problem - I get no 'symptoms' of low battery ("object below horizon" etc).

Any thoughts on how to achieve a meridian flip from the Keypad please? Should I have set something from the Astro-Physics driver instead?
 
Eventually I slewed the mount manually to perform the "flip".
 
Thanks for any pointers.

14521 - 14540 of 86404