ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    MAG SDA 3P3V shorted to ground

    VOXL 2 Mini
    2
    4
    17
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      cbay
      last edited by

      Been working with the VOXL2 Mini for awhile, communicating with I2C devices using QUP0 on J19. Today ran into an issue of communication and I2C probing failing, finally figured it out to be my SDA line being shorted by the VOXL. I tried different cables, different I2C devices and a seperate VOXL2 Mini, all of them had the SDA line shorted on one mini, and pulled high as is proper on the other.

      I see no visible damage on the voxl2 mini and nothing has happened that could've caused this. Any information would be greatly appreciated, specially as if this mini cant use that I2C bus anymore it is useless for our purposes.

      Cheers
      Carson

      C 1 Reply Last reply Reply Quote 0
      • C
        cbay @cbay
        last edited by

        @cbay Reflashing seems to have fixed it, so it isnt a hardware problem and is instead a firmware issue. I am loading custom drivers into voxl-px4, any clue how that can affect it

        C 1 Reply Last reply Reply Quote 0
        • C
          cbay @cbay
          last edited by

          @cbay This may be a stretch but I do think it has something to do with the difference between voxl-fpv-px4 and voxl-px4. Can someone explain the differences between them

          Eric KatzfeyE 1 Reply Last reply Reply Quote 0
          • Eric KatzfeyE
            Eric Katzfey ModalAI Team @cbay
            last edited by

            @cbay voxl-fpv-px4 is based on voxl-px4 but has some custom tuning code / parameters for our fpv drones that isn't in voxl-px4. So, it's kind of a superset. But there isn't anything related to low level i2c drivers so I have no idea how that could be causing this issue.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Powered by NodeBB | Contributors