Interesting… Okay well we’re getting closer to identifying the problem at least!
Could you please, on your microscope, run:
sudo ofm upgrade -u https://build.openflexure.org/openflexure-microscope-server/debug/openflexure-microscope-server-mmgoessens-0.tar.gz
then
sudo ofm stop
then
sudo ofm serve
Your console will fill up with a TONNE of junk constantly showing the size of the current stream frame. Could you please watch this number (it should be pretty high, hundreds of thousands) then move to a region that causes your stream to cut off, and see if the number drops to 0 or stays high?
When you’re done, you cat Ctrl-C to exit. Please only do this once, as pressing again during the shutdown sequence can cause your settings file to become corrupt (unlikely but I’ve seen it happen)
I appreciate this is a time sink for you, but it would really help debug the issue.
Thanks!
For anyone else on the dev team following this, my logic is that if the frame size stays high, then we can assume it’s an issue with the network. If the frame size drops to zero then it may be something like running out of VRAM when encoding the camera data to JPEGs. If it’s a network limit then there’s not a lot we can do save for allowing reduced stream quality at the expense of autofocus reliability.