Drone lab
Sketch a route. Arrange a swarm. Rehearse movement together in local 3D space.
Open the drone lab →From imagined worlds to physical things
Give your world senses.
One place to explore robots, drones, microcontrollers, and the observations they share.
Live Virtual world
VIRTUAL ONLYConnecting to Virtual…
Validate a route, then launch it into the world.
Waiting for world telemetry.
Four formations · up to 64 vehicles.
Simulated sensors · selected vehicle
Waiting for simulated sensors.
Sensor readings use local Y-up metres. Terrain clearance and vehicle-centre distance are ideal simulated observations; they do not detect obstacles or prevent collisions.
Motion and cameras use the Virtual world’s renderer and simulation clock. Rover height follows terrain; these sketches do not model obstacles, wheel dynamics, or flight physics.
Devices & sensors
Read an existing device’s identity, telemetry, and chain evidence through the IoT workspace.
Inspect a device →Arduino & ESP
Serial discovery and sensor ingestion have runtime foundations. Board-specific firmware, protocols, and physical validation are the next step.
No board connection claimed.Connection map
Device
Identity, serial transport, readings, and command acknowledgements.
IoT
Onboarding, telemetry, snapshots, and command coordination.
Robotics
Device observations and the path from virtual rehearsal to physical adapters.
Inspect an existing device
Use the peer and device identifiers from your runtime. This reads its current observation; it does not connect a new board.
No device selected.
A verified reading chain is preserved as reported by its owner. It does not establish sensor accuracy or physical execution.