Date   

Re: AP1100 Newbie Question

Mark Lamb
 

No automated rotator, but I have a dovetail type (w/ 3 screws) rotating adapter from my Vixen FL55ss drawtube to M48.  I manually set the camera angle using levels or the BuckeyeStarGazer's triple camera rotation levels, so it needs a flat reference point, which I use as the Park 3 position (assuming the mount was perfectly level).  With the AP1100's RA and Dec reference marks, I will be off to the extent the tripod is not exactly level.

With my other scopes, SVX130T, Esprit 100, and EdgeHD 925, I will be doing something similar, using the same ~ Park 3 position and either rotating the focuser, the scope in rings, or the COAG's dovetail rotation.


Re: APCC/Driver exception

Ray Gralak
 

Dave,

so why after slewing to M76 was APCC/driver reporting "at park"? is there a command that
could cause it?
Did you look at the log you posted? At the top of the log:

CCDCommander
23:32:42 Starting imager exposure (6 of 6).
23:40:33 Very cloudy condition detected! Pausing Action List.23:40:33 Very cloudy condition detected! Pausing Action List.
23:40:33 Parking mount...
23:41:58 Done parking!

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of david w pearson via groups.io
Sent: Wednesday, November 3, 2021 7:33 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC/Driver exception

Is it possible that after slewing to M76, a "park" was issued and before ASCOM/driver could respond or the
mount move, there was a slew issued?
dave

On Wednesday, November 3, 2021, 06:49:17 PM PDT, david w pearson <p.davidw@...> wrote:


thanks,,,,but a question because i am still confused......according to APCC log.....the mount had slewed to
M76 and "at park" was true...and when told to slew to Sh2-234 got the exception because it was thinking it
was parked. so why after slewing to M76 was APCC/driver reporting "at park"? is there a command that
could cause it?
dave

On Wednesday, November 3, 2021, 06:11:25 PM PDT, Bill Long <bill@...> wrote:


The mount is parked and is being asked to slew. That is not a legal operation. Matt should unpark the mount if
it is parked and CCD Commander wants to slew the mount.

335589 2021-11-03 01:59:07.122: ASCOM: Info : GET Connected = True
335590 2021-11-03 01:59:07.123: ASCOM: Info : GET RightAscension = 1.74197222222222
335591 2021-11-03 01:59:07.123: ASCOM: Info : GET Declination = 51.4927777777778
335592 2021-11-03 01:59:07.123: ASCOM: Info : GET Tracking = False
335593 2021-11-03 01:59:07.124: ASCOM: Info : GET Slewing = False, MoveAxis(0)=0,
MoveAxis(1)=0
335594 2021-11-03 01:59:07.145: ASCOM: Info : GET AtPark = True
335595 2021-11-03 01:59:07.180: ASCOM: Info : GET SideOfPier = East
335596 2021-11-03 01:59:07.296: ASCOM: Info : GET Connected = True
335597 2021-11-03 01:59:07.387: Driver: Info : CommandString TX=':GR#'
335598 2021-11-03 01:59:07.403: Driver: Info : CommandString: APCC response:
':APCC,109370,GR#', Response='01:44:32.1#'
335599 2021-11-03 01:59:07.558: Driver: Info : CommandString TX=':GD#'
335600 2021-11-03 01:59:07.575: Driver: Info : CommandString: APCC response:
':APCC,109371,GD#', Response='+51*29:34#'
335601 2021-11-03 01:59:07.885: Driver: Info : CommandString TX=':GOS#'
335602 2021-11-03 01:59:07.902: Driver: Info : CommandString: APCC response:
':APCC,109372,GOS#', Response='P99000200P000#'
335603 2021-11-03 01:59:07.904: Driver: Info : CommandString TX=':GS#'
335604 2021-11-03 01:59:07.918: Driver: Info : CommandString: APCC response:
':APCC,109373,GS#', Response='03:47:42.8#'
335605 2021-11-03 01:59:07.971: ASCOM: Info : GET RightAscension = 1.74225
335606 2021-11-03 01:59:07.972: ASCOM: Info : GET SiderealTime = 3.79523972222222
335607 2021-11-03 01:59:07.972: ASCOM: Info : GET RightAscension = 1.74225
335608 2021-11-03 01:59:07.972: ASCOM: Info : GET SiderealTime = 3.79523972222222
335609 2021-11-03 01:59:07.973: ASCOM: Info : GET SiderealTime = 3.79523972222222
335610 2021-11-03 01:59:07.973: ASCOM: Info : GET RightAscension = 1.74225
335611 2021-11-03 01:59:07.973: ASCOM: Info : GET SiderealTime = 3.79523972222222
335612 2021-11-03 01:59:07.973: ASCOM: Info : GET RightAscension = 1.74225
335613 2021-11-03 01:59:07.973: ASCOM: Info : GET SiderealTime = 3.79523972222222
335614 2021-11-03 01:59:07.973: ASCOM: Info : GET SiderealTime = 3.79523972222222
335615 2021-11-03 01:59:07.974: ASCOM: Info : GET RightAscension = 1.74225
335616 2021-11-03 01:59:07.974: ASCOM: Info : GET Declination = 51.4927777777778
335617 2021-11-03 01:59:07.974: ASCOM: Info : GET RightAscension = 1.74225
335618 2021-11-03 01:59:07.974: ASCOM: Info : GET Declination = 51.4927777777778
335619 2021-11-03 01:59:07.974: ASCOM: Info : GET Slewing = False, MoveAxis(0)=0,
MoveAxis(1)=0
335620 2021-11-03 01:59:08.055: ASCOM: Info : GET SiderealTime = 3.79526138888889
335621 2021-11-03 01:59:08.055: ASCOM: Info : GET SiderealTime = 3.79526138888889
335622 2021-11-03 01:59:08.056: ASCOM: Info : GET SiderealTime = 3.79526138888889
335623 2021-11-03 01:59:08.056: ASCOM: Info : GET SiderealTime = 3.79526138888889
335624 2021-11-03 01:59:08.062: ASCOM: Info : SlewToCoordinatesAsync() RA=5.49582868725247,
Dec=34.4413830565668
335625 2021-11-03 01:59:08.062: check_connected: Exception : bMustNotBeParked and g_bParked: True,
True : SlewToCoordinatesAsync




________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of david w pearson via groups.io
<p.davidw@...>
Sent: Wednesday, November 3, 2021 4:51 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] APCC/Driver exception

Hi Ray,

I am getting this error from ASCOM/driver

"check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsyn"

Do you have any insight on this exception and what may cause it?

Background.
I use CCDCommander for my auto imaging script.
After parking the mount due to bad weather/Roof Closure, and being in a weather pause for maybe hours, i
get this error after coming out of a weather pause and restarting my imaging session.

CCDCommander log
01:59:08 JNow Coordinates: RA: 05h 29m 45.0s Dec: +34°26'29"
01:59:08 Slewing to Sh2-234...
01:59:08 Error Number: -2147220471
01:59:08 Illegal operation while parked

I have enclosed a summary txt file of CCDCommander and APCC(to shorter the search)

In summary....CCDCommander goes into weather pause, and tells APCC/driver to park and it does.
After the weather pause, CCDCommander tells APCC/driver to go to last image and it appears to do
that.....however, "at park" stays true.

question here.....when "at park" is true, does this just mean not slewing or tracking? Slewing and tracking
stays false.

CCDCommander discovers that the last object is not the planned object due to the weather delay, and tells
APCC/driver to slew to correct object, and the Exception occurs.

Mount is parked at alt/az of the last object when exception occurred and of course is still there upon
observing the mount next morning.

I realize my issue is an interface issue between the mount and CCDCommander, but maybe if there some
possible issues
that make this happen i can work around it or get Matt at CCDCommander to fix.

This has been a CCDCommander issue since i started in 2010 and has been noted by others over the years.
I have talked to Matt about it and he has given me workarounds to try, but none have worked.

So i decided to try to figure it out myself, and pass info over to Matt.

Any ideas what is causing the APCC exception?

I know this is not really your issue.....but a lot of us have been struggling with this for some time......you are
probably our last hope.(pun intended!)
Thanks... if you choose to accept this challenge!! Hopefully easy for you!

dave


Re: How often do people refresh their All-Sky Pointing Model? (Observatory)

Marcelo Figueroa
 


I do unguided imaging and I do it when I notice that my stars start to appear oval.
 
It happens when the temperature changes significantly from winter to summer, if I did the modeling during a cold winter night it works fine for several months, however at some point in the summer it stops working and the stars appear oval. It is time to redo the modeling.


Re: TPoint vs. APPM -- Translation Possible?

mjb87@...
 

i'll give that a try. May be a week or two before I can.


Re: APCC/Driver exception

david w pearson
 

Is it possible that after slewing to M76, a "park" was issued and before ASCOM/driver could respond or the mount move,  there was a slew issued?
dave

On Wednesday, November 3, 2021, 06:49:17 PM PDT, david w pearson <p.davidw@...> wrote:


thanks,,,,but a question because i am still confused......according to APCC log.....the mount had slewed to M76 and "at park" was true...and when told to slew to Sh2-234 got the exception because it was thinking it was parked.    so why after slewing to M76 was APCC/driver reporting "at park"?   is there a command that could cause it?
dave

On Wednesday, November 3, 2021, 06:11:25 PM PDT, Bill Long <bill@...> wrote:


The mount is parked and is being asked to slew. That is not a legal operation. Matt should unpark the mount if it is parked and CCD Commander wants to slew the mount. 

335589 2021-11-03 01:59:07.122:            ASCOM: Info      : GET Connected = True
335590 2021-11-03 01:59:07.123:            ASCOM: Info      : GET RightAscension = 1.74197222222222
335591 2021-11-03 01:59:07.123:            ASCOM: Info      : GET Declination = 51.4927777777778
335592 2021-11-03 01:59:07.123:            ASCOM: Info      : GET Tracking = False
335593 2021-11-03 01:59:07.124:            ASCOM: Info      : GET Slewing = False, MoveAxis(0)=0, MoveAxis(1)=0
335594 2021-11-03 01:59:07.145:            ASCOM: Info      : GET AtPark = True
335595 2021-11-03 01:59:07.180:            ASCOM: Info      : GET SideOfPier = East
335596 2021-11-03 01:59:07.296:            ASCOM: Info      : GET Connected = True
335597 2021-11-03 01:59:07.387:           Driver: Info      : CommandString TX=':GR#'
335598 2021-11-03 01:59:07.403:           Driver: Info      : CommandString: APCC response: ':APCC,109370,GR#', Response='01:44:32.1#'
335599 2021-11-03 01:59:07.558:           Driver: Info      : CommandString TX=':GD#'
335600 2021-11-03 01:59:07.575:           Driver: Info      : CommandString: APCC response: ':APCC,109371,GD#', Response='+51*29:34#'
335601 2021-11-03 01:59:07.885:           Driver: Info      : CommandString TX=':GOS#'
335602 2021-11-03 01:59:07.902:           Driver: Info      : CommandString: APCC response: ':APCC,109372,GOS#', Response='P99000200P000#'
335603 2021-11-03 01:59:07.904:           Driver: Info      : CommandString TX=':GS#'
335604 2021-11-03 01:59:07.918:           Driver: Info      : CommandString: APCC response: ':APCC,109373,GS#', Response='03:47:42.8#'
335605 2021-11-03 01:59:07.971:            ASCOM: Info      : GET RightAscension = 1.74225
335606 2021-11-03 01:59:07.972:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335607 2021-11-03 01:59:07.972:            ASCOM: Info      : GET RightAscension = 1.74225
335608 2021-11-03 01:59:07.972:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335609 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335610 2021-11-03 01:59:07.973:            ASCOM: Info      : GET RightAscension = 1.74225
335611 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335612 2021-11-03 01:59:07.973:            ASCOM: Info      : GET RightAscension = 1.74225
335613 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335614 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335615 2021-11-03 01:59:07.974:            ASCOM: Info      : GET RightAscension = 1.74225
335616 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Declination = 51.4927777777778
335617 2021-11-03 01:59:07.974:            ASCOM: Info      : GET RightAscension = 1.74225
335618 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Declination = 51.4927777777778
335619 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Slewing = False, MoveAxis(0)=0, MoveAxis(1)=0
335620 2021-11-03 01:59:08.055:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335621 2021-11-03 01:59:08.055:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335622 2021-11-03 01:59:08.056:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335623 2021-11-03 01:59:08.056:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335624 2021-11-03 01:59:08.062:            ASCOM: Info      : SlewToCoordinatesAsync() RA=5.49582868725247, Dec=34.4413830565668
335625 2021-11-03 01:59:08.062:  check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsync




From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of david w pearson via groups.io <p.davidw@...>
Sent: Wednesday, November 3, 2021 4:51 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] APCC/Driver exception
 
Hi Ray,
 
I am getting this error from ASCOM/driver
 
"check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsyn"
 
Do you have any insight on this exception and what may cause it?
 
Background.
I use CCDCommander for my auto imaging script.
After parking the mount due to bad weather/Roof Closure, and being in a weather pause for maybe hours, i get this error after coming out of a weather pause and restarting my imaging session.
 
CCDCommander log
01:59:08  JNow Coordinates: RA: 05h 29m 45.0s Dec: +34°26'29"
01:59:08  Slewing to Sh2-234...
01:59:08  Error Number: -2147220471
01:59:08  Illegal operation while parked
 
I have enclosed a summary txt file of CCDCommander and APCC(to shorter the search)
 
In summary....CCDCommander goes into weather pause, and tells APCC/driver to park and it does.
After the weather pause, CCDCommander tells APCC/driver to go to last image and it appears to do that.....however, "at park" stays true.
 
question here.....when "at park" is true, does this just mean not slewing or tracking?   Slewing and tracking stays false.
 
CCDCommander discovers that the last object is not the planned  object due to the weather delay, and tells APCC/driver to slew to correct object, and the Exception occurs.
 
Mount is parked at alt/az of the last object when exception occurred and of course is still there upon observing the mount next morning.
 
I realize my issue is an interface issue between the mount and CCDCommander, but maybe if there some possible issues 
that make this happen i can work around it or get Matt at CCDCommander to fix.
 
This has been a CCDCommander issue since i started in 2010 and has been noted by others over the years.    I have talked to Matt about it and he has given me workarounds to try, but none have worked.
 
So i decided to try to figure it out myself, and pass info over to Matt.
 
Any ideas what is causing  the APCC exception?
 
I know this is not really your issue.....but a lot of us have been struggling with this for some time......you are probably our last hope.(pun intended!)
Thanks... if you choose to accept this challenge!!   Hopefully easy for you!
 
dave


Re: APCC Pro Error FindFreeQacindex: no free entries!

Chris White
 

Well, in any event it sounds like its not serious.  Thanks for looking.


Re: APCC/Driver exception

david w pearson
 

thanks,,,,but a question because i am still confused......according to APCC log.....the mount had slewed to M76 and "at park" was true...and when told to slew to Sh2-234 got the exception because it was thinking it was parked.    so why after slewing to M76 was APCC/driver reporting "at park"?   is there a command that could cause it?
dave

On Wednesday, November 3, 2021, 06:11:25 PM PDT, Bill Long <bill@...> wrote:


The mount is parked and is being asked to slew. That is not a legal operation. Matt should unpark the mount if it is parked and CCD Commander wants to slew the mount. 

335589 2021-11-03 01:59:07.122:            ASCOM: Info      : GET Connected = True
335590 2021-11-03 01:59:07.123:            ASCOM: Info      : GET RightAscension = 1.74197222222222
335591 2021-11-03 01:59:07.123:            ASCOM: Info      : GET Declination = 51.4927777777778
335592 2021-11-03 01:59:07.123:            ASCOM: Info      : GET Tracking = False
335593 2021-11-03 01:59:07.124:            ASCOM: Info      : GET Slewing = False, MoveAxis(0)=0, MoveAxis(1)=0
335594 2021-11-03 01:59:07.145:            ASCOM: Info      : GET AtPark = True
335595 2021-11-03 01:59:07.180:            ASCOM: Info      : GET SideOfPier = East
335596 2021-11-03 01:59:07.296:            ASCOM: Info      : GET Connected = True
335597 2021-11-03 01:59:07.387:           Driver: Info      : CommandString TX=':GR#'
335598 2021-11-03 01:59:07.403:           Driver: Info      : CommandString: APCC response: ':APCC,109370,GR#', Response='01:44:32.1#'
335599 2021-11-03 01:59:07.558:           Driver: Info      : CommandString TX=':GD#'
335600 2021-11-03 01:59:07.575:           Driver: Info      : CommandString: APCC response: ':APCC,109371,GD#', Response='+51*29:34#'
335601 2021-11-03 01:59:07.885:           Driver: Info      : CommandString TX=':GOS#'
335602 2021-11-03 01:59:07.902:           Driver: Info      : CommandString: APCC response: ':APCC,109372,GOS#', Response='P99000200P000#'
335603 2021-11-03 01:59:07.904:           Driver: Info      : CommandString TX=':GS#'
335604 2021-11-03 01:59:07.918:           Driver: Info      : CommandString: APCC response: ':APCC,109373,GS#', Response='03:47:42.8#'
335605 2021-11-03 01:59:07.971:            ASCOM: Info      : GET RightAscension = 1.74225
335606 2021-11-03 01:59:07.972:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335607 2021-11-03 01:59:07.972:            ASCOM: Info      : GET RightAscension = 1.74225
335608 2021-11-03 01:59:07.972:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335609 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335610 2021-11-03 01:59:07.973:            ASCOM: Info      : GET RightAscension = 1.74225
335611 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335612 2021-11-03 01:59:07.973:            ASCOM: Info      : GET RightAscension = 1.74225
335613 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335614 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335615 2021-11-03 01:59:07.974:            ASCOM: Info      : GET RightAscension = 1.74225
335616 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Declination = 51.4927777777778
335617 2021-11-03 01:59:07.974:            ASCOM: Info      : GET RightAscension = 1.74225
335618 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Declination = 51.4927777777778
335619 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Slewing = False, MoveAxis(0)=0, MoveAxis(1)=0
335620 2021-11-03 01:59:08.055:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335621 2021-11-03 01:59:08.055:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335622 2021-11-03 01:59:08.056:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335623 2021-11-03 01:59:08.056:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335624 2021-11-03 01:59:08.062:            ASCOM: Info      : SlewToCoordinatesAsync() RA=5.49582868725247, Dec=34.4413830565668
335625 2021-11-03 01:59:08.062:  check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsync




From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of david w pearson via groups.io <p.davidw@...>
Sent: Wednesday, November 3, 2021 4:51 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] APCC/Driver exception
 
Hi Ray,
 
I am getting this error from ASCOM/driver
 
"check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsyn"
 
Do you have any insight on this exception and what may cause it?
 
Background.
I use CCDCommander for my auto imaging script.
After parking the mount due to bad weather/Roof Closure, and being in a weather pause for maybe hours, i get this error after coming out of a weather pause and restarting my imaging session.
 
CCDCommander log
01:59:08  JNow Coordinates: RA: 05h 29m 45.0s Dec: +34°26'29"
01:59:08  Slewing to Sh2-234...
01:59:08  Error Number: -2147220471
01:59:08  Illegal operation while parked
 
I have enclosed a summary txt file of CCDCommander and APCC(to shorter the search)
 
In summary....CCDCommander goes into weather pause, and tells APCC/driver to park and it does.
After the weather pause, CCDCommander tells APCC/driver to go to last image and it appears to do that.....however, "at park" stays true.
 
question here.....when "at park" is true, does this just mean not slewing or tracking?   Slewing and tracking stays false.
 
CCDCommander discovers that the last object is not the planned  object due to the weather delay, and tells APCC/driver to slew to correct object, and the Exception occurs.
 
Mount is parked at alt/az of the last object when exception occurred and of course is still there upon observing the mount next morning.
 
I realize my issue is an interface issue between the mount and CCDCommander, but maybe if there some possible issues 
that make this happen i can work around it or get Matt at CCDCommander to fix.
 
This has been a CCDCommander issue since i started in 2010 and has been noted by others over the years.    I have talked to Matt about it and he has given me workarounds to try, but none have worked.
 
So i decided to try to figure it out myself, and pass info over to Matt.
 
Any ideas what is causing  the APCC exception?
 
I know this is not really your issue.....but a lot of us have been struggling with this for some time......you are probably our last hope.(pun intended!)
Thanks... if you choose to accept this challenge!!   Hopefully easy for you!
 
dave


Re: APCC/Driver exception

Ray Gralak
 

01:59:08 Illegal operation while parked
I think this says it all! The mount needs to be unparked before attempting a slew.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of david w pearson via groups.io
Sent: Wednesday, November 3, 2021 4:52 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC/Driver exception

Hi Ray,

I am getting this error from ASCOM/driver

"check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsyn"

Do you have any insight on this exception and what may cause it?

Background.
I use CCDCommander for my auto imaging script.
After parking the mount due to bad weather/Roof Closure, and being in a weather pause for maybe hours, i
get this error after coming out of a weather pause and restarting my imaging session.

CCDCommander log
01:59:08 JNow Coordinates: RA: 05h 29m 45.0s Dec: +34°26'29"
01:59:08 Slewing to Sh2-234...
01:59:08 Error Number: -2147220471
01:59:08 Illegal operation while parked

I have enclosed a summary txt file of CCDCommander and APCC(to shorter the search)

In summary....CCDCommander goes into weather pause, and tells APCC/driver to park and it does.
After the weather pause, CCDCommander tells APCC/driver to go to last image and it appears to do
that.....however, "at park" stays true.

question here.....when "at park" is true, does this just mean not slewing or tracking? Slewing and tracking
stays false.

CCDCommander discovers that the last object is not the planned object due to the weather delay, and tells
APCC/driver to slew to correct object, and the Exception occurs.

Mount is parked at alt/az of the last object when exception occurred and of course is still there upon
observing the mount next morning.

I realize my issue is an interface issue between the mount and CCDCommander, but maybe if there some
possible issues
that make this happen i can work around it or get Matt at CCDCommander to fix.

This has been a CCDCommander issue since i started in 2010 and has been noted by others over the years.
I have talked to Matt about it and he has given me workarounds to try, but none have worked.

So i decided to try to figure it out myself, and pass info over to Matt.

Any ideas what is causing the APCC exception?

I know this is not really your issue.....but a lot of us have been struggling with this for some time......you are
probably our last hope.(pun intended!)
Thanks... if you choose to accept this challenge!! Hopefully easy for you!

dave


Re: APCC Pro Error FindFreeQacindex: no free entries!

Ray Gralak
 

It sounds like the ASCOM hub is blocking APCC in some way. I'll see if it is possible to move the hub off to another thread so they won't interfere. If I can do that, it will be in the next build.

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Chris White
Sent: Wednesday, November 3, 2021 4:13 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] APCC Pro Error FindFreeQacindex: no free entries!

Ray. It seems to happen when I am either accessing or closing the ASCOM Hub Properties. I switchde from
using the ASCOM Hub to the ASCOM Lunatico driver and I dont seem to get the error anymore. I'm not sure it
is able to access all the data that the device can generate, but I get RH, Temp, Barometer and Dew Point.. so I
guess that is sufficient for the purposes of APCC.


Re: TPoint vs. APPM -- Translation Possible?

Ray Gralak
 

Marty,

Can you expose a little longer, say 10 seconds, to get a deeper image?

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of mjb87 via groups.io
Sent: Wednesday, November 3, 2021 2:02 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] TPoint vs. APPM -- Translation Possible?

Hi Ray... I have not tried the automatic TPoint modeling methodology yet.

To my uneducated eyes, it seems the problem is that the platesolving routines, given the very low FoV,
cannot identify enough stars above the underlying noise caused by mediocre seeing. So I get failed solutions
or erroneous solutions. Not sure denser data is the solution.

Marty


Re: APCC/Driver exception

Bill Long
 

The mount is parked and is being asked to slew. That is not a legal operation. Matt should unpark the mount if it is parked and CCD Commander wants to slew the mount. 

335589 2021-11-03 01:59:07.122:            ASCOM: Info      : GET Connected = True
335590 2021-11-03 01:59:07.123:            ASCOM: Info      : GET RightAscension = 1.74197222222222
335591 2021-11-03 01:59:07.123:            ASCOM: Info      : GET Declination = 51.4927777777778
335592 2021-11-03 01:59:07.123:            ASCOM: Info      : GET Tracking = False
335593 2021-11-03 01:59:07.124:            ASCOM: Info      : GET Slewing = False, MoveAxis(0)=0, MoveAxis(1)=0
335594 2021-11-03 01:59:07.145:            ASCOM: Info      : GET AtPark = True
335595 2021-11-03 01:59:07.180:            ASCOM: Info      : GET SideOfPier = East
335596 2021-11-03 01:59:07.296:            ASCOM: Info      : GET Connected = True
335597 2021-11-03 01:59:07.387:           Driver: Info      : CommandString TX=':GR#'
335598 2021-11-03 01:59:07.403:           Driver: Info      : CommandString: APCC response: ':APCC,109370,GR#', Response='01:44:32.1#'
335599 2021-11-03 01:59:07.558:           Driver: Info      : CommandString TX=':GD#'
335600 2021-11-03 01:59:07.575:           Driver: Info      : CommandString: APCC response: ':APCC,109371,GD#', Response='+51*29:34#'
335601 2021-11-03 01:59:07.885:           Driver: Info      : CommandString TX=':GOS#'
335602 2021-11-03 01:59:07.902:           Driver: Info      : CommandString: APCC response: ':APCC,109372,GOS#', Response='P99000200P000#'
335603 2021-11-03 01:59:07.904:           Driver: Info      : CommandString TX=':GS#'
335604 2021-11-03 01:59:07.918:           Driver: Info      : CommandString: APCC response: ':APCC,109373,GS#', Response='03:47:42.8#'
335605 2021-11-03 01:59:07.971:            ASCOM: Info      : GET RightAscension = 1.74225
335606 2021-11-03 01:59:07.972:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335607 2021-11-03 01:59:07.972:            ASCOM: Info      : GET RightAscension = 1.74225
335608 2021-11-03 01:59:07.972:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335609 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335610 2021-11-03 01:59:07.973:            ASCOM: Info      : GET RightAscension = 1.74225
335611 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335612 2021-11-03 01:59:07.973:            ASCOM: Info      : GET RightAscension = 1.74225
335613 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335614 2021-11-03 01:59:07.973:            ASCOM: Info      : GET SiderealTime = 3.79523972222222
335615 2021-11-03 01:59:07.974:            ASCOM: Info      : GET RightAscension = 1.74225
335616 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Declination = 51.4927777777778
335617 2021-11-03 01:59:07.974:            ASCOM: Info      : GET RightAscension = 1.74225
335618 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Declination = 51.4927777777778
335619 2021-11-03 01:59:07.974:            ASCOM: Info      : GET Slewing = False, MoveAxis(0)=0, MoveAxis(1)=0
335620 2021-11-03 01:59:08.055:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335621 2021-11-03 01:59:08.055:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335622 2021-11-03 01:59:08.056:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335623 2021-11-03 01:59:08.056:            ASCOM: Info      : GET SiderealTime = 3.79526138888889
335624 2021-11-03 01:59:08.062:            ASCOM: Info      : SlewToCoordinatesAsync() RA=5.49582868725247, Dec=34.4413830565668
335625 2021-11-03 01:59:08.062:  check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsync




From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of david w pearson via groups.io <p.davidw@...>
Sent: Wednesday, November 3, 2021 4:51 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] APCC/Driver exception
 
Hi Ray,
 
I am getting this error from ASCOM/driver
 
"check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsyn"
 
Do you have any insight on this exception and what may cause it?
 
Background.
I use CCDCommander for my auto imaging script.
After parking the mount due to bad weather/Roof Closure, and being in a weather pause for maybe hours, i get this error after coming out of a weather pause and restarting my imaging session.
 
CCDCommander log
01:59:08  JNow Coordinates: RA: 05h 29m 45.0s Dec: +34°26'29"
01:59:08  Slewing to Sh2-234...
01:59:08  Error Number: -2147220471
01:59:08  Illegal operation while parked
 
I have enclosed a summary txt file of CCDCommander and APCC(to shorter the search)
 
In summary....CCDCommander goes into weather pause, and tells APCC/driver to park and it does.
After the weather pause, CCDCommander tells APCC/driver to go to last image and it appears to do that.....however, "at park" stays true.
 
question here.....when "at park" is true, does this just mean not slewing or tracking?   Slewing and tracking stays false.
 
CCDCommander discovers that the last object is not the planned  object due to the weather delay, and tells APCC/driver to slew to correct object, and the Exception occurs.
 
Mount is parked at alt/az of the last object when exception occurred and of course is still there upon observing the mount next morning.
 
I realize my issue is an interface issue between the mount and CCDCommander, but maybe if there some possible issues 
that make this happen i can work around it or get Matt at CCDCommander to fix.
 
This has been a CCDCommander issue since i started in 2010 and has been noted by others over the years.    I have talked to Matt about it and he has given me workarounds to try, but none have worked.
 
So i decided to try to figure it out myself, and pass info over to Matt.
 
Any ideas what is causing  the APCC exception?
 
I know this is not really your issue.....but a lot of us have been struggling with this for some time......you are probably our last hope.(pun intended!)
Thanks... if you choose to accept this challenge!!   Hopefully easy for you!
 
dave


Re: AP1100 Newbie Question

 

are you using an automated rotator?


On Wed, Nov 3, 2021 at 4:37 PM Mark Lamb <lamb_mark@...> wrote:
The accuracy of the the 1st GoTo is very minor to me, as it is easily corrected.  My main concern is having the best reference point for the camera levels to set camera rotation, as that will impact my sub framing.



--
Brian 



Brian Valente


How often do people refresh their All-Sky Pointing Model? (Observatory)

Chris White
 

Should this be done seasonally? (For those of us in northern climates?)
Should this be done after updating a PEC curve?
Should this be done after changing controllers?
Should this be done after a certain amount of time?
Should this be done after greasing the gears?

Is there a specific amount of spacing for RA and DEC that would allow you to be able to take advantage of DEC arc tracking without needing to run new DEC arcs before imaging?

Thank you in advance,


Re: AP1100 Newbie Question

Mark Lamb
 

For the record, last night's Park 3 was bang on the alignment notches.


APCC/Driver exception

david w pearson
 

Hi Ray,
 
I am getting this error from ASCOM/driver
 
"check_connected: Exception : bMustNotBeParked and g_bParked: True, True : SlewToCoordinatesAsyn"
 
Do you have any insight on this exception and what may cause it?
 
Background.
I use CCDCommander for my auto imaging script.
After parking the mount due to bad weather/Roof Closure, and being in a weather pause for maybe hours, i get this error after coming out of a weather pause and restarting my imaging session.
 
CCDCommander log
01:59:08  JNow Coordinates: RA: 05h 29m 45.0s Dec: +34°26'29"
01:59:08  Slewing to Sh2-234...
01:59:08  Error Number: -2147220471
01:59:08  Illegal operation while parked
 
I have enclosed a summary txt file of CCDCommander and APCC(to shorter the search)
 
In summary....CCDCommander goes into weather pause, and tells APCC/driver to park and it does.
After the weather pause, CCDCommander tells APCC/driver to go to last image and it appears to do that.....however, "at park" stays true.
 
question here.....when "at park" is true, does this just mean not slewing or tracking?   Slewing and tracking stays false.
 
CCDCommander discovers that the last object is not the planned  object due to the weather delay, and tells APCC/driver to slew to correct object, and the Exception occurs.
 
Mount is parked at alt/az of the last object when exception occurred and of course is still there upon observing the mount next morning.
 
I realize my issue is an interface issue between the mount and CCDCommander, but maybe if there some possible issues 
that make this happen i can work around it or get Matt at CCDCommander to fix.
 
This has been a CCDCommander issue since i started in 2010 and has been noted by others over the years.    I have talked to Matt about it and he has given me workarounds to try, but none have worked.
 
So i decided to try to figure it out myself, and pass info over to Matt.
 
Any ideas what is causing  the APCC exception?
 
I know this is not really your issue.....but a lot of us have been struggling with this for some time......you are probably our last hope.(pun intended!)
Thanks... if you choose to accept this challenge!!   Hopefully easy for you!
 
dave


Re: AP1100 Newbie Question

Mark Lamb
 

The accuracy of the the 1st GoTo is very minor to me, as it is easily corrected.  My main concern is having the best reference point for the camera levels to set camera rotation, as that will impact my sub framing.


Re: APCC Pro Error FindFreeQacindex: no free entries!

Chris White
 

Ray.  It seems to happen when I am either accessing or closing the ASCOM Hub Properties.  I switchde from using the ASCOM Hub to the ASCOM Lunatico driver and I dont seem to get the error anymore.  I'm not sure it is able to access all the data that the device can generate, but I get RH, Temp, Barometer and Dew Point.. so I guess that is sufficient for the purposes of APCC. 


Re: TPoint vs. APPM -- Translation Possible?

mjb87@...
 

Hi Ray... I have not tried the automatic TPoint modeling methodology yet.

To my uneducated eyes, it seems the problem is that the platesolving routines, given the very low FoV, cannot identify enough stars above the underlying noise caused by mediocre seeing. So I get failed solutions or erroneous solutions. Not sure denser data is the solution.

Marty


Re: AP1100 Newbie Question

George
 

Mark,

 

The slight offset is due to ReCals that may have been done during the course of the night.   The next night when you resume from Last Parked, your GoTo to the first object will be more accurate.    Not to be concerned…you’re fine.   <G>

 

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 Mark Lamb
Sent: Wednesday, November 3, 2021 1:50 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] AP1100 Newbie Question

 

A couple of weeks ago I received my new AP1100, and I am familiarizing myself with it.  The only other mount I have had is a G11, which has a simple, straight-forward operation, with integrated levels on the RA and Dec Saddle and only 1 Park position, which would be the equivalent of Park 3.  With the G11, the 1st thing I would always do (with G11 parked) is adjust the RA and Dec so that both levels were in the middle.  At this NCP pointing position, I would adjust the rotation of my camera to what I wanted for the night's target, using either the BuckeyeStarGazer's triple camera rotation levels or an angle finder with level.

The AP1100 does not have any built in RA and Dec levels, but has very nice alignment notches at 90deg increments on both RA and Dec.  I leveled my Losmandy FHD tripod (though not dead perfect) and the tripod is on a concrete patio.  The AP1100's single bubble level in totally inside the circle, but not in the dead center.  Polar alignment is done every night, even though the mount has NOT been moved, using a Polemaster.  (Aside: it seems that the night to night variability in PA on the AP1100 is noticeable less than the G11.)  I perfectly align the AP1100's RA and Dec alignment notches (loosen clutches) while at Park 3, and then set my camera's rotation, just like I would with my G11 and its levels.

At the end of the night's imaging run, NINA parks the AP1100 to Park 3.  I notice that the alignment notches are slightly offset.  The next night, I will again perfectly align the AP1100's RA and Dec alignment notches (loosen clutches) while at Park 3 before unparking, and then make sure the camera rotation is correct.

I have notice that the most recent night's are slightly rotated from earlier night's subs by a few degrees.  The earlier subs were taken in a side-by-side arrangement, but the Dec notches were aligned (though 90deg rotated).

I am wondering if I am doing things right.  I assume the slight misalignment of the notches at the end of the night's park is due to pointing corrections with plate-solving.  I have NOT built any APPM models yet.

Should I re-align the notches when parked?  Should this be avoiding during the night's imaging, if parked before the end of imaging?  Should this only be done at the beginning of the night's session?

Is my intuition right that the RA and Dec alignment notches need to be matched at Park 3 for setting proper camera rotation?


Re: #WiFi SkySafari Pro won't connect to GTOCP4 #WiFi

Donald Rudny
 

Hi Tom,

No, the Mount doesn’t need to be initialized.  I was out with my 1100 with CP4 last night.  I hadn’t used it for a while and had the same problem as you, SkySafari wouldn’t connect with my iPad. The Wi-Fi connection showed the CP4, but every time I hit connect it said it wasn’t communicating with the Mount.  It also said to check to make sure the local network tab was on.  I never heard of that but went into “settings” and selected the app.  Sure enough, there was a local network tab and it was off.  Turned it on and it connected fine.  The updated SkySafari will connect at several positions now.  The local network thing must have crept in on the update.  No need to initialize first.  I run the 1100 solely with SkySafari.

Hope this is your problem, too.

Don

Don Rudny
Pepeekeo, HI 96783-0106


On Nov 3, 2021, at 7:59 AM, Tom Zepf <tjzcos@...> wrote:

Thanks for checking Howard. That .101 is the address the CP4 gave to my Mac/iPad, indeed the .1 is for the CP4 itself. At one time I had both the iPad and the Mac connected, and the first one got .100 and the next one got .101.

I read on some other thread that the mount needed to be initialized before it would work. Is that what might be happening here?

4241 - 4260 of 86843