Date   

Re: ODD Tracking message at APCC Horizon Limit

Joe Zeglinski
 

Thanks for that further explanation Ray,
 
    Mind you, in my test, NO PLANETARIUM program was running – absolutely nothing but APCC.
I let the “settling message” continue at Park-2 for a couple of minutes, until it seemed it was NOT going to soon settle down. Could have waited longer, but it already seemed to be stuck in an unreasonable delay.
 
    I wonder if all motion had really ceased  before this wait, and the motors stopped, even as APCC waited for some kind of oscillation to end.
BTW – it was a dead calm night, so no winds were buffeting the truss tube.
 
    Next time, I’ll repeat the test, and if it happens again, give it say ... a half hour to finally come to rest.
 
Joe


Re: odd parking position discrepancy

john
 

Hi Rolando,

Thanks, that is perfectly clear...I figured there was a good reason the "error" was so reliably repeatable.

best

John Collins

__________________________________________________


On 7/5/2017 7:43 AM, chris1011@... [ap-gto] wrote:
The Park positions, especially Park1 and Park4, will never be exactly parallel to the earth. There are a number of reasons for that, including the time it takes for the Dec axis to stop moving after the RA axis has gotten to the park position. During the Dec slewing the RA will be tracking at the sidereal rate, so that at the end of the park sequence it will be slightly off. The second reason is that atmospheric refraction is being applied so that the RA and Dec positions will be slightly high.

For the above reasons, when you re-start the system next time, don't Resume from Park4, rather use the more accurate Resume from Present Position. That is the most accurate way to start your mount after it has been parked. The mount always keeps track of the slight differences on the actual position, so let it resume from its internal known position. The only time I would ever use Resume from Park4 (or 1 or 2 etc.) is when starting with a fresh setup where the internal mount positions are not known or where you have moved the scope via loosening the clutches.

Rolando



-----Original Message-----
From: john astro@... [ap-gto]
To: ap-gto
Sent: Tue, Jul 4, 2017 9:00 pm
Subject: [ap-gto] odd parking position discrepancy

Hi,


John Collins from Oregon here. Wondering if anyone has seen/fixed this:

Historically, my CP3-controlled setup (AP 1600GTO, CDK17, STX camera)
would maneuver all night and return to park with no discrepancy at all
using SkyX native driver. Setting up a new observatory with CP4, APCC
Pro, and V2 driver, I'm seeing a discrepancy creep into results. I have
a digital level on the cw shaft....physically set RA and DEC to 0.00
degrees at park 4.....if I so much as nudge the scope out of park, then
repark using APCC pro for both moves, I have a 0.4 degree RA and a 1.1
degree DEC error when apcc reports parked. These discrepancies repeat
reliably...that is, there doesn't seem to be some loose thingy flapping
around...the errors are quite deliberate. The weird part is that SkyX
pro "likes" the erroneous numbers better, showing the scope parked
right-on-the money, whereas there is a slight offset in SkyX when the
park 4 numbers are "correct".

I'm sitting here in daylight just fiddling...will experiment tonight as
to what actually works........

This may be part of CP4/APCC new-guy syndrome, so feel free to bop me on
the head if needed...never saw this issue with CP3, but then I didn't
have this resolution before either. I've done the balance, lash,
etc........drawing a blank at this point. Any ideas?


thanks

John Collins

Oregon

________________




------------------------------------
Posted by: john
------------------------------------

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: Upcoming solar eclipse

Fritz K
 

Eclipse Chasers: I think it was here that I was first alerted to the fact that some Oregon hotels are stiffing their customers. I can specifically report that Super 8, Ontario stiffed me out of 11 rooms. If you have a room in or near the eclipse path, DOUBLE CHECK your reservation and make sure it is still good and for the price you signed up for!

Indy Fritz


Re: ODD Tracking message at APCC Horizon Limit

Ray Gralak
 

Joe,

I think this may replicate the situation that a recent poster mentioned about finding his mount “not quite
parked”, after an imaging session let the mount continue tracking to a limit (perhaps).
I doubt that. That's a completely different scenario. Roland explained the situation accurately. The park position that TheSky uses definitely *is* different!

Once the limit is triggered and some movement action is given to the mount, tracking can be enabled - otherwise you would never be able to get out of the limit. But there has to be an indicator that a limit was reached (and there was, according to you).

And, about the settling "problem," APCC send the mounts to coordinates and waits for the coordinates to be within a certain amount. If the mount doesn't reach those coordinates, like if you cancel the motion, then the settling message may stay up until APCC can poll the mount and determine state has changed (this may take a while). Eventually the parking status window will close. If you are impatient, you can close the window on your own.

Some of this logic has been updated in the version that will be released soon, so there's no point worrying about it now.

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


-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Wednesday, July 5, 2017 4:11 PM
To: ap-gto@...
Subject: Re: [ap-gto] ODD Tracking message at APCC Horizon Limit



Sorry – minor correction on the last part.

APCC shows the “Limits Reached” and selected Action taken, if you hover the mouse over, for example,
the warning yellow Horizon box in the coordinates display panel. That is sufficient “notification” about why
the mount was parked, or stopped tracking, if one remembers (or knows) to check it. So, the hang-up with the
stuck Parking “Settling” remains a mystery.

Joe

From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
Sent: Wednesday, July 5, 2017 7:01 PM
To: ap-gto@...
Subject: Re: [ap-gto] ODD Tracking message at APCC Horizon Limit



Hi Rolando,

You seem to be answering an entirely different post – I did NOT mention the Hand Controller – in fact, it
isn’t even plugged in. All commands were done directly from the APCC control panel.

I also ran the test again, this time slewing the mount to the very edge of the Horizon profile, but still in the
safe zone. I jogged the mount carefully, to with a few minutes of crossing the boundary with Tracking
enabled, and set the Horizon Limits option action to PARK – to see what APCC would do in a “normal”
situation, as the mount approaches the border.

Sure enough, it behaved as advertised, and promptly PARKED the mount the moment it hit the edge of the
Horizon Limit profile.
However ... and there’s always a however :-) --- the odd thing was that APCC could not get out of its
“SETTLING MODE”, once it reached the designated parked position. In fact, even clicking on the RED STOP
button in that box, wouldn’t cancel the Settling. I actually had to close the Settling window, by clicking on the
“X”.

I think this may replicate the situation that a recent poster mentioned about finding his mount “not quite
parked”, after an imaging session let the mount continue tracking to a limit (perhaps). That would execute the
operator’s set option, if one had been chosen, Seems APCC still requires operator interaction, to actually
CLOSE the event, even after it responded properly to a Limits violation. Perhaps the intention was to leave it
hanging, as an indication that a Limit had been violated. Otherwise, the operator would never find out –
assuming the event was of interest. Perhaps it might be as an inspiration that APCC was really on guard for
us, or as a heads up to fix a script.

Bottom line ... the LIMITS only work, when coming in from the Safe zone.

Hope this helps,
Joe Z.



From: chris1011@... [ap-gto]
Sent: Wednesday, July 5, 2017 5:50 PM
To: ap-gto@...
Subject: Re: [ap-gto] ODD Tracking message at APCC Horizon Limit





In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off.

The present Hand controller software does not communicate with the mount or any other software to know
what any of the settings are that you have sent from the other software. He Hand Controller ONLY knows
what its own internal settings are and will send them to the mount if it is used to initialize the mount or if you
toggle thru the settings. Always the Hand controller is totally silent and sends nothing and receives nothing
from the mount (this will be changed in the next HC software upgrade). This is the way the HC has always
worked and I have explained this many times on this user group.

In the future we will make the HC an active program so that it updates itself as to settings inside the mount
when those settings are changed by an outside program. Until then, DO NOT use the HC to try and determine
what settings are in the mount (if you are sending instruction via a separate computer program). It simply does
not know. It is a 1 way street always sending instructions from the HC to the mount, not vice versa.

Rolando



-----Original Message-----
From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto] <ap-gto@...>
To: ap-gto <ap-gto@...>
Sent: Wed, Jul 5, 2017 4:38 pm
Subject: [ap-gto] ODD Tracking message at APCC Horizon Limit




Hi,

Just wondering why – with the fully updated current V2 driver and APCC PRO on my AP-1200 & CP4, , its
status bar still shows . UNPARKED (AP) and “TRACKING = SIDEREAL” even though the Horizon button is
lit in Yellow, its contents proclaiming ... “Limit Reached (Action: Zero Tracking)”.

No astronomy apps besides APCC, were running during today’s re-test.

Same thing if I change to the ... ACTION: PARK MOUNT ... option on Limit reached. The Limits tab info
concurs with the tripped condition, since obviously the scope position in the globe meatball, is definitely
inside my mapped horizon profile. This was just slewing the mount away from Park-2, but to a spot still inside
the limits field.

Shouldn’t the status bar toggle to also be in line with the Horizon Limit condition?
In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off. Looks
like the options in LIMITS, don’t actually affect the mount tracking or parking.

Then again ... Perhaps this was intentional, and it only works when a Limit is reached with motion from the
Safe zone ... outside the Limits field. That may have to do with not getting jailed at a Park position with no
escape except by momentarily de-activating Limits.
Do the Limits trigger only when coming in from the Safe Zone? Didn’t work that way either, when I discovered
this oddity last night, during a normal PEMPRO (PA) run.

I think this could potentially cause a mount collision, if we setup an imaging script, and go off to bed,
assuming APCC will safe the mount, eventually, when Limits are hit. Hopefully I am wrong.

Concerned ....
Joe Z.




Re: Upcoming solar eclipse

Christopher Erickson
 

You'll just have to catch me the next time you are on the Big Island!
 
Two kayaks, four seats and no waiting!
 
 
-Christopher Erickson
Observatory engineer
Summit Kinetics
Waikoloa, HI 96738
www.summitkinetics.com
 



From: ap-gto@... [mailto:ap-gto@...]
Sent: Wednesday, July 5, 2017 4:34 AM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

The AP folks – Roland, Marj, George, Christine, and Karen – will be in Casper, WY for ASTROCON, and then outside the city for the eclipse.  Sorry we’ll miss you, Chris!
Karen

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 02, 2017 4:21 PM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

 

 

Victor, Idaho.  Just outside the main gate of Yellowstone.

 

Supposed to be one of the two most likely places along the eclipse path to be cloud free.  The other is Eastern Oregon.

 

 

-Christopher Erickson
Observatory engineer
Summit Kinetics

Waikoloa, HI 96738
www.summitkinetics.com

 

 


From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 2, 2017 8:31 AM
To: ap-gto@...
Subject: [ap-gto] Upcoming solar eclipse

Where is the AP gang going to be for the eclipse?

 

Fred

 

Virus-free. www.avg.com


Re: ODD Tracking message at APCC Horizon Limit

Joe Zeglinski
 

Sorry – minor correction on the last part.
 
    APCC shows the “Limits Reached” and selected Action taken,  if you hover the mouse over, for example,  the warning yellow Horizon box in the coordinates display panel. That is sufficient “notification” about why the mount was parked, or stopped tracking, if one remembers (or knows) to check it. So, the hang-up with the stuck  Parking “Settling” remains a mystery.
 
Joe
 

From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
Sent: Wednesday, July 5, 2017 7:01 PM
To: ap-gto@...
Subject: Re: [ap-gto] ODD Tracking message at APCC Horizon Limit
 


Hi Rolando,
 
    You seem to be answering an entirely different  post – I did NOT mention the Hand Controller – in fact, it isn’t even plugged in. All commands were done directly from the APCC control panel.
 
    I also ran the test again, this time slewing the mount to the very edge of the Horizon profile, but still in the safe zone. I jogged the mount carefully, to with a few minutes of crossing the boundary with Tracking enabled, and set the Horizon Limits option action to PARK – to see what APCC would do in a “normal” situation, as the mount approaches the border.
 
    Sure enough, it behaved as advertised, and promptly PARKED the mount the moment it hit the edge of the Horizon Limit profile.
    However ... and there’s always a however :-)  --- the odd thing was that APCC could not get out of its “SETTLING MODE”, once it reached the designated parked position. In fact, even clicking on the RED STOP button in that box,  wouldn’t cancel the Settling. I actually had to close the Settling window, by clicking on the “X”.
 
    I think this may replicate the situation that a recent poster mentioned about finding his mount “not quite parked”, after an imaging session let the mount continue tracking to a limit (perhaps). That would execute the operator’s set option, if one had been chosen, Seems APCC still requires operator interaction, to actually CLOSE the event, even after it responded properly to a Limits violation. Perhaps the intention was to leave it hanging, as an indication that a Limit had been violated. Otherwise, the operator would never find out – assuming the event was of interest. Perhaps it might be as an inspiration that APCC was really on guard for us, or as a heads up to fix a script.
 
    Bottom line ... the LIMITS only work, when coming in from the Safe zone.
 
Hope this helps,
Joe Z.
 
 
 
From: chris1011@... [ap-gto]
Sent: Wednesday, July 5, 2017 5:50 PM
To: ap-gto@...
Subject: Re: [ap-gto] ODD Tracking message at APCC Horizon Limit
 


 
In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off.
The present Hand controller software does not communicate with the mount or any other software to know what any of the settings are that you have sent from the other software. He Hand Controller ONLY knows what its own internal settings are and will send them to the mount if it is used to initialize the mount or if you toggle thru the settings. Always the Hand controller is totally silent and sends nothing and receives nothing from the mount (this will be changed in the next HC software upgrade). This is the way the HC has always worked and I have explained this many times on this user group.

In the future we will make the HC an active program so that it updates itself as to settings inside the mount when those settings are changed by an outside program. Until then, DO NOT use the HC to try and determine what settings are in the mount (if you are sending instruction via a separate computer program). It simply does not know. It is a 1 way street always sending instructions from the HC to the mount, not vice versa.

Rolando
 
 
-----Original Message-----
From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
To: ap-gto <ap-gto@...>
Sent: Wed, Jul 5, 2017 4:38 pm
Subject: [ap-gto] ODD Tracking message at APCC Horizon Limit



Hi,
 
    Just wondering why – with the fully updated current V2 driver and APCC PRO on my AP-1200 & CP4, , its  status bar still shows . UNPARKED (AP) and  “TRACKING = SIDEREAL” even though the Horizon button is lit in Yellow, its contents proclaiming ...  “Limit Reached (Action: Zero Tracking)”.
 
    No astronomy apps besides APCC, were running during today’s re-test.
 
    Same thing if I change to the ...  ACTION: PARK MOUNT ... option on Limit reached. The Limits tab info concurs with the tripped  condition, since obviously the scope position in the globe meatball, is definitely inside my mapped horizon profile. This was just slewing the mount away from Park-2, but to a spot still inside the limits field.
 
    Shouldn’t the status bar toggle to also be in line with the Horizon Limit condition?
In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off. Looks like the  options in LIMITS, don’t actually affect the mount tracking or parking.
 
    Then again ... Perhaps this was intentional, and it only works when a Limit is reached with motion from the Safe zone ... outside the Limits field. That may have to do with not getting jailed at a Park position with no escape except by momentarily de-activating Limits.
Do the Limits trigger only when coming in from the Safe Zone? Didn’t work that way either, when I discovered this oddity last night, during a normal PEMPRO (PA) run.
 
    I think this could potentially cause a  mount collision, if we setup an imaging script, and go off to bed, assuming APCC will safe the mount, eventually,  when Limits are hit. Hopefully I am wrong.
 
Concerned ....
Joe Z.



Re: ODD Tracking message at APCC Horizon Limit

Joe Zeglinski
 

Hi Rolando,
 
    You seem to be answering an entirely different  post – I did NOT mention the Hand Controller – in fact, it isn’t even plugged in. All commands were done directly from the APCC control panel.
 
    I also ran the test again, this time slewing the mount to the very edge of the Horizon profile, but still in the safe zone. I jogged the mount carefully, to with a few minutes of crossing the boundary with Tracking enabled, and set the Horizon Limits option action to PARK – to see what APCC would do in a “normal” situation, as the mount approaches the border.
 
    Sure enough, it behaved as advertised, and promptly PARKED the mount the moment it hit the edge of the Horizon Limit profile.
    However ... and there’s always a however :-)  --- the odd thing was that APCC could not get out of its “SETTLING MODE”, once it reached the designated parked position. In fact, even clicking on the RED STOP button in that box,  wouldn’t cancel the Settling. I actually had to close the Settling window, by clicking on the “X”.
 
    I think this may replicate the situation that a recent poster mentioned about finding his mount “not quite parked”, after an imaging session let the mount continue tracking to a limit (perhaps). That would execute the operator’s set option, if one had been chosen, Seems APCC still requires operator interaction, to actually CLOSE the event, even after it responded properly to a Limits violation. Perhaps the intention was to leave it hanging, as an indication that a Limit had been violated. Otherwise, the operator would never find out – assuming the event was of interest. Perhaps it might be as an inspiration that APCC was really on guard for us, or as a heads up to fix a script.
 
    Bottom line ... the LIMITS only work, when coming in from the Safe zone.
 
Hope this helps,
Joe Z.
 
 
 

From: chris1011@... [ap-gto]
Sent: Wednesday, July 5, 2017 5:50 PM
To: ap-gto@...
Subject: Re: [ap-gto] ODD Tracking message at APCC Horizon Limit
 


 
In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off.
The present Hand controller software does not communicate with the mount or any other software to know what any of the settings are that you have sent from the other software. He Hand Controller ONLY knows what its own internal settings are and will send them to the mount if it is used to initialize the mount or if you toggle thru the settings. Always the Hand controller is totally silent and sends nothing and receives nothing from the mount (this will be changed in the next HC software upgrade). This is the way the HC has always worked and I have explained this many times on this user group.

In the future we will make the HC an active program so that it updates itself as to settings inside the mount when those settings are changed by an outside program. Until then, DO NOT use the HC to try and determine what settings are in the mount (if you are sending instruction via a separate computer program). It simply does not know. It is a 1 way street always sending instructions from the HC to the mount, not vice versa.

Rolando
 
 
-----Original Message-----
From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
To: ap-gto
Sent: Wed, Jul 5, 2017 4:38 pm
Subject: [ap-gto] ODD Tracking message at APCC Horizon Limit



Hi,
 
    Just wondering why – with the fully updated current V2 driver and APCC PRO on my AP-1200 & CP4, , its  status bar still shows .. UNPARKED (AP) and  “TRACKING = SIDEREAL” even though the Horizon button is lit in Yellow, its contents proclaiming ...  “Limit Reached (Action: Zero Tracking)”.
 
    No astronomy apps besides APCC, were running during today’s re-test.
 
    Same thing if I change to the ...  ACTION: PARK MOUNT ... option on Limit reached. The Limits tab info concurs with the tripped  condition, since obviously the scope position in the globe meatball, is definitely inside my mapped horizon profile. This was just slewing the mount away from Park-2, but to a spot still inside the limits field.
 
    Shouldn’t the status bar toggle to also be in line with the Horizon Limit condition?
In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off. Looks like the  options in LIMITS, don’t actually affect the mount tracking or parking.
 
    Then again ... Perhaps this was intentional, and it only works when a Limit is reached with motion from the Safe zone ... outside the Limits field. That may have to do with not getting jailed at a Park position with no escape except by momentarily de-activating Limits.
Do the Limits trigger only when coming in from the Safe Zone? Didn’t work that way either, when I discovered this oddity last night, during a normal PEMPRO (PA) run.
 
    I think this could potentially cause a  mount collision, if we setup an imaging script, and go off to bed, assuming APCC will safe the mount, eventually,  when Limits are hit. Hopefully I am wrong.
 
Concerned ....
Joe Z.



Re: ODD Tracking message at APCC Horizon Limit

Roland Christen
 


In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off.
The present Hand controller software does not communicate with the mount or any other software to know what any of the settings are that you have sent from the other software. He Hand Controller ONLY knows what its own internal settings are and will send them to the mount if it is used to initialize the mount or if you toggle thru the settings. Always the Hand controller is totally silent and sends nothing and receives nothing from the mount (this will be changed in the next HC software upgrade). This is the way the HC has always worked and I have explained this many times on this user group.

In the future we will make the HC an active program so that it updates itself as to settings inside the mount when those settings are changed by an outside program. Until then, DO NOT use the HC to try and determine what settings are in the mount (if you are sending instruction via a separate computer program). It simply does not know. It is a 1 way street always sending instructions from the HC to the mount, not vice versa.

Rolando


-----Original Message-----
From: 'Joseph Zeglinski' J.Zeglinski@... [ap-gto]
To: ap-gto
Sent: Wed, Jul 5, 2017 4:38 pm
Subject: [ap-gto] ODD Tracking message at APCC Horizon Limit



Hi,
 
    Just wondering why – with the fully updated current V2 driver and APCC PRO on my AP-1200 & CP4, , its  status bar still shows ... UNPARKED (AP) and  “TRACKING = SIDEREAL” even though the Horizon button is lit in Yellow, its contents proclaiming ...  “Limit Reached (Action: Zero Tracking)”.
 
    No astronomy apps besides APCC, were running during today’s re-test.
 
    Same thing if I change to the ...  ACTION: PARK MOUNT ... option on Limit reached. The Limits tab info concurs with the tripped  condition, since obviously the scope position in the globe meatball, is definitely inside my mapped horizon profile. This was just slewing the mount away from Park-2, but to a spot still inside the limits field.
 
    Shouldn’t the status bar toggle to also be in line with the Horizon Limit condition?
In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off. Looks like the  options in LIMITS, don’t actually affect the mount tracking or parking.
 
    Then again ... Perhaps this was intentional, and it only works when a Limit is reached with motion from the Safe zone ... outside the Limits field. That may have to do with not getting jailed at a Park position with no escape except by momentarily de-activating Limits.
Do the Limits trigger only when coming in from the Safe Zone? Didn’t work that way either, when I discovered this oddity last night, during a normal PEMPRO (PA) run.
 
    I think this could potentially cause a  mount collision, if we setup an imaging script, and go off to bed, assuming APCC will safe the mount, eventually,  when Limits are hit. Hopefully I am wrong.
 
Concerned ....
Joe Z.



ODD Tracking message at APCC Horizon Limit

Joe Zeglinski
 

Hi,
 
    Just wondering why – with the fully updated current V2 driver and APCC PRO on my AP-1200 & CP4, , its  status bar still shows ... UNPARKED (AP) and  “TRACKING = SIDEREAL” even though the Horizon button is lit in Yellow, its contents proclaiming ...  “Limit Reached (Action: Zero Tracking)”.
 
    No astronomy apps besides APCC, were running during today’s re-test.
 
    Same thing if I change to the ...  ACTION: PARK MOUNT ... option on Limit reached. The Limits tab info concurs with the tripped  condition, since obviously the scope position in the globe meatball, is definitely inside my mapped horizon profile. This was just slewing the mount away from Park-2, but to a spot still inside the limits field.
 
    Shouldn’t the status bar toggle to also be in line with the Horizon Limit condition?
In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off. Looks like the  options in LIMITS, don’t actually affect the mount tracking or parking.
 
    Then again ... Perhaps this was intentional, and it only works when a Limit is reached with motion from the Safe zone ... outside the Limits field. That may have to do with not getting jailed at a Park position with no escape except by momentarily de-activating Limits.
Do the Limits trigger only when coming in from the Safe Zone? Didn’t work that way either, when I discovered this oddity last night, during a normal PEMPRO (PA) run.
 
    I think this could potentially cause a  mount collision, if we setup an imaging script, and go off to bed, assuming APCC will safe the mount, eventually,  when Limits are hit. Hopefully I am wrong.
 
Concerned ....
Joe Z.


ODD Tracking message at APCC Horizon Limit

Joe Zeglinski
 

Hi,
 
    Just wondering why the APCC status bar still shows ... UNPARKED (AP) and  “TRACKING = SIDEREAL” even though the Horizon button is lit in Yellow, its contents proclaiming ...  “Limit Reached (Action: Zero Tracking)”.
 
    Same thing if I change to the ACTION: PARK MOUNT option on Limit reached. The Limits tab concurs with that condition, since obviously the scope position in the globe meatball, is definitely inside my mapped horizon profile.
 
    Shouldn’t the status bar toggle to also be in line with the Horizon Limit condition?
In fact, switching to HA display, the mount is definitely still tracking, until I click to Toggle Tracking off. Looks like the  options in LIMITS, doesn’t actually affect the mount.
 
    Then again ... perhaps this was intentional, and it only works when a Limit is reached from travel from the Safe zone ... outside the Limits field. That may have to do with not getting jailed at a Park position with no escape except by momentarily de-activating Limits.
 
    I think this could potentially cause a  mount collision, if we setup an imaging script, and go off to bed, assuming APCC will safe the mount, eventually when Limits are hit. Hopefully I am wrong.
 
Joe Z.


Re: Upcoming solar eclipse

 

George will be at a campsite in an undisclosed location :^). We are hoping to join him for the eclipse the night before, however we are not sure if that will actually work out. We anticipate that the park system will be overwhelmed and may end up observing at one of the ASTROCON sites.

 

Clear Skies,

 

Marj Christen

Astro-Physics, Inc

11250 Forest Hills Rd

Machesney Park, IL 61115

Phone: 815-282-1513

Fax: 815-282-9847

www.astro-physics.com

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Wednesday, July 05, 2017 10:00 AM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

 

 

We will be in Casper also.  Any particular place outside of the city?

 

Fred

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Wednesday, July 05, 2017 9:34 AM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

 

 

The AP folks – Roland, Marj, George, Christine, and Karen – will be in Casper, WY for ASTROCON, and then outside the city for the eclipse.  Sorry we’ll miss you, Chris!
Karen

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 02, 2017 4:21 PM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

 

 

Victor, Idaho.  Just outside the main gate of Yellowstone.

 

Supposed to be one of the two most likely places along the eclipse path to be cloud free.  The other is Eastern Oregon.

 

 

-Christopher Erickson
Observatory engineer
Summit Kinetics

Waikoloa, HI 96738
www.summitkinetics.com

 

 


From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 2, 2017 8:31 AM
To: ap-gto@...
Subject: [ap-gto] Upcoming solar eclipse

Where is the AP gang going to be for the eclipse?

 

Fred

 

Virus-free. www.avg.com


Re: Upcoming solar eclipse

fl.lusen
 

We will be in Casper also.  Any particular place outside of the city?

 

Fred

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Wednesday, July 05, 2017 9:34 AM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

 

 

The AP folks – Roland, Marj, George, Christine, and Karen – will be in Casper, WY for ASTROCON, and then outside the city for the eclipse.  Sorry we’ll miss you, Chris!
Karen

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 02, 2017 4:21 PM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

 

 

Victor, Idaho.  Just outside the main gate of Yellowstone.

 

Supposed to be one of the two most likely places along the eclipse path to be cloud free.  The other is Eastern Oregon.

 

 

-Christopher Erickson
Observatory engineer
Summit Kinetics

Waikoloa, HI 96738
www.summitkinetics.com

 

 


From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 2, 2017 8:31 AM
To: ap-gto@...
Subject: [ap-gto] Upcoming solar eclipse

Where is the AP gang going to be for the eclipse?

 

Fred

 

Virus-free. www.avg.com


Re: PEMPro without a keypad?

Roland Christen
 

You do not need a keypad to use PEMPro.

Rolando



-----Original Message-----
From: dbartolini@... [ap-gto]
To: ap-gto
Sent: Tue, Jul 4, 2017 9:23 pm
Subject: [ap-gto] PEMPro without a keypad?



Hi all,

I'm waiting for my new mount to arrive, so I decided to look through the APCC manual while I wait. I read through a brief discussion of PEMPro, and if I'm reading it correctly, the preferred method to record PEM is to use the keypad in order to record more than one worm cycle. I didn't order a keypad because I'll be imaging with a computer. Is it possible to use a virtual keypad (either ASCOM or APCC keypad window) to get a multi-cycle PEM recording?

I am aware that the mount comes preprogrammed for my specific mount, but I assume that I'll want to do a new recording at some point in the future.

Thanks,
Dave



Re: odd parking position discrepancy

Roland Christen
 

The Park positions, especially Park1 and Park4, will never be exactly parallel to the earth. There are a number of reasons for that, including the time it takes for the Dec axis to stop moving after the RA axis has gotten to the park position. During the Dec slewing the RA will be tracking at the sidereal rate, so that at the end of the park sequence it will be slightly off. The second reason is that atmospheric refraction is being applied so that the RA and Dec positions will be slightly high.

For the above reasons, when you re-start the system next time, don't Resume from Park4, rather use the more accurate Resume from Present Position. That is the most accurate way to start your mount after it has been parked. The mount always keeps track of the slight differences on the actual position, so let it resume from its internal known position. The only time I would ever use Resume from Park4 (or 1 or 2 etc.) is when starting with a fresh setup where the internal mount positions are not known or where you have moved the scope via loosening the clutches.

Rolando



-----Original Message-----
From: john astro@... [ap-gto]
To: ap-gto
Sent: Tue, Jul 4, 2017 9:00 pm
Subject: [ap-gto] odd parking position discrepancy

Hi,


John Collins from Oregon here. Wondering if anyone has seen/fixed this:

Historically, my CP3-controlled setup (AP 1600GTO, CDK17, STX camera)
would maneuver all night and return to park with no discrepancy at all
using SkyX native driver. Setting up a new observatory with CP4, APCC
Pro, and V2 driver, I'm seeing a discrepancy creep into results. I have
a digital level on the cw shaft....physically set RA and DEC to 0.00
degrees at park 4.....if I so much as nudge the scope out of park, then
repark using APCC pro for both moves, I have a 0.4 degree RA and a 1.1
degree DEC error when apcc reports parked. These discrepancies repeat
reliably...that is, there doesn't seem to be some loose thingy flapping
around...the errors are quite deliberate. The weird part is that SkyX
pro "likes" the erroneous numbers better, showing the scope parked
right-on-the money, whereas there is a slight offset in SkyX when the
park 4 numbers are "correct".

I'm sitting here in daylight just fiddling...will experiment tonight as
to what actually works........

This may be part of CP4/APCC new-guy syndrome, so feel free to bop me on
the head if needed...never saw this issue with CP3, but then I didn't
have this resolution before either. I've done the balance, lash,
etc........drawing a blank at this point. Any ideas?


thanks

John Collins

Oregon

________________




------------------------------------
Posted by: john
------------------------------------

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: Upcoming solar eclipse

Karen Christen
 

The AP folks – Roland, Marj, George, Christine, and Karen – will be in Casper, WY for ASTROCON, and then outside the city for the eclipse.  Sorry we’ll miss you, Chris!
Karen

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 02, 2017 4:21 PM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

 

 

Victor, Idaho.  Just outside the main gate of Yellowstone.

 

Supposed to be one of the two most likely places along the eclipse path to be cloud free.  The other is Eastern Oregon.

 

 

-Christopher Erickson
Observatory engineer
Summit Kinetics

Waikoloa, HI 96738
www.summitkinetics.com

 

 


From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 2, 2017 8:31 AM
To: ap-gto@...
Subject: [ap-gto] Upcoming solar eclipse

Where is the AP gang going to be for the eclipse?

 

Fred

 

Virus-free. www.avg.com


Re: PEMPro without a keypad?

Christopher Erickson
 

You don't need a keypad to operate PEMPro and analyze your PEM curve and optionally create and save a new one.
 
 
-Christopher Erickson
Observatory engineer
Summit Kinetics
Waikoloa, HI 96738
www.summitkinetics.com
 



From: ap-gto@... [mailto:ap-gto@...]
Sent: Tuesday, July 4, 2017 4:24 PM
To: ap-gto@...
Subject: [ap-gto] PEMPro without a keypad?

Hi all,


I'm waiting for my new mount to arrive, so I decided to look through the APCC manual while I wait. I read through a brief discussion of PEMPro, and if I'm reading it correctly, the preferred method to record PEM is to use the keypad in order to record more than one worm cycle. I didn't order a keypad because I'll be imaging with a computer. Is it possible to use a virtual keypad (either ASCOM or APCC keypad window) to get a multi-cycle PEM recording?


I am aware that the mount comes preprogrammed for my specific mount, but I assume that I'll want to do a new recording at some point in the future.


Thanks,

Dave


Virus-free. www.avg.com


PEMPro without a keypad?

Dave Bartolini
 

Hi all,


I'm waiting for my new mount to arrive, so I decided to look through the APCC manual while I wait. I read through a brief discussion of PEMPro, and if I'm reading it correctly, the preferred method to record PEM is to use the keypad in order to record more than one worm cycle. I didn't order a keypad because I'll be imaging with a computer. Is it possible to use a virtual keypad (either ASCOM or APCC keypad window) to get a multi-cycle PEM recording?


I am aware that the mount comes preprogrammed for my specific mount, but I assume that I'll want to do a new recording at some point in the future.


Thanks,

Dave


odd parking position discrepancy

john
 

Hi,


John Collins from Oregon here. Wondering if anyone has seen/fixed this:

Historically, my CP3-controlled setup (AP 1600GTO, CDK17, STX camera) would maneuver all night and return to park with no discrepancy at all using SkyX native driver. Setting up a new observatory with CP4, APCC Pro, and V2 driver, I'm seeing a discrepancy creep into results. I have a digital level on the cw shaft....physically set RA and DEC to 0.00 degrees at park 4.....if I so much as nudge the scope out of park, then repark using APCC pro for both moves, I have a 0.4 degree RA and a 1.1 degree DEC error when apcc reports parked. These discrepancies repeat reliably...that is, there doesn't seem to be some loose thingy flapping around...the errors are quite deliberate. The weird part is that SkyX pro "likes" the erroneous numbers better, showing the scope parked right-on-the money, whereas there is a slight offset in SkyX when the park 4 numbers are "correct".

I'm sitting here in daylight just fiddling...will experiment tonight as to what actually works........

This may be part of CP4/APCC new-guy syndrome, so feel free to bop me on the head if needed...never saw this issue with CP3, but then I didn't have this resolution before either. I've done the balance, lash, etc........drawing a blank at this point. Any ideas?


thanks

John Collins

Oregon

________________


Re: Upcoming solar eclipse

calypte@...
 

Menan, Idaho, for me.


Re: FIXED!! fiasco with apcc/V2 driver virtual ports

Ray Gralak
 

Hi John,

I'm glad that you were able to fix the problem!

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

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Monday, July 3, 2017 2:28 PM
To: ap-gto@...
Subject: [ap-gto] FIXED!! fiasco with apcc/V2 driver virtual ports



Hi

To everyone that responded, thank you. The virtual ports issue was pretty persistent...uninstalling, scrubbing
the registry, and reinstalling the FTDI drivers fixed things perfectly. Comms are back to normal now. Another
lesson in Leave-No-Stone-Unturned: since the physical port appeared to be working, I had ruled out the FTDI
stuff and concentrated on the virtual ports as the issue. If only I understood all this...........

In any case, all fixed....

John Collins

Eugene, Oregon

____________________________

On 6/29/2017 6:43 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto]
wrote:
Hi John,

First, I assume you have connected APCC to the mount or driver will not connect.

If that's not the problem, are you using a USB/serial device? Some are known to use a new virtual port
every time, thus eventually using all the virtual ports.

Then, try this:

1) Open Device Manager

2) From the View menu, select 'Show Hidden Devices'

3) Expand 'Ports (COM & LPT)' category from the list

4) Right-click on all the devices and remove them (no need to tick to
delete the driver)

5) From the Action menu, select 'Scan for New Devices'

Then enable the checkbox "Auto-Config" in the AP V2 driver and try connecting. If that doesn't work
uncheck the option and set the first two ports to ports you don't think have ever been used, like maybe
COM20 and COM21. Create the ports in APCC to make sure they work. Make sure you are connected to the
mount in APCC or driver will not connect. Then try connecting using one of the AP ASCOM driver utilities,
like AP Jog.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/a
pcc/apcc Author of PEMPro: http://www.ccdware.com Author of
Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author
of PulseGuide: http://www.pulseguide.com Author of Sigma:
http://www.gralak.com/sigma


-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Thursday, June 29, 2017 12:49 PM
To: ap-gto@...
Subject: Re: [ap-gto] fiasco with apcc/V2 driver virtual ports



Hi Ray,

Thanks for the effort, but I think I may not have been clear.

The entire setup of apcc pro, V2, skyX and the CP4 were operating
well...I was even marvelling at how simple the setup had been.
Something has happened that is causing a problem....in bullet point form:

* previously working system is started after standing for
days...everything fires up, but the V2 Com port # indicator in APCC
pulsed on/off 4 times then threw the "no mount on com port" error.
The mount is operating properly.

* V2 com port intermittently connected in response to manual
"connect", eventually throwing a "create virtual port before trying to connect"
after several tries...the apcc virtual ports page showed no virtual
ports (had been com 9 and com 11)...com 9 and 11 missing from
drop-down list

* Device manager shows virtual ports 9 and 10 but apcc has com 9 and
11 removed from drop down list AND not created in apcc --- situation
is deteriorating

*tried the "now" button...nothing--I've ended up with com 9 and 11
half-selected--new selections seem locked out

*tried delete all and delete residual, nothing. Uninstalled,
scrubbed, reinstalled apcc and V2....problem persists....I expect
some config file is being left behind at uninstall---configs
reappeared on reinstall, complete with virtual ports issue

*After reinstall, virtual ports do not appear in device manager

* tried com 11...connected, but pulsed and died, throwing error

*tried "now".....nothing. Manually selected com 15.....worked for one
session.....restarted apcc and com 15 started the pulse-and-die behavior.

I suspect the ultimate solution is to uninstall/reinstall, however
there seems to be a file or files that remain after uninstall, which
preserves the problem. I can handle the reinstallation easy-peasy,
but not sure where the files that store configs may be. I'd like to
do a thorough reinstall. Whatever the original cause, I have no idea.

What do I have to delete/uninstall to kill my original config--I'll
reenter info from scratch.

thanks

John Collins

__________________________________________________________

On 6/29/2017 6:09 AM, 'Ray Gralak (Groups)' groups3@...
[ap-gto]
wrote:
Hi John,

While the V2 driver did not connect when apcc called, it did
connect manually using the connect button.......tried fiddling with
the V2 com port timeout setting--no discernable change.
A number of builds ago, a "Now" button, as in "configure now", was
added in
APCC's "AP V2 Driver" group box. When clicked, APCC will find free
virtual ports and automomagically configure everything in the ASCOM
driver, including setting the virtual port number. You should not
even need to open the AP V2 driver's setup window. This was done to make it extremely simple to
configure all settings.
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: http://www.ccdware.com Author of Astro-Physics V2
ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide:
http://www.pulseguide.com Author of Sigma:
http://www.gralak.com/sigma

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...]
Sent: Thursday, June 29, 2017 12:15 AM
To: ap-gto@...
Subject: [ap-gto] fiasco with apcc/V2 driver virtual ports



Hi,

John Collins from Eugene, Oregon here. Operations just went
downhill incredibly fast....I had been running apcc pro ver
1.5.0.20 with the V2 driver ver 5.09.09 just fine using USB
control. Started up tonight and apcc started, then called the V2
driver as always, however, the V2 virtual com port# window pulsed
on/off 4 times and threw an "error connecting to the AP V2
driver-no mount on the com port". I checked port #'s, aok.
Restarted pc and apcc showed no virtual com ports....win
10 dev mgr showed com9 and com 10 virtual ports. APCC would not
delete or recreate the ports--com 9 and 10 were not in apcc's port
selection drop down....probably since they were considered in use(?).

While the V2 driver did not connect when apcc called, it did
connect manually using the connect button.......tried fiddling with
the V2 com port timeout setting--no discernable change.

Tried the "use ascom object" check box as suggested--no change.

Uninstalled and reinstalled apcc pro (checked the install/reinstall
virtual ports box) and V2 driver....no change.......apcc calls the
driver, but no data loaded into display windows. APCC pro does have
all the mount data displayed via the physical port. Now the V2
driver is not even trying to connect.

I smell a rat in my pc but can't find it........

any ideas?

will try going back to the native skyX driver for the moment

many thanks

John Collins

____________________________________________________



------------------------------------
Posted by: "Ray Gralak &#92;(Groups&#92;)" <groups3@...>
------------------------------------

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

Yahoo Groups Links





------------------------------------
Posted by: "Ray Gralak &#92;(Groups&#92;)" <groups3@...>
------------------------------------

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

Yahoo Groups Links