Of course, I set all the parameters and save the sequence.
The problem occurs only if I start shooting from the EKOS panel. Both in the case of starting a single shot (acquire preview) and starting a sequence. If I start a shot from the INDI control panel then everything works...

I thought offset adjustment was a new feature and the camera only had 31 ADU maximum. I do now know why you could set it to 256. Maybe it is a software offset. because the sensor can only support up to 4095 from 65535 at 16-bit mode.

Sorry for the late reply. I still can't get used to opening the forum every day, and I have been busy recently. I am so sorry.

So yes, based on the info, your cam is an older version and the whole system went off when CAMERA_STOP or switch resolution is called.

Maybe when INDI starts triggering, it would call switch resolution, even if it is the same resolution but the procedure would call the CAMERA_STOP.
Or maybe after the sub is finished, INDI would call CAMERA_STOP to put it to reset mode.

Neither of them is necessary if the user does not switch the resolution.

Hi Karas, really thanks for information! I did some test and found that camera stops cooling only when CCD_CAPTURE_FORMAT property is setting. It happens even if property value is not changed

The problem is software _have_ to set property `CCD_CAPTURE_FORMAT.INDI_RAW=true` even if it is already `true` because if not to do it, INDI driver will return RGB image instead of RAW.

Please fix it!

Does anyone have the new heat control working? It does not work for my Touptek IMX571

Hi everyone

We seem to be discussing two different scenarios:
- Risingcam and other varieties of camera using libtoupcam
- Omegon cameras using libomegonpro

Using the omegonpro software, our veTEC571 (purchased from Nimax two weeks ago) is working fine apart from having to set the temperature manually before starting capture... Almost certainly something I've overlooked when saving the capture sequence. It will however maintain that temperature accurately all night over many exposures.

The Risingcam 571 variants received both hardware and firmware updates recently. Amongst other differences, the old cameras have the power input diagonally opposite the usb3. The new cameras, beneath. I wonder if the issues mentioned here are anything to do with older models?

Here is the log and the .esl for an all night session with the veTEC:
drive.google.com/drive/folders/1mS9jrZuB...2TqSt?usp=share_link

Cheers, clear skies and HTH,
Steve

I did workaround in `ToupBase::SetCaptureFormat` : gist.github.com/art-den/e32eed7791cfd1f29db1bbcdadf5920c

I addedand then stop or start camera only if `format_changed == true`

This workaround solved the problem with cooling stop on taking of each photo

Denis,
thanks a lot for the workaround! Now my Omegon 571 is working fine again...

I tried to do live stacking with new driver last night and met same issue: indilib.org/forum/general/9923-omegon-pr....html?start=48#92186 ((

Image can't be downloaded from camera randomly, I had to restart live stacking each 10-20 minutes. Previous version of driver worked fine for my RizingCam IMX571

Hello all,
this is my first post after I am using Astroberry since almost 3 years.

My problem: I bought a Touptec 2600 camera, labled and sold by Noctutec in Germany. However, Astroberry does not recognize the camera at all, so did Sharpcap and even Toupsky in the beginning.
After contacting them, Noctutec informed me that the camera has the very latest firmware status and that there are also new drivers necessary (which they attached to their reply). After installing, Sharpcap and Toupsky (Windows) are working, however, I have no idea how to install the drivers in Linux or if they probably need to be modified for INDI.

Is somebody out there who can help?

Thank you for your replies

Bernhard

It's supported in INDI for a while now. Just make sure you have the latest libindi and indi-3rd party installed.