ASTAP astrometry integration
han.k wrote: Yes that will be interesting for me. Focal length of 190 mm hasn't been tested. Try to save a series and drop it somewhere in the web so I can have a look.
To avoid saturation, short or very short exposure times will be beneficial for solving.
I've attached 2 images. They are actually fits files but the forum software does not allow fits files for some reason.
File Attachment:File Name: Light_L_1_...1-14.txt
File Size:4,151 KB
File Attachment:File Name: NGC7293_Li..._001.txt
File Size:4,151 KB
Skywatcher Evostar 80ED with 0.85 reducer/flattener
ASI1600MM Pro with ZWO 8x1.25" EFW,
Guide scope 50x190mm, Guide camera ASI290MM
ZWO EAF focuser
The FITS header reports 190 mm focal length. That's is correct.
Pixel size is in the header PIXSIZE1 is 2.9 microns.
The CDELT1, CDELT2 are already specified at 3.258E-4 degrees per pixel . After solving they are 8.8118E-4 degrees per pixel. The CDELT1,2 values overwrite the result from focal length and pixel size.
So the CDELT1, CDELT2 values are wrong in the header. At the moment I don't know where you can correct a value to get CDELT1, CDELT2 corrected.
Focal length 560 mm
Pixel size 3.8 micrometer. Pixel size 1.4 arcsec/pixel equals 0.000391 degrees/pixel
Dimensions 4656 x 3520 => Image size is 1.82 x 1.37 degrees
CDELT1,2 in header 0.000777 degrees/pixel but should be 0.000391 degrees/pixel
Why are CDELT1,2 wrong ?
knro wrote: It's not set in the driver, it's calculated. So they need to use INDI Nightly or update from GIT. Since this is a major bug, I will also publish it to the stable channel.
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!
Thanks for the feedback.
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.
Not familiar with the issue.
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.