Results 1 to 8 of 8
  1. #1
    Join Date
    Nov 2005
    Location
    Ellinbank, Victoria, Australia
    Posts
    131

    Default AP Parking freeze causes Scheduler Freeze

    Hello Bob,
    I'm running the latest versions of expert and MaxIm.
    I have two issues:
    1. After a cloud interval passes ACP reports its waiting for 10 minutes of clear weather, unfortunately several hours may pass and
    the observatory still does not open. This is the most important issue as there are early morning targets I need to get.
    2. Shutdown script parks the scope but does not warm the camera up and shutdown MaxIm. This is a relatively minor issue.

    I have included a couple of screen shots from the last couple of nights. You can see the last observation was before midnight, there was
    an interval of cloud, but several hours of clear weather occurred but the observations didn't resume.

    What logs do you need?

    Thanks
    Peter
    Attached Images Attached Images

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

    Default

    What logs do you need?
    The Scheduler Engine Logs (My Documents\ACP Astronomy\Scheduler Engine logs). I do not need the RunDetail files, just the Scheduler engine Logs from the problem nights. Attach them here, no need to zip or whatever, I have "unlimited" disk storage on the Comm Center. I am going to suspect the weather input so please also attach the latest weather server trace... hopefully it is from a night where you had problems. Only the latest is saved. You will find it in My Documents\ACP Astronomy\Logs with a name like BoltwoodFileTrace.log.

    Did this "just start happening"?
    -- Bob

  3. #3
    Join Date
    Nov 2005
    Location
    Ellinbank, Victoria, Australia
    Posts
    131

    Default

    Hi Bob,
    Attached are the files from the 14th where the observatory did not reopen after after about 2 hrs of cloud (starting around 23:00). There was about 2 hrs of clear weather after that. ACP kept reporting that it was waiting for 10 mins of clear weather.
    Its hard to be certain when this issue started but it seems to be after I upgraded to the latest version.
    This also happened on the 12 March.
    The weather files span 2 days eg 2019-03-14 2019-03-15

    Thanks
    Peter
    Attached Images Attached Images
    Attached Files Attached Files

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

    Default

    This is an easy one. Both of your Scheduler Engine logs show this pattern:

    2019-03-15 16:24:39.3: -- Weather Unsafe --
    2019-03-15 17:02:36.0: ++ Weather Safe ++
    2019-03-15 17:02:37.6: ++ Observatory Startup ++
    2019-03-15 17:02:37.8: Start ACP Sequencer's StartupObs script
    2019-03-15 17:02:39.3: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:03:39.3: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:04:39.3: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:05:39.6: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:06:39.9: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:07:40.2: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:08:40.4: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:09:40.7: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:10:41.1: WARNING: Request sent while Weather Safety Script is running
    2019-03-15 17:11:41.2: WARNING: Request sent while Weather Safety Script is running

    2019-03-15 17:12:41.5: WARNING: Request sent to busy ACP (ShutdownObs)
    2019-03-15 17:13:41.5: WARNING: Request sent to busy ACP (ShutdownObs)
    2019-03-15 17:14:41.8: WARNING: Request sent to busy ACP (ShutdownObs)
    2019-03-15 17:15:42.2: WARNING: Request sent to busy ACP (ShutdownObs)
    2019-03-15 17:16:42.2: WARNING: Request sent to busy ACP (ShutdownObs)
    2019-03-15 17:17:42.2: ERROR: Failed to start ACP script due to ACP being busy or locked
    2019-03-15 17:17:42.6: **EXCEPTION IN SCHEDULER:
    2019-03-15 17:17:42.6: Observatory startup failed, cannot continue.

    This is due to your weather safety script getting stuck. Before doing anything else, start up your observatory but do not start the Scheduler. Open up the dome or roof. Get things into the condition where it is ready to observe. Now, in the ACP console, load ACP-Weather.xxx, and start it. You should see that at some point it stops and just sits there waiting for something to finish. What is going on? Is the Dome/Roof stuck closing? Whatever is preventing ACP-Weather from completing is at the root of your problem.
    -- Bob

  5. #5
    Join Date
    Nov 2005
    Location
    Ellinbank, Victoria, Australia
    Posts
    131

    Default

    Thanks Bob.. Problem lay with a discrepancy between ASCOm and ACP in tracking and parking.
    Reloading the AP driver fixed the problem :-)
    Peter

  6. #6
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    26,879

    Default

    Was this in essence a problem with the AP control system (driver/APCC)? Was it that the AP mount was not reporting that it had finished parking, and thus ACP was waiting in the Weather Safety script for this? That's what I am guessing right now.

    I will be unhappy if the ASCOM libraries or interfaces were involved.
    -- Bob

  7. #7
    Join Date
    Nov 2005
    Location
    Victoria, Australia
    Posts
    5

    Default

    Prior to the reinstall, the mount operated correctly from MaximDL which showed the same tracking/parked status as APCC (eg: the mount reported that it was parked (eventually) after a park command was issued - verified using Pipe). An uninstall and reinstall of the AP driver (and consequent reselect of the driver in both ACP & MaximDL) seems to have rectified the problem.

  8. #8
    Join Date
    Oct 2005
    Location
    Mesa, AZ
    Posts
    26,879

    Default

    Ok. Note that MaxIm may not bother trying to determine if the park has completed. ACP on the other hand insists that the mount report completion (AtPark = true). This is by design. If the mount is not acting right, you’ll see something in ACP....
    -- 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, 23:25
  2. AP 900 Mount not reporting AtPark, causes shutdown freeze
    By Bruce McMath in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 31
    Last Post: Feb 23, 2017, 20:47

Posting Permissions

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