Thanks, I suspected as much. The release notes for 3.4 (
) said it was included, so I was a little confused, hoping it extended to the new stellarmate 1.5. I'll be more patient...
For me, with the Stellarmate OS 1.5, IL don't see the Sextractor option for plate solving in the astrometry.net configuration tab, with either the released OS or switching to the bleeding edge, although it reports kstars 3.4.0 Build: 2020-02-08T18:45:26Z
Should it be there?
I have the same issue for providing device names in the snoop fields etc. Would it be possible for someone replace the text field with a selection list of possible drivers so that we don't have the naming uncertainty?
I would hazard a guess that your system is actually an arm64 system rather than amd, so try an intstaller based on ARM. I have it running on an Odroid without problems, using astap_arm64.deb.
Well I actually have both already
I find I prefer the Odroid-N2, seems snappier. Much of that is likely due to the eMMC vs SD.
I'm a complete novice with electronics, so this looks similar, but maybe not sufficiently so.
El Corazon wrote:
jerry wrote: Anyone able to guess if the hat alone would fit onto a Odroid-N2 without modification?
Depends on whether the ODroid has the same GPIO pin configuration. If it does, it might.
If push comes to shove, your ODroid will go up in flames and you will finally be able to buy an RPi4 in good conscience.....
Anyone able to guess if the hat alone would fit onto a Odroid-N2 without modification?
I just did an AstroPi3 update and and ran the system software updater. I get this error on launching kstars (the bleeding edge version from today)
Thread 1 "kstars" received signal SIGSEGV, Segmentation fault. 0x0000005555af998c in CometsComponent::downloadReady (this=0x5557bab2a0) at ./kstars/skycomponents/cometscomponent.cpp:260 260 ./kstars/skycomponents/cometscomponent.cpp: No such file or directory. (gdb) bt #0 0x0000005555af998c in CometsComponent::downloadReady() (this=0x5557bab2a0) at ./kstars/skycomponents/cometscomponent.cpp:260 #1 0x0000007fb5f4f17c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/aarch64-linux-gnu/libQt5Core.so.5 #2 0x0000005555c5b9d0 in FileDownloader::dataFinished(QNetworkReply*) (this=0x55598b92f0, pReply=0x555985bb10) at ./kstars/auxiliary/filedownloader.cpp:121 #3 0x000000555584f858 in FileDownloader::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./obj-aarch64-linux-gnu/kstars/KStarsLib_autogen/AG5HAXE226/moc_filedownloader.cpp:109 #4 0x0000007fb5f4f17c in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/aarch64-linux-gnu/libQt5Core.so.5 #5 0x0000007fb6fe32c4 in QNetworkAccessManager::finished(QNetworkReply*) () at /usr/lib/aarch64-linux-gnu/libQt5Network.so.5 #6 0x0000007fb6fe4304 in () at /usr/lib/aarch64-linux-gnu/libQt5Network.so.5 #7 0x00000055598b9300 in () (gdb)
Then I tried updating my version on the same Odroid-N2 built from source using the instructions at indilib.org/forum/general/210-howto-buil...st-libindi-ekos.html
I'm a complete newbie with git, so I think I pulled the new changes from the specific folders (after a requested stash, which is one of the things I don't really understand). QtCreator was running, and detected source code changes.
I ran both the debug version and non-debug version from QtCreator without a problem.
How do I identify the version of code in the version I downloaded using software updater (now that I've forgotten what it said)? I think it was 2019-11-25.
Thanks, Ihoujin, my Meade focal reducer is missing/hiding at the moment. I may have to replace it.
Ihoujin wrote: Ok. I'll just quickly say that from a little sleuthing I found that the older Meade SCTs require their F/6.3 focal reducer/field flattener to correct for these aberrations. Their newer models feature 'advanced coma-free optics' and do not require one.
As for the diffraction spike, inspect all optical surfaces carefully. Also check your secondary mirror collimation from time to time, especially if you are transporting the telescope.