Results 1 to 10 of 13

Threaded View

  1. #1

    Default Dome Controller causes Operator Intervention in Scheduler

    Hi Bob

    I was able to do the first light test with Scheduler yesterday.
    Startup script, and imaging went fine but there seems to be some kind of a problem:

    The scheduler says "Operator Intervention" and I found this in the log:

    2017-02-13 23.35.06.9: **EXCEPTION IN SCHEDULER:
    2017-02-13 23.35.06.9: Inndatastrengen hadde ugyldig format. (Trasnlated to English): Input string had an invalid format.

    When I checked the observatory this morning, it looked like this:

    Dome shutter was closed
    Mount tracking stopped
    FocusMax and Maxim still running
    Cooler on
    Dragonfly relays still closed
    FlitFlap still open

    So it seems there might be a problem with the shutdown script?
    I've attached the log and the shutdown script.

    Can it be something about the date/time format, similar to the problem I had with the Scheduler Engine not working?
    Hope you can help me out here.

    Thanks,
    Kristian
    Attached Files Attached Files

 

 

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Dome/Roof Control Issues (was: repeated operator intervention)
    By Bruce McMath in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 12
    Last Post: Apr 16, 2016, 20:53
  2. Testing Scheduler Operator Intervention Tool
    By Dave Wormuth in forum Pre-Sales Technical Questions and Help
    Replies: 1
    Last Post: Jan 9, 2016, 18:07
  3. Scheduler did not report that operator intervention was needed after one hour
    By Robert Capon in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 3
    Last Post: Nov 25, 2014, 17:27

Posting Permissions

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