ES-Alexander

Record MAVLink telemetry in a `.tlog` file

7

This is generally expected functionality for control station software, and provides some data security in the case of a lost vehicle. Not sure how hard it is to continuously write...

frontend: make a unified container widget

1

### Current behaviour We have separate implementations for nearly identical feature sets, and several issues that are unique to one of the container types (so there's extra to test, and...

### Bug description ### Steps to reproduce 1. Add a slider to the top-bar 2. Move it 3. The value indicator is clipped off the top ### Primary pain point(s)...

wizard: subtitle config appears on top of the wizard

1

### Bug description ### Steps to reproduce 1. Start the wizard 2. Click through until at the subtitle configuration screen 3. The subtitle config cannot be interacted with 4. The...

Add viewer for 3D models and scenes

1

Useful for things like - showing the current vehicle attitude - this could use the vehicle's active model when using BlueOS, and could likely make use of @Williangalvani's model viewing...

Joystick: allow axis protocol configuration

5

Currently we forcibly send MAVLink `MANUAL_CONTROL` messages at a fixed rate, even though many vehicles don't support them, and some users may wish to change the frequency. It would be...

joystick: indicate expected motion axes for axis names

1

### Current behaviour Axis inputs can be assigned to [Manual Control](https://mavlink.io/en/services/manual_control.html) axes, which have single-letter names and behaviour that's dependent on the firmware of the vehicle's autopilot. This is [causing](https://discuss.bluerobotics.com/t/is-custom-dynamic-axis-switching-possible/12459/15)...

### Current behaviour The setting needs to be manually pulled and processed by individual widgets, and cannot be readily accessed in user-created variables, Actions, or components. ### Expected or desired...

### Bug description Cockpit only [defines](https://github.com/bluerobotics/cockpit/blob/master/src/libs/joystick/protocols/mavlink-manual-control.ts#L27) the set of button functions and parameter names [used by ArduSub](https://mavlink.io/en/services/manual_control.html#mapping-buttons), but it provides them for selection to any connected vehicle, regardless of firmware...

### Current behaviour We currently support gamepad controller configuration, which allows Cockpit to process user input into a combination of MAVLink commands sent directly to the autopilot, Actions to control...