Navigation

    Robolink logo
    • Register
    • Login
    • Search
    • [[global:header.categories]]
    • [[global:header.recent]]
    • [[global:header.tags]]
    • [[global:header.popular]]
    • [[global:header.users]]
    • [[global:header.groups]]
    As of September 2021, we have moved technical support to Robolink Help

    Welcome to the Robolink Community forum!

    You can post here to interact with others in the Robolink community. We're checking it weekly, and we'll respond to some messages. If you're looking for technical support, head over to Robolink Help.

    Codrone Pairing but always showing battery 0% after failed firmware update

    CoDrone Troubleshooting
    2
    4
    2530
    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.
    • J
      jarthur1222 last edited by

      While trying to update the firmware through the petrone app, the update crashed. Since then, I can pair with the drone, but it always shows a battery at 0%. I have paired through blockly, snap, and python. All pair but give the exact same results on the battery. I just got the unit in last Wednesday, so I don't think the battery is bad yet.

      I have a demo for investors tomorrow, I need this up and working asap.

      1 Reply Last reply Reply Quote 0
      • robolink_leila
        robolink_leila last edited by

        @jarthur1222 Glad to hear it's resolved!

        1 Reply Last reply Reply Quote 0
        • J
          jarthur1222 last edited by

          Battery was fine. I tried the update on an android version on PETRONE app and it resolved the problem. This issue was with trying the update on the iPad.

          1 Reply Last reply Reply Quote 0
          • robolink_leila
            robolink_leila last edited by

            @jarthur1222 ,
            After letting the battery charge fully, try doing a calibration test. If it's flying, it might be a bug, but it may be something else.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post