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.
I'm a little bit afraid if the problem will occure or not...
Would be great if the final solution will be part of INDI 1.9.6. Unfortunately for Astroberry this packet will be updated 2-3 weeks after Stellarmate.
So I will wait before buying the camera. and hopefully we will see the solution in the release-note..
I recently bought the Omegon GUIDE2000C (Color Version) and was unable to get it to work with the default toupcam driver.
However, browsing the sources, I noticed the Product ID (0x1367) missing in the files.
Maybe they have a new version released?
So I assumed this model would not work for now.
Desperate I tried integrating the PID which lead to a lot of crashing.
But I than noticed Omegon has a new SDK released, which is different from the toupcam SDK.
I now integrated this Omegon SDK like the other subtypes of cams (mallincam etc).
With these changes I can use both of my Omegon cameras (veTEC -> Omegon Pro) and the Guide CAM simultanously.
After some testing I provide the changes via Pull Request.