HUD/PrearmStatus: fix failure messages #3250
Conversation
robertlong13
force-pushed
the
pr/prearm_stale_msg
branch
from
5d61601
to
60c19e5
Compare
|
@meee1 another simple bug fix PR when you get a chance |
|
Basically, as soon as you land, and get a prearm failure for still being in the landing sequence, you'll briefly get something like "accels unhealthy" or "IMU temperature low" on the HUD, which wasn't true. That was leading to some errant support questions. |
When prearm checks are failing, the HUD displays the last failure message, even if that message is very stale. This changes it so it displays the latest failure message since the last time it passed the prearm check. The prearm failure messages were also moved to the lowest priority, so that they would not mask other sensor failures. The PrearmStatus window had a similar problem, where it would show all failure messages briefly when it first launched, instead of the latest relevant ones. Also, a drive-by fix of where the messageHigh setter function sets the _messageHighTime variable, which was causing flickers.
robertlong13
force-pushed
the
pr/prearm_stale_msg
branch
from
60c19e5
to
8e21277
Compare
|
Here's a tlog I created so you can reproduce the behavior I'm talking about and test that the PR fixes it. Right after landing, the HUD pops up a "PreArm: Gyros inconsistent", even though the real reason it's failing is that you are in a landing sequence and are in AUTO without the next command being a takeoff. Try replaying this log on master and with this PR to see what I mean. What it says after the flight Why it's actually failing prearm The idea behind my fix is that there's no reason to assume that the current reason for not-ready-to-arm has anything to do with any previous one. This is especially true if the last case was several minutes or hours ago, but I think it's best to only display prearm failure messages that have come in since the prearm status went red. This is a very common thing I have to explain to people |
When prearm checks are failing, the HUD displays the last failure message, even if that message is very stale. This changes it so it displays the latest failure message since the last time it passed the prearm check. The prearm failure messages were also moved to the lowest priority, so that they would not mask other sensor failures.
The PrearmStatus window had a similar problem, where it would show all failure messages briefly when it first launched, instead of the latest relevant ones.
Also, a drive-by fix of where the messageHigh setter function sets the _messageHighTime variable, which was causing flickers.