Re: APCC/Driver exception


david w pearson
 

Let me confirm what you are saying?

1) at park = true ,and when Parked at Park positions 1-5.   must unpark, start tracking before slewing can occur?
2) at park= true can occur if pointing at a star and tracking is turned off ?
3) at park= true and not at park positions 1-5, must unpark, and start tracking before slewing?
4) while slewing or tracking....at park=false

Is this correct?
thanks for your time
dave

On Wednesday, November 3, 2021, 10:48:31 PM PDT, Ray Gralak <iogroups@...> wrote:


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#'

And again here, the mount status says it is parked according to the response from the GOS command.

-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 8:24 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] APCC/Driver exception
>
> Sorry Ray we are not communicating......Step by step....
> i was imaging M76 when weather pause occurred....Mount was parked for about a hour (APCC confirms)
> When weather cleared....CCDCommander told mount to unpark and go to M76.....which as I interpret from
> APCC log that it did (and the fact that is where  the mount was pointed  in the morning).
> Because time had passed,  M76 was not to be shot at this time, but should be imaging Sh2-234.
> When CCD Commander tried to slew from M76 to SH2-234 that is where the exception occurred.
>
> according APCC/driver log.....after weather pause, mount took about 49 seconds to slew to M76 after it had
> been parked in park position 4  for about than hour.
>
> possibilities
> 1) mount never parked when weather caused imaging to stop and just stopped tracking.  however
> APCC/driver said it did park
> 2) after weather cleared and imaging started up  again, mount slewed to M76  ( i may be wrong but scope was
> pointed where M76 was when exception occurred)
>      a) after going to M76...somehow park was issued and then immediately issued slew to Sh2-234 was issued
> causing the exception.
>      b)??????????
>
>
> hope that clears it up
> dave
>
>
>
>
> On Wednesday, November 3, 2021, 07:56:13 PM PDT, Ray Gralak <iogroups@...> wrote:
>
>
> 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=yahoo.com@groups.io>
> > 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.