Thanks, I appreciate it!

Thanks, I'm glad you liked it!

Thank you very much :)

Thank you!

No worries, glad to help!

Thanks!

Thanks!

Thank you!

Thanks!

Thanks!

Thanks!

Thank you!

Thank you :)

Thanks!

Thanks :D

Thanks Jon :)

Thanks!

Thanks! Yeah I think they've changed that behaviour in the time since. However they have also since released rqt_tf_tree which is a much easier way to achieve the same result so I recommend using that instead!

Thank you!

I have recheched properly no typoss, Still getting the same error. Can you help please.

I keep getting the same error. How did you solve? Did you just put the file in the folder suggested ?

I did what I typed above and it worked, now my question is , can we automate all that to just launch something and have our robot displayed in rviz?

Sorry it has been so long since I used ROS 1 I'm not sure. If I recall correctly, it's about the same except the URDF file is passed directly into RSP? Or something like that? I hope you got it working. The main parts of the URDF (joints, links, etc) work exactly the same on ROS1 and ROS2, but some things like plugins and some Gazebo settings will be different.

any update?

And perhaps some tips on how to deal with hydraulic actuators. I struggle to find documentation on this.

Got it now. Had to sort out my public keys for downloading from repositories, run $> apt update and $> apt upgrade and then $> sudo apt install ros-humble-xacro and $> sudo apt install ros-humble-joint-state-publisher-gui

Maybe you had humble version? On Ubuntu 22 its humble version so commands are: sudo apt install ros-humble-xacro ros-humble-joint-state-publisher-gui

@@tbtitans21 i fixed the problem

You know, I have also wondered that and never looked into it... I just checked now, and the only source I can find is in the tf2 Python listener code. If I had to guess, it looks like they want to have a mechanism by which you can tell which node was broadcasting a particular transform, but that isn't implemented so it is overridden to just say "default_authority"? Someone in the know may be able to provide a better answer. In any case, it's nothing to worry about :) github.com/ros2/geometry2/blob/2687a3543bf61481b06dcf37839c7e92bed85d2e/tf2_ros_py/tf2_ros/transform_listener.py#L115-L123

Thanks, I'm glad you got it sorted!

@@ArticulatedRobotics thanks for your videos. I am getting error [rcl] : Failed to parse global arguments when I am trying Dynamic transformation system. Any advice? Thanks in advance

@@jirivchi same problem

I needed up fixing the problem but I’m not sure as to why there was this problem in the first place. What i ended up doing was manually downloading the file example_robot_urdf.xacro and then placing it in my home folder and running he same code. But why did i have this problem in the first place. Why didn’t it get created automatically when i ran the same code you did? (I understand if you dont know why) Thanks for the videos!

thank you for this @@Anthonylion232

Hii, you found solution to this error? Please help.

How did you install xacro on Humble?

googer somewhere said don't do that just pass the path to the udf file ros2 run robot_state_publisher robot_state_publisher src/urdf_example/description/example_robot.urdf.xacro That goes farther, but gripes about 10 errors. The first is the material "blue" isn't defined. so I copied the color section out of the include and pasted it the main file. Rerun and that error is cleared. That was easy enough but the next error is Unable to parse component [${arm_length/2}] to a double (while parsing a vector value) - yieks.... This mess ends with : Error: joint xml is not initialized correctly at line 233 in ./urdf_parser/src/model.cpp Failed to parse robot description using: urdf_xml_parser/URDFXMLParser terminate called after throwing an instance of 'std::runtime_error' what(): Unable to initialize urdf::model from robot description [ros2run]: Aborted

hii, you found solution for this? please share