The idea at the moment is to make posts here when new beta versions get released, listing out the main features that would benefit from some extra eyes, and then spin those off into separate threads once each set of betas gets compiled into a stable release.
If you’re interested in helping with Cockpit beta testing (or just seeing more of how our software gets developed) you can turn on notifications for this thread, and it will be kept to just relevant testing and development discussion for the latest in-progress release.
New mode selection joystick button functions available per vehicle type (#2313)
Mode switching for non-ArduSub autopilot firmware no longer requires using the mode switcher dropdown widget if a joystick is connected
3. Web-socket connections for data-lake input
It is now possible to connect Cockpit to generic web-sockets to receive data (#2383)
Data can be sent from services onboard the vehicle, on the control station computer, or elsewhere on the network, without needing to go through MAVLink
4. Mission planning and the map widget
New button (bottom right) to switch between flight and mission planning modes (#2294)
The selected map tile provider is now remembered between sessions (#2267)
The last map display is now remembered between sessions ( #2261)
Mission waypoints that have been reached now change colour (#2343)
Mission waypoints no longer get misaligned by zooming (#2289)
Survey polygon corners can now have their coordinates set numerically (#2319)
Survey path generation now avoids some unnecessary sharp angles (#2290)
Various other UI fixes
5. PX4 autopilot firmware can now be connected to Cockpit
Once we’re in the release candidate stage I will post our list of standard release tests, for anyone who wants to confirm Cockpit’s general feature list still works as expected for them.
Love it @EliotBR !
Piling on with some testing notes related to vehicle configuration management. Earlier versions of Cockpit got us all familiar with this familiar warning:
This is resolved with Beta 18 version of Cockpit - however the solution is still a work in progress. It currently relies on timestamps, and for the moment different vehicles having different IP addresses to switch between profiles automatically. As I use many vehicles when testing, but they all have the same IP address (on their ethernet interface BROV2 or BlueBoat, we’re consistent with default of 192.168.2.2), it isn’t quite working… but for most users I don’t expect this is as much of an issue!
The settings synchronisation / conflict resolution is the only listed “major” point, and is the first poll option. Were you wanting a split out option for testing it with multiple vehicles or something?
@EliotBR - Oops!
I guess I’m hoping we get more feedback on the setting sync features from users like me that have many different vehicles that they use across at least 2-3 computers… haha!
Click a topic for the context and testing details
.