TB5-WaLI Blog: Jazzy TB4 on Raspberry Pi 5 - Ubuntu 24.04 #517
Replies: 16 comments 10 replies
-
|
Full Success getting
My install Turtlebot4 Jazzy on Raspberry Pi 5 is here Bot arrives Thursday, so more testing has to wait. (And creating modified URDF and SDF.) |
Beta Was this translation helpful? Give feedback.
-
Not so fast...Bot arrived, camera needs aux 5v power or bad juju randomly occurs. |
Beta Was this translation helpful? Give feedback.
-
|
Determined everything runs fine if provide power to the Oak-D-Lite camera not through the Raspberry Pi 5. Put a power splitter cable on the Oak-D-Lite:
And connected a HiLetGo 6-20V DC Buck-Buck 5V "USB Charging" supply to the Create3 "Battery Aux" header
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Slamtec RPLidar C1 arrived today - managed to integrate the sllidar_ros2/sllidar_node to the turtlebot4 bringup! So far with Oak-D-Lite camera running and the C1 LIDAR operating, and the RPi5 running the turtlebot4 bringup items, the current draw is 1.5A - well below the 3A the Create3 can provide.. 
|
Beta Was this translation helpful? Give feedback.
-
|
WaLI's "ride" arrived today, but the battery was totally shot - not just shutdown ... cannot wake.
|
Beta Was this translation helpful? Give feedback.
-
Boring Stuff: My "TurtleBot4 History"This Incarnation: TB5-WaLI Jan 2025 - Create3 plus Raspberry Pi 5, RPLidar C1, Oak-D-Lite
Consolation Period: Implemented TurtleBot3 Cartographer, Navigation and Gazebo Classic simulation for 24/7 "alive" GoPi5Go-Dave (GoPiGo3) Raspberry Pi 5 robot (in Docker) Second Incarnation: Create3-WaLI Dec 2023 - Mar 2024 (Returned Crashed running RTABmap)
First Incarnation: TurtleBot4 Nov 2022 (Returned Immediately - Damage in Shipment)
Consolation Period: Created ROS 2 Humble GoPiGo3 Raspberry Pi 4 image and "Humble-Dave" Beta Incarnation: Create3 Simulation Beta Oct 2021
|
Beta Was this translation helpful? Give feedback.
-
What is inside the iRobot Create3 battery?DANGER - DO NOT ATTEMPT THIS - FOR CURIOSITY ONLYThe iRobot Create3 battery is a true engineering marvel. Really! The amount of design thinking that went into the battery really surprised me when I managed to open the "dead" battery without destroying it.
|
Beta Was this translation helpful? Give feedback.
-
TB5-WaLI Is "Alive"!Well the "5-WaLI" part is alive, the turtlebot4.service did not start everything successfully. I stopped the "TB" (mainly to turn republisher off), returned the Create3 to an empty namespace, and started my WaLI nodes (wali_node, say_server, odometer). Problem appears to be USB surge power required is greater than Pi 5 will supply, designing aux powered USB hub. WaLI will get off the dock when the battery is 99% charged (if not during "sleeptime" 10pm to 8am), TB5-WaLI is drawing 9.8W total, 4.3W for the Create3, and 5.5W for the RPi5, and speaker. (LIDAR and Oak-D-Lite powered but not operating). His very first "playtime" lasted 2.6 hours: His first "after playtime" recharge took 2.7 hours and ATM is off the dock for his second "playtime":
|
Beta Was this translation helpful? Give feedback.
-
TB5-WaLI Survives His First Night As A True Turtlebot4TB5-WaLI with the turtlebot4 service running in Simple Discovery mode was republishing topics just fine, but actions and services were not being republished to the Create3 and the responses were not successfully being republished, TB5-WaLI docked successfully when his battery dropped below 15%, When "sleep time" ended at 8:00AM local, WaLI was trickle charging at below 99% so he did not immediately get off the dock, |
Beta Was this translation helpful? Give feedback.
-
|
Interesting to note: While the Create3 odometry is surprisingly good, my idea to reset_pose after every docking does not maintain the odometry quality. The reason is that the Create3 automatic docking can be far from normal to the wall. Last night TB5-Wali docked with a heading of +12 degrees to the wall-dock-normal. I performed the "quality maintenance reset_pose", which resulted in the odometry heading -12 degrees from reality. Nav2 introduced a camera guided docking feature recently, it will be interesting to see if that will dock with more consistent heading. (Eventually will get around to trying that. Lots to learn first.) 
|
Beta Was this translation helpful? Give feedback.
-
Runaway Oakd (Camera) ContainerInteresting issue with Oak-D-Lite camera operation: /stop_camera service call when docked eventually will cause camera driver to stop publishing /oakd/rgb/preview/image_raw topics and the oakd container to runaway (100% of one CPU). I submitted an issue to Luxonis - need to compare launching the camera separate from the turtlebot4_bringup launch. Since I am trying to run pure "installed turtlebot4" code (/opt/ros/jazzy/share/turtlebot4_*) I am currently testing with a modified turtlebot4_bringup/config/turtlebot4.yaml that sets In my current test: "turn off turtlebot4_node power_saver feature" (which prevents stopping camera when on the dock) the
Next I'll figure out how to properly stop TB4 oakd container to "run the camera driver via a launch file" and then test repeated stop_camera and start_camera service calls. (The camera is drawing 1W from a separated 5v power supply, with very good voltage regulation of +/-10mV.)
|
Beta Was this translation helpful? Give feedback.
-
|
Yup - issue only with the Jazzy release of the Luxonis depthai_ros_driver, accepted, reproduced, diagnosed, and branched with a fix in 48 hours, and will be pushed out in the February monthly Jazzy distribution update. Luxonis support has exceeded my expectations for over four years now that I have been asking questions on their forum. This is the first issue I have submitted, and they didn't disappoint. |
Beta Was this translation helpful? Give feedback.
-
TB5-WaLI Does First MapI managed to modify the turtlebot4.urdf (kludged) to match WaLI's C1 LIDAR position and orientation, (and Oak-D-Lite position), so WaLI could try out the tb4_navigation asynchronous SLAM. Most of the ROS mapping videos I see show mapping in quite sterile office environments, so WaLI's map cluttered with unrecognizable home obstacles might be surprising. Eventually, I will have to test if localization is better with the cluttered, sensor map, or with a "clean house boundary map".
Here's the video of WaLI's First Map: |
Beta Was this translation helpful? Give feedback.
-
Robots make different sounds when they are in pain.Last night as I was watching the late night weather, WaLI started screaming. He was obviously in pain, so I ran to see if I could help him. The screaming was coming from inside the Raspberry Pi 5 case, so I went to my computer to safely shutdown WaLI's "brain". WaLI spends the night on his dock, so I went to sleep leaving WaLI's brain repair for the morning before his usual 8AM undocking. Turns out the Raspberry Pi 5 case fan developed a bad bearing. Luckily I had a Pi5 Active Cooler handy to cool WaLI's pain. WaLI is back to himself, off his dock, quietly observing the world around him.
|
Beta Was this translation helpful? Give feedback.
-
KLUDGE: How to re-modify TurtleBot4 code after update/upgradeThe proper way to customize ROS code is to build overlays and setup the path to find the overlay code rather than the stock code, but two issues with this:
So I am kludging my changes onto the updated turtlebot4 packages with three "install____.sh" scripts. Full instructions: NOTE: After running sudo apt update && sudo apt upgrade -y run: Then wait till oakd container is up with "camera ready" and then find the PID to kill the camera (this is the workaround till the Luxonis Jazzy depthai_ros_driver will /stop_camera without crashing): (if need the camera cmds/launch_camera.sh) |
Beta Was this translation helpful? Give feedback.
-
|
Cool - thank you for responding with the repo fork suggestion - That is the key to knowing when there are updates available for me to decide to accept, merge, or reject for my particular configuration. So to customize the turtlebot4 lite URDF, I need to fork
Q: Should I fork turtlebot4_setup even though I don't need to change any code there? (will it handle the /etc/turtlebot files correctly if it is not forked?) I will end up with repos structured:
I've never worked with a fork under my repo, only forks as the top level repo. I'm going to backup my system before I start this - it sounds likely I am not going to get a fully working system first try. |
Beta Was this translation helpful? Give feedback.
-
You don't need to fork the turtlebot4 setup repo since you won't be changing its software. Turtlebot4 is only a configuration package, and is not part of the ROS running code. It exists as a tool to facilitate modifying certain settings. You just need to use the setup tool to set the path which changes what path is sourced at the beginning of the service.
Forking this is one option, the other option is that you can create a copy of the config file that you want to modify and place it in the
I'm not completely sure what you mean by this. You will have multiple different repos that may be forked etc. but they are still their own repos, collected in a common workspace. I would expect your structure to look like this:
To be clear, the build, install and log folders will be auto-generated in the build process. |
Beta Was this translation helpful? Give feedback.
-
|
Ok - I'm starting to understand and document how to do this for my TB5-WaLI robot and repository Basically:
My structure will be:
Lastly I will need to figure the build and turtlebot4-setup steps - but first get the forked cloned branches down, built and the process documented. To Be Continued ... |
Beta Was this translation helpful? Give feedback.
-
Almost ready to try it - forked, cloned, modified, and BUILT!!!(added to ~/TB5-WaLI/config/README.md ) To Be Continued ... |
Beta Was this translation helpful? Give feedback.
-
SUCCESS - TB5-WaLI with (modified) ROS 2 Jazzy Turtlebot4 OverlaysCompleted the setup process (with complete documentation) and confirmed:
Big THANK YOU to @hilary-luo and @smatarCPR for the guidance that enabled making WaLI a "legit" user of Turtlebot4 code base, that enables a "proper" software development maintenance process - no more kludge for robot WaLI. Three mods for TB5-Wali (URDF, publish /stop_status, power_saver off):
|
Beta Was this translation helpful? Give feedback.
-
TB5-WaLI's SecretThe secret to the success of this WaLI incarnation is the Create3-Republisher-Node and ROS 2 Discovery-Server running on the Raspberry Pi, that isolate the Create3 from unrelated ROS 2 topics to prevent overloading the Create3 processor. Big shout out to @alsora for the development of the Create3 Republisher - The critical secret to the iRobot Create3 platform success! |
Beta Was this translation helpful? Give feedback.
-
Logitech F710 Wireless USB Game Controller for Turtlebot4 TB5-WaLIAdded a mapping for the Logitech F710 buttons to correlate to the stock TB4 Game Controller Logitech F710 Game Controller for TB5-WaLI
added to turtlebot4_robot/turtlebot4_bringup/config/turtlebot4.yaml:
Using Undock, Dock Button on F710 Game Controller: |
Beta Was this translation helpful? Give feedback.
-
Turtlebot3 vs Turtlebot4 Mapping - Interesting resultWith another of my ROS 2 robots, I was able to create a great map of my house using turtlebot3_cartographer, where my efforts to create a map with slam_toolbox were stymied. With TB5-WaLI I ran the turtlebot4_navigation async SLAM and created a map, and for comparison have created "turtlebot4_cartographer" and built a map. With turtlebot4_cartographer:
The map with my "turtlebot4_cartographer" (Jazzy turtlebot3_cartographer with name changed to tb4):
The first map with turtlebot4_navigation async SLAM: and another run with turtlebot4_navigation async SLAM: |
Beta Was this translation helpful? Give feedback.
-
Safe to charge to 100%It is suggested (for Electric Vehicles) that Li-Ion batteries be charged to 80% and discharged no more than 20%, to maximize battery life (about 3000-4000 cycles over 10 years for EVs). Currently I have my "TB5-WaLI" (Turtlebot4 with a Raspberry Pi 5 - WallFollower Looking For Intelligence) remain charging on the dock till 99.5% charged and return to the dock at 20.5% charge. (Docked charge time is extended currently because I disabled power_save due to the Luxonis DepthAI ROS driver issue crashes the camera container.) ATM, charge time is about 3 hours, and “playtime” is 2 hours. I asked iRobot support: “Is this going to shorten the battery life?” Is it realistic to expect 3000-4000 cycles (5 per day) making the battery last 2-3 years if I dock at 20% and undock at 100% charge? Received this response from iRobot support: Current stats for TB5-WaLI with "Charge to 100%, Play to 20%": |
Beta Was this translation helpful? Give feedback.
-
Blog for TB5-WaLI (TurtleBot5 Wallfollower Looking for Intelligence)
This Incarnation: TB5-WaLI Jan 2025 - Create3 plus Raspberry Pi 5, RPLidar C1, Oak-D-Lite running Jazzy TB4 service
Second Incarnation: Create3-WaLI Dec 2023 - Mar 2024 (Returned Crashed running RTABmap)
First Incarnation: TurtleBot4 Nov 2022 (Returned Immediately - Damage in Shipment)
Beta Incarnation: Create3 Simulation Beta Oct 2021 - (Built Raspberry Pi 4 ROS 2 Galactic to test Create3 Simulation Beta)
Jump to latest post->"Safe To Charge To 100%”
Beta Was this translation helpful? Give feedback.
All reactions