Update the recommendation for the provisional best settings.
Karas said he will later make a Python script that can run sensor analysis under LINUX. It can be used to validate this data set. And get finer discrete values.
The current Mode0 recommended settings are as follows.
HFW = On
LCG = On (By threshold AUTO)
LN = On
2023 Jan Toup Ascom Driver （Same file with INDI 3rd）
Any Tips for station mode wifi connect crash？
On my computer，onstep INDI wifi connection is 100% got crash.
After trying on multiple computers, I found the only way.
reinstall the system (mine is Xubuntu) and install the software via PPA, once I have compiled INDI myself, this computer will not be able to connect to QHY, I suspect that some packages in the process of building the compiled environment and the QHY port conflict
I asked Karas about this and he said that the SDKs used by Ascom and Indi were not intentionally adjusted, which means that the measurements under Ascom are able to provide a reference for Indi to choose Logic Gain.
I looked carefully at the table you posted, and the 100Gain under LCG is in line with the HFW Off expectation.
So now we mainly need the measurement result of HFW On + LCG ON + (Optional LN OFF).
I upload here Latest Toupcam Ascom's HFW (High Full Well Mode) driver download, which is also the version build in December, it supports running sensor analysis in Sharpcap.
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.
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
First of all, the use of USB 2.0 is not recommended, there may be strange problems, including card readout and so on, and secondly, the current need to manually copy the OEM so file for replacement, other functions are the same
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.