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

MAX30010 issues when connected to PaHub #324

Open
YonatanAmir1996 opened this issue Dec 15, 2023 · 4 comments
Open

MAX30010 issues when connected to PaHub #324

YonatanAmir1996 opened this issue Dec 15, 2023 · 4 comments

Comments

@YonatanAmir1996
Copy link

Hi, In case of multiple I2C devices which one of them is MAX30010, making issues with MAX30010 device, such that the results are invalid, note that the I2C addresses between devices are different.

@felmue
Copy link
Contributor

felmue commented Dec 25, 2023

Hello @YonatanAmir1996

what are the I2C addresses of all the I2C devices you have connected? Note: If they are all different, then there is no need for a PaHub - you could simple connect them all directly to the core.

Thanks
Felix

@YonatanAmir1996
Copy link
Author

There is one I2C device which has the same address, but anyway, physically the max30100 can't be connected in a middle of row. Is there an alternative or changes needed to be done in MAX30100 API code?

@felmue
Copy link
Contributor

felmue commented Jan 1, 2024

Hello @YonatanAmir1996

I do not have a max30100 - so I cannot try myself whether it should work through PaHub or not. Sorry.

Thanks
Felix

@Tinyu-Zhao
Copy link
Collaborator

Are you using Unit Heart?

@Tinyu-Zhao Tinyu-Zhao transferred this issue from m5stack/M5CoreS3 Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants