|
I’m trying to nail down an issue where ACP sends a park command to the mount but seems to hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The difference from before is I was using a roll off roof observatory and the mount had to park before the roof could close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed. If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP issue but….. Any ideas on what to do or what to look for. If you have access to the ACP forum the posting is here. And yes, I had made some assumptions that proved wrong…..again. Thanks -Steve
|
|
|
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
I’m trying to nail down an issue where ACP sends a park command to the mount but seems to hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The difference from before is I was using a roll off roof observatory and the mount had to park before the roof could close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed. If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP issue but….. Any ideas on what to do or what to look for. If you have access to the ACP forum the posting is here. And yes, I had made some assumptions that proved wrong…..again. Thanks -Steve
|
|
|
I knew I’d leave something important out…. APCC – 1.9.6.7 AP1200 Firmware VCP4-P02-15 ASCOM Driver v5.60.05 The interesting thing here is the latest driver is installed but I have the flashing message to update to the same driver version. -Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente Sent: Thursday, March 16, 2023 2:57 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] AP1200 Park Issue Hi Steve Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions? I’m trying to nail down an issue where ACP sends a park command to the mount but seems to hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The difference from before is I was using a roll off roof observatory and the mount had to park before the roof could close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed. If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP issue but….. Any ideas on what to do or what to look for. If you have access to the ACP forum the posting is here. And yes, I had made some assumptions that proved wrong…..again. Thanks -Steve
--
|
|
|
Steve can you just double-check to make sure everything is configured properly and you are following the startup routine outlined in the latest video?
Otherwise it would help to know more about exactly what the error was from ACP. zipping up the logs would help (use the APCC log zipper utility)
Brian
I knew I’d leave something important out…. APCC – 1.9.6.7 AP1200 Firmware VCP4-P02-15 ASCOM Driver v5.60.05 The interesting thing here is the latest driver is installed but I have the flashing message to update to the same driver version. -Steve Hi Steve Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions? I’m trying to nail down an issue where ACP sends a park command to the mount but seems to hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The difference from before is I was using a roll off roof observatory and the mount had to park before the roof could close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed. If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP issue but….. Any ideas on what to do or what to look for. If you have access to the ACP forum the posting is here. And yes, I had made some assumptions that proved wrong…..again. Thanks -Steve
--
|
|
|
Brian, I had indeed watched and followed the new APCC and driver setup when 1st announced but watched again to be sure I didn’t miss anything. I had updated when these 1st came out so I’ve been using them for a fair while now. And I always use ACP, current as well, when imaging. Do you want any APCC logs from last night and if so what should be included? The log files for the last day are almost 18MB from APCC. -Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente Sent: Thursday, March 16, 2023 3:47 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] AP1200 Park Issue Steve can you just double-check to make sure everything is configured properly and you are following the startup routine outlined in the latest video? Otherwise it would help to know more about exactly what the error was from ACP. zipping up the logs would help (use the APCC log zipper utility) I knew I’d leave something important out…. APCC – 1.9.6.7 AP1200 Firmware VCP4-P02-15 ASCOM Driver v5.60.05 The interesting thing here is the latest driver is installed but I have the flashing message to update to the same driver version. -Steve Hi Steve Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions? I’m trying to nail down an issue where ACP sends a park command to the mount but seems to hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The difference from before is I was using a roll off roof observatory and the mount had to park before the roof could close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed. If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP issue but….. Any ideas on what to do or what to look for. If you have access to the ACP forum the posting is here. And yes, I had made some assumptions that proved wrong…..again. Thanks -Steve
--
--
|
|
|
Thanks steve
Use the log zipper and if the resulting archive is big can you post a link to it from Dropbox Google drive etc
Brian
Brian, I had indeed watched and followed the new APCC and driver setup when 1st announced but watched again to be sure I didn’t miss anything. I had updated when these 1st came out so I’ve been using them for a fair while now. And I always use ACP, current as well, when imaging. Do you want any APCC logs from last night and if so what should be included? The log files for the last day are almost 18MB from APCC. -Steve Steve can you just double-check to make sure everything is configured properly and you are following the startup routine outlined in the latest video? Otherwise it would help to know more about exactly what the error was from ACP. zipping up the logs would help (use the APCC log zipper utility) I knew I’d leave something important out…. APCC – 1.9.6.7 AP1200 Firmware VCP4-P02-15 ASCOM Driver v5.60.05 The interesting thing here is the latest driver is installed but I have the flashing message to update to the same driver version. -Steve Hi Steve Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions? I’m trying to nail down an issue where ACP sends a park command to the mount but seems to hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The difference from before is I was using a roll off roof observatory and the mount had to park before the roof could close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed. If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP issue but….. Any ideas on what to do or what to look for. If you have access to the ACP forum the posting is here. And yes, I had made some assumptions that proved wrong…..again. Thanks -Steve
--
--
|
|
|
The link for the file is here on Dropbox. -Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente Sent: Thursday, March 16, 2023 4:45 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] AP1200 Park Issue Use the log zipper and if the resulting archive is big can you post a link to it from Dropbox Google drive etc Brian, I had indeed watched and followed the new APCC and driver setup when 1st announced but watched again to be sure I didn’t miss anything. I had updated when these 1st came out so I’ve been using them for a fair while now. And I always use ACP, current as well, when imaging. Do you want any APCC logs from last night and if so what should be included? The log files for the last day are almost 18MB from APCC. -Steve Steve can you just double-check to make sure everything is configured properly and you are following the startup routine outlined in the latest video? Otherwise it would help to know more about exactly what the error was from ACP. zipping up the logs would help (use the APCC log zipper utility) I knew I’d leave something important out…. APCC – 1.9.6.7 AP1200 Firmware VCP4-P02-15 ASCOM Driver v5.60.05 The interesting thing here is the latest driver is installed but I have the flashing message to update to the same driver version. -Steve Hi Steve Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions? I’m trying to nail down an issue where ACP sends a park command to the mount but seems to hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The difference from before is I was using a roll off roof observatory and the mount had to park before the roof could close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed. If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP issue but….. Any ideas on what to do or what to look for. If you have access to the ACP forum the posting is here. And yes, I had made some assumptions that proved wrong…..again. Thanks -Steve
--
--
--
|
|
|
Hi Steve,
Just to be clear, which applications hung? ACP -- or the driver and/or APCC?
If APCC/driver were active, did the driver and APCC indicate the mount was parked?
-Ray
toggle quoted message
Show quoted text
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steve Reilly
Sent: Thursday, March 16, 2023 6:35 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
The link for the file is here <https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-2023-03-16-
161724.zip?dl=0> on Dropbox.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 4:45 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Thanks steve
Use the log zipper and if the resulting archive is big can you post a link to it from Dropbox Google drive etc
Brian
On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
Brian,
I had indeed watched and followed the new APCC and driver setup when 1st announced but watched
again to be sure I didn’t miss anything. I had updated when these 1st came out so I’ve been using them for a fair
while now. And I always use ACP, current as well, when imaging. Do you want any APCC logs from last night and
if so what should be included? The log files for the last day are almost 18MB from APCC.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 3:47 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve can you just double-check to make sure everything is configured properly and you are following the
startup routine outlined in the latest video?
https://youtu.be/7r2qujy8BkM
Otherwise it would help to know more about exactly what the error was from ACP. zipping up the logs would
help (use the APCC log zipper utility)
Brian
On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
I knew I’d leave something important out….
APCC – 1.9.6.7
AP1200 Firmware VCP4-P02-15
ASCOM Driver v5.60.05
The interesting thing here is the latest driver is installed but I have the flashing message to update to
the same driver version.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 2:57 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
I’m trying to nail down an issue where ACP sends a park command to the mount but seems to
hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown
script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The
difference from before is I was using a roll off roof observatory and the mount had to park before the roof could
close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks
the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never
acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention
script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed.
If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP
issue but…..
Any ideas on what to do or what to look for. If you have access to the ACP forum the posting
is here <http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And yes, I had made some
assumptions that proved wrong…..again.
Thanks
-Steve
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
|
|
|
Steve,
Although you included APCC and APPM logs, there are no ASCOM logs in your zip file, which I also need to see. Make sure you have ASCOM logging enabled in the AP V2 driver.
-Ray
toggle quoted message
Show quoted text
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steve Reilly
Sent: Thursday, March 16, 2023 6:34 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
The link for the file is here <https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-2023-03-16-
161724.zip?dl=0> on Dropbox.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 4:45 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Thanks steve
Use the log zipper and if the resulting archive is big can you post a link to it from Dropbox Google drive etc
Brian
On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
Brian,
I had indeed watched and followed the new APCC and driver setup when 1st announced but watched
again to be sure I didn’t miss anything. I had updated when these 1st came out so I’ve been using them for a fair
while now. And I always use ACP, current as well, when imaging. Do you want any APCC logs from last night and
if so what should be included? The log files for the last day are almost 18MB from APCC.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 3:47 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve can you just double-check to make sure everything is configured properly and you are following the
startup routine outlined in the latest video?
https://youtu.be/7r2qujy8BkM
Otherwise it would help to know more about exactly what the error was from ACP. zipping up the logs would
help (use the APCC log zipper utility)
Brian
On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
I knew I’d leave something important out….
APCC – 1.9.6.7
AP1200 Firmware VCP4-P02-15
ASCOM Driver v5.60.05
The interesting thing here is the latest driver is installed but I have the flashing message to update to
the same driver version.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 2:57 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
I’m trying to nail down an issue where ACP sends a park command to the mount but seems to
hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown
script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The
difference from before is I was using a roll off roof observatory and the mount had to park before the roof could
close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks
the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never
acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention
script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed.
If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP
issue but…..
Any ideas on what to do or what to look for. If you have access to the ACP forum the posting
is here <http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And yes, I had made some
assumptions that proved wrong…..again.
Thanks
-Steve
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
|
|
|
Hey Ray,
That may have been the issue with the logs as I wasn't aware that Debug Log needed enabling in the ASCOM driver which it is now. I guess it's never been on before.....
-Steve
toggle quoted message
Show quoted text
-----Original Message----- From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak Sent: Thursday, March 16, 2023 11:36 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] AP1200 Park Issue Steve, Although you included APCC and APPM logs, there are no ASCOM logs in your zip file, which I also need to see. Make sure you have ASCOM logging enabled in the AP V2 driver. -Ray -----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Steve Reilly
Sent: Thursday, March 16, 2023 6:34 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
The link for the file is here
<https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-2023-
03-16-
161724.zip?dl=0> on Dropbox.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian
Valente
Sent: Thursday, March 16, 2023 4:45 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Thanks steve
Use the log zipper and if the resulting archive is big can you post a
link to it from Dropbox Google drive etc
Brian
On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
Brian,
I had indeed watched and followed the new APCC and driver setup when
1st announced but watched again to be sure I didn’t miss anything. I
had updated when these 1st came out so I’ve been using them for a fair
while now. And I always use ACP, current as well, when imaging. Do you want any APCC logs from last night and if so what should be included? The log files for the last day are almost 18MB from APCC.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 3:47 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve can you just double-check to make sure everything is configured
properly and you are following the startup routine outlined in the latest video?
https://youtu.be/7r2qujy8BkM
Otherwise it would help to know more about exactly what the error was
from ACP. zipping up the logs would help (use the APCC log zipper
utility)
Brian
On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
I knew I’d leave something important out….
APCC – 1.9.6.7
AP1200 Firmware VCP4-P02-15
ASCOM Driver v5.60.05
The interesting thing here is the latest driver is installed but I
have the flashing message to update to the same driver version.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 2:57 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
I’m trying to nail down an issue where ACP sends a park command to
the mount but seems to hang/fail. This has happened several times in
the past but is erratic. In this case ACP was running the shutdown
script, same one I’ve used for years, and for some reason fails to
acknowledge it has parked and hangs. The difference from before is I
was using a roll off roof observatory and the mount had to park before
the roof could close. In this case now with the dome it closes anytime
regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed.
If it wasn’t because of a past issue with Park not being
acknowledged I’d think it was an ACP issue but…..
Any ideas on what to do or what to look for. If you have access to
the ACP forum the posting is here
<http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And yes, I had made some assumptions that proved wrong…..again.
Thanks
-Steve
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
|
|
|
Hi Steve,
Okay, please capture the issue again with the logs enabled.
Also, can you tell me which application(s) were locked? ACP, the driver, or APCC? Or all of them??
-Ray
toggle quoted message
Show quoted text
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steve Reilly
Sent: Friday, March 17, 2023 7:12 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hey Ray,
That may have been the issue with the logs as I wasn't aware that Debug Log needed enabling in the ASCOM
driver which it is now. I guess it's never been on before.....
-Steve
-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Thursday, March 16, 2023 11:36 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve,
Although you included APCC and APPM logs, there are no ASCOM logs in your zip file, which I also need to see.
Make sure you have ASCOM logging enabled in the AP V2 driver.
-Ray
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Steve Reilly
Sent: Thursday, March 16, 2023 6:34 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
The link for the file is here
<https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-2023-
03-16-
161724.zip?dl=0> on Dropbox.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian
Valente
Sent: Thursday, March 16, 2023 4:45 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Thanks steve
Use the log zipper and if the resulting archive is big can you post a
link to it from Dropbox Google drive etc
Brian
On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
Brian,
I had indeed watched and followed the new APCC and driver setup when
1st announced but watched again to be sure I didn’t miss anything. I
had updated when these 1st came out so I’ve been using them for a fair
while now. And I always use ACP, current as well, when imaging. Do you want any APCC logs from last night and if so what should be included? The log files for the last day are almost 18MB from APCC.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 3:47 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve can you just double-check to make sure everything is configured
properly and you are following the startup routine outlined in the latest video?
https://youtu.be/7r2qujy8BkM
Otherwise it would help to know more about exactly what the error was
from ACP. zipping up the logs would help (use the APCC log zipper
utility)
Brian
On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
I knew I’d leave something important out….
APCC – 1.9.6.7
AP1200 Firmware VCP4-P02-15
ASCOM Driver v5.60.05
The interesting thing here is the latest driver is installed but I
have the flashing message to update to the same driver version.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 2:57 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
I’m trying to nail down an issue where ACP sends a park command to
the mount but seems to hang/fail. This has happened several times in
the past but is erratic. In this case ACP was running the shutdown
script, same one I’ve used for years, and for some reason fails to
acknowledge it has parked and hangs. The difference from before is I
was using a roll off roof observatory and the mount had to park before
the roof could close. In this case now with the dome it closes anytime
regardless without issue so the dome closes then parks the mount. This has been fine for maybe a year and
then this morning the shutdown script runs but never acknowledges it has reached the park position. This causes
ACP to fail and then activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP
forum and I can reprint here if needed.
If it wasn’t because of a past issue with Park not being
acknowledged I’d think it was an ACP issue but…..
Any ideas on what to do or what to look for. If you have access to
the ACP forum the posting is here
<http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And yes, I had made some assumptions
that proved wrong…..again.
Thanks
-Steve
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
|
|
|
Hey Ray,
If you remember this has been an ongoing but rare event, if they are related, and not repeatable that I'm aware of. All my imaging sessions are done using ACP Expert, MaxIm, FocusMax v4, APCC, Pyxis Commander (rotator), AAG CloudWatcher, and of course my Outlet Control. The mount is only connected in APCC and then ACP. This seemed to happen while the shutdown script was running in ACP and if I remember this has happened before but a long time back. We had a conversation about that at the time. The same happened when I was running rescue squad some years ago where a weather event (clouds then rain) had attempted to close the roll off roof but failed. The driver appeared hung at attempting to park, which it was actually in that position, but ACP doesn't continue to poll after it's initial call. At least that seems to be what I remember. That's why now I have the dome which can close in any telescope position regardless. I wish now I had rearranged the screen capture to better show all the active windows....but the scope was in Park 4, which was correct, but evidently ACP had not received the information. When I restarted the system, ACP had thrown an Operator Intervention and was idle from there on waiting on me to correct the issue. When I went into APCC and hit Park the scope didn't move, went through the normal shutdown afterwards when asked and closed as expected.
When I initially looked at the system and ACP I thought a weather event had initiated the shutdown but Bob told me weather events are disabled when shutdown is occurring. His remarks are below:
Code:
...
2023-03-16 10:27:10.3: -- Observatory Shutdown --
2023-03-16 10:27:10.3: Weather safety is now disabled
2023-03-16 10:27:10.3: Start ACP Sequencer's ShutdownObs script
2023-03-16 10:27:49.9: ** ACP script "ShutdownObs" failed:
2023-03-16 10:27:49.9: **Script Error (Tracking has been stopped)**
Source: ASCOM V2 AstroPhysics GTO Driver
Message: APCC Park failed:
Location: line 81 column 9.
2023-03-16 10:27:49.9: Weather safety is re-enabled
2023-03-16 10:27:49.9: **EXCEPTION IN SCHEDULER:
2023-03-16 10:27:49.9: Observatory shutdown failed, cannot continue.
2023-03-16 10:27:49.9: Traceback:
at DC3.Scheduler.Engine.DoShutdownIf()
at DC3.Scheduler.Engine.Run()
2023-03-16 10:27:50.2: Weather safety is now disabled
2023-03-16 10:27:50.2: Weather safety is re-enabled
2023-03-16 10:27:53.4: Running C:\Windows\SYSWOW64\cscript.exe
2023-03-16 10:27:53.4: Arguments: '"C:\Users\Public\Documents\ACP Config\Scheduler\OperatorInterventionScript.vbs"'
2023-03-16 10:28:12.5: Results look OK, the tool returned this text:
2023-03-16 10:28:12.5: 'Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Scheduler closing the roof...
(this may take minutes)
... roof should now be closed
'
2023-03-16 10:28:12.5: Operator Intervention tool returned message:
2023-03-16 10:28:12.5: 'Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Scheduler closing the roof...
(this may take minutes)
... roof should now be closed
'
[...]
2023-03-16 10:28:16.0: ACPSequencer: Failed to get ACP's DispatcherEnabled property. ACP is compromised.
2023-03-16 10:28:16.0: Object reference not set to an instance of an object.
Log closed at Thu, Mar 16 2023 10:28:17 UTC (actual time)
Analysis:
1. Disabled weather interrupts
2. Tried to park your scope but that failed. "APCC Park failed"
3. Shutdown script failed due to the APCC runtime error
4. Enabled weather interrupts
5. Declared a Scheduler Operator Intervention due to the mount parking failure (It's getting wet or ???)
6. Ran your Operator Intervention script, which appears to try to close the roof but ACP has failed at this point.
This was a chain of failures caused by the APCC park error. I can't guess why ACP died out from under Scheduler."
Not sure what else I can provide. The ASCOM driver is now set to log sessions.
-Steve
toggle quoted message
Show quoted text
-----Original Message----- From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak Sent: Friday, March 17, 2023 10:39 AM To: main@ap-gto.groups.io Subject: Re: [ap-gto] AP1200 Park Issue Hi Steve, Okay, please capture the issue again with the logs enabled. Also, can you tell me which application(s) were locked? ACP, the driver, or APCC? Or all of them?? -Ray -----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Steve Reilly
Sent: Friday, March 17, 2023 7:12 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hey Ray,
That may have been the issue with the logs as I wasn't aware that
Debug Log needed enabling in the ASCOM driver which it is now. I guess it's never been on before.....
-Steve
-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray
Gralak
Sent: Thursday, March 16, 2023 11:36 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve,
Although you included APCC and APPM logs, there are no ASCOM logs in your zip file, which I also need to see.
Make sure you have ASCOM logging enabled in the AP V2 driver.
-Ray
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Steve Reilly
Sent: Thursday, March 16, 2023 6:34 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
The link for the file is here
<https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-202
3-
03-16-
161724.zip?dl=0> on Dropbox.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of
Brian Valente
Sent: Thursday, March 16, 2023 4:45 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Thanks steve
Use the log zipper and if the resulting archive is big can you post
a link to it from Dropbox Google drive etc
Brian
On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
Brian,
I had indeed watched and followed the new APCC and driver setup
when 1st announced but watched again to be sure I didn’t miss
anything. I had updated when these 1st came out so I’ve been using
them for a fair while now. And I always use ACP, current as well,
when imaging. Do you want any APCC logs from last night and if so what should be included? The log files for the last day are almost 18MB from APCC.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 3:47 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve can you just double-check to make sure everything is
configured properly and you are following the startup routine outlined in the latest video?
https://youtu.be/7r2qujy8BkM
Otherwise it would help to know more about exactly what the error
was from ACP. zipping up the logs would help (use the APCC log
zipper
utility)
Brian
On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
I knew I’d leave something important out….
APCC – 1.9.6.7
AP1200 Firmware VCP4-P02-15
ASCOM Driver v5.60.05
The interesting thing here is the latest driver is installed but I
have the flashing message to update to the same driver version.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 2:57 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
I’m trying to nail down an issue where ACP sends a park command
to the mount but seems to hang/fail. This has happened several times
in the past but is erratic. In this case ACP was running the
shutdown script, same one I’ve used for years, and for some reason
fails to acknowledge it has parked and hangs. The difference from
before is I was using a roll off roof observatory and the mount had
to park before the roof could close. In this case now with the dome
it closes anytime regardless without issue so the dome closes then
parks the mount. This has been fine for maybe a year and
then this morning the shutdown script runs but never acknowledges it
has reached the park position. This causes ACP to fail and then
activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed.
If it wasn’t because of a past issue with Park not being
acknowledged I’d think it was an ACP issue but…..
Any ideas on what to do or what to look for. If you have access
to the ACP forum the posting is here
<http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And
yes, I had made some assumptions
that proved wrong…..again.
Thanks
-Steve
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
|
|
|
Hi steve
>>> The mount is only connected in APCC and then ACP.
ACP connects through the ASCOM V2 driver to APCC which I’m sure is why ray is requesting the companion ascom log
Hey Ray,
If you remember this has been an ongoing but rare event, if they are related, and not repeatable that I'm aware of. All my imaging sessions are done using ACP Expert, MaxIm, FocusMax v4, APCC, Pyxis Commander (rotator), AAG CloudWatcher, and of course my Outlet Control. The mount is only connected in APCC and then ACP. This seemed to happen while the shutdown script was running in ACP and if I remember this has happened before but a long time back. We had a conversation about that at the time. The same happened when I was running rescue squad some years ago where a weather event (clouds then rain) had attempted to close the roll off roof but failed. The driver appeared hung at attempting to park, which it was actually in that position, but ACP doesn't continue to poll after it's initial call. At least that seems to be what I remember. That's why now I have the dome which can close in any telescope position regardless. I wish now I had rearranged the screen capture to better show all the active windows....but the scope was in Park 4, which was correct, but evidently ACP had not received the information. When I restarted the system, ACP had thrown an Operator Intervention and was idle from there on waiting on me to correct the issue. When I went into APCC and hit Park the scope didn't move, went through the normal shutdown afterwards when asked and closed as expected.
When I initially looked at the system and ACP I thought a weather event had initiated the shutdown but Bob told me weather events are disabled when shutdown is occurring. His remarks are below:
Code:
...
2023-03-16 10:27:10.3: -- Observatory Shutdown --
2023-03-16 10:27:10.3: Weather safety is now disabled
2023-03-16 10:27:10.3: Start ACP Sequencer's ShutdownObs script
2023-03-16 10:27:49.9: ** ACP script "ShutdownObs" failed:
2023-03-16 10:27:49.9: **Script Error (Tracking has been stopped)**
Source: ASCOM V2 AstroPhysics GTO Driver
Message: APCC Park failed:
Location: line 81 column 9.
2023-03-16 10:27:49.9: Weather safety is re-enabled
2023-03-16 10:27:49.9: **EXCEPTION IN SCHEDULER:
2023-03-16 10:27:49.9: Observatory shutdown failed, cannot continue.
2023-03-16 10:27:49.9: Traceback:
at DC3.Scheduler.Engine.DoShutdownIf()
at DC3.Scheduler.Engine.Run()
2023-03-16 10:27:50.2: Weather safety is now disabled
2023-03-16 10:27:50.2: Weather safety is re-enabled
2023-03-16 10:27:53.4: Running C:\Windows\SYSWOW64\cscript.exe
2023-03-16 10:27:53.4: Arguments: '"C:\Users\Public\Documents\ACP Config\Scheduler\OperatorInterventionScript.vbs"'
2023-03-16 10:28:12.5: Results look OK, the tool returned this text:
2023-03-16 10:28:12.5: 'Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Scheduler closing the roof...
(this may take minutes)
... roof should now be closed
'
2023-03-16 10:28:12.5: Operator Intervention tool returned message:
2023-03-16 10:28:12.5: 'Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Scheduler closing the roof...
(this may take minutes)
... roof should now be closed
'
[...]
2023-03-16 10:28:16.0: ACPSequencer: Failed to get ACP's DispatcherEnabled property. ACP is compromised.
2023-03-16 10:28:16.0: Object reference not set to an instance of an object.
Log closed at Thu, Mar 16 2023 10:28:17 UTC (actual time)
Analysis:
1. Disabled weather interrupts
2. Tried to park your scope but that failed. "APCC Park failed"
3. Shutdown script failed due to the APCC runtime error
4. Enabled weather interrupts
5. Declared a Scheduler Operator Intervention due to the mount parking failure (It's getting wet or ???)
6. Ran your Operator Intervention script, which appears to try to close the roof but ACP has failed at this point.
This was a chain of failures caused by the APCC park error. I can't guess why ACP died out from under Scheduler."
Not sure what else I can provide. The ASCOM driver is now set to log sessions.
-Steve
-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, March 17, 2023 10:39 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve,
Okay, please capture the issue again with the logs enabled.
Also, can you tell me which application(s) were locked? ACP, the driver, or APCC? Or all of them??
-Ray
> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> Of Steve Reilly
> Sent: Friday, March 17, 2023 7:12 AM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] AP1200 Park Issue
>
> Hey Ray,
>
> That may have been the issue with the logs as I wasn't aware that
> Debug Log needed enabling in the ASCOM driver which it is now. I guess it's never been on before.....
>
> -Steve
>
>
> -----Original Message-----
> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray
> Gralak
> Sent: Thursday, March 16, 2023 11:36 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] AP1200 Park Issue
>
> Steve,
>
> Although you included APCC and APPM logs, there are no ASCOM logs in your zip file, which I also need to see.
> Make sure you have ASCOM logging enabled in the AP V2 driver.
>
> -Ray
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> > Of Steve Reilly
> > Sent: Thursday, March 16, 2023 6:34 PM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] AP1200 Park Issue
> >
> > The link for the file is here
> > <https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-202
> > 3-
> > 03-16-
> > 161724.zip?dl=0> on Dropbox.
> >
> >
> >
> > -Steve
> >
> >
> >
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of
> > Brian Valente
> > Sent: Thursday, March 16, 2023 4:45 PM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] AP1200 Park Issue
> >
> >
> >
> > Thanks steve
> >
> >
> >
> > Use the log zipper and if the resulting archive is big can you post
> > a link to it from Dropbox Google drive etc
> >
> >
> >
> > Brian
> >
> >
> >
> > On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
> >
> > Brian,
> >
> >
> >
> > I had indeed watched and followed the new APCC and driver setup
> > when 1st announced but watched again to be sure I didn’t miss
> > anything. I had updated when these 1st came out so I’ve been using
> > them for a fair while now. And I always use ACP, current as well,
> > when imaging. Do you want any APCC logs from last night
> and if so what should be included? The log files for the last day are almost 18MB from APCC.
> >
> >
> >
> > -Steve
> >
> >
> >
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
> > Sent: Thursday, March 16, 2023 3:47 PM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] AP1200 Park Issue
> >
> >
> >
> > Steve can you just double-check to make sure everything is
> > configured properly and you are following the startup routine outlined in the latest video?
> >
> >
> >
> > https://youtu.be/7r2qujy8BkM
> >
> >
> >
> > Otherwise it would help to know more about exactly what the error
> > was from ACP. zipping up the logs would help (use the APCC log
> > zipper
> > utility)
> >
> >
> >
> > Brian
> >
> >
> >
> > On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
> >
> > I knew I’d leave something important out….
> >
> >
> >
> > APCC – 1.9.6.7
> >
> > AP1200 Firmware VCP4-P02-15
> >
> > ASCOM Driver v5.60.05
> >
> >
> >
> > The interesting thing here is the latest driver is installed but I
> > have the flashing message to update to the same driver version.
> >
> >
> >
> > -Steve
> >
> >
> >
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
> > Sent: Thursday, March 16, 2023 2:57 PM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] AP1200 Park Issue
> >
> >
> >
> > Hi Steve
> >
> >
> >
> > Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
> >
> >
> >
> >
> >
> >
> >
> > On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
> >
> > I’m trying to nail down an issue where ACP sends a park command
> > to the mount but seems to hang/fail. This has happened several times
> > in the past but is erratic. In this case ACP was running the
> > shutdown script, same one I’ve used for years, and for some reason
> > fails to acknowledge it has parked and hangs. The difference from
> > before is I was using a roll off roof observatory and the mount had
> > to park before the roof could close. In this case now with the dome
> > it closes anytime regardless without issue so the dome closes then
> > parks the mount. This has been fine for maybe a year and
> then this morning the shutdown script runs but never acknowledges it
> has reached the park position. This causes ACP to fail and then
> activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed.
> >
> >
> >
> > If it wasn’t because of a past issue with Park not being
> > acknowledged I’d think it was an ACP issue but…..
> >
> >
> >
> > Any ideas on what to do or what to look for. If you have access
> > to the ACP forum the posting is here
> > <http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And
> > yes, I had made some assumptions
> that proved wrong…..again.
> >
> >
> >
> > Thanks
> >
> >
> >
> > -Steve
> >
> >
> >
> >
> >
> >
> > --
> >
> > Brian
> >
> >
> >
> >
> >
> >
> >
> > Brian Valente
> >
> > astro portfolio
> > https://www.brianvalentephotography.com/astrophotography/
> >
> > portfolio brianvalentephotography.com
> > <http://brianvalentephotography.com>
> >
> > astrobin https://www.astrobin.com/users/bvalente/
> >
> >
> >
> >
> >
> >
> > --
> >
> > Brian
> >
> >
> >
> >
> >
> >
> >
> > Brian Valente
> >
> > astro portfolio
> > https://www.brianvalentephotography.com/astrophotography/
> >
> > portfolio brianvalentephotography.com
> > <http://brianvalentephotography.com>
> >
> > astrobin https://www.astrobin.com/users/bvalente/
> >
> > --
> >
> > Brian
> >
> >
> >
> >
> >
> >
> >
> > Brian Valente
> >
> > astro portfolio
> > https://www.brianvalentephotography.com/astrophotography/
> >
> > portfolio brianvalentephotography.com
> > <http://brianvalentephotography.com>
> >
> > astrobin https://www.astrobin.com/users/bvalente/
> >
> >
>
>
>
>
>
>
>
>
>
>
|
|
|
Steve,
I searched your logs for all park operations. I only found two about 10 seconds apart.
Your log shows that APCC responded with response indicating success and each started to park the mount successfully. However, for some reason an ASCOM clients (ACP?) issued the second park request before the first had completed. However, that is allowed and APCC responded again with a "success" response.
Given the two Park requests, maybe ACP does not handle asynchronous park operations and retried and failed again?
I saw no sign that APCC or the driver, which was still making requests to APCC, failed. And, the mount parked successfully.
-Ray
toggle quoted message
Show quoted text
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steve Reilly
Sent: Thursday, March 16, 2023 6:35 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
The link for the file is here <https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-2023-03-16-
161724.zip?dl=0> on Dropbox.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 4:45 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Thanks steve
Use the log zipper and if the resulting archive is big can you post a link to it from Dropbox Google drive etc
Brian
On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
Brian,
I had indeed watched and followed the new APCC and driver setup when 1st announced but watched
again to be sure I didn’t miss anything. I had updated when these 1st came out so I’ve been using them for a fair
while now. And I always use ACP, current as well, when imaging. Do you want any APCC logs from last night and
if so what should be included? The log files for the last day are almost 18MB from APCC.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 3:47 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve can you just double-check to make sure everything is configured properly and you are following the
startup routine outlined in the latest video?
https://youtu.be/7r2qujy8BkM
Otherwise it would help to know more about exactly what the error was from ACP. zipping up the logs would
help (use the APCC log zipper utility)
Brian
On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
I knew I’d leave something important out….
APCC – 1.9.6.7
AP1200 Firmware VCP4-P02-15
ASCOM Driver v5.60.05
The interesting thing here is the latest driver is installed but I have the flashing message to update to
the same driver version.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 2:57 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
I’m trying to nail down an issue where ACP sends a park command to the mount but seems to
hang/fail. This has happened several times in the past but is erratic. In this case ACP was running the shutdown
script, same one I’ve used for years, and for some reason fails to acknowledge it has parked and hangs. The
difference from before is I was using a roll off roof observatory and the mount had to park before the roof could
close. In this case now with the dome it closes anytime regardless without issue so the dome closes then parks
the mount. This has been fine for maybe a year and then this morning the shutdown script runs but never
acknowledges it has reached the park position. This causes ACP to fail and then activate an Operator Intervention
script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed.
If it wasn’t because of a past issue with Park not being acknowledged I’d think it was an ACP
issue but…..
Any ideas on what to do or what to look for. If you have access to the ACP forum the posting
is here <http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And yes, I had made some
assumptions that proved wrong…..again.
Thanks
-Steve
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com <http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
|
|
|
Source: ASCOM V2 AstroPhysics GTO Driver
Message: APCC Park failed: Steve, there is no such message as "APCC Park failed" in APCC or the driver that I could find. Besides your logs show APCC returned success from each park request. -Ray
|
|
|
Steve,
One more thing. Since your logs only have APCC logs, there is a possibility that the driver received other Park requests and they were rejected by the driver. That's one reason I need to see the driver logs.
-Ray
toggle quoted message
Show quoted text
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Steve Reilly
Sent: Friday, March 17, 2023 9:30 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hey Ray,
If you remember this has been an ongoing but rare event, if they are related, and not repeatable that I'm aware of.
All my imaging sessions are done using ACP Expert, MaxIm, FocusMax v4, APCC, Pyxis Commander (rotator),
AAG CloudWatcher, and of course my Outlet Control. The mount is only connected in APCC and then ACP. This
seemed to happen while the shutdown script was running in ACP and if I remember this has happened before but
a long time back. We had a conversation about that at the time. The same happened when I was running rescue
squad some years ago where a weather event (clouds then rain) had attempted to close the roll off roof but failed.
The driver appeared hung at attempting to park, which it was actually in that position, but ACP doesn't continue to
poll after it's initial call. At least that seems to be what I remember. That's why now I have the dome which can
close in any telescope position regardless. I wish now I had rearranged the screen capture to better show all the
active windows....but the scope was in Park 4, which was correct, but evidently ACP had not received the
information. When I restarted the system, ACP had thrown an Operator Intervention and was idle from there on
waiting on me to correct the issue. When I went into APCC and hit Park the scope didn't move, went through the
normal shutdown afterwards when asked and closed as expected.
When I initially looked at the system and ACP I thought a weather event had initiated the shutdown but Bob told
me weather events are disabled when shutdown is occurring. His remarks are below:
Code:
...
2023-03-16 10:27:10.3: -- Observatory Shutdown --
2023-03-16 10:27:10.3: Weather safety is now disabled
2023-03-16 10:27:10.3: Start ACP Sequencer's ShutdownObs script
2023-03-16 10:27:49.9: ** ACP script "ShutdownObs" failed:
2023-03-16 10:27:49.9: **Script Error (Tracking has been stopped)**
Source: ASCOM V2 AstroPhysics GTO Driver
Message: APCC Park failed:
Location: line 81 column 9.
2023-03-16 10:27:49.9: Weather safety is re-enabled
2023-03-16 10:27:49.9: **EXCEPTION IN SCHEDULER:
2023-03-16 10:27:49.9: Observatory shutdown failed, cannot continue.
2023-03-16 10:27:49.9: Traceback:
at DC3.Scheduler.Engine.DoShutdownIf()
at DC3.Scheduler.Engine.Run()
2023-03-16 10:27:50.2: Weather safety is now disabled
2023-03-16 10:27:50.2: Weather safety is re-enabled
2023-03-16 10:27:53.4: Running C:\Windows\SYSWOW64\cscript.exe
2023-03-16 10:27:53.4: Arguments: '"C:\Users\Public\Documents\ACP
Config\Scheduler\OperatorInterventionScript.vbs"'
2023-03-16 10:28:12.5: Results look OK, the tool returned this text:
2023-03-16 10:28:12.5: 'Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Scheduler closing the roof...
(this may take minutes)
... roof should now be closed
'
2023-03-16 10:28:12.5: Operator Intervention tool returned message:
2023-03-16 10:28:12.5: 'Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Scheduler closing the roof...
(this may take minutes)
... roof should now be closed
'
[...]
2023-03-16 10:28:16.0: ACPSequencer: Failed to get ACP's DispatcherEnabled property. ACP is compromised.
2023-03-16 10:28:16.0: Object reference not set to an instance of an object.
Log closed at Thu, Mar 16 2023 10:28:17 UTC (actual time)
Analysis:
1. Disabled weather interrupts
2. Tried to park your scope but that failed. "APCC Park failed"
3. Shutdown script failed due to the APCC runtime error
4. Enabled weather interrupts
5. Declared a Scheduler Operator Intervention due to the mount parking failure (It's getting wet or ???)
6. Ran your Operator Intervention script, which appears to try to close the roof but ACP has failed at this point.
This was a chain of failures caused by the APCC park error. I can't guess why ACP died out from under
Scheduler."
Not sure what else I can provide. The ASCOM driver is now set to log sessions.
-Steve
-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, March 17, 2023 10:39 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve,
Okay, please capture the issue again with the logs enabled.
Also, can you tell me which application(s) were locked? ACP, the driver, or APCC? Or all of them??
-Ray
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Steve Reilly
Sent: Friday, March 17, 2023 7:12 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hey Ray,
That may have been the issue with the logs as I wasn't aware that
Debug Log needed enabling in the ASCOM driver which it is now. I guess it's never been on before.....
-Steve
-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray
Gralak
Sent: Thursday, March 16, 2023 11:36 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve,
Although you included APCC and APPM logs, there are no ASCOM logs in your zip file, which I also need to see.
Make sure you have ASCOM logging enabled in the AP V2 driver.
-Ray
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Steve Reilly
Sent: Thursday, March 16, 2023 6:34 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
The link for the file is here
<https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-202
3-
03-16-
161724.zip?dl=0> on Dropbox.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of
Brian Valente
Sent: Thursday, March 16, 2023 4:45 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Thanks steve
Use the log zipper and if the resulting archive is big can you post
a link to it from Dropbox Google drive etc
Brian
On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
Brian,
I had indeed watched and followed the new APCC and driver setup
when 1st announced but watched again to be sure I didn’t miss
anything. I had updated when these 1st came out so I’ve been using
them for a fair while now. And I always use ACP, current as well,
when imaging. Do you want any APCC logs from last night and if so what should be included? The log files for the last day are almost 18MB from APCC.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 3:47 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve can you just double-check to make sure everything is
configured properly and you are following the startup routine outlined in the latest video?
https://youtu.be/7r2qujy8BkM
Otherwise it would help to know more about exactly what the error
was from ACP. zipping up the logs would help (use the APCC log
zipper
utility)
Brian
On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
I knew I’d leave something important out….
APCC – 1.9.6.7
AP1200 Firmware VCP4-P02-15
ASCOM Driver v5.60.05
The interesting thing here is the latest driver is installed but I
have the flashing message to update to the same driver version.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 2:57 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
I’m trying to nail down an issue where ACP sends a park command
to the mount but seems to hang/fail. This has happened several times
in the past but is erratic. In this case ACP was running the
shutdown script, same one I’ve used for years, and for some reason
fails to acknowledge it has parked and hangs. The difference from
before is I was using a roll off roof observatory and the mount had
to park before the roof could close. In this case now with the dome
it closes anytime regardless without issue so the dome closes then
parks the mount. This has been fine for maybe a year and
then this morning the shutdown script runs but never acknowledges it
has reached the park position. This causes ACP to fail and then
activate an Operator Intervention script. Bob’s analysis on the event is posted on the ACP forum and I can reprint here if needed.
If it wasn’t because of a past issue with Park not being
acknowledged I’d think it was an ACP issue but…..
Any ideas on what to do or what to look for. If you have access
to the ACP forum the posting is here
<http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And
yes, I had made some assumptions
that proved wrong…..again.
Thanks
-Steve
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
|
|
|
Ray,
I think I follow this but as I said the driver wasn't configured for logging which I have since turned on. So nothing before today would be found. I wasn't aware this was a feature that needed turning on. The screen capture shows the current status of the driver configuration and I did check and logs are now being created. Nothing before was of course.
-Steve
toggle quoted message
Show quoted text
-----Original Message----- From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak Sent: Friday, March 17, 2023 1:04 PM To: main@ap-gto.groups.io Subject: Re: [ap-gto] AP1200 Park Issue Steve, One more thing. Since your logs only have APCC logs, there is a possibility that the driver received other Park requests and they were rejected by the driver. That's one reason I need to see the driver logs. -Ray -----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Steve Reilly
Sent: Friday, March 17, 2023 9:30 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hey Ray,
If you remember this has been an ongoing but rare event, if they are related, and not repeatable that I'm aware of.
All my imaging sessions are done using ACP Expert, MaxIm, FocusMax v4,
APCC, Pyxis Commander (rotator), AAG CloudWatcher, and of course my
Outlet Control. The mount is only connected in APCC and then ACP. This
seemed to happen while the shutdown script was running in ACP and if I
remember this has happened before but a long time back. We had a conversation about that at the time. The same happened when I was running rescue squad some years ago where a weather event (clouds then rain) had attempted to close the roll off roof but failed.
The driver appeared hung at attempting to park, which it was actually
in that position, but ACP doesn't continue to poll after it's initial
call. At least that seems to be what I remember. That's why now I have
the dome which can close in any telescope position regardless. I wish
now I had rearranged the screen capture to better show all the active
windows....but the scope was in Park 4, which was correct, but
evidently ACP had not received the information. When I restarted the system, ACP had thrown an Operator Intervention and was idle from there on waiting on me to correct the issue. When I went into APCC and hit Park the scope didn't move, went through the normal shutdown afterwards when asked and closed as expected.
When I initially looked at the system and ACP I thought a weather
event had initiated the shutdown but Bob told me weather events are disabled when shutdown is occurring. His remarks are below:
Code:
...
2023-03-16 10:27:10.3: -- Observatory Shutdown --
2023-03-16 10:27:10.3: Weather safety is now disabled
2023-03-16 10:27:10.3: Start ACP Sequencer's ShutdownObs script
2023-03-16 10:27:49.9: ** ACP script "ShutdownObs" failed:
2023-03-16 10:27:49.9: **Script Error (Tracking has been stopped)**
Source: ASCOM V2 AstroPhysics GTO Driver
Message: APCC Park failed:
Location: line 81 column 9.
2023-03-16 10:27:49.9: Weather safety is re-enabled
2023-03-16 10:27:49.9: **EXCEPTION IN SCHEDULER:
2023-03-16 10:27:49.9: Observatory shutdown failed, cannot continue.
2023-03-16 10:27:49.9: Traceback:
at DC3.Scheduler.Engine.DoShutdownIf()
at DC3.Scheduler.Engine.Run()
2023-03-16 10:27:50.2: Weather safety is now disabled
2023-03-16 10:27:50.2: Weather safety is re-enabled
2023-03-16 10:27:53.4: Running C:\Windows\SYSWOW64\cscript.exe
2023-03-16 10:27:53.4: Arguments: '"C:\Users\Public\Documents\ACP
Config\Scheduler\OperatorInterventionScript.vbs"'
2023-03-16 10:28:12.5: Results look OK, the tool returned this text:
2023-03-16 10:28:12.5: 'Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Scheduler closing the roof...
(this may take minutes)
... roof should now be closed
'
2023-03-16 10:28:12.5: Operator Intervention tool returned message:
2023-03-16 10:28:12.5: 'Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Scheduler closing the roof...
(this may take minutes)
... roof should now be closed
'
[...]
2023-03-16 10:28:16.0: ACPSequencer: Failed to get ACP's DispatcherEnabled property. ACP is compromised.
2023-03-16 10:28:16.0: Object reference not set to an instance of an object.
Log closed at Thu, Mar 16 2023 10:28:17 UTC (actual time)
Analysis:
1. Disabled weather interrupts
2. Tried to park your scope but that failed. "APCC Park failed"
3. Shutdown script failed due to the APCC runtime error 4. Enabled
weather interrupts 5. Declared a Scheduler Operator Intervention due
to the mount parking failure (It's getting wet or ???) 6. Ran your
Operator Intervention script, which appears to try to close the roof but ACP has failed at this point.
This was a chain of failures caused by the APCC park error. I can't
guess why ACP died out from under Scheduler."
Not sure what else I can provide. The ASCOM driver is now set to log sessions.
-Steve
-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray
Gralak
Sent: Friday, March 17, 2023 10:39 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve,
Okay, please capture the issue again with the logs enabled.
Also, can you tell me which application(s) were locked? ACP, the driver, or APCC? Or all of them??
-Ray
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of Steve Reilly
Sent: Friday, March 17, 2023 7:12 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hey Ray,
That may have been the issue with the logs as I wasn't aware that
Debug Log needed enabling in the ASCOM driver which it is now. I guess it's never been on before.....
-Steve
-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray
Gralak
Sent: Thursday, March 16, 2023 11:36 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve,
Although you included APCC and APPM logs, there are no ASCOM logs in
your zip file, which I also need to see.
Make sure you have ASCOM logging enabled in the AP V2 driver.
-Ray
-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On
Behalf Of Steve Reilly
Sent: Thursday, March 16, 2023 6:34 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
The link for the file is here
<https://www.dropbox.com/s/rbn5fymb0j18akg/ApccZip-Steven_Reilly-2
02
3-
03-16-
161724.zip?dl=0> on Dropbox.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of
Brian Valente
Sent: Thursday, March 16, 2023 4:45 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Thanks steve
Use the log zipper and if the resulting archive is big can you
post a link to it from Dropbox Google drive etc
Brian
On Thu, Mar 16, 2023 at 1:22 PM Steve Reilly <sreilly24590@...> wrote:
Brian,
I had indeed watched and followed the new APCC and driver setup
when 1st announced but watched again to be sure I didn’t miss
anything. I had updated when these 1st came out so I’ve been using
them for a fair while now. And I always use ACP, current as well,
when imaging. Do you want any APCC logs from last night and if so what should be included? The log files for the last day are almost 18MB from APCC.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 3:47 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Steve can you just double-check to make sure everything is
configured properly and you are following the startup routine outlined in the latest video?
https://youtu.be/7r2qujy8BkM
Otherwise it would help to know more about exactly what the error
was from ACP. zipping up the logs would help (use the APCC log
zipper
utility)
Brian
On Thu, Mar 16, 2023 at 12:42 PM Steve Reilly <sreilly24590@...> wrote:
I knew I’d leave something important out….
APCC – 1.9.6.7
AP1200 Firmware VCP4-P02-15
ASCOM Driver v5.60.05
The interesting thing here is the latest driver is installed but
I have the flashing message to update to the same driver version.
-Steve
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Brian Valente
Sent: Thursday, March 16, 2023 2:57 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 Park Issue
Hi Steve
Just to confirm, are you on the absolute latest ASCOM V2 and APCC versions?
On Thu, Mar 16, 2023 at 11:55 AM Steve Reilly <sreilly24590@...> wrote:
I’m trying to nail down an issue where ACP sends a park command
to the mount but seems to hang/fail. This has happened several
times in the past but is erratic. In this case ACP was running the
shutdown script, same one I’ve used for years, and for some reason
fails to acknowledge it has parked and hangs. The difference from
before is I was using a roll off roof observatory and the mount
had to park before the roof could close. In this case now with the
dome it closes anytime regardless without issue so the dome closes
then parks the mount. This has been fine for maybe a year and
then this morning the shutdown script runs but never acknowledges it
has reached the park position. This causes ACP to fail and then
activate an Operator Intervention script. Bob’s analysis on the
event is posted on the ACP forum and I can reprint here if needed.
If it wasn’t because of a past issue with Park not being
acknowledged I’d think it was an ACP issue but…..
Any ideas on what to do or what to look for. If you have access
to the ACP forum the posting is here
<http://forums.dc3.com/showthread.php?t=14674&goto=newpost> . And
yes, I had made some assumptions
that proved wrong…..again.
Thanks
-Steve
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
--
Brian
Brian Valente
astro portfolio
https://www.brianvalentephotography.com/astrophotography/
portfolio brianvalentephotography.com
<http://brianvalentephotography.com>
astrobin https://www.astrobin.com/users/bvalente/
|
|
|
