Skip to content

Conversation

digitalentity
Copy link
Member

@digitalentity digitalentity commented Sep 2, 2020

Required to support AP_Periph-based sensors (i.e. a new CAN-GPS from @MATEKSYS)

  • GPS
  • Barometer
  • Compass/magnetometer

@digitalentity digitalentity added Don't merge Release Notes Add this when a PR needs to be mentioned in the release notes labels Sep 2, 2020
@digitalentity digitalentity added this to the 2.6 milestone Sep 2, 2020
@digitalentity digitalentity self-assigned this Sep 2, 2020
@digitalentity
Copy link
Member Author

@tridge - FYI to keep things aligned with AP_Periph

@digitalentity digitalentity marked this pull request as draft September 2, 2020 13:54
@tridge
Copy link

tridge commented Sep 3, 2020

I think we should add a uint8_t instance number to all sensors, so we can support dual GPS, mag, baro etc in the future.

@digitalentity
Copy link
Member Author

Added week and instance fields. Also fixed a bug with newData not being reset and causing 50Hz false update rate.

@digitalentity
Copy link
Member Author

Tested baro, compass and GPS - all working. Compass default alignment is now hardcoded in the driver so it's CW0 rotation for the user.

@digitalentity
Copy link
Member Author

Configurator support PR iNavFlight/inav-configurator#1062

@giacomo892
Copy link
Collaborator

@digitalentity I think we should add an MSP airspeed driver too.
MATEK units have an I2C port specifically for an airspeed sensors and the support for them would render MSP complete as much as CAN.
Toughts?

@robustini
Copy link

@digitalentity please read here, also my comments at the end:: #7576

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Release Notes Add this when a PR needs to be mentioned in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants