Hello! When I tried last night to shoot M31 the driver for my SV405CC really didn't want to cooperate. First it'd crash mid-exposure or while downloading the frame. I reinstalled it and thought that fixed it but the frames kept coming in with an abysmal SNR, which paradoxically seems to get worse the longer the exposure length is. I've attached below a screenshot of 10s, 60s and 300s frames in that order from left to right. If needed I could run some tests and send some logs. In case anyone encountered this issue before, do you know of any way I could fix it?
PS: I'm running Kstars 3.6.7 and INDI 2.0.4.

I've just noted the same issue with SV405cc. I'm running Ubuntu 22.04.3 with indi-svbony package 1.3.8+t202310010705~ubuntu22.04.1 installed on an Odroid (aarch64). The very first capture after connecting to the camera is fine... but the second has poor signal to noise. I had not noticed further degradation after the second frame, but I couldn't rule it out. After disconnecting and reconnecting, the behavior repeats (good first image, bad subsequent images). I had used this camera successfully several weeks ago... so something changed in recent updates to this driver. :<

If used on Windows, does this SNR issue occurs? If not, then it's an SVBony SDK bug for Linux and must be reported to them ASAP. If it is replicated on Windows, then a hardware/firmware issue is more likely.

Some quick tests in NINA yesterday had the camera perform just right. I'll also try INDI+Kstars in Windows later today when I get home. Also, I can confirm what Frederick said, that up until about 4-5 weeks ago, when I last used the camera, everything worked alright.

Could you please get the latest indi-3rdpary/libsvbony and indi-3rdparty/indi-svbony from GitHub, build them and check them?
The indi-svbony included in the official version of INDI 2.0.4 is halfway implemented and unstable.
Also, indi-svbony 1.3.8 has a different structure from the latest code and is already unsupported.

I have not reproduced such a problem when shooting with SV405CC in my environment using the latest indi-svbony build.
I have checked the following two different nights

2023/11/3 Raspberry PI 4B: INDI+KStars/EKOS
2023/11/5 Raspberry PI 4B: INDI, Windows:KStars/EKOS

Hi, Jasem
Can you please show them how to install the latest indi-svbony driver if there is one in the nightly build for the OS they are using?

I checked the nightly PPA but couldn't find the driver for Svbony CCDs there (only for the 305). I also tried building from indi-3rdpary but cmake is throwing out errors:
Make Error at CMakeLists.txt:13 (find_package):
By not providing "FindCFITSIO.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "CFITSIO", but
CMake did not find one.

Could not find a package configuration file provided by "CFITSIO" with any
of the following names:

CFITSIOConfig.cmake
cfitsio-config.cmake

Add the installation prefix of "CFITSIO" to CMAKE_PREFIX_PATH or set
"CFITSIO_DIR" to a directory containing one of the above files. If
"CFITSIO" provides a separate development package or SDK, be sure it has
been installed.

Hi Ovidiu

Unfortunately, the sky was cloudy, so I photographed a nearby building.

Format: RAW 16 bit
Gain: 300, Offset: 40

Top: FITS: from left to right: 10s, 60s, 300s
Bottom: XISF: from left to right: 10s, 60s, 300s
* All images are delayered, No stretching.

INDI: 2.0.4 StellarMate OS Raspberry PI 4B
INDI SVBONY CCD Driver: 1.4.0
SVBONY Camera SDK: 1.11.4
KStars/EKOS: 3.6.7 WIndows 11

Increasing the exposure time also improves the SN value.
The SN value was checked in PixInsight's PROCESS>Image>Statistics.



The INDI SVBONY CCD Driver and EKOS simply save the image data retrieved from the camera by the SVBONY Camera SDK without processing it and adding a FITS header.
The phenomenon you posted is very strange when it comes to the INDI SVBONY CCD Driver.
I feel that it is most likely caused by something in the SVBONY Camera SDK, camera, optics, or weather/atmosphere.

It is still better to check with a newer version.
I usually build with StellarMate OS on my Raspberry PI and have not encountered any build errors, so I cannot advise you on your build errors.
If you describe your environment, there may be people on the forum who can advise you on the cause of build failures.

I'm trying to build using the terminal in the latest version of KDE Neon (which is based on Ubuntu 22.04)

Nevermind, it seems that the download was corrupted or something. I redid it and now it builds successfully. I did a bit of preliminary testing and it seems to work alright now. I'll return with more data when the next clear night comes around.

It sounds like this is fixed in the latest codebase (awesomeness), but just for completeness I wanted to note that I downloaded the deb for version 1.3.5+t202306010459~ubuntu22.10.1...and with no other changes...the problem I experienced was gone.

How do you check the SVBONY CCD Driver level? I can't get my 405cc to connect al and it crashes as soon as I click connect (I have stellarmate od on raspberry pi) I'm new to this so don't know how to do most things

When you say build them what do you mean?