×
INDI Library v1.8.3 Released (02 Jan 2020)

Minor monthly bugfix release with a new RainbowAstro mount driver and improved pier side simulation.

ASTAP astrometry integration

2 months 1 week ago 2 months 1 week ago by Carneb. Reason: added hardware installed on
Carneb
Junior Boarder
Junior Boarder
Posts: 20
More
ASTAP astrometry integration #45739
I installed ASTAP on my Raspberry Pi 4 running Stellarmate, The 64bit version wouldn't install but the 32bit version did. It was cloudy last night so could only test from Kstars just using simulators and loading a previous image. It solved the image very quickly so it looks like its working. Hopefully tonight I can test it outside and also see if it works with the polar align assistant.

RPi 4B (4gb) running Stellarmate OS
Skywatcher Evostar 80ED with 0.85 reducer/flattener
Skywatcher AZ-EQ6,
ASI1600MM Pro with ZWO 8x1.25" EFW,
Guide scope 50x190mm, Guide camera ASI290MM
ZWO EAF focuser

Please Log in or Create an account to join the conversation.

2 months 1 week ago
han.k
Gold Boarder
Gold Boarder
Posts: 203
Karma: 6
More
ASTAP astrometry integration #45741

mpfjr wrote: I have a Raspbian Buster 64bit OS install on my Raspberry Pi 4 and everything is 64bit which I am happy with.

However, the .deb packages from the ASTAP website that are 64bit do not install using package manager. They all told me they could not be installed. So I grabbed the 32bit which was armhf and it worked fine for the install. I have not tried it live yet.

If there is a way to install the 64bit Aarm64 bit version I would love to know what it is I have to do.

Essentially I downloaded the Rasp buster full from Raspberry pi's website. Did all the updates to it to bring it to latest version. Then I used the install script from AstroPi3's thread. Then updated everything again. Then tried to install ASTAP.

Unfortunately only the 32bit version would install.



I'm a little surprised that the 32 bit installs and the 64 bit not. These are not interchangeable. Maybe there is confusion about the architecture. 32 bit is for armhf and 64 bit arm64. But also AArch64 is used.

You should be able to extract the files like this

sudo dpkg -i /path/to/deb/file

All the files are normally installed at /opt/astap

No dependency. can be installed at any location

Please tell me if you get it working.

Han

Please Log in or Create an account to join the conversation.

2 months 1 week ago
schwim
Expert Boarder
Expert Boarder
Posts: 110
More
ASTAP astrometry integration #45748
Testing out on OSX, Kstars 3.3.7.

I am able to get ASTAP to run, however I have not been able to get a solution reliably. Sometimes trying a second or third time immediately will result in success. Saving the images from the alignment tab that failed and loading them in to ASTAP by hand proves that it can get a solution with the images as they are. I'm not sure but I think maybe the failure appears to be related to the Field Height Image setting in the alignment tab of ASTAP, which I notice is sometimes erroneously set at a number less than 2x the actual. I haven't figured out how this value is getting in the config. I tried forcing this setting in Ekos (presumably with the -fov parameter) but it is overwritten each time and doesn't seem to take. I also noticed that the command line parameters for the astrometry.net solver pop into the options field if you click on the pencil icon to open settings then select OK. This is reproducible.

Please Log in or Create an account to join the conversation.

2 months 1 week ago
han.k
Gold Boarder
Gold Boarder
Posts: 203
Karma: 6
More
ASTAP astrometry integration #45756
Hello Schwim,

Probably the best thing is to update the focal ratio & sensor size in Ekos. What you could do is open an unsolved image in the ASTAP viewer. Look to the status bar and you will see the dimensions. Then solve the image in ASTAP or Nova.Astrometry.net and see if the dimensions match with the unsolved image. If they change more then 5% then adapt the focal ratio or sensor size in Ekos. This will be only effective for any new image. To test it with the image in the ASTAP viewer you could overwrite it as shown below.

ASTAP can handle differences up to maybe 30% but solving will be more unreliable. So better correct this.

Han



Attachments:

Please Log in or Create an account to join the conversation.

2 months 1 week ago
Carneb
Junior Boarder
Junior Boarder
Posts: 20
More
ASTAP astrometry integration #45779
I had some success using ASTAP in Kstars on my Rpi4 running stellarmate last night. Using my primary scope and camera it solved very quickly and every time. However using my guide scope and camera (190 x 50mm and asi290mm) it would not solve at all. A small rectangular window would pop up in the top left of the screen and count up in degrees (e.g. 5(30) then 6(30)...) but then eventually say solver failed. The image size was also displayed in the window and that was the correct image size.

RPi 4B (4gb) running Stellarmate OS
Skywatcher Evostar 80ED with 0.85 reducer/flattener
Skywatcher AZ-EQ6,
ASI1600MM Pro with ZWO 8x1.25" EFW,
Guide scope 50x190mm, Guide camera ASI290MM
ZWO EAF focuser

Please Log in or Create an account to join the conversation.

2 months 1 week ago
han.k
Gold Boarder
Gold Boarder
Posts: 203
Karma: 6
More
ASTAP astrometry integration #45783
Carneb,

Can you share an image made by the setup you try to solve?

Han

Please Log in or Create an account to join the conversation.

2 months 1 week ago
Carneb
Junior Boarder
Junior Boarder
Posts: 20
More
ASTAP astrometry integration #45789

han.k wrote: Carneb,

Can you share an image made by the setup you try to solve?

Han


I didn't save any of the images, but I will try to get some tonight and share them here.

RPi 4B (4gb) running Stellarmate OS
Skywatcher Evostar 80ED with 0.85 reducer/flattener
Skywatcher AZ-EQ6,
ASI1600MM Pro with ZWO 8x1.25" EFW,
Guide scope 50x190mm, Guide camera ASI290MM
ZWO EAF focuser

Please Log in or Create an account to join the conversation.

2 months 1 week ago
han.k
Gold Boarder
Gold Boarder
Posts: 203
Karma: 6
More
ASTAP astrometry integration #45799
I didn't save any of the images, but I will try to get some tonight and share them here.[/quote]

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.

Han

Please Log in or Create an account to join the conversation.

2 months 1 week ago 2 months 1 week ago by Carneb. Reason: fix format
Carneb
Junior Boarder
Junior Boarder
Posts: 20
More
ASTAP astrometry integration #45803

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.

Han


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

RPi 4B (4gb) running Stellarmate OS
Skywatcher Evostar 80ED with 0.85 reducer/flattener
Skywatcher AZ-EQ6,
ASI1600MM Pro with ZWO 8x1.25" EFW,
Guide scope 50x190mm, Guide camera ASI290MM
ZWO EAF focuser
Attachments:

Please Log in or Create an account to join the conversation.

2 months 1 week ago 2 months 1 week ago by han.k.
han.k
Gold Boarder
Gold Boarder
Posts: 203
Karma: 6
More
ASTAP astrometry integration #45804
They solve without problems if you overwrite the image height in degrees from 0.37 degrees to 0.97 degrees (in the ASTAP program, stack menu, tab alignment).

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.

Han

Please Log in or Create an account to join the conversation.

2 months 1 week ago
universalmaster
Expert Boarder
Expert Boarder
Posts: 153
More
ASTAP astrometry integration #45805
I have had some problems (not with ASTAP) that related to wrong information on the fits header. Maybe a small sanity check and a warning if the values are wrong would help identify these kinds of problems. It was at least not the first thing to my mind when I had trouble, which turned out not to be trouble after all but a bad fits header ;-)

Please Log in or Create an account to join the conversation.

2 months 1 week ago
han.k
Gold Boarder
Gold Boarder
Posts: 203
Karma: 6
More
ASTAP astrometry integration #45813
I have a similar problem with image from a Mac user. The CDELT1,CDELT2 values in the header are also wrong.

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 ?


image link
dl.free.fr/getfile.pl?file=/gAfdJ7sV

Please Log in or Create an account to join the conversation.

Time to create page: 0.940 seconds