Now, that's what I call "reactivity"!
I was having the same issues, and only while using the guidescope, like the others here.
This is the reason why Indi is far better than any other library I know of: amazing community, and amazing people taking care of it in real-time!
Just want to say, I had nothing but headaches working with the astrometry.net local server. This ASTAP solver is GREAT! Can't believe the improvement. Solves all fields, and usually within 1 second. Amazing.
A technical question. I'm still a little worried about the problem with the CDELT1, CDELT2 keywords in the fits header. I'm still try to understand the scale of the problem. 1) Did you update INDI with the fix of Jasem? 2) Do you have the possibility to check if the FITS files contain the header keywords CDELT1, CDELT2 prior to solving and if they are correct? The problem is that these CDELT1, CDELT2 values overrule the focal length and pixel size setting.
I did update everything before attempting to use ASTAP as the solver. So far have had no issues at all. I've used the images generated from INDI & ASTAP solved in Aladin and Astrometrica. Seems to work fine.
I have one issue with ASTAP in EKOS as I've had mixed results getting to it to solve. My scope is currently in its 1400mm FL setup. After some trial and error I find I have to set the binning to 1x1 (from 4x4 that I've been using with Astrometry) and I have to change the default "r30" for ASTAP to "r50". This then solves quite well. The problem now though is that for all subsequent solves, it reverts that setting back to "r30" again. How do I make permanent changes to this in EKOS please. I'm running v3.3.7 on a Mac if this helps.
ASTAP behaves differently. 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 focal ratio, sensor/pixel size correct.
- Image shall not be severely saturated or stretched. RAW images works best.
I have all those requirements met Han. Astrometry is having zero problems, but is a tad slower.
I can get ASTAP to solve consistently but only when default of “r30” as the CLI option is changed to “r50”. I need it to be “r50” (and have that change made permanent for this scope configuration) as right now every time it goes back for another solve it reverts it back to “r30” as the CLI option again.plate solving is failing ~50% of the time with that setting.