The log says it all. The dispatcher needs to check if a weather interrupt occurred during autofocus.



20-Nov-2011 00:18:05.4: ConnectWeather(), already connected.

20-Nov-2011 00:18:05.4: ++ Weather Safe ++

20-Nov-2011 00:18:06.4: Weather disconnected.

20-Nov-2011 00:18:06.5: ++ Observatory Startup ++

20-Nov-2011 00:18:06.5: Start ACP Sequencer's StartupObs script

20-Nov-2011 00:18:16.5: Sequencer is now active

20-Nov-2011 00:18:23.5: Sequencer is no longer active

20-Nov-2011 00:18:23.7: Weather successfully connected.

20-Nov-2011 00:18:29.6: ++ Auto Focus ++

20-Nov-2011 00:18:29.6: Doing initial autofocus.

20-Nov-2011 00:18:29.6: Start special ACP AutoFocus script for scheduler

20-Nov-2011 00:18:39.6: Sequencer is now active

20-Nov-2011 00:18:46.9: Sequencer is no longer active

20-Nov-2011 00:18:46.9: ** Autofocus failed (n=1), will retry ASAP after 0 min.

20-Nov-2011 00:18:46.9: **EXCEPTION IN SCHEDULER:

20-Nov-2011 00:18:46.9: The telescope is not connected.

20-Nov-2011 00:18:46.9: Traceback:

at ACP.TelescopeClass.get_SlewSettleTime()

at DC3.Scheduler.ACPSequencer.get_SlewSettleTime()

at DC3.Scheduler.Engine.CalculateTimeSpans(Plan P, ArrayList OList)

at DC3.Scheduler.Engine.DoSchedulePass()

at DC3.Scheduler.Engine.Run()




SEE ACP-757 FOR MARCH 2012 (3.5) ACTIVITY

Closing, collected into SCHEDULER-816 (see link)

More problems. The whole thing of disconnecting and reconnecting weather is a loser. The 3.5 BETA is experiencing fatal weather related disconnects and "server gone" errors. This has to be re-worked!!!!!



Reopened all of the related issues on this.

See ACP-757. Closing this.