Scheduler did not report that operator intervention was needed after one hour
Bob:
If you take a look at this thread, you'll see I'm providing more data to Tim on the DDW driver. Yet another case where the driver is coming up short:
http://forums.dc3.com/showthread.php...9229#post49229
But I do have one Scheduler question. At 6:00 a.m., Scheduler sends a shutdown command. But when I woke up at 7:00 a.m., the ACP window says "Dome Closing".
So why did Scheduler/ACP start a shutdown command, and leave the state as "Dome Closing" without noticing that the shutdown sequence was stuck and send a "Fatal" message that operator intervention is necessary? The dome was hung up, but Scheduler/ACP did not take action. At present, if the "Fatal" email went out, I would have gotten a text message and two phone calls (landline and mobile).
Best,
Rob
Rob Capon
(Self-appointed) "Executive Director"
Stillhouse Mountain Observatory
Charlottesville, VA
----------------------------------
RCOS 12.5 with SBIG STL11000M
Televue NP101is with SBIG ST8300
Paramount ME with SkyX
Techn. Innovations PD10 with Digital Domeworks
Robofocuser
ACP with MaximDL and FocusMax