ES-Alexander

#1778 was merged a while ago, so closing. Please comment if the issue is not actually fixed, and we can re-open and try to investigate as relevant.

I don't see why performing dead-zone calibration would be any more complex on a chart showing a red, expanding obviously "off" output region vs on a bar showing nothing in...

Is this a duplicate of #1389, or is it evidence that original issue has been partially resolved?

> I think there was an issue for it, but I cant find it Possibly #2792?

That could potentially cause support issues. I think a preferable approach would be to support two fallbacks, one that's user-specified, and one that was installed by BR, as discussed [here](https://github.com/bluerobotics/BlueOS-docker/issues/1041#issuecomment-1429133078).

Hi @RakshithaMH24, welcome to the community! :-) I'm unsure on what's most beginner friendly at the moment, but to get a sense of things that have been requested you can...

This is based on [quite weird naming of things](https://github.com/ArduPilot/ardupilot/pull/14159), and some tenuous logic. It should be possible to set the measurement noise without adjusting the parameter (to avoid persistent changes...

#2063 presumably needs to be resolved first.

Relevant to #2168 and #1868. I think this meshes well with the idea of a more general "ViewDo" mini-widget, which I think is the best way forward for our general...

I think output should be preemptively disabled for a couple of seconds at startup, during which the presence of [`MANUAL_CONTROL`](https://mavlink.io/en/messages/common.html#MANUAL_CONTROL), [`RC_CHANNELS_OVERRIDE`](https://mavlink.io/en/messages/common.html#RC_CHANNELS_OVERRIDE), [`RC_CHANNELS`](https://mavlink.io/en/messages/common.html#RC_CHANNELS), and [`HIL_RC_INPUTS_RAW`](https://mavlink.io/en/messages/common.html#HIL_RC_INPUTS_RAW) messages should be checked for, and...