Skip to content

MAX30010 issues when connected to PaHub #324

Open

Description

@YonatanAmir1996

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.

Activity

  1. felmue commented on Dec 25, 2023

    @felmue
    Contributor

    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

  2. YonatanAmir1996 commented on Dec 30, 2023

    @YonatanAmir1996
    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?

  3. felmue commented on Jan 1, 2024

    @felmue
    Contributor

    Hello @YonatanAmir1996

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

    Thanks
    Felix

  4. TinyuZhao commented on Jun 7, 2024

    @TinyuZhao
    Member

    Are you using Unit Heart?

  5. transferred this issue fromm5stack/M5CoreS3on Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions