Date   

Re: Mach 1 PEC enablement via iOS

Roland Christen
 


Alternatively, once pec is enabled does it stay enabled after power is cycled or is the state stored in non-volatile memory?
The PE curve remains in NVM and is always played back unless your specific application sends a command to turn it off (for instance, the keypad can be set to always turn it on at startup). If you do a new PEMPro run, the original curve can be saved by uploading it and storing it to your laptop, but once you load the new curve into the mount servo, the old curve will be erased and replaced by the new one.

Rolando


-----Original Message-----
From: kirthgersenwall@... [ap-gto]
To: ap-gto
Sent: Tue, Aug 7, 2018 10:58 pm
Subject: [ap-gto] Re: Mach 1 PEC enablement via iOS

Hello

I too am interested in the broad topic of iOS control from the perspective of standalone portable imaging.

I've read that the Luminos app can command AP mounts to traverse to any of their park positions, which may indicate a better level of base support.

Per the GTOCP4 manual, periodic error correction apparently defaults to off; the manual mentions APCC, the keypad and ASCOM can enable it, presumably defaulting to the factory installed curve for a new mount.

Are there any iPhone/pad options to do this? Alternatively, once pec is enabled does it stay enabled after power is cycled or is the state stored in non-volatile memory?

Thanks
Derek


------------------------------------
Posted by: kirthgersenwall@...
------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list
see http://groups.yahoo.com/group/ap-gto
------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ap-gto/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/ap-gto/join
(Yahoo! ID required)

<*> To change settings via email:
ap-gto-digest@...
ap-gto-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
ap-gto-unsubscribe@...

<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/


Re: Help! AP1200 issues at remote observatory

Dhaval
 

Hi Ray - 

To answer your question about back up - APCC settings were restored from the APCC's backup directory, so I did not loose my settings - they were very much restored.

I can try re-creating a pointing model and see if things will be back to normal, however, at this point, with me being 300 miles away, I am very hesitant to do anything. Maybe, I will have to have my observatory manager be around when I run the pointing model.

I will ask the observatory manager to ensure the clutches locked, however, the fact that I was able to image one of the nights after the initial snafu tells me that everything else should be fine - but it does not hurt to recheck. 

Thanks,
Dhaval


Re: Help! AP1200 issues at remote observatory

Ray Gralak
 

Hi Dhaval,

A few nights ago, I had what I was told a catastrophic
failure of my PC.
First, I'm sorry to hear that your PC died.

All this while, APCC had lost all my setting information,
however, I was able to get that from a backed up version
and reload it again.
Unless the hard disk died you didn't lose your settings information, as APCC creates a backup of settings every time you start it.

Do you know if APCC's settings were restored from a system backup, or from APCC's settings backup directory? The latter would have the freshest settings information. If the settings were from the former you might want to see if you can get the settings off of the crashed computer's hard disk if that is possible.

I guess, I am at a loss, I am not sure what is going on and
how to ensure I fix it.
From what you said it's hard to say what's wrong. It could be that the settings you restored don't have a pointing model, or the model is not accurate. In that case maybe a new pointing model needs to be created.

I had to call my observatory manager and ask him to put the
mount in Park 3 position manually - which he did
Also, maybe have the clutches checked to make sure the scope is not slipping after having been moved manually to the Park 3 location.

Best regards,

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Tuesday, August 7, 2018 9:25 PM
To: ap-gto@...
Subject: [ap-gto] Help! AP1200 issues at remote observatory



Hello all,

I am not sure how to best describe what's going on, so please bear with me.




A few nights ago, I had what I was told a catastrophic failure of my PC. Essentially, just about the time when I
turned on APCC Pro, the computer somehow lost power - I am still trying to figure how why that happened - but
that is besides the point right now.




As a result of that power loss, something happened and I lost all settings in APCC and the mount, when the PC
restarted, was lost. At this point, I had to call my observatory manager and ask him to put the mount in Park 3
position manually - which he did (I could confirm that because I was watching on the IP camera in the
observatory). I tried to RCAL the mount, but it kept telling me that the mount was way off and I could not RCAL.
As a result, I got the RA/DEC of where the mount was pointing and SYNC' d to that position (through APCC) and
then parked it in Park 3 position. Everything was OK at this point. After that, I slewed the mount to M101 and it
slewed there fine, I centered on M101 via plate solving and it was near perfect. I was able to image through the
rest of the night on a couple of targets and it was working fine.




All this while, APCC had lost all my setting information, however, I was able to get that from a backed up version
and reload it again.




Tonight, I again had M101 to image, which it started doing. At the end of the M101 sequence, I had planned on
imaging NGC6960 - however, it did not slew to NGC6960 and I believe it hit the horizon limit and stopped tracking
(at least I am hoping that is what happened). I am not sure if the scope hit the pier - looking through the
observatory camera, everything looks OK - however, until I get a first hand report from my observatory manager
tomorrow morni ng, I won't be sure.




When I park the mount to Park 3 - it "seems" to park OK - although I do not think it is true Park 3 (pretty close, but
not quite Park 3).




I guess, I am at a loss, I am not sure what is going on and how to ensure I fix it.




Any help will be greatly appreciated.


Thanks,
Dhaval


Help! AP1200 issues at remote observatory

Dhaval
 

Hello all,

I am not sure how to best describe what's going on, so please bear with me. 


A few nights ago, I had what I was told a catastrophic failure of my PC. Essentially, just about the time when I turned on APCC Pro, the computer somehow lost power - I am still trying to figure how why that happened - but that is besides the point right now. 


As a result of that power loss, something happened and I lost all settings in APCC and the mount, when the PC restarted, was lost. At this point, I had to call my observatory manager and ask him to put the mount in Park 3 position manually - which he did (I could confirm that because I was watching on the IP camera in the observatory). I tried to RCAL the mount, but it kept telling me that the mount was way off and I could not RCAL. As a result, I got the RA/DEC of where the mount was pointing and SYNC'd to that position (through APCC) and then parked it in Park 3 position. Everything was OK at this point. After that, I slewed the mount to M101 and it slewed there fine, I centered on M101 via plate solving and it was near perfect. I was able to image through the rest of the night on a couple of targets and it was working fine.


All this while, APCC had lost all my setting information, however, I was able to get that from a backed up version and reload it again.


Tonight, I again had M101 to image, which it started doing. At the end of the M101 sequence, I had planned on imaging NGC6960 - however, it did not slew to NGC6960 and I believe it hit the horizon limit and stopped tracking (at least I am hoping that is what happened). I am not sure if the scope hit the pier - looking through the observatory camera, everything looks OK - however, until I get a first hand report from my observatory manager tomorrow morning, I won't be sure. 


When I park the mount to Park 3 - it "seems" to park OK - although I do not think it is true Park 3 (pretty close, but not quite Park 3). 


I guess, I am at a loss, I am not sure what is going on and how to ensure I fix it. 


Any help will be greatly appreciated.


Thanks,
Dhaval


Re: APPM tracking error

Ray Gralak
 

Hi Craig,

In the past I have not been able to get APPM to accurately point > or track, even with models up to 200 points,
I think Howard has contacted via private email about what you should try, but I wanted to say that APPM just collects the data points. The modeling, including pointing corrections and tracking rate corrections are not done by APPM, but by APCC Pro.

Best regards,

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Tuesday, August 7, 2018 10:39 AM
To: ap-gto@...
Subject: [ap-gto] APPM tracking error



Setup:

AP1600GTOAE
F/W: VCP4-P01-10
APCC Pro version: V1.6.0.3
V2 ASCOM driver: V5.10.02
Maxim DL version: 6.17
plate scale: 0.57"/pixel
Location: southern hemisphere (New Zealand)

In the past I have not been able to get APPM to accurately point or track, even with models up to 200 points, so I
gave up and used a guide camera. But recently the guide camera failed so I learned how to use the RA and DEC
correction rates in the V2 driver to carefully offset tracking errors. This has worked very well the last few weeks
but does require updating the correction rates every 15 minutes or so, probably due to changes in refraction and
the alignment of the system. For example, if the star drifted to the left in the image I knew I had to increase
numerically the DEC correction rate in the V2 driver.


Last night I per formed a 110 point model over both hemispheres (55 points in each hemisphere). I then enabled
APPM pointing and tracking correction. Selecting a random star, APPM displayed the tracking correction:

APPM correction: RA 1.23 sec/hr, DEC 38.3 arc-sec/hr

After a few minutes the star drifted noticeably in both DEC and RA, with the DEC drift much greater than the RA
drift. This hinted that the tracking error in both axis scaled with the APPM correction amounts above.

To see if the APPM corrections were being applied in the opposite direction I calculated V2 corrections:

V2 RA corr = -(APPM RA corr * 2) / 3600, V2 DEC corr = -(APPM DEC corr * 2) / 3600.


V2 RA corr = -(1.23 * 2) / 3600, V2 DEC corr = -(38.3 * 2) / 3600




V2 RA corr = -0.00068, V2 DEC corr = -0.02128




The reason for multiplying the APPM corr rate by 2 is because the V2 corr rate is numerically added to the APPM
corr rate, and since I needed to reverse the correction I needed X1 to cancel the correction and X2 to reverse the
correction.





I entered these two values into the V2 driver and after several minutes the star drift in RA was 0 but DEC was
much worse, which meant the sign was incorrect in DEC. So I changed the V2 settings:




V2 RA corr = -0.00068, V2 DEC corr = 0.02128 figuring the DEC directions were reversed




After several minutes tracking both RA and DEC drift were now 0. So it does appear the APPM corrections are
being applied in the wrong direction.




Looking back at my notes when using V2 correction I noticed that when pointing in this area of the sky I used:




V2 RA corr: -0.00050 and V2 DEC corr: 0.01000

converting this to APPM values:

APPM RA corr: -1.8 sec/hr, DEC corr: 36 arc-sec/hr

this matches fairly well with the above results. The APPM RA corr rate needs the opposite sign (- instead of + in
the tests above), and the APPM DEC corr rate needs to move the DEC axis in the opposite direction. In other
words, the APPM corr rate is displayed correctly but is applied in the wrong direction to the DEC motor.





There seems to be two possible explanations. First, since tracking and pointing are reasonably accurate without
APPM, implies the configuration of the mount is correct. In other words, the RA and DEC directions for the
southern hemisphere agree fairly well with the sky and the motors do indeed move in the correct direction. But
with APPM correction not working well for either pointing or tracking it would indicate that APPM corrections are
being applied in the opposite direction to the motors.




The other possibility is there is a configuration problem in APPM that does not correct for southern hemisphere
operation. If other telescopes operating with similar hardware and software are operating successfully in the
southern hemisphere with APPM then there must be a configuration problem on my end.




Any suggestions?




Craig





Re: Mach 1 SkySafari Tracking Rate

Derek K.
 

To correct/augment an earlier message of mine which has not yet appeared: A useful description (dated April '17) from AP, describing the control capabilities supported in Luminos and SkySafari
http://www.astro-physics.com/products/mounts/control/wi-fi-options.pdf


---In ap-gto@..., <george@...> wrote :

Chris,

 

Email me directly and I can give you the necessary command sequence.   SkySafari does not offer tracking speed changes (yet).

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-282-1513

Email:  george@...

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Tuesday, July 31, 2018 9:07 AM
To: ap-gto@...
Subject: [ap-gto] Mach 1 SkySafari Tracking Rate

 

 

I ran a search on the forum and didn't see this topic addressed so I thought I would post the question.  Just received my new Mach 1 (yay!) and have it talking to my Apple devices using SkySafari (6 plus).  So far so good.  However, I am puzzled as to how to adjust the tracking rate (Sidereal, Lunar, Solar, etc.).  Can I change this setting in SkySafari or do I need ASCOM to do that?  Is it intuitive in that it adjusts tracking speed to the object selected?

Thanks,

Chris


 


New file uploaded to ap-gto

ap-gto@...
 

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the ap-gto
group.

File : /Mach1 Guiding/Deep Sky with 130GTX and 1100 mount/Pelican1_8-6-2018.jpg
Uploaded by : uncarollo2 <chris1011@...>
Description : H-alpha image taken with 130GTX on 1100 mount under hazy skies

You can access this file at the URL:
https://groups.yahoo.com/neo/groups/ap-gto/files/Mach1%20Guiding/Deep%20Sky%20with%20130GTX%20and%201100%20mount/Pelican1_8-6-2018.jpg

To learn more about file sharing for your group, please visit:
https://help.yahoo.com/kb/index?page=content&y=PROD_GRPS&locale=en_US&id=SLN15398

Regards,

uncarollo2 <chris1011@...>


Re: Mach 1 PEC enablement via iOS

Derek K.
 

Hello

I too am interested in the broad topic of iOS control from the perspective of standalone portable imaging.

I've read that the Luminos app can command AP mounts to traverse to any of their park positions, which may indicate a better level of base support.

Per the GTOCP4 manual, periodic error correction apparently defaults to off; the manual mentions APCC, the keypad and ASCOM can enable it, presumably defaulting to the factory installed curve for a new mount.

Are there any iPhone/pad options to do this? Alternatively, once pec is enabled does it stay enabled after power is cycled or is the state stored in non-volatile memory?

Thanks
Derek


New file uploaded to ap-gto

ap-gto@...
 

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the ap-gto
group.

File : /Mach1 Guiding/Pelican1_8-6-2018.jpg
Uploaded by : uncarollo2 <chris1011@...>
Description : H-alpha Image of Pelican nebula taken over 2 nights with hazy skies

You can access this file at the URL:
https://groups.yahoo.com/neo/groups/ap-gto/files/Mach1%20Guiding/Pelican1_8-6-2018.jpg

To learn more about file sharing for your group, please visit:
https://help.yahoo.com/kb/index?page=content&y=PROD_GRPS&locale=en_US&id=SLN15398

Regards,

uncarollo2 <chris1011@...>


Re: APPM tracking error

Howard Hedlund
 

Hi Craig,

I don't want this to get confused with a bunch of answers from northern hemisphere users, so I'd like to take this off-group, if you don't mind.  I have something I'd like for you to try, and then we can get our results to Ray for his thoughts. 

Any other southern hemisphere users of APCC Pro, please feel free to chime in with your experiences and thoughts.  I know that some of you are having excellent results, but we don't really have a large pool of SH users from which we can learn. 

Thanks! 


APPM tracking error

Craig Young
 

Setup:

AP1600GTOAE
F/W: VCP4-P01-10
APCC Pro version: V1.6.0.3
V2 ASCOM driver: V5.10.02
Maxim DL version: 6.17
plate scale: 0.57"/pixel
Location: southern hemisphere (New Zealand)

In the past I have not been able to get APPM to accurately point or track, even with models up to 200 points,  so I gave up and used a guide camera.  But recently the guide camera failed so I learned how to use the RA and DEC correction rates in the V2 driver to carefully offset tracking errors.  This has worked very well the last few weeks but does require updating the correction rates every 15 minutes or so, probably due to changes in refraction and the alignment of the system.  For example, if the star drifted to the left in the image I knew I had to increase numerically the DEC correction rate in the V2 driver.

Last night I performed a 110 point model over both hemispheres (55 points in each hemisphere).  I then enabled APPM pointing and tracking correction.  Selecting a random star, APPM displayed the tracking correction:

APPM correction: RA 1.23 sec/hr, DEC 38.3 arc-sec/hr

After a few minutes the star drifted noticeably in both DEC and RA, with the DEC drift much greater than the RA drift.  This hinted that the tracking error in both axis scaled with the APPM correction amounts above.

To see if the APPM corrections were being applied in the opposite direction I calculated V2 corrections:

V2 RA corr = -(APPM RA corr * 2) / 3600, V2 DEC corr = -(APPM DEC corr * 2) / 3600.

V2 RA corr = -(1.23 * 2) / 3600, V2 DEC corr = -(38.3 * 2) / 3600


V2 RA corr = -0.00068, V2 DEC corr = -0.02128


The reason for multiplying the APPM corr rate by 2 is because the V2 corr rate is numerically added to the APPM corr rate, and since I needed to reverse the correction I needed X1 to cancel the correction and X2 to reverse the correction.


I entered these two values into the V2 driver and after several minutes the star drift in RA was 0 but DEC was much worse, which meant the sign was incorrect in DEC.  So I changed the V2 settings:


V2 RA corr = -0.00068, V2 DEC corr = 0.02128 figuring the DEC directions were reversed


After several minutes tracking both RA and DEC drift were now 0.  So it does appear the APPM corrections are being applied in the wrong direction.


Looking back at my notes when using V2 correction I noticed that when pointing in this area of the sky I used:


V2 RA corr: -0.00050 and V2 DEC corr: 0.01000

converting this to APPM values:

APPM RA corr: -1.8 sec/hr, DEC corr: 36 arc-sec/hr

this matches fairly well with the above results.  The APPM RA corr rate needs the opposite sign (- instead of + in the tests above), and the APPM DEC corr rate needs to move the DEC axis in the opposite direction.  In other words, the APPM corr rate is displayed correctly but is applied in the wrong direction to the DEC motor.


There seems to be two possible explanations.  First, since tracking and pointing are reasonably accurate without APPM, implies the configuration of the mount is correct.  In other words, the RA and DEC directions for the southern hemisphere agree fairly well with the sky and the motors do indeed move in the correct direction.  But with APPM correction not working well for either pointing or tracking it would indicate that APPM corrections are being applied in the opposite direction to the motors.


The other possibility is there is a configuration problem in APPM that does not correct for southern hemisphere operation.  If other telescopes operating with similar hardware and software are operating successfully in the southern hemisphere with APPM then there must be a configuration problem on my end.


Any suggestions?


Craig



Re: Mach 1 SkySafari Tracking Rate

George
 

Chris,

 

Email me directly and I can give you the necessary command sequence.   SkySafari does not offer tracking speed changes (yet).

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-282-1513

Email:  george@...

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Tuesday, July 31, 2018 9:07 AM
To: ap-gto@...
Subject: [ap-gto] Mach 1 SkySafari Tracking Rate

 

 

I ran a search on the forum and didn't see this topic addressed so I thought I would post the question.  Just received my new Mach 1 (yay!) and have it talking to my Apple devices using SkySafari (6 plus).  So far so good.  However, I am puzzled as to how to adjust the tracking rate (Sidereal, Lunar, Solar, etc.).  Can I change this setting in SkySafari or do I need ASCOM to do that?  Is it intuitive in that it adjusts tracking speed to the object selected?

Thanks,

Chris


Re: Mach 1 SkySafari Tracking Rate

Christopher Erickson
 

Sky Safari 5 does not let users change the tracking rate from sidereal.
 
Sky Safari 6 might add that feature... if the developers are pestered (or monetarily incentivized) enough to do it.
 
 
-Christopher Erickson
Observatory engineer
Summit Kinetics
Waikoloa, HI 96738
www.summitkinetics.com
 


From: ap-gto@... [mailto:ap-gto@...]
Sent: Tuesday, July 31, 2018 4:07 AM
To: ap-gto@...
Subject: [ap-gto] Mach 1 SkySafari Tracking Rate

I ran a search on the forum and didn't see this topic addressed so I thought I would post the question.  Just received my new Mach 1 (yay!) and have it talking to my Apple devices using SkySafari (6 plus).  So far so good.  However, I am puzzled as to how to adjust the tracking rate (Sidereal, Lunar, Solar, etc.).  Can I change this setting in SkySafari or do I need ASCOM to do that?  Is it intuitive in that it adjusts tracking speed to the object selected?

Thanks,

Chris


Virus-free. www.avg.com


Re: PEC Curve Analysis

Stephen Winston
 

Hi Jerry,

One quick comment on your data:  Your imaging pixel scale (6.3 arc-s pixel) is almost as big as the measured pk-pk PE (5.3 arc-seconds).  Or in other words, the PE was measured over less that 2 pixels.

What imaging train were you using to measure your PE?  If possible yo might want to use a longer focal length  instrument or different camera (smaller pixels) as it will probably give a more accurate measurement.

And to be clear:  I'm not saying your measurements are not accurate, but at that imaging scale it's hard to tell.

Steve


Re: PEC Curve Analysis

Roland Christen
 

This is not appropriate to post on this user group since nobody can give you any real information about your results. If you had sent it to Howard, George, myself or Ray Graylak, you would have had a crew of experts at your side to analyze your results.

Roland Christen
Astro-Physics Inc.



-----Original Message-----
From: astrojer@... [ap-gto]
To: ap-gto
Sent: Mon, Aug 6, 2018 8:37 pm
Subject: [ap-gto] PEC Curve Analysis



Ran new PEC data via PEMPRO for my Mach1GTO (SN M10505) after cleaning and lubing the worm and gears.

The results do not look like anything posted on the AP website and would appreciate any comments/observations people might have on the noted oscillations and if they are "OK" or indicative of some problem with the gear train.  The PEMPRO files are in the Files JERRY folder posted today 8/6.

Thanks,

Jerry Hulm




Re: Another APCC question

Ray Gralak
 

Hi Dale,

When I brought the CP3 back online with the new battery,
the driver
could not change the lat/long *at all* and the mount was stuck at > 0/0 for its lat/long:

http://i.imgur.com/eKA8Xqd.png
The driver should automatically initialize from RA=0 and Dec=90, but it doesn't look like that happened. Can you zip the driver logs
using the driver's Log Zipper utility and post the logs to the file section?

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Monday, August 6, 2018 9:14 AM
To: ap-gto@...
Subject: Re: [ap-gto] Another APCC question





On Aug 3, 2018, at 8:35 AM, 'Ray Gralak (Groups)' groups3@... [ap-gto] <ap-gto@...>
wrote:

In that regard, I agree that the AP V2 driver documentation and user feedback should be more clear. The only
place that you can
change Lat/Long is in the AP V2 setup dialog, which is usually run when the driver is not connected. And in the
help section for
"Initialization Setup" it states that most of the options (including "Set Latitude/Longitude") apply only when the
mount is
initialized. I think a more straight forward statement there is needed.

https://www.siriusimaging.com/apdriver/help/initialization_setup.htm
Yeah it essentially says that, but it could be clearer for sure.

However your thought about applying Lat/Long from a "known" parked position may be possible. I will talk this
over with Howard to
see if there is a "safe" way that this can be done.
If you two could make that happen, it would certainly push me (at least) over the edge on making the CP3 (Rev
O) -> CP4 jump. Due to living under a light dome and having poor sight lines to the sky around my house, I'm
stuck having to be mobile for any viewing/imaging except for solar. Between the different club sites or places I go
camping, any improvement in flexibility and ease regarding Location setup would be a big deal.

The subject must have released the gremlins, as just this past weekend I spent an hour trying to figure out a
location issue that my CP3/Mach1 started experiencing after I had to switch batteries, which of course meant the
mount had to be powered down momentarily. When I brought the CP3 back online with the new battery, the driver
could not change the lat/long *at all* and the mount was stuck at 0/0 for its lat/long:

http://i.imgur.com/eKA8Xqd.png

After an hour of repeatedly power-cylcing the CP3 and trying to get the driver to initialize the it with the right
lat/long for my site's preset, the problem persisted. Eventually, I gave up and dug out the hand controller, inputted
the site's lat/long into a location slot and was able to set it that way.

Thanks again for the feedback, Dale!
Thank you for looking into this!

/dale


RAPAS alignment on Cloudy Nights

Roland Christen
 

 On Cloudy:

https://www.cloudynights.com/topic/628491-initial-alignment-of-rapas/#entry8753318

"Does the AP polar app correct for refraction?"

No, of course not. The App simply tells the user where Polaris is with respect to the pole and allows him to place Polaris on the reticle at the proper position. This Polaris to Pole orientation and distance does not change anywhere on Earth, even at the equator.

Now you can adjust the reticle to compensate completely for refraction by simply offsetting the mount's vertical angle by the requisite amount of arc minutes and then re-adjusting the RAPAS push-pull screws to bring it back into the same alignment. Or you can simply do a drift alignment with your favorite method and then align the RAPAS to that via the push-pull screws. However, you will find that the best alignment that produces the lowest overall drift of both axes over most of the sky would be to NOT align the mount on the actual pole, rather to align the mount on the refracted pole. The only place where this is not as accurate is near the equator, but for any place above 20 degrees latitude, the refracted pole (the one you actually see) is more accurate.

For near perfect tracking for both RA and Dec I would first simply do Dec drift at the celestial equator, ignoring any RA drift. This can be done by guiding on a star in RA with Dec guiding turned off and watching Dec drift in the guider graph. Once that is accomplished, lock the azimuth axis and unlock the altitude. Send the mount to the zenith or slightly below toward the south and watch the RA drift with RA guiding set to zero. Raise or lower the RA axis until you get zero drift in RA. Sometimes, depending how far off you were in the altitude, you may have to go back to touch up Dec and then RA once more.

Once you have RA and Dec not drifting, you can then dial in the RAPAS via the push-pull screws and place Polaris on the reticle according to the App.

The whole process takes about 45 minutes and can be done before the sky is fully dark. You only have to do it once and forever more you can use the RAPAS to re-create that alignment - no more drift align needed.

Rolando



Re: Fist session with Mach1

Ray Gralak
 

Hi Darrell,

Now it is working how I expected it would.
That's good news! Now, if only yahoogroups would work as expected!

Best regards,

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Monday, August 6, 2018 5:56 AM
To: ap-gto@...
Subject: RE: [ap-gto] Re: Fist session with Mach1



Ray

APCC worked for a while, then I just had no end of trouble. It was not running how I expected. So I decided to
reinstall following your instructions. I am pleased to say it is now working. Again. And probably better.

I have changed some of the settings you suggested back to the way they are in the manual to include the auto
initialisation.

Now it is working how I expected it would.

Thanks very much.
Darrell


Re: HELP! Mount is lost - how to recover

Stephen Winston
 

>By the way, you never have to power cycle to sync to a known star. Leave the mount running, 
>loosen clutches, push the scope manually, OR even simpler move the scope via the buttons at 
>1200x to the star, bring it up in the menu and sync. No need to turn power off, no need to re-initialize.

Makes sense - SYNC'ing on a known good target undoes the previous bad sync...

Even simpler!  And I promise not to sync Deneb as Vega ;)!


New file uploaded to ap-gto

ap-gto@...
 

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the ap-gto
group.

File : /Jerry/PEMPro-2018-08-05-222614.ppc
Uploaded by : gb2010sb <astrojer@...>
Description :

You can access this file at the URL:
https://groups.yahoo.com/neo/groups/ap-gto/files/Jerry/PEMPro-2018-08-05-222614.ppc

To learn more about file sharing for your group, please visit:
https://help.yahoo.com/kb/index?page=content&y=PROD_GRPS&locale=en_US&id=SLN15398

Regards,

gb2010sb <astrojer@...>