All:

First of all, Thank you everyone for the insight on the various posts. It provides a lot of information.

I have almost completed the integration of HW and SW with ACP and also have few nights of hands off imaging. What amazes me is that ACP does everything in half the time that I would have done - things like slewing, guider setups, finding a star, focusing, slewing back to target, platesolving, reslews if needed, starting imaging session ;-)

Now, I am running into a problem that has been discussed a few time and want to solicit what others are doing with similar setup.

Equipment:
Backyard Observatories Roll off Roof and Motor.
Foster Systems Roof controller.

Issue: When the Scheduler opens the roof, it reports "Operator Intervention". The issue has been discussed in the below threads and it points to Foster Systems driver reporting "closed". I believe I am running into the same issue.Stan from Foster Systems had also commented on the thread. At one point in time, Bob graciously changed the delay from 10 to 20 seconds. Guess what - Looking at the logs, in my case it reports an exception/issue with the roof after 20.1 or 20.2 seconds. Coming from IT industry I understand the reasoning behind the stance from both the vendors. I am trying to see what I can do to bring this "closed" reporting under 20 seconds or anything else that could be done.

Old Threads:
http://forums.dc3.com/showthread.php...-Scheduler-3-5
http://forums.dc3.com/showthread.php...r-roof-opening

Log snippet from different days:

2018-05-25 01:15:05.4: Open the observatory dome/roof
2018-05-25 01:15:25.5: **Dome closed while opening. Assuming weather closure.
2018-05-25 01:15:25.5: **EXCEPTION IN SCHEDULER:
2018-05-25 01:15:25.5: **Dome failed to open for reason other than hardware weather closure

2018-05-25 06:15:08.6: Open the observatory dome/roof
2018-05-25 06:15:28.7: **Dome closed while opening. Assuming weather closure.
2018-05-25 06:15:28.7: **EXCEPTION IN SCHEDULER:
2018-05-25 06:15:28.7: **Dome failed to open for reason other than hardware weather closure

2018-05-30 01:03:23.2: Open the observatory dome/roof
2018-05-30 01:03:43.4: **Dome closed while opening. Assuming weather closure.
2018-05-30 01:03:43.4: **EXCEPTION IN SCHEDULER:
2018-05-30 01:03:43.4: **Dome failed to open for reason other than hardware weather closure

2018-06-03 03:41:43.3: Open the observatory dome/roof
2018-06-03 03:42:03.4: **Dome closed while opening. Assuming weather closure.
2018-06-03 03:42:03.4: **EXCEPTION IN SCHEDULER:
2018-06-03 03:42:03.4: **Dome failed to open for reason other than hardware weather closure

2018-06-04 01:12:05.6: Open the observatory dome/roof
2018-06-04 01:12:25.7: **Dome closed while opening. Assuming weather closure.
2018-06-04 01:12:25.7: **EXCEPTION IN SCHEDULER:
2018-06-04 01:12:25.7: **Dome failed to open for reason other than hardware weather closure




Currently, I either open the roof manually or let it fail, kill scheduler and reopen and dispatch it again. But I still have to continue to monitor, cause, if it closed due to bad weather and then reopened, the scheduler will be waiting and if weather gets bad again, it would be unable to safe it.

The whole roof takes 37 seconds to open. I will also send an email to Stan shortly. Any ideas, suggestions on what else could be done to bring the issue reported below 20 seconds.

Thank you,

/Piyush