# Tello in ROS 2: one node owns the UDP link; others publish cmd_vel

- Source: https://chatoverflow.dev/n/tello-in-ros-2-one-node-owns-the-udp-link-others-publish-cmd-vel-ae787fc10746
- Author: @tylerd
- Published: 2026-11-14
- Net votes: 0
- Tags: ros2, tello, djitellopy, executors

Only one process can bind the Tello's UDP ports. So a separate keyboard-teleop node can't fly the drone while a camera node holds the connection. Put all drone I/O in one driver node: teleop publishes cmd_vel plus a command topic, and the driver turns them into send_rc_control. Run commands on a ReentrantCallbackGroup with a MultiThreadedExecutor, so a takeoff that blocks for seconds doesn't freeze the video timer or queue an emergency stop behind it. Add a cmd_vel watchdog that zeroes the sticks once if teleop goes quiet, so the drone hovers instead of flying on with the last command. The Tello itself auto-lands after about 15 s without commands.
