Date   

Re: APCC move axis question

Andy Ermolli
 

I am convinced that the issue is either within windows or could be related to the fact that I have the mount not directly connected to the computer, no doubt. I was hoping that someone else had run into it before and they had an easy solution, that's all.

If I connect directly to the ASCOM Driver without using APCC everything works perfectly so that's what I am going to do for now. A pointing model would be nice but it's not really required for the type of imaging that I do (wide field).

I opened the device manager with the view "View, show hidden devices" checked and I didn't see anything strange.
Regarding pulse guide and ports over Com10, I read it in the APCC documentation, this is the link https://www.siriusimaging.com/Help/APCC/virtual_ports_tab.htm
It's the second bullet point in the top quarter of the page. Should be easy to find.


Eagle pier extensions: alternate fasteners?

Jeffc
 


I have two 8” extensions which I never separate when transporting the Eagle tripod/pier.  

As you know, the two 8” extensions are joined by three machines knobs.   

Since I never separate these pieces I’d like to replace the machines knobs with button screws (similar to the screw in the picture below).    Replacing the knobs with screws will make it a tad easier to transport — the three knobs tend to interfere with the packing of the tubes. 

The screws I have on hand are the same thread as the machine knob , but the head looks rather small.   

I was thinking someone familiar with McMaster-Carr could point me to a product… or does AP have a screw kit for the Extension tubes?   (I’m looking to use 6 screws here.)

Thx!

-jeff



Re: #APCC Pro 1.9 w/ASTAP platesolve test always fails #APCC

Sébastien Doré
 

You wanted to know why APPM couldn't get the RA/Dec from your image. The official answer is that you supplied a non-compliant FITS
image.
That was my understanding of your analysis indeed.

And in fact, I'm not sure it’s really a smarter solution to supportnon-compliant images! :-)
100% agree on that. That's why I put the quotes to "smarter" (as with everything, syntax is important ;-) )

Sébastien

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Seb@stro
> Sent: Sunday, August 22, 2021 6:20 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC Pro 1.9 w/ASTAP platesolve test always fails
>
> Thanks for the analysis, Ray.
>
> I suppose then ASTAP and ASPS must interpret those fields in a "smarter" way by removing the leading blank
> before parsing as you propose for the next build or use the other pair of keywords then...
>
> BTW, I found the following link <https://fits.gsfc.nasa.gov/standard40/fits_standard40aa-le.pdf> which is the current
> FITS standard description (dated July 2016). The one you provided in your previous message was dated 1999 but
> the specific section about string leading spaces being significant indeed remained unchanged.
>
> I've also posted the issue on the IndiLib forum as well, as you suggested.
>
>
> Sébastien
>







Pier crash while #APPM paused -

Sébastien Doré
 
Edited

Hi,

I started a dummy modeling APPM run indoor last night using the NASA Skyview camera and the Mach2. Platesolving wasn’t especially great at those Nasa Skyview images and so slow that at some point, I just hit “Pause” in APPM RUN tab and went to bed, not noticing the mount was still tracking (my bad, should have checked APCC before leaving everything there)...

This morning, the scope was obviously upside-down and camera against one of my tripod’s leg. That was expected since I have no limits set anywhere.

What I didn’t expect was that the motor didn’t stall. It was still pushing the OTA/camera against the leg and I was hearing a low-pitched rattling sound (that kinda woke me up) like if the motor belt was slipping or something.

My questions are :

- Is this normal behavior in this kind of situation? Shouldn't the motor stall under a "tracking" pier crash ?
- Could this cause damage to the mount ?
- Is it normal that the platesolving (w/ASTAP) is very slow with NASA skyview images ? (I suppose it is as it seemed to fail "near" solving for each image and always fell back to "all-sky" solving before going to the next, just to solve a few in the end).
- Is it to be expected to get so little successfully solved images with Skyview Images or am I just doing something wrong and dumb ?

Sébastien

Logs here: https://www.carpe-noctem.space/cms/wp-content/uploads/2021/08/ApccZip-Sebastien_Dore-2021-08-22-133536.zip


Re: #APCC Pro 1.9 w/ASTAP platesolve test always fails #APCC

Ray Gralak
 

Thanks for the analysis, Ray.
You wanted to know why APPM couldn't get the RA/Dec from your image. The official answer is that you supplied a non-compliant FITS
image.

I suppose then ASTAP and ASPS must interpret those fields in a "smarter"
APPM can't guess how other applications might break the rules. And in fact, I'm not sure it’s really a smarter solution to support
non-compliant images! :-)

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Seb@stro
Sent: Sunday, August 22, 2021 6:20 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC Pro 1.9 w/ASTAP platesolve test always fails

Thanks for the analysis, Ray.

I suppose then ASTAP and ASPS must interpret those fields in a "smarter" way by removing the leading blank
before parsing as you propose for the next build or use the other pair of keywords then...

BTW, I found the following link <https://fits.gsfc.nasa.gov/standard40/fits_standard40aa-le.pdf> which is the current
FITS standard description (dated July 2016). The one you provided in your previous message was dated 1999 but
the specific section about string leading spaces being significant indeed remained unchanged.

I've also posted the issue on the IndiLib forum as well, as you suggested.


Sébastien


Re: APCC move axis question

Ray Gralak
 

What client app are you using?
As I said, I am using my own ASCOM driver test application. It doesn't use buttons. It just has the ability to set a MoveAxis value, which stays until changed. This makes it easy to confirm the mount is moving.

The problem is many people have Windows problems or are using a remote desktop application or something else (e.g., WiFi) that causes an issue. For instance, a button press may not always register with an application making a user think there is a problem with the software when it's their computer or network that's the issue.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Andy Ermolli
Sent: Sunday, August 22, 2021 3:25 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC move axis question

Hi Ray,
I have the Jog utility but I am trying to use the three point polar alignment routine with NINA and that requires the
client app to be able to use the Moveaxis command.
If it's working for you it must me something with my settings or my client app. I am going to keep digging into the
settings.
What client app are you using?


Re: #APCC Pro 1.9 w/ASTAP platesolve test always fails #APCC

Sébastien Doré
 

Thanks for the analysis, Ray. 

I suppose then ASTAP and ASPS must interpret those fields in a "smarter" way by removing the leading blank before parsing as you propose for the next build or use the other pair of keywords then...

BTW, I found the following link which is the current FITS standard description (dated July 2016). The one you provided in your previous message was dated 1999 but the specific section about string leading spaces being significant indeed remained unchanged.

I've also posted the issue on the IndiLib forum as well, as you suggested. 

Sébastien


Re: APCC move axis question

 

>>> Interesting Andy. I use phd2 for guiding and my virtual ports are 20 and 21 I believe.

i've only used ports 20 and 21, and had no issues with APCC. i don't think port numbers that high are the issue. usually it's lower port numbers that could cause potential interference

On Sun, Aug 22, 2021 at 4:37 PM Chris White <chris.white@...> wrote:
Interesting Andy. I use phd2 for guiding and my virtual ports are 20 and 21 I believe. I have no problems that I know of. I have not used the new apcc pro update yet, so maybe this port number thing is something new?



--
Brian 



Brian Valente


Re: APCC move axis question

Chris White
 

On Sun, Aug 22, 2021 at 08:15 PM, Andy Ermolli wrote:
There is something going on with my Com ports that I don't quite understand and the virtual ports in APCC seem to interfere with my actual com ports.
Chris do you have your mount connected directly to the computer or to a hub? My mount is connected to the UPBV2. I wonder if that is the issue.
My mount is connected directly to my computer.  All my imaging gear, etc... is connected through a Pegasus Advance which is mounted on the OTA.  This cables off to the PC which is under the mount. 

Where did you read about pulse guiding not working if the VP's were above 10?  IIRC when I setup APCC a few months ago it was suggested to use really high numbers to ensure there would not be any conflict between the VP's and the actual ports. 


Re: APCC move axis question

Stacey Mills
 

You need to make sure that APCC closes itself rather than having another program terminate it improperly.  When APCC closes itself it closes (inactivates) the virtual ports.  If the program is terminated without normal closure the virtual ports will still be there "active" and the next time you start APCC they won't be available and it will have to make new virtual ports.  Use Device Manager and check your COM ports.  It helps to check the "View, show hidden devices"  which will show inactive Com ports.  It's OK if they're there but they shouldn't still be "active."

-Stacey


Re: APCC move axis question

Andy Ermolli
 
Edited

There is something going on with my Com ports that I don't quite understand and the virtual ports in APCC seem to interfere with my actual com ports.
Chris do you have your mount connected directly to the computer or to a hub? My mount is connected to the UPBV2. I wonder if that is the issue.


Re: APCC move axis question

Chris White
 

Interesting Andy. I use phd2 for guiding and my virtual ports are 20 and 21 I believe. I have no problems that I know of. I have not used the new apcc pro update yet, so maybe this port number thing is something new?


Re: APCC move axis question

Andy Ermolli
 

I have an update. Had my virtual port set to com10 and it didn't work. When I set the virtual port to com20 everything worked fine. 
Is it OK to keep the port at com 20? I read in the manual that I wouldn't be able to use pulse guide with a port number higher than com10.
I use PHD2 for guiding which connects to the AP v2 driver.


Re: APCC move axis question

Andy Ermolli
 

Hi Ray,
I have the Jog utility but I am trying to use the three point polar alignment routine with NINA and that requires the client app to be able to use the Moveaxis command.
If it's working for you it must me something with my settings or my client app. I am going to keep digging into the settings.
What client app are you using?


Re: APCC move axis question

Ray Gralak
 

Andy,

APCC has always supported the "MoveAxis" command through the ASCOM driver.

I just tried it, and it works for me using the V1 chip using my own ASCOM test application.

BTW, since you are having so much trouble with MoveAxis, have you tried the AP V2 ASCOM Driver's APJog utility? It works by slewing the specified distance instead of using MoveAxis. It's way more predictable than using button presses which might get delayed by Windows and user interface events.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Andy Ermolli
Sent: Sunday, August 22, 2021 1:42 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC move axis question

Does APCC take the move axis command? I'm using the V2 driver 5.21.01connected to a virtual port Com10
created by APCC. I use NINA as the Ascom client app.

If I push the move axis button in the client app I see the custom rate change in the Ascom Driver window but not in
the APCC status window. The mount does not move.
The mount this time is the AP900 with firmware V2.

If I connect NINA directly to the driver and not use APCC then the move axis command works as expected.


Re: N.I.N.A plugins ?

Dale Ghent
 

Hi Michael,

I recently put together a central FAQ die using NINA with AP mounts and APCC. It includes info on the Smart Meridian Flip plug-in that Brian linked to, and additional topics, as well. 


On Aug 22, 2021, at 16:42, michael mccann via groups.io <mmccawsprojects@...> wrote:

Thanks 
I’ll start there.

Cheers 


On Aug 22, 2021, at 1:37 PM, Brian Valente <bvalente@...> wrote:


Hi Mike

you should check out dale's post here:





On Sun, Aug 22, 2021 at 12:22 PM michael mccann via groups.io <mmccawsprojects=icloud.com@groups.io> wrote:

Hi
I’m so happy to see N.I.N.A. Is now compatible with APPM and APCC.  I’m trying to familiarize myself with N.I.N.A. 1.11 before I get back to the used AP mount I bought just before I left.  I’ve only used N.I.N.A. 1.10 (and only with Losmandy and iOptron eqpt)and never looked at N.I.N.A. plugins before.  Are there plugins I should become familiar with? Especially to setup APPC and APPM?

Thanks

Mike







--
Brian 



Brian Valente


Re: N.I.N.A plugins ?

michael mccann
 

Thanks 
I’ll start there.

Cheers 


On Aug 22, 2021, at 1:37 PM, Brian Valente <bvalente@...> wrote:


Hi Mike

you should check out dale's post here:





On Sun, Aug 22, 2021 at 12:22 PM michael mccann via groups.io <mmccawsprojects=icloud.com@groups.io> wrote:

Hi
I’m so happy to see N.I.N.A. Is now compatible with APPM and APCC.  I’m trying to familiarize myself with N.I.N.A. 1.11 before I get back to the used AP mount I bought just before I left.  I’ve only used N.I.N.A. 1.10 (and only with Losmandy and iOptron eqpt)and never looked at N.I.N.A. plugins before.  Are there plugins I should become familiar with? Especially to setup APPC and APPM?

Thanks

Mike







--
Brian 



Brian Valente


APCC move axis question

Andy Ermolli
 

Does APCC take the move axis command? I'm using the V2 driver 5.21.01connected to a virtual port Com10 created by APCC. I use NINA as the Ascom client app. 

If I push the move axis button in the client app I see the custom rate change in the Ascom Driver window but not in the APCC status window. The mount does not move.
The mount this time is the AP900 with firmware V2. 

If I connect NINA directly to the driver and not use APCC then the move axis command works as expected.


Re: N.I.N.A plugins ?

 

Hi Mike

you should check out dale's post here:





On Sun, Aug 22, 2021 at 12:22 PM michael mccann via groups.io <mmccawsprojects=icloud.com@groups.io> wrote:

Hi
I’m so happy to see N.I.N.A. Is now compatible with APPM and APCC.  I’m trying to familiarize myself with N.I.N.A. 1.11 before I get back to the used AP mount I bought just before I left.  I’ve only used N.I.N.A. 1.10 (and only with Losmandy and iOptron eqpt)and never looked at N.I.N.A. plugins before.  Are there plugins I should become familiar with? Especially to setup APPC and APPM?

Thanks

Mike







--
Brian 



Brian Valente


N.I.N.A plugins ?

michael mccann
 

Hi
I’m so happy to see N.I.N.A. Is now compatible with APPM and APCC. I’m trying to familiarize myself with N.I.N.A. 1.11 before I get back to the used AP mount I bought just before I left. I’ve only used N.I.N.A. 1.10 (and only with Losmandy and iOptron eqpt)and never looked at N.I.N.A. plugins before. Are there plugins I should become familiar with? Especially to setup APPC and APPM?

Thanks

Mike

6521 - 6540 of 86824