Date   

Re: Setting up NINA

DFisch
 

Best response of the year “ How’s the weather in Nepal these days?”, kinder and more humorous! 

On Sat, Oct 16, 2021 at 14:11 Dale Ghent <daleg@...> wrote:

Hi Bruce,

How is the weather in Nepal these days? ;)

In NINA, a north latitude is positive and a west longitude is negative. You note a lat/long of "28.688/81.49" in your message, which would put you at a very picturesque yet pretty remote corner of Nepal, not perhaps a more likely location of southern California.

/dale

> On Oct 16, 2021, at 13:43, Bruce Donzanti <donza2735@...> wrote:
>
> Thanks Linwood.
>
> I went down your checklist of items and was testing during the day.  It is still not slewing to the correct coordinates that I enter.  Also, the Sky Atlas is showing the correct coordinates as expected but the transit time for an object is way off, still indicating the mount thinks it is elsewhere.  It will return correctly to park 4.  So, I am still at a loss what else to check.  Lat/long (28.688/81.49) are correct; the "Do not sync" is off; in the AP ASCOM v2 driver v5.30.10 lat and long are correct.  However, when I click Get Lat/Long from Mount, the Long direction flips from W to E. 
>
> I am not sure what else to sync or check but I am obviously something very basic.
>
> Bruce
>






--
TJF MOBILE


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

Ray Gralak
 

Mmmh, seems are getting a bit complicated I must admit. And now, when parking to position 5, the CW are
getting quite high !!!! What's happening ? Is is related to the "decimal" point that I changed :( ?
Yes, probably. Try parking to Park 3 which should place the counterweight shaft pointing to the ground. If it is not, then manually adjust the mount so that it is in the Park 3 position.

Also, I noticed a lot of failed network responses in your logs. Maybe the mount was powered off, but if not, it could be connection to the mount is not very solid.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
Sent: Saturday, October 16, 2021 3:43 PM
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!"

Hi Ray,

Mmmh, seems are getting a bit complicated I must admit. And now, when parking to position 5, the CW are
getting quite high !!!! What's happening ? Is is related to the "decimal" point that I changed :( ?

I apply your suggestions and let you know asap.

Regards,
Aygen

Le dim. 17 oct. 2021 à 00:18, Ray Gralak <iogroups@...> a écrit :


Hi Aygen,



I'm going to assume that all of your astronomy applications are now using "." instead of a comma as a
decimal point. If that is not the case, then you may need to change settings in those applications.



However, if all apps are using "." as a decimal point, then it could be a bad RECAL. APCC has
protection against bad plate solves or syncing on the wrong star in a planetarium program. But, if you are sure
that telescope pointing is off by 13.651 degrees, you can disable the setting "Prevent errant RECALs" in
APCC's advanced settings (see screenshot below). Make sure to enable it again after you have completed the
RECAL.









-Ray



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

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

> Sent: Saturday, October 16, 2021 2:59 PM

> 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 evening Ray,

>

> Thank you so much for your kind support, much appreciated. I did change the setting and it seems to
be

> working now.

>

> However, another message occurred :(

>

> * VPort 3 : Recal failed because it is too far (13.651 > 5 000 degrees) from current RA/Dec !

>

> I am honestly lost ! Don't know what's happening all of a sudden.

>

> Link to the log if needed : https://www.dropbox.com/s/cmfnj50px7c1zhv/ApccZip-
AYGEN_ERKASLAN-2021-

> 10-16-235257.zip?dl=0

>

> Best regards,

> Aygen

>

> Le sam. 16 oct. 2021 à 23:10, Ray Gralak <iogroups@...> a écrit :

>

>

> Hi Aygen ,

>

> I just got a chance to review your logs. The problem is the AP V2 ASCOM driver is trying to use
a

> comma as a decimal point, which is producing invalid coordinates in some cases. I am not sure why
this is

> just starting to happen, but you may need to adjust your Windows regional settings to use "." as a
decimal

> point.

>

> -Ray

>

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

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

> > Sent: Saturday, October 16, 2021 8:05 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!"

> >

> > Dear Ray,

> >

> > Thank you very much for your quick reply. Below is link to access the files.

> >

> > https://www.dropbox.com/s/lo9lxj6ggq9p6zo/AscomZip-Aygen-2021-10-16-165729.zip?dl=0

> >

> > In the meantime, I did follow one of your recommendation to delete the ap.ini files and re-do
the

> config "now"

> > of the AP Driver.

> >

> > Regards,

> > Aygen

> >

>

>

>

>

>

>

>

>








Re: IC 1805, Heart Nebula | Mach1 GTO3 | Takahashi ε-180ED

Don Anderson
 

Very well done! Gives the rest of us city imagers with severe light pollution something to strive for!
Don


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

Erkaslan Aygen
 

Hi Ray,

Mmmh, seems are getting a bit complicated I must admit. And now, when parking to position 5, the CW are getting quite high !!!! What's happening ? Is is related to the "decimal" point that I changed :( ?

I apply your suggestions and let you know asap.

Regards,
Aygen

Le dim. 17 oct. 2021 à 00:18, Ray Gralak <iogroups@...> a écrit :

Hi Aygen,

 

I'm going to assume that all of your astronomy applications are now using "." instead of a comma as a decimal point. If that is not the case, then you may need to change settings in those applications.

 

However, if all apps are using "." as a decimal point, then it could be a bad RECAL. APCC has protection against bad plate solves or syncing on the wrong star in a planetarium program. But, if you are sure that telescope pointing is off by 13.651 degrees, you can disable the setting "Prevent errant RECALs" in APCC's advanced settings (see screenshot below). Make sure to enable it again after you have completed the RECAL.

 

 

 

-Ray

 

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

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

> Sent: Saturday, October 16, 2021 2:59 PM

> 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 evening Ray,

>

> Thank you so much for your kind support, much appreciated. I did change the setting and it seems to be

> working now.

>

> However, another message occurred :(

>

> *       VPort 3 : Recal failed because it is too far (13.651 > 5 000 degrees) from current RA/Dec !

>

> I am honestly lost ! Don't know what's happening all of a sudden.

>

> Link to the log if needed : https://www.dropbox.com/s/cmfnj50px7c1zhv/ApccZip-AYGEN_ERKASLAN-2021-

> 10-16-235257.zip?dl=0

>

> Best regards,

> Aygen

>

> Le sam. 16 oct. 2021 à 23:10, Ray Gralak <iogroups@...> a écrit :

>

>

>          Hi Aygen ,

>

>          I just got a chance to review your logs. The problem is the AP V2 ASCOM driver is trying to use a

> comma as a decimal point, which is producing invalid coordinates in some cases. I am not sure why this is

> just starting to happen, but you may need to adjust your Windows regional settings to use "." as a decimal

> point.

>

>          -Ray

>

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

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

>          > Sent: Saturday, October 16, 2021 8:05 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!"

>          >

>          > Dear Ray,

>          >

>          > Thank you very much for your quick reply. Below is link to access the files.

>          >

>          > https://www.dropbox.com/s/lo9lxj6ggq9p6zo/AscomZip-Aygen-2021-10-16-165729.zip?dl=0

>          >

>          > In the meantime, I did follow one of your recommendation to delete the ap.ini files and re-do the

> config "now"

>          > of the AP Driver.

>          >

>          > Regards,

>          > Aygen

>          >

>

>

>

>

>

>

>

>


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

Ray Gralak
 

Hi Aygen,

 

I'm going to assume that all of your astronomy applications are now using "." instead of a comma as a decimal point. If that is not the case, then you may need to change settings in those applications.

 

However, if all apps are using "." as a decimal point, then it could be a bad RECAL. APCC has protection against bad plate solves or syncing on the wrong star in a planetarium program. But, if you are sure that telescope pointing is off by 13.651 degrees, you can disable the setting "Prevent errant RECALs" in APCC's advanced settings (see screenshot below). Make sure to enable it again after you have completed the RECAL.

 

 

 

-Ray

 

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

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

> Sent: Saturday, October 16, 2021 2:59 PM

> 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 evening Ray,

>

> Thank you so much for your kind support, much appreciated. I did change the setting and it seems to be

> working now.

>

> However, another message occurred :(

>

> *       VPort 3 : Recal failed because it is too far (13.651 > 5 000 degrees) from current RA/Dec !

>

> I am honestly lost ! Don't know what's happening all of a sudden.

>

> Link to the log if needed : https://www.dropbox.com/s/cmfnj50px7c1zhv/ApccZip-AYGEN_ERKASLAN-2021-

> 10-16-235257.zip?dl=0

>

> Best regards,

> Aygen

>

> Le sam. 16 oct. 2021 à 23:10, Ray Gralak <iogroups@...> a écrit :

>

>

>          Hi Aygen ,

>

>          I just got a chance to review your logs. The problem is the AP V2 ASCOM driver is trying to use a

> comma as a decimal point, which is producing invalid coordinates in some cases. I am not sure why this is

> just starting to happen, but you may need to adjust your Windows regional settings to use "." as a decimal

> point.

>

>          -Ray

>

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

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

>          > Sent: Saturday, October 16, 2021 8:05 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!"

>          >

>          > Dear Ray,

>          >

>          > Thank you very much for your quick reply. Below is link to access the files.

>          >

>          > https://www.dropbox.com/s/lo9lxj6ggq9p6zo/AscomZip-Aygen-2021-10-16-165729.zip?dl=0

>          >

>          > In the meantime, I did follow one of your recommendation to delete the ap.ini files and re-do the

> config "now"

>          > of the AP Driver.

>          >

>          > Regards,

>          > Aygen

>          >

>

>

>

>

>

>

>

>


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

Erkaslan Aygen
 

Good evening Ray,

Thank you so much for your kind support, much appreciated. I did change the setting and it seems to be working now. 

However, another message occurred :(
  • VPort 3 : Recal failed because it is too far (13.651 > 5 000 degrees) from current RA/Dec
I am honestly lost ! Don't know what's happening all of a sudden. 


Best regards,
Aygen

Le sam. 16 oct. 2021 à 23:10, Ray Gralak <iogroups@...> a écrit :
Hi Aygen ,

I just got a chance to review your logs. The problem is the AP V2 ASCOM driver is trying to use a comma as a decimal point, which is producing invalid coordinates in some cases. I am not sure why this is just starting to happen, but you may need to adjust your Windows regional settings to use "." as a decimal point.

-Ray

> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
> Sent: Saturday, October 16, 2021 8:05 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!"
>
> Dear Ray,
>
> Thank you very much for your quick reply. Below is link to access the files.
>
> https://www.dropbox.com/s/lo9lxj6ggq9p6zo/AscomZip-Aygen-2021-10-16-165729.zip?dl=0
>
> In the meantime, I did follow one of your recommendation to delete the ap.ini files and re-do the config "now"
> of the AP Driver.
>
> Regards,
> Aygen
>







Re: 1200 return to Park 5 with CWs up

Ray Gralak
 

Hi Peter,

Park 5 should have the shaft relatively horizontal. So when you say that the "CW's up", do you mean that the CW shaft just slightly off from being horizontal, or do you mean the mount tries to slew the scope underneath the mount?

If it's the former, that's typically okay as that can be caused by a Synch/Recal, or the pointing model changing the RA offset slightly.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Peter Bresler via groups.io
Sent: Saturday, October 16, 2021 11:31 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] 1200 return to Park 5 with CWs up

My 1200 keeps returning to Park 5 with the CWs up. I reset the location time, which appears to be correct.

https://www.dropbox.com/s/ub6xv4x3gvyni79/ApccZip-Peter_Bresler-2021-10-16-112232.zip?dl=0

Peter


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

Ray Gralak
 

Hi Aygen ,

I just got a chance to review your logs. The problem is the AP V2 ASCOM driver is trying to use a comma as a decimal point, which is producing invalid coordinates in some cases. I am not sure why this is just starting to happen, but you may need to adjust your Windows regional settings to use "." as a decimal point.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Erkaslan Aygen
Sent: Saturday, October 16, 2021 8:05 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!"

Dear Ray,

Thank you very much for your quick reply. Below is link to access the files.

https://www.dropbox.com/s/lo9lxj6ggq9p6zo/AscomZip-Aygen-2021-10-16-165729.zip?dl=0

In the meantime, I did follow one of your recommendation to delete the ap.ini files and re-do the config "now"
of the AP Driver.

Regards,
Aygen


Re: Is my LT2APM or 119FSA Miss-Drilled?

Mark Lamb
 


Here is a look from the bottom:


Is my LT2APM or 119FSA Miss-Drilled?

Mark Lamb
 
Edited

A couple days ago I received my AP1100 mount with a LT2APM  and 119FSA to mount on my Losmandy FHD tripod.

Today, I am assembling the AP1100 on the FHD tripod and I noticed some problems, as the holes of the LT2APM and 119FSA do not line up in the proper orientation.

According the the AP1100 manual, the counterweights should be directly over the North tripod leg.  I cannot get the pieces to align this way when using 4 screws between the LT2AP and 119FSA.  Proper alignment is possible using only 2 screws, but the manual says to use 4.  None of the other 6 holes on the LT2APM line up with the 119FSA.

I can line up 4 holes, but counterweights will be offset from the North leg.

Is the LT2APM or 119FSA Miss-Drilled?

Is using 2 screws, with the CW directly over the N leg stable enough?

Is using 4 screws, but with the CW offset vs. the N leg stable enough?

The photo below has the proper orientation, with all the tripod legs being aligned with the inside "triangle" holes on the LT2APM, and the AP1100 will thread into the 6 holes on the 119FSA  collar, resulting in good aligment, but with only 2 screws fastening.  None of the other 6 holes of the 119FSA line up with the LT2APM.



Re: Setting up NINA

ap@CaptivePhotons.com
 

Bruce Donzanti, wearing an orange robe, wrote:

 

  • Nepal did look interesting in Raiders of the Lost Ark :-).

 

The default version of NINA is free.

 

A very special, extremely expensive version, that teleports you to the latitude/longitude entered is much more expensive.   😊

 

Glad it's sorted.

 

Linwood

 


Re: Setting up NINA

Bruce Donzanti
 

I can't stop laughing along with having MORON written on my forehead.  I just responded to you in Discord- that fixed the problem.  Nepal did look interesting in Raiders of the Lost Ark :-).


1200 return to Park 5 with CWs up

Peter Bresler
 

My 1200 keeps returning to Park 5 with the CWs up. I reset the location time, which appears to be correct.

https://www.dropbox.com/s/ub6xv4x3gvyni79/ApccZip-Peter_Bresler-2021-10-16-112232.zip?dl=0

Peter


Re: Setting up NINA

KHursh
 

Maybe you live in MINUS 81.49 degrees longitude?


Re: Setting up NINA

Dale Ghent
 

Hi Bruce,

How is the weather in Nepal these days? ;)

In NINA, a north latitude is positive and a west longitude is negative. You note a lat/long of "28.688/81.49" in your message, which would put you at a very picturesque yet pretty remote corner of Nepal, not perhaps a more likely location of southern California.

/dale

On Oct 16, 2021, at 13:43, Bruce Donzanti <donza2735@...> wrote:

Thanks Linwood.

I went down your checklist of items and was testing during the day. It is still not slewing to the correct coordinates that I enter. Also, the Sky Atlas is showing the correct coordinates as expected but the transit time for an object is way off, still indicating the mount thinks it is elsewhere. It will return correctly to park 4. So, I am still at a loss what else to check. Lat/long (28.688/81.49) are correct; the "Do not sync" is off; in the AP ASCOM v2 driver v5.30.10 lat and long are correct. However, when I click Get Lat/Long from Mount, the Long direction flips from W to E.

I am not sure what else to sync or check but I am obviously something very basic.

Bruce


Re: Setting up NINA

Bruce Donzanti
 

Thanks Linwood.

I went down your checklist of items and was testing during the day.  It is still not slewing to the correct coordinates that I enter.  Also, the Sky Atlas is showing the correct coordinates as expected but the transit time for an object is way off, still indicating the mount thinks it is elsewhere.  It will return correctly to park 4.  So, I am still at a loss what else to check.  Lat/long (28.688/81.49) are correct; the "Do not sync" is off; in the AP ASCOM v2 driver v5.30.10 lat and long are correct.  However, when I click Get Lat/Long from Mount, the Long direction flips from W to E.  

I am not sure what else to sync or check but I am obviously something very basic.

Bruce


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

Erkaslan Aygen
 

Hi Ray,

I am very sorry, my bad. Please find below the requested files.

https://www.dropbox.com/s/wxs42bdenxmgc30/ApccZip-AYGEN_ERKASLAN-2021-10-16-184807.zip?dl=0

Thank you for your support.

Best regards,
Aygen


Re: WoW! Another APOD for Ignacio

Richard Hennig
 

Really impressive. The detail is outstanding. Congratulations Ignacio!


On Oct 15, 2021, at 10:27 PM, Roland Christen via groups.io <chris1011@...> wrote:


With his 168mm refractor that I made from some one-off glass I had on hand. Maybe I should make some more of them?

Anyway, congratulations Ignacio. You are making good use of that scope.

Rolando

--
Roland Christen
Astro-Physics


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

Ray Gralak
 

Hi Aygen,

 

Unfortunately, you used the AP V2 Log Zipper and not the APCC log zipper, so there are no APCC logs.

 

So, please use the APCC log zipper to zip the APCC logs. You can run the APCC log zipper from APCC's Tools menu, as shown in this screenshot:

 

 

Thanks!

 

-Ray

 

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

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

> Sent: Saturday, October 16, 2021 8:05 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!"

>

> Dear Ray,

>

> Thank you very much for your quick reply. Below is link to access the files.

>

> https://www.dropbox.com/s/lo9lxj6ggq9p6zo/AscomZip-Aygen-2021-10-16-165729.zip?dl=0

>

> In the meantime, I did follow one of your recommendation to delete the ap.ini files and re-do the config "now"

> of the AP Driver.

>

> Regards,

> Aygen


IC 1805, Heart Nebula | Mach1 GTO3 | Takahashi ε-180ED

mftoet
 
Edited

Very happy owner of a Mach1 GTO3 since 2012. That mount honestly never let me down! Since a year it’s permanently placed in my backyard roll-off roof observatory. Where I live light pollution is severe. That means narrowband filters for deep sky imaging. 

I would like to share an image of the Heart Nebula with a little more than 29 hours of integration time through the new Baader Planetarium CMOS optimised Ultra-Highspeed SII (4nm), Hα (3.5nm) and OIII (4nm) filters mapped in Hubble palette. Captured with a Takahashi Epsilon-180ED f/2.8 and ZWO ASI294MM Pro camera. Pre-processing was done in Astro Pixel Processor. Post-processing in Adobe Photoshop. For post-processing the stars where separated from the nebulas with Russell Croman's excellent new 'StarXTerminator' plug-in. Thanks for watching!

https://www.mauricetoet.nl/DeepSky/i-khbKmLt/A

 

4561 - 4580 of 86825