destogl's profile - activity

If you are using this under your own namespace then you should also place controller manager under a namespace, i.e., th

I was doing admittance control on KUKAs with external FTS sensor. And yes for impedance control you need dynamic model w

If someone ends up here searching for how to that in ROS2 the key is: rclpy.init(args=args, signal_handler_options=Sig

I doubt that this is possible because when you are generating Debian files you are doing this in a separate (fakeroot) e

Yes, of course. The easiest is to generate debian packages using bloom. Then users can simply install them on their comp

As for the joint_state_broadcaster in ros2_controllers, I will wait until we get some kind of consensus on this to discu

I don’t think you have to do anything with qt creator. Simply create an rqt plugin based on examples. If you want to do

Hi, I was doing something similar few years ago and we decided to create an rqt plugin specifically for our robot/need

The hw_positions_ store position values of the example hardware. On a real hardware or simulation, you will also use som

Communication to hardware using topics, services, or actions is not and will not be possibly off-the-shelf. If you reall

Communication to hardware using topics, services, or actions is not and will not be possibly off-the-shelf. If you reall

Hi, I guess that you are using some old version or publishing to a wrong topic, your velocity commands for DiffBot. Did

I see now. I am open to reconsider everything we do in ros2_control, but for now, DDS shown itself rather as a bottlenec

(disclosure: biased answer from a ros2_control maintainer) TL;DR: booth approaches are equally valid, but you probably

Check my edit about too

Now with ROS 2, not working on facilitating distributed, deterministic control, but instead still trying to work-arou

@gvdhoorn I agree with you on all points. And I fully understand your comments. Let me clarify some things I think are m

Now with ROS 2, not working on facilitating distributed, deterministic control, but instead still trying to work-arou

@gvhoorn I agree with you on all points. And I fully understand your comments. Let me clarify some things I think are mi

(disclosure: biased answer from a ros2_control maintainer) TL;DR: booth approaches are equally valid, but you probably

These issues are usually caused by friction parameters. It appears that you are using dead-reckoning for rotation. There

Then if you need any help with setting up the ros2_control driver for the gripper let me know.

@sameh4 I wrote my commend as answer. Please mark it as correct if you are happy with it.

These issues are usually caused by friction parameters. It appears that you are using dead-reckoning for rotation. There

You are already doing it correctly. I am using remapping in large projects, and they work great. The issues you have is

The support for transmission has just landed in ros2_control. At least the test case with SimpleTransmission is working.

There are currently no controllers supporting explicitly parallel (delta) robots. But what you can always do is to use

These issues are usually caused by friction parameters. It appears that you are using dead-reckoning for rotation. There

Regarding the latest comment. IMHO, one should always use .xacro files, even urdf is straightforward. It just gives you

This is desired, since i would need to write only one hardware interface if the robots are identical and would only n

ROS-industrial seems very well developed and maintained but it is based on ROS-Kinetic which was already EOL in April

Hi, there is not and will not be any error management done by controller_manager for foxy. We integrated error manageme

Since you don't have “e” version, you should probably connect the gripper directly. If there are no drivers for it, then

Hi all, There is an example for a simple diff-drive robot in ros2_control_demos repository. See here for the explanati