I’ve had this issue too but mostly with the browser version of cockpit which happens when you switch (ie lose focus) to another browser page (eg blueos) or app (eg pingviewer).
Situation seemsmuch better with the standalone version where you can instead add another ‘view’ page with an iframe widget to the blueos, sonarview etc. This is very useful as allows you to switch rapidly between the different views with a joystick/controller button (and even set the iframe transparency so you can still see the normal cockpit view/camera etc.)
Haven’t been able to get the ping1d to display in Sonarview/iframe yet but see this thread for an impending solution.
The Omniscan 450 FS works great setup like this but is still a bit clunky - I have to cycle through all the views to clear the last iframe to load (I think) and is better to wait a minute after starting cockpit for everything to load properly.
Also I found the ‘lost control’ error varies a lot between different computers I’ve tried. Not sure whether this is to do with different graphics, CPU capacity etc. or maybe the available power on the USB ports (a higher capacity power supply might help).
Awesome setup and love to see a photo of how you integrated all this as not a lot of space for all that!