at 3:08 another thing you can do, you can put the command in .bashrc file, so everytime you open the bash shell it will automatically source the ros2 interface for you.
Absolutely. As I said in the video, I have noetic commands in my bashrc scripts. Hence I didn’t want to change that. But you can always source ROS 2 distro the same way
@@hummingbird19 Thanks for replying, I want to say thank you to teaching ros2. I also have some suggestions for you for incorporating it in future videos. * managing the ros2 package with mamba and robostack * Incorporating pytorch with ros2 * Using micro-ros with RTOS like freertos, Zephyr and directly on bare metel I know, it is lot to cover but we will patiently wait for the videos and if you need any help, we will help you Thanks 🙏🙏🙏
@@vikaspoddar001 It's a pleasure, Vikas. Thank you for watching :) I'm currently working on a series. But I'd love to get on with some of the stuff you mentioned, as soon as it's possible. I'll try my best :)
I'm trying to create a listener, talker on 2 machines, 1 machine is virtual machine running on a windows machine, the other is a raspberry pi, I am able to ping each other, but the talker/listener example doesn't communicate, the talker talks, but the listener doesn't see it
Can someone resolve the error I m facing on Ubuntu 22.04 LTS with ROS (Humble hawksbill) robot@robot - hp:~$ sudo apt install ros-humble-desktop Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-paraview : Conflicts: python3-vtk9 but 9.1.0+really9.1.0+dfsg2-3build1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
at 3:08 another thing you can do, you can put the command in .bashrc file, so everytime you open the bash shell it will automatically source the ros2 interface for you.
Absolutely. As I said in the video, I have noetic commands in my bashrc scripts. Hence I didn’t want to change that. But you can always source ROS 2 distro the same way
@@hummingbird19 Thanks for replying, I want to say thank you to teaching ros2.
I also have some suggestions for you for incorporating it in future videos.
* managing the ros2 package with mamba and robostack
* Incorporating pytorch with ros2
* Using micro-ros with RTOS like freertos, Zephyr and directly on bare metel
I know, it is lot to cover but we will patiently wait for the videos and if you need any help, we will help you
Thanks 🙏🙏🙏
@@vikaspoddar001 It's a pleasure, Vikas. Thank you for watching :)
I'm currently working on a series. But I'd love to get on with some of the stuff you mentioned, as soon as it's possible. I'll try my best :)
Great Channel!!
thanks a lot !
I'm trying to create a listener, talker on 2 machines, 1 machine is virtual machine running on a windows machine, the other is a raspberry pi, I am able to ping each other, but the talker/listener example doesn't communicate, the talker talks, but the listener doesn't see it
Have you tried this?
roboticsbackend.com/ros2-multiple-machines-including-raspberry-pi/
Can someone resolve the error I m facing on Ubuntu 22.04 LTS with ROS (Humble hawksbill)
robot@robot - hp:~$ sudo apt install ros-humble-desktop
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-paraview : Conflicts: python3-vtk9 but 9.1.0+really9.1.0+dfsg2-3build1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Wish this was in c++ but great content nonetheless