Hi everyone!
I’ve been building RobotLens, a native robotics engineering workspace that brings visualization, debugging, diagnostics, simulation, and development workflows into one connected environment.
My background is in computer graphics and game development. When I started learning ROS 2, I found myself constantly switching between terminals, visualizers, logs, simulators, and other tools.
Each tool was useful on its own, but as a beginner, I often struggled to understand how everything connected and what was actually happening across the system.
That experience led me to start building RobotLens.
Coming from graphics and game development, I’ve always appreciated how tools like Unity and Unreal bring complex workflows into a single, interactive workspace. I wanted to explore a similar approach for robotics engineering.
Here’s what’s been built so far:
-
ROS 2 or Zenoh Workspace: Live discovery, topic inspection, TF visualization, diagnostics, and communication backend support.
-
Visualization: Native Vulkan rendering, robot visualization, and interactive scene manipulation, topic visualization.
-
Simulation: Gazebo and MuJoCo integration, with support for different simulation workflows.
-
Navigation & Motion Planning: Nav2, EasyNav, and MoveIt 2 integration.
-
Debugging & Analysis: Recording, plotting, logs, diagnostics, and an interactive topology view to explore system relationships at a glance.
-
Integrated Development Environment: Built-in code editing, scripting, terminal, and development tools.
-
Procedural Environment Generation: Create simulation environments programmatically, with MCP-based extensibility and LLM-assisted workflows.
-
Reinforcement Learning: An RL Cockpit for visualizing, monitoring, and debugging robot training.
-
Extensibility: MCP support for extending workflows, debugging, executing commands and building additional tools.
-
User Experience: Drag-and-drop interactions and visual workflows designed to reduce repetitive configuration and command-line operations.
The goal isn’t simply to put existing ROS tools into one application.
It’s to make robotics development more connected, intuitive, and accessible, while still providing the depth and flexibility experienced developers need.
RobotLens is still under active development, and I’m preparing it for early users.
I’d value feedback from people working with ROS and robotics every day.
I’m also open to collaborations, partnerships, and conversations with individuals, research labs, or robotics companies interested in exploring RobotLens.
Looking forward to hearing your thoughts!
Vidoes : https://www.youtube.com/watch?v=BwFGRrJkLpk&list=PLNVRrfh5q7Zo&index=1
Website : https://robotlens.dev/
LinkedIn : LinkedIn Login, Sign in | LinkedIn