Since yesterday, we have been having difficulty connecting to BROV2-Heavy through the Cockpit software.
The vehicle can be connected to and controlled via QGroundControl, but we no longer use it because all our settings and controls are configured in Cockpit, and we are much more comfortable using it.
I can connect to BlueOS without any issues. The ROV is able to send and receive MAVLink messages otherwise. However, in the Cockpit, I cannot see MAVLink messages, video streams, or arm/disarm controls, and I also cannot see the controller being connected.
Cockpit lets me search for the vehicle, and it finds the BlueROV2, but when it refreshes to reconnect, nothing happens. I have also tried the web version of Cockpit, but that is not working either.
We have also tried restarting the ROV a number of times, but that didn’t help either. I normally use Chrome for BlueOS, but I also tried Microsoft Edge as well.
We have been using Cockpit for a year now, and it has never behaved like this. Also, have field visits these days, so any help or fixes would be greatly appreciated.
Just to add to the things we tried, we normally use the desktop version of Cockpit which didn’t work either (it gave us the search option but that didn’t let us get connected). Fianlly, we tried installing the software on different laptops to check but the problem persisted.
Can you try manually specifying the vehicle network connection (in Settings > General) as the same URL you’re using to connect to BlueOS?
Beyond that, do you know which Cockpit version you’re using? 1.18 was very recently released as stable, so I would be interested to know if you’ve upgraded and that somehow stopped the connection from working / if the previous (1.17) version still works for you.
Hello, thank you for the quick response! Yes, I already tried that with manually inputting the address and then applying. At the same place, I tried the auto-search option as well.
I was using the 1.17 already. I tried 1.18 (x86_64) today, but the issue persists.
@AtifSultan also, could you grab us one log from 1.17 and one log from 1.18? Just open each one, leave it there for a minute and download the last log from /menu/settings/dev.
Ok so the issue was not very consistent. The issue disappeared on certain restarts.
I have the cockpit logs from when the issue occurred.
One progress is that when I checked the autopilot, there were no parameters being displayed in blueOS. when restarted the autopilot it also fixed the cockpit. Autopilot appears to be the culprit so far. What else can we do to diagnose the issue?
(We are mainly using c3-BR for surveys so we dont use the front camera feed, and also because it’s prone to getting disrupted by any physical movements)
The issue hasn’t reoccurred yet. If it does, I’ll try switching to Mavlink Server.
Also, I am now trying the 1.18.1 version of Cockpit @Rafael Araujo Lehmkuhl.
I’ve been using Cockpit for quite a while now without any issues. Switched to Mavlink Server on the endpoint page (and using the newer version of cockpit), the issue hasn’t reoccurred since.
