Results 1 to 4 of 4

Threaded View

  1. #1

    Default 10 Micron Scope does not raise error on failure of Connected=True

    Hi Bob

    Occasionally it happens that the scope does not connect during StartupObs, but instead of reporting an exception it just reports 'OK'. I've customised StartupObs quite a lot and I've attached the full file, but the relevant code is:

    Code:
        try {
            if(!Telescope.Connected) {
                Util.WaitForMilliseconds(5000);
                Console.PrintLine("Connect ACP to the telescope, will auto-home if needed");
                Telescope.Connected = true;                  // (Requires driver "home on connect")
                Console.PrintLine("OK");
            } else {
                Console.PrintLine("Telescope already connected");
            }
        } catch(ex) {
            Console.PrintLine("**StartupObs Failed to connect to the Telescope:");
            Console.PrintLine("  " + ex.description);
            throw new Error(0x80040001, "==== Startup failed, cannot continue");
        }
    I would prefer the startup to fail so I get an email notification and can take corrective action. I was hoping you might spot why this is happening (not the failure to connect, but the failure to report the failure).

    Thanks
    Peter.
    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. Telescope.Connected = true Fails to connect telescope
    By Gerald Ruch in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 5
    Last Post: Jul 25, 2012, 14:49
  2. Sync Scope failure...
    By Chris Brennan in forum Hardware/Software/Driver Topics Not Directly Related to Our Software
    Replies: 6
    Last Post: Jan 3, 2009, 00:37

Posting Permissions

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