afeebjce

Finally! Success! After three years + I have finally gotten an autoguiding system to work.
Wow. This is going to be a game changer.

In the past, because of the very high magnification used in planetary imaging, and even just seeing alone, much less bad tracking or pointing, meant that one had to manually guide the scope to keep Jupiter in the Region of Interest field of view. Typically Jupiter is around 45 arc seconds large and I generally shoot an ROI around 60-70 arcseconds.

I would have to touch the manual tracking every 30-60 seconds or so or risk it touching an edge, ruining the entire run.
And don’t even wanna to talk about bathroom runs!

So the autoimaging run would be set up for say 20-30 runs in a row and in the early days I would sit outside with the hand paddle that never wants to work well, less so in the cold.

For maybe a year I have been inside, remote controlling and it is much nicer, warmer, but introduced a few of its own quirks.

Last night I got the complete system up and running correctly.
ascom platform drivers for the lx200gps on the windows 10 laptop
firecapture telescope control initializing correctly.
tracking configuration set correctly (the last piece fell into place when I realized that I flip the x and y axes for imaging (north at top) but I had to tell the guiding control that as well. The last 5 attempts had it correctly in the negative direction, loosing Jupiter completely in 5-10 seconds. I thought it was just broken.

So the biggest thing coming will be much longer sequences of runs, instead of only maybe 20 runs covering 40 minutes, with autoguiding I should be able to ramp that up into the 100-200 region, covering 400 minutes.. maybe 6 hours!?

drive space now becomes the limiting factor… have to start working on managing that better… or buy a bigger SSD (240GB now).

In any event, long post.. here is some eye candy… seeing and transparency were poor, pretty much full moon above the horizon, focus was difficult, not much to see.
jupiter_20160424