-
Notifications
You must be signed in to change notification settings - Fork 272
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
Cannot control the car in Gazebo with keyboard : Car won't move #25
Comments
The demo only launches the joystick teleoperation nodes. If you want to use keyboard control you'll need to add appropriate nodes to capture the keyboard input and map those it to the topics for the demo like we do for the joystick: https://github.com/osrf/car_demo/blob/master/car_demo/nodes/joystick_translator If you'd like to implement this and submit a PR we'd be happy to review and merge it but since this is a demo repository we're not actively developing on it. |
Hi, In the I didn't try to get rid of it, as I couldn't find any documentation on that type of plugin in Gazebo on the official website. Anyway, I download the whole repo, build the Docker image and run it all again, and it works now. I guess it was some stuff going on with Docker cache and previous image that got messed up. I saw in the trace log that it was using a lot of cache IDs. Do you have any tips on that matter? This issue is closed though, thank you for your time |
The KeyboadGUIPlugin just publishes key chars to |
Thanks for the info! I should definitely not get rid of it in the world file. When typing Have a nice day :) |
Battery state machine
Hi all,
I don't have a joystick so I'm controlling the car using the keyboard. It was working perfectly well so far.
However, I wanted to see if I could use the launch script on plain Kinetic, without Docker.
When I tried to catkin_make, it said that the package ignition-msgs0 was not found. So I manually installed libignition-msgs0 with
However, the caktin_make command kept crashing on dependancies, so I gave up on this, and decided to stay with the Docker setup. But now, when I launch the simulation, the car doesn't move according to keyboard letters pressed. In fact, it doesn't move at all.
I've checked in the Docker container that the librairy was still loaded and it is there:
alongside with
I don't have the slicest idea of where to look next to find where the bridge is broken between the keyboard and the simulation.
It's my fault, I should have stayed with the original setup, sorry for bothering you.
Have a nice day
Guillaume
The text was updated successfully, but these errors were encountered: