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

System is arming (or thinks it is arming) even with Critical warnings (specifically "MAG SENSORS INCONSISTENT") #9155

Closed
Antiheavy opened this issue Mar 25, 2018 · 6 comments · Fixed by #9193
Assignees
Labels

Comments

@Antiheavy
Copy link
Contributor

Antiheavy commented Mar 25, 2018

PX4 1.7.3, installed on a Pixracer, using QGC v3.3.0. The pixracer is sitting on my desk connected to QGC over USB. I have a valid GPS fix. I try to Arm and it seems to let me even with the following Critical warnings:

image
image

Is this right?

@Antiheavy
Copy link
Contributor Author

however, once i fixed the compass rotation problem (that was giving the "MAG SENSORS INCONSISTENT" warning), then the system properly prevents arming:
image

@Antiheavy Antiheavy changed the title System is arming (or thinks it is arming) even with Critical warnings System is arming (or thinks it is arming) even with Critical warnings (specifically "MAG SENSORS INCONSISTENT") Mar 25, 2018
@dagar dagar self-assigned this Mar 25, 2018
@dagar dagar added the bug label Mar 25, 2018
dagar added a commit that referenced this issue Mar 26, 2018
@dagar
Copy link
Member

dagar commented Mar 26, 2018

Working on a fix here - https:/PX4/Firmware/tree/pr-commander_preflight

dagar added a commit that referenced this issue Mar 27, 2018
@taileron
Copy link
Contributor

taileron commented Mar 27, 2018

I think it´s not so bad to allow arming for stabilized flights and reject only e.g. positopn, auto mission or rtl that is directly dependent on the sensor´s errors

@dagar
Copy link
Member

dagar commented Mar 27, 2018

@taileron I agree, but it needs to be done explicitly and I'm not entirely sure how we'd want to go about that.

Some of these requirements we could determine from the system configuration. For example if the user has and RC or data link loss failsafe configured for RTL then at arming time the system could require a valid global position estimate and valid home position.

dagar added a commit that referenced this issue Mar 27, 2018
@taileron
Copy link
Contributor

taileron commented Mar 27, 2018

@dagar some errors disappear when the fc runs a minute but mostly it is necessary to reboot the system to get rid of conditions that could prevent arming.
so what´s about to have the possibility or do it automatic at the attempt of arming: repeat the preflight check after 40 ... 120 sec when temperatures and reference voltages are more stable and more gps satellites than directly after boot, deleting all previous preflight errors + nsh "commander check" with current sensor values

@dagar
Copy link
Member

dagar commented Mar 30, 2018

Immediate fix in #9193.

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