Hi @dr_stony,
To be able to connect Cockpit to the vehicle, you need BlueOS to be running in that vehicle. If you don’t have BlueOS running in your vehicle yet, you can read more about it here.
Once you have it, make sure you can connect to BlueOS by having the vehicle on your network and accessing it through its IP on the browser. This is the same IP that you will use on the General configuration menu.
Hi @3dMB!
About the first problem, we fixed it already and should not happening in the latest version (1.0.2) anymore.
About the second one, we were not aware and will investigate.
Thanks @rafael.lehmkuhl
I have just tried with a different controller and the same issue occurs. I have also tried on my Mac, all still no control.
Thanks for the detailed report. I’ve opened an issue to check it. Will be back from vacation on monday and check that immediately.
Hi,
I ran into the same problem like Marcus. But I cannot find a point “General” in the slideout on the center left. Can you be a bit more precise? I’m very exited about this new Software but wondering a bit why the IP is not set as default so the average user does not has to struggle with find out where and what to type in.
If I start it directly from BlueOS on Rasp, I get a picture from the ROV but the latency is extremely poor and the heartbeat and manual control gets lost every 5 seconds. No operation possible. In QGC everythings OK, same Laptop with win11.
Thanks a lot for your development!
Best regards from the baltic sea
Chris
I do not have any experiences with installing an OS of the ROV. So the question:
Regarding that QGC is working fine,
Does the BueOS have to be reinstalled like a new firmware in the ROV itself?
Or is the BueOS installed on the ROV anyway, otherwise it wouldn’t work at all?
Would there be any problems getting data from the water temperature sensor?
Would a subtitle with the dive data (depth, temp etc.) also be displayed during film recordings?
If something goes wrong, do I have to assume that QGC will also stop working?
So far, for now
There’s some information on how to upgrade in the official release post from back in early 2022.
For some additional clarity:
Depending on when you bought / set up your ROV it may already have BlueOS installed, or our older Companion Software. If you’re not sure you should be able to find out from the vehicle’s web interface, which for Companion is at port 2770 (e.g. http://192.168.2.2:2770). BlueOS has a few different ways you can connect.
If your vehicle has a Navigator flight controller board then you’re definitely on BlueOS, and if you have a Pixhawk and you haven’t upgraded the vehicle to BlueOS then it’s most likely running Companion.
If this is just the standard temperature measurement(s) from a sensor that’s connected to the flight controller board (e.g. a Bar30, Bar100, or Celsius) then that’s mostly unrelated to the onboard computer software.
If you have some kind of custom water temperature sensor that you’ve integrated (which seems unlikely) then whether it’s affected by the onboard computer software will depend on how you’ve done that integration.
Cockpit does also generate subtitle files with its video recordings, and it provides much more control for that than QGroundControl 
It depends on the cause of the issue.
If Cockpit fails then that has no impact on QGC, but if the autopilot firmware (e.g. ArduSub) or onboard computer software (BlueOS) fail somehow then that will typically impact both QGC and Cockpit equally.
It’s in the Settings:
Apologies, the docs for this are still in progress.
http://blueos-avahi.local is a general address that should work as long as the computer has access to the vehicle, even if its IP address or mDNS domain have been set to something custom. If mDNS is somehow restricted or disabled for your computer (i.e. if you’re only able to access your vehicle via a direct IP address) then it’s necessary to manually specify an IP address to connect Cockpit to the vehicle.
If Cockpit is being hosted by BlueOS (i.e. installed as a BlueOS Extension on the vehicle, instead of being installed as an independent application on your control station computer) then it will automatically use whichever connection method you’re using for connecting to the vehicle.
I believe we’re also working on a startup wizard that walks through the relevant connection and setup processes to reduce the friction for this kind of thing in future
Oh yay! Not sure how I missed this. Congratulations all!
I’m confused on how to install 1.0.2…
I go to the link. Download the 1.0.2 file:
Downloads shows 1.0.2 file downloaded:
Install the file. Cockpit shows v1.0.1:
This version number in the about page is currently hardcoded and we forgot to update it. We will be linking that to our CI to update this automatically soon.
Hi,
Yesterday I tried once again to get a connection to the ROV over the Cockpit desktop version: I typed navis.local in the shown textfield but that didn’t help. I think, I’m going to wait until the installation wizard is available.
Best regards,
Chris
navos is the custom domain I’ve configured for one of my local development setups[1] - I was just trying to show you where the field was.
You’ll want to use a domain or IP address that your vehicle is accessible at (e.g. by default that’s typically 192.168.2.2, or blueos.local). If you’re able to access the BlueOS interface then you can generally use the same URL to connect Cockpit to BlueOS
If you’ve got it working as an Extension then you should be able to use the same URL that’s configured in that instance, as the URL to connect to with the desktop version (and if that’s not working, please let us know), but fair enough if that’s not something you want to mess around with at the moment.
I have two setups I regularly test with, and to make them accessible at the same time I have the Pixhawk one configured to use pixos as its mDNS domain name, and the Navigator one configured to use navos. That’s not relevant to most people, but I thought it was worth explaining in case anyone’s curious. ↩︎
At that moment when I knew what to do, I understood what you are talking about. 
Thanks a lot, now it works. The latency is OK and now I’m going to edit the User Interface. I’m looking forward for the first dive! Don’t forget to implement sound transmission that makes the ROV movements more precise for the pilot.
Best regards from the Baltic Sea
Chris
This is great work!
I notice the cockpit does have a linux-arm download, does it mean I can install it on a raspberry pi 4B board and set up a much smaller desktop instead of using a laptop?
Hi @AliceShanghai, yes, that is the plan
Just a note, there are 64 bits, older SBCs will be unable to run it.
This is really exciting! 
HiPatrick, Do I need to update my older flightcontrol firmware to BlueOS to work with cockpit, OR cockpit works well with the old Ardusub?
Hi @AliceShanghai -
To clarify - Cockpit requires BlueOS, and not the older Companion OS used on the Raspberry Pi. The ArduSub firmware version should not matter, but it is good to be on the latest on your Pixhawk (or newer Navigator) !
