Running latest version of Cockpit on a ROV2 HEAVY.
This latest version seems to take longer to get connected than previous software.
I’m not sure if there is a setting we can change but we have to wait for the double beep from the ROV and then start Cockpit. If we start Cockpit before ROV has completed it’s set up it never connects and we have to close it and restart.
Previous software the connection was made whilst the programme was running. It’s only 10 more seconds or so but we want to get up and running asap.
Which version are you referring to? If you’re on the 1.18 stable, there have been some improvements to the (re)connection process in Cockpit 1.19 (currently in beta) that may resolve your issue - it would be helpful if you could try installing a beta version to confirm.
We are using the May version of Cockpit at the moment. I don’t really want to rusk the Beta at this point just in case of bugs. Can it be installed alongside the May version and run independently or will I have to replace it entirely?
We have Cockpit installed as a standalone app version. Us there any benefit to installing it through Blue OS?
No advantage to using the extension version of Cockpit in the Browser - actually only disadvantages!
You can switch back and forth between Cockpit instances with easy, but you would need to uninstall / reinstall I believe. In general, I’ve not had any issues with Cockpit beta versions, and have run both ROV and BlueBoat on them for hours.
At least on Mac it’s possible to just rename the executables - I would assume the situation is similar on Windows, but I’m less familiar with the installation process.
There could potentially be some issues with settings handling if dropping back to an older version from a newer one, but I’m uncertain how isolated the settings are, or what issues such differences may cause.