PDA

View Full Version here: : Shakes head - tracking wow - guiding - bizarre!


g__day
01-01-2008, 10:47 PM
Oh the joy I'm having, I drift and drift and drift aligned until alignment seemed very accurate for over an hour - so on a 15 minute unguided shot of Canpous at 2.3 metre focal length I get the following very pleasing results (see below attached picture).

But there's a catch - guiding with PHD has gone wierd. If I turn guiding only in RA - I see slight drift in a 360 second shot, turn guiding on in DEC and its yo-yo's surrealy all over the place within 30 seconds!

So I am happy tracking is so good - but now guiding is showing me deeper errors somewhere - probably chasing seeing and poor backlash in the DEC.

Isn't it amazing how you fix one serious problem and a wierder smaller problem pops its head up and refuses to behave! Anyone else seen this sort of behaviour or have a better guess what it is I am experienceing (guiding still through PHD)?

Matt

Phil
02-01-2008, 08:59 AM
yeah your not wrong Matt i find with my G11 if the balance is of a little bit i get wierd problems in the guiding. And some nights everything goes like clock work and another everything goes to crap.
Phil

g__day
02-01-2008, 10:48 AM
One thing I did notice that surprised me is stars hopped around a lot whilst they were being merely tracked.

So to provide more detail on what occurred.

Calibration – appeared fine

I set on the SkySensor2000-PC the auto-guide rates down from 0.5 to 0.4 sidereal for both RA and DEC and I left the backlash for RA and DEC set to the default 100 settings (there seems to be a lot of slop in the DEC backlash).

I checked with GPINTCheck pulses were working fine in +/- RA and DEC – all okay.

With the pulse guide set to 400 ms during calibrate – it took around 40 pulses to move the targeted star 24.5 pixels in RA and about 46 pulses in DEC to do the same (angle calculated as close to 0.0 and the rate 0.88), but there were about 20 pulses in DEC to clear backlash.

On selecting a star and refreshing every 1.0 versus 1.5 versus 2.0 versus 4.0 seconds I observed quite a bit of movement before initiating guiding, for example the X, Y co-ordinates might cycle like:

RA / DEC
204.8, 391.4
205.0, 392.0
204.2, 391.2
205.0, 392.0
204.2, 392.0
204.0, 391.4
205.1, 392.0

So with the tightest focus I could achieve using a 127mm aperture MAK with a 1500 mm focal length – cut to 750mm by a focal reducer into a Meade DSI, selecting faint stars that didn’t overload the light well of the DSI’s pixels – I was seeing stars jump by about +/- 0.3 pixels per every few seconds.

Now I knew that a 900 second, unguided shot at 2300 mm focal length (side saddle) was producing beautifully tight, circular stars, so I intuited it was seeing that was moving these guide stars so wildly.

So I set minimum pixel before a pulse guide is triggered up from 0.2 to first 0.4, then 0.5, then 0.6 then 0.9 then 1.2 pixels – before finally giving up on guiding!

Guiding – weird results within 30 seconds – huge over corrections

What eventuated was massive over corrections – causing the guide star to be lost within 30 seconds. After maybe 20 seconds a pulse would be sent (that I guess was way too big). The star would move out of the 16 pixel search region, and I guess PHD then sent another over large pulse in the same direction). The result was a huge drift.

I turned DEC guiding off – same thing still happened in RA, it just took slightly longer.

So then I set RA aggressiveness down from 100% to 90% to 50% to 20% - all to no avail. In each instant the corrections were huge and lost the star way too fast!.

I didn’t try expanding the search area from 16 pixels to say 50 pixels – not that that would address way to large pulses being sent.

I’ll ping these details to Craig at Stark labs and see what he advises – stay tuned!

g__day
03-01-2008, 01:15 PM
Well I am still waiting to hear from Craig Stark, but I sense my issues are two fold - alignment - more drift processing to do and seeing fluctations on the guide rig (OTA / CCD combination).

I think I got it even better last night (until 1am when I played with PEMPro for 2.5 hours (its Polar align routine) and ponder did I improve or worsen things... But I will try a marathon driftt alignment soon - I am sure I need more experience in this...

On the guide scope OTA / CCD combination, well I would love some advise as to what I am seeing and how to address it.

I watched a star last night and read of the RA / DEC (x / y) pixel positions in PHD every two seconds. What I saw went like this:

RA (x) / DEC (y)
392.2 153.0
392.0 153.1
392.2 153.0
392.2 152.9
391.9 353.1
391.9 353.6
391.1 352.9
391.9 353.0
391.2 353.0
351.3 352.9
351.9 352.3

etc - 30 minutes later - real drift had occurred and the observations went:

383.2 151.0
382.9 151.1
383.0 351.0
383.0 350.9
383.1 350.9
352.2 351.0
382.1 150.9

50 minutes after this results were

356.8 153.9
356.9 154.0
356.8 154.7
356.0 154.1

So here is my challenge - is that much variance in readings showing a focus issue (collimination) seeing issues - CCD pixel size to OTA mis-match or something else?

How do I account for it - do I simply find software other than PHD that can track multiple stars and average out seeing shifts - should I change to a different guide scope and/or CCD?

What do folk recommend will help me the most please?