Hi Bob
My Scheduler crashed last night while idle due to lack of work. The following 4 messages were displayed on screen. I've also attached the scheduler engine log.
This was one of the reasons I had a fresh Windows install done on my observatory PC...looks like that wasn't the cause. I noticed though that the exception happened just short of 200 minutes since the last activity. I wonder if something times out or goes to sleep?
Peter.
Thank you very much for gathering this data from your screen!!
It was Scheduler polling ACP for its status and ACP had a fatal error while polling one of the devices. The lower right error box holds the key. This was a chain reaction error started when one of the devices (I'm going to guess the Dome or Telescope/Mount control program) ended. ACP says it lost its connection to some executable, which compromised ACP, which compromised Scheduler. Which of your devices is controlled by an ASCOM executable? It was one of those. Does this help at all?
Thanks Bob for the quick reply. I have raised the issue with my IT support guy and will let you know the outcome.
I don't control the roof directly but ACP's weather server polls a roof status app every 30 seconds...perhaps that's the culprit.
Peter.
My IT guy has had a look and found that there was a device failure on my MCD Hub (this is a 6-port USB hub that I can control remotely, gives me the virtual ability to unplug/re-plug devices myself). He has updated a couple of drivers and we'll see how things go.
Peter.
Ah, OK. Thanks Peter.