Skip to content
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

change mavlink_log from critical to info for battery state #14377

Closed
wants to merge 2 commits into from

Conversation

DanielePettenuzzo
Copy link
Contributor

This is only for BATTERY_WARNING_LOW and BATTERY_WARNING_CRITICAL states. BATTERY_WARNING_EMERGENCY stays the same for now since we don't have any better way of showing this in QGC.

…BATTERY_WARNING_CRITICAL states. BATTERY_WARNING_EMERGENCY stays the same for now.
Copy link
Member

@bkueng bkueng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide the explanation why you want to change it?
Preferably the QGC UI should also already be updated before this goes in.

@DanielePettenuzzo
Copy link
Contributor Author

The main reason is that we don't want it to show up as a warning in the log file. I guess we can wait for proper UI to be implemented on the QGC side before getting it in.

…rgency

When this happens very likely the user had a crash so we should flag it
as an error and not just warning.
@TSC21 TSC21 requested a review from bkueng April 4, 2020 08:12
@TSC21
Copy link
Member

TSC21 commented Apr 4, 2020

@DanielePettenuzzo can yoi rebase?

@stale
Copy link

stale bot commented Jul 3, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@LorenzMeier
Copy link
Member

I'm closing this as stale.

@LorenzMeier LorenzMeier deleted the pr-change-battery-warning-messages branch January 31, 2021 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants