wolf-e fleet console

A throwaway console for the endpoints. The SCS replaces this.

wolf-e

… battery —

Fleet

loading…

Map

Click to add a waypoint (blue). The selected route is dashed grey; while it is being walked it turns amber, filled where the robot is heading. The robot is a green ring when localized, and a dashed grey one marked "last known" when it is not — that position is stale, not where it is now. Free floor is green, unknown grey, occupied light.

Tasks

none

Selected robot

View

A fleet-connected robot signals through this server; media is WebRTC (P2P or TURN), not a transcode here. The host field is a LAN fallback for camera, lidar and driving when the robot is not on the wire — and is still required for mapping, which has no relayed path yet. Top-down LiDAR, about 7.7 m around the robot, in its local frame — it turns with the robot, so this is "what is around me now," not the stored map. Green floor, red obstacle, grey unobserved; the blue ring is the robot with its heading. Lighter than the camera and far lower latency, so better while mapping.

Drive

Arrow keys or WASD to walk and turn, Q/E to step sideways. Hold to move while pressed; double-tap a button or key to latch continuous motion (it turns amber). Only one direction latches at a time; tap it again or press space to stop. Space, or switching tabs, stops everything. A fleet-connected robot is driven through this server, so no LAN address is needed; the host field is the fallback when it is not on the wire. Releasing a key, losing focus, closing the tab or losing the link all stop the robot — that is the gateway's deadman, and nothing in between keeps a setpoint alive on your behalf.

Routes

Doors

Open now goes to the selected robot's gateway — set the gateway host in the Camera panel.

Events

Activity

Confirm