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

Join main@ap-gto.groups.io to automatically receive all group messages.