indigo_ccd_omegonpro not working with framework version 2.0-368

[HorstUSH]

After Update on Linux-Raspberry from 2.0-362 to 2.0-364 and selecting Camera 'Omegon veTEC571C' in ain_imager, the astrocamera did not start cooling and it is not possible to get a preview image.
For testing I restarted the indigo server only with omegonpro:
/usr/bin/indigo_server -c -w -vv indigo_ccd_omegonpro >> /var/log/indigosrv.log
This is an excerpt from the log:

18:44:26.897148 indigo_server: INDIGO server 2.0-364 Linux/arm64 built on 2026-03-31T12:49:46+00:00 production
18:44:26.901806 indigo_server: Driver indigo_ccd_omegonpro 2.0.0.40 loaded
18:44:26.902254 indigo_server: indigo_ccd_omegonpro: SDK version 59.31026.20260322
18:44:26.903478 indigo_server: indigo_ccd_omegonpro[indigo_ccd_omegonpro:2803]: libusb_hotplug_register_callback ->  OK
18:44:27.165372 indigo_server: Server attached
18:44:27.165922 indigo_server: Server started on port 7624
18:44:27.177144 indigo_server: Service registered as rapsfeld
18:44:27.449451 indigo_server: indigo_ccd_omegonpro[ccd_attach:643]: flags = 180876B8CC9
18:44:27.449730 indigo_server: indigo_ccd_omegonpro: 'Omegon veTEC571C' attached
18:44:30.939983 indigo_server: Driver indigo_agent_imager 2.0.0.56 loaded

after Camera-selection 'Omegon veTEC571C' in ain_imager:

18:46:04.321526 indigo_server: indigo_ccd_omegonpro[ccd_connect_callback:869]: Open(@tp-2-2-2-0547-12b7) -> 0x7f94001020

18:46:11.396582 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
18:46:16.397295 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
18:46:21.398477 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
18:46:26.399928 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
18:46:31.400605 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
18:46:36.401850 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f

this runs endless :-(

after setting Coler target-temperature to '3'

18:55:43.767232 indigo_server: indigo_ccd_omegonpro[ccd_change_property:1282]: put_Temperature() -> 8007001f
18:55:46.516641 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
18:55:51.517244 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f

setting cooling target temp fails, the callback-lines are filling the log
cooling power remains 0% , cooler actual temp shows 3.0°C , that is wrong, room temperature is 23°C
Attempt to start a preview produce this error:
19:00:10.108 Imager Agent.CCD_EXPOSURE: Exposure failed, pull callback was not called
this is seen in logfile:

19:00:06.575489 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
19:00:10.106374 indigo_server: indigo_ccd_omegonpro[exposure_watchdog_callback:423]: pull_callback() was not called in time
19:00:11.576090 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
19:00:16.576770 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f

server halted
rollback INDIGO framework to version 2.0-362
now restart /usr/bin/indigo_server -c -w -vv indigo_ccd_omegonpro (with 2.0-362 drivers)
After selecting Camera 'Omegon veTEC571C' in ain_imager, the astrocamera immediate starts cooling and reports correct power % and actual temperature. Image previews works as usual.
The log do not show endless temperature_callback 533 / 8007001f - lines.
Restart the server with normal options -c -w -v ,and the Version 2.0-362 works as usual

[rumengb]

I believe the problem is fixed in the repository. It will be released in a couple of days.

…

On Thu, Apr 30, 2026, 9:37 PM HorstUSH ***@***.***> wrote: *HorstUSH* created an issue (indigo-astronomy/indigo#747) <#747> After Update on Linux-Raspberry from 2.0-362 to 2.0-364 and selecting Camera 'Omegon veTEC571C' in ain_imager, the astrocamera did not start cooling and it is not possible to get a preview image. For testing I restarted the indigo server only with omegonpro: /usr/bin/indigo_server -c -w -vv indigo_ccd_omegonpro >> /var/log/indigosrv.log This is an excerpt from the log: 18:44:26.897148 indigo_server: INDIGO server 2.0-364 Linux/arm64 built on 2026-03-31T12:49:46+00:00 production 18:44:26.901806 indigo_server: Driver indigo_ccd_omegonpro 2.0.0.40 loaded 18:44:26.902254 indigo_server: indigo_ccd_omegonpro: SDK version 59.31026.20260322 18:44:26.903478 indigo_server: indigo_ccd_omegonpro[indigo_ccd_omegonpro:2803]: libusb_hotplug_register_callback -> OK 18:44:27.165372 indigo_server: Server attached 18:44:27.165922 indigo_server: Server started on port 7624 18:44:27.177144 indigo_server: Service registered as rapsfeld 18:44:27.449451 indigo_server: indigo_ccd_omegonpro[ccd_attach:643]: flags = 180876B8CC9 18:44:27.449730 indigo_server: indigo_ccd_omegonpro: 'Omegon veTEC571C' attached 18:44:30.939983 indigo_server: Driver indigo_agent_imager 2.0.0.56 loaded after Camera-selection 'Omegon veTEC571C' in ain_imager: 18:46:04.321526 indigo_server: indigo_ccd_omegonpro[ccd_connect_callback:869]: ***@***.***) -> 0x7f94001020 18:46:11.396582 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f 18:46:16.397295 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f 18:46:21.398477 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f 18:46:26.399928 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f 18:46:31.400605 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f 18:46:36.401850 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f this runs endless :-( after setting Coler target-temperature to '3' 18:55:43.767232 indigo_server: indigo_ccd_omegonpro[ccd_change_property:1282]: put_Temperature() -> 8007001f 18:55:46.516641 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f 18:55:51.517244 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f setting cooling target temp fails, the callback-lines are filling the log cooling power remains 0% , cooler actual temp shows 3.0°C , that is wrong, room temperature is 23°C Attempt to start a preview produce this error: 19:00:10.108 Imager Agent.CCD_EXPOSURE: Exposure failed, pull callback was not called this is seen in logfile: 19:00:06.575489 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f 19:00:10.106374 indigo_server: indigo_ccd_omegonpro[exposure_watchdog_callback:423]: pull_callback() was not called in time 19:00:11.576090 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f 19:00:16.576770 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f server halted rollback INDIGO framework to version 2.0-362 now restart /usr/bin/indigo_server -c -w -vv indigo_ccd_omegonpro (with 2.0-362 drivers) After selecting Camera 'Omegon veTEC571C' in ain_imager, the astrocamera immediate starts cooling and reports correct power % and actual temperature. Image previews works as usual. The log do not show endless temperature_callback 533 / 8007001f - lines. Restart the server with normal options -c -w -v ,and the Version 2.0-362 works as usual — Reply to this email directly, view it on GitHub <#747>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5EZBLX3OBO575NXMBATNT4YOMP7AVCNFSM6AAAAACYMTNM2KVHI2DSMVQWIX3LMV43ASLTON2WKOZUGM3DANBVGAZDOMQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[HorstUSH]

I now have tried this:
synaptic: rollback to indigo 2.0-362

find /usr  -type f -name '*omegonpro*' -ls
  189288 Mär 17 15:40  /usr/lib/indigo_ccd_omegonpro.so
  195104 Mär 17 15:40  /usr/bin/indigo_ccd_omegonpro

save the 2.0-362-omegonpro-files

cp /usr/bin/indigo_ccd_omegonpro     /usr/bin/indigo_ccd_omegonpro362
cp /usr/lib/indigo_ccd_omegonpro.so  /usr/lib/indigo_ccd_omegonpro.so.362

synaptic: indigo update to 2.0-364
trying restore only old 2.0-362 omegonpro-files while framework remains 2.0-364

cp /usr/lib/indigo_ccd_omegonpro.so.362  /usr/lib/indigo_ccd_omegonpro.so
cp /usr/bin/indigo_ccd_omegonpro362 /usr/bin/indigo_ccd_omegonpro
/usr/bin/indigo_server -c -w -v indigo_mount_pmc8 indigo_ccd_omegonpro indigo_ccd_bresser etc.

serverlog:

17:15:59.374320 indigo_server: INDIGO server 2.0-364 Linux/arm64 built on 2026-03-31T12:49:46+00:00 production
17:15:59.375100 indigo_server: Driver indigo_mount_pmc8 2.0.0.9 loaded
17:15:59.469214 indigo_server: Driver indigo_ccd_omegonpro 2.0.0.40 loaded
17:15:59.474526 indigo_server: indigo_ccd_bresser: SDK version 59.30239.20251209
17:16:00.018216 indigo_server: indigo_ccd_omegonpro: 'Omegon veTEC571C' attached
17:16:00.024406 indigo_server: indigo_ccd_bresser: 'Bresser GPCMOS01200KPF' attached
17:16:00.084376 indigo_server: indigo_ccd_bresser: 'Bresser GPCMOS01200KPF (guider)' attached
17:16:20.714969 indigo_server: indigo_mount_pmc8: Connected to /dev/ttyIEXOS
17:19:38.245648 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
17:19:43.246570 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f
17:19:48.248445 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:533]: get_Temperature() -> 8007001f

restoring only ccd_omegonpro* files to old version did not fix the issue.
synaptic: rollback to indigo 2.0-362 - this actually works for me
I try later the next released version

[rumengb]

Try 2.0-366... or if you wait several more hours 2.0-368 (i added some small improvements)

[HorstUSH]

Today I tested version 2.0-368
After selecting OmegonPro in ain_imager, the camera starts cooling and correct power% and temperature values are reported. This did not happen in version 2.0-364
But, after trying to capture an image, cooling stops, no image arrived and cooler remains off.
The log shows this entry:
12:04:04.561475 indigo_server: indigo_ccd_omegonpro[exposure_watchdog_callback:453]: pull_callback() was not called in time

Downgrade to 2.0-366
After selecting OmegonPro in ain_imager, the behavior is identical to version 2.0-368
Unfortunately after starting an image preview the error occurs again, no image, cooling stops, and the log shows:
12:27:44.072 Omegon veTEC571C @ rapsfeld.CCD_EXPOSURE: Exposure failed, pull callback was not called
Close GUI
Disconnect Camera from 12V power and USB
Reconnect Camera to 12V and USB
The raspberry is connected to home LAN
Open ain_imager on x86_64 GNU/Linux AMD Ryzen Desktop where framework 2.0-368 is installed
The ain_imager connects via LAN to raspberry running 2.0-366, and the camera starts cooling again.
After starting an image preview the camera stops again, no image, no cooling, error line again:
12:35:30.231 Imager Agent.CCD_EXPOSURE: Exposure failed, pull callback was not called
Now selected the Bresser guider-camera for testing. Image preview works as expected.
change to 'omegon veTEC571' - no operation again.
Disconnect camera from 12V and USB and reconnect it
Now selecting 'omegon veTEC571' starts the cooler, the temperature and power% shows correct values.
But, immediately after starting preview or expose, the cooler stops working, and 'pull callback was not called' is displayed.
Downgrade raspberry to 2.0-362
Restart indigo server on raspberry
start ain_imager on raspberry , cooler and preview works as expected.
Cooler fan is paused for 1..2 seconds while the image is retrieved, then it speeds up again. This is the normal behavior.
close ain_imager on raspberry
start ain_imager on x86_64 GNU/Linux AMD Ryzen Desktop connected via LAN to raspberry, cooler and preview works as expected.

[HorstUSH]

short update :-)
Upgrade ain_imager to new version 2.10-0
try indigo version 2.0-368, symptoms are identical to them obtained with ain_imager 2.0

17:13:38.588875 indigo_server: indigo_ccd_omegonpro[exposure_watchdog_callback:453]: pull_callback() was not called in time
17:13:40.661945 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:594]: get_Temperature() -> 8007001f

downgrade indigo to 2.0-362 , this works with new ain_imager 2.10-0, witch indigo_ccd_omegonpro 2.0.0.40 atached as main camera and indigo_ccd_bresser 2.0.0.4 atached as guider camera

[rumengb]

Thank you! I wrote a bug report to tpuptek. Both Omegon and Bresser are rebranded Touptek cameras. This is an SDK regression, and now we are waiting for touptek to take care of the issue. Rumen

…

On Thu, May 7, 2026 at 6:58 PM HorstUSH ***@***.***> wrote: *HorstUSH* left a comment (indigo-astronomy/indigo#747) <#747 (comment)> short update :-) Upgrade ain_imager to new version 2.10-0 try indigo version 2.0-368, symptoms are identical to them obtained with ain_imager 2.0 17:13:38.588875 indigo_server: indigo_ccd_omegonpro[exposure_watchdog_callback:453]: pull_callback() was not called in time 17:13:40.661945 indigo_server: indigo_ccd_omegonpro[ccd_temperature_callback:594]: get_Temperature() -> 8007001f downgrade indigo to 2.0-362 , this works with new ain_imager 2.10-0, witch indigo_ccd_omegonpro 2.0.0.40 atached as main camera and indigo_ccd_bresser 2.0.0.4 atached as guider camera — Reply to this email directly, view it on GitHub <#747 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5EZBMR35LCRAGQFES6AQL4ZSXBTAVCNFSM6AAAAACYMTNM2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGOJYG4YTIOBVGM> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>