TheSky X 22007 Limit Error

[Peter Prendergast]

Bob:
Just installed the latest version of TSXPro daily build designed to deal with error 22007 and it appears it has. I got the following failure from scheduler. TSXPro is still working perfectly, no reported error, tracking along just fine. What do you think is happening here?
Peter


02-Dec-2011 00:37:24.7: No pending plans that can be started now.
02-Dec-2011 00:37:24.7: Dispatcher cycle time: 0.011 sec.
02-Dec-2011 00:37:54.8: ConnectWeather(), already connected.
02-Dec-2011 00:37:54.8: SelectRunning: No running plans
02-Dec-2011 00:37:54.8: No pending plans that can be started now.
02-Dec-2011 00:37:54.8: Dispatcher cycle time: 0.01 sec.
02-Dec-2011 00:38:24.9: ConnectWeather(), already connected.
02-Dec-2011 00:38:25.0: SelectRunning: No running plans
02-Dec-2011 00:38:25.0: Efficiency: Only one pending plan ngc 604-Luminesence (1-6), it is the "best"
02-Dec-2011 00:38:25.0: Dispatcher cycle time: 0.0550055 sec.
02-Dec-2011 00:38:25.0: Acquire data for Observation ngc 604...
02-Dec-2011 00:38:25.0: Send Observation ngc 604 to ACP Sequencer
02-Dec-2011 00:38:35.0: Sequencer is now active
02-Dec-2011 01:47:48.7: Sequencer is no longer active
02-Dec-2011 01:47:48.7: Post-job status check done (stat=Completed)
02-Dec-2011 01:47:48.7: Acquisition time: 4163.7038228 sec.
02-Dec-2011 01:47:48.7: Data for Observation ngc 604 acquired successfully.
02-Dec-2011 01:47:48.7: Image Efficiency: 86.5%
02-Dec-2011 01:47:48.7: Cycle Efficiency: 100.0%
02-Dec-2011 01:47:48.8: ConnectWeather(), already connected.
02-Dec-2011 01:47:48.8: ++ Auto Focus ++
02-Dec-2011 01:47:48.8: Doing periodic autofocus.
02-Dec-2011 01:47:48.8: Start special ACP AutoFocus script for scheduler
02-Dec-2011 01:47:58.8: Sequencer is now active
02-Dec-2011 01:49:40.9: Sequencer is no longer active
02-Dec-2011 01:49:40.9: ** Autofocus failed (n=1), will retry ASAP after 0 min.
02-Dec-2011 01:49:40.9: **EXCEPTION IN SCHEDULER:
02-Dec-2011 01:49:40.9: The telescope is not connected.
02-Dec-2011 01:49:40.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()
02-Dec-2011 01:49:41.2: Run statistics:
02-Dec-2011 01:49:41.2: Observations: 292
02-Dec-2011 01:49:41.2: Considered: 229
02-Dec-2011 01:49:41.2: Completed: 203
02-Dec-2011 01:49:41.2: Skipped: 24
02-Dec-2011 01:49:41.2: Never Eligible: 63
02-Dec-2011 01:49:41.2: Failed: 2
02-Dec-2011 01:49:41.2: Shutter-Open efficiency: 81.55%
02-Dec-2011 01:49:41.2: Overall Efficiency: 99.90%
02-Dec-2011 01:49:41.2: Release ACP sequencer
Log closed at Fri, Dec 02 2011 01:49:42 UTC (actual time)

[Bob Denny]

Can you find the corresponding Autofocus log from ACP? It will tell how the scope got disconnected. Some sort of error like weather, dome problem, scope hiccup, ??? The log from the Autofocus run will have the smoking gun. I promise to make atofocus failures non-fatal in the next release.

[Peter Prendergast]

Not sure which log you mean? Feel free to noodle around in the obs Bob. Let me know this is new.

[Bob Denny]

Oh wait! Did I read that they maybe FOUND and FIXED the 22007 problem??? This would be very good news on a bunch of levels.

[Peter Prendergast]

yep that is the correct reading. But why did this fail then???? I did not have a 22007 error last night or so far tonight. However, it can take up to a week for it to rear its ugly head. I have followed their instructions to the letter for further error tracking should it occur. Did you also see my other post weird error but not a disaster like 22007 was!! Image time out?? Well its in another post.

[Peter Prendergast]

but unfortunately as I was typing this it reared its ugly head again. Went through the steps they asked and emailed the data to them. Pretty hefty log of stuff they've created so looks like more insight may be possible. By the way AGAIN with a call for auto focus this has come up. Rather odd.

[Bob Denny]

Just the timing of the slews involved in the AutoFocus. I'm moving this to the Hardware/Driver section since this is not an issue with ACP or Scheduler, but with TheSky X which is a telescope control system/driver in its role here.

[Peter Prendergast]

I don't understand there was NO TSXPro error???????

[Bob Denny]

then what caused the scope to disconnect? I am still working through my backlog. Help me by looking for the corresponding ACP run logs and seeing what you can see. Perhaps they'll answer; If needed I can get on to your system probably tomorrow.

[Peter Prendergast]

The scope wasn't disconnected except by the weather script. Thus ACP did its job, disconnected the scope shut the dome. But some how Scheduluer didn't pick up on that. Wierd stuff. I hate that this is so muddled. But it is my experience. This junk goes away on a clear night then scheduler is like a demon grabbng data down. Even with all this junk I still managed to grab some OIII frames last night and a few Blue frames...these are 30 minute exposures.. Help yourself to the logs you can use team viewer or my web page as I just did to look they are all up there.

Hey it aint all bad, tons of stuff that was not working is working! Oh and I think I have referred a new customer to you...he'll probably be buying ACP after the first of the year.