Jarno Paananen replied to the topic 'What's wrong with my guiding?' in the forum. yesterday

For ballpark numbers my purely anecdotal experience is that on a typical night before the PPEC starts to work I usually get around 1" RMS and it gradually drops to around 0.8". This is with a similar setup as you have (8" TS RC with reducer, though my pixel scale is 1.02"/pix) but HEQ5 instead of EQ6-R. The most noticeable visible improvement in my case was that shape of stars is better thanks to less oscillation in RA direction due to PE. My DE error is small to begin with as I have fixed setup with good PA.

Read More...

Jarno Paananen replied to the topic 'What's wrong with my guiding?' in the forum. yesterday

Yes, it's one of the RA guiding modes in PHD2, Predictive Periodic Error Correction, where PHD2 "learns" the periodic error frequencies during guiding and gradually starts to correct them already in advance. This starts to help after one worm period, before that it behaves as normal hysteresis mode.

Read More...

Jarno Paananen replied to the topic 'What's wrong with my guiding?' in the forum. yesterday

I've mostly used PHD2 with my belt modded and otherwise slightly tuned (and overloaded, which is why I recently upgraded to EQ8) HEQ5 as its PPEC guiding mode seems to work very well with this mount and routinely got under 1" RMS, usually around 0.8" and at best around 0.5", partially depending on the direction of the target (high DE targets guide better) and noticed that slight imbalance (east heavy) on RA does help quite a lot. I have a fixed remote location so I couldn't shift the weight when meridian flipping, but also the site is such that I would image mostly towards west of meridian so I balanced the rig accordingly. I use the target pier side option to image slightly before the meridian which extends the target area.

I did get the internal guider to work quite well too, but running PHD2 isn't really that much work and did give noticeable improvement as my imaging pixel scale is quite small so I switched to that. Also PHD guiding assistant and guide logs helped a lot in getting the settings tuned with less guess work. I use 0.5x guide speed and 2 or 3s exposures with OAG and Lodestar X2. With faster guide speeds the guiding became quite restless and with slower ones it didn't react quite fast enough to periodic errors so 0.5x was a suitable compromise.

Read More...

INDI Dome base class snoops the telescope coordinates and calculates the needed dome azimuth in GetTargetAz function which is then set to the dome via driver's MoveAbs function. The code is in Dome::UpdateAutoSync() in indidome.cpp.

Read More...

Jarno Paananen replied to the topic 'Dome SHUTTER close on park!' in the forum. 7 days ago

I don't know about the NexDome, but for ScopeDome it depends on the model, larger domes only supply power to shutter at home/park position so my driver first rotates the dome to park position and then closes the shutter.

Read More...

Jarno Paananen replied to the topic 'guide module (internal)' in the forum. 1 week ago

Exactly, sometimes things are fortunately quite simple :)

Read More...

Jarno Paananen replied to the topic 'guide module (internal)' in the forum. 1 week ago

As you are using 1x guiding rate, 100ms sounds way too much, if I calculate it correctly that would be 1.5 arc seconds, and the 0.5" you are after would be 33ms. So lower the minimum pulse value so that minimum correction is comfortably below pixel scale. Also possibly lower the guide rate to 0.5x, but that depends on the mount, my HEQ5 guides much more smoothly at 0.5x, but yours might like 1x better.

Read More...