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

[Feature Request]: Support hmc5883l & qmc5883l #596

Open
unbelauscht opened this issue Mar 21, 2024 · 2 comments
Open

[Feature Request]: Support hmc5883l & qmc5883l #596

unbelauscht opened this issue Mar 21, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@unbelauscht
Copy link

unbelauscht commented Mar 21, 2024

Platform

ESP32

Description

Supporting hmc5883l & qmc5883l modules would provide accurate compass data for heading vs buggy GPS calculated heading.

EDIT: I can find hmc & qmc mentions in the code, but it's not clear how to attach a module and how to enable it.

@unbelauscht unbelauscht added the enhancement New feature or request label Mar 21, 2024
@garethhcoleman
Copy link
Contributor

garethhcoleman commented Apr 11, 2024

I can see that QMC5883L has some mentions in the code as a telemetry sensor but it isn't coded in a telemetry module or listed as supported here. Recently @caveman99 made this comment about telemetry for an accelerometer that I think is relevant to your request "We only support slow-changing data or data with is averaged over time. Use cases for this type of sensor is heading while stationary (add-on to position module)".

@fifieldt
Copy link
Contributor

@dhskinner is working on accelerometer support which should be helpful for compasses
meshtastic/firmware#4662

for now, a QMC5883L will be detected if plugged in by I2C, but nothing much will happen with it.

@thebentern thebentern transferred this issue from meshtastic/firmware Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants