CCDWare, Ltd.    CCDWare Support Community    Forums  Hop To Forum Categories  CCDWare Products  Hop To Forums  CCDAutoPilot 3    Other cloud sensor logic problems??
Go
New
Find
Notify
Tools
Reply
  
-star Rating Rate It!  Login/Join 
Good Seeing
Posted
John--Looking back at some logs, there are a couple of other situations that may be worth looking at:

1. Meridian flip caused continued waiting after a very cloudy condition was encountered. I would expect the merdian flip wait to be trumped by the v.c. condition. Also you will see the same "post close" problems as in my previous post:

05:14:02 Dither: -1.5, -2.6,
05:14:10 Guider running
05:14:16 Guide Error X: 1.2, Y: 3.7
05:14:22 Guide Error X: 0.7, Y: 2.3
05:14:29 Guide Error X: 0.1, Y: 0.2
05:14:29 Altitude: 48 deg.
05:14:29 Exposing...
05:23:01 Pause after the current exposure for clouds...
Pause after the current exposure for clouds...
05:25:09 C:\Users\Owner\Documents\CCDWare\CCDAutoPilot3\Images\080117_M104\Luminance82E_M104_00104.fit
05:25:12 Waiting for meridian flip time...
05:26:10 *** Aborting run due to very cloudy conditions (3).
*** Aborting run due to very cloudy conditions (3).
05:32:32 Meridian flip starting...
05:32:33 Guider stopped.
05:32:34 Current Rotator position: -278.7
05:32:34 Slewing scope...
05:34:23 Slewed to RA: 12 40 24.5, Dec: -11 40 08
05:34:23 Mount settling for 3 sec. after slew.
05:34:30 Rotator movement to -98.7 complete
05:34:31 Rotator position: -98.7
05:34:32 AO recentered
05:34:32 Adjusting PM pointing location...
05:34:32 Pointing error (arcmin): RA -11399.6; Dec 697.4
05:34:32 Excessive correcting slew not made
05:34:32 Meridian Flip completed.
05:34:32 Telescope RA: 12 40 24.6, Dec: -11 40 07
05:34:32 Refreshing guide star location...
05:34:45 Guide star peak value: 891
05:34:48 Guider running
05:34:48 Guider x: 133.5, y: 43.6
05:34:49 Guider stopped.
05:34:49 Trying to park mount due to clouds.
05:34:53 Telescope tracking on
05:34:53 Telescope RA: 12 40 24.5, Dec: -11 40 07
05:34:53 Parking telescope...
05:35:49 Telescope parked.
05:35:51 Shutter is open. Now closing...
05:36:09 Shutter is closed
05:36:09 Closed dome due to clouds.
05:36:11 P:TO1, TheSky6.Document: No connection.

Error code = 200 (0xc8).
05:36:11 Tracking off failed.
05:36:15 P:TO2, TheSky6.Document: No connection.

Error code = 200 (0xc8).
05:36:15 Tracking on failed.
05:36:15 P:TS1TheSky6.Document: No connection.

Error code = 200 (0xc8).
05:36:15 Reading telescope coordinates failed.
05:36:16 Slewing scope...
05:36:16 Slew aborted - target RA and Dec coordinates = 0
05:36:16 Parking telescope...
05:36:16 Telescope parked.
05:36:16
05:36:16 Dark/Bias Frames
05:36:16 Dark set 1 of 1 starting...
05:36:16 Dark/Bias Series 1: 3 dark frame(s), binned 1x1, Luminance filter, 600 seconds.
05:36:16 Exposing...
05:45:34 Run aborted.


2. This other problem I cannot find a log for. But the conditions were the same. I tested and forced a very cloudy situation while darks were being taken during a CCDAP run. The run terminated as expected, but the roof close was not issued as part of the abort.

Do you see this second problem in the code anywhere?
 
Posts: 140 | Location: Fredericksburg, TX | Registered: 04 December 2007Reply With QuoteEdit or Delete MessageReport This Post
  Powered by Eve Community  
 

CCDWare, Ltd.    CCDWare Support Community    Forums  Hop To Forum Categories  CCDWare Products  Hop To Forums  CCDAutoPilot 3    Other cloud sensor logic problems??