1200 not taking SGP corrections


Peter Bresler
 

Plate solve corrections generated by SGP are not being made by my 1200. The plate solve may work as a blind solve or direct solve by PS2, the error is shown, but on the next try there is no change in the error. I tried a couple of different computers, thinking there might be some problem with the settings.

https://www.dropbox.com/s/v2simav8cflq749/ApccZip-Peter_Bresler-2021-08-01-011435.zip?dl=0


Bill Long
 

Not sure this is causing your problem, but this warning entry is all over the place in the log:



Is your site information correct? If not, update it and reboot the mount and try again.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Peter Bresler via groups.io <PABresler@...>
Sent: Sunday, August 1, 2021 2:01 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] 1200 not taking SGP corrections
 
Plate solve corrections generated by SGP are not being made by my 1200. The plate solve may work as a blind solve or direct solve by PS2, the error is shown, but on the next try there is no change in the error. I tried a couple of different computers, thinking there might be some problem with the settings.

https://www.dropbox.com/s/v2simav8cflq749/ApccZip-Peter_Bresler-2021-08-01-011435.zip?dl=0


Ray Gralak
 

Bill is correct. Not only that, both Latitude and Longitude are incorrectly set to 0 at one point:

 

0000050 2021-08-01 00:40:54.250:      Debug,  Command Thread, TX = ':Gt#'

0000051 2021-08-01 00:40:54.250:      Debug,        UDP Send, --> :Gt#   Timeout(msecs)= 100

0000052 2021-08-01 00:40:54.252:      Debug,        UDPReply, <-- +00*00:00#      (1 msecs)

0000053 2021-08-01 00:40:54.252:      Debug,  Command Thread, TX=':Gt#'|RX='+00*00:00#'

0000054 2021-08-01 00:40:54.253:      Debug,  Command Thread, TX = ':Gg#'

0000055 2021-08-01 00:40:54.253:      Debug,        UDP Send, --> :Gg#   Timeout(msecs)= 100

0000056 2021-08-01 00:40:54.255:      Debug,        UDPReply, <-- +00*00:00#      (2 msecs)

0000057 2021-08-01 00:40:54.255:      Debug,  Command Thread, TX=':Gg#'|RX='+00*00:00#'

 

Power off the mount if it is not off already. Then power on the mount and run APCC . Watch APCC to make sure that it initializes the mount with the proper Lat/Long values. If something else initializes the mount first (e.g. the keypad?) you will not see APCC’s popup initialization window, and APCC will not set the mount’s latitude and longitude. You can check thevalues set in the mount on APCC’s Site tab.

 

-Ray

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Sunday, August 1, 2021 2:14 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] 1200 not taking SGP corrections

 

Not sure this is causing your problem, but this warning entry is all over the place in the log:

 

 

Is your site information correct? If not, update it and reboot the mount and try again.

 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Peter Bresler via groups.io <PABresler@...>
Sent: Sunday, August 1, 2021 2:01 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] 1200 not taking SGP corrections

 

Plate solve corrections generated by SGP are not being made by my 1200. The plate solve may work as a blind solve or direct solve by PS2, the error is shown, but on the next try there is no change in the error. I tried a couple of different computers, thinking there might be some problem with the settings.

https://www.dropbox.com/s/v2simav8cflq749/ApccZip-Peter_Bresler-2021-08-01-011435.zip?dl=0


Peter Bresler
 

I did manually enter the lat and longitude, and also powered the mount off several times and restarted APCC. The problem persisted. It mostly affected the DEC axis, but once the RA also did not correct. The cables look good, as usual. No other obvious problems. I will not be able to try again until I return from vacation in 3 weeks. What else do you suggest? I send an email to George.

I made a previous post about PHD not being able to make DEC corrections, but assumed that was a problem with the guide star.


Christopher Erickson
 

Where did you enter your lat/lon numbers?

-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   

On Sun, Aug 1, 2021, 7:16 AM Peter Bresler via groups.io <PABresler=aol.com@groups.io> wrote:
I did manually enter the lat and longitude, and also powered the mount off several times and restarted APCC. The problem persisted. It mostly affected the DEC axis, but once the RA also did not correct. The cables look good, as usual. No other obvious problems. I will not be able to try again until I return from vacation in 3 weeks. What else do you suggest? I send an email to George.

I made a previous post about PHD not being able to make DEC corrections, but assumed that was a problem with the guide star.


Peter Bresler
 
Edited

Los Osos
 
35° 18' 36.54'' N
 
120° 49' 31.5804'' W

I entered them in the ASCOM driver. Finally I rechecked that driver and they were there.


Ray Gralak
 

Hi Peter,

 

> I entered them in the ASCOM driver. Finally I rechecked that driver and they were there.

 

If you are using APCC with the ASCOM driver, then APCC will initialize the mount. So, the place you should set up the lat/long coordinates is in the Sites dialog in APCC. Here's a screenshot:

 

 

-Ray

 


Peter Bresler
 

Thanks.I will give it another shot in a couple of weeks.