# Unable to bind controller anymore to Starling V2

Source: https://forum.modalai.com/topic/3930/unable-to-bind-controller-anymore-to-starling-v2
Category: Development Drones (https://forum.modalai.com/category/44/development-drones)
Tags: starling
Posted: 2024-11-12 20:19:20 UTC by mario
Replies: 10 · Views: 1493

## mario · 2024-11-12 20:19:20 UTC

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?

## Reply by tom (ModalAI staff) · 2024-11-12 21:25:02 UTC

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

## Reply by mario · 2024-11-13 15:58:51 UTC (in reply to tom)

@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?

## Reply by mario · 2024-11-13 16:01:47 UTC (in reply to tom)

@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?

## Reply by mario · 2024-11-13 17:33:45 UTC (in reply to tom)

@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

## Reply by Jainik Mehta · 2024-11-13 20:31:46 UTC (in reply to mario)

@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?

## Reply by mario · 2024-11-13 20:37:16 UTC (in reply to Jainik Mehta)

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

## Reply by mario · 2024-11-18 16:28:55 UTC (in reply to tom)

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

## Reply by tom (ModalAI staff) · 2024-11-18 19:32:16 UTC (in reply to mario)

@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

## Reply by mario · 2024-11-18 22:47:45 UTC (in reply to tom)

@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?

## Reply by tom (ModalAI staff) · 2024-11-18 22:54:35 UTC (in reply to mario)

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