New Kstars 3.3.7 ASTAP Plate Solving Speed is FAST!!! #45620
Many people are having issues with ASTAP, me included, when it does work it works really well, but that is not much of the time, on random sky it solves super quick, but if you slew to a specific object such as a galaxy or Nebula, it does not solve.... so still some work to be done...
Stellarmate OS on Raspberry pi4b
Skywatcher EQ8 pro, on steel pier
Takahashi FSQ85 & Meade 8” SCT (de-forked)
Starlight Xpress SXVR H18, SXVR M25c, Lodestar x2 Guide Camera
Pegasus Ultimate Hub V2 for all USB & Power
Pegasus focus motors on both scopes
New Kstars 3.3.7 ASTAP Plate Solving Speed is FAST!!! #47212
I don't want to talk ASTAP down, I used it yesterday night and it's awesome, however I don't think it can really do blind solve, especially when called from kstars/ekos which passes the pole coordinate as a search starting point when images have no pre-set coordinates.
What I'm asking is, are you sure this was really a blind solve? Were those fits captured with ekos? If so, it's possible they had the coordinates written in the FIT header.
New Kstars 3.3.7 ASTAP Plate Solving Speed is FAST!!! #47223
Blind solving is solving without knowing anything about the picture you're working with: no focal lenght, no FOV, no camera details and obviously no known coordinate. It's a slow process, but it's something that astrometry.net can do.
If ASTAP is working sometimes and other it doesn't, check that on your solved pictures the focal lenght is the same as the one you specify in your ekos equipment profile. ASTAP is pretty sensitive to that.
New Kstars 3.3.7 ASTAP Plate Solving Speed is FAST!!! #47232
An other thing you should check is binning. The height of the image send for solving should be 1000 pixels or more. So reduce binning accordingly.
Checklist for reliable solving:
ASTAP behaves differently then Astrometry.net. As long you adapt the settings for that , it will work fine:
- Resolution, the image height should be 1000 pixels or more. So adapt (decrease) binning.
- Stars shall be pretty round and reasonable in focus.
- FOV (field of view) shall be specified within 5 % accuracy for maximum reliability but detection is possible if FOV is 30 or 40% off. So set telescope focal ratio, sensor/pixel size correctly in INDI.
- A minimum of about 20 to 30 stars should be visible (this could be just above noise level. Exposure time of 1 or 2 seconds can work)
- Image shall not be severely saturated or stretched. RAW images works best.
The FOV is detected from the values in the FITS header. To check the FOV, start ASTAP from the applications menu Education and open an unsolved image in the ASTAP viewer. The image dimensions in degrees will be shown in the ASTAP status bar and are updated as soon you solve the image. If the dimensions change a lot (more then 5%) you better update the focal length and or sensor size settings in INDI.
The image dimensions are indicated in the
which is show as soon the solver is 2 degrees from the starting point: