You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: