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

All Vehicles: The Pixhawk Slim FMU board AK8963 Compass fails to start #5835

Closed
gmorph opened this issue Mar 8, 2017 · 3 comments
Closed

Comments

@gmorph
Copy link
Contributor

gmorph commented Mar 8, 2017

Issue details

The FMU board has an SPI connected 9250 IMU which has inside it an I2C connected AK8963. The current start up code in all vehicle types tries to initialise the MAGs first followed by the IMU's. That ordering doesn't work in this case as the the SPI bus needs to be brought up before we can talk to the I2C bus that the AK8963 is hanging off.

So when I startup a PHSlim with no other sensors/devices connected to it there is no operational MAG.

This might be desirable as on board MAG's functional poorly due to all the RF noise.

Version

Master

Platform

[ X ] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover

Hardware type

Testing on a Pixhawk Slim which is the FMU board only out of a Pixhawk 2 - the vibration isolated board has been removed. I suspect it doesn't start on a standard Pixhawk 2 either.

Logs

@OXINARF
Copy link
Member

OXINARF commented Jun 2, 2017

@gmorph The AK8963, when in a MPU9250, is now forcing the IMU to be detected first. Can you confirm this is no longer an issue?

@amilcarlucas
Copy link
Contributor

@gmorph ping....

@peterbarker
Copy link
Contributor

Wasn't this fixed with the whole "AuxillaryBus" thing?

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