[ ] Implement an automatic “safe mode”, that by default is on when armed
Basically for BlueOS-level pre-arm checks, since BlueOS can’t actually prevent arming
Should show indications of what is blocked when engaged
Things that should be blocked in safe mode:
Firmware flashing
2000
2019
BlueOS updates
Extensions installations
Vehicle Setup (configuration, failsafes, etc)
Loading parameter files
Setting reboot-required parameters
[ ] Add warnings for:
network interface changes
Mavlink Endpoints
speed tests
Rebooting (core and host os)
Accessing the File Browser
Downloading logs
Changing the vehicle type
2001
Warning dialog should have options for “disarm and do the thing”, “ignore and do the thing”, “don’t do the thing”, with a checkbox for “don’t warn me again” (with a configurable duration?)
[ ] Have the safe/unsafe state accessible from anywhere (BlueOS itself and extensions). Maybe an endpoint?
[ ] Allow dedicating some number of cores to the autopilot functionality
[ ] BlueOS could send status messages on the MAVLink stream when things get critical (throttling, temperature, cpu, disk, etc)
[ ] BlueOS could also send messages about temperature, storage, etc, to the MAVLink stream so Cockpit can show it to the pilot
2000
2019
2001