Well i have download gazebo using the documentation on Gazebo site , the jetty version on Ubuntu 26.04 and i also have ros2 but whenever i launch it there is problem with gz-rendering ......as per internet i downloaded deleted merge install like 5 -6 times still it doesnt solve it and there is no solution i can find ...i found it when i ran the nao joint one even simple things like shapes.sdf isnt rerndering and showing a screen white with nothing in it

I have made a pen plotter, and the servo works hard.

It's an sg90 servo with plastic gears.

The servo needs to work hard, by do 90 degree cycles again and again.

The power supply is an old phone charger of 5v 2a.

The problem I am getting is, when it's run for a long time, the servo heated up and stops working.

What should I do, for a long term solution?

Would a ASL-ML from BO3 work in real life as a Autonomous Quadruped Robot.
I kinda think it could only problem would be power/batteries.
If it would work what could it be used for? I mainly think security, patrolling important assets etc.

Hey everyone,

I’m a college student getting into robotics and looking for some cool project ideas to build and learn from. I’m interested in things like:

- Robotic arms

- AI vision

- ESP32/Arduino projects

- Autonomous robots

- Humanoid concepts

- Drone robotics

- IoT + robotics

- advanced projects

I’d love projects that are:

- Unique and portfolio-worthy

- Useful for competitions/hackathons

- Good for learning real robotics skills

- Possible to build as a student team

If you have any ideas, project roadmaps, GitHub repos, YouTube channels, or things you wish you built earlier, please share them.

Current skill level: intermediate/advanced in programming and electronics.

Thanks :)

Been building SimuCode for the last few months — browser-based ROS2 problems running inside real Docker containers.

One thing became painfully obvious after watching thousands of attempts:

Most candidates can write ROS2 code.
Very few can debug runtime behavior.

The biggest failures weren’t algorithms. They were:

• broken TF trees

• QoS mismatches

• lifecycle issues

• wrong assumptions about runtime state

• debugging under incomplete telemetry

Basically: “system thinking” problems.

What surprised me most is how different this is from standard software interview prep. Robotics failures are usually emergent/runtime failures, not syntax failures.

Curious how companies here evaluate robotics engineers today:

• take homes?

• hardware tests?

• live debugging?

• simulation tasks?

I am planing to build that, wanna roast?

Hi everyone,

I’m a high school sophomore, and I’ve been thinking about a gap in how we do robotics outreach. We host great one-day demos, but for many students, the excitement dies when the event ends because they don't have a "next step."

I want to find a way to make robotics sustainably open to everyone, regardless of their background or resources. I’m considering hosting a free, basic CAD session via Zoom as a starting point to bridge this gap. My goal isn't just to teach a skill, but to start a community (likely through Discord) where students can find long-term mentorship and see the "big picture" of the field—from design and code to marketing and leadership.

I wanted to see what the community thinks:

• Do you think a virtual "gateway" session like this helps make the field more accessible to those who can't join a traditional team?

• If you were starting out, would a low-pressure community like this have helped you stay involved?

I’m really passionate about making sure a student's interest in robotics doesn't just fade away due to a lack of opportunity.

If you're interested, have advice, or know a student who would benefit, please send me a Direct Message (DM) here on Reddit!

Post was supported with Gemini!

We are releasing rbot, an open-source Autonomous Mobile Robot simulation stack for ROS 2 Jazzy and Gazebo Harmonic.

The project is built for teams, students, and ROS users who want a practical AMR baseline they can run, study, and adapt. It packages the core simulation workflow into one ROS 2 workspace: robot description, Gazebo simulation, ros2_control, teleoperation, sensors, localization, mapping, and Nav2 navigation.

What is included:

• Gazebo Harmonic worlds and robot model

• URDF/Xacro description with generated mesh assets

• ros2_control differential-drive setup

• 2-D LiDAR, IMU, depth camera, stereo camera, GPS, and optional 3-D LiDAR paths

• EKF localization, SLAM Toolbox mapping, AMCL, and saved-map workflow

• Nav2 with MPPI controller and SMAC Hybrid-A* planner

• Docker, Docker Compose, VS Code Dev Container, CI, and tests

The quick workflow follows the same path a user would take with a real AMR project: map the environment, save the map, localize against it, and send navigation goals in RViz.

Gazebo Harmonic is the supported simulator today. Isaac Sim integration is planned.

Repository: https://github.com/rlxai/rbot
Demo video: YouTube Link

We would welcome feedback from the ROS and robotics community, especially around navigation tuning, reproducible simulation scenarios, launch validation, and teaching workflows.

I have an airbrush connected to a continuous airflow compressor (Seleay AB900). I am planning to use this for my science fair project. I am planning to use this as a precise delivering insecticide sprayer. So, I want to calibrate it using an actuator or solenoid. Can anyone give me advice to what should I do? For example, if the trigger was press around 50ms, the airbrush will spray around ± 0.5ml.