I am using ASTAP in the following environment:
Raspberry Pi 4 running Astroberry and CCDCiel with INDI drivers and HNSKY for planetarium.
I am just messing around trying to learn the software as a newbie. Accordingly, my INDI devices are the CCD Simulator and the Telescope Simulator.
Here are the versions in case someone might spot some incompatibility somewhere:
In CCDCiel, I connect my devices and HNSKY. I then click (under Planetarium, New Target. It asks me to click my target in HNSKY. I do so, let's say Vega, but any star will fail. Coming back to CCDCiel I note that it shows me the coordinates of Vega. I click OK, and the system begins to slew the telescope to point at Vega. It successfully does so, and then I'll let the logging explain what happens:
I've tried loading the .fits file into ASTAP and trying to resolve it. It fails there as well.
I've installed the h17 star database as indicated on the ASTAP page.
I can't find any way to make ASTAP's internal logging visible to diagnose the problem further. Is there a way?
I'll attach my astap config file. Perhaps someone find a problem there:
I think I've found the source of the problem with the help of Patrick Chevalley. The INDI CCD simulator is based on data that isn't good around bright stars. Aiming away from them, it seems to work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can activate some logging in ASTAP but easiest way to diagnose is to load the image in ASTAP. There you test solving, test star detection and see if hotpixels are detected. So more visual then a text log.
ASTAP 0.9.300 is pretty old from year 2019. Try the newest version. This version will work better.
Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, the new version won't install. I downloaded this link for my 64-bit Raspberry Pi.
I try to install it using the Pi's "package installer". It gives the following message:
"One of the selected packages failed to install correctly. More information is available in the detailed report." I have no idea what is meant by "detailed report". A quick scan of the directory tree produces no likely suspects. I have tried installing with both the "pi" and "astroberry" usernames, with the same results.
Is there another recommended method of installation?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Today I learned that my Raspberry Pi 4, although listed (on the box) as having a "64-bit quad-core Cortex-A72 processor", is shipped with an OS built on the arm7vl architecture which is 32-bit.
Apparently, armhf is compatible with armv7l so the 32-bit Raspberry Pi version was the one to install. The previously installed version was also armhf.
This works.
Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good it is solved. There is also a newer database, the H version instead of G. The difference is that it works faster due to smaller segments. No need to upgrade if your happy with the speed.
Can you send a note to the author of Astroberry that it is time to upgrade. The newer ASTAP version will work better.
Regards, Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What might have saved me a little time on your ASTAP webpage https://www.hnsky.org/astap.htm would have been some sort of notation
indicating that most Raspberry Pi's still use the 32-bit OS, even if they
have 64-bit processors. I was certainly confused. 64-bit Raspberry Pi OS
has only recently emerged from beta testing https://www.raspberrypi.com/news/raspberry-pi-os-64-bit/ and my 64-bit
Raspberry Pi, shipped to me less than a month ago, comes with a 32-bit OS.
And Astroberry hasn't released a 64-bit version yet. Maybe the author is
waiting for that to upgrade astap.
Users unsure of which they have should run the command uname -m.
Good it is solved. There is also a newer database, the H version instead
of G. The difference is that it works faster due to smaller segments. No
need to upgrade if your happy with the speed.
Can you send a note to the author of Astroberry that it is time to
upgrade. The newer ASTAP version will work better.
I am using ASTAP in the following environment:
Raspberry Pi 4 running Astroberry and CCDCiel with INDI drivers and HNSKY for planetarium.
I am just messing around trying to learn the software as a newbie. Accordingly, my INDI devices are the CCD Simulator and the Telescope Simulator.
Here are the versions in case someone might spot some incompatibility somewhere:
In CCDCiel, I connect my devices and HNSKY. I then click (under Planetarium, New Target. It asks me to click my target in HNSKY. I do so, let's say Vega, but any star will fail. Coming back to CCDCiel I note that it shows me the coordinates of Vega. I click OK, and the system begins to slew the telescope to point at Vega. It successfully does so, and then I'll let the logging explain what happens:
I've tried loading the .fits file into ASTAP and trying to resolve it. It fails there as well.
I've installed the h17 star database as indicated on the ASTAP page.
I can't find any way to make ASTAP's internal logging visible to diagnose the problem further. Is there a way?
I'll attach my astap config file. Perhaps someone find a problem there:
I think I've found the source of the problem with the help of Patrick Chevalley. The INDI CCD simulator is based on data that isn't good around bright stars. Aiming away from them, it seems to work.
You can activate some logging in ASTAP but easiest way to diagnose is to load the image in ASTAP. There you test solving, test star detection and see if hotpixels are detected. So more visual then a text log.
ASTAP 0.9.300 is pretty old from year 2019. Try the newest version. This version will work better.
Han
Well, the new version won't install. I downloaded this link for my 64-bit Raspberry Pi.
I try to install it using the Pi's "package installer". It gives the following message:
"One of the selected packages failed to install correctly. More information is available in the detailed report." I have no idea what is meant by "detailed report". A quick scan of the directory tree produces no likely suspects. I have tried installing with both the "pi" and "astroberry" usernames, with the same results.
Is there another recommended method of installation?
Also,
sudo apt install ./astap_arm64.debfails with Error Code 1.
Looking more closely at the output, I see this:
This is interesting because when I query the system architecture I don't get armhf or arm64, I get:
whatever
armv7lis. This may explain why a recent version of astroberry includes an old version of astap.Last edit: Steve Cohen 2022-06-03
More and more interesting!
Today I learned that my Raspberry Pi 4, although listed (on the box) as having a "64-bit quad-core Cortex-A72 processor", is shipped with an OS built on the
arm7vlarchitecture which is 32-bit.Apparently,
armhfis compatible witharmv7lso the 32-bit Raspberry Pi version was the one to install. The previously installed version was alsoarmhf.This works.
Thank you.
Hello Steve,
Good it is solved. There is also a newer database, the H version instead of G. The difference is that it works faster due to smaller segments. No need to upgrade if your happy with the speed.
Can you send a note to the author of Astroberry that it is time to upgrade. The newer ASTAP version will work better.
Regards, Han
I see after looking at the Astroberry Wiki, that the author has this
covered under updates in his FAQ
https://www.astroberry.io/docs/index.php?title=Astroberry_Server#.E2.80.A6_but_ASTAP_isn.E2.80.98t_upgraded_using_the_normal_means.3F,
but it's not easy to find. I guess he hasn't made a new release.
What might have saved me a little time on your ASTAP webpage
https://www.hnsky.org/astap.htm would have been some sort of notation
indicating that most Raspberry Pi's still use the 32-bit OS, even if they
have 64-bit processors. I was certainly confused. 64-bit Raspberry Pi OS
has only recently emerged from beta testing
https://www.raspberrypi.com/news/raspberry-pi-os-64-bit/ and my 64-bit
Raspberry Pi, shipped to me less than a month ago, comes with a 32-bit OS.
And Astroberry hasn't released a 64-bit version yet. Maybe the author is
waiting for that to upgrade astap.
Users unsure of which they have should run the command uname -m.
On Sat, Jun 4, 2022 at 5:13 AM han.k han59@users.sourceforge.net wrote: