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

Implement hardware interface #5

Open
adam-slucki opened this issue Apr 10, 2021 · 1 comment
Open

Implement hardware interface #5

adam-slucki opened this issue Apr 10, 2021 · 1 comment
Assignees
Labels
hardware requires actual robot to develop or test

Comments

@adam-slucki
Copy link
Collaborator

Currently the steering and drive motor responds directly to messages sent to /cmd_vel topic. What's more, the node ignores what the values in the message actually represent.

To be able to use external ROS packages a hardware interface supporting our robot must be implemented.
Note: it must be done in C++, Python is not supported.

@adam-slucki adam-slucki added the hardware requires actual robot to develop or test label Apr 10, 2021
@adam-slucki adam-slucki self-assigned this Apr 10, 2021
@adam-slucki
Copy link
Collaborator Author

Update: there's a working stub in hardware_interface branch.
Python object will be used for controlling pwm driver: https://learn.adafruit.com/16-channel-pwm-servo-driver?view=all

Python embedding in c++ part already works. Hardware Interface also works and correctly communicates with the ackermann controller.

Missing parts:

  1. Ackermann controller - angular velocity isn't translated into steering angle #19
  2. Converting requested velocity to PWM signal width

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hardware requires actual robot to develop or test
Projects
None yet
Development

No branches or pull requests

1 participant