Remote robot operation

Remote operation connects an operator to a particular physical robot. It needs an enrolled unit, the intended connection and supported controls. A model preview, simulation or saved task is not an operating session.

The test business had no linked servos. The setup draft and entry routes were inspected, while the control and sensor behavior below was checked against the implementation. No robot session, movement, arm command, headset connection or room scan was completed. Empty connection views and synthetic sensor data are not used as product screenshots.

Remote Robot Control

Start from Servos, select the actual unit and open its supported Steer action. This provides the unit context; a bare Steer route is not proof that a target is selected or connected.

Before using a physical session, confirm the unit identity, access, current software and actual operating environment. Review live video, status and the available controls for that model. A “connecting” message is still a connection attempt, not permission to infer that commands will arrive.

The interface provides movement and model-specific command groups, with a visible STOP control. Available actions differ by robot and controller. Learn their meaning in an appropriate simulation before considering physical use; this guide does not claim that browser screenshots verify stopping distance or emergency behavior on hardware.

End the active session through the supported controls and confirm the robot's actual state. Disconnecting, stopping a policy and stopping physical movement should not be assumed to be the same operation.

In the review, opening the route without a unit showed a connection status surface, but there was no selected servo to request a session. We left the route without sending control input. Follow Servo setup before attempting a real unit session.

Immersive Robot Teleoperation

The immersive implementation combines a supported robot session with headset view and tracking. Head control and Full Body are different modes: viewing the robot's cameras does not mean its arms are following your hands.

On supported Quest paths, the teleoperation flow distinguishes view, align and active. Alignment is a deliberate step before arm following; re-entry aligns again. Check the actual controller/backend and capability requirements rather than assuming every humanoid or headset supports the same path.

For a properly configured session, review what the interface reports before and after engagement: tracking availability, alignment, controller state and current command ownership. If the agent already controls the head, related manual controls can be unavailable. A virtual hand or cursor alone does not prove that physical motion followed correctly.

No headset, stereo video, alignment gesture or physical following was tested here. Compatibility, tracking recovery and stop behavior must be verified with the actual device and robot; source-confirmed state handling is not measured physical performance.

Robot Arm Control

Arm controls depend on the robot, supported controller and live joint information. The desktop arm panel and immersive hand-following path are related interfaces, not interchangeable demonstrations of hardware capability.

Review the selected robot and controller before enabling arm mode. The implementation includes an alignment/engagement boundary and separates the intended hand target from current robot feedback. Check tracking, command rate and any reach/limit indications together; a target marker is not evidence that the arm reached it.

The streaming implementation stops producing new targets when input tracking is stale, and relies on robot-side handling for that condition. This is source-confirmed behavior, not a physical safety or recovery test. Do not promise that every network loss, tracking dropout or unsupported controller recovers identically.

No arm mode was engaged, no joint target was sent and no gripper or controller action was exercised in this review. Use the actual supported setup and its device guidance before operational use.

Room Scanning

The current room-scan path uses supported R1 depth and left-eye video with pose information. It is separate from a LiDAR point-cloud view and from manually drawing a layout.

The session's Room scan panel can request the required streams, then start, pause or resume scanning. It reports conditions such as waiting for streams, loading the depth model and scanning. Review the actual frame and map-point counts before assuming a useful scan exists.

The panel distinguishes live odometry from a visual-only condition, and provides leveling and camera-height context. Its AI depth option is another processing path, not a guarantee of measured survey accuracy. Changing stream requirements can require a reconnection.

Where a scan has points, Save scan (.ply) downloads its point cloud. An optional upload to the session is a separate outcome: the interface can report that the file was downloaded but upload failed. Inspect the actual saved result before assuming a cloud copy is available.

Recording depth, left-eye video and pose for later session review is also a separate option. Starting a scan does not establish that all source data was recorded, and downloading a PLY does not by itself create a ticketing floor plan, work order or robot navigation map.

No depth stream, odometry feed, scan, recording or export was created in this review. A populated real scan and its physical accuracy remain unverified; no fabricated room map is included.

Troubleshooting

Symptom	What to check
Steer remains on connection status	Open the intended enrolled unit and inspect session availability and permissions.
Controls differ from another robot	Check model, controller and current capabilities.
Headset view works but arms do not follow	Viewing, alignment and active arm control are separate states.
An arm target differs from the robot	Review live feedback, limits, tracking and controller state; a marker is not completion.
Room scan waits for streams	Verify supported depth and left-eye tracks and the active connection.
Scan is downloaded but missing from the session	Check the separate upload result.

Continue with Servos, Policy deployment, Simulator and Stints.