-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Fix the case where the flight controller is connected to the battery (charge 100), QGC shows no battery #15306
Conversation
…(charge 100), QGC shows no battery
I'm not sure that I'm following the logic correctly. Why is this happening at 100? What does |
Hi, @CUAVcaijie I think this is the same (or similar) problem that I have faced. Furthermore, in my case, I tried to use 1 of regular PM and 1 of CANPMU at the same time for redundancy. I solved the problem by changing battery remaining of CANPMU to 1 ( in sensors/battery.cpp), then the system will choose the lowest one to make decisions about arm or disarm. It is temporarily fixed. |
Because CUAV CAN PMU is not a smart battery, it cannot provide accurate remaining power |
@dagar Do you have any other questions? |
@dagar How about this? |
@dagar How about this? |
@dagar How about this? |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
I've rebased this: #16591 |
thank you |
I use the CAN PMU to power the CUAVv5+. When the CAN PMU reaches 100, the QGC shows no battery .
It was found that MAVLINK SYS_STATUS selected the first group of unconnected battery status. Instead of the actual battery status behind