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.

    SOLVED Tips to Aid in Debugging CoDrone Movement

    Educators Corner
    3
    4
    4633
    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
      johnnytechknow last edited by

      I have been working on the point to point challenge and am losing track of which movement code I need to adjust or change.

      Can you suggest a way to make debugging CoDrone movement coding a bit easier? In addition to using comments in the code can the controller board produce a sound triggered by code before a section of code is run as a marker of some kind? Could this be done coding LEDs on the remote or on the CoDrone itself?

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

        @johnnytechknow I think that @robolink_arnold can answer this more effectively, but one of the things he often teaches in his classes is to use beeps as markers for notifying where you are in the code. I've listed an example of doing a series of beeps right here:

        CoDrone.Buzz(4000, 10);
        CoDrone.Buzz(8000, 10);
        CoDrone.Buzz(2000, 2);
        CoDrone.Buzz(4000, 10);
        CoDrone.Buzz(8000, 10);
        

        The parameters are (tone, length)

        We recommend this technique to the kids in our classes as well, it's a great debugging tool. I like to put it in my setup as a way to beep to confirm connection was established, and as a way to signal when I've activated the emergency stop.

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

          @johnnytechknow Definitely add buzzers for debugging. Especially use them inside of if statements to verify where the drone is in the code.

          1 Reply Last reply Reply Quote 1
          • robolink_wes
            robolink_wes last edited by

            Here's the tutorial on how to use Buzzers.

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

              @johnnytechknow I think that @robolink_arnold can answer this more effectively, but one of the things he often teaches in his classes is to use beeps as markers for notifying where you are in the code. I've listed an example of doing a series of beeps right here:

              CoDrone.Buzz(4000, 10);
              CoDrone.Buzz(8000, 10);
              CoDrone.Buzz(2000, 2);
              CoDrone.Buzz(4000, 10);
              CoDrone.Buzz(8000, 10);
              

              The parameters are (tone, length)

              We recommend this technique to the kids in our classes as well, it's a great debugging tool. I like to put it in my setup as a way to beep to confirm connection was established, and as a way to signal when I've activated the emergency stop.

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