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

Could not calibrate magnetometer on BeagleBone Blue #12516

Closed
silentjet opened this issue Jul 18, 2019 · 3 comments
Closed

Could not calibrate magnetometer on BeagleBone Blue #12516

silentjet opened this issue Jul 18, 2019 · 3 comments
Labels

Comments

@silentjet
Copy link

silentjet commented Jul 18, 2019

Describe the bug
Could not calibrate sensors (mag, accel, gyro) on BeagleBone Blue board.
Every calibration ends up with several timeout error messages.
When installing the board to the actual frame of the drone, it is almost impossible to fly due to the huge instability and constant jerking.

To Reproduce
Steps to reproduce the behavior:

  1. Board powered up
  2. px4 service is started manually by using the following command:
sudo build/beaglebone_blue_native/bin/px4 -s posix-configs/bbblue/px4.config
  1. By using WiFi QGC connects to the px4
  2. Starting calibration of the compass or gyro from Sensors menu
  3. Calibration failed with a timeouts

Expected behavior
Calibration succeed. Drone behaves stable when in the air.

Log Files and Screenshots
calibration_console_log.txt
calibration_qgc_view

Drone (please complete the following information):

  • standard quad 450

Additional context
OS: Debian for BeagleBone family
Kernel: 4.14.71-ti-rt-r80

@julianoes
Copy link
Contributor

Just FYI, I'm not aware of anyone currently using PX4 on the BeagleBone Blue, so you'll probably have to fix these things yourself.

@julianoes
Copy link
Contributor

Also, the plan is to deprecate the DriverFramework at some point which would mean some changes for the BBB coming up. On the flipside this would then make thinks like calibration consistent again and prevent these sorts of issues.

@stale
Copy link

stale bot commented Oct 17, 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 17, 2019
@bresch bresch closed this as completed Aug 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants