Results 1 to 10 of 23

Threaded View

  1. #22
    Join Date
    Nov 2005
    Location
    Virgil, NY
    Posts
    5,125

    Default

    Hi Bob,

    I understand from your reply that my comments are not the issue for Peter's current problem.

    My question is about the 30-second delay during dome opening. Unfortunately, my memory of how this delay came to be is really dim, but I know the change was made in the fall of 2018 while I was finishing my own ASCOM dome driver, and someone else was also having a similar problem. Could it have had to do with weather interrupts prior to the era of disabling weather interrupts? You provided a revised scheduler.exe at the time. For my own case, though, I would like that 30-second OpenDome() delay changed back to what was the original 3-second value. Here's what happens.

    When starting up in Scheduler, StartupObs runs as usual. After StartupObs finishes, a few seconds later, or later when weather permits, Scheduler opens the dome. My dome opens in about 7 seconds. The Dome Control Panel in the ACP console stops flashing "Opening" at that time and displays "Open." But in the web browser, Scheduler continues to flash "Opening" and pauses processing for that additional 30 seconds before resuming.

    This is certainly not critical, but it sure is an annoying and useless delay from my point of view. Having written all this out and now reading it back to myself, it seems silly to go on about this. So despite my annoyance, whatever suits your determination about the needs of other users will be okay with me.


    EDIT:

    Bob, I don't want to bring up bad memories, so I'm changing my mind. I finally found the origin messages relating to the "blind ignore" of 30 seconds in DomeOpen(). The discussion began on June 4, 2018 with a message from Piyush Patel regarding the Foster Systems dome control. (http://forums.dc3.com/showthread.php...0055#post70055) It proceeded through several message threads over the course of 5 months to include me, Jerry Yesavage, Ron Crouch, Jon Swift, and Colin Haig. Your definitive response on Nov 28, '18 was here: http://forums.dc3.com/showthread.php...3020#post73020.

    In my own case, I don't believe 3 seconds would be a problem in my driver anymore, but I'm not eager to have you change back to 3 seconds only to find out my dome driver breaks again.
    Last edited by Dick Berg; Sep 15, 2020 at 14:02.
    Dick
    www.VirgilObservatory.us
    Pier-mounted Meade 12-inch SCT "classic"
    w. focal reducer to f/5.3 ~ FL 1630mm
    Optec TCF-S focuser
    SBIG CFW-8A and ST7-XME
    FOV ~ 15' x 10'
    H-alpha, BVRI, RGB & Clear filters
    MaxIm and, of course, ACP!
    AAVSO Code: BRIC

 

 

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. MaximDL crashes possible relationship to ACP
    By Peter Prendergast in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 27
    Last Post: Sep 16, 2015, 19:15
  2. ACP Crashes after parking scope (TheSky X)
    By Chris Johnson in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 5
    Last Post: Nov 20, 2010, 14:55

Posting Permissions

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