Excellent! I assume you'll talk about where the talker sent its messages, a named pipe, a special place, where, and can nodes send messages to specific nodes, so that other nodes wouldn't be able to hear them. Thank you and will continue watching later.
Thank you so much for doing this series. I've been learning Ros from various web sources, a little here, a little there. This could have saved me so much time. I've also followed your website tutorials. I really appreciate your help!
for those who are getting error: package 'demo_nodes_cpp' not found type in terminal: for cpp: sudo apt-get install ros-humble-demo-nodes-cpp for python: sudo apt-get install ros-humble-demo-nodes-py
There is an error message when running rqt_launch, but still able to launch: libGL error: pci id for fd 44: 1ab8:0010 driver (null) pci id for fd 45: 1ab8:0010, driver (null) I'm using ubuntu 22.04 on Parallels on a Macbook Air m1 chip
hi thanks for your tutorial i did this source /opt/ros/jazzy/setup.bash and i gor this ...6HB:~$ ros2 run demo_nodes_ usage: ros2 run [-h] [--prefix PREFIX] package_name executable_name ... ros2 run: error: the following arguments are required: executable_name, argv any can help
So I finally got around to trying robotics and I fell like I want to quit already due to how poor the software/platforms are on Raspberry pi (which is supposed to be beginner based). FIRST. ROS2 does not run on the official Raspberry Pi OS (Raspbian which is really just debian, which is really just garbage which can't run anything due to no updates). They require you to hack together some docker files or use outdated documentation (OSRF keeps saying use foxy which is EOL already). What's the point of continuing if things just won't work? Then i thinka bout the ACTUAL hardware that needs to connect to some linux based OS and think about the driver hardware issues and support and think about hell. I don't think any of this is going to get wider adoption unless they fix the poor platform that is linux robotics. There's too many hateful open source issues that destroy your life/time trying to figure out.
Unfortunately, Raspberry Pi is not big enough to be any priority concern for the developers behind ROS. Still I got good success using Ubuntu for Raspberry Pi and installing ROS. I know, there might be some additional work for specific libraries, but it's worth the effort when you finish a nice project. Also, working with ROS is frustrating. All the time. Just something you have to get used to ;)
I'm also digging into same way. Still sticking with docker but if it's not working, then I will try Linux PC with arduino ROS setup. I hope this setup solve the issue you mentioned no GPIO with Linux.
Thank you for watching!
🔥 To go further with ROS2, check out this complete and step-by-step ROS2 course
👉 rbcknd.com/ros2-for-beginners
Thank you so much for providing course for ROS 2. I've been trying to find where do I start with ROS2 and I found this gem! I appreciate your help!
Excellent! I assume you'll talk about where the talker sent its messages, a named pipe, a special place, where, and can nodes send messages to specific nodes, so that other nodes wouldn't be able to hear them. Thank you and will continue watching later.
Thank you so much for doing this series. I've been learning Ros from various web sources, a little here, a little there. This could have saved me so much time. I've also followed your website tutorials. I really appreciate your help!
Hey Thanks a lot man i was just looking to find where to start in ROS and your videos have been a great help :)
This tutorial is amazing. Just amazing. Thank you so much.
awesome tutorial
Package demo_node_cpp not found please help
for those who are getting error:
package 'demo_nodes_cpp' not found
type in terminal:
for cpp: sudo apt-get install ros-humble-demo-nodes-cpp
for python: sudo apt-get install ros-humble-demo-nodes-py
hi, can u give me the name of the terminal which includes 4 windows terminal please
Terminator. Install with sudo apt install terminator
how did you do the automatic alarm completion process, I couldn't do it, I'd be glad if you could help
Will you please make the rest 9 tutorials available if already recorded
They will all be released in the following days - one each day :)
hi
when i do the same thing i resive by the Listener nothing !!
can someone help.
i also tried to do: ros2 node list and it showed me nothing
Hi, could you tell which terminal are you using (coz it certainly doesn't looks like gnome-terminal) and how you can drag all four of it at once?
This is called "terminator", you can install with "sudo apt install terminator". Then Shift + Ctrl + O / E to create more terminals
Thank You but my rqt_graph is inverted one. Is it a problem?
No problem, sometimes the display of nodes will be different. But the arrows should be between the same nodes as in the video.
Hi, I got the problem of X11 connection broke(error1) when I use rqt, is there any solution?
rqt graph does not show all the running nodes
There is an error message when running rqt_launch, but still able to launch:
libGL error: pci id for fd 44: 1ab8:0010 driver (null)
pci id for fd 45: 1ab8:0010, driver (null)
I'm using ubuntu 22.04 on Parallels on a Macbook Air m1 chip
rqt is a software that unfortunately contains a lot of bugs. If you can manage to run it (even with error logs), I wouldn't worry too much about it :)
hi
thanks for your tutorial
i did this
source /opt/ros/jazzy/setup.bash
and i gor this
...6HB:~$ ros2 run demo_nodes_
usage: ros2 run [-h] [--prefix PREFIX] package_name executable_name ...
ros2 run: error: the following arguments are required: executable_name, argv
any can help
Rqt_graph is not working for me. I followed all the previous steps
try running rqt_graph command before writing any other command
also, keep refreshing it after every node you add
So I finally got around to trying robotics and I fell like I want to quit already due to how poor the software/platforms are on Raspberry pi (which is supposed to be beginner based). FIRST. ROS2 does not run on the official Raspberry Pi OS (Raspbian which is really just debian, which is really just garbage which can't run anything due to no updates). They require you to hack together some docker files or use outdated documentation (OSRF keeps saying use foxy which is EOL already). What's the point of continuing if things just won't work? Then i thinka bout the ACTUAL hardware that needs to connect to some linux based OS and think about the driver hardware issues and support and think about hell. I don't think any of this is going to get wider adoption unless they fix the poor platform that is linux robotics. There's too many hateful open source issues that destroy your life/time trying to figure out.
Unfortunately, Raspberry Pi is not big enough to be any priority concern for the developers behind ROS. Still I got good success using Ubuntu for Raspberry Pi and installing ROS. I know, there might be some additional work for specific libraries, but it's worth the effort when you finish a nice project.
Also, working with ROS is frustrating. All the time. Just something you have to get used to ;)
I'm also digging into same way. Still sticking with docker but if it's not working, then I will try Linux PC with arduino ROS setup. I hope this setup solve the issue you mentioned no GPIO with Linux.