Just trying to have someone help jog my memory on what could cause this. I have logs from before a ~10 day weather and vacation break from imaging. Paramount ME in a fixed observatory location. PinPoint plate solving. Slews from 10 days ago show near perfect RA and DEC correction after the first correcting slew (-12.0 in RA and 4 in DEC to 0.1 or 0.0 after one correction). Now after this downtime I am seeing a ~ -15 RA error and 4 DEC error not showing any change in RA error after the correcting slews but with a near perfect DEC correction after just the first correcting slew.

What could cause this that I am not thinking of? I do not think I even went into this dome to check before resuming images after 10 days other than to check for spider webs. I have restarted TheSky6 and powered off and on the Paramount ME but the problem persists.

Help appreciated!

Ok,yes, thanks, you were all correct. This indeed appears to be potentially a computer clock issue. Just kidding on all of the non-responses.

After checking another scope and noticing RA was not correcting there either I checked my computers time and noted that my Dimension 4 time sync software had not made an clock updated in the last 12 days or so. Not sure why yet but I think I am heading in the right direction???

Ok one of you smart folks please help a guy out who is not so smart. Clearly there is a conspiracy here and I am sure it is me and me at least. The time issue was clearly and issue but perhaps not this issue?

I got the time syncs working again and to be safe disconnected and connected to TheSky again as well as disconnected and connected to CCDAP4 just in case. My RA is still not being corrected with the precision slew location corrections.

Help a tired guy with a two kids and a wife with the swine flu out please ;-> and end my suffering here...

David,

Post a log if you have one. Make sure your location hasn't changed in TheSky6 and your computer time is correct. If you changed it, power cycle the ME and then connect to it from TheSky. Make sure the RA adjuster is set properly.

Thanks John. Log attached. I did not cycle the power on the mount after re-syncing the computer clock--I only disconnected and reconnected TheSky6 and CCDAP4. I did not think think power cycling the Paramount would make a difference. I will try that tonight. Just to be clear, I am seeing this on both Paramounts controlled by CCDAP4.

Are you refering to the RA clutch/gerar release/knob on the Paramount me as the "RA adjuster" or something else.

Thanks again!

Two_logs.zip (8 KB, 2 downloads)

David,

Please update to 4.15.8 and see if the problem reoccurs. The log has more diagnostic information with the latest version.

This is not a CCDAP problem most likely as I have run numerous test runs with similar hardware without incident. Make sure you can move the telescope in RA using the Telescope motion controls to jog the mount in TheSky6.

Also, see private email.

I hope I wasnt implying that this was a CCDAP issue. I cant make this great SW break anymore ;-> It just runs and runs!

I was hoping however that those most familiar here with automated imaging might quickly be able to jog my memory on what might cause this challenge as I am sure we are more likley to catch and quantify such a problem with the great log feedback provided in CCDAP4... Hard to miss these errors!

David,

Disconnecting and re-connecting does not reset the ME's internal time base. It is still going on the time it received from the initial connection to TheSky, presumably when your computer's time base was inaccurate. Now, if your initial time was off, it will still be off unless the ME is power cycled.

The fact that you are seeing it with two mounts points tobtime synchronization as a possible cause. But again, use the TheSky's Telescope Motion Control window to jog 15 min. E and W to make sure the mount does indeed move.