1. main@ap-gto.groups.io
  2. Messages
   Date   
Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

ap@CaptivePhotons.com
 

Erkaslan Aygen wrote:

 

  • I gave it a try with the regional setting back = problem back ! This is really, really embarrassing and irritating. Sure, by having the regional setting as if I am in the USA, it's seems to be working as a breeze. However, and as mentioned, by doing this, I have only limited access to my automated software. 

That's Voyager, right?  I am not a Voyager user, but I understand a lot of AP users are.  Have you asked Voyager support about the situation?  The data being rejected comes from Voyager, right?

 

 
Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

So, all updates installed correctly. 

I gave it a try with the regional setting back = problem back ! This is really, really embarrassing and irritating. Sure, by having the regional setting as if I am in the USA, it's seems to be working as a breeze. However, and as mentioned, by doing this, I have only limited access to my automated software. 

Honestly, I don't know what to do anymore. For the time being, I will test only with the AP driver (APCC uninstalled) and see what result I can get. 

Last, what might cause the below message (first time I got it) ?
Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

Hi Ray,

I have some Windows updates pending and one pertaining to ".NET 4.8.... I am about to install them.

BTW, I am currently running some tests since I upgraded one of my refractor and guess what ? My automation software is triggering error messages following the regional settings change ! This is just insane and irritating :(

Fingers crossed that W10 updates / .NET 4.8 could solve all this mess.

Regards,
Aygen



Le ven. 22 oct. 2021 à 15:42, Ray Gralak <iogroups@...> a écrit :
Hi Aygen,

> the AP driver using decimal comas rather than a normal "." while sending command, then :

Thank you for summarizing and agreeing with my original assessment of the issue. I will be looking into the globalization issue with the specific version of Windows Enterprise that you are using.

BTW, have you applied all available updates to Windows and the .NET 4.8 Framework? If not, it is essential that you do. The AP V2 ASCOM driver is written in VB6, and there have been issues with some Windows updates that have been fixed in later updates. Here is one example:

https://www.zdnet.com/article/microsoft-these-windows-10-updates-fix-broken-visual-basic-apps-but-not-for-1903/

-Ray


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
> Sent: Friday, October 22, 2021 1:15 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"
>
> Good morning all,
>
> Finally my problem seems to be solved. Should you ever happen to experience similars issues, i.e. the AP
> driver using decimal comas rather than a normal "." while sending command, then :
>
>
>
> 1.    Simply open the regional settings and change the region. In my case, I live in Switzerland. What I did, I
> choose "USA".
> 2.    By doing so, Windows will automatically update the regional settings, including "replacing the comas
> with a dot".
>
> As per my yesterday tests, the problem seemed to be solved since no error message was shown in APCC nor
> in Voyager !
>
> Thank you all for your kind support.
>
> Regards,
> Aygen
>






Re: New beta version of APCC Standard (1.9.1.0) and Pro (1.9.1.1)

Dale Ghent
 


Big thanks to Ray for implementing this option. I'm going to be fleshing out the dec-arc integration for my NINA plugin over the next week.




On Oct 22, 2021, at 15:15, Seb@stro <sebastiendore1@...> wrote:

Hello Ray,

Re 3D viewer, a quick test confirmed it now tracks the movements on my Mach2 (FW: VCP5-P02-10 if that matters) with clutches disengaged. 

Will test the APPM/ASTAP enhancement next time I get a chance to do a real mapping run, but I can already tell the solving time I now get with the NINA camera simulator (which shouldn't be that much different with my own camera assuming correct exposure and solver settings) has improved by 10 times, from 5 sec to 0.5 sec per point ! 🙂

Also I don't know if it has something to do with it (or if a recent intempestive Win10 update or something else fixed it) but I also got the "Refresh COM Ports" in APCC working with this version, which never did for me before (always had to restart APCC when I managed to create COM ports conflicts somehow). 

That plus the continued DEC-Arc modeling integration effort with NINA's feature set makes very good reasons for that version to be loved, as far as I am concerned.

Thanks for this update. I for one much appreciate it. 

Sébastien
Re: New beta version of APCC Standard (1.9.1.0) and Pro (1.9.1.1)

Sébastien Doré
 

Hello Ray,

Re 3D viewer, a quick test confirmed it now tracks the movements on my Mach2 (FW: VCP5-P02-10 if that matters) with clutches disengaged. 

Will test the APPM/ASTAP enhancement next time I get a chance to do a real mapping run, but I can already tell the solving time I now get with the NINA camera simulator (which shouldn't be that much different with my own camera assuming correct exposure and solver settings) has improved by 10 times, from 5 sec to 0.5 sec per point ! 🙂

Also I don't know if it has something to do with it (or if a recent intempestive Win10 update or something else fixed it) but I also got the "Refresh COM Ports" in APCC working with this version, which never did for me before (always had to restart APCC when I managed to create COM ports conflicts somehow). 

That plus the continued DEC-Arc modeling integration effort with NINA's feature set makes very good reasons for that version to be loved, as far as I am concerned.

Thanks for this update. I for one much appreciate it. 

Sébastien
Re: APPM and ASTAP #APCC

Erkaslan Aygen
 

Hi Ray,

This was with the official version (not the beta). I could give it try tonight with the beta.

Aygen

Le ven. 22 oct. 2021 à 15:48, Ray Gralak <iogroups@...> a écrit :
Hi Aygen,

> I am just asking since I am also experiencing the same issue: Plate solving is pretty much always failing while
> using ASTAP. However, when used "outside" APPM, it's working as a breeze and solving a couple of secs.

Is this with version 1.9.0.11, or the new version 1.9.1.1 beta with a fix?

https://www.apastrosoftware.com/apcc_download/APCC_Pro_BETA_Setup_1.9.1.1.exe

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
> Sent: Friday, October 22, 2021 1:23 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APPM and ASTAP #APCC
>
> Hi Bill,
>
> Did you have any success while changing the settings ?
>
> I am just asking since I am also experiencing the same issue: Plate solving is pretty much always failing while
> using ASTAP. However, when used "outside" APPM, it's working as a breeze and solving a couple of secs.
>
> I did increase the "min star" size to 1.5 (for example), but it didn't change my situation.
>
> As for my equipment :
>
>
> *     ASI 2600 MM PRO used with a TAK FSQ 85 (2.73 resolution)
>
> Cheers,
> Aygen
>






Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

Thank you, Ray, for your kind suggestions regarding W10 updates. I need to have look at just to make sure that I have the key updates.

Aygen
Re: New beta version of APCC Standard (1.9.1.0) and Pro (1.9.1.1)

Ray Gralak
 

Thanks, Linwood, for giving the beta a try! I'm glad the new APPM version solved the ASTAP problem.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of ap@...
Sent: Thursday, October 21, 2021 5:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] New beta version of APCC Standard (1.9.1.0) and Pro (1.9.1.1)

Ray Gralak wrote:



APCC Pro - APPM - Add check box to ASTAP plate solve configuration to use FITS header for RA, Dec,
and image scale.



I had a bit of time waiting for dark so I ran the prior and beta through 2-3 points in a "run" from APPM (not just
the plate solve).



As best I can tell it worked perfectly. Here is the log in the old version:



0000390 2021-10-21 19:37:46.472: Info, ASTAP Plate Solve, Solve() called.

0000391 2021-10-21 19:37:46.472: Error, ASTAP Plate Solve, Failed to get FITS dimensions
(NAXIS1/NAXIS2)

0000392 2021-10-21 19:37:46.472: Info, ASTAP Plate Solve, StartSolve: application path: c:/program
files/astap/astap.exe

0000393 2021-10-21 19:37:46.472: Info, ASTAP Plate Solve, StartSolve: arguments: -f
"C:\Users\ferguson\Documents\Astro-Physics\APPM\Image-APPM-2021-10-21-193634.txt-0002-RA_20.213-
DEC_-41.000.fit" -ra 20.1891585182137 -spd 48.9385895224573 -fov 0 -s 1000 -r 5

0000394 2021-10-21 19:37:46.488: Info, ASTAP Plate Solve, ASTAP is still running.

0000395 2021-10-21 19:37:46.640: Info, State Machine, Entering State=PlateSolveWait

0000396 2021-10-21 19:37:46.702: Info, ASTAP Plate Solve, ASTAP is still running.

0000397 2021-10-21 19:37:46.905: Info, ASTAP Plate Solve, ASTAP is still running.

0000398 2021-10-21 19:37:47.109: Info, ASTAP Plate Solve, ASTAP is still running.

0000399 2021-10-21 19:37:47.311: Info, ASTAP Plate Solve, ASTAP is still running.

0000400 2021-10-21 19:37:47.514: Info, ASTAP Plate Solve, ASTAP is still running.

0000401 2021-10-21 19:37:47.718: Info, ASTAP Plate Solve, ASTAP has exited.

0000402 2021-10-21 19:37:47.718: Info, ASTAP Results, Results Filename =
C:\Users\ferguson\Documents\Astro-Physics\APPM\Image-APPM-2021-10-21-193634.txt-0002-RA_20.213-
DEC_-41.000.ini

0000403 2021-10-21 19:37:47.719: Info, ASTAP Results, PLTSOLVD=T

0



Note the "-fov 0" which causes a couple of extra loops, and the "failed to get FITS dimensions".



In the new version:



0000531 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, Init

0000532 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, Solve() called.

0000533 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, Image scale (arc-secs/pixel): X =
0.793280434129994, Y = 0.793280434129994

0000534 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, NAXIS1/NAXIS2 (pixels) = 4784 / 3194, Image
dimensions X/Y (degrees) = 1.03062828266667 / 0.688090872666667

0000535 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, StartSolve: application path: c:/program
files/astap/astap.exe

0000536 2021-10-21 19:40:50.143: Info, ASTAP Plate Solve, StartSolve: arguments: -f
"C:\Users\ferguson\Documents\Astro-Physics\APPM\Image-APPM-2021-10-21-194002.txt-0001-RA_20.468-
DEC_26.570.fit" -ra 20.4524913831812 -spd 116.499133899902 -fov 0.688090872666667 -s 1000 -r 5

0000537 2021-10-21 19:40:50.160: Info, ASTAP Plate Solve, ASTAP is still running.

0000538 2021-10-21 19:40:50.334: Info, State Machine, Entering State=PlateSolveWait

0000539 2021-10-21 19:40:50.365: Info, ASTAP Plate Solve, ASTAP is still running.

0000540 2021-10-21 19:40:50.568: Info, ASTAP Plate Solve, ASTAP is still running.

0000541 2021-10-21 19:40:50.771: Info, ASTAP Plate Solve, ASTAP has exited.

0000542 2021-10-21 19:40:50.771: Info, ASTAP Results, Results Filename =
C:\Users\ferguson\Documents\Astro-Physics\APPM\Image-APPM-2021-10-21-194002.txt-0001-RA_20.468-
DEC_26.570.ini

0000543 2021-10-21 19:40:50.772: Info, ASTAP Results, PLTSOLVD=T



In this it has a calculated fov and no error. The solve time was fast in both cases, but did improve from 1.25s
to 0.62s.



I didn't have time to do a full model but let it run a couple points and all looked good.



Thank you.



Linwood
Re: APPM and ASTAP #APCC

Ray Gralak
 

Hi Aygen,

I am just asking since I am also experiencing the same issue: Plate solving is pretty much always failing while
using ASTAP. However, when used "outside" APPM, it's working as a breeze and solving a couple of secs.
Is this with version 1.9.0.11, or the new version 1.9.1.1 beta with a fix?

https://www.apastrosoftware.com/apcc_download/APCC_Pro_BETA_Setup_1.9.1.1.exe

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
Sent: Friday, October 22, 2021 1:23 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APPM and ASTAP #APCC

Hi Bill,

Did you have any success while changing the settings ?

I am just asking since I am also experiencing the same issue: Plate solving is pretty much always failing while
using ASTAP. However, when used "outside" APPM, it's working as a breeze and solving a couple of secs.

I did increase the "min star" size to 1.5 (for example), but it didn't change my situation.

As for my equipment :


* ASI 2600 MM PRO used with a TAK FSQ 85 (2.73 resolution)

Cheers,
Aygen
Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Ray Gralak
 

Hi Aygen,

the AP driver using decimal comas rather than a normal "." while sending command, then :
Thank you for summarizing and agreeing with my original assessment of the issue. I will be looking into the globalization issue with the specific version of Windows Enterprise that you are using.

BTW, have you applied all available updates to Windows and the .NET 4.8 Framework? If not, it is essential that you do. The AP V2 ASCOM driver is written in VB6, and there have been issues with some Windows updates that have been fixed in later updates. Here is one example:

https://www.zdnet.com/article/microsoft-these-windows-10-updates-fix-broken-visual-basic-apps-but-not-for-1903/

-Ray


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
Sent: Friday, October 22, 2021 1:15 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Good morning all,

Finally my problem seems to be solved. Should you ever happen to experience similars issues, i.e. the AP
driver using decimal comas rather than a normal "." while sending command, then :



1. Simply open the regional settings and change the region. In my case, I live in Switzerland. What I did, I
choose "USA".
2. By doing so, Windows will automatically update the regional settings, including "replacing the comas
with a dot".

As per my yesterday tests, the problem seemed to be solved since no error message was shown in APCC nor
in Voyager !

Thank you all for your kind support.

Regards,
Aygen
Re: GPS Solutions

Ray Gralak
 

Would it be possible to consider an APCC feature to use the time reading from whatever GPS is connected
and sync whatever system one is using to that timebase?
No, APCC cannot do this without elevated permissions on Windows, so it's not something we can consider doing.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steve Armen
Sent: Thursday, October 21, 2021 7:09 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GPS Solutions

Apologies if this has been asked and answered in the past.

Ray,
Would it be possible to consider an APCC feature to use the time reading from whatever GPS is connected
and sync whatever system one is using to that timebase? For example windows 10, or mac os. Not required
to be automatic. Maybe have an option to sync everything together with one button AFTER the GPS is
connected and the mount and any control SW (SGP, NINA, TSX, Maxim) are all connected. That would clearly
take some work, however would be mighty handy.

Just having this work with APCC, Windows10, and SGP would be very nice :->.
Mach1 gears

steve.duck@...
 

Hello could anyone tell me if the hex bolt behind the large cog should be loose of tight I was doing a bit of maintenance checking and found the one on ra was loose and one on dec was tight 
Thanks for any advice steve
Re: APPM and ASTAP #APCC

Erkaslan Aygen
 

Hi Bill,

Did you have any success while changing the settings ? 

I am just asking since I am also experiencing the same issue: Plate solving is pretty much always failing while using ASTAP. However, when used "outside" APPM, it's working as a breeze and solving a couple of secs. 

I did increase the "min star" size to 1.5 (for example), but it didn't change my situation. 

As for my equipment :
  • ASI 2600 MM PRO used with a TAK FSQ 85 (2.73 resolution)
Cheers,
Aygen
Re: VPort2 / Fault / Sync Target: Valid Alt/Az, RA/Dec, HA/Dec has not been received!"

Erkaslan Aygen
 

Good morning all,

Finally my problem seems to be solved. Should you ever happen to experience similars issues, i.e. the AP driver using decimal comas rather than a normal "." while sending command, then :

  1. Simply open the regional settings and change the region. In my case, I live in Switzerland. What I did, I choose "USA".
  2. By doing so, Windows will automatically update the regional settings, including "replacing the comas with a dot".
As per my yesterday tests, the problem seemed to be solved since no error message was shown in APCC nor in Voyager !

Thank you all for your kind support. 

Regards,
Aygen
Re: GPS Solutions

michael mccann
 

So clouds gotchas.

What’s frustrating to me is windows keeps automatically setting my laptop to pacific time zone thanks to AZ time zone, I think. My cell phone, hence my internet connection using a MOFI, connects to the cell tower servicing both Arizona and New Mexico. So turning off all of Windows 10 automatic settings for time and manually setting to my current time and date, the mount comes closer to slewing to target. So I probably just have to use the manuals process to return it to park 3.

On Oct 21, 2021, at 21:01, ap@... wrote:

I just finished hauling stuff inside (clouds moved in), so I fired up NINA and tried it. I moved from EDT to UTC with NINA open. It did not adjust on the fly, but I closed NINA and restarted it, and the sky atlas shows M31 appropriately, as well as the correct time for sunrise, set. etc in UTC time.

Note APCC has sites with their own time zone setting. I have no idea how they will react if they are not the same. I don't have the mount hooked up at present.


-----Original Message-----
From: ap@...
Sent: Thursday, October 21, 2021 10:50 PM
To: main@ap-gto.groups.io
Subject: RE: [ap-gto] GPS Solutions

michael mccann wrote:

So I changed pc manual time settings to UTC, now it’s Friday at 02:35 UTC 0.
Nina sky Atlas even though my lat/long is set to somewhere in New Mexico, sky atlas is showing M31 at it’s western altitude. So when using UTC settings how does one tell Nina the object is up, or even East or west of meridian ?

NINA should take its time zone from the PC's time zone setting, so if you changed the zone (not just the time) it should just know. But you might need to restart NINA if you have not since changing the time zone.

Did NINA on the sky atlas have proper times for things like subset, moonise, etc?






Re: GPS Solutions

ap@CaptivePhotons.com
 

I just finished hauling stuff inside (clouds moved in), so I fired up NINA and tried it. I moved from EDT to UTC with NINA open. It did not adjust on the fly, but I closed NINA and restarted it, and the sky atlas shows M31 appropriately, as well as the correct time for sunrise, set. etc in UTC time.

Note APCC has sites with their own time zone setting. I have no idea how they will react if they are not the same. I don't have the mount hooked up at present.

-----Original Message-----
From: ap@...
Sent: Thursday, October 21, 2021 10:50 PM
To: main@ap-gto.groups.io
Subject: RE: [ap-gto] GPS Solutions

michael mccann wrote:

So I changed pc manual time settings to UTC, now it’s Friday at 02:35 UTC 0.
Nina sky Atlas even though my lat/long is set to somewhere in New Mexico, sky atlas is showing M31 at it’s western altitude. So when using UTC settings how does one tell Nina the object is up, or even East or west of meridian ?

NINA should take its time zone from the PC's time zone setting, so if you changed the zone (not just the time) it should just know. But you might need to restart NINA if you have not since changing the time zone.

Did NINA on the sky atlas have proper times for things like subset, moonise, etc?
Re: GPS Solutions

ap@CaptivePhotons.com
 

michael mccann wrote:

So I changed pc manual time settings to UTC, now it’s Friday at 02:35 UTC 0.
Nina sky Atlas even though my lat/long is set to somewhere in New Mexico, sky atlas is showing M31 at it’s western altitude. So when using UTC settings how does one tell Nina the object is up, or even East or west of meridian ?

NINA should take its time zone from the PC's time zone setting, so if you changed the zone (not just the time) it should just know. But you might need to restart NINA if you have not since changing the time zone.

Did NINA on the sky atlas have proper times for things like subset, moonise, etc?
Re: GPS Solutions

michael mccann
 

So I changed pc manual time settings to UTC, now it’s Friday at 02:35 UTC 0.
Nina sky Atlas even though my lat/long is set to somewhere in New Mexico, sky atlas is showing M31 at it’s western altitude. So when using UTC settings how does one tell Nina the object is up, or even East or west of meridian ?

Cheers
Re: GPS Solutions

Steve Armen
 

Apologies if this has been asked and answered in the past. 

Ray, 
Would it be possible to consider an APCC feature to use the time reading from whatever GPS is connected and sync whatever system one is using to that timebase? For example windows 10, or mac os. Not required to be automatic. Maybe have an option to sync everything together with one button AFTER the GPS is connected and the mount and any control SW (SGP, NINA, TSX, Maxim) are all connected. That would clearly take some work, however would be mighty handy.

Just having this work with APCC, Windows10, and SGP would be very nice :->.
Re: GPS Solutions

michael mccann
 

I haven’t figured windows yet. It once gave me the message that I didn’t have admin rights. I’m the only user , so I’m going to try again tonight 


On Oct 21, 2021, at 19:39, fernandorivera3 via groups.io <fernandorivera3@...> wrote:

Mike why not set the CP4, keypad, computer and everything else to UT ??

Fernando

4441 - 4460 of 86824