I've recently done several compilations using github.com/JerryBlack/buildKstarsNightlyFromGit for several computers. I found that Kstars 3.6.2 works well with INDI 2.0.0, and toupcam basically has no problems.

But once Kstars3.6.3 is compiled, EKOS keeps reporting shooting failures. I believe the problem Jasem encountered most likely happened with 3.6.3, and I recorded the logs.

Also EKOS 3.6.3 has a very serious bug, Cature&Solve for Slew to Target will only parse once and then it won't work or try to slew to fix the error. This caused me to return to 3.6.2

How do you reproduce this issue? you mean manual rotation?

Sorry, the problem has been solved, now 3.6.3 and 2.0.0 are working fine together, toupcam doesn't crash anymore and solver is centered properly. Looks like it was a permissions issue I configured yesterday

===============
Please check reproduce video. I don't have E-CAA. I just mean normal Telescope Slew. to center the target



In the video:
First，use Sync to prove my Solver works fine.
Second, use Slew to Target solved success but dont slew and continue solving. My device has World Wide accessing VNC, if you need, you could login my device by IP port to test. ( This email address is being protected from spambots. You need JavaScript enabled to view it. )

Further testing revealed that after aborting an in-progress shot, infinite exposure failure occurs.

The test conditions were a focus module, a 1s cycle of short exposures by the camera, and stopping midway.

Lanco, would you be able to test the new driver using a usb 2.0 connection? I have never been able to get my Risingcam 2600 to work with usb 2. It connects, but any attempt to capture remains stuck in "Capturing" and nothing downloads.

indilib.org/forum/ccds-dslrs/12884-toupcam-driver.html

First of all, the use of USB 2.0 is not recommended, there may be strange problems, including readout stick, and secondly, the current need to manually copy the OEM so file for replacement, other functions are the same

Thank you for the information.

The usb 3 only restriction is unfortunate, because:

1) The camera works fine over usb 2 with the windows driver in ToupSky

2) My mount's (CEM40) through-the-mount cabling is usb 2, so I must run a separate usb 3 cable for the camera.

Back to the main point of the thread, the new High-FullWell mode:

What are your recommended settings?

HFW - On
Low-noise - Off(?)
LCG or HCG?

With the prior sdk version I was normally using LN=on and HCG Gain 100, while rarely using LCG, gain 100

HFW and LCG is badly needed,

LN on and off is rather ok.

And gain is best at 1e/ADU. I'm still try to measure which logic gain is 1e/ADU. If anyone got it, looking forward to hear. Limited by the quality of the light source, my last measurement is not very accurate, the theoretical value may be around 177 to 200

www.lightvortexastronomy.com/measuring-y...with-pixinsight.html

Considering that every sensor is different from the factory, it is recommended to measure your unity gain if you can.

The Crash JASEM encountered was reproduced on my pc for the first time. After the release of 2.0.0INDI and 3.6.3Kstars, I was curious if the stable version solved the connection of QHYcam and Toupcam, so yesterday I helped a friend of our Observatory to install Xubuntu 22.04 and the latest program from PPA as a clean install.

First I tested the connection to QHY5LIIM on my friend's computer, although still slower than ZWO, but the connection is much faster than in the past, and successfully connected and exposed.

After that I tested connecting the ToupCam 2600. It seems slow to establish a connection on my friend's computer, as this camera was instantly connected in the version I had built earlier.

But at least both cameras were able to connect to my friend's computer at the same time and work properly, I was then convinced that the stable version of PPA apt-install was no longer has this problem.

=============

Today I used the script github.com/lancoyan/buildKstarsNightlyFromGit on my computer, a computer that has compiled INDI 2.0.0 many times over, probably with some kind of residue.

In all the combinations of versions I build, including 3.6.2/3.6.3+2.0.0, the chart was instantly connected and worked fine, but QHY was completely unrecognized and unconnected (probably an isolated case of my computer).

So I wanted to try the PPA version to see if it would solve all the problems.

After installing the PPA version, perhaps with my previous compilation residue, the Toupcam begins to crash all the time.

I then uninstalled PPA, rebooted, rebuild my version, and installed the gdb package

sudo apt install gdb
sudo apt-get install indi-dbg
gdb --ex run --eval-command="set follow-fork-mode child" --args indiserver -v indi_toupcam_ccd

Surprisingly, before rebooting or installing GDB, even my build version was crashing, but after that it was fine, no more crashing, and the graph could run stably. QHY still won't connect though, and I have purchased ASI220 to replace QHY.

Toupcam Engineers Karas said they would try the PPA version on Monday to see if the crashes could be reproduced.

Camera offset information is not written in the FITS file. Is this Ok?

I do not have PI, so cannot run that type of sensor analysis. However, CN user Cbaxter ran a a sensor analysis in Sharpcapsensor analysis in Sharpcap . and those results are consistent with analyses from other brand 571 cameras



There is no "unity gain". For either LCG or HCG any gain higher than 100 suffers a loss of dynamic range.