Using astrometry on Windows 10, I've installed ANSVR and the relevant index files "4202 to 4208" on a couple of occasions it has been successful on its first iteration, and then proceeded to fail on any further attempts, most of the time it just fails. As regards the inner workings of a computer, I'm a dummy, wondered whether anyone has any clues, I've attached a photo of the last ANSVR log.
Astrometry.net really needs a bit of tweaking before it will run perfectly. There are a number of settings and of course the index files that will all affect how it runs. It is about the optimization of all these variables. It is hard to say exactly which variables should be tweaked to make it run better, more of a trial and error.
Looks like you are already binning 4x4, are you down sampling too? That does usually help
Double check your focal length and aperture and calculated field size.. if it is wrong you can change or disable it.
Double check your position in ra and dec, you can disable this too if needed.
You can try longer or shorter exposure times to see if that helps.
For the index files, I would recommend uploading a few images to nova. Astrometry.net and see what it uses to solve them. Make sure you have those installed. 4202 seems too low. With your field size in your screenshot I could see 4204 or 4203, but probably not 4202. Also you might try installing the high end like 4209, but your field size is pretty small. But yeah test with images to see what it uses to solve them.
Finally if a certain spot in the sky doesn’t solve, move the scope to a slightly different spot and it might solve. You do have a very small field size.
Thanks Rob, appreciate that, I'll try out your advice when the weather clears. As regards the FOV uploaded a photo to nova astrometry that's what it gave me, cheers Davey
I had offline aligning working fine before last week's updates. Now its not working. Basically it bombs immediately after getting first image. Prob some simple config detail is incorrect. ?? Index files are there from my prior Kstars, FOV is correct, and otherwise I'm using the default settings. Online aligning works fine. Other detail is that I did factory reset on Stellarmate Saturday night (a few nights ago), and reran SM updater. I have Kstars 3.1.1 now (but 3.1.0 had same issue). When loading new version of Kstars, are there some pointers that need to be changed?
The message window messages are pasted below.
(Sorry, I tried to get log file too, with astrometry debug enabled, but time stamps on log file don't make sense to me, doesn't seem to be opening a fresh log file - I'll omit it now. It you really need it, let me know. I'll try again.)
Apart from using the scheduler, is there a way to have Ekos do an alignment, say every 60minutes, during a capture sequence?
I see the option to refocus every xx minutes. How about realign/plate solve every xx minutes??
Make sure that the KStars application path does not contain a space. Now it is "/Applications/kstars 3.app" so rename it to "/Applications/kstars3.app" (note the removed space between kstars and the number 3) or "/Applications/kstars_3.app" (note the underscore).