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

Pixhawk Cube_calibration issue on Master #12692

Closed
Tony3dr opened this issue Aug 13, 2019 · 11 comments
Closed

Pixhawk Cube_calibration issue on Master #12692

Tony3dr opened this issue Aug 13, 2019 · 11 comments
Assignees
Labels
bug Drivers 🔧 Sensors, Actuators, etc stale

Comments

@Tony3dr
Copy link

Tony3dr commented Aug 13, 2019

Describe the bug
When setting up the vehicle for a flight, on arming the vehicle I get a "Compass not found" message, see image below:
image
This issue is on Master e25db01 & PR Pull12650, tried on Stable version and was able to fly. v1.9.2 (1069058).
To Reproduce
Steps to reproduce the behavior:

  1. Power on the Drone
  2. Uploaded mission
  3. Arm vehicle and Takeoff
  4. Error, "Preflight Fail: COmpass trying to build PX4 Firmware on OSX 10.7 #2 uncalibrated"
  5. Calibrate vehicle
  6. Error message Gyro 1 no matching uORB devid
  7. Unable to calibrate the vehicle on Master
    image

Log Files
Compass not found and Calibration issue log on Master:
https://review.px4.io/plot_app?log=13cc9db5-4a03-41ff-a9e2-b80013d3e104

Stable v1.9.2 (1069058) log:
https://logs.px4.io/plot_app?log=71a782cc-7979-4ff1-a6e8-f3d8f4757f55

PR 12650 log issue:
https://review.px4.io/plot_app?log=18094d44-f808-4b67-b7d6-8ef0df7f4f05

**Drone **
Frame- DJI F450
Flight Controller: Pixhawk 2(The Cube)

@dagar we tried calibrating the vehicle and get an Error message Gyro 1 no matching uORB devid. On Stable version, we were able to arm, calibrate and fly the vehicle with no issues.

@dagar
Copy link
Member

dagar commented Aug 14, 2019

I believe this is a bug with the icm20948 driver, which up until recently was using an incorrect device id. I'll try to reproduce.

@proficnc
Copy link

So was this introduced bug fixed?

@darshanz
Copy link

darshanz commented Nov 13, 2019

Is it fixed yet??

Tried building the source for px4_fmu-v3_default and faced faced the same problem with latest v1.10.0-rc1.
Installing v1.10.0 Beta 4 using QGC also had the same problem.

Then, tried building v1.10.0-rc1 for another hardware with px4_fmu-v5_default, didn't face that problem though.

@FlavioTonelli
Copy link
Contributor

I'm facing a similar issue with Here2 compass on a pixhawk 4 board.
That seems to confirm the bug is related to ICM20948 driver.

@JacobCrabill
Copy link
Member

Is this pull request relevant?
#11189

@feemi
Copy link

feemi commented Dec 16, 2019

This issue still exists on pixhawk cube 2.1 fmu-v3 autopilot.

@FlavioTonelli
Copy link
Contributor

I can't reproduce anymore this issue on current stable version.
Tested on both Pixhawk v3 and v5 autopilot, equipped with an Here 2 antenna.
Is that been fixed?

@JacobCrabill
Copy link
Member

It's possible that this has been fixed by #14345, if the issue was in regards to external UAVCAN compasses.

@mrpollo
Copy link
Contributor

mrpollo commented Apr 6, 2020

@Tony3dr Can you please verify @JacobCrabill comment? it would be great to resolve/close this issue asap.

@stale
Copy link

stale bot commented Jul 5, 2020

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 Jul 5, 2020
@LorenzMeier
Copy link
Member

Solved a long time ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Drivers 🔧 Sensors, Actuators, etc stale
Projects
None yet
Development

No branches or pull requests

10 participants