Is there actually any success story of a fully stable astroberry / ekos/ inid setup with QHYCCD imaging equipment?

I have been using Ekos/Indi for a few years now, starting with the AstroPi script. I have a QHY5L-II-M and 163M. I frequently had "stability" issues, but it is hard to say whether this was from indi/ekos or the QHY drivers themselves (after all, QHY's EZCAP_QT will still crash on my on my PC and Mac). Or was it my hardware, since I was using SBCs? I used a Rock64 setup until recently, and on that Ekos/Kstars would certainly crash now-and-then. I just got a Raspberry Pi 4 and installed Astroberry, but the weather has only been decent once. Everything seemed to go smoothly until .... Best I can tell, the vnc server died or wireless networking died while I wasn't monitoring the session, according to the logs. My sequence completed though, and I got an image of the Atlas comet before it broke apart.

That is very interesting! I have observed exactly the same problem twice lately where my wireless network was working fine, but suddenly during the night would disconnect. The scheduler completed the sequence, however, and the images were saved and the mount parked itself just fine, as programmed.
There seem to be consistent wireless problems on the Pi4, but this particular kind I had never seen until about a week ago.

It's not that the VNC server died, thee entire wireless connection went down on the Pi4 side and it lost its IP address, so no way to connect via ssh and restarting vnc either.

Has anyone else had the same problem/

Jo

The more I read this forum the less confidence I have to get all the problems resolved and ensure my setup is working perfectly in rare clear sky in my location.
I've decided to temporarily fall back to windows / ASCOM based system, at least it works almost all the time for me.
Not saying astroberry/ INDI is no good, it does offer a free remote solution to many, but I can't even get to the point which I can get both my QHY main and QHY guide cameras connected so maybe this version is not for me. I will wait for the next version.
Hope to see more development on it.

I don't know what cameras you are using, but I cannot recall ever having a connection issue with my QHY5L-II-M and Ekos. The 163M took longer, but as I alluded to, the QHY drivers took a long time to mature across all platforms. I do seem to recall someone having an issue with other combinations of QHY cameras. Yeah, I have mostly stuck with Indi/Ekos to have a compact solution while travelling with my gear, and I use an iPad Mini to do most of the control.
A few people have attributed connection issues to underpowered PSUs, so you might see if you can give it some more juice. There was a recommendation for a while to put the cameras through a dedicated, powered USB hub. While using my Rock64 SBC, I used to do that (Sabrent USB 3 , 7 port hub).
If you want to troubleshoot it, there are people here to assist. The output of "lsusb" and "dmesg" is often useful to know if the computer is even recognizing the devices.
Regards.

That's what the forum is for. Indi/Ekos is one of the best astrophotograpyhy suites around. It is still on the road to perfection, but it is lightyears ahead of where it was when I first joind 30 months ago.

So be patient!

Oh good, I'm not the only one who can't get EZCAP_QT running. I tried running it directly (the thing that shows up in your start menu is a script) and it failed. I even tried compliling it according to instructions on QHY's site, but the downloaded source code is missing what appears to be a fairly critical file, so it won't actually compile.

I've had that too with the VNC cutting out. But Ekos over the network seems to work fine.

We probably should create a different thread on the VPN issue....
WiFi Connection dropped on me again Sunday night. I used a lightning-to-rj45 dongle to connect directly. Oddly, the UI said I was still connected via WiFi, but perhaps the act of directly connecting reset the configuration. I disconnected and reconnected for good measure, and no problems the rest of the night.

Re the post below, I'm still unable to get everything resolved and when I switch the pi on again the other day with the QHY cameras connected, the keyboard and mouse USB ports refused to join the debugging game... and hence... game over... and lets get back to the real hobby - imaging, not debugging.
indilib.org/forum/astroberry/6827-astrob...kstars-and-indi.html

I tried to brainwash myself this is just part of the fun...

In answer to the question "Is there actually any success story of a fully stable astroberry / ekos/ inid setup with QHYCCD imaging equipment?" Not sure if it helps but I have a very stable setup running the QHY5L-II M as guide camera on Indi/Ekos on a Rock64, although I built it using the simple download Ubuntu instructions at: indilib.org/download/ubuntu.html. I have been using the setup with changes of equipment for about 2 years. Some learning: use a well powered USB hub; make sure the 12v supply has enough power, I use RoyPow 12V 10A Adapter, wires beats wireless, my Rock64 has a wired ethernet connection. One of the challenges of Indi/Ekos is that there are so many options & settings and it takes some digging to get them right. So recently I found Astrometry stopped solving when I changed spacing on a scope and it took me a while to find the setting to get it to forget the old "FOV". But when then once I have a settled config everything works wonderfully.

What's your main camera? Is it also a QHY CCD?

One of the problems I'm facing is that multiple QHY cameras can't live together with astroberry, but only 1 is fine.