Having some Issues with standalone Cockpit

Blue Robotics Software
1

Hi everyone,

I’m currently having some issues with the standalone version of cockpit, I couldn’t get the camera, depth sensor, etc to be found/recognized by the standalone. I finally opened the extension in my browser and it loaded up normally with camera and depth sensor data, and once it loaded there it found it and loaded it in the standalone, and then I closed the extension and can control everything from the standalone. Is this expected behavior? I could not find where to setup a camera stream directly in the standalone cockpit.

That leads me to my second question, do I even need Qgroundcontrol now that cockpit is so capable? It seems like I don’t need it, other than there does seem to be some settings I can’t find in cockpit that I can find in qgroundcontrol and in the browser version of cockpit. Do I just need to spend more time in the standalone and documentation, or are there limitations in the standalone, and to use all features I need to use qgroundcontrol and/or the browser cockpit?

I also get a message every time I open the standalone that tells me the settings for blueos and cockpit don’t match, and ask me to use the blueos or cockpit settings, how would I best go about making them the same so that I don’t get that error?

For reference, I am using a rov that I built, but it is heavily based on the bluerov2 heavy, and its controlled using a raspberry pi 3b with blueos, and a pixhawk with ardusub.

Thanks in advance for your time and help, I’m pretty new to rov’s and their software, but I’m excited by the cockpit software, and I’d love to be able to just fire up the standalone software, connect my rov, and go, without opening 2 or 3 programs if possible, but if not no worries.

2

Hi @FishingEngineer -
Glad to hear you’re enjoying Cockpit! It’s strange the standalone version didn’t recognize your vehicle at first - was it powered up? Checking your connection settings (settings >general > search for vehicles) may be a way to resolve that if it happens again.
Camera stream setup should happen automatically in Cockpit, but under settings>video you can see the streams that were detected, and verify your vehicle IP is set correctly (it will ignore IP addresses that aren’t listed here.)

Blue Robotics is moving towards dropping QGC completely - things that you may not find in Cockpit can be found under BlueOS / Vehicle Setup (sensor calibrations, motor directions setup.) The documentation for both is quite good!

That conflict message is unfortunately a bug, but should be fixed in the version of Cockpit that came out today. Sorry for the annoyance!

1 Like
3

This is very helpful, thank you!

Yeah it was a little strange, the camera stream wasn’t even detected until I opened the extension, then the standalone detected it, :man_shrugging: it always works now though, so I’m not too worried about it.

I understand now the message is a glitch, no worries there, I just thought maybe it was something I had done.

Thanks for responding and all your work!