Some additional information. I see the same behaviour in PHD2. When I connect my guide camera to PHD2 and the INDI Telescope Simulator, the guide camera keeps on taking exposure. When I change the mount to the INDI Celestron GPS driver, I get exposure time outs in PHD2. Exactly the same as with the internal guider of Ekos. So it seems to me there is some interference with the serial connection to the mount and the USB connection to the Touptek camera's. I had a discussion about this with a member of my astronomy club who has the exact same issue with his Omegon camera and his iOptron mount. I'm not sure of this is of any help but I hope it narrows it down a little
Please see my previous message. When I use Toupcam Guide Camera via the Telescope Simulator I also have no exposure time outs. But as soon as I use real mount with a usb to serial connection through the Celestron hand controller I get the time outs. Same behaviour in PHD2 on Stellarmate
Well, I can't replicate exactly that but I have serial devices connected to StellarMate and still no issues. Try to swap ports, or check power supply. (now running 35 mins with 5 devices connected to StellarMate and still no timeouts)
I tried all of that over the course of a couple of months. Different USB-cables, different powered hubs, non-powered hubs, exactly the same behaviour running kstars natively on my macbook pro and on Linux Ubuntu virtual machine on my HP-laptop. But everytime I get the same results. So I'm pretty out of options by now. The only thing left to do I if there's no solution for this is to get a new guide camera maybe. Any suggestions on what is a good reliable option?
I'm using a veTEC533c with Astroberry & Stellarmate via RPi4 USB3 port.
Additionally I'm using a ZWO ASI120MC-S connected via USB-3 cable to the veTEC USB-2.0 HUB.
The veTEC is powered by external 12V.
This works great and as expected using the internal Guider, not PHD2.
Now I want to exchange the ASI120MC-S by a veTEC GUIDE 2000M (has an USB2.0 Port).
Could the above stated problem also occure if using the "Internal Guider" or is is only related to the usage of PHD2?
I too have the Omegon Guide 2000M and the problem is the same in PHD2 as in the internal guider. I have the same problem on my MacBook Pro with the Omegon camera. Only under Windows and the ASCOM driver does the guide camera performs reliably.