I have posted about this before but it has reared it’s ugly head again.
After a flip and resorting to a blind solve I get this.
Thing is if I tick the ‘continue sequence’ box then the dismiss button the next solve resolves in moments? I guess it was not as bad as it thought! If I was not there to baby sit it the sequence would have failed and shut down.
What can I do to resolve this ?
I’m not sure. This protection is in there to ensure that that a false positive solve does not attempt to make a crazy (equipment damaging correction to your rig). The hints provided indicate this:
[5/2/2017 12:00:40 AM] [DEBUG] [Telescope Thread] PlateSove2 Param: RA (HRS) - 12.9466146566321
[5/2/2017 12:00:40 AM] [DEBUG] [Telescope Thread] PlateSove2 Param: RA (RAD) - 3.38941579117778
[5/2/2017 12:00:40 AM] [DEBUG] [Telescope Thread] PlateSove2 Param: DEC (DEG) - 21.68484375
[5/2/2017 12:00:40 AM] [DEBUG] [Telescope Thread] PlateSove2 Param: DEC (RAD) - 0.378471921218014
[5/2/2017 12:00:40 AM] [DEBUG] [Telescope Thread] PlateSove2 Param: SCALE - 2.41322
Then the actual solve looks like this:
[5/2/2017 12:02:28 AM] [DEBUG] [Telescope Thread] Astrometry.NET - Solve Completed
[5/2/2017 12:02:28 AM] [DEBUG] [Telescope Thread] Astrometry.NET - Solve Successful
[5/2/2017 12:02:28 AM] [DEBUG] [Telescope Thread] Astrometry.NET - RA: 12.9458498262968
[5/2/2017 12:02:28 AM] [DEBUG] [Telescope Thread] Astrometry.NET - DEC: 5.98926676896209
[5/2/2017 12:02:28 AM] [DEBUG] [Telescope Thread] Astrometry.NET - Scale: 2.41110612191481
[5/2/2017 12:02:28 AM] [DEBUG] [Telescope Thread] Checking to see if solve might be bad…
[5/2/2017 12:02:28 AM] [DEBUG] [Telescope Thread] Solve might be bad (auto center)! New solve coordinates deviate too far from current position.
The solved values and the hint values are simply too far off for SGPro to consider it a good solve (the delta in scale is the first red flag).
Thank you Ken. The sequence failed again last night in almost the same manner.
You will have to help me out as I have no idea what that means?
So this basically boils down to a mechanical issue in that the mount is not moving to the proper coordinates?
Why does it resolve so quickly after I do the continue thing?
Delta is the difference between where your scope thinks it is and where the solved image actually is. 21.685… DEC vs 5.983… DEC and so on…
Look like a big difference. Is your location all setup?
If the telescope was pointing correctly before the flip but not after then it looks like an issue with how the mount handles pointing on either side of the meridian. This could be what’s called cone error, and is the amount by which the optical axis of the telescope is not orthogonal to the Dec axis.
The way that most of the difference is in declination supports this, the difference of 15.7 degrees could imply a cone error of half that - 7.8 degrees.
You should be able to test this manually. Slew to an object really close to the meridian, center it in the EP and note the Ra and Dec values the mount reports.
Then do a pier flip manually, setting the mount to the same coordinates but on the other side of the pier. It should be pointed differently and if you centre the same object you should see that the Dec value in particular is different.
A good suggestion. SGPro allows for a certain amount of error here and maybe we should loosen the error tolerance (in location, but not scale) when solving switches over to the blind solver.
Sorry I did not reply to this sooner.
It seems I have this issue sorted out. Evidently the gear mesh on the RA axis was a little too tight and the stepper was stalling in spots. I backed off the gear mesh just a bit and everything is working fine now.
It almost never has to resort to a blind solve after the first solve and synch.
Go figure.
