Results 1 to 7 of 7
  1. #1
    Join Date
    Jun 2013
    Location
    Pasadena, CA
    Posts
    220

    Default No Scheduler activity - PWI Rotator Locked up

    Bob,

    This may or may not be related to the aquiresupport script stuff we talked about today but it started when I opened and changed the PWI callout, but I put it back to the original code.

    On Don's setup, currently, it starts up, goes to a target and just sits there waiting and never actually starts taking the image of the target it selected. I am going through the logs and see all kinds of errors I have never seen before. Here are a few snippets (I will attach the full logs).

    Attach ACP sequencer
    2019-07-14 06:44:02.5: There is no controllable dome or roof.
    2019-07-14 06:44:02.6: Weather successfully connected. Wait for valid data...
    2019-07-14 06:44:03.5: Sequencer does screen/panel flats
    2019-07-14 06:44:07.6: HTTP command listener failed to start: Access is denied
    2019-07-14 06:44:07.6: If this is Windows 8-10, you will need to add permission (ACL) to listen on port 9123.
    2019-07-14 06:44:07.6: See Scheduler Help > Configuring the Program > Noteworthy Configuration Options, at the bottom.
    2019-07-14 06:44:07.6: ++ Weather Safe ++


    Sequencer is now active
    2019-07-14 11:51:55.0: ** Script interrupted by weather safety event.
    2019-07-14 11:52:34.2: Sequencer is no longer active
    2019-07-14 11:53:04.3: Post-job status check done (stat=Running)
    2019-07-14 11:53:04.3: ACP ABORT: Acquisition process was interrupted by weather unsafe.
    2019-07-14 11:53:04.3: ACP data acquisition failed for Observation M 27.
    2019-07-14 11:53:04.3: (Plan M 27-SII 300s (13-24) will be resubmitted in its entirety.
    2019-07-14 11:53:04.3: (Observation M 27 interrupted by weather unsafe event.)
    2019-07-14 11:53:04.5: -- Weather Unsafe --
    2019-07-14 11:53:05.5: ++ Morning Screen Flats ++
    2019-07-14 11:53:05.5: Start ACP AutoFlat script for panel/screen flats
    2019-07-14 11:53:05.5: ACP.RunScript(AutoFlat, C:\Users\Telescope Control\Documents\ACP Astronomy\Plans\SchedulerDawnFlats.txt):
    2019-07-14 11:53:05.5: Script ACP-Weather is loaded, and
    2019-07-14 11:53:05.5: the console is idle.
    2019-07-14 11:53:05.5: In start loop, i = 0
    2019-07-14 11:53:05.5: Console is now idle
    2019-07-14 11:53:05.6: Loaded C:\PROGRA~2\ACPOBS~1\Scripts\AutoFlat.vbs successfully
    2019-07-14 11:53:05.6: Set parameter "C:\Users\Telescope Control\Documents\ACP Astronomy\Plans\SchedulerDawnFlats.txt" successfully
    2019-07-14 11:53:05.6: Script started successfully
    2019-07-14 11:53:15.6: Sequencer is now active
    2019-07-14 12:27:42.1: **DISPATCHER INTERRUPT LEVEL 1 RECEIVED**
    2019-07-14 12:27:56.7: Sequencer is no longer active
    2019-07-14 12:27:56.7: ** ACP script "AutoFlat" failed:
    2019-07-14 12:27:56.7: **Script Error**
    Source: ACP
    Message: The script was aborted.
    Location: line 804 column 13.




    2019-07-15 15:14:38.7: -- Observatory Shutdown --
    2019-07-15 15:14:38.7: Start ACP Sequencer's ShutdownObs script
    2019-07-15 15:14:38.7: ACP.RunScript(ShutdownObs, ):
    2019-07-15 15:14:38.7: Script ShutdownObs is loaded, and
    2019-07-15 15:14:38.7: the console is idle.
    2019-07-15 15:14:38.7: In start loop, i = 0
    2019-07-15 15:14:38.7: Console is now idle
    2019-07-15 15:14:38.7: Loaded C:\Users\Public\Documents\ACP Config\Scheduler\ShutdownObs.js successfully
    2019-07-15 15:14:38.7: Script started successfully
    2019-07-15 15:14:48.7: Sequencer is now active
    2019-07-15 15:14:53.7: Sequencer is no longer active
    2019-07-15 15:15:36.8: ACPSequencer: transient error getting DispatcherEnabled.
    2019-07-15 15:15:36.8: The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. (Exception from HRESULT: 0x80010007 (RPC_E_SERVER_DIED))
    2019-07-15 15:15:36.8: ACPSequencer: transient error getting DispatcherEnabled.
    2019-07-15 15:15:36.8: The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. (Exception from HRESULT: 0x80010007 (RPC_E_SERVER_DIED))
    2019-07-15 15:15:37.3: ACPSequencer: transient error getting DispatcherEnabled.
    2019-07-15 15:15:37.3: The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. (Exception from HRESULT: 0x80010007 (RPC_E_SERVER_DIED))
    2019-07-15 15:15:37.3: **EXCEPTION IN SCHEDULER:
    2019-07-15 15:15:37.3: The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. (Exception from HRESULT: 0x80010007 (RPC_E_SERVER_DIED))
    2019-07-15 15:15:37.3: Traceback:
    at ACP.UtilClass.get_Scheduler()
    at DC3.Scheduler.ACPSequencer.set_DispatcherStatus(St atusValue value)
    at DC3.Scheduler.Engine.set_Status(StatusValue value)
    at DC3.Scheduler.Engine.Run()
    2019-07-15 15:15:37.3: DOME/ROOF FAILURE: In addition, attempting to close your dome/roof this error occurred:
    2019-07-15 15:15:37.3: The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. (Exception from HRESULT: 0x80010007 (RPC_E_SERVER_DIED))
    2019-07-15 15:15:37.3: ACPSequencer: transient error getting DispatcherEnabled.
    2019-07-15 15:15:37.3: The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. (Exception from HRESULT: 0x80010007 (RPC_E_SERVER_DIED))
    2019-07-15 15:15:37.3: ACPSequencer: transient error getting DispatcherEnabled.
    2019-07-15 15:15:37.3: The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. (Exception from HRESULT: 0x80010007 (RPC_E_SERVER_DIED))
    2019-07-15 15:15:37.4: No operator intervention command tool specified





    Are any of these errors related to the weather fix?

    Paul
    Attached Files Attached Files

  2. #2
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    26,245

    Default

    In all of this I never see it go to target.

    Analyzing the logs:

    20190715@235845.txt
    ...
    2019-07-15 23:58:52.8: Weather successfully connected. Wait for valid data...
    2019-07-15 23:58:53.3: Sequencer does screen/panel flats
    ...
    2019-07-16 01:37:56.8: ++ Weather Safe ++
    2019-07-16 11:53:04.8: -- Weather Unsafe --

    --- LOG ENDS HERE DID YOU TASK SCHEDULER KILL IT? ---

    It never even tried to run the startup script. It sat there all night. The dispatcher was started, the weather went safe a half hour later, and nothing happened all night, then the log simply ended with no further action on the part of the scheduler. Weird. Let me analyze the others...

    20190715@143955.txt

    1. Started in unsafe weather. I noted that the SampleStartupObs had been loaded into ACP's console before this. That seems strange.
    2. The scheduler immediately shut down. I note that the ACP-Weather script was somehow loaded into ACP after the StartupObs script. This is even stranger since the weather has not gone from unsafe to safe and back to unsafe. How could this happen? What caused it to shut down without any changes in weather condition???
    3. Now the scheduler shut down again. This is completely strange.

    I have to say I am stumped on this one and will likely need to do some live testing at Don's for this.

    20190714@064414.txt

    2019-07-14 07:36:27.4: Acquire data for Observation M 27...
    2019-07-14 07:36:27.4: (belongs to Project M 27, Plan M 27-SII 300s (13-24))
    2019-07-14 07:36:27.4: ACP Last AF Time 12-Jul-2019 09:26:14 UTC
    2019-07-14 07:36:27.4: Send Observation M 27 to ACP Sequencer
    2019-07-14 07:36:27.4: ACP.RunScript(AcquireScheduler, ):
    ... 4 and a half HOURS later...
    2019-07-14 11:51:55.0: ** Script interrupted by weather safety event.
    2019-07-14 11:52:34.2: Sequencer is no longer active
    2019-07-14 11:53:04.3: Post-job status check done (stat=Running)
    2019-07-14 11:53:04.3: ACP ABORT: Acquisition process was interrupted by weather unsafe.


    so far this looks fine except for the LONG LONG running job. I would need to see the individual ACP run log for Project M 27, Plan M 27-SII 300s (13-24) to see why it ran so long. Probably ran into daylight as the unsafe weather condition. Something got stuck most likely, and caused the acquisition process to stall. No errors though, just super unusual. The weather unsafe (too light) unstuck it. Now, immediately it decides that it's time to do morning screen flats.

    2019-07-14 11:53:04.5: -- Weather Unsafe --
    2019-07-14 11:53:05.5: ++ Morning Screen Flats ++
    2019-07-14 11:53:05.5: Start ACP AutoFlat script for panel/screen flats
    ...
    2019-07-14 11:53:15.6: Sequencer is now active


    A half hour later it appears that the AutoFlat process was just killed by hitting the abort button.

    2019-07-14 12:27:42.1: **DISPATCHER INTERRUPT LEVEL 1 RECEIVED**
    2019-07-14 12:27:56.7: Sequencer is no longer active
    2019-07-14 12:27:56.7: ** ACP script "AutoFlat" failed:
    2019-07-14 12:27:56.7: **Script Error**
    Source: ACP
    Message: The script was aborted.
    Location: line 804 column 13.

    Then it sat there all day until the "too light" unsafe condition went away and then

    2019-07-15 02:26:48.4: ++ Weather Safe ++
    2019-07-15 11:50:42.9: -- Weather Unsafe --


    Another night doing absolutely nothing. This looks for all the world like there was just nothing to to. The log level is Extreme so there must not be anything at all that can even be looked at??? Again for this I will need to get on to that system to look and probably watch live.

    20190714@064353.txt

    2019-07-14 06:44:03.5: Sequencer does screen/panel flats
    2019-07-14 06:44:07.6: HTTP command listener failed to start: Access is denied
    2019-07-14 06:44:07.6: If this is Windows 8-10, you will need to add permission (ACL) to listen on port 9123.
    2019-07-14 06:44:07.6: See Scheduler Help > Configuring the Program > Noteworthy Configuration Options, at the bottom.
    2019-07-14 06:44:07.6: ++ Weather Safe ++
    2019-07-14 06:44:14.7: Run statistics:
    ... etc

    Here it started up, and immediately exited. Again I have no clue how this can happen. There's going to be an "AH HA" moment but I need to see all of this stuff with my own eyes. I can't imagine how it can happen right now.

    Are any of these errors related to the weather fix?
    No.
    -- Bob

  3. #3
    Join Date
    Jun 2013
    Location
    Pasadena, CA
    Posts
    220

    Default

    OK. I adjusted some PWI settings to see if the mount was just sitting there waiting to settle. I have had lots of issues with PWI hanging up and it doesn't offer any feedback. like a rotator will get stuck and it just sits there and does nothing so ACP sits there waiting for the word that PWI is done slewing. The system is running right now, waiting for dark. I am going to keep a close eye on It tonight.

    Like I always say....I am good at breaking things.

    Paul

  4. #4
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    26,245

    Default

    Doggone it. I can't join you tonight. I seriously doubt that all of this stuff is due to a PWI settling issue.

    I want to see it because I have a release I need to get out and I HATE to think about doing that with this sort of inscrutable weirdness going on!!!!! Actually this is going to stall that release until I get all of the issues understood and dealt with as needed.

    Is it possible to get together on this tomorrow night? Or ASAP????
    -- Bob

  5. #5
    Join Date
    Jun 2013
    Location
    Pasadena, CA
    Posts
    220

    Default

    tomorrow will be fine. I will watch and take notes tonight.

  6. #6
    Join Date
    Jun 2013
    Location
    Pasadena, CA
    Posts
    220

    Default

    it was totally a PWI issue. The rotator was locked into a hard limit. PWI isn't intelligent enough to know that and will just set there waiting to finish a slew literally until the sun comes up.

  7. #7
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    26,245

    Default

    The rest of this thread was unrelated to this issue, so it has been moved to

    Thread: AcquireSupport does not support PlaneWave PWI2
    -- Bob

 

 

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. PWI Focuser Error causes ACP to freeze and Scheduler to fail with a Windows error box
    By Russell Carroll in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 6
    Last Post: Apr 22, 2017, 22:25
  2. PWI Software Too Old (was: ACP 7.2 and PWI 3.2.4)
    By Colin Eldridge in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 4
    Last Post: Sep 23, 2014, 14:39

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •