Exactly, just in the Indi profile, remove the Touptec/ Omegon camera.

For 'normal' guiding though, I'd suggest to use the internal guider. I've used it often and it's good!

It should work as long as you select "INDI Camera" in PHD2.

I'm quite sure that I've already tested it that too a couple of times, but never worked. Just "time out".

I wish I could really! I do not like to have two apps running, but unfortunately, I didn't have good results with the internal guider while the same night I could achieve better RMS with PHD2.

What Omegon camera's do you have? I have a Guide 2000M and have a lot of connection issues with it in INDI/Ekos. The camera works great with the ASCOM drivers but loses connection after some minutes in ekos. Sometimes it recovers, sometimes it doesn't. But it's not reliable at all. I tried so many things that I gave up on it. I really would love to make it work, because I love using Ekos-Kstars a lot.

I have the Omegon 533 C for main and the Omegon 1200m for guide. I've tried both to connect them to PHD2 while are ON in Ekos but I had the same result "Unable to complete exposure, time out etc".

As soon as I disconnect the camera from indi tab, it works in PHD2.

That's exactly the same with my guide camera. I get the exposure time-out message. Not only in PHD2 but also with the internal guider of Ekos. If the guide camera is the only device that's connected it works fine. But as soon as I connect my mount or when an image is being dowloaded from my dslr. I tried different usb-cables, powered hub, directly connected to a raspberry pi with Stellarmate and even ran Ekos on my Macbook Pro, everytime the same behavior

I can confirm the issue with two camera (altair + toupcam). I'll look into it and see if it might be related to USB or something else.

Thanks Jasem, Please let me know if you need more information on the issue. I can provide you with some logs but I already looked at them but couldn't find much info there except for the exposure time-out and that ekos tries to reconnect.

I've spent a few hours on this. I see the same issue on my powerful PC, so it's not a USB issue at all. Something is broken in the Touptek library that causes then. Sometimes a frame times out without any reason. Even after I enabled "frame timeout notification" for touptek SDK, the timeout event wasn't triggered. Eventually, I had to introduce a custom timeout functionality and that appeared to did the trick. It's now on GIT.

Please test the nightlies later today and report back.

Can I do that on my Astroberry setup too? Cause probably will have the same issue too. Are there any instructions how to?

Jasem, I've just updated my Stellarmate copy to the latest stable and created a new simple profile (pic attached). As soon as I press start, the driver crashes. (In the meantime, it works in Astroberry copy).

That was the issue that you solved on the nightly?

This is from the debugger:

<code>2021-06-30T21:52:35: startup: /usr/bin/indiserver -r 0 -v indi_toupcam_ccd indi_manual_wheel indi_ioptronv3_telescope
[Attaching after Thread 0xb6ffa090 (LWP 2570) fork to child process 2580]
[Detaching after fork from parent process 2570]
2021-06-30T21:52:35: Driver indi_toupcam_ccd: pid=2580 rfd=3 wfd=6 efd=7
2021-06-30T21:52:35: Driver indi_manual_wheel: pid=2581 rfd=4 wfd=9 efd=10
2021-06-30T21:52:35: Driver indi_ioptronv3_telescope: pid=2582 rfd=5 wfd=12 efd=13
2021-06-30T21:52:35: listening to port 7624 on fd 8
2021-06-30T21:52:36: Driver indi_ioptronv3_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2021-06-30T21:52:36: Driver indi_ioptronv3_telescope: snooping on GPS Simulator.TIME_UTC
2021-06-30T21:52:36: Driver indi_ioptronv3_telescope: snooping on Dome Simulator.DOME_PARK
2021-06-30T21:52:36: Driver indi_ioptronv3_telescope: snooping on Dome Simulator.DOME_SHUTTER
2021-06-30T21:52:36: Driver indi_toupcam_ccd: indi_toupcam_ccd: symbol lookup error: indi_toupcam_ccd: undefined symbol: _ZN4INDI3CCD22checkTemperatureTargetEv
2021-06-30T21:52:36: Driver indi_toupcam_ccd: stderr EOF
2021-06-30T21:52:36: Driver indi_toupcam_ccd: Terminated after #0 restarts.
Child process 2580 died
No stack.</code>