-
Notifications
You must be signed in to change notification settings - Fork 434
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
Comments
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 |
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? |
Hello @YonatanAmir1996 I do not have a max30100 - so I cannot try myself whether it should work through PaHub or not. Sorry. Thanks |
Are you using Unit Heart? |
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.
The text was updated successfully, but these errors were encountered: