Replies: 1 comment
-
Hi, Apologies for the late response, we do not currently support ROS2. However, as a hunch, the two vescs have different port names. If you execute ls /dev/ttyACM* you should probably see /dev/ttyACM0
/dev/ttyACM1 You would then need to specify the port name for each vesc (usually given in the launch file). Thanks, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello Evryone
I am currently working on a project to make a four-wheeled differential drive robot using 4 VESCs with ROS2 as the means of communication. Two vesc will be masters and the rest two will be slaves. I found the vesc_hw_interface in which I used for one VESC and it was okay. But when I tried to use two VESCs with some modification in the ros2_control_xacro by including two hardware and two joints, there was an error like the following
I tried using the controllers (joint_state_broadcaster and velocity_controller), which worked with a single VESC, launching it with two VESCs with two ros2_control tags including two separate actuator-type hardware. I also tried to change the velocity controller to diff_drive_controller and tried the same thing with two VESCs. But it fails every time. I am attaching the screenshot of my configuration and xacro file. Any suggestion will be really helpful.
[NB. I commented out the servo parameters and used parameters that are required for velocity as command interface and positional and velocity for state interfaces]
Beta Was this translation helpful? Give feedback.
All reactions