Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Driver won't connect to Gazebo simulated drone #65

Closed
ciaran-helgen opened this issue Jan 12, 2022 · 2 comments
Closed

Driver won't connect to Gazebo simulated drone #65

ciaran-helgen opened this issue Jan 12, 2022 · 2 comments

Comments

@ciaran-helgen
Copy link

When launching the sample Gazebo sim with ros2 launch tello_gazebo simple_launch.py and the driver with ros2 launch tello_driver teleop_launch.py then running ros2 service call /tello_action tello_msgs/TelloAction "{cmd: 'takeoff'}" to arm the drone, the response from the driver is always [tello_driver]: Not connected, dropping 'takeoff'
From the code I can see this is the warning that occurs when the state socket or video socket are not receiving data. When no command is sent, a [tello_driver]: Command timed out error is printed at regular intervals, which indicates no connection.
Any insight as to what might be wrong?
I am running this in Docker if that is relevant

@ciaran-helgen
Copy link
Author

It works if I don't load the driver per your response here #47 (comment)
My bad!

@ciaran-helgen
Copy link
Author

I was leaving out the drone1 namespace. The call should have been ros2 service call /drone1/tello_action tello_msgs/TelloAction "{cmd: 'takeoff'}"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant