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

    Voxl2 + M0041 RevB Battery Monitor on Arducopter

    Ask your questions right here!
    2
    11
    425
    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.
    • Eric KatzfeyE
      Eric Katzfey ModalAI Team @Dan Jennings
      last edited by

      @Dan-Jennings Which arducopter build are you using?

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

        @Dan-Jennings Rather than use voxl-inspect-battery have you tried QGC or Mission Planner or Mav Proxy?

        Dan JenningsD 1 Reply Last reply Reply Quote 0
        • Dan JenningsD
          Dan Jennings @Eric Katzfey
          last edited by

          @Eric-Katzfey
          We're on voxl-ardupilot 4.8.0-325875bb

          I've been connecting through mission planner, but have not been able to get any battery data. Looked through mavlink inspector and there is no battery_status topic.

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

            @Dan-Jennings I'd try our voxl-inspect-mavlink application. Check voxl-inspect-mavlink mavlink_onboard and voxl-inspect-mavlink mavlink_to_gcs and see if battery_status appears at all. I just loaded voxl-ardupilot_ArduCopter_4.8.0-94b27fd3_arm64.deb on my voxl2 with our standard APM and I see battery status in QGroundControl and with voxl-inspect-mavlink mavlink_to_gcs. Also, can you upgrade to VOXL SDK 1.6.x?

            Dan JenningsD 2 Replies Last reply Reply Quote 0
            • Dan JenningsD
              Dan Jennings @Eric Katzfey
              last edited by

              @Eric-Katzfey

              I don't see any battery_status message
              2eb6bb40-4283-4e6d-9acb-5d2873af8853-image.png

              1 Reply Last reply Reply Quote 0
              • Dan JenningsD
                Dan Jennings @Eric Katzfey
                last edited by

                @Eric-Katzfey
                We will look into updating the sdk, but that's always a fair bit of work.

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

                  @Dan-Jennings I'm also guessing that the driver may not be detecting the hardware so is not able to get the data for the battery_status. Have you tried swapping some other hardware to see if the problem is associated with a particular unit?

                  Dan JenningsD 1 Reply Last reply Reply Quote 0
                  • Dan JenningsD
                    Dan Jennings @Eric Katzfey
                    last edited by

                    @Eric-Katzfey I finally had an opportunity to try a different power board but we still do not have any battery_status topic. We will look at updating the SDK but don't want to derail our CV development doing so. I'd prefer to find a solution without having to do that.

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

                      @Dan-Jennings Honestly, I don't think updating the SDK version will help this issue. But, we highly encourage everyone to be on the latest SDK, regardless, since that's where you'll get the latest fixes and features. And it's how you'll get the best support from us. but in this case I don't think a newer SDK will get you the battery_status. It's probably a hardware issue or a parameter issue. You swapped boards and that didn't help. What about the cable? Those 4 wire cables are notoriously fragile. Can you swap it out and see if that helps? The other item is parameters. You saw that other post about setting BATT_MONITOR to 21 and BATT_I2C_BUS to 1. If you don't see the BATT_I2C_BUS parameter then it must mean that BATT_MONITOR hasn't been set to 21. Make sure it is set to 21, then reboot, then you should see the BATT_I2C_BUS parameter. Then set it to 1, reboot, then you should see correct battery_status.

                      Dan JenningsD 1 Reply Last reply Reply Quote 0
                      • Dan JenningsD
                        Dan Jennings @Eric Katzfey
                        last edited by

                        @Eric-Katzfey
                        I'm not sure what may have changed, before when setting BATT_MONITOR to 21 the param would write but we wouldn't get the additional parameters that that setting should have enabled. Last week I tried it again to reply to your last message and we got the BATT_I2C_BUS parameter and were able to get it all working. Gotta love when things seem to magically fix themselves, thanks for the support.

                        PS, we have built a parallel system on the latest SDK and will be migrating the current one over to match.

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