Don Pearce avatar
So everything was going well with both cameras the QHY 294C & the QHY 178C using hyperstar on my EDGE HD9.25 over the past few months. I have reconfigured my scope with a .7 reducer and my QHY 178C. Now I cant plate solve. It wont even plate solve with astromony.net server installed as fall back.

I am using SGP with platesolve 2.8. It slews to target then seems to do a slight move every time just before it starts to take an image to solve? It never did this before. Whats more frustrating is that I can see the image in the field of view of the plate solve image?

1645mm focal length. Chip for QHY 178c 3056 x 2048. 2.4u

It will solve the image usually within 65 to 400 regions then it adjust mount and tries again only to keep repeating the error which is usually about 3000 pixels out and in the same region. It should be getting closer to my target of 200 pixel error each time it solves yeah?

Not sure what I have done, I have the appropriate indexes installed in astronomy.net as well.

Has anyone ever had a similar problem?

Cheers

Don
Nadir Astro avatar
Did you change your Pixel Scale in imaging and platesolve programs after you added 0.7 reducer ?
AwesomeAstro avatar
Yeah you have to change the focal length under the camera settings to make sure it calculates your approximate pixel scale correctly. If you need to push the program along to "figure it out", right click your image in SGP and choose "plate solve". Put in the pixel scale manually and the approximate coordinates to get it started. Then you can solve and sync.

The only other reason a focal reducer would hurt your plate solving is if it introduces extreme distortion (unlikely) or that the stars are now too small. There is a minimum star size setting as well, although that's not as likely to be the problem as the image scale is. The program doesn't know to update this.
Helpful Concise
Don Pearce avatar
I have changed the pixel scale and focal length in the SGP profile manager. I'm not sure how to change it in PlateSolve 2.29,
I thought it did it automatically as it is a part of SGP? Can you see anything strange here.

Don Pearce avatar
Going through all my settings, I nticed that my coordinates  where a couple off degrees out. I have changed this in all my equipment  profiles. I have recalibrated and synchronized. I have checked  all my pixel scales are correct for resolution, pixel size and focal length. Now when i scew to a target  it is very accurate and it plate solves almost instantly. I can see the target in the field view.

I have set my accuracy  for 200 pixels. After plate solving it the first time it solves again but each time it moves the target away from the target slightly.  I have it configured to try 6 times to solve but instead of closing in on my requested error of 200 pixels it solves a little  further away  each time.

Its so frustrating  and I bave wasted this months entire new moon period. I know it must be a simple setting or equipment  mis-configuration.

Any ideas would be welcome
AwesomeAstro avatar
Glad you've gotten it solving things correctly.

As for the slew error, this heavily depends on your equipment. Some mounts don't quite have the accuracy to center to that precision and, although they think they're doing well enough, they end up off by more than your tolerance. They can't gradually inch closer, either, because the mount is probably programmed to enter from a specific side on each axis to prevent gear slop/backlash, which means it will, each time, leave the target and reenter upon centering each time.

The solution here depends on how far off it is. You're saying 200px is being exceeded. By how much and at what pixel scale? If it's 250 each time, or 280 or 300, you should simply increase the tolerance parameter so it stops bothering you. Especially if you're dithering, this shouldn't matter. In my setup it's even less critical; I use off-axis guiding which means I look at phd2 while it's trying to center, and when my planned guide star appears, I stop the centering anyways and move it where I want within the pick-off prism from the phd2 side.

If it's substantially off, say by more than 25% of your field of view, that's another story. For reference, my tolerance has been set to 130px I believe. At 0.35"/px, this is 46" max of error (binned 1x1). If your error in arcseconds isn't much more than this, I wouldn't pull your hair out; just set the tolerance higher.
Helpful
Don Pearce avatar
Thanks for responding. The plate solve is usually out by about 1200 pix. About 1/3 of my field of view. Do you know if. There is a way of turning plate solve off in SGP. I could then at least slew to target and centre it manually? Would this work. Deep sky stacker should be able to centre the sessions up?
AwesomeAstro avatar
Plate solving should only occur when you demand it; either because you chose "solve" for the image you took, or because you've set up a "centering" event in the sequence. You can definitely disable plate solving/centering in the settings panel, however I'm surprised that it's off this much. You're using the EQ6R pro? Although I don't have this mount I suspect it should be able to center more accurately than this. Even my AVX would put it within 150 px (after a try or two) at very high focal length (2032mm).

This may require some experimentation to get to the root of the issue, such as trying centering in different parts of the sky (to see if you're getting some weird flexure?) or trying to let it continue trying, and seeing if a pattern emerges. There may be "approach" settings in the mount that need to be improved, or else some other setting being off.

You can definitely center by hand and continue from there. The registration of the light frames will always correct for movement between sub frames. Dithering should be occurring anyways, so every image of mine is off from the previous one slightly.
Helpful Insightful Respectful Engaging Supportive
Don Pearce avatar
Maybe it is flexure, I have had better results in other areas of the sky. I might go over my image train and make sure all is firm. Hopefully will get a break in the clouds tonight, I'll let you know.

Thanks heaps for your input.

Don
AwesomeAstro avatar
Mirror shifting also comes to mind, I have the EdgeHD (and have used the 8se) and the mirror definitely moves some, although never enough to throw off centering… But this is interesting since you said it actually gets worse as it continues to center. I would let it go for 5-10 attempts and see if there's something you can glean from the results. It's not unusual to have it be slightly worse from one to the next, since it's essentially just shooting over to the target each time, but if it continues getting worse 10 times in a row without any getting better, this speaks to something changing in your system.
Helpful
Nadir Astro avatar
If you're using EQ6 and EQMOD, try changing Alignment/Sync in EQMOD to Dialog Based instead of Append on Sync.
Well Written Concise
Don Pearce avatar
I have finally a small break in the weather, I have successfully disabled plate solving and I am up and running.   Thanks for the tips. I am still yet to work out my plate solving issues as I am just keen to get some data at last.

I have yet to try changing to Dialog Based instead of Append on Sync. I will give it ago later in the lunar cycle. I will can then focus my time on fault finding again.

Thanks for the help, I'll let you know how I go.