I also found that trying to use ASTAP to solve without installing it did nothing, not even the image acquisition. Ideally I'd have expected a message in the status window saying why nothing happened but I'm not that bothered. Obviously not a refelection on Han's program it can hardly be expected to work when it's not been installed.

I'll download and try it when I've sorted out my broadband download limits, I'm currently paying a fortune for 50Gb a month, and a bigger fortune per Gb over that.

Chris

Wondering if the 64bits RPI build for ASTAP can be used with the ODroid N2 (ARM architecture) or if a separate build is required.

Thanks!

Both the ODroid N2 (A73 processor) and Pi4 (A72 processor ) are using ARMv8-A 64-bit instruction set. So I expect the ASTAP 64 bit Pi version will run without problems on the ODroid N2 assuming it running Linux and not Android. Try it and tell me.

If your field of view is not very small, you could use the G16 database instead of the G17 to save some space.

Han

No it was to help you with your problem - thats why the Windows were there -! If ASTAP does not exist you would not be able to start ASTAP from the command line.

You can run ASTAP via Kstars or from the command line - the latter gives more options and is useful when trouble shooting.

Normal Astap platesolving workflow is the same in Ekos as per "local" Astrometry.net same buttons to click - you just "tell " Ekos to use ASTAP - which is via Astrometry options - SO LONG AS ASTAP IS INSTALLED.

Sounds like you,as per your quote above , have not installed ASTAP at all just the G17 Star database - see the other parts of this thread. Probably because you are used to Stellarmate where everything is done for you. Astrometry .net (local) is not (or was not) installed by default in normal Kstars/Ekos but not using Stellarmate I wasn't sure if it was now a standard part of the Stellarmate image.

Perhaps ,if you are unsure, you need to wait for Jasem to create a new Stellarmate image with it installed or the ASTAP specific How to/ FAQ/Support/Install info. - as its new to Ekos.

Downloaded and tried ASTAP on Windows and RP14.

It seems impressively fast, on the PC especially.
It seems better with real images than with the INDI simulator, however increasing the simulator image size helps. I wasn't getting solves with 1280x1024 but setting 2560x2048 gave good solves in 4 to 5 seconds.

BTW the default location in Ekos is incorrect, it's installed to opt/astap. The star database goes into the same directory. You need to set this in Ekos. I found the settings window difficult to find, it's behind the button with the pencil icon on the align tab.

Chris

Thanks Han,

As you mentioned, ASTAP 64 bits works with the ODroid N2. I think that the reason it did not previously install is because i distractedly downloaded the 32 bits version yesterday.

Its slower (3 seconds solution) than my i5 laptop (1 second solution) but from a quick test, its twice as fast as my offline astrometry.net solution. I'll take that!

Gilles

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 had to use "apt install astap..." to install it on my ODroid N2. "gdebi", which I had never used before, would not install it for some reason. I did the same to install the g17 database.

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.

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

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.

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