Skip to content

[Bug] Power redundancy check status message too long for mavlink message #24737

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mtzm opened this issue Apr 19, 2025 · 0 comments · May be fixed by #24738
Open

[Bug] Power redundancy check status message too long for mavlink message #24737

mtzm opened this issue Apr 19, 2025 · 0 comments · May be fixed by #24738

Comments

@mtzm
Copy link

mtzm commented Apr 19, 2025

Describe the bug

The "Preflight Fail: Power redundancy not met: X instead of Y" is too long for a mavlink message and therefore broken up.
As QGroundControl doesn't call out messages that start with "Preflight Fail:" but rater shows them in the preflight checks panel, only the second part of the message is sometimes called out (I suppose this happens if the first mavlink message is lost).

To Reproduce

  1. Enable power redundancy check (ex. 2)
  2. Use a datalink that has some (small level) of packet loss
  3. disable one power supply
  4. wait long enough, an eventually you will get a callout "d of 2" which is the last part of "Preflight Fail: Power redundancy not met: 0 instead of 2"

Expected behavior

No response

Screenshot / Media

No response

Flight Log

No response

Software Version

No response

Flight controller

No response

Vehicle type

None

How are the different components wired up (including port information)

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant