Hello,
I wanted to ask for advice for debugging this issue I had with the diff robot; I fixed one of the main issues which involved the missing xacro tag of the gazebo ros2_control dependency in its gazebo xacro file but after that was finished. I double checked the code from the xacro main file of the diff bot when you only need to add the tags for the xacro diff drive with the yaml file configuration for those joints and wheel joints. I am a bit lost on what to do next to debug or troubleshoot in having the controller manager active being able to activate the joint_state_broadcaster controller and the diff drive controller? Thank you all for your help!
Firstly, for the controller to launch and load successfully, you MUST have the robot loaded and spawned in Gazebo Simulation.
If you have the spawn code in your launch file and the robot has not spawned, then you have an issue with your robot description file.
First spawn the robot. Make sure that robot is spawned by looking at the simulation window.
Then launch the controllers one by one using the command line first. Once you verify everything works, you can combine them into one single launch file.
I did load the robot correctly in the simulation. My apologies for the low-quality picture. The diff sim robot is there on the side and I was able to have the robot move as described in the tutorial. The main thing that changed was that I ran it today the same way as I did previously following the steps in the tutorial and now it worked perfectly. I do want to thank you for the recommendations when running into this issue when I am working on the Ubuntu system ROS2 controls in my simulation these recommendations are very valuable sources of advice. So thank you!