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

Can't control the Go1 Edu with ROS #18

Closed
Taucrates opened this issue Feb 25, 2022 · 1 comment
Closed

Can't control the Go1 Edu with ROS #18

Taucrates opened this issue Feb 25, 2022 · 1 comment

Comments

@Taucrates
Copy link

Hi,

We are trying to control the robot Unitree Go1 Edu using ROS. We've installed all packages and have a successful connection with the rosmaster executed on the Raspberry Pi of the robot. We can receive and send ROS messages from the robot to our PC and vice versa. The thing is that following all the steps described in different manuals and in the same github page of the packages we are not able to move the robot using ROS. We receive information of the sensors in ROS format, but anything related to the movement of the robot.

We have taken some screenshots of the rqt_graph and rqt_tf_tree as you can see below.

rqt_graph:
firulais_graph
When we execute the walk_lcm node (following the steps described in the section "Run the package" of the unitree_ros_to_real package) it appears, obviously, in the rqt_graph without any connection to other nodes. And the robot still does any movement.

rqt_tf_tree:
frames_Go1

Anybody knows nothing on which steps have to follow to control de Go1 Edu with ROS?

Thanks in advance.

@manik9000
Copy link

@Taucrates did you ever figure this out?

I am trying to run simple slam.
My plan was to piggyback on this ros_to_real package to send cmd_vel generated through AMCL and move base.

Issue is the TF tree is split into 2 as shown in your post. So I am confused, which base and odom frame should I be referring to for navigation.

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

2 participants