Cockpit first Beta release!

Blue Robotics Software Cockpit
4

Thanks for the testing and feedback Bill! Will comment on each point below:

  1. We indeed have a (big) video problem in Cockpit right now, and we are releasing the solution on Beta3 today. As you can see there, we are using (a lot) more resources than necessary and this, together with a bug we discovered recently in the camera manager is causing lags, stuttering and sometimes even loss of control on the vehicle. I expect all of those problems to be gone on Beta3. I don’t expect changes in this behavior from Beta1 to Beta2, as there were no changes related to that, but if you happen to have opened a video recording or updated your BlueOS version to master, that could have worsened the problem.

  2. Was that a MAVLink MANUAL_CONTROL “Camera trigger” function that you added? If so, this function is not directly connected to Cockpit, and is actually sending a message to the vehicle saying it wants to trigger the camera, although I don’t know if the vehicle or our camera manager do have support for that. I’m summoning @williangalvani, @joaoantoniocardoso and @patrickelectric here to clarify on this one. If we already have support on both ArduSub and MCM, we can make Cockpit work with it, although I think a more straightforward solution is to just add a “Toggle video recording” function to the Cockpit Actions protocol. Opened an issue to track that.

  3. Actually the VeryGenericIndicator already has a preset for tether turns. After you click to use it you can check on the “Custom” tab which is the variable being consumed by it.

  4. You did it right. The problem was that our extensions manager was not considering <1.0.0 versions as unstable, so if you had v0.18.2 for example, when Beta1+ were released, BlueOS considered those to be unstable versions and didn’t offer it to you. We are fixing that for the next minor stable release on BlueOS. For now, you just need to open BlueOS’s extensions page, and on the store tab, click to install the latest Beta version of Cockpit. I just realized there’s no need to uninstall it first, so I’m removing that from the original post. @EliotBR I think there’s an opportunity here to improve the documentation on the extensions page side.

  5. I’m very, very glad you liked it. It’s been a long development, but we’ve been enjoying it a lot, the internal response to it has been great, and we are excited now to be sharing it with you. I predict an awesome year coming. With those feedbacks we are receiving from people like you, it’s much easier for us to go in the right direction and create a good product. We are the ones who need to thank you.

1 Like