Date   

Re: APCC Questions

Eric Dreher
 

Let me preface my response with:  I'm only a six-month user of APCC and a Mach1, and there are those who know far more that will correct any errors in my response.

1.  I've never seen APCC or the V2 driver cause my laptop to freeze.  How much "horsepower" are you running?  Have you checked the Task Manager for how much processor and memory occupancy you're using?

2.  CdC is not a resource-hungry program.  If all you're running is the A-P software and CdC, you might have a look at whatever else is running in the background.

3.  When you first power-up the mount, it's sync'd and initialized from that parked position.  Under the driver's advanced tab you'll find a box that should be checked, labeled "Convert SYNCs to RCALs (Highly Recommended).  This will override the sync command you'll use in CdC, converting its sync to an RCAL automatically.

4.  As to moving with the driver or APCC, I've done both and have found no difference in my experience.

HTH

Eric


APCC Questions

Darrell Betts
 

Hi All

 

I now have the Mach1 and APCC working, but I have several user questions.

 

I am using APCC with AP V2 Ascom and Cartes du Ciel.

 

After I have done the alignment and do a goto, I need to nudge the scope a bit.  I have tried the AP Jog button in the upper right corner of APCC, but that seems to cause my laptop to freeze.  I can find two other options.

There is the Move Scope group in APCC, and there are the Move Scope Controls in AP V2 ASCOM.  I am wondering which of these two do most people use. Is one preferred over the other?

 

Second, once I have nudged the scope I will need to do a Recal.  I understand the difference between Recal and Sync.  And I can do this using the KeyPad.  But how do I do a Recal from the laptop?  In CdC, there is a Sync option under the Telescope menu.  With my old EQ6, this is what I used.  With the Mach1 (GTOCP4) does anyone know if the Sync option in CdC will do a Sync or Recal?  Or should I use an option in APCC?

 

Thanks

Darrell

 



Re: APPM tracking error

Craig Young
 

Hi Ray,

I didn't know that .. thanks heaps for that, will make it easier in identifying the source of the problem.

Craig


Re: APPM tracking error

Craig Young
 

No problem taking this off group.  It was cloudy last night so I was not able to test reversing the RA and DEC directions in APPM.  Tonight looks good, so we should know something in the next few hours.

Craig


Re: New file uploaded to ap-gto

Roland Christen
 

Just a quickie shot of the Pelican between bouts of bad weather. Taken with the 130GTX, QSI 683 camera on an 1100 mount that I am testing.

Rolando



-----Original Message-----
From: ap-gto
To: ap-gto
Sent: Tue, Aug 7, 2018 11:32 pm
Subject: [ap-gto] New file uploaded to 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@...>


------------------------------------

------------------------------------

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: 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