Having some Issues with standalone Cockpit

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.

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

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!

A couple of follow up questions if that’s okay, hopefully they aren’t too basic. I can’t seem to find anywhere in blueos/cockpit to setup/change battery parameters, such as the battery voltage divider/multiplier or the a/v for amps, is that a feature that exists in the software? I can update it in qgroundcontrol for now, but just curious.

My other issue is that whenever I am trying to control the rov with my controller, it is also controlling my pc (windows), and so clicking buttons not only moves or activates the rov, it also opens different programs, closes others, etc. I feel like this should be an obvious setting in either windows or cockpit, but I cannot for the life of me find it.

Thanks again for all your help, you guys are awesome.

Hi @FishingEngineer -
You can modify the battery parameters in the Autopilot Parameters menu. You’ll be after BATT_VOLT_MULT, BATT_AMP_PERVLT, and BATT_AMP_OFFSET. You can quickly tune / calibrate your power sensor with the powerswitch calibration extension!

As for your issue with the controller affecting Windows - I’ve only seen this happen with a single button, generally at the center - and so I avoid using that button! If you have other buttons, or more than one button controlling windows, maybe you have some other software or setting configured for games / computer control? I don’t think that should happen in general - if using a controller that has different pairing modes, it may be worth trying another type/mode to pair the controller in. I saw on a forum with a quick search that steam / xbox controller settings could be causing this? ( settings->controller and uncheck Xbox controller support.)

1 Like

Thanks for the response!

I got the battery settings done, that was super helpful and easy.
It looks like my issue is with my steam gaming program trying to use the controller at the same time, so I’m working on disabling that, I didn’t even think about that also using the controller.

Thank you for such a fast response!

Jeremy

1 Like