Date   

Re: APCC download - malware detection

Worsel
 

David

This may be similar to Norton's WSReputation.1 flag.  It means that the security software does not have enough usage info in its database on the tested software.  That's not a surprise for ANY astro software.  I use Norton and have bypassed the WSReputation.1 flag without issue.

Bryan


Re: Oh my god..it doesn't get better than this.

Tom Blahovici
 

Using a regular pointing model. 100 points for half the sky.
Tom


Re: AP1100 Newbie Question

ap@CaptivePhotons.com
 

Mark Lamb wrote:

 

  • 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.

 

I do not have an automated one either, but use NINA's "Manual Rotator" (I think Voyager has one also). 

 

With this, I can do a plate solve early in the evening, and it will prompt me "Rotate clockwise 10 degrees" (or whatever), and continue to iterate with an exposure and prompt until I achieve whatever level of accuracy I desire.  I use 1 degree.  This keeps multi-night sessions well aligned so I do not lose a lot of the area from bad overlaps.

 

I mention it as convenient for those who find manual leveling and eyeball rotation a bit frustrating or not accurate enough.

 

I have a short sequence that slews high for a PHD2 calibration, and it does the rotation "calibration" just before PHD2, and ASTAP's plate solving is good enough it all occurs well before it is dark enough to really start imaging.

 

One thing I'm impressed with on the Ap1100 is after the flip it's within a small fraction of a degree of the same sky rotation, nicely orthogonal.

 

Linwood


Re: APCC Pro Error FindFreeQacindex: no free entries!

Ray Gralak
 

Hi David,

 

> Minor complaint about error windows in APCC.  I often can’t access the error window.  It appears to be hidden

> by the main APCC window. 

 

The Error Log Window is set to be a "top most" window, so it will be in front of APCC's main window if APCC is not also set to be on top.

 

That said, clicking the Tools->Error Log menu item (see screenshot below) will bring the error log window to the front of any windows, even if it is in the background.

 

 

-Ray

 

 

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

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

> Sent: Thursday, November 4, 2021 6:15 AM

> To: main@ap-gto.groups.io

> Subject: Re: [ap-gto] APCC Pro Error FindFreeQacindex: no free entries!

>

> I’ve gotten the same error recently.  It happened when building my APPM model, not while acquiring data.  It

> didn’t seem to have any effect on the process.

>

> Minor complaint about error windows in APCC.  I often can’t access the error window.  It appears to be hidden

> by the main APCC window.  Even using Alt Tab to cycle through the windows doesn’t work.  I do not not have

> the box for APCC to always be on top checked.  There’s an easy workaround, which is to go to the bottom of

> the screen and close the window by right clicking on the tab, then click the show errors to bring it up again on

> top, but it is annoying and has happened multiple times. Seems like there would be an easy fix.

>


Re: APCC Pro Error FindFreeQacindex: no free entries!

David Johnson
 

I’ve gotten the same error recently.  It happened when building my APPM model, not while acquiring data.  It didn’t seem to have any effect on the process. 

Minor complaint about error windows in APCC.  I often can’t access the error window.  It appears to be hidden by the main APCC window.  Even using Alt Tab to cycle through the windows doesn’t work.  I do not not have the box for APCC to always be on top checked.  There’s an easy workaround, which is to go to the bottom of the screen and close the window by right clicking on the tab, then click the show errors to bring it up again on top, but it is annoying and has happened multiple times. Seems like there would be an easy fix. 


Re: Oh my god..it doesn't get better than this.

M Hambrick
 

Most impressive.

I can't read the details on your screen shot. Are you using some king of pointing model ?

Mike


Re: APCC/Driver exception

Ray Gralak
 

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@...>
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
 

Dave,

There's a bunch of lines missing from your attachment, but according to line 330505 the response from the GOS command indicates the mount is parked.

330420 2021-11-02 23:41:49.586: ASCOM: Info : GET SideOfPier = East
Stopped Slewing
330495 2021-11-02 23:41:52.785: ASCOM: Info : GET AtPark = False
330496 2021-11-02 23:41:52.819: ASCOM: Info : GET Tracking = False
330497 2021-11-02 23:41:52.820: ASCOM: Info : GET Azimuth = 180.000555555556
330498 2021-11-02 23:41:52.820: Driver: Info : CommandString TX=':GA#'
330499 2021-11-02 23:41:52.850: Driver: Info : CommandString: APCC response: ':APCC,69137,GA#', Response='-00*00:02#'
330500 2021-11-02 23:41:52.850: ASCOM: Info : GET Altitude = -5.55555555555556E-04
330501 2021-11-02 23:41:52.852: ASCOM: Info : GET RightAscension = 1.50144444444444
330502 2021-11-02 23:41:52.853: ASCOM: Info : GET Declination = -54.6697222222222
330503 2021-11-02 23:41:53.118: ASCOM: Info : GET Connected = True
330504 2021-11-02 23:41:53.144: Driver: Info : CommandString TX=':GOS#'
330505 2021-11-02 23:41:53.182: Driver: Info : CommandString: APCC response: ':APCC,69138,GOS#', Response='P99000200P000#'

-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@...>
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: Oh my god..it doesn't get better than this.

Tom Blahovici
 

I think Roland went out of his way to make sure my mount was super special.


Oh my god..it doesn't get better than this.

Tom Blahovici
 

90 shots. All the same.  3 arc second pointing accuracy. My new Ap1100 without decoders.  it  doesn't get better than this.


Re: APCC/Driver exception

david w pearson
 

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
>







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.

5421 - 5440 of 88034