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

    Unable to bind controller anymore to Starling V2

    Starling & Starling 2
    3
    11
    310
    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.
    • M
      mario
      last edited by

      I'm not able anymore to bind the controller that comes with the Starling V2.

      I've done multiple power cycles of the drone and controller, and ran the voxl-elrs --unbind and voxl-elrs --bind commands and go through the binding process, which used to work to rebind the joystick, but I'm no longer able to.

      I then tried to reflash the receiver as per https://docs.modalai.com/voxl-elrs/#recovering-a-bricked-receiver, but still can't get the joystick to bind.

      Any further suggestions to try?

      tomT 1 Reply Last reply Reply Quote 0
      • tomT
        tom admin @mario
        last edited by

        @mario Have you tried using the button on the receiver itself in order to put it into binding mode?

        M 4 Replies Last reply Reply Quote 0
        • M
          mario @tom
          last edited by

          @tom, can you elaborate which button on the ELRS receiver you are talking about? You mean the power on/off cycling button? Is there a way to press it such that it binds to the controller?

          1 Reply Last reply Reply Quote 0
          • M
            mario @tom
            last edited by

            @tom, in other words, aside from these docs https://docs.modalai.com/voxl-elrs/, where are these instructions that refer to using a button on the ELRS receiver to bind?

            Jainik MehtaJ 1 Reply Last reply Reply Quote 0
            • M
              mario @tom
              last edited by

              @tom, one more question, we're trying to run /usr/share/modalai/voxl-elrs/tools/debug.py to try to see the logs, but the code doesn't seem to work.

              For example, it looks for dev.port = '/dev/tty-slpi-7', but we can't find that file, so is this debug.py actually the right code to use?

              Also, this error message is returned, even on a drone that is working correctly that binds to the controller.

              ERROR: voxl_uart_read_bytes: Bus '17' is not initialized

              PS, regarding the original post, unbinding and flashing did work, we can see the LED changes, etc, and messages from the drone

              1 Reply Last reply Reply Quote 0
              • Jainik MehtaJ
                Jainik Mehta @mario
                last edited by

                @mario Were you able to bind the controller to the drone? I think I have the same problem with my starling 2 drone. I assume you also have ORQA controller like me. Are you seeing constant green LED on drone when you turn it on?

                M 1 Reply Last reply Reply Quote 0
                • M
                  mario @Jainik Mehta
                  last edited by

                  @Jainik-Mehta I have a Commando controller, and yes, all the LEDs on the drone operate as expected

                  1 Reply Last reply Reply Quote 0
                  • M
                    mario @tom
                    last edited by

                    @tom, just checking to see if you had any further thoughts on this.

                    tomT 1 Reply Last reply Reply Quote 0
                    • tomT
                      tom admin @mario
                      last edited by

                      @mario There should be only physical button on the receiver itself, pressing and holding it for a couple seconds within 30 seconds of powering on should put it into bind mode

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        mario @tom
                        last edited by

                        @tom, when that happens, does the LED do the "blink-blink-pause-blink-blink-pause..." sequence, i.e. the sequence listed here under "Binding mode enabled": https://www.expresslrs.org/quick-start/led-status/.

                        That's the same mode I get when I do voxl-elrs --bind, so is there a difference between doing it via the command vs doing it by holding down that button?

                        tomT 1 Reply Last reply Reply Quote 0
                        • tomT
                          tom admin @mario
                          last edited by

                          @mario Should be the same, if you're seeing that LED pattern then binding mode has started correctly

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