Thank you, It works!
Please try to use the INDI V4L2 driver as it works better with UVC cameras.
Stellarmate Ekos on Raspbery Pi 5 hangs when UVC Web Cameras driver loads
This is a downstream issue. INDI does not install fxload. Should be installed by the system.
Forgot to mention I am using 3.7.5 build 2025-02-24T04:19:28Z
Initial install of QHY driver does not update fxload
Thank you for the information...Perhaps the problem comes from differents configurations (Indi control panel and Ekos window...) I put screenshoots in attachement. Hope you'll be able/want to help, even if I could'nt find how to use EkosDebugger... Reagrds. Franck.
I have the exact camera model and cannot produce a crash. Please use EkosDebugger to submit the backtrace (https://stellarmate.com/support/tutorials/ekos-debugger.html)
QSI-583-SWG & Ekos - Cannot download image
Ok, I think I may have found the answer. It took a while to get to grips with, but I finally got the GUI to come up within in Kstars, so evidently it is launched from within an application. Why is this not made clear in any documentation? So far I haven't been able to get it to work in Stellarium though.
Ok, I think I have found the answer. I finally got the GUI to come up within in Kstars, so evidently it it launched from within an application. So far I haven't been able to get it to work in Stellarium yet though.
Wjere is the options tab?
And it happened again. This time I fortunate to remember to switch back to primary a few minutes in. Only a few minutes lost. Perhaps I should explain my workflow. I take down my rig after every session. This means I must set it back up whenever I use it, and must polar align each time. Since I am using my guide camera to polar align, this means that every session I must remember to change my optical train to polar align and then change it back for alignment during the observing session. This is...
Separate Polar Align Optical Train from Regular Align Optical Train
Please run the following commands and take a screenshot: cd ~/Projects/indi git log indiserver cd ~/Projects/indi-3rdparty git log From the error message, it seems that indilib is not 2.0.9 (but it is unclear whether the file version is wrong or the installation is wrong).
Mars, I followed your script for second time and i get compilation errors... And the camera still doesn't work... Here you can see the command history. I had no errors installing packages, not even the one you mention in the txt. However fails in the last steps when indi-qhy is compiled... 1 sudo apt update 2 sudo apt upgrade 3 sudo apt -y install kstars 4 sudo apt-get install -y git cdbs dkms cmake fxload libev-dev libgps-dev libgsl-dev libraw-dev libusb-dev zlib1g-dev libftdi-dev libjpeg-dev libkrb5-dev...
Ok. Thanks. --Bob Robert Vanderbei I’m Robert J. Vanderbei and I approve this message. On Nov 15, 2024, at 1:56 AM, Jasem Mutlaq slovin@users.sourceforge.net wrote: That's the client's responsibility. Please contact SkyCharts developers. [support-requests:#3]https://sourceforge.net/p/indi/support-requests/3/ How to enter Universal Time in Site Management section Status: open Group: v1.0_(example) Created: Sun Nov 10, 2024 07:56 PM UTC by Robert J Vanderbei Last Updated: Tue Nov 12, 2024 07:28 AM...
That's the client's responsibility. Please contact SkyCharts developers.
Can we update things so that Cartes du Ciel also will fill in automatically? --Bob Robert Vanderbei I’m Robert J. Vanderbei and I approve this message. On Nov 12, 2024, at 6:30 AM, Robert J. Vanderbei rvdb@princeton.edu wrote: I use Cartes du Ciel. --Bob Robert Vanderbei I’m Robert J. Vanderbei and I approve this message. On Nov 12, 2024, at 2:28 AM, Jasem Mutlaq slovin@users.sourceforge.net wrote: It depends on the client. If you use KStars, it would be filled automatically. [support-requests:#3]https://sourceforge.net/p/indi/support-requests/3/...
I use Cartes du Ciel. --Bob Robert Vanderbei I’m Robert J. Vanderbei and I approve this message. On Nov 12, 2024, at 2:28 AM, Jasem Mutlaq slovin@users.sourceforge.net wrote: It depends on the client. If you use KStars, it would be filled automatically. [support-requests:#3]https://sourceforge.net/p/indi/support-requests/3/ How to enter Universal Time in Site Management section Status: open Group: v1.0_(example) Created: Sun Nov 10, 2024 07:56 PM UTC by Robert J Vanderbei Last Updated: Mon Nov 11,...
It depends on the client. If you use KStars, it would be filled automatically.
Thanks Jasem! That’s very interesting. I wonder if there’s any way to get my computer to automatically fill that in when I start the app. --Bob Robert Vanderbei I’m Robert J. Vanderbei and I approve this message. On Nov 10, 2024, at 11:28 PM, Jasem Mutlaq slovin@users.sourceforge.net wrote: It needs to be ISO8601 format! Attachments: Screenshot_20241111_072814.pnghttps://sourceforge.net/p/indi/support-requests/_discuss/thread/78ac8f9e06/c902/attachment/Screenshot_20241111_072814.png (7.9 kB; image/png)...
It needs to be ISO8601 format!
How to enter Universal Time in Site Management section
I believe there are a few points that need to be clarified.: This is the complete set of steps and scripts, just like the pictures provided before, starting from the burning of the SD card, and you should also start from this step (this is to completely eliminate old environmental factors). There are two ways to install indi-3rdparty, full installation and partial installation. To debug this issue, only one driver is installed in the script, so you should follow the content in the script. (You will...
Mars, I believe this procedure is incomplete. It doesn't include the installation of indi-3rdparty, so the camera is still not working. Could you please provide a complete installation procedure, including all the steps required to get the QHY174GPS camera working? [2024-11-02T12:11:04.329 -03 INFO ][ org.kde.kstars] - Welcome to KStars 3.6.2 Stable [2024-11-02T12:11:04.329 -03 INFO ][ org.kde.kstars] - Build: 2022-12-22T16:31:38Z [2024-11-02T12:11:04.330 -03 INFO ][ org.kde.kstars] - OS: "debian"...
Mars, I believe this procedure is incomplete. It doesn't include the installation of indi-3rdparty, so the camera is still not working. Could you please provide a complete installation procedure, including all the steps required to get the QHY174GPS camera working? [2024-11-02T12:11:04.329 -03 INFO ][ org.kde.kstars] - Welcome to KStars 3.6.2 Stable [2024-11-02T12:11:04.329 -03 INFO ][ org.kde.kstars] - Build: 2022-12-22T16:31:38Z [2024-11-02T12:11:04.330 -03 INFO ][ org.kde.kstars] - OS: "debian"...
Mars, I believe this procedure is incomplete. It doesn't include the installation of indi-3rdparty, so the camera is still not working. Could you please provide a complete installation procedure, including all the steps required to get the QHY174GPS camera working? [2024-11-02T12:11:04.329 -03 INFO ][ org.kde.kstars] - Welcome to KStars 3.6.2 Stable [2024-11-02T12:11:04.329 -03 INFO ][ org.kde.kstars] - Build: 2022-12-22T16:31:38Z [2024-11-02T12:11:04.330 -03 INFO ][ org.kde.kstars] - OS: "debian"...
The issue you encountered should be due to the master version being too active in development. I have selected a specific version in the script (both INDI and 3rd party need to use the same version). I have documented the scripts used You can skip the part about modifying the /etc/apt/sources.list file; I had to change the mirror myself because the network was too slow.
This issue appears to be related to a commit from this month; I need to set up a new system to verify it.
Mars, Here is the image
I understand that from the phenomena you've observed, it does seem like an SDK error, but I'm looking at the logs from execution. The logs show that the incorrect API was called, and it was called in a very strange way (half right, half wrong). This kind of issue typically occurs in some temporary versions during the development phase, and previous logs also indicate that the SDK at that time was a temporary version, not a released version. So it's clear that the error occurred before the SDK. Moreover,...
I understand that from the phenomena you've observed, it does seem like an SDK error, but I'm looking at the logs from execution. The logs show that the incorrect API was called, and it was called in a very strange way (half right, half wrong). This kind of issue typically occurs in some temporary versions during the development phase, and previous logs also indicate that the SDK at that time was a temporary version, not a released version. So it's clear that the error occurred before the SDK. Moreover,...
I understand that from the phenomena you've observed, it does seem like an SDK error, but I'm looking at the logs from execution. The logs show that the incorrect API was called, and it was called in a very strange way (half right, half wrong). This kind of issue typically occurs in some temporary versions during the development phase, and previous logs also indicate that the SDK at that time was a temporary version, not a released version. So it's clear that the error occurred before the SDK. Moreover,...
Hi Mars, This link https://indilib.org/download/raspberry-pi/category/6-raspberry-pi.html uses astroberry repo and is out of date. Isn't avaliable for ARM64. I followed the instructions from https://github.com/indilib/indi-3rdparty on Raspberry Pi OS Bookworm 64-bit, but the process failed when attempting to install either only indi_qhy_ccd or all drivers. (See 2024-10-30_00-23.png) Anyway, I used the previous SD card (with Raspberry Pi OS Bookworm 64-bit and software installed using the scripts...
yes, indi-3rdParty is missing maybe follow this steps https://indilib.org/download/raspberry-pi/category/6-raspberry-pi.html I use these steps allow me chose the version I want https://github.com/indilib/indi https://github.com/indilib/indi-3rdparty If you can use remote assistance software, such as TeamViewer anyDesk, we can arrange a time to check the issue together. (The email address has already been posted in the previous post)
Hi Mars, I couldn't advance with that last some days due to some extra work. Any way I'm back. I followed the process you suggest, however Camera doesn't connect to Kstars. Bellow I summarize the deploy process and issue. * I flashed the uSD card with Raspberry Pi OS Bookworm 64bits * I istalled uSD card and power on RPI * I enabled VNC (whit sudo raspi-config) * System update * sudo apt update * sudo apt upgrade * sudo reboot * Installa Kstars * sudo apt install kstars * Check KStars version astropi@astropi:~...
Hi Mars, I couldn't advance with that last some days due to some extra work. Any way I'm back. I followed the process you suggest, however Camera doesn't connect to Kstars. Bellow I summarize the deploy process and issue. * I flashed the uSD card with Raspberry Pi OS Bookworm 64bits * I istalled uSD card and power on RPI * I enabled VNC (whit sudo raspi-config) * System update * sudo apt update * sudo apt upgrade * sudo reboot * Installa Kstars * sudo apt install kstars * Check KStars version astropi@astropi:~...
I understand that having more systems that can "very well" support various devices and software is definitely a good thing for amateur astronomer. I myself also use different versions of customized astronomy systems. I like them. However, every system with good support goes through a painful process (I actually saw a small part of AstroArch's scripts, which is why I find it quite challenging; the scripts also make special handling of some driver files, so I guess it might be to avoid some undesirable...
I understand that having more systems that can "very well" support various devices and software is definitely a good thing for amateur astronomer. I myself also use different versions of customized astronomy systems. I like them. However, every system with good support goes through a painful process (I actually saw a small part of AstroArch's scripts, which is why I find it quite challenging; the scripts also make special handling of some driver files, so I guess it might be to avoid some undesirable...
Hello Mars, I'll try to answer your questions, but first I should mention that I'm not a software developer or tester. I'm just an amateur astronomer with some knowing about software integration who wants to control your the QHY Camera and other components with Raspberry Pi to make the observations more autonomous. And I basically want to take pictures of the sky with the hardware I bought and not struggle so much with the software. I use AstroArch or the astro-soft-build script because they are...
I have some questions: Why use https://gitea.nouspiro.space/nou/astro-soft-build instead of https://github.com/indilib/indi for verification? I have re-downloaded and installed the official version of the OS, both 32-bit and 64-bit, installed KStars with system libraries, recompiled INDI and INDI 3rdparty, and installed the SDK as prompted (https://www.qhyccd.cn/html/prepub/log.html#!log.md). I think now I can be sure that both methods can be used normally with cooling. Additionally, regarding that...
Some updates, I tried in same hardware setup on other SD Card with Raspberry Pi OS Bookworm (64 bit) and I still having the same problem. Software deployed with nou astro-soft-build script : INDI Library: 2.1.0 Code v2.1.0. Protocol 1.7. kstars 3.7.3 Stable Here you can find the log log_12-34-32.txt
I have set up a test environment under astroarch and found that directly controlling the temperature is ok. However, the power (PWM) obtained from kstars is incorrect, and I am investigating the cause. I will return to the Raspberry Pi OS system, but I need to wait a bit (more SD cards are needed).
Some updates, I tried in same hardware setup on other SD Card with Raspberry Pi OS Bookworm (64 bit) and I still having the same problem. Software deployed with nou astro-soft-build script : INDI Library: 2.1.0 Code v2.1.0. Protocol 1.7. kstars 3.7.3 Stable Here you can find the log log_12-34-32.txt
Some updates, I tried in same hardware setup on other SD Card with Raspberry Pi OS Bookworm (64 bit) and I still having the same problem. Software deployed with nou astro-soft-build script : INDI Library: 2.1.0 Code v2.1.0. Protocol 1.7. kstars 3.7.3 Stable Here you can find the log log_12-34-32.txt
Some updates, I tried in same hardware setup on other SD Card with Raspberry Pi OS Bookworm (64 bit) and I still having the same problem. Software deployed with [nou astro-soft-build]https://gitea.nouspiro.space/nou/astro-soft-build) script : INDI Library: 2.1.0 Code v2.1.0. Protocol 1.7. kstars 3.7.3 Stable Here you can find the log log_12-34-32.txt
Some updates, I tried in same hardware setup on other SD Card with Raspberry Pi OS Bookworm (64 bit) and I still having the same problem. Software deployed with [nou astro-soft-build]https://gitea.nouspiro.space/nou/astro-soft-build) script : INDI Library: 2.1.0 Code v2.1.0. Protocol 1.7. kstars 3.7.3 Stable Here you can find the log log_12-34-32.txt
May by with the command indi_qhy_ccd ?
QHYCCD cámera exposure timeout
I saw that response, but I didn't think that is the direction I want to go I believe astroarch didn't fully understand this issue. I might have to use the astroarch system to debug this problem and see where the issue lies. From the logs, it seems that for some reason the wrong API was called. This might be the easiest way to handle it. Another question: Besides using indiserver and md5sum, are there any other ways to confirm the version of indi_qhy_ccd?
I saw that response, but I didn't think that is the direction I want to go I believe astroarch didn't fully understand this issue. I might have to use the astroarch system to debug this problem and see where the issue lies. From the logs, it seems that for some reason the wrong API was called. This might be the easiest way to handle it. Another question: Besides using indiserver and md5sum, are there any other ways to confirm the version of indi_qhy_ccd?
I saw that response, but I didn't think that is the direction I want to go I believe astroarch didn't fully understand this issue. Below, I might have to use the astroarch system to debug this problem and see where the issue lies. From the logs, it seems that for some reason the wrong API was called. This might be the easiest way to handle it. Another question: Besides using indiserver and md5sum, are there any other ways to confirm the version of indi_qhy_ccd?
Hi Mars, I'm afraid my comment might have been hidden among previous messages. I'll repeat it below, apologies if that's not the case. I posted the same issue on the AstroArch GIT repository and a contributor wrote this about the SDK version. The SDK version is set directly there https://github.com/indilib/indi-3rdparty/blob/master/libqhy/CMakeLists.txt#L5
64bit OS image
I posted the same issue on the AstroArch GIT repository and a contributor wrote this about the SDK version. The SDK version is set directly there https://github.com/indilib/indi-3rdparty/blob/master/libqhy/CMakeLists.txt#L5
Raspberry Pi OS 32 or 64 bits?
Raspberry Pi OS KStars 3.7.2 INDI 2.0.8 this problem not occur
I am working on verifying this, but the permission issue has not been resolved yet. I will continue to update if there is any new progress. What bothers me more than verifying this is figuring out where the strange version number of the SDK comes from.
Hi Mars, if I understand you correctly, this problem occurs only in astroarch, is that correct? So if I install INDI and KStars directly on Raspberry Pi OS for example, this problem shouldn't occur?
We tested the directly downloaded indi2.0.8 and 2.0.9, but neither could reproduce the issue, so we plan to shift our focus to the system environment. However, we encountered a new problem: I am unable to obtain system permissions locally, which may take some time to check. I am still concerned about the unusual SDK version mentioned in the logs; this usually indicates a non-released version, and it also implies that this image might be using some unconventional environments, making it difficult...
Hi Mars, thanks for commenting on the progress. Let me know if I can do any tests to help you, if I can, I will. Best regards.
It seems a bit strange: when connecting to 174GPS, the log shows that the wrong API was used, but when connecting to 600M, it is correct. Therefore, it might be happening at the upper layer (driver). I will continue to investigate this issue, please wait patiently.
No problem, I will set up an AstroArch environment to confirm this issue. If AstroArch uses the same SDK as you, I should be able to resolve it. Additionally, since the National Day holiday has just begun, all testing will be slower, please be patient (about 8 days).
Sorry @mars can't understand you. I'm user, no developer. As previously post i'm using AstroArch SO over Raspberry Pi that includes indi 2.0.9.
The SDK version looks like not a publish version, can you tell me where you get that SDK? Please send to (my◎qhyccd.com)
Hi, some updates. The issue occurs with and without filter wheel connected. I enabled logging, start INDI, power on and configure the camera cooler both from Ekos capture panel and INDI control panel. I attach the log file.
QHY174GPS camera cooling doesn't work
After a rebuild and reinstall of indi core and drivers, made by Jasem Mutlaq, I've tested the driver, connecting and disconnecting it a few times, and it has always started well. So I think that now the bug is fixed. (Only remains the mentioned failure of connection in the first attempt, which is solved on the second attempt without any crash of the driver; but this is another less important issue). Thank you very much. Best regards Carlos Vera Hernández.
indi_scopedome_dome driver crash, after KStars last update to version 3.7.1
indi_scopedome_dome driver crash, after KStars last update to version 3.7.1
Error installing Indi/kstars-bleeding packages on Kubuntu 24.04 BETA
Edit The HC8408 version is 150302. OK, as per the motherboard driver v1220/v1216 I have the SmartEQ pro, not the Pro+. Then why I have a user manual for Pro+ with the mount?
Edit The HC8408 version is 150302. Might that be the issue with tracking? I will update it and try again.
iOptron SmartEQ pro+ tracking issue
QHY Driver crashing in StellarMate OS under Raspberry PI4
Please report issue here: https://github.com/indilib/indi
falcon rotator does not report current position
Please file the issue here https://github.com/indilib/indi
I forgot to give details of the driver package used on the RPI4 which provided the Lacerta MFOC driver AFAIK: Package: libindi1 Version: 1.9.9+202211300913~ubuntu22.04.1 Priority: optional Section: libs Source: libindi Maintainer: Jasem Mutlaq mutlaqja@ikarustech.com Installed-Size: 3122 kB
Lacerta MFOC Driver Hangs Up When Relative Positioning
indi_weather_vantage reporting error
https://www.indilib.org/ccds/toupcam-cameras.html
Toupcam Camera Driver Docu not up to date
ToUpTek Driver crashes in lates Astroberry Distro
Please file the bug here: https://github.com/indilib/indi/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc Include with it logs from the rotator driver. Check this guide on how to submit logs: https://indilib.org/individuals/logs-howto.html
PEgasus falcon rotator endless spin
Hi Jasem, I duplicated the report there: #522 Correction: The table has a typo: the two 4096 values should read 4095.
Please file this issue at https://github.com/indilib/indi-3rdparty
indi_mi: missing FITS headers and properties in ekos
Hi Jasem, How to get this fix on Stellarmate? Thanks
Please use Github to report issues: https://github.com/indilib/indi/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc At any rate, I submitted a fix to GIT. Please update from Git and test again if you can.
"INDI SkySafari Middleware Driver" point to fault coordination on negattive DEC object
The driver is called "ZWO EFW". Do you see the driver under filters? -- Best Regards, Jasem Mutlaq On Tue, Apr 27, 2021 at 5:16 PM Jim DeSpain jdespain@users.sourceforge.net wrote: thanks, was using ekos/stellarmate to set up system, when the system does a scan it picks up the filterwheel but in the drivers shown there is not a selection for any zwo driver under filter wheel? Am I not setting this up correctly or is there another driver location to acess? [feature-requests:#8] https://sourceforge.net/p/indi/feature-requests/8/...
thanks, was using ekos/stellarmate to set up system, when the system does a scan it picks up the filterwheel but in the drivers shown there is not a selection for any zwo driver under filter wheel? Am I not setting this up correctly or is there another driver location to acess?
There is just one driver that handles both. Best Regards, Jasem Mutlaq On Tue, Apr 27, 2021 at 3:27 AM Jim DeSpain jdespain@users.sourceforge.net wrote: [feature-requests:#8] https://sourceforge.net/p/indi/feature-requests/8/ ZWO filter wheel* Status: open Group: 0.9.6 Labels: Filter Created: Tue Apr 27, 2021 12:26 AM UTC by Jim DeSpain Last Updated: Tue Apr 27, 2021 12:26 AM UTC Owner: nobody can you provide the driver for the ZWO 5 position filter wheel Sent from sourceforge.net because you indicated...
ZWO filter wheel
Apogee Alta U16M fails to connect in INDI Control Panel.