Amazing! I love your series. I am trying to use your guild with a similar project. The difference is using an available model (file .STL) When I launch on Rviz2 (command: ros2 launch agv rsp.launch.py), it works well But, when I launch on Gazebo (command: ros2 launch agv launch_sim.launch.py). It also run without errors or warnings. However, the model didn't appear on world. After some test, I find out that problem is about .STL file. Can you help me?
Micro-ROS seems interesting, but getting the pico to talk over an RJ45 wire though TCP-IP or UDP has stumped me, as I want to set up multiple pico's around my home to monitor the humidity, temperature and more. For now though it seems a bit complex, even with a w5500_evb_pico.
Personally, I'd like to see a video on passive vs active voice in engineering writing. Active expresses ideas in less space more life than passive. Passive, sadly, dominates technical writing and puts us all to sleep.
Hello sir, thanks for the great video, just a quick question, how can I add Gazebo to the dev container? I tried to add 'RUN sudo apt install ros-humble-gazebo-*' to Dockerfile template, but the container failed ERROR: failed to solve: process "/bin/sh -c sudo apt install ros-humble-gazebo-*" , any help would be appriated.
I am really struggling to get my raspberry pi camera 3 wide module working with ubuntu mate 22.04 with humble. Has anyone had success with this? Even after setting everything up as Josh did in the Ready to Humble video, i still can't get it to work.
This is going to help me so much to organize and simplify my workflow. I can't remember how many times I've reset my systems because of broken dependencies.
i wanted to change the topic name from cmd_vel to any another i have tryed using this <command_topic>smd_vel_ok</command_topic> in code but its not working any way i can change default topic name????
Thank you for creating these videos! I started following your videos along with my hardware, but I thought I would install the latest ROS jazzy along with Gazebo harmonic. Jazzy works fine with your code but Harmonic is completely different. I am not able to make it work even after reading all the Gazebo to ROS tutorials. I am just curious if you have any pointers for me. Should I downgrade to the older Gazebo?
can anybody help i have an issue my joint traj controller never seems to configure [1725282866.749748394] [spawner_joint_trajectory_controller]: Loaded joint_trajectory_controller [ros2_control_node-2] [INFO] [1725282866.750886615] [controller_manager]: Configuring controller 'joint_trajectory_controller' [ros2_control_node-2] [WARN] [1725282866.750966218] [joint_trajectory_controller]: 'joints' parameter is empty. [ros2_control_node-2] [INFO] [1725282866.751008551] [joint_trajectory_controller]: No specific joint names are used for command interfaces. Using 'joints' parameter. [ros2_control_node-2] [ERROR] [1725282866.751043506] [joint_trajectory_controller]: 'command_interfaces' parameter is empty. [ros2_control_node-2] [ERROR] [1725282866.751064255] [controller_manager]: After configuring, controller 'joint_trajectory_controller' is in state 'unconfigured' , expected inactive. [spawner-7] [ERROR] [1725282866.751949355] [spawner_joint_trajectory_controller]: Failed to configure controller [ERROR] [spawner-7]: process has died [pid 406079, exit code 1, cmd '/opt/ros/humble/lib/controller_manager/spawner joint_trajectory_controller --ros-args']. Yet ii have my yaml file well prased and it has its joints and command interfaces : joint_trajectory_controller: type: joint_trajectory_controller/JointTrajectoryController ros__parameters: joints: - T0-1 - T1-2 - T2-3 - T3-4 command_interfaces: - position state_interfaces: - position - velocity state_publish_rate: 100.0 action_monitor_rate: 20.0 allow_partial_joints_goal: false constraints: stopped_velocity_tolerance: 0.01 goal_time: 0.1
I am using ros2 humble to follow up on these tutorials. I am getting this error when i try to run <ros2 launch my_bot rsp.launch.py> : [INFO] [launch]: All log files can be found below /home/danny/.ros/log/2024-09-01-12-24-26-637618-danny-15734 [INFO] [launch]: Default logging verbosity is set to INFO [ERROR] [launch]: Caught exception in launch (see debug for traceback): Caught multiple exceptions when trying to load file of format [py]: - ExpatError: not well-formed (invalid token): line 5, column 11 - InvalidFrontendLaunchFileError: The launch file may have a syntax error, or its format is unknown what could be the issue?
great video! the problems with DDS have been coming to a head for a while but i'm surprised the community coalesced around zenoh rather than more established IPC middlewares. can't argue with "networked with opt in" rather than "networked by default" though -- that was honestly a crazy design choice in ROS1 and even crazier that it's been kept in ROS2 for so long.
Hey Guys, my question is not related to this video but I was wondering. I wanted to build a autonomous delivery robot. So for outdoors there well be no Wi-Fi available so like how to control, monitor the data as well as receive the video feed, and debug and edit code when the robot is outdoors using ros2 on my laptop. What kind hardware and software will be required. Josh if you could make a video on this it would be great.
I am having an error. Once I added the wheels, the rviz2 complains that "No transform [left_wheel] to [base_line]" "No transform [right_wheel] to [base_line]". I am using ROS2 Humble. Anyone else is having this issue? And any ideas how to fix it?
after installing xacro for iron and running the launch file i get the exception that there is no module named xacro - should i try to do a brute pip install of xacro - not sure how to proceed. thanks!
Excited about this video series!! I am building a human sized dinosaur robot. Am hoping that I will be able to set up some kind of odometry for the walking mechanism. Uses worm drive encoder motors to power a fairly basic walking mechanism that I have spruced up with some extra motors for turning!
when you say you can use PWM to drive a motor backwards (2:57) , do you mean you can send a PWM signal that drives the motor backwards, or do you need a switching circuit that you send the same signal through to drive the motor backwards? Can you like switch the bias of a PWM signal to be negative or something? Pretty new to mechatronics, but I come from music and radio land, so I like working with waves. Thanks for the help
Has anyone solved the problem of the odom frame not existing in rviz? In addition to that i don't have transforms from wheels to my base_footprint (in his example i think this would be base_link)
I've got answers (sort of). For my issue with transforms, I restructured my urdf to match the example with the same names and that seemed to do the trick (i must have at it set up incorrectly). As for why these transforms now show up correctly without also running join_state_publisher, i do not know. For the issue with the odom frame, we need to add two extra lines to the plugin in the gazebo_control.xacro. Those are: <command_topic>/cmd_vel</command_topic> <odometry_topic>/odom</odometry_topic>. After this addition, you should see the odom frame. Hope this helps somebody!
I'm late to the party but I'm doing this. I found this series a year ago and definitely knew I wasn't ready. I've done some smaller, simple electronics projects and basics on ROS. I'm feeling more confident now and will give this a shot. Awesome series!
Great video! Very well explained. About your method 4 (cross-host discovery via 2 routers): the routers are not propagating gossip discovery to other routers, only to the local peers. This is to avoid scalability issues in case of very large systems with lot of peers. Still, for p2p across hosts, what you can do is: - start only 1 router (e.g. in RaspPi) - configure the peers in RaspPi to listen to any interfaces (`[::]`) - configure the peers in Local Machine to connect to the router in RaspPi Note that such config might be counter-productive over WiFi, as multiple TCP connections means higher overhead wrt. same traffic over 1 TCP connection only. Moreover grouping all the traffic via a single TCP connection allows Zenoh to batch small messages into single frames, reducing the overhead further. But this config is useful in the case of a multi-hosts robot, with ethernet interconnectivity between hosts. Here, no drawback with multiple TCP connections over ethernet (providing the bandwidth is large enough). And p2p across hosts lowers the latency.
Thanks Julien, for both your detailed reply and your work on Zenoh! I'll pin your comment so everyone can see it. That last point is what I was thinking - if you have a few different hosts that are on a tight wired network where latency is important, it's nice to be able to remove the extra hops. (Also I think that is what I tried but I probably just mixed something up on my end - glad you can confirm it should work)
