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

Unstable sensors cause Critical problem #8927

Closed
Ahrovan opened this issue Feb 20, 2018 · 16 comments
Closed

Unstable sensors cause Critical problem #8927

Ahrovan opened this issue Feb 20, 2018 · 16 comments
Assignees

Comments

@Ahrovan
Copy link

Ahrovan commented Feb 20, 2018

Bug Report

I used Pixhawk hardware's (listed below), but in Most of the time see "PREFLIGHT FAIL" message for MAG,GYRO,ACCEL and in one case cause crashed.

log uploaded (Pixhawk LITE 2.4.6)

[commander] PREFLIGHT FAIL: ACCEL #1 UNCALIBRATED
[commander] PREFLIGHT FAIL: GYRO #1 UNCALIBRATED
[commander] PREFLIGHT FAIL: MAG SENSORS INCONSISTENT
[commander] PREFLIGHT FAIL: MAG #1 UNCALIBRATED
  • All boards calibrated with USB cable, in some case with WiFi module

The hardware's list (all with PX4 Firmware v1.7.3 + gps module m8n):

  • Pixhawk 2.4.6 (maybe 3DR original version)
  • Pixhawk 2.4.6 (Copy version)
  • Pixhawk LITE 2.4.6
@LorenzMeier
Copy link
Member

@dagar Is this related to the open detection PR?

@Ahrovan
Copy link
Author

Ahrovan commented Feb 20, 2018

@LorenzMeier Probably a mistake occurred in your reply :)

@LorenzMeier
Copy link
Member

No it's not.

@Ahrovan
Copy link
Author

Ahrovan commented Feb 21, 2018

@dagar @LorenzMeier What is your opinion about this problem? Do you need more information for troubleshooting? I try with another pixhawk and send log file today (and I'll check #8475)

@dagar
Copy link
Member

dagar commented Feb 21, 2018

@Ahrovan it's possible your issue is related to #8703, #8643. I've discussed with @davids5 and have a potential fix to implement and test later tonight.

Could you expand on exactly what you did? When did you calibrate relative to flashing? How are you powering the pixhawk? Did you command a restart from QGroundControl (including selecting an airframe) or the reboot command in nuttx?

@dagar dagar self-assigned this Feb 21, 2018
@dagar dagar added the bug label Feb 21, 2018
@dagar
Copy link
Member

dagar commented Mar 14, 2018

Could you try #9074?

@Ahrovan
Copy link
Author

Ahrovan commented Dec 18, 2018

@dagar The problem persists with the latest version (v1.8.2 Stable Release)

@stale
Copy link

stale bot commented Mar 18, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@hansbonini
Copy link

Same problem on 1.9-dev

@stale stale bot removed the Admin: Wont fix label Mar 27, 2019
@stale
Copy link

stale bot commented Jun 25, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Jul 9, 2019

Closing as stale.

@stale stale bot closed this as completed Jul 9, 2019
@julianoes
Copy link
Contributor

@hansbonini and @Ahrovan could you answer to this:

Could you expand on exactly what you did? When did you calibrate relative to flashing? How are you powering the pixhawk? Did you command a restart from QGroundControl (including selecting an airframe) or the reboot command in nuttx?

And can you try latest master?

@julianoes julianoes reopened this Jul 10, 2019
@stale stale bot removed the Admin: Wont fix label Jul 10, 2019
@stale
Copy link

stale bot commented Oct 8, 2019

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

@stale stale bot added the stale label Oct 8, 2019
@julianoes
Copy link
Contributor

Closing because no one followed up.

@Ahrovan
Copy link
Author

Ahrovan commented Oct 8, 2019

I'm a follower. But there is no feedback from developers

@hamishwillee
Copy link
Contributor

@Ahrovan This request was waiting on a response here from you or @hansbonini:
#8927 (comment)

If you're happy to act as the stakeholder on the reporter side (?) I'm sure @julianoes is more than happy to reopen and continue investigation

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

No branches or pull requests

6 participants