Start the rover
Select Reset, then Start. The rover moves toward the barrier. With reduced motion enabled, select Next step to advance through the sequence.
Developer documentation
From robot program to replay.
This guide describes the Studio engineering workflow and gives you a public exercise you can run in any current browser with JavaScript enabled.
The architecture reflects the development build. The browser example uses its own fixed route and shows the sequence of a simple barrier response.
Public example
Reproduce a barrier response.
Open the Robotics Lab. Keep the demo in view while it runs. Each state is announced below the controls.
Observe the status
The rover stops at the barrier, takes the fixed detour, and arrives at the end of the route. The final status reads “Arrived at the end of the route.”
Repeat the run
Select Reset and run it again. You should observe the same sequence. The demo uses a predefined route and illustrates the behavior without benchmarking an autonomous planner.
Studio architecture
How the engineering build executes a program.
The project stores the robot definition and program. A virtual run uses that data and produces a separate record of the robot’s state.
Project and program
A .nrobot project stores the robot configuration and program. Blocks and supported subsets of Python and C++ compile into a shared intermediate representation called Robot IR.
Runtime and simulation
The runtime executes Robot IR at fixed simulation ticks. The virtual world updates robot state, and modeled sensors supply input to the program.
Debugging and replay
The engineering build can step through execution and compare recorded runs. Repeatability depends on matching the software build, project, starting state, and inputs.
Integration boundaries
Check what each interface can carry.
Source tests exercise individual integration paths. Verify each specific combination before using it in a physical or production workflow.
Robot model interchange
URDF and SDF support is bounded to tested subsets. Keep the original .nrobot project and inspect imported joints, geometry, and sensor definitions.
Recordings
Studio’s recording tools support a limited MCAP profile for run data. Keep the project file and record which build, inputs, and scenario produced the trace.
Devices and ROS 2
The optional ROS 2 bridge and board-facing transports are experimental. Live graph checks and physical device qualification remain open.
See how we test robot behavior.
Read the controlled navigation observations and the physical trials we plan to run.