INDI Astronomical Control Protocol / Bugs / #99 QHY174GPS camera cooling doesn't work

Matías Leonel Martini - 2024-09-29

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.

371881561-0e7ae828-d3b2-4de3-9d8e-2c593e5abc40.png

log_15-09-51.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

mars - 2024-09-30

The SDK version looks like not a publish version, can you tell me where you get that SDK?
Please send to (my◎qhyccd.com)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Matías Leonel Martini - 2024-09-30

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.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- mars - 2024-09-30
  
  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).
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

mars - 2024-09-30

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.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Matías Leonel Martini - 2024-09-30

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.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

mars - 2024-10-09

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 to pinpoint the issue.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Matías Leonel Martini - 2024-10-09
  
  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?
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - mars - 2024-10-09
    
    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.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Matías Leonel Martini - 2024-10-09
      
      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
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - mars - 2024-10-09
    
    Raspberry Pi OS
    KStars 3.7.2
    INDI 2.0.8
    
    this problem not occur
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Matías Leonel Martini - 2024-10-09
      
      Raspberry Pi OS 32 or 64 bits?
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

mars - 2024-10-10

64bit OS image

pi4_uname.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Matías Leonel Martini - 2024-10-10

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

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- mars - 2024-10-12
  
  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?
  
  Last edit: mars 2024-10-12
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Matías Leonel Martini - 2024-10-12
    
    May by with the command indi_qhy_ccd ?
    
    Captura.PNG
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

mars - 2024-10-12

Last edit: mars 2024-10-12

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Matías Leonel Martini - 2024-10-13

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

Last edit: Matías Leonel Martini 2024-10-14

log_12-34-32.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

mars - 2024-10-14

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).

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

mars - 2024-10-14

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 strange issue: in the astroarch system, I am temporarily unsure which direction to focus on next because the base library tests have passed, so the SDK and firmware is correct, and the indiserver indi-3rdparty also seems to be correct, which is why I wanted to verify the versions of various files across different systems.

I am not very familiar with the astroarch system, and moreover, in my location (China), its network support is relatively poor, leading to various unexpected issues during debugging.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Matías Leonel Martini - 2024-10-14

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 the easiest way, for a common user, to deploy the entire software set needed. People I interact with regularly in person and forum also do so this way or with other distributions such as Astroberry or StellarMate. For a common user isn't so simple build and install all the things separately (INDI, INDI Drivers, SDK, etc). I treated in the past and i fail because the instructions are not adapted for a Raspberry Pi.

From my point of view I can't see the problem in this way of deploy INDI. I have other setup (same but ZWO ASI178-M camera) that works well. I also have friends who use INDI in the same way with different cameras without problems. One of them actually has a QHY163M. In fact, the problem seems to be with QHY174GPS INDI Driver or SDK.

Furthermore, as you can see, boot AstroArch are using official INDI repositories https://github.com/indilib/indi and https://github.com/indilib/indi-3rdparty. As you say, I don't know why indi-3rdparty doesn't use the official SDK, I understand that it is updated by the manufacturers. If you are one of the maybe now more than me.

Any way, for me is the same use the camera on AstroArch or Raspberry Pi OS, may be the last is the better. If you were able to get the QHY174GPS camera working on Raspberry Pi OS, please send me the implementation instructions and I can do the same.

Best Regards,

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

mars - 2024-10-15

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 issues).

The indi-3rdparty actually uses a historical version of the official SDK released, but this is not a problem, especially for the 174GPS camera.

The recommended testing method is to use the native Raspberry Pi system to test this issue (simply because this method is more commonly used, at least for now).

The recommended installation order is:

Flash the Raspberry Pi system.
Update apt.
Install kstars using apt.
Ensure you are using the same version of indi-core and indi-3rdParty (1.9.9 by default in the system or 2.1.0 from GitHub).
In the previous step, you may be prompted to install libqhyccd.so; please download it from this website (https://www.qhyccd.com/html/prepub/log_en.html#!log_en.md#Demo_And_API_Documentation). Note to distinguish between arm_32 and arm_64.
If you still encounter problems following the above order, you can send me an email(my◎qhyccd.com). I think we can quickly resolve it remotely.

Last edit: mars 2024-10-15

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

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:~ $ kstars --version
QStandardPaths: wrong permissions on runtime directory /run/user/1000, 0770 instead of 0700
QStandardPaths: wrong permissions on runtime directory /run/user/1000, 0770 instead of 0700
Call to writableLocation without an application-based location.
kstars 3.6.2 Stable

Check INDI Server version

astropi@astropi:~ $ indiserver --version
2024-10-28T00:01:11: startup: indiserver --version
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 1.9.9
Code 1.9.9-tgz. Protocol 1.7.

SDK installation
- wget https://www.qhyccd.com/file/repository/publish/SDK/240801/sdk_Arm64_24.08.01.tgz
- tar xvf sdk_Arm64_24.08.01.tgz
- cd sdk_Arm64_24.08.01/
- sudo bash install.sh
- ls -al /usr/local/lib/libqhy*

astropi@astropi:~ $ ls -al /usr/local/lib/libqhy*
-rw-r--r-- 1 astropi astropi 19504316 Aug  1 05:13 /usr/local/lib/libqhyccd.a
lrwxrwxrwx 1 astropi astropi       15 Aug  1 05:13 /usr/local/lib/libqhyccd.so -> libqhyccd.so.20
lrwxrwxrwx 1 astropi astropi       22 Aug  1 05:13 /usr/local/lib/libqhyccd.so.20 -> libqhyccd.so.24.8.1.16
-rw-r--r-- 1 astropi astropi  5628904 Aug  1 05:12 /usr/local/lib/libqhyccd.so.24.8.1.16

ldd /usr/bin/indi_qhy_ccd |grep libqhy*

astropi@astropi:~ $ ldd /usr/bin/indi_qhy_ccd |grep libqhy*
ldd: /usr/bin/indi_qhy_ccd: No such file or directory

I run Kstars, create a new profile and started but camera does'n connect. Here the log

[2024-10-27T21:08:44.585 -03 WARN ][                       default] - QStandardPaths: wrong permissions on runtime directory /run/user/1000, 0770 instead of 0700
[2024-10-27T21:08:49.358 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:08:49.516 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:08:50.571 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:08:50.924 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:08:56.303 -03 DEBG ][           org.kde.kstars.ekos] - Resetting Ekos Manager...
[2024-10-27T21:08:56.341 -03 INFO ][           org.kde.kstars.ekos] - "Starting INDI services..."
[2024-10-27T21:08:56.343 -03 DEBG ][           org.kde.kstars.indi] - INDI: Starting local drivers...
[2024-10-27T21:08:56.344 -03 DEBG ][           org.kde.kstars.indi] - Starting INDI Server:  ("-v", "-p", "7624", "-m", "1024", "-r", "0", "-f", "/tmp/indififod48d5d62") -f "/tmp/indififod48d5d62"
[2024-10-27T21:08:56.357 -03 DEBG ][           org.kde.kstars.indi] - INDI: INDI Server started locally on port  7624
[2024-10-27T21:08:56.358 -03 DEBG ][           org.kde.kstars.indi] - INDI Server Started?  true
[2024-10-27T21:08:56.358 -03 DEBG ][           org.kde.kstars.indi] - Starting INDI Driver "indi_simulator_telescope"
[2024-10-27T21:08:56.380 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: startup: /usr/bin/indiserver -v -p 7624 -m 1024 -r 0 -f /tmp/indififod48d5d62"
[2024-10-27T21:08:56.380 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: listening to port 7624 on fd 5"
[2024-10-27T21:08:56.381 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: Local server: listening on local domain at: @/tmp/indiserver"
[2024-10-27T21:08:56.381 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: FIFO: start indi_simulator_telescope -n \"Telescope Simulator\""
[2024-10-27T21:08:56.381 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: With name: Telescope Simulator"
[2024-10-27T21:08:56.381 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: FIFO: Starting driver indi_simulator_telescope"
[2024-10-27T21:08:56.381 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: Driver indi_simulator_telescope: pid=2268 rfd=9 wfd=9 efd=10"
[2024-10-27T21:08:56.381 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2024-10-27T21:08:56.383 -03 WARN ][           org.kde.kstars.indi] - Driver "QHY CCD" failed to start. Retrying in 5 seconds...
[2024-10-27T21:08:56.450 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: Driver indi_simulator_telescope: HaAxis: TrackRate 1, trackingRateDegSec 15.041067 arcsec"
[2024-10-27T21:08:56.450 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2024-10-27T21:08:56.456 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: Driver indi_simulator_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD"
[2024-10-27T21:08:56.456 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: Driver indi_simulator_telescope: snooping on GPS Simulator.TIME_UTC"
[2024-10-27T21:08:56.457 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_PARK"
[2024-10-27T21:08:56.457 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  "2024-10-28T00:08:56: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_SHUTTER"
[2024-10-27T21:08:56.457 -03 DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2024-10-27T21:08:58.464 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:08:58.910 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:08:59.384 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:09:01.036 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:09:01.076 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:09:01.505 -03 WARN ][           org.kde.kstars.indi] - Driver "QHY CCD" failed to start. Retrying in 5 seconds...
[2024-10-27T21:09:06.504 -03 WARN ][           org.kde.kstars.indi] - Driver "QHY CCD" failed to start. Retrying in 5 seconds...
[2024-10-27T21:09:08.731 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:09:09.783 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:09:09.870 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:09:10.131 -03 CRIT ][                              ] - QWaylandShmBuffer: mmap failed (Invalid argument)
[2024-10-27T21:09:11.505 -03 WARN ][           org.kde.kstars.indi] - Driver "QHY CCD" failed to start. Retrying in 5 seconds...
[2024-10-27T21:09:16.503 -03 WARN ][           org.kde.kstars.indi] - Driver "QHY CCD" failed to start. Retrying in 5 seconds...

It seems like something is missing in that procedure, maybe indi-3rdParty. Could you help me to solve it?

Best regards

Last edit: Matías Leonel Martini 2024-10-28

mars - 2024-10-29

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)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

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 from https://gitea.nouspiro.space/nou/astro-soft-build) and follow the instructions from https://www.qhyccd.com/html/prepub/log_en.html#!log_en.md#Demo_And_API_Documentation. I then installed the latest official SDK version with the following commands:

wget https://www.qhyccd.com/file/repository/publish/SDK/240801/sdk_Arm64_24.08.01.tgz
tar xvf sdk_Arm64_24.08.01.tgz
cd sdk_Arm64_24.08.01/
sudo bash distclean.sh
sudo bash install.sh
ls -al /usr/local/lib/libqhy*

astropi@astropi:~ $ ls -al /usr/local/lib/libqhy*
-rw-r--r-- 1 astropi astropi 19504316 Aug  1 05:13 /usr/local/lib/libqhyccd.a
lrwxrwxrwx 1 astropi astropi       15 Aug  1 05:13 /usr/local/lib/libqhyccd.so -> libqhyccd.so.20
lrwxrwxrwx 1 astropi astropi       22 Aug  1 05:13 /usr/local/lib/libqhyccd.so.20 -> libqhyccd.so.24.8.1.16
-rw-r--r-- 1 astropi astropi  5628904 Aug  1 05:12 /usr/local/lib/libqhyccd.so.24.8.1.16

ldd /usr/bin/indi_qhy_ccd |grep libqhy*

astropi@astropi:~ $ ldd /usr/bin/indi_qhy_ccd |grep libqhy*
    libqhyccd.so.20 => /usr/local/lib/libqhyccd.so.20 (0x0000007f9d7b0000)

I checked software stack versions, note SDK versión = 24.08.01

astropi@astropi:~ $ kstars --version
QStandardPaths: wrong permissions on runtime directory /run/user/1000, 0770 instead of 0700
QStandardPaths: wrong permissions on runtime directory /run/user/1000, 0770 instead of 0700
Call to writableLocation without an application-based location.
kstars 3.7.3 Stable
astropi@astropi:~ $ indiserver --version
2024-10-30T03:41:29: startup: indiserver --version
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 2.1.0
Code v2.1.0. Protocol 1.7.
...
astropi@astropi:~ $ indi_qhy_ccd 
-- qhyccd.cpp param
QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
QHYCCD|QHYCCD.CPP|libusb_version 1.0.26.11724
QHYCCD|QHYCCD.CPP|libusb_init(libqhyccd_context) called...
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
************************** config file path  24.8.1.16 svn: 14086  ************************************
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|Load ini filePath = /home/astropi  fileName = qhyccd.ini
libusb_handle_events() failed: LIBUSB_ERROR_INTERRUPTED

After that I ran Kstars, but the camera cooling still doesn't work. Attached, you can find the log. As you can see, the SDK version is 24.08.01.

[2024-10-28T23:51:16.966 -03 INFO ][           org.kde.kstars.indi] - QHY CCD QHY174M-1a59dc4 :  "[INFO] Using QHY SDK version 24.8.1 "

So, do you still think this is an AstroArcho, deploy script or INDI issue? I'm no expert, but it seems pretty clear that it's an SDK issue. Anyway, It shouldn't be so overly complex to get it working para un usuario. I've never had issues with other cameras in these environments.

Sorry to ask, but did you actually get the QHY174GPS camera working properly with INDI?

If you still think it's just my problem we can arrange a meeting between 21:00 UTC and 03:00 UTC to solve together but I'm afraid we lose time.

log_23-47-47.txt

QHY174GPS camera cooling doesn't work

Group

Searches

Help

#99 QHY174GPS camera cooling doesn't work

Discussion