Come and join our community. Expand your network and get to know new people!
An easy solution for you then would be to try running the home-brew version of astrometry until I get this resolved.:
1. At the command line run this command:
brew install astrometry-net
2. Inside the KStars astrometry options, select to use the homebrew solve field and wcsinfo. See the screenshot.
Addendum to my earlier reply:
I tried "verbose" mode on solve-field and get:
Reading input file 1 of 1: "/Users/rnlucas/Documents/ekos/NGC6883/Light/NGC6883_Light_054.fits"...
Base: "/Users/rnlucas/Documents/ekos/NGC6883/Light/NGC6883_Light_054", basefile "NGC6883_Light_054.fits", basedir "/Users/rnlucas/Documents/ekos/NGC6883/Light", suffix "fits"
Checking if file "/Users/rnlucas/Documents/ekos/NGC6883/Light/NGC6883_Light_054.fits" ext 0 is xylist or image: Illegal instruction: 4
Thank you for the test version of ksatrs. Unfortunately, the update did not solve the problem for me.
I ran into a problem running the python setup: it verified that home-brew was installed and attempted to instal python. After a short time, it put up a dialog saying: “Python installation failure”.
I opened a terminal window and attempted the installation per your instructions elsewhere in this thread. Home-brew claimed python was installed and up to date. I checked:
Robert-Lucass-Mac-Mini:~ rnlucas$ which python
Robert-Lucass-Mac-Mini:~ rnlucas$ which python3
Robert-Lucass-Mac-Mini:~ rnlucas$ python3 -V
After this, I retried the setup, and this time it appeared to complete normally.
Robert-Lucass-Mac-Mini:~ rnlucas$ pip install astropy
Requirement already satisfied: astropy in /usr/local/lib/python3.7/site-packages (3.2.1)
Requirement already satisfied: numpy>=1.13 in /usr/local/lib/python3.7/site-packages (from astropy) (1.16.4)
However, it still seems to fail in the same way (from Ekos):
2019-06-15T19:10:09 Solver failed. Try again.
2019-06-15T19:10:09 Error starting solver: Process crashed
2019-06-15T19:10:09 Reading input file 1 of 1: "/Users/rnlucas/Documents/ekos/NGC6883/Light/NGC6883_Light_054.fits"...
2019-06-15T19:10:09 /Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -3 302.861 -4 35.8077 -5 15 --config /Applications/kstars.app/Contents/MacOS/astrometry/bin/astrometry.cfg -W /private/var/folders/k7/18sgd_pd0fd_khn8l64crc0r0000gn/T/solution.wcs /Users/rnlucas/Documents/ekos/NGC6883/Light/NGC6883_Light_054.fits
2019-06-15T19:10:09 Starting solver...
2019-06-15T19:10:09 export PYTHONPATH=/Applications/kstars.app/Contents/MacOS/python/bin/site-packages
2019-06-15T19:10:09 export PATH=/Applications/kstars.app/Contents/MacOS/netpbm/bin:/usr/local/opt/python/libexec/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
2019-06-15T19:10:09 Solver iteration #1
2019-06-15T19:10:09 Using solver options: -O --no-plots --no-verify --resort --downsample 2 -3 302.861 -4 35.8077 -5 15
2019-06-15T19:10:01 Capture aborted.
2019-06-15T19:09:56 Capturing image...
2019-06-15T19:09:48 Detected Astrometry.net version 0.76
From the command line:
Robert-Lucass-Mac-Mini:~ rnlucas$ /Applications/kstars.app/Contents/MacOS/astrometry/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -3 302.861 -4 35.8077 -5 15 --config /Applications/kstars.app/Contents/MacOS/astrometry/bin/astrometry.cfg -W /private/var/folders/k7/18sgd_pd0fd_khn8l64crc0r0000gn/T/solution.wcs /Users/rnlucas/Documents/ekos/NGC6883/Light/NGC6883_Light_054.fits
Reading input file 1 of 1: "/Users/rnlucas/Documents/ekos/NGC6883/Light/NGC6883_Light_054.fits"...
Illegal instruction: 4
I'm on macOS Mojave 10.14.5.
Thank you for your suggestion. When I get back to my house, I will investigate oaCapture. Everything worked fine before the update. I am not adverse to updates. The QHYCCD company did not indicate or I failed to notice the drop of support of QYH5 in EKOS.
I had a nice 3.0 USB 4 port hub. I added the QHYCCD PoleMaster. It was not working. I thought not enough power. I got a powered hub. I had 4 USB devices. Now, I had 5. More power was needed.
Come to find out, libraries needed to be copied to other areas not mentioned in the excellent RPI installation documentation. I thought the PATH changes took care of needing special replication. The PoleMaster works . But, guide camera, QHY5-II-C, was not working. QHYCCD does not provide any RPI tools.
This thread claims that the developers SDK from QHYCCD did not contain the QHY5 model. KSTARS device manager and QHYCCD says, No QHYCCD product found. So, the QHY5 family is discontinued within KSTARS and EKOS. Developers can only code to what is provided from hardware vendors.
What hardware are you using? Raspberry Pi? Some other PC-like device? In any case, Ubuntu Mate 18.04 has been rock stable for me over the past year.
I do not think that EKOS is eliminating devices. There is an indi_qhy_ccd driver, which will rely on the QHYCCD proprietary library for communicating to an initialized QHYCCD USB camera.
Multiple things could have gone wrong:
* The device did not get properly initialized. Maybe it was not recognized, or udev failed to load the appropriate firmware.
* The QHYCCD library cannot communicate with the device anymore, because it was obsoleted (might have happened to the original QHY5).
* Something changed in the QHYCCD library and indi-qhy-ccd cannot handle it.
As you are running Astroberry, try oaCapture (without starting INDI at all) and see if it recognizes your QHY-5L-II. I assume it also uses the QHYCCD library, but maybe it uses a different version. At least we would know if the issue is in INDI or already in initializing the device.
I'm having a large amount of stability issues, and have decided to rebuild my system from scratch. ( app crashing and usb device issues)
What OS / Version should I pick to get the most stable solution for KStars / Ekos / Indi.
For QHY drivers in INDI Lib v1.7.8, the Live View / Streaming tab is still not available for the CCD camera QHY8L .
Indi control panel of Kstars already without streaming tab, the corresponding icon in the Ekos camera control disabled.
Am I really the only user detecting this problem?
A note: The update procedure returns the error message "Setting up libqhy (5.0.7 + r4893 ~ 201905281316 ~ ubuntu16.04.1) ...
rm: can not remove '/lib/udev/rules.d/85-qhy.rules': No such file or directory ".
Regarding to the important Funktion Auto Focus I would be very happy to get any support for solving this problem.
My system environment:
Astroberry Server (Raspberry PI 3 , Ubuntu Mate 16.04 Desktop
libindi1/xenial,now 1.7.8~201905111153~ubuntu16.04.1 armhf [installed,automatic]
indi-qhy/xenial,now 2.4~201905111650~ubuntu16.04.1 armhf [installed,automatic]
LX200 Autostar, QHY8L-C, ASI120MC, USB_focusV3
Client: Kstars for Windows V 3.2.3
I tested the new Mac version and all is good.
The Setup panel is open on the first run if Python and indiweb is not installed.
The GSC install work fine, without problem with the default directory.
Then I compiled and tested on Linux (Ubuntu 18.04 x86_64). No problem after installing the cmake requirement.
The application work fine.
Now it's working properly.
Thanks for the effort, Jasem.
DerPit wrote: So far I had manually started indiserver on my small PC at the mount, and then used EKOS on my laptop to connect to it:
<code>indiserver indi_asi_ccd indi_asi_wheel indi_dmfc_focus indi_ieq_telescope</code>
Today I wanted to check if the computer is powerfull enough to also run kstars/ekos on it, and wanted to make use of ekos starting indiserver by itself. For that I had to select a mount (CEM60). This created a new configuration in ~/.indi, named iOptron CEM60_config.xml. The other one, created when running the manual indiserver command, was called iEQ_config.xml. And of course, after that change, PHD2 didn't find the mount anymore, as it was looking for the iEQ device
So I checked the running indi programs, but that didn't give a hint how the name had been passed to the indi_ieq_telescope program. I'd really like to use the same name for both methods so I can easily switch without having to change the configuration of PHD2. I tried 'indiserver --help' but that doesn't mention driver options...
How would I have to start indiserver to use the new device configuration file?
If you start INDI Server in FIFO mode, you can start drivers with specific names (see indilib.org/develop/developer-manual/92-indi-server.html ). Ekos always uses FIFO mode so that it can dynamically start/stop drivers and renames the default name (e.g. iEQ) to a more friendly label (e.g. "iOptron CEM60").
If you don't want to use Ekos and have INDI Web Manager installed and running, you can make an web API call and it would a profile with all the "correct" labels always.
Spartacus wrote: The GLIBC version will be higher than 2.17
I think that 2.27 is the version for Ubuntu 18.04
So update using
sudo apt-get update
sudo apt-get install libc-bin=2.27-3ubuntu1
This should allow TV to work. But follow the instructions on the previous post website link.
an apt-get install indicates that libc-bin is already the newest version (2.2.7-3ubuntu)
when running the TV pgk TeamViewer_14.3.4730_amd64.deb I still get the same error: Dependency is not 'satisflable':libc6(>=2.17)
Is there a way to create a symlink somewhere to force the install to recognize the newer libc6?
When trying to install QT, I get
Desktop Music Public qt-opensource-linux-x64-5.6.3.run
Documents PHD2 Templates qt-opensource-linux-x64-5.9.8.run
Downloads Pictures Videos rtl8822bu
bash: ./qt-opensource-linux-x64-5.9.8.run: cannot execute binary file: Exec format error
P.S. I was able to get a tightvnc server running reasonably well (no grey screen), but my sysytemd service for it will start it, but not after a reboot.
/etc/systemd/system/vncserver@.service [Unit] Description=Start TightVNC server at startup #After=syslog.target network.target After=syslog.target network.target [Service] Type=forking User=odroid Group=odroid WorkingDirectory=/home/odroid #RestartSec=35 #Restart=on-failure PIDFile=/home/odroid/.vnc/%H:%i.pid ExecStartPre=-/usr/bin/vncserver -kill :%i > /dev/null 2>&1 ExecStart=/usr/bin/vncserver -depth 24 -geometry 1280x800 :%i ExecStop=/usr/bin/vncserver -kill :%i
Any help you might be able to provide would be greatly appreciated.
Or take a picture and let the plate solver do it’s normal work. It will fill out the FOV for you. Ekos will remember it and next time Polar Alignment can start straight away.
Glad to see you were able to fix it!
go to the alignment tab. Then hover with your mouse over area next to FOV. Now a message with the calculated FOV will pop up. Then type the displayed FOV manually in. Now it should work.