Date   

Re: APCC with SGP Pier Flip Failure #APCC

Marcelo Figueroa
 

On Thu, Sep 23, 2021 at 09:46 AM, George wrote:

Out of curiosity, are you using the SGP v3 32 bit or the SGP v4 64 bit?

 

Regards,

Hello
 
I am using the latest 3.1 version of SGP (3.1.0.558) and it works perfect for what I need. In fact, if I disable the meridian options in APCC (1.8.8.17) and let SGP take care of everything, it works perfect, no problem at all.
 


Re: #Keypad Park Positions: AP 1100 GTO with encoders #Keypad

Thomas Giannaccini
 

Roland,
Thank you for the time you took to write that email. Yesterday, I was able to follow your instructions with some success but an issue still remains. I will outline my actions below.

I rough polar aligned the mount using RAPAs.
I updated the keypad firmware. I still do not have Park 5 in my list. Therefore, I used Park 4 instead, as will be described. 


I double checked my time and location data. Please note I am currently in the mountain time zone. The time was precisely synched at the correct moment although the screen shot of the official time was taken a few seconds after the time synch was completed.

IMG_0711.jpgIMG_0712.PNG
IMG_0713.jpgIMG_0714.PNG

I began this process with Auto Connect "No" to see how the process would go and to allow for a comparison.

I started in Park 3 (a rough, eyeball approximation)
I slewed to Park 2; It was spot on. Level was verified with a carpenter's level, 
I slewed to Park 4. It was off as shown below. The RA moved correctly The CW shaft was level and pointing West. When the Dec axis rotated it stopped at approximately the 10:30 position (just past 10 O'clock) and retreated to about 10 O'clock. This makes me think some sort of limit was hit?
IMG_0708.jpg
I then adjusted the OTA position so that it was correctly in Park 4. this change in Dec axis rotation was made my loosening clutches and moving the OTA by hand. Level was verified with a carpenter's level. 

I then slewed the mount back to Park 3. It was also not correct. It appeared to be off by the same amount that Park 4 was off. This is what Park 3 looked like:
IMG_0706.jpg
IMG_0707.jpg

Again I loosened the clutches, corrected the OTA position to Park 3. Then I slewed to Park 2. It was, again, spot on. Park 4 was again off by the same amount as before.  So the issue here is that I can attain either Park 3 or Park 4 but not both. This was all with AutoConnect "No".

I then selected Auto Connect "Yes"
I powered down the mount. I plut the OTA in Park 3 by loosening the clutches. I powered up the mount and repeated the above process Going from Park 3 to Park 2 to Park 4.  The behavior of the mount was identical to when AutoConnect was set to "No"

I then went to the polar alignment menu. Used 3 star alignment with a Reticle eyepiece in the main OTA. I slewed to 3 target stars. Polaris, Vega, and I can't remember the third. Each time any necessary adjustments were made only using keypad direction keys. I synched each star. No re-cal was performed. Just synch to each of those 3 stars. 

Then I slewed to targets. I would describe the mount performance as nearly flawless at this point; certainly good enough for where I am in my learning curve. 

If starting in Park 3, verifying Park 2 and then polar aligning via 3 stars will yield accurate results, this is easily within my grasp. I will continue to leave Auto Connect On and just restart from where I left off. I agree that this will be much easier. Thank you for the suggestion. I did not understand the details as you described them regarding a permanent mount.

Lastly, I placed a volt meter in line from the battery as you suggested. It is now semi-permanent. I did notice that the voltage dropped pretty quickly from over 13 volts to somewhere between 12.5 to 12.85 volts but was always above 12 volts.

Thank you for your help,

Tom





On Wed, Sep 22, 2021 at 12:05 PM Roland Christen via groups.io <chris1011=aol.com@groups.io> wrote:
You have basically a permanent setup and I believe you are missing a fundamental fact about the mount CP4 controller. The fact is that the controller always knows where the mount is pointed, even after the power is removed. That assumes that you do not take the telescope off the mount and disturb the positions of the axes by loosening the clutches. Therefore, once you have established the mount's position in the sky by having it go to a known object and doing a Recal on it, then all other positions will be correct. There is never a need to go to a known park position and doing a "Resume from Park X" routine.

The absolute simplest and most foolproof way to operate your mount is to change the setting in the keypad from Autoconnect "NO" to Autoconnect "YES". This will insure that the logic in the mount servo controller is always in charge of the operation and is never fooled by human error during startup. With Autoconnect YES the mount will start automatically and will never be lost or go to wrong park positions. You can move your mount on the dolly and it will not change the mount's internal calibration - as long as you never loosen the clutches and move the axes manually.

You have a permanent setup, which is defined as having the telescope attached to the mount and never removed and not disturbing the axes by loosening the clutches. Therefore the best, easiest and most sure-fire way to start your mount is to allow the mount's controller to determine where the axes are, and not over-riding this internal knowledge by starting manually every time. Set the keypad to Autostart YES and your startup will be seamless and accurate every time. Of course you can park your mount at any of the park positions at the end of your session, even Park 1 if that's where the setup clears your roof. Autostart YES will take all that into consideration, EVEN if the mount is parked with counterweight up and past the meridian!!

IMPORTANT: as long as you never loosen the clutches and move the axes manually.

We put a lot of smarts into the CP4 controllers in order to make operation of the mount as simple as possible. You take advantage of that by setting the keypad to Autostart "YES". If you always start with Autostart "NO", then you are throwing away all the smarts that are built into the mount, and it becomes just another mediocre mount that needs a lot of babysitting to get it going every night. Does all this make sense to you?

Roland Christen
Astro-Physics Inc.

-----Original Message-----
From: Thomas Giannaccini <tgiann3@...>
To: main@ap-gto.groups.io
Sent: Wed, Sep 22, 2021 11:42 am
Subject: Re: [ap-gto] #Keypad Park Positions: AP 1100 GTO with encoders

The mount and pier are on a motorized dolly. The dolly moves about 20-30 ft. I have not taken the setup apart yet but in the future, yes, it will be disassembled and substantially moved. 

I think updating the keypad to Park 5 and using the sequence you suggested will go a long way. 

Thank you,

Tom

On Wed, Sep 22, 2021 at 8:42 AM Roland Christen via groups.io <chris1011=aol.com@groups.io> wrote:
Let me ask you a more fundamental question. Do you have a fixed setup where you do not remove the scope from the mount after each session?

Roland

-----Original Message-----
From: Thomas Giannaccini <tgiann3@...>
To: main@ap-gto.groups.io
Sent: Tue, Sep 21, 2021 9:32 pm
Subject: Re: [ap-gto] #Keypad Park Positions: AP 1100 GTO with encoders

Mike,
I received an email from Roland telling me to use Park 3, 2 and 5. So I will try that. 

I think I generally only used “resume from park” on the initial startup. Initially that was Park 1, until George said to use Park 3. So, from that point forward I would resume from Park 3. 

I store the mount in Park 1 so it will fit in the shed. Perhaps I can try Park 4 or 5 to store it. I will first try resuming from Park 4 or 5 but if that doesn't work, I will just start from Park 3 by manually placing it there by hand if necessary  after slewing to Park 3.

In terms of waiting, I never timed it but I never went immediately to a target, I didn’t realize there was a time crunch. I did read the manual but I think it takes a few iterations for it to all sink in. 

What was confusing is that some Park attempts would end with the OTA in very odd positions. So it wasn’t a small margin of error as if the difference was based on movement from tracking; there were many times it wasn’t even in the ballpark. As to if the weights were pointed upwards, I did not notice them pointing up but if it was by a small amount I may not have seen it.

I am interested to try Roland’s suggestion. I think I may have to update my keypad to get Park 5. 

I try not to bog the forum with beginner questions, I only really ask when my attempted solutions don’t seem to work at all.

Thank you for your help,

Tom




On Tue, Sep 21, 2021 at 6:56 PM Mike Dodd <mike@...> wrote:
On 9/21/2021 8:37 PM, Thomas Giannaccini wrote:
> When I try to attain Park 4 by slewing to it then
> manually adjusting, it throws the other Park positions off.

After you manually adjust the mount in Park 4, what do you do next? Do
you "Resume From Last Parked?"

> ...when the mount is in Park 1 and slews to Park 4 which way
> is the main objective of the OTA supposed to swing? South or North?

In Park 1, the OTA is horizontal pointing north. In Park 4, the OTA is
horizontal pointing south.

The issue with Park 1, as pointed out by A-P, is that as soon as you
unpark, the mount is tracking, and after only a few seconds, it believes
the counterweight is up, which can be bad. From the keypad manual: "Park
1 is only seconds away from tracking into a counterweight-up status and
slews from Park 1 to western objects may cause the scope to point toward
the ground when beginning the slew."

How long do you wait after unparking from Park 1 before you slew to a
sky target? I usually do that immediately, as quickly as I can pick a
target. I have never had a problem unparking from Park 1 if I'm quick to
slew  to an east target. But, again, Park 4 where I level the mount and
OTA if necessary. (Actually, I will use Park 5 in the future because
that doesn't stretch my imaging cables as much as Park 4.)

--- Mike


--- Mike







--
CN: HasAnyoneSeenMyNeblua

--
Roland Christen
Astro-Physics

--
CN: HasAnyoneSeenMyNeblua

--
Roland Christen
Astro-Physics


--
CN: HasAnyoneSeenMyNeblua


Re: Trouble with MaxDome II slaving to APPM

Alan Erickson
 

Hi Shane,

Thanks for the tip about Device Hub. That plus passive mode did the trick. I use SGP, but when that is connected to the dome, I can't make another connection, so APPM couldn't monitor the dome. I think the MaxDome II ASCOM driver doesn't want multiple connections.

-Alan 


Re: APPM different with V1.9.0.9?

Bill Long
 

Nice and quick response to the issue! :) 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <iogroups@...>
Sent: Thursday, September 23, 2021 6:00 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] APPM different with V1.9.0.9?
 
Hi Rouz,

Yes, there was a change to APPM to use the Real-time RADec feature to get the RA and Dec from the mount with less latency. The installed APCC Pro 1.9.0.9 has an extra character (":") in the RA string response, which is invalid, so it always returns RA=0. You can see this in the APPM logs.

This was confusing to me because this was a bug I had fixed before creating the release. When I retested this morning, I could reproduce the problem with the installer version of 1.9.0.9, but not with the debugger on my computer. They should have had the same behavior, so I think I must have missed a step in building the APPM release executable.

So, I apologize for the issue. I created a new version, 1.9.0.11, which I tested, fixes this issue:

https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apastrosoftware.com%2Fapcc_download%2FAPCC_Pro_Setup_1.9.0.11.exe&amp;data=04%7C01%7C%7C63d31817c7e4488368bd08d97e921a8c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637679988244006680%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=k3%2FtMjarkmbSruortO0cyf%2BukA9febN%2Fo7%2BYADIP2q4%3D&amp;reserved=0

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Rouz
> Sent: Wednesday, September 22, 2021 9:32 PM
> To: main@ap-gto.groups.io
> Subject: [ap-gto] APPM different with V1.9.0.9?
>
> Hi Ray,
>
> Just installed V1.9.0.9 and running APPM again.
>
> The RA Delta figure getting larger and larger with every plateslove and then its fails.
>
> Im using ASTAP and NINA which working perfectly last week.
>
> I tried "Use last pate solve's offset as hint" on and off.
>
> I tried pointing model corrections on and off.
>
> Attached are the new APPM results:
>







Re: APCC Pro 1.9.0.11

M Hambrick
 

Hi Ray

Is there any concern to download this new version even if we don't have the Realtime RADec feature ?

Mike


Re: APPM different with V1.9.0.9?

 

>>> Is there a way you can cut/paste the east points data and not have to redo the entire thing?

afaik you can't add to or change a model (yet?) so you would need to rerun the model



On Thu, Sep 23, 2021 at 8:49 AM Rouz <rbidshahri@...> wrote:
Brian, glad it's working.

I wasn't able to finished the model before the clouds and just moved to the West Model before aborting.

Is there a way you can cut/paste the east points data and not have to redo the entire thing?


-Rouz,



--
Brian 



Brian Valente


Re: APPM different with V1.9.0.9?

Rouz
 

Brian, glad it's working.

I wasn't able to finished the model before the clouds and just moved to the West Model before aborting.

Is there a way you can cut/paste the east points data and not have to redo the entire thing?


-Rouz,


Re: APPM different with V1.9.0.9?

Rouz
 

Hi Ray,

Glad to hear you found the bug.
I'll download the new one and try again when clear again.

Do we know what causes the slew warning pause? Is that related to the bug.

Thanks,

-Rouz,


Re: APPM different with V1.9.0.9?

Mark Knogge
 

Ray,

That is exactly what I saw in the logs. Thanks for fixing so quickly.

Mark


APCC Pro 1.9.0.11

Ray Gralak
 

Hello All,

There is an issue with APPM in APCC Pro v1.9.0.9 that is fixed in this version. This fix only affects users with licenses that have
the Realtime RADec feature (Pro licenses, dated August 1, 2020, or later). APCC Standard is not affected.

https://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.9.0.11.exe

Best regards,

-Ray


Re: APCC with SGP Pier Flip Failure #APCC

George
 

Marcelo,

 

Out of curiosity, are you using the SGP v3 32 bit or the SGP v4 64 bit?

 

Regards,

 

George

 

George Whitney

Astro-Physics, Inc.

Phone:  815-222-6538 (direct line)

Phone:  815-282-1513 (office)

Email:  george@...

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Marcelo Figueroa via groups.io
Sent: Thursday, September 23, 2021 1:40 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC with SGP Pier Flip Failure #APCC

 

I'm in the same thing, trying to get SGP and APCC to work together on the meridian flip and I have a question.

 

Reviewing the different settings I see that Flip Offset allows to set a period of time to perform the flip before the meridian. My question is, is there any way to set an offset for after the meridian?

 

My problem is that if for example I set SGP to flip 10 minutes past the meridian, APCC has no idea of this and simply stops the mount when it reaches its own limit (which causes SGP to abort the session).

 

Maybe the Meridian Delay option is the answer, but I'm not sure about it  (or course, I'm doing something wrong).

 

Thanks,

 


Re: Closing Ascom V2 driver

 

FYI I had some similar frustrations thinking that all my clients were disconnected from ASCOM but it still reported clients being connected

I hunted down the mystery client to the planewave PWI control software for their focuser/rotator - it creates a connection to the mount, even though I don't use that software for anything mount related. 

so it's handy to have # of clients connected 

On Thu, Sep 23, 2021 at 6:44 AM Ray Gralak <iogroups@...> wrote:

> If I wanr to close the driver the only way I can do it is by clicking the "OK" button. The normal cross at the top

> right hand side has never worked for me. Is this a feature, or am I missing something?

 

The driver is not meant to be closed manually. It will close automatically when all ASCOM clients disconnect.

 

That said, you can force the driver to close by double-clicking the Clients label. Any connected client will likely show an error if you do this.

 

See this screenshot:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Geoff Smith

> Sent: Thursday, September 23, 2021 12:12 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] Closing Ascom V2 driver

>

> If I wanr to close the driver the only way I can do it is by clicking the "OK" button. The normal cross at the top

> right hand side has never worked for me. Is this a feature, or am I missing something?



--
Brian 



Brian Valente


Re: APPM different with V1.9.0.9?

 

Rouz thanks for chasing this one down

I went back and checked my model performance and you were right (obviously, since Ray issued an update)

I reloaded my model built with APPM 1.9.0.9 into 1.9.0.11 and it seems to be working correctly

Not sure if I need to rebuild the model though

On Thu, Sep 23, 2021 at 12:28 AM Rouz <rbidshahri@...> wrote:
I use a Dome but its a slave to Nina and not connected to APPM. So APPM doesn't really see the dome I believe.



--
Brian 



Brian Valente


Re: Closing Ascom V2 driver

ap@CaptivePhotons.com
 

Ray wrote:

But this brings up something related that puzzles me… what is the connect to ASCOM in APCC for? It is like
it is its own client, which is a bit circular as the Ascom driver then connects to APCC. I get the configure
button, but when and why does one connect from APCC to Ascom (as opposed to the reverse)?
APCC does not use the ASCOM driver, so there is no circular path.
Sure, sorry, I was unclear, I realized it couldn't "use" it in the normal sense which is why I said circular, not meaning to imply the circular aspect was a problem just how I knew it was not obviously userful.

The *ONLY* purpose for APCC starting the ASCOM driver is to keep the ASCOM driver open during a session.
This saves a few milliseconds if the driver has to open and close when all clients disconnect, then connect again.
Got it. I hope one day I get so methodical that a few milliseconds is meaningful. 😊


Re: Closing Ascom V2 driver

Ray Gralak
 

But this brings up something related that puzzles me… what is the connect to ASCOM in APCC for? It is like
it is its own client, which is a bit circular as the Ascom driver then connects to APCC. I get the configure
button, but when and why does one connect from APCC to Ascom (as opposed to the reverse)?
APCC does not use the ASCOM driver, so there is no circular path.

The *ONLY* purpose for APCC starting the ASCOM driver is to keep the ASCOM driver open during a session. This saves a few milliseconds if the driver has to open and close when all clients disconnect, then connect again.

I usually don't enable the option, but there is nothing wrong with enabling it.

-Ray


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@CaptivePhotons.com
Sent: Thursday, September 23, 2021 6:38 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Closing Ascom V2 driver

Mike Dodd wrote:



On 9/23/2021 3:12 AM, Geoff Smith wrote:
If I wanr to close the driver the only way I can do it is by clicking
the "OK" button. The normal cross at the top right hand side has never
worked for me. Is this a feature, or am I missing something?


For me, the driver closes automatically when all clients are disconnected from the mount. Occasionally
some kind of glitch might leave it running after all connections are closed, and the only way I've found to
close it then is with Task Manager. Right-click on the task bar

-> Task Manager.


Why do you want to close the driver?


That's how it should work, though periodically I also get stuck with it open and no apparent clients connected.
APCC can't be closed with the driver open either; end task works (takes a bit). APCC tells which are
connected to it – but all it shows is Ascom, and Ascom doesn't (as best I can tell) show what is connected to
it?



But this brings up something related that puzzles me… what is the connect to ASCOM in APCC for? It is like
it is its own client, which is a bit circular as the Ascom driver then connects to APCC. I get the configure
button, but when and why does one connect from APCC to Ascom (as opposed to the reverse)?



Linwood




Re: Closing Ascom V2 driver

Mike Dodd
 

On 9/23/2021 9:44 AM, Ray Gralak wrote:
That said, you can force the driver to close by double-clicking the
Clients label. Any connected client will likely show an error if you
do this.
That's good to know, Ray. The next time my ASCOM driver is still open after disconnecting all clients, I'll first check this to see how many the driver thinks are still connected, then double-click it to close the driver.

--- Mike


Re: Closing Ascom V2 driver

Mike Dodd
 

On 9/23/2021 9:38 AM, ap@CaptivePhotons.com wrote:
That’s how it should work, though periodically I also get stuck with it
open and no apparent clients connected. APCC can’t be closed with the
driver open either; end task works (takes a bit). APCC tells which are
connected to it – but all it shows is Ascom, and Ascom doesn’t (as best
I can tell) show what is connected to it?
The ASCOM window shows the MOUNT it's controlling, but not the clients that are using it.

But this brings up something related that puzzles me… what is the
connect to ASCOM in APCC for? It is like it is its own client, which
is a bit circular as the Ascom driver then connects to APCC. I get the
configure button, but when and why does one connect from APCC to Ascom
(as opposed to the reverse)?
I don't have APCC (yet), so I can't answer that.

--- Mike


Re: Closing Ascom V2 driver

Ray Gralak
 

> If I wanr to close the driver the only way I can do it is by clicking the "OK" button. The normal cross at the top

> right hand side has never worked for me. Is this a feature, or am I missing something?

 

The driver is not meant to be closed manually. It will close automatically when all ASCOM clients disconnect.

 

That said, you can force the driver to close by double-clicking the Clients label. Any connected client will likely show an error if you do this.

 

See this screenshot:

 

 

-Ray

 

> -----Original Message-----

> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Geoff Smith

> Sent: Thursday, September 23, 2021 12:12 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] Closing Ascom V2 driver

>

> If I wanr to close the driver the only way I can do it is by clicking the "OK" button. The normal cross at the top

> right hand side has never worked for me. Is this a feature, or am I missing something?


Re: Closing Ascom V2 driver

ap@CaptivePhotons.com
 

Mike Dodd wrote:

 

>On 9/23/2021 3:12 AM, Geoff Smith wrote:

> > If I wanr to close the driver the only way I can do it is by clicking

> > the "OK" button. The normal cross at the top right hand side has never

> > worked for me. Is this a feature, or am I missing something?

 

> For me, the driver closes automatically when all clients are disconnected from the mount. Occasionally some kind of glitch might leave it running after all connections are closed, and the only way I've found to close it then is with Task Manager. Right-click on the task bar

> -> Task Manager.

 

> Why do you want to close the driver?

 

That’s how it should work, though periodically I also get stuck with it open and no apparent clients connected.  APCC can’t be closed with the driver open either; end task works (takes a bit).  APCC tells which are connected to it – but all it shows is Ascom, and Ascom doesn’t (as best I can tell) show what is connected to it?

 

But this brings up something related that puzzles me… what is the connect to ASCOM in APCC for?   It is like it is its own client, which is a bit circular as the Ascom driver then connects to APCC.   I get the configure button, but when and why does one connect from APCC to Ascom (as opposed to the reverse)?

 

Linwood

 


Re: Closing Ascom V2 driver

Mike Dodd
 

On 9/23/2021 3:12 AM, Geoff Smith wrote:
If I wanr to close the driver the only way I can do it is by clicking
the "OK" button. The normal cross at the top right hand side has never
worked for me. Is this a feature, or am I missing something?
For me, the driver closes automatically when all clients are disconnected from the mount. Occasionally some kind of glitch might leave it running after all connections are closed, and the only way I've found to close it then is with Task Manager. Right-click on the task bar -> Task Manager.

Why do you want to close the driver?

--- Mike

5141 - 5160 of 86433