How to debug a crashed disabled widget
A disabled widget usually has 2 causes:
- OpenTX killed the widget because it was using too much time (CPU KILL)
- the widget crashed because of a Lua runtime exception
To get some insight on why a widget is showing as disabled do the following steps:
Long press [Tele]
Page to the screen that holds the widget and select "Setup widgets"
Short press [Encoder] and select "Widget settings"
this is the error that caused the widget to crash:
- Passthrough protocol specs
- Screen Layout
- Display GPS coordinates on Taranis radios
- Feature list
- Sensor discovery
- How to display additional sensors on screen
- Flight modes
- Voltage sources
- Battery configurations
- Airspeed vs Groundspeed
- Alerts
- Telemetry reset
- Telemetry logging to SD
- MavToPT support
- Supported Radios
- Installation on BW LCD radios running OpenTX/EdgeTX
- Installation on Color LCD radios running OpenTX/EdgeTX
- Installation on Color LCD radios running Ethos
- CRSF and ExpressLRS support
- Ardupilot Hardware requirements
- Ardupilot Configuration
- Google Maps configuration
- GMAPCatcher Maps configuration
- QGIS Maps configuration
- Maps Zoom control
- Plotting telemetry values on OpenTX/EdgeTX
- Configuration menu
- Sound files customization
