Get Connected!
Come and join our community. Expand your network and get to know new people!
I downloaded the OSX build dates 27 May and notes two issues before I quit it.
1. Immediately after selecting Calculate and Slew, EKOS set my rotator to 360. This was unexpected, as normally it only rotates with LOAD and slew. I had never seen this action before.
2. Once it did the above, It no longer saw any of my plate solving index files. I assume it just lost the link to their location, but I don’t know why. No other previous version of KStars OSX did that.
As the night was clear and I needed to finish a target, I quit this version and launched one from May 11, which worked perfectly.
I’ll go back in and see if I can figure out what happened to the solver index files later today.
Read More...
Hi Stefan, no ideas then. Is it possible for you to give me access to your system through anydesk so that I could debug it? I don't own a touptek and it would be mostly impossible to check what's wrong
Read More...
Hey folks,
I am new to this community but have been using INDI for a while now with astroberry. This weekend I decided to rebuild everything because I found out nou's script(gitea.nouspiro.space/nou/astro-soft-build) that made everything sound pretty easy and I liked the idea of being independent from astroberry.
Everything looked fantastic during building and installing and Kstars started up exactly like it should but when I added my gear to Ekos(or even just used simulators) and started everything up, all the indi drivers crashed and at some point after retrying over and over again Kstars crashed too.
I am using a Raspberry Pi4 8GB, instead of an SD-Card I use a 128GB SSD connected via USB. That setup works perfectly fine, the Pi is set to accept an USB drives as the OS volume.
Here is what I do to reproduce the issue:
1. take the latest Raspberry Pi OS with Desktop 64bit Image and write it to the USB drive
2. start up the Pi and perform the initial setup(user, password, locale, network, hostname, ssh, vnc, updates, no additional software
3. git clone gitea.nouspiro.space/nou/astro-soft-build.git and cd into the directory
4. run ./install-dependencies.sh and afterwards /build-soft-stable.sh
As already said, the script did exactly what I expected it to do, I didn't notice any errors but when I start KStars and try to get started with Ekos all the drivers crash. I tried to get some details from the logs but found them not very helpful.
This is from the logs when I try to get only my guiding camera to work:
[2023-05-29T12:18:34.771 CEST DEBG ][ org.kde.kstars.ekos] - Resetting Ekos Manager...
[2023-05-29T12:18:34.842 CEST INFO ][ org.kde.kstars.ekos] - "Starting INDI services..."
[2023-05-29T12:18:34.845 CEST DEBG ][ org.kde.kstars.indi] - INDI: Starting local drivers...
[2023-05-29T12:18:34.846 CEST DEBG ][ org.kde.kstars.indi] - Starting INDI Server: ("-v", "-p", "7624", "-m", "1024", "-r", "0", "-f", "/tmp/indififoc3edcdc5") -f "/tmp/indififoc3edcdc5"
[2023-05-29T12:18:34.865 CEST DEBG ][ org.kde.kstars.indi] - INDI: INDI Server started locally on port 7624
[2023-05-29T12:18:34.866 CEST DEBG ][ org.kde.kstars.indi] - Starting INDI Driver "indi_asi_single_ccd"
[2023-05-29T12:18:34.866 CEST DEBG ][ org.kde.kstars.indi] - INDI Server Started? true
[2023-05-29T12:18:34.868 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Scheduler Ekos status is 1
[2023-05-29T12:18:34.869 CEST DEBG ][ org.kde.kstars.indi] - Adding managed driver "ZWO Camera"
[2023-05-29T12:18:34.870 CEST DEBG ][ org.kde.kstars.indi] - INDIListener: Adding a new client manager to INDI listener..
[2023-05-29T12:18:34.871 CEST DEBG ][ org.kde.kstars.indi] - INDI: Connecting to local INDI server on port 7624 ...
[2023-05-29T12:18:34.872 CEST DEBG ][ org.kde.kstars.indi] - INDI server connected.
[2023-05-29T12:18:34.873 CEST INFO ][ org.kde.kstars.ekos] - "INDI services started on port 7,624."
[2023-05-29T12:18:34.899 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: startup: /usr/bin/indiserver -v -p 7624 -m 1024 -r 0 -f /tmp/indififoc3edcdc5"
[2023-05-29T12:18:34.899 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: listening to port 7624 on fd 5"
[2023-05-29T12:18:34.899 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: Local server: listening on local domain at: @/tmp/indiserver"
[2023-05-29T12:18:34.900 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: FIFO: start indi_asi_single_ccd -n \"ZWO Camera 1\""
[2023-05-29T12:18:34.900 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: With name: ZWO Camera 1"
[2023-05-29T12:18:34.900 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: FIFO: Starting driver indi_asi_single_ccd"
[2023-05-29T12:18:34.900 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: Driver indi_asi_single_ccd: pid=1891 rfd=9 wfd=9 efd=10"
[2023-05-29T12:18:34.900 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: Client 8: new arrival from 127.0.0.1:33790 - welcome!"
[2023-05-29T12:18:34.900 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: Driver indi_asi_single_ccd: indi_asi_single_ccd: error while loading shared libraries: libXISF.so.0: cannot open shared object file: No such file or directory"
[2023-05-29T12:18:34.901 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: Driver indi_asi_single_ccd: read: Connection reset by peer"
[2023-05-29T12:18:34.901 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:34: Driver indi_asi_single_ccd: Terminated after #0 restarts."
[2023-05-29T12:18:34.901 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2023-05-29T12:18:34.903 CEST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_asi_single_ccd" crashed!
[2023-05-29T12:18:40.575 CEST DEBG ][ org.kde.kstars.indi] - Removing managed driver "ZWO Camera"
[2023-05-29T12:18:40.576 CEST DEBG ][ org.kde.kstars.indi] - Stopping INDI Driver "indi_asi_single_ccd"
[2023-05-29T12:18:40.588 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:40: FIFO: stop indi_asi_single_ccd -n \"ZWO Camera 1\""
[2023-05-29T12:18:40.589 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2023-05-29T10:18:40: With name: ZWO Camera 1"
[2023-05-29T12:18:40.589 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""Is something wrong with libXISF? That part of the script worked perfectly fine as far as I can tell.
I already did a full reinstall(OS and script)twice but got the same results.
It's absolutely possible that I am doing something wrong. With astroberry I used things a little bit different, I always operated the Indiserver with the sidepanel and then connected Ekos to that server but it should work with just Kstars/Ekos, right?
Also could it be the 64bit Version of Raspberry Pi OS?
Any help would be appreciated!
Kind regards
Read More...
Please help me identify what the problem may be.
I started to get this failure and am not sure whether introducing the Rolloff Roof hardware into the mix caused it although the driver has been installed for a while now. I say not sure because it came ok for a little while and I tested for a few sequences and it seemed to work ok.
When I try individual or looping frames I get the failure almost all the time. I can get one or two ok. I did not try another sequence test.
Please let me know if there is any other information required that may help.
Thanks in advance.
Krish
Read More...
Hi Mattia,
made a new installation of AstroArch without installing AstroDMx manually. Updated to the current version.
Unfortunatly Indi still states: "Unable to establish: +Toupcam. Please ensure the device is connected and powered on."
No further info in the logs.
Any Idea?
Regards
Stefan
Read More...
tstudioastronomy.blog.fc2.com/blog-entry-634.html
I wrote the information that I could not write here on my blog. (If you are interested, please read it with the translation function.)
Read More...
dmesg is a command you enter in a terminal. It’s mainly for tailing the kernels message output. If you run this and then plug in the focuser usb cable it will hopefully show the messages as the kernel loads up the driver.
Otherwise you can look at the various log files which live in /var/log. You will need to open a terminal cd to /var/log type ls -lrt to list the files in last modified time order and look for ones called something like boot.log or kern.log (there are various log files and I’m not entirely sure of the differences so you might have to look at a couple). Use something like vi (or editor of choice) and search for Celestron which should take you to the correct messages. I can’t confirm 100% as my setup is currently in pieces but it should be fairly obvious from what I remember. These lines should show which usb port is assigned. If it’s the one the indi driver is trying to use then keep looking through your log file to see if something else takes over that port as happened to me.
Another alternative is to use lsusb to list what ports are assigned to what, however you will most likely need to install the package usbutils. See www.thegeekdiary.com/lsusb-command-not-found/ for some details about this.
Read More...
dmesg is a command you enter in a terminal. It’s mainly for tailing the kernels message output. If you run this and then plug in the focuser usb cable it will hopefully show the messages as the kernel loads up the driver.
Otherwise you can look at the various log files which live in /var/log. You will need to open a terminal cd to /var/log type ls -lrt to list the files in last modified time order and look for ones called something like boot.log or kern.log (there are various log files and I’m not entirely sure of the differences so you might have to look at a couple). Use something like vi (or editor of choice) and search for Celestron which should take you to the correct messages. I can’t confirm 100% as my setup is currently in pieces but it should be fairly obvious from what I remember. These lines should show which usb port is assigned. If it’s the one the indi driver is trying to use then keep looking through your log file to see if something else takes over that port as happened to me.
Another alternative is to use lsusb to list what ports are assigned to what, however you will most likely need to install the package usbutils. See www.thegeekdiary.com/lsusb-command-not-found/ for some details about this.
Read More...
Dave,
thanks for reporting this, indeed, the parking options are only working for flats.
As a workaround, please try out the wall option in the calibration settings. It should work for flats and darks, but not for bias frames.
In the mean time, I will start fixing it.
HTH
Wolfgang
Read More...
I can confirm the issue, it's a regression. We'll hopefully have a fix by the time 3.6.5 is out in a couple of days.
Read More...
Discussed it with KStars development team and we'll go ahead with it. Unfortunately, there is no time to include in upcoming 3.6.5 release so it has to wait for 3.6.6 due in August.
Read More...
I summarized the requests and made a diagram.
The points are as follows.
・Do not mix with existing functions → It becomes difficult to use if there is a problem or lack of functions.
・Simplify the driver connection procedure.
Add an interface that simply has what you need where you need it. (for EAA)
EAA requires functions similar to those for planetary imaging. (Currently the most lacking part)
If only the EAA part is newly added and the steps to connect are reduced, it will be friendly to new users.
The atmosphere has changed a lot since the last forum, and I myself can't use some of my devices due to this update, so this is my final request.
Hope for better development.
Read More...
That's actually a brilliant idea. Similar to what we're doing to focus & guide images. Would be very useful for diagnostics.
Read More...
Please edit your signature and include your equipment and also what versions you're using so we don't need to ask about them.
I literally tested this yesterday to diagnose another issue with BLOB snooping. So Astrometry was definitely working. Was profile local or remote? The driver itself has an issue because BLOB snooping is now broken in INDI and hopefully there is a fix for this soon.
Read More...
