On Dec 14, 2021, at 5:33 AM, Ray Gralak <iogroups@...> wrote:

Hi Mike,

I seem to have fat-fingered the PEM setting in APCC Pro last night and I was wondering whether the PEM
change gets written to the APCC log file. This would help me separate causes of tracking problems.

If you are worried about tracking performance, it is best to capture some unguided data using PEMPro or PHD2 and look at the
periodic error and drift. If you need more specific instructions, let me know.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Hayford, Michael
Sent: Monday, December 13, 2021 12:19 PM
To: main@ap-gto.groups.io
Cc: Michael Hayford
Subject: [ap-gto] APCC log question

I seem to have fat-fingered the PEM setting in APCC Pro last night and I was wondering whether the PEM
change gets written to the APCC log file. This would help me separate causes of tracking problems.
Thanks in advance.
Mike Hayford

On Dec 14, 2021, at 8:28 AM, Ray Gralak <iogroups@...> wrote:

Hi Bob,

- Mount would not respond to the NSEW buttons or start tracking no matter what I tried. An error code thrown
was Fault Triggered: East Limit.

The mount is hitting an axis limit, which is separate from a Horizon or Meridian limit. The best solution is to go to the "Homing/Limits" tab in APCC and click the "Configure Home and Limits" button to have APCC reconfigure the mount's limits. You must reconfigure the limits after moving the mount manually with the clutches released.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bob Enouen
Sent: Monday, December 13, 2021 2:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1600 Lost


The issue is resolved thanks to your help! More details below:

- I physically moved it to Park 3, unparked from last position, and tried to use NINA to successfully plate
solve but it would not sync because the mount was not tracking.

- Mount would not respond to the NSEW buttons or start tracking no matter what I tried. An error code thrown
was Fault Triggered: East Limit. I checked the 3D view and could see that the mount was displaying almost
upside down despite my attempts to ReCal via the GoTo tab.

- I was finally able to resolve by going to the APPC - Meridian Tracking limits Explorer and after selecting the
‘West’ button clicked Go To Meridian. The mount then moved far enough away from the limit that I was able to
start tracking, but I had to use the Stop Slew button before it really turned upside down. I was then able to
plate solve and sync in NINA. I’ve not yet established Meridian Limits and simply tell the mount to flip at the
Meridian.

- I checked the logs and can see that the time was not an issue and it unparked from Last Position the night it
failed so I’m not sure how I got stuck here, but am happy Ito have discovered another solution if it happens
again.


Thanks again!
Bob


Robert J. Enouen
Cell 513-504-4410


On Dec 9, 2021, at 10:08 AM, Dale Ghent <daleg@...> wrote:




Ah yes, I forgot about "Prevent Errant RECALs" (I have that turned off in my setups because of all the
testing I do with NINA, so the last time that has gotten in the way of things has faded from my memory.)




On Dec 9, 2021, at 09:53, Ray Gralak <iogroups@...> wrote:





Hi Bob,





What Dale suggests will work unless the pointing error is more than 5 degrees and "Prevent
Errant Recals" is enabled in APCC's Advanced settings. If you disable "Prevent Errant RECALs", make sure to
re-enable it after syncing!





BTW, if you manually move the mount to the Park 3 position and unpark from Park 3, the mount
should be pointing within 5 degrees. Thus, when you do a RECAL to regain precise pointing you will not need
to disable "Prevent errant RECALs".





-Ray





-----Original Message-----


From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bob Enouen


Sent: Thursday, December 9, 2021 5:46 AM


To: main@ap-gto.groups.io


Subject: Re: [ap-gto] AP1600 Lost





Ahh! Thanks so much Dale! I’ll do that at the next clear sky night - which will be Sunday
night here in


Springboro, OH.





Bob








Robert J. Enouen


Cell 513-504-4410





On Dec 9, 2021, at 8:12 AM, Dale Ghent <daleg@...> wrote:











Use the N/S/E/W buttons, either in APCC or in NINA, to drive the mount and point
the telescope at a clear


patch of sky, then a manual plate solve+sync inside NINA from the Imaging -> Plate Solve
window. The mount


will then know how it's oriented. There's no need to undo clutches and manually sling the
OTA around to a


park position.





The main question is /how/ your mount got to disoriented. One of the ways this can
happen is if you have


the mount parked in a particular position and then command it to unpark, but from a
different position instead


of Last parked or from the actual park position it was parked at.








On Dec 9, 2021, at 08:05, Bob Enouen <renouen@...> wrote:





Hi Ray,





My observatory-based AP1600 CP4 lost its location last night after a few
days of no activity due to


clouds. It’s been tracking great using a 300+ point APPM model on 180 second unguided
exposures with a


RC 16” that has a 3250mm focal length. I’m forwarding the APPC Pro logs and the NINA
logs for the last two


days for reference.





My question: I assume that if I physically release the RA/Dec gear boxes and
move the mount to Park 3


and then Recal using Alt/Az in APPC Pro to that position this will get me close enough to
then Recal using


PlateSolving. I do not have a hand control. Is this correct?





Thanks, Bob








Robert J. Enouen


Cell 513-504-4410


20211205-024656-2.0.0.2006.912.log


20211208-172149-2.0.0.2006.6568.log


ApccZip-BOB_ENOUEN-2021-12-09-061744.zip

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Larry Phillips
Sent: Tuesday, December 14, 2021 5:27 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Install APCC first or AP V2?

George, what was the answer?
Larry

I'm setting up a new imaging PC.  I can't remember if I'm supposed to install the V2 driver first or APCC.

Thanks,
Jim

I now have the same issue.  DIdn't notice until I tried the RAPAS for the first time for real (I put it in when new, but have never used it, NINA's TPPA is too easy). 

Did you just push it back up?  Is there something that is supposed to actually hold it there?

It is a little disturbing that it just falls down like that, if it is protecting that very expensive encoder.

If no one has a better answer, will call Monday. But in case a second data point is helpful.  Others might want to take a look also, I have no idea how long it had been down.

On Dec 13, 2021, at 6:13 AM, Dale Ghent <daleg@...> wrote:



It’s something I would be interested in, and I don’t even have a Stowaway. I have a CFF 92 f/6 refractor and the M63 APM-Riccardi reducer that have been using on it is baaaaarely passable, with some leniency,  when using it with my APS-C sensor. I’m using an OAG with this scope since it’s a compact travel imager, so its pick-off mirror is definitely sitting outside the corrected area in order to avoid intruding into the sensor’s fov. A larger corrected field is certainty something that I miss and would jump at the opportunity to have, even if it meant a focuser upgrade (my CFF 92 came with a 3” FTF; an improved optical design similar to the M63 format or a little larger, would be fine in my case.)

The APS-C Sony IMX571 sensor that is now in many CMOS astrocams is a fantastic sensor and is fairly accessible in terms of price, which is fueling its rise as a common sensor to see now. It’s the smaller cousin of the full-frame IMX455 which is also popular, of course.  A TCC and flattener that could competently handle both would be noticed. Other makes of (mainly Chinese) refractors in the 90-110mm range also lack a competent reducer/flattener for these sensor sizes and one could find use with those. 

On Dec 11, 2021, at 19:33, Roland Christen via groups.io <chris1011@...> wrote:



It's certainly possible to design and build a super sharp telecompressor for the 92 Stowaway to cover the full frame CMOS cameras with sharp round stars into the corners with no vignetting. It would require 3 things, a more exotic compressor design, a larger focuser and market for it. It would be more or less a super astrograph, rather than a small fun portable scope, plus it would cost more. Is the interest there or not, that is the question.

Rolando

-----Original Message-----
From: Roland Christen via groups.io <chris1011@...>
To: main@ap-ug.groups.io <main@ap-ug.groups.io>
Sent: Sat, Dec 11, 2021 6:15 pm
Subject: Re: [ap-ug] M33 with 92mm Stowaway, combining RGB, H-alpha, and O-III

Tonight I'm shooting in very clear skies, very cold sub-freezing, but poor seeing. Moon is also nearby.

Roland

-----Original Message-----
From: Eric Weiner <weinere@...>
To: main@ap-ug.groups.io
Sent: Sat, Dec 11, 2021 6:09 pm
Subject: Re: [ap-ug] M33 with 92mm Stowaway, combining RGB, H-alpha, and O-III

Thanks Roland. I have the 92FF as well.  Just exploring my options. Focal length of 644 vs 488, a 1’x0.7’ delta. That’s worth the trouble of flats for some targets imho. Our skies in Colorado have been terrible so I haven’t had a chance to experiment with the TCC myself yet. I just got it on Monday. 

Eric

On Dec 11, 2021, at 19:33, Roland Christen via groups.io <chris1011@...> wrote:



It's certainly possible to design and build a super sharp telecompressor for the 92 Stowaway to cover the full frame CMOS cameras with sharp round stars into the corners with no vignetting. It would require 3 things, a more exotic compressor design, a larger focuser and market for it. It would be more or less a super astrograph, rather than a small fun portable scope, plus it would cost more. Is the interest there or not, that is the question.

Rolando

-----Original Message-----
From: Roland Christen via groups.io <chris1011@...>
To: main@ap-ug.groups.io <main@ap-ug.groups.io>
Sent: Sat, Dec 11, 2021 6:15 pm
Subject: Re: [ap-ug] M33 with 92mm Stowaway, combining RGB, H-alpha, and O-III

Tonight I'm shooting in very clear skies, very cold sub-freezing, but poor seeing. Moon is also nearby.

Roland

-----Original Message-----
From: Eric Weiner <weinere@...>
To: main@ap-ug.groups.io
Sent: Sat, Dec 11, 2021 6:09 pm
Subject: Re: [ap-ug] M33 with 92mm Stowaway, combining RGB, H-alpha, and O-III

Thanks Roland. I have the 92FF as well.  Just exploring my options. Focal length of 644 vs 488, a 1’x0.7’ delta. That’s worth the trouble of flats for some targets imho. Our skies in Colorado have been terrible so I haven’t had a chance to experiment with the TCC myself yet. I just got it on Monday. 

Eric

On Dec 9, 2021, at 10:08 AM, Dale Ghent <daleg@...> wrote:


Ah yes, I forgot about "Prevent Errant RECALs" (I have that turned off in my setups because of all the testing I do with NINA, so the last time that has gotten in the way of things has faded from my memory.)

On Dec 9, 2021, at 09:53, Ray Gralak <iogroups@...> wrote:

Hi Bob,

What Dale suggests will work unless the pointing error is more than 5 degrees and "Prevent Errant Recals" is enabled in APCC's Advanced settings. If you disable "Prevent Errant RECALs", make sure to re-enable it after syncing!

BTW, if you manually move the mount to the Park 3 position and unpark from Park 3, the mount should be pointing within 5 degrees. Thus, when you do a RECAL to regain precise pointing you will not need to disable "Prevent errant RECALs".

-Ray

-----Original Message-----

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bob Enouen

Sent: Thursday, December 9, 2021 5:46 AM

To: main@ap-gto.groups.io

Subject: Re: [ap-gto] AP1600 Lost

Ahh!  Thanks so much Dale!  I’ll do that at the next clear sky night - which will be Sunday night here in

Springboro, OH.

Bob

Robert J. Enouen

Cell 513-504-4410

On Dec 9, 2021, at 8:12 AM, Dale Ghent <daleg@...> wrote:

Use the N/S/E/W buttons, either in APCC or in NINA, to drive the mount and point the telescope at a clear

patch of sky, then a manual plate solve+sync inside NINA from the Imaging -> Plate Solve window. The mount

will then know how it's oriented. There's no need to undo clutches and manually sling the OTA around to a

park position.

The main question is /how/ your mount got to disoriented. One of the ways this can happen is if you have

the mount parked in a particular position and then command it to unpark, but from a different position instead

of Last parked or from the actual park position it was parked at.

On Dec 9, 2021, at 08:05, Bob Enouen <renouen@...> wrote:

Hi Ray,

My observatory-based AP1600 CP4 lost its location last night after a few days of no activity due to

clouds.  It’s been tracking great using a 300+ point APPM model on 180 second unguided exposures with a

RC 16” that has a 3250mm focal length.  I’m forwarding the APPC Pro logs and the NINA logs for the last two

days for reference.

My question: I assume that if I physically release the RA/Dec gear boxes and move the mount to Park 3

and then Recal using Alt/Az in APPC Pro to that position this will get me close enough to then Recal using

PlateSolving.  I do not have a hand control.  Is this correct?

Thanks, Bob

Robert J. Enouen

Cell 513-504-4410

20211205-024656-2.0.0.2006.912.log

20211208-172149-2.0.0.2006.6568.log

ApccZip-BOB_ENOUEN-2021-12-09-061744.zip