I am in touch with someone from Risingcam.
They gave me some curves to try to fix my hesitations about the gain value. But the choice of the right value is still not really clear to me.
And I don't have many clear nights to check it.
For the error concerning the temperature sensor information. I sent the sdk I received with the camera to Jasem. As it seems more recent than the one used for the INDI current version, I hope it will fix the problem.
The underlying problem is that I am not very confident to the value returned in Ekos. But I might be too careful.

Hi
Eddie at Risingcam sent me this as the latest SDK:
drive.google.com/file/d/143Q0zIgmwQQqY6c...5fIAj9WA&usp=sharing

Any use?
Cheers,
Steve

Thank you,
This is the same I sent to Jasem.
You get in touch with Eddie too. A sympathetic contact very listening at Risingcam.

Ah, good. Yeah, Eddie responds to messages but works in sales. I've not yet managed to speak to anyone with technical knowledge.
I've told him that if he can ship from Europe, I'm buying. Let's see.
Good luck anyway. Most of the stuff you should be able to test during daytime.
Cheers

The SDK in INDI is already the latest.

Great Jasem,
So the error message about failure getting sensor temperature is still here.
Might be on a timeout while trying to get info from sensor without answer of it. Seems to disappears when doing off/on on cooler button. As if the sensor is not online since we do it.
If this could help current or future owners of the camera here are joins the curves I received from Eddie of Risingcam.
 

Hi Patrick, I have the same cam. Gain 100 means 0. Aslo found optimal offset 190-200 (2/3 hist shifted in biases). Temp error rises when setup 0C, I dont know why. If you change this value the error disapered.

Optimal offset 190-200 - thanks.

Anyone have advice on LCG/HCG usage also - in HCG I cant see anything unless I have gain of 10000. So far my temp seems to be OK at 0 but will adjust to -5 in case.

Did anyone get any updated drivers since the previous post?

last updates was in 2021. I've requested RisingCam Official Store, they gave this link drive.google.com/file/d/1p_0bIBacDHKcsJN...n.0.0.43853e5fiV4rbz but there is no indi driver. Here is another link from ToupTek www.touptek.com/download/download.php?lang=en&class2=66 but updates were made in the last year as well.

My Risingcam IMX571 returns to duty. I had issues with the driver on RPi 4 with previous versions of INDI. The last version has fixed the problem.
I agree with Dmitrii 0 or 100 is quite equivalent, 200 seems to be a reasonable value.
Those gain curves are really a bit confusing.
I still have a problem with the offset. I really don't know what value to use. So by default I set it to 10.

About the drivers, I don't see the plus value to update it.

I do not have this camera but I have another rebrand of ToupTek (Omegon 533) that uses the same driver.

The "temp alert" message is visible to me too but my cooling works great.

Lately I was troubleshooting my camera with my seller's service department and I found that if I load camera's drivers to NINA (yeah I know...) the default values are Gain 309, Offset 192 for Unity Gain. Maybe it's a hint you can use too to find out about your model.

I received my RisingCam IMX571C camera a few days ago. I have not seen the temperature alert (despite setting it to 0c). For gain, the consensus over on CN is to always use gain 100, with LCG for normal or HCG for a duoband filter. Any other gain setting reduces dynamic range with not enough reduction in read noise to make it worthwhile.

My problem, however, is random crashes. My first two sessions both experienced a crash of KStars. I have found a post on how to add the EkosDebugger Tool to Astroberry, but I just found it a minute ago so will not be able to do that tonight - debug info will have to wait for another night. The regular log has nothing interesting looking right before the moment of the crash, just normal guiding info. I used the internal guider one night and PHD2 the other, and PHD2 continued guiding after KStars crashed, so guiding is unlikely to be the culprit.

If anyone has suggestions for any other specific logging to enable, I would appreciate that.